[01:29] maic23: It looks like you have another existing and active Launchpad account (perhaps you deactivated your login.ubuntu.com account without first deactivating your Launchpad account?). What do you want done with the two different accounts? [01:30] cjwatson: Maybe merge them if possible? [01:30] maic23: which of the two usernames would you prefer? [01:31] The older one [01:31] (probably can't do it tonight, but tomorrow morning for sure) [01:31] This seems a rather common issue. I wonder if it was possible to warn in such case [01:31] OK [01:31] there's an open bug [01:31] oh, ok fine. [01:32] And thx for having a look! [01:32] https://bugs.launchpad.net/launchpad/+bug/1607242 - it is ... complicated to get right [01:32] Ubuntu bug 1607242 in Launchpad itself "Logging into a placeholder person OOPSes if email address already on another person" [Critical,Triaged] [01:33] maic23: is it your belief that you deactivated your login.u.c account as I theorised above? [01:35] I think I clicked on "Permanentely delete account" on https://login.launchpad.net/+delete but I am not sure. It has been some weeks. [01:36] The new account was created recently. My old account is a couple of years old [01:36] ok === chihchun_afk is now known as chihchun [02:03] maic23: Try now? [02:03] works. Thanks again [02:04] no problem, sorry it took a while to be around at the same time as you === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === JanC is now known as Guest39941 === JanC_ is now known as JanC === maclin1 is now known as maclin [11:16] I'd like to identify the sponsor and uploader of a package_upload object, but don't see a suitable property. Any tips? The only way I can see is to read the changes file for "Changed-by" and check who signed the dsc file for the sponsor. [11:17] But that's awkward because I don't necessary have all signers' keys locally. [11:17] necessarily [11:18] If I do have to parse the changes file, is there a convenient parser in Python I can use? Or custom regex time? === _salem is now known as salem_ [11:29] python-debian parses changes file just fine [11:31] (or any other rfc 822 parser, depends if you want to parse fields like Files which deb822 already splits for you, etc) [11:52] rbasak: udd.debian.org has an ubuntu_upload_history table too, FWIW [11:58] Laney: thanks, but in this case I'm processing unapproved/new queue items, so I presume they won't be in there? [11:58] mapreri: useful, thanks. [11:58] rbasak: nope, sorry [12:09] rbasak: We do have it internally; would you like to try to put together a branch to export the information you need? [12:15] cjwatson: useful to know. I'd like to add it but it's not essential so I probably shouldn't go too deep into this right now. I might get back to you for some pointers later though, thanks. [12:15] I was hoping it'd be already there :) [12:17] It's only informational - I have some code working now that imports new/unapproved queue items into our git tree, so that should help with SRU reviews. I can now easily diff against any other version instantly. I was hoping to add some metadata to the commit message to assist reviewers (eg. if contact is required) but I can leave the people information out for now, and implement it later now that I know [12:17] how I'd approach it. [12:17] Basically self.sources[0].sourcepackagerelease.creator and self.signing_key_owner or something like that. With a little care they could be exported as extra read-only attributes. [12:17] Noted in my logs, thanks :) [12:18] * rbasak unwinds his stack and gets back to reviewing the thing he just wrote tooling to review :-) === chihchun is now known as chihchun_afk [16:15] cjwatson: hi. i want to do a partial archive rebuild w/python3.6 as supported so we can start identifying ftbfs and fix them. my goal is to enable 3.6 as supported (not default) for z. doko suggested asking you to create a python packageset to make that partial rebuild easier. what do you think? (iirc, he or i had a script to identify packages needing rebuild for the 3.5 transition,but i know i don't have that any more) [16:16] barry: well, I can't do that, creating packagesets requires either admin or techboard [16:17] barry: I guess it's a reasonable approach though [16:18] cjwatson: that or just ad-hoc a rebuild in a big ol' ppa [16:19] that seems easier, frankly [16:20] cjwatson: ok. let me pursue that approach first. thx [18:18] cjwatson: Sorry, just saw your reply. I have no idea how I got two accounts. Can they be merged into one? If one is new (within the last week or so), simply deleting it would fine too [18:18] thanks [18:18] ppannuto: You have one from 2006 and one from 2017, I think [18:19] ppannuto: Does https://launchpad.net/~psquared89+ubuntu look familiar? [18:19] It has your address on it, at least [18:19] yeah, that's an old e-mail for me [18:19] can everything move over to ppannuto? [18:20] ppannuto / pat.pannuto@gmail.com is current username / email for everything in my life [18:20] Either way round is fine. [18:20] I guess you must have deleted your login.ubuntu.com account at some point without deactivating your Launchpad account first. [18:21] interesting, don't remember doing that, but I'd believe it - anything I need to do on my end to fix? [18:22] ppannuto: Actually it might be better if I merged into ~psquared89+ubuntu, freeing up ~ppannuto, and then you can rename your account; that would preserve the account's longevity [18:22] ppannuto: Is that OK with you? [18:22] sounds good to me [18:28] ppannuto: done; you should now be able to log in and change your username on https://launchpad.net/~/+edit [18:30] perfect; looks like everything is fixed - thanks for your help! [18:30] no problem [19:13] cjwatson: hi again, different question. i'm looking at LP: #1647204 and LP: #1655298 (gpgme hang during tests). can buildd's schroot sudo mode be easily reproduced on a local (zesty host) sbuild? [19:13] Launchpad bug 1647204 in gpgme1.0 (Ubuntu) "1.8.0-2 FTBFS in zesty 17.04" [Undecided,Confirmed] https://launchpad.net/bugs/1647204 [19:13] Launchpad bug 1655298 in launchpad-buildd "Indefinite build hangs during python tests of gpgme1.0 v1.8" [Undecided,New] https://launchpad.net/bugs/1655298 [19:44] cjwatson: thanks for the git cherry picks [19:44] cjwatson: would unsuspending https://code.launchpad.net/~gophers/golang/+git/golang be an apprpopriate test? [19:50] cjwatson: er the staging version of that import, rather [20:16] mwhudson: I have a test on qastaging (not staging), but it's broken at the moment and I haven't yet figured out why [20:17] cjwatson: worth me poking too? [20:18] barry: in principle probably yes; in practice it might be easier to deploy https://jujucharms.com/u/launchpad/launchpad-buildd/ (requires login for some reason) [20:19] mwhudson: if you fancy dusting off your codeimport chops; I've evidently broken something fairly badly, as you can see from https://code.qastaging.launchpad.net/~cjwatson/golang/+git/golang and https://code.qastaging.launchpad.net/~cjwatson/man-db/+git/tmp [20:19] "fatal: remote part of refspec is not a valid name in +refs/heads/master:refs/heads/master" -> sadface [20:20] cjwatson: that's fairly impressive [20:21] cjwatson: is it possible to push to hosted git on qastaging still? [20:21] mwhudson: I haven't checked but also haven't changed much there recently [20:21] mwhudson: (been concentrating today on getting tests to pass on xenial, which involves debugging EVERYTHING simultaneously) [20:21] cjwatson: woo [20:21] barry: you can look at sbuild-package and sbuildrc in lp:launchpad-buildd for the configuration that's in use [20:22] cjwatson: well no massive hurry, i can go on clicking retry on the prod import for now [20:22] I don't think that'll achieve anything :) [20:22] pretty sure there's a command line length limit breaking stuff [20:22] or similar [20:23] mwhudson: I would definitely appreciate help, but if you don't manage it then I'll probably be able to have a look either tomorrow or first thing next week [20:23] always assuming that whatever comes out of the Cape Town sprint doesn't upend my world :P [20:24] cjwatson: clicking retry gets the master branch updated [20:24] which is all i actually care about [20:24] aha [20:24] I wondered why you were bothering [20:24] cjwatson: i'll see how long the email mountain takes today (took some leave, pity my inbox) [20:24] yeah, I meant to do that this week but ... === salem_ is now known as _salem [20:45] cjwatson: hmm, that link doesn't resolve for me, but in any case i'm going to try to debug it elsewise. thanks [20:51] barry: for some reason you have to sign in with SSO; I think it should work then? === smoser` is now known as smoser