[00:00] if the branch is renamed, then the target has changed [00:00] hence the message appears correct [00:00] Hm, no, the target has no changed in that case [00:00] The target is the product, source package, or person [00:00] It doesn't involve the name. [00:00] and if the person is different.... [00:00] Rename != change owner [00:01] i meant change owner above sorry [00:01] Right, that makes more sense :) [00:01] i knew what i meant even if my typing didn't :-/ [00:02] Heh [00:02] http://i.imgur.com/uFbIq.png [00:02] wallyworld_: Confirmed that renaming triggers the notification [00:02] So there is a bug of some sort [00:02] hmmm. bollocks [00:03] 3 notification messages is not good either [00:03] wallyworld_: .target isn't what you think it is [00:04] It's IBranchTarget(person) for a personal branch [00:04] Not None [00:05] right, so the first bit of the check is bogus [00:06] Could you just store the old branch.target before calling setTarget, then compare it with the one afterwards? [00:13] perhaps, i'll look at it after i finish my current branch === darjeeli_ is now known as darjeeling === vednis is now known as mars [01:33] hi, can anyone manage to get this hg branch imported? https://code.launchpad.net/~renatosilva/pidgin/trunk === michaelh is now known as michaelh|away === stub1 is now known as stub === michaelh|away is now known as michaelh === ajf__ is now known as ajf_ === michaelh is now known as michaelh|away [13:29] I'm curious [13:29] what determines when I can hide others' comments on bugs? [13:30] I can't work out a pattern. On some bugs I can do it and on others I can't. Both of the ones I'm looking at now (one in each category) have upstream as well as Ubuntu tasks, so it's not as simple as that === slank` is now known as slank === slank is now known as Guest43410 === matsubara-afk is now known as matsubara === yofel_ is now known as yofel [15:06] is there an issue uploading to ppa's? been 2.5h and haven't got the confirmation email, and don't see it waiting to build yet === issyl0 is now known as Guest45577 === Guest45577 is now known as issyl0 [15:59] launchpad, y u no accept my PPA upload?? ;-) [15:59] launchpad seems to be ignoring my attempt to upload to my ppa https://launchpad.net/~canonical-hwe-team/+archive/sputnik-kernel/+packages ... I tried yesterday, and again this morning, but have not received any accept/reject email from my attempt to upload a new revision of one of those packages. [16:00] can someone investigate logs or read the tea leaves or whatever, to sort out whats happening here? === sinzui changed the topic of #launchpad to: Reduced Builder capacity at present | Help contact: sinzui, jcsackett | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support: https://answers.launchpad.net/launchpad [16:33] this page has refused to load for some days, can anyone help? https://bugs.launchpad.net/elementary/+milestone/luna-beta1 === codygarver is now known as cody|dogwalk === Guest43410 is now known as slank === cody|dogwalk is now known as codygarver [17:04] sinzui, jcsackett, any idea about the dput upload issue? launchpad not accepting new packages and not sending confirmation emails anymore today, atleast as of 8hours ago [17:05] I will look [17:06] patdk-wk, sinzui: is that ^^ a known issue then? I'm also seeing that, since yesterday afternoon. [17:07] I can't find anything about it being known [17:07] patdk-wk: oh, your having described it as "the dput upload issue" had me fooled! ;-) [17:08] well, I used dput to upload to my ppa, dunno if that is related or not [17:08] but more info generally helps :) [17:08] kamal, patdk-wk, Lp is running days behind schedule because of loss of builders last month. I have not heard of any issues where packages were not being accepted [17:08] sinzui, I have been submitting packages all week [17:08] normally accepted within minutes [17:08] sinzui: specifically, its not sending the usual accept/reject email at all, since yesterday [17:08] except today [17:09] and still not showing up in the ppa as waiting to build [17:09] understood [17:09] sinzui, patdk-wk: I even re-uploaded after waiting 12 hours, but still no response at all from launchpad [17:10] patdk-wk: have you verified that the package you uploaded is signed with the same gpg key which is associated with your lp account? [17:10] yep, I had just tried a reupload a few min ago [17:10] kamal: ^^ [17:10] dobey: yes, thats not the problem [17:10] dobey: launchpad would have / should have sent a reject email if I'd mis-signed the package [17:10] dobey, I would, but I have never touched that, and have a dedicated machine to package it [17:10] kamal: nope [17:11] dobey: well, its not the problem anyway :-) [17:11] kamal: it wouldn't know who to send the mail to :) [17:11] Primary key fingerprint: 66BE 5DCF 814A 4787 18D3 144B 19D4 8158 67A4 B7F2 [17:11] Subkey fingerprint: F934 1363 F265 DD0E F0EC D29E 7087 4573 9DC4 D013 [17:11] pub 1024D/67A4B7F2 2005-11-20 Danny Swett [17:11] Patrick Domack [17:11] hmm, how to compare them [17:11] if you don't get an accept/reject mail, and no package was accepted into the PPA, it's almost always a case of mismatched GPG keys [17:12] dobey: ok, double checked. that's not the problem. [17:13] dobey: its the same key I always use (and I upload packages to this PPA using this same build procedure quite regularly). [17:13] 0x66be5dcf814a478718d3144b19d4815867a4b7f2 [17:13] well that defently matchs [17:13] kamal: lp:~kamal is your account? [17:13] dobey: plus, it seems unlikely that patdk-wk and I would both independently be suddently "doing it wrong" :-) [17:13] dobey: kamalmostafa [17:14] ~patrickdk here === matsubara is now known as matsubara-lunch [17:17] dobey: I think that perhaps you're incorrect about launchpad using an email address from your gpg sig as the address to send accept/reject email to. [17:17] consider that there are often many email addresses associated with a gpg key -- how would it know which to use? I think it uses the Changed-by: line in the _source.changes file instead, and that it is unrelated to the signing key. [17:18] patdk-wk, kamal you are both using dput? [17:18] kamal: no, it gets the e-mail address from your account [17:18] sinzui: yes. [17:18] kamal: if the gpg key you signed with is wrong, it can't figure out which account you belong to [17:18] * sinzui is asking webops if a process is not picking up [17:19] dobey: ok, gotcha -- and yes, now I realize also that I use different Changed-by: lines sometimes, but I always get my accept/reject emails to the same address [17:31] kamal, patdk-wk We see uploads, but I also see a lot coming from Lp itself. We have restarted a process. Please try uploading again and see if we get a proper response [17:31] ok, uploaded again [17:32] sinzui: ok, done. thanks for chasing this down! [17:33] kamal, well I am just an intermediary. Ping when you get an email. That will confirm that the sftp server was throwing a wobbly [17:33] s/when/if/ ;-) [17:33] sinzui: will do [17:34] kamal, which ppa were you sending to? Can you say? [17:34] https://launchpad.net/~canonical-hwe-team/+archive/sputnik-kernel [17:45] sinzui: its been about 13 minutes -- no email response from launchpad. patdk-wk, how about you? [17:45] nothing [17:45] if it was broken and fixed now, I would expect a backlog, but dunno how it works :) [17:46] I have seen those emails take 2hours before though [17:47] patdk-wk: yeah, I dunno how it works either. I normally expect to get my accept email with 5 minutes of uploading (assuming no backlog, if that is actually relevant) [17:47] patdk-wk, I don't see a change either [17:48] We just saw an upload arrive and be queue for Ubuntu [17:48] This might just be a ppa issue. [17:48] which is what we are looking at now [18:17] patdk-wk, We see gpg verification rejects. for keys that did work. Are you signing with a subkey perhaps? [18:17] patdk-wk: hey, are you (like me) signing your upload with a subkey of your primary key? [18:17] :-) [18:18] patdk-wk: specifically, I just discovered that if I sign with my primary key instead of my subkey, the upload works properly -- whereas signing with my subkey certainly worked until mid-yesterday. [18:28] patdk-wk, I have confirmed from the log that your error (no public key) is the same as kamal's === codygarver is now known as cody|brb [18:43] how is it no public key? [18:44] http://pastebin.com/XVvc6KPB [18:44] and that fingerprint matchs my launchpad account one [18:46] hmm, I probably use the subkey [18:46] and consider it bad form to use the primary key [18:47] the primary key is only to be used to sign subkeys, atleast in my usage === cody|brb is now known as codygarver [18:52] patdk-wk++ absolutely agreed! [18:53] patdk-wk: but I'm almost sure this is the problem -- can you verify that you are indeed using a subkey then? and (if you are inclined) test an upload signed with the primary to prove that works? [18:53] patdk-wk: I've just filed this about the issue: https://bugs.launchpad.net/launchpad/+bug/1053568 [18:53] Ubuntu bug 1053568 in Launchpad itself "PPA uploads signed with subkeys silently fail" [Undecided,New] [18:53] heh, I'm attempting to figure out how to tell, and how to force it :) [18:54] patdk-wk: I already spent that 10 minutes :-) so .... [18:54] I had another cert issue, dealing with ADP, always fun [18:54] so was away for abit === matsubara-lunch is now known as matsubara [18:54] patdk-wk: debsign '-k5409E422!' your_source.changes [18:54] ah, I let dpkg-buildpackage sign it for me [18:54] patdk-wk: the exclamation mark there is the magic that says "use the primary, not a subkey" [18:55] patdk-wk: well don't do that! :-) [18:56] it accepts -k and passes it along :) [19:00] ok, I was def using the subkey before [19:00] uploaded with primary now [19:00] got confirmation [19:02] patdk-wk: ok, thanks. I'm entirely convinced that we've identified the problem. [19:03] this issue wouldn't annoy me so badly if the builders wheren't so far behind :) [19:09] patdk-wk: they are not soo far behind at all https://launchpad.net/builders [19:09] 14hours? [19:10] not as bad as sometimes (2-3days), but [19:12] patdk-wk: there havebeen some issues with the builders since our move, but compared to a few weeks ago it's a lot better and should be even better in the coming weeks [19:13] ya, but between the builder and this issue, it's pushed me back a full day now [19:20] kamal: did you add a new subkey recently and upload with it, but didn't push the updated key to the keyring.ubuntu.com server? [19:20] dobey, I have only ever used my subkey [19:20] for the last 3 years [19:21] dobey: no, not at all. I've been using this exact subkey since january [19:21] I have never uploaded with anything except that same subkey :) [19:21] ah ok, weird then :) [19:21] dobey: fundamentally: uploads with this key worked two days ago (the logs show such) but don't anymore. [19:21] subkey generated 2009-07-12 [19:23] dobey: I will mention that you were entirely correct when you said "it's almost always a case of mismatched GPG keys" ... its just that the 'mismatch' seems to be due to an actual launchpad breakage. [19:25] yeah, i guess a deployment today(?) broke something [19:25] I first noticed the problem about 24 hours ago, and I know that it wasn't a problem 48 hours ago. [19:26] ya, my last upload was 2/3days ago [19:37] Ouch the amd64 build queues are really backed up... Asked to build a 4KB package and there is a 13 hour delay. [19:39] czajkowski: please tell the builders to build faster, k? ;-) [19:46] lol [19:47] did someone click the turbo button? so we only going 2mhz instead of 16mhz? [19:47] heh it's a 14 hrs delay now. That will teach me to complain! [19:48] heh those were the days.... === michaelh|away is now known as michaelh === codygarver is now known as cody|afk === sinzui changed the topic of #launchpad to: Reduced Builder capacity at present | Help contact: - | Launchpad is an open source project: https://dev.launchpad.net/ | This channel is logged: http://irclogs.ubuntu.com/ | User Guide: https://help.launchpad.net/ | Support: https://answers.launchpad.net/launchpad === michaelh is now known as michaelh|away === michaelh|away is now known as michaelh === cody|afk is now known as codygarver === michaelh is now known as michaelh|away === codygarver is now known as cody|afk === Guest57491 is now known as cheako