← Back to team overview

launchpad-users team mailing list archive

Re: Unable to push package to my PPA

 

On Wed, Jul 16, 2014 at 06:44:59PM +1000, William Grant wrote:
> On 16/07/14 05:27, Darryl L. Pierce wrote:
> > Our team Launchpad has a PPA [1]. I'm trying to push a package named
> > "qpid-proton" up to that repo, but it is being consistently rejected
> > with the message:
> > 
> > Files specified in DSC are broken or missing, skipping package unpack
> > verification.
> > 
> > but it's not telling me which file(s) are missing or broken.
> > 
> > I had previously pushed this exact same package to a different PPA [2]
> > that our team has, which we're deleting (we want to put everything under
> > the "released" PPA).
> > 
> > What am I doing wrong?
> 
> There was another line in the email you got:
> 
> 2014-07-15 19:07:22 DEBUG   Unable to find qpid-proton_0.7.orig.tar.gz
> in upload or distribution.
> 2014-07-15 19:07:22 DEBUG   Files specified in DSC are broken or
> missing, skipping package unpack verification.
> 
> Your .dsc refers to an orig.tar.gz that doesn't exist in your PPA, so
> your upload needs to include it. Rebuild your package with "debuild -S
> -sa" instead of "debuild -S" and upload it again.

So I did this (thank you) and when I try to push I'm now seeing:

Rejected:
File qpid-proton_0.7-1.2.debian.tar.gz already exists in Qpid Proton
Debian Packages, but uploaded version has different contents. See more
information about this error in
https://help.launchpad.net/Packaging/UploadErrors.
Files specified in DSC are broken or missing, skipping package unpack
verification.

It seems that uploads to this new PPA (qpid/released) are being rejected
due to the contents of the old one (qpid/proton) that we plan to delete.
Which is odd since the qpid-dispatch package existed in that other PPA
but I was able to upload it as well.

I've now deleted the older ones and will try to upload again later,
unless there is a more practical approach. I tried downloading the
.orig.tar.gz for Proton and rebuilding using that (per the link in the
rejection email) but that didn't work and produced the same error again.

-- 
Darryl L. Pierce <mcpierce@xxxxxxxxx>
http://mcpierce.blogspot.com/
Famous last words:
   "I wonder what happens if we do it this way?"

Attachment: pgpGn5KJyt26P.pgp
Description: PGP signature


Follow ups

References