Build Uploaded Successfully But Does Not Appear on Launchpad

Asked by Andrew Martin

Hello,

I am attempting to upload my first package to a PPA, the latest release of libvirt (1.0.2). I have successfully signed the changes file, imported my GPG and SSH keys, and signed the Ubuntu Code of Conduct. dput tells me that the upload was successful:
$ dput ppa:asmartin/backports libvirt_1.0.2-2_source.changes
Checking signature on .changes
gpg: Signature made Tue 05 Feb 2013 02:53:44 PM CST using RSA key ID 9F614DDF
gpg: Good signature from "Andrew Martin <email address hidden>"
Good signature on /home/amartin/libvirt_1.0.2/libvirt_1.0.2-2_source.changes.
Checking signature on .dsc
gpg: Signature made Tue 05 Feb 2013 02:53:20 PM CST using RSA key ID 9F614DDF
gpg: Good signature from "Andrew Martin <email address hidden>"
Good signature on /home/amartin/libvirt_1.0.2/libvirt_1.0.2-2.dsc.
Package includes an .orig.tar.gz file although the debian revision suggests
that it might not be required. Multiple uploads of the .orig.tar.gz may be
rejected by the upload queue management software.
Uploading to ppa (via ftp to ppa.launchpad.net):
  Uploading libvirt_1.0.2-2.dsc: done.
  Uploading libvirt_1.0.2.orig.tar.gz: done.
  Uploading libvirt_1.0.2-2.debian.tar.gz: done.
  Uploading libvirt_1.0.2-2_source.changes: done.

This is a newer version of the libvirt source code than is provided in the Ubuntu repositories, so the .orig.tar.gz is needed.

My very first attempt (1.0.2-1) did appear on the builds list, https://launchpad.net/~asmartin/+archive/backports/+builds?build_text=&build_state=all , but it failed because the .orig.tar.gz source code did not contain a Makefile, which causes dh_auto_clean to fail. I added a fake Makefile (since it will be overwritten by dh_auto_configure) to solve this problem. I tried incrementing the version number from 1.0.2-1 to 1.0.2-2, but still no new builds appear in the above URL. Can someone please advise what else I can try?

Thanks!

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Andrew Martin
Solved:
Last query:
Last reply:
Revision history for this message
William Grant (wgrant) said :
#1

You were sent an email about the package's rejection:

"""
2013-02-06 00:00:15 DEBUG Sending rejection email.
[...]
2013-02-06 00:00:15 DEBUG File libvirt_1.0.2.orig.tar.gz already exists in Ubuntu Backports, but uploaded version has different contents. See more information about this error in https://help.launchpad.net/Packaging/UploadErrors.
2013-02-06 00:00:15 DEBUG Files specified in DSC are broken or missing, skipping package unpack verification.
"""

The orig.tar.gz is, as the name suggests, meant to be precisely the original upstream tarball (that is, it should be byte-identical to http://libvirt.org/sources/libvirt-1.0.2.tar.gz), so it doesn't make sense to upload the same filename again with different content. If you've uploaded a bad tarball you'll need to upload the corrected one with a different version (eg. 1.0.2+repack1).

Revision history for this message
Andrew Martin (asmartin) said :
#2

Thanks for the clarification - I see now that the rejection messages were being filtered by my email client.

The build process gets farther this time, but fails now because of a missing build dependency:
checking for pkg-config... no
checking libxml2 xml2-config >= 2.6.0 ... configure: error: Could not find libxml2 anywhere (see config.log for details).

Is there any way I can specify additional packages required for the build?

Revision history for this message
William Grant (wgrant) said :
#3
Revision history for this message
Andrew Martin (asmartin) said :
#4

Thanks