[10:06] <sophomeric> I just uploaded a new new package to https://launchpad.net/~researchgate/+archive/ubuntu/nginx-dev/ and got a rejection that it already exists. It's the first upload of a new version, so I'm not sure why it says it exists already?
[10:07] <sophomeric> You'll see 1.9.13 there, and I just pushed 1.9.15 but got "File nginx_1.9.15.orig.tar.gz already exists in Primary Archive for Ubuntu, but uploaded version has different contents".
[10:11] <cjwatson> sophomeric: Right, if the source exists in the primary Ubuntu archive then files can't have the same name but different contents.
[10:11] <cjwatson> sophomeric: Just fetch nginx_1.9.15.orig.tar.gz from Ubuntu and use that to build your source package.
[10:14] <sophomeric> Ah, okay. Just the first time I've hit that and I've been doing this same build process for awhile.
[10:15] <sophomeric> You can see a nginx_1.9.13.orig.tar.gz on the existing build I have there.
[10:19] <cjwatson> sophomeric: Sure.  But when you uploaded that, 1.9.13 hadn't yet been uploaded to Ubuntu, so there was no conflict.
[10:19] <cjwatson> sophomeric: In this case Ubuntu had it first.
[10:20] <cjwatson> sophomeric: There's usually no point in having a different orig from Ubuntu.  In general orig files ought to be downloaded directly from upstream, not built yourself.
[10:23] <sophomeric> Well it's generated from checking out the 1.9.15 tag of nginx's github source =P
[10:23] <sophomeric> I'm not trying to argue btw, it's just a little weird and I'm curious.
[10:24] <sophomeric> Does that mean Ubuntu go the same message when they tried to push 1.9.13 after me? :D
[10:25] <cjwatson> No, we don't block Ubuntu on PPAs, only the other way round.
[10:26] <cjwatson> Generating it from checking out the tag won't give you a bitwise-identical tarball.  There are tarballs on nginx.org.
[10:27] <cjwatson> Ubuntu uses http://nginx.org/download/nginx-1.9.15.tar.gz
[10:36] <sophomeric> Well it's a little harder to track your changes in a fork then though.
[10:37] <cjwatson> Uh
[10:37] <cjwatson> Those go in the packaging delta, surely.
[10:37] <cjwatson> Or else give it a different version number.
[10:38] <cjwatson> I mean a different upstream version number.
[10:38] <cjwatson> If the orig.tar.gz part of your source package is identical to upstream 1.9.15, then use their tarballs.  Otherwise, call it 1.9.15+sophomeric1-0ubuntu1 or similar.  There isn't a middle ground.
[10:40] <sophomeric> Yeah, that's what I'm going to do for now at least.
[12:24] <sophomeric> Maybe this is a silly question, but is there a trick to get launchpad to build against openssl 1.0.2?
[12:32] <cjwatson> sophomeric: Supply suitable packages in your PPA or in some other PPA you declare as a dependency.
[12:36] <sophomeric> Thanks. I didn't realize I was getting that from a PPA already =/
[12:36] <sophomeric> I had libssl-dev in build-depends, which was 1.0.2 on my environment but it kept coming out of launchpad linked to 1.0.0
[12:38] <cjwatson> sophomeric: It will be coming from the primary Ubuntu archive, but you can override it in your PPA if you want.
[18:20] <oparoz_> Hi all, the builders seems to have lots of proxy problems today. Is it just because of the release of 16.04?
[18:36] <oparoz_> https://bugs.launchpad.net/launchpad/+bug/1573184
[18:36] <ubot5`> Launchpad bug 1573184 in Launchpad itself "git clone in builders lead to proxy error 407" [Undecided,New]
[21:07] <est31> is it possible to use external git repositories for bzr-builder?
[21:11] <dobey> you mean for recipe builds? no, but you can import them into a bzr branch on launchpad, or wait for git->git import
[21:16] <est31> yeah currently we have an imported bzr branch
[21:16] <est31> but there is this bug with signed git commits
[21:16] <est31> they break the whole import
[22:45] <est31> dobey, is there a tracker bug for git->git import?