Updated certification-docs package not appearing on Launchpad

Fri Dec 18 17:28:10 UTC 2015

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/17/2015 06:09 PM, Jeffrey Lane wrote:
> Any luck? And as Brendan mentioned, perhaps the prod stack outage
> us causing this?

Thanks everybody for your help. It turns out that I fumble-fingered
some OpenPGP key management a while ago and managed to deactivate my
most important key. This caused the failure. It's now corrected. FWIW,
there's an existing 8-year-old bug about the lack of feedback in cases
like this:

https://bugs.launchpad.net/launchpad/+bug/136593

I've added some comments in the hopes that it gets some well-deserved
attention.

> On Thursday, December 17, 2015, Roderick W. Smith 
> <rod.smith at canonical.com <mailto:rod.smith at canonical.com>> wrote:
> 
> On 12/17/2015 01:49 PM, Daniel Manrique wrote:
>> Launchpad should always send the email, even if to say it
>> rejected the package because of $REASONS.
> 
>> At this point it looks like something is wrong with Launchpad.
>> It may make sense to ask in #launchpad (I think it's on
>> freenode?). I was about to go in and do it for you but I'd just
>> be a middleman, so I suggest you ask there directly.
> 
> I've done so. No reply yet (but it's only been about four
> minutes).
> 
>> On Thu, Dec 17, 2015 at 1:25 PM, Roderick W. Smith 
>> <rod.smith at canonical.com <javascript:;>> wrote: On 12/17/2015
> 11:43 AM, Daniel
>> Manrique wrote:
>>>>> This is weird. Can you try creating a PPA under your user 
>>>>> (https://launchpad.net/~/+activate-ppa) and uploading the 
>>>>> package there?
> 
>> Done, and no luck:
> 
>> https://launchpad.net/~rodsmith/+archive/ubuntu/testing
> 
>> I tried doing this both from my laptop (which I use for official 
>> Canonical projects) and my desktop (which I use for my rEFInd 
>> project, among other things). I'm getting no e-mail saying
>> anything about the files being accepted or rejected. Aside from
>> the complaint if I try uploading again, it's as if I never
>> uploaded anything.
> 
>> I also tried uploading an interim copy of rEFInd to my testing 
>> PPA, and it was accepted, although the web UI says that the
>> build is scheduled for an hour from now. The fact that rEFInd
>> was accepted would tend to rule out the OpenStack outage as being
>> a cause. At this point I'm guessing there's something subtly
>> wrong with the packaging, but lintian isn't complaining, and I'm
>> able to build a package locally just fine.
> 
>>>>> On Thu, Dec 17, 2015 at 11:27 AM, Roderick W. Smith 
>>>>> <rod.smith at canonical.com <javascript:;>> wrote: Daniel
>>>>> e-mailed
> me directly
>>>>> and suggested I update the package version and resubmit,
>>>>> so I've done that, but it's still not working....
>>>>> 
>>>>> On 12/17/2015 11:24 AM, Daniel Manrique wrote:
>>>>>>>> Hey... I still don't see it :(
>>>>>>>> 
>>>>>>>> Could you show me the output of the dput command 
>>>>>>>> you're using? (if you can --debug it, all the
>>>>>>>> better).
>>>>>>>> 
>>>>>>>> 
>>>>>>>> It really should appear by now.
>>>>> 
>>>>> Sure, here's the dput output on my end:
>>>>> 
>>>>> $ dput ppa:hardware-certification/public 
>>>>> ../certification-docs_0.1.4.1-0ppa1_source.changes
>>>>> Checking signature on .changes gpg: Signature made Thu 17
>>>>> Dec 2015 11:16:51 AM EST using RSA key ID 95D058E6 gpg:
>>>>> Good signature from "Roderick W. Smith
>>>>> <rod.smith at canonical.com
> <javascript:;>>" Good
>>>>> signature on 
>>>>> ../certification-docs_0.1.4.1-0ppa1_source.changes.
>>>>> Checking signature on .dsc gpg: Signature made Thu 17 Dec
>>>>> 2015 11:16:51 AM EST using RSA key ID 95D058E6 gpg: Good
>>>>> signature from "Roderick W. Smith <rod.smith at canonical.com
> <javascript:;>>" Good
>>>>> signature on ../certification-docs_0.1.4.1-0ppa1.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 <http://ppa.launchpad.net>): Uploading 
>>>>> certification-docs_0.1.4.1-0ppa1.dsc: done. Uploading 
>>>>> certification-docs_0.1.4.1.orig.tar.gz: done. Uploading 
>>>>> certification-docs_0.1.4.1-0ppa1.debian.tar.gz: done. 
>>>>> Uploading certification-docs_0.1.4.1-0ppa1_source.changes: 
>>>>> done. Successfully uploaded packages.
>>>>> 
>>>>> 
>>>>>>>> On Thu, Dec 17, 2015 at 11:18 AM, Roderick W. Smith 
>>>>>>>> <rod.smith at canonical.com <javascript:;>> wrote: On
> 12/17/2015 10:37
>>>>>>>> AM, Daniel Manrique wrote:
>>>>>>>>>>> The PPA still shows this version:
>>>>>>>>>>> 
>>>>>>>>>>> 0.1.3-0ppa1
>>>>>>>>>>> 
>>>>>>>>>>> looks like something went wrong with the build 
>>>>>>>>>>> process if it's not letting you upload, yet 
>>>>>>>>>>> doesn't show the new version.
>>>>>>>>>>> 
>>>>>>>>>>> Could you bump your package's version to 
>>>>>>>>>>> 0.1.4-0ppa2 and reupload?
>>>>>>>> 
>>>>>>>> I've just uploaded an updated version
>>>>>>>> (0.1.4.1-0ppa1). There's no sign of it yet on the
>>>>>>>> PPA's web page, but it's only been a minute or so.
>>>>>>>> 
>>>>>>>>>>> Let me know so I can keep an eye on the PPA.
>>>>>>>>>>> 
>>>>>>>>>>> On Thu, Dec 17, 2015 at 10:06 AM, Roderick W. 
>>>>>>>>>>> Smith <rod.smith at canonical.com <javascript:;>>
>>>>>>>>>>> wrote: Hi,
>>>>>>>>>>> 
>>>>>>>>>>> I recently made some changes to the 
>>>>>>>>>>> certification-docs package 
>>>>>>>>>>> (https://code.launchpad.net/certification-docs),
>>>>>>>>>>>
>>>>>>>>>>> 
which I submitted to out PPA with:
>>>>>>>>>>> 
>>>>>>>>>>> dput ppa:hardware-certification/public
>>>>>>>>>>> 
>>>>>>>>>>> This submission seemed to be accepted;
>>>>>>>>>>> however, it's not appeared in the PPA, and I
>>>>>>>>>>> can find no error messages in my e-mail inbox
>>>>>>>>>>> or on the PPA's web interface 
>>>>>>>>>>> (https://launchpad.net/~hardware-certification/+archive/ubun
t
>
>>>>>>>>>>> 
u/p <https://launchpad.net/~hardware-certification/+archive/ubunt u/p>
> 
>>>>>>>>>>> 
> ublic)
>>>>>>>> 
>>>>>>>>>>> 
>>>>> 
>>>>>>>>>>> 
>> .
>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>> I
>>>>>>>>>>> can build it locally and get a valid .deb
>>>>>>>>>>> file. Attempting to resubmit the package via
>>>>>>>>>>> dput results in the error:
>>>>>>>>>>> 
>>>>>>>>>>> Package has already been uploaded to ppa on 
>>>>>>>>>>> ppa.launchpad.net <http://ppa.launchpad.net>
>>>>>>>>>>> Nothing more
> to do for
>>>>>>>>>>> certification-docs_0.1.4-0ppa1_source.changes
>>>>>>>>>>> 
>>>>>>>>>>> I made my initial submission yesterday
>>>>>>>>>>> afternoon, so there's been more than enough
>>>>>>>>>>> time for the build to happen. Does anybody have
>>>>>>>>>>> any clues about what's happening, or have
>>>>>>>>>>> suggestions for finding out what's wrong? I've
>>>>>>>>>>> done this before, albeit not very often, so I
>>>>>>>>>>> doubt if it's a permissions issue.
>>>>>>>>>>> 
>>>>>>>>>>> Thanks!
>>>>>>>>>>> 
>>>>>>>>>>>> 
>>>>>>>>>>>> -- Checkbox-devel mailing list 
>>>>>>>>>>>> Checkbox-devel at lists.ubuntu.com
>>>>>>>>>>>> <javascript:;> Modify
> settings
>>>>>>>>>>>> or unsubscribe at: 
>>>>>>>>>>>> https://lists.ubuntu.com/mailman/listinfo/checkbox-devel
>>>>>>>>
>>>>>
>>>>>>>>>>>>
>
>>>>>>>>>>>> 
> 
> -- Checkbox-devel mailing list Checkbox-devel at lists.ubuntu.com
> <javascript:;> Modify settings or unsubscribe at: 
> https://lists.ubuntu.com/mailman/listinfo/checkbox-devel
> 
> 
> 
> -- Sent from my iPhone so please forgive any typos, top posting and
> such.

- -- 
Rod Smith
Server and Cloud Certification Engineer
rod.smith at canonical.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJWdEIqAAoJEFgyRI+V0FjmwOkH+wSDxlPlZMw3SFK36oF/Uxlw
9us+bRYdY3JOXyjzXTOwpqIVR/eH5kTWxaCljsRBT7ZnyW6B9MaUzCRJ8Jo90Iqv
eYJyUY1IpaXq+VxdSRSHMFx0O4sDc4xQiNIUbd6zglqScVrlCrPFHtpAP4UGUKhU
+YKgowB7RALlcnwi4xD2ATeTzBqrDsSiL5/aDRb6u5WXj7oxBmQB7c8mhHVcOwFV
gPs+KY8xWlfmTrqH6qND3b60yla3blvW7t8h7AXCNGfKeOwMKq/epyxaBzL8OyF7
hED87GwojsfC4cRN6VQVy8NKsPpn76sLKi8oKLo4uQuoPe6rHuh/pjdp+HZbjKg=
=4MkU
-----END PGP SIGNATURE-----