=== cp16net|away is now known as cp16net === cp16net is now known as cp16net|away === cp16net|away is now known as cp16net === cp16net is now known as cp16net|away === cp16net|away is now known as cp16net === tasdomas_afk is now known as tasdomas === mwhudson_ is now known as mwhudson === yofel_ is now known as yofel === cp16net is now known as cp16net|away [14:20] Hi all. I'm the signing uploader of a source package. The build fails. What permission am I lacking in that I can not ask it to retry building, but some others can? [14:20] https://launchpad.net/ubuntu/+source/chromium-browser/28.0.1500.52-0ubuntu2/+build/4749281 [14:34] qengho: You're the signer, but you don't actually have upload permissions, I see - Chris sponsored that for you [14:34] qengho: Anyone with direct upload permissions can retry builds [14:44] cjw, thx. === cp16net|away is now known as cp16net === tasdomas is now known as tasdomas_afk === Guest14633 is now known as joey === tasdomas_afk is now known as tasdomas === tasdomas is now known as tasdomas_afk === cp16net is now known as cp16net|away === cp16net|away is now known as cp16net === rcleere_ is now known as rcleere === TheDrums_ is now known as TheDrums === cp16net is now known as cp16net|away === cp16net|away is now known as cp16net === cp16net is now known as cp16net|away === cp16net|away is now known as cp16net [22:28] is there a way to get Launchpad to keep more than one version of a package in a PPA? [22:54] autojack: not in a single series, each series can have just one version of a package [22:55] what constitutes a series? [22:55] 1.0.0 vs. 1.1.0 ? [22:57] for example, I see that the nginx PPA has 1.0.14 and 1.4.1 versions of the same package and distro combination. [22:57] the reason I ask is, the guy who maintains the Node.js PPA is saying he can't keep e.g. version 0.8 and 0.10 in the same PPA. [22:58] I was just trying to figure out what the constraints/rules are. [23:00] autojack: a series - a release of ubuntu [23:00] precise, saucy etc. [23:01] whats the url for the nginx ppa? [23:35] lifeless: sorry, I was in a meeting: http://ppa.launchpad.net/nginx/stable/ubuntu/pool/main/n/nginx/ [23:39] autojack: https://launchpad.net/~nginx/+archive/stable [23:39] autojack: one per release of ubuntu [23:40] I see that there, but in http://ppa.launchpad.net/nginx/stable/ubuntu/pool/main/n/nginx/ I see e.g. nginx-common_1.0.14-1ppa1~precise_all.deb and nginx-common_1.4.1-1ppa1~precise_all.deb [23:41] how are those different, other than version number? [23:41] as far as I can tell, if I had that PPA configured on a Precise system I could in theory install either of those two versions. [23:41] so there are some complex gc rules about when things are deleted [23:41] I suspect a change in architecture support leading to a bug [23:41] ah interesting. [23:41] so you think this is just a fluke on the Launchpad side? [23:42] positive [23:42] not normally supported? [23:42] interesting. OK then. [23:42] wgrant: ^ [23:42] autojack: it is not supported, most definitely. [23:42] I was just trying to get a definitive answer re: the basic question of >1 version being supported. [23:42] so that's fine. [23:42] annoying for me, but I can understand why it would work that way. [23:42] 1.0.14 isn't in the precise sources publication [23:43] http://ppa.launchpad.net/nginx/stable/ubuntu/dists/precise/main/source/Sources [23:43] ahhh [23:43] so I'm fairly sure LP thinks its gone, not sure why the old debs are being published still [23:43] lifeless: it is in Packages though, at least on amd64 http://ppa.launchpad.net/nginx/stable/ubuntu/dists/precise/main/binary-amd64/Packages [23:47] trism: yes, otherwise the deb wouldn't be there, but this is most definitely a bug, Such overlaps are meant to occur but only transiently.