[06:50] <morphis> can someone help me with https://ci-train.ubuntu.com/job/ubuntu-landing-054-1-build/39/console ?
[06:50] <morphis> basically the generated source package isn't uploaded as it seems as the build is warning with:
[06:51] <morphis> Package includes an .orig.tar.gz file although the debian revision suggests
[06:51] <morphis> that it might not be required. Multiple uploads of the .orig.tar.gz may be
[06:51] <morphis> rejected by the upload queue management software.
[06:51] <morphis> this one is a bit different from what we're normally doing with citrain (release canonical upstream to the archive) as I am trying to also use it for a package which we're not upstream for
[06:52] <morphis> where https://code.launchpad.net/~morphis/bluez/vivid-5.36-upgrade/+merge/278302 is the source for
[06:52] <morphis> things are already adjusted so that citrain doesn't change the version number or the changelog
[06:53] <morphis> however this work when building the first time in a silo but when updating the MP (with also bumping the version of the package) we end up with the warning above and nothing gets to the silo
[07:16] <wgrant> morphis: Is the orig.tar.gz identical to the previous upload?
[07:16] <morphis> wgrant: it should
[07:16] <morphis> wgrant: see https://code.launchpad.net/~morphis/bluez/vivid-5.36-upgrade/+merge/278302
[07:16] <morphis> rev 10 is what I added for the rebuild
[07:16] <morphis> rev 9 is what was published to the silo before
[07:17] <wgrant> 2015-11-23 19:00:16 INFO        File bluez_5.36.orig.tar.gz already exists in Landing PPA 054, but uploaded version has different contents. See more information about this error in https://help.launchpad.net/Packaging/UploadErrors.
[07:17] <wgrant> The orig tarball differs from the original upload.
[07:17] <morphis> hm, then the only reason for this can be that the orig tarball is constructed from the bzr tree
[07:18] <wgrant> Is it constructed in a deterministic way?
[07:18] <morphis> it should
[07:18] <morphis> bzr bd -S afaik
[07:19] <wgrant> Perhaps someone messed with the tags in the branch.
[07:21] <morphis> "Using the current branch without the 'debian' directory to create the tarball"
[07:21] <morphis> wgrant: there are only two tags and those are already in trunk
[07:22] <morphis> wgrant: so how does the system check if two tarballs are the same? checksum?
[07:22] <wgrant> There is no pristine-tar metadata in the branch AFAICS.
[07:22] <wgrant> Yes, the files must be bitwise equal.
[07:24] <morphis> and that wont work when building the orig tarball with --split
[14:06] <xnox> is it possible to "subscribe" all the "build" mail? that is to receive all failed to build notifications from launchpad, for ubuntu, for xenial for example?
[14:06] <xnox> (or just all of them, and then i shall filter them)
[14:08] <cjwatson> xnox: I think primary archive failures all go to https://lists.ubuntu.com/mailman/listinfo/launchpad-buildd-admins - I've never been bored enough to subscribe to find out (no archives for hopefully obvious reasons)
[14:09] <xnox> let's see how much spam that is.
[14:10] <cjwatson> xnox: There should be X-Launchpad-Build-Arch headers
[14:10]  * xnox ponders if i have to be in https://launchpad.net/~launchpad-buildd-admins/+members to be allowed to lurk that list
[14:10] <cjwatson> xnox: No
[14:10] <cjwatson> At least you shouldn't
[14:11] <xnox> good =) i don't want to be there.
[14:11] <cjwatson> That's a superpowered team anyway ...
[14:11] <cjwatson> Hm, well, being on the list might let you do evil team-claiming games
[14:11] <xnox> =/ meh, not interested
[14:12] <cjwatson> I wonder what a more sensible build mail subscription model would look like.
[14:12] <xnox> RSS
[14:12] <xnox> =)
[14:12]  * xnox is weird
[14:13] <cjwatson> A feed wouldn't be entirely impossible, though it would take some thought.
[14:14]  * xnox is half expecting for https://launchpad.net/ubuntu/xenial/amd64/+builds?build_text=&build_state=all to be a feedable location.
[15:14] <jgdx> !isitdownforanyoneelse
[15:15] <dobey> no
[15:17] <jgdx> right, it's just one url
[15:17] <jgdx> heh
[15:18] <Laney> launchpadlibrarian is
[15:18] <Laney> at least for me
[15:22] <cjwatson> yeah, I just noticed, reporting
[15:22] <cjwatson> sorry for slow response, I was in the middle of being perplexed debugging something else that turned out to be the same thing
[15:24] <cjwatson> it was an upgrade that took out dhcp that took out swift, apparently
[15:25] <Laney> np, I saw the chat about that and assumed it would be fixing itself shortly
[15:26] <Laney> there it is
[15:28] <Laney> sort of
[15:35] <cjwatson> jgdx,Laney: should be back now
[15:36] <jgdx> cjwatson, thanks
[15:36] <Laney> cjwatson: yeah, https://launchpad.net/ubuntu/+source/lttngtop/0.3-3 happened, cheers
[15:36] <jgdx> cjwatson, btw, go get against launchpad fails with an insecure warning. is this known?
[15:36] <cjwatson> jgdx: not to me
[15:37] <jgdx> cjwatson, okay, I was wondering what I should file against
[15:37] <cjwatson> jgdx: feel free to start by filing against Launchpad itself, we can reassign if need be
[15:37] <jgdx> cjwatson, thx
[15:37] <cjwatson> go get at least used to have weird special cases for LP
[15:38] <jgdx> hm, maybe that broke
[15:38] <cjwatson> there was work on removing that, I don't know if it was completed
[18:33] <Rovident> How do I change a launchpad 'team' to a project ?
[18:44] <Rovident> hello ?
[18:45] <dobey> you can't
[18:45] <dobey> you just register a team
[18:47] <Rovident> dobey , ok so how do I register a project ?
[18:49] <dobey> go to the launchpad home page and click on "Register a new project"
[18:49] <dobey> it is in fact the link immediately preceding "Register a team"
[18:55] <Rovident> dobey, OK, done that - I registering a bug.
[22:21] <clivejo> hi, Im trying to upload to LaunchPad, but everytime the upload hangs on - Uploading calligra_2.9.8.orig.tar.xz: 190104k/190105k, why is this?
[22:29] <cjwatson> clivejo: Not clear from logs; try uploading over SFTP rather than FTP?  (method = sftp, login = <your LP user name>)
[22:29] <clivejo> is the package too big?
[22:30] <clivejo> it seems to be only this one package and its driving me crazy
[22:31] <cjwatson> clivejo: It's not too big for us, but perhaps the size causes you to trigger some firewall state tracking bug along the route between you and Launchpad (speculating, but it's the sort of thing that could result in this symptom)
[22:32] <cjwatson> clivejo: I suggest SFTP because it's less likely to be fiddled with in ways that might break
[22:33] <clivejo> I dont seem to have a dput.cf
[22:33] <cjwatson> https://help.launchpad.net/Packaging/PPA/Uploading
[22:33] <cjwatson> you can create ~/.dput.cf if it doesn't exist