=== chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === maclin1 is now known as maclin === maclin1 is now known as maclin === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk [14:59] Hello, I have a question about re-uploading a release to add support for new Ubuntu releases. [14:59] Is this the best channel or should I be on #launchpad-dev? [15:00] #launchpad-dev is for development of Launchpad itself, not this sort of thing. [15:00] What's your question? [15:00] I'm the packaging manager for Ettus Research's UHD driver [15:00] https://launchpad.net/~ettusresearch/+archive/ubuntu/uhd [15:01] Our last release 3.10.1.1 went out in January [15:01] dkozel: and you wan to trigger a build for zesty? [15:01] I'd like to add packages for Ubuntu 17.04 and 17.10, but when I tried uploading them they just vanished [15:01] nacc: Yes, and 17.10 ideally [15:02] Uploading a new version works fine of course https://launchpad.net/~ettusresearch/+archive/ubuntu/uhd-3.9.lts [15:02] dkozel: Do you actually need a separate build or would the binaries from earlier releases work fine? [15:03] We link against boost and some other libraries, I think we need a separate build. [15:03] They didn't really just disappear - our system sent you a rejection email [15:03] Ah! [15:03] I'll find that and read it [15:03] Look in the email address attached to https://launchpad.net/~ettusresearch [15:04] But basically, you can't replace a given file in a given archive with a file with different contents but the exact same name [15:04] So you need to make sure that the uhd_3.10.1.1.orig.tar.xz you use for your upload is bitwise-identical to the one that's already in that PPA [15:04] We append a suffix I thought with the target release [15:04] ah [15:05] derp [15:05] That makes sense [15:05] BTW you should at some point switch over to using things like ~ubuntu17.04.1 suffixes rather than ~zesty1 [15:06] If that's prefered that's simple to do [15:06] We've wrapped the alphabet so the assumption that codenames will sort is not safe [15:06] So it'd mean that upgraders from zesty->artful with your PPA wouldn't get an upgrade [15:06] The launchpad guide suggests codenames [15:06] You'll probably need to start doing this only with your next version bump, since "ubuntu17.04" < "zesty" [15:06] Oh, where's that? I'll correct it [15:07] Let me dig [15:07] I had it open debugging this [15:07] I thought we'd got all that kind of thing a few years back but I guess we missed a few spots [15:08] "So a package for the Intrepid Ibex could be named myapp_1.0-2~ppa1~intrepid1 and for the Hardy Heron myapp_1.0-2~ppa1~hardy1." [15:09] https://help.launchpad.net/Packaging/PPA/Uploading [15:12] dkozel: thanks, corrected [15:13] No problem, thanks for the speedy help [15:14] I'll probably have to pull down the original uhd_3.10.1.1.orig.tar.xz since this should have been bit-exact already if we were able to do that [15:14] and I'll get on changing the codenames to dateed releases