| rfried | Hey, | 06:53 |
|---|---|---|
| rfried | I uploaded a new package to a new PPA about 12 hours ago, didn't receive any mail, how can I know the status ? | 06:53 |
| wgrant | rfried: If you don't get an email within ten minutes of an upload it almost always means the signature verification failed. There's some trouble with the keyservers at the moment, so a reupload might work. | 06:54 |
| wgrant | But the other possibility is that your package wasn't signed properly. | 06:54 |
| wgrant | If you tell me the package and PPA I can check the logs. | 06:54 |
| rfried | wgrant: I tried adding my ppa in a different computer, and I got: | 06:57 |
| rfried | Error: signing key fingerprint does not exist | 06:57 |
| rfried | Failed to add key. | 06:57 |
| rfried | Is it related ? | 06:57 |
| wgrant | rfried: A PPA's key isn't generated until the first package is uploaded. | 06:57 |
| rfried | shouldn't the signing key propagate through the system already ? | 06:57 |
| rfried | oh... | 06:57 |
| rfried | make sense. | 06:57 |
| rfried | thanks. | 06:57 |
| rfried | I'll try to upload again soon. | 06:58 |
| === lifeless_ is now known as lifeless | ||
| rfried | Hey. | 17:20 |
| rfried | trying to upload a package, finally I received an email but with a rejection: | 17:21 |
| rfried | bitwise_0.14-1.dsc: Unknown section 'xenial' | 17:21 |
| rfried | I thought that in section you have to write the Ubuntu release you're aiming for. | 17:22 |
| cjwatson | No, section is a different thing - the release goes in the first line of the changelog | 17:29 |
| cjwatson | https://www.debian.org/doc/debian-policy/ch-archive.html#sections | 17:29 |
| cjwatson | Ubuntu follows Debian on this | 17:30 |
| cjwatson | The Ubuntu release name goes in the "distribution" field as documented in https://www.debian.org/doc/debian-policy/ch-source.html#debian-changelog-debian-changelog | 17:30 |
| cjwatson | Though you're normally best off just using dch to set that | 17:31 |
| rfried | Hmmm...ok | 17:33 |
| rfried | Is it possible to upload a package to multiple distributions at once ? | 17:33 |
| cjwatson | No. Our usual recommendation is either to upload to the oldest distribution series and copy forward once it's built (if the same binary package will do for all of them, which is often the case) or else upload separately to each target series using the sort of version schema explained in https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging | 17:37 |
| cjwatson | Or in fact https://help.launchpad.net/Packaging/PPA/BuildingASourcePackage | 17:37 |
| cjwatson | That explains both pathways | 17:37 |
| cjwatson | Starting from "Version numbers must be unique" | 17:38 |
| rfried | thanks | 17:39 |
| Eickmeyer | cjwatson, wgrant: How's our venerable build farm doing today (I say as I notice the red X's)? | 23:18 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!