=== Lcawte is now known as Lcawte|Away [01:02] it's driving my batty that malone wraps bug comments at ~70 characters [01:03] this really screws up tracebacks [01:16] poolie: amen === Ursinha is now known as Ursinha-afk [03:12] When using malone's mail UI, do I need to indent commands by exactly one space? [03:12] Ah, must start with a space. [03:12] * twb tries again. [04:23] hello when I upload to a PPA its getting rejected that it cannot build on any arch requested [04:24] I m building for natty [04:26] hi spiv, the latest failure for your excellent loggerhead branch is a known ec2 issue that is not raised by buildbot or cause problems in production. i've sent your branch directly to PQM. [04:27] coolbhavi: Natty isn't enabled for PPAs yet. [04:37] bac: Out of interest, the same failure as I brought up on the -dev list? [04:37] StevenK: yes, test_network [04:37] StevenK: thanks for starting the discussion [05:04] I get "Page not found error" when I click on my name (I've merged my two accounts yesterday) [05:04] How can I fix this? [05:08] hello [05:09] can anyone help me? [05:11] spiv: but i didn't notice we were in [testfix]. argh. [05:11] napster: what is the account you are using? [05:11] bac: Could I put the URL here? [05:12] napster: sure, or just the account name, ~whatever [05:12] bac: https://launchpad.net/~subinsebastien [05:14] bac: haha [05:14] bac: thanks :) [05:14] spiv: your branch is cursed [05:15] bac: it's certainly one of those days around here [05:16] Sick baby, two hard drives apparently failing within hours of each other... a cursed branch is just a minor inconvenience, really ;) [05:23] ugh, sorry spiv [05:26] spiv: 2 drives? wheeee [05:27] spiv: same batch? [05:31] lifeless: same make/model at least, haven't taken the time to check the batch yet. [05:31] The 2 new ones are different makes. [05:33] I'm still quite sceptical that they really both started failing together, if only because their use patterns have been different. [05:33] But we've plugged them both into a completely different system and encountered read errors in both... [05:35] spiv did the baby throw up on them? [05:36] Haha, no, we have a baby fence to keep him away from the hardware :) === ivoks-afk is now known as ivoks === ivoks is now known as ivoks-afk === doko_ is now known as doko [12:56] Is there a way to see which blueprints have been proposed for a sprint, but not yet either accepted or denied? [13:13] Hello, is it possible to buy a voucher for a private project on launchpad ? [13:17] Yes. [13:17] * persia forgets the question number though, and encourages waiting for someone with more information to provide it. [13:17] hi, why does lauchpad tries to verify email signatures? It keeps bouncing my emails when they are signed my thunderbird [13:18] zyga, So that I don't change all your bugs claiming to be you. [13:18] persia, bzz, not true, if I drop the signature the email gets accepted [13:18] Less snarkily, send yourself a message, and try to gpg-verify it. [13:18] As you? [13:19] Without GPG signature? [13:19] persia, (I complain only because the feature is not working, lauchpad says it cannot verify that signature, this is totally broken IMHO if a signed email is rejected but unsigned is sent as intended) [13:19] No, signed emails are supposed to be accepted, and grant you extra permissions that you would have if you provided your password. [13:19] persia, note that lauchpad _has_ my key :D [13:19] Do check to make sure that you can verify the text of the message as sent. [13:20] persia: How can i buy it ? [13:20] persia: seems to be absent from the canonical store [13:20] persia, I don't care, I just want to reply to a comment by email, which I _still_can_after_disabling_the_signature_ [13:20] alopenerp, I don't recally, but I've seen the question asked here before, and people give positive answers. I recommend waiting. [13:20] persia, if lauchpad cannot process thunderbird signature that's a LP bug, if it can but cannot find my key (despite being stored on LP) it's a LP bug [13:21] persia: thanks are you a prince ? [13:21] zyga, Yes, but "cannot verify signature" implies your signature isn't considered valid. Whether it should check for unprivileged actions is an interesting question, but there's something else happening. [13:21] persia, but that is irrelevant, the fact that removing the signature makes the message pass is the crazy bug here :) [13:21] persia, perhaps [13:21] zyga, Only for unprivileged actions would that work. [13:21] persia, that's the action I'm doing [13:21] persia, I was not ever aware you could do other actions via email [13:22] I'd say, file a bug that it shouldn't verify the signature for unprivileged actions. [13:22] persia, nor does the 1-line email I get in response contain any helpful hints [13:22] You can change bugs' statuses etc via email [13:22] But I'd also spend some time trying to be sure that you have confirmed your signature is valid. [13:22] zyga: https://help.launchpad.net/Bugs/EmailInterface [13:22] geser, this is not about bugs [13:22] geser, this is about merge reviews [13:24] zyga, Same email interface. [13:24] zyga: https://help.launchpad.net/Code/Review#Email%20interface [13:25] (not that there's much difference: unauthenticated emails can add comments, appropriately authenticated emails can e.g. change statuses) [13:25] spiv, that's true [13:26] It seems like a reasonable request that LP could be more helpful when an email a) is signed but fails validation, and b) would be accepted without being authenticated [13:26] Perhaps by just accepting it, perhaps by sending back a more helpful error. [13:27] I can imagine arguments either way. [13:28] I don't think it's an either way thing. I think both are issues. [13:28] But I think there is a third issue, which is why zyga's signature isn't considered valid. [13:28] persia, I'm checking that now [13:31] persia, gpg claims the message is signed correctly [13:31] How can i buy a launchpad voucher to make a project private ? It seems to be absent from the canonical shop where it used to be before. [13:32] zyga, Hrm. I presume you round-tripped it somewhere, and didn't use thunderbird to verify? [13:32] persia, I saved the sent message to a text file, ran gpg < message.txt [13:32] Maybe double-compare the data LP has to your public key? [13:32] persia, gpg printed my keys and confirmed this is good [13:32] persia, did that too [13:33] persia, I'm not sure what's wrong really [13:33] OK. Two bugs. 1) LP shouldn't verify signatures when it doesn't affect permissions, 2) LP should be helpful when telling users it couldn't verify, and a question: Why can't LP verify your key? [13:34] File all that, and you'll probably be in best shape. I'd recommend attaching a sample signed message to the question. [13:34] persia, my key according to LP: http://keyserver.ubuntu.com:11371/pks/lookup?search=0xA2C9EB19E937897573BB3113A911E21401448FA5&op=index [13:34] persia, will do [13:35] zyga, I believe you. I don't actually know how LP works except for about two bits of code, and both are separate from your issues, I'm just familiar with requesting LP support. [13:41] persia, filed [13:41] thanks [13:43] if I'm rotating GPG keys, must I deactivate my CoC signature before I can re-sign it (it's currently signed with an expired and revoked key) [13:59] persia: There is at least one bug open about LP failing signature verification when it shouldn't, so it may not be the user's fault. [14:10] ScottK, Ah, good to know. [14:16] Hello launchpad admins, please redirect this link https://launchpad.net/~subinsebastien-gmail-merged to https://launchpad.net/~subinsebastien please! === Ursinha is now known as Ursinha-afk [14:17] * napster after an account merge, totally f**ked up! === Ursinha-afk is now known as Ursinha [14:22] split their news arm out and I'd agree with him [14:22] echan, oops [14:58] hi, http://svn.gnome.org/ says GNOME has changed to using Git for version control. Current GNOME sources can be found on git.gnome.org. All content on this site is obsolete [14:58] if the svn is obsolete then https://code.launchpad.net/~vcs-imports/dasher/trunk might be a waste ? why does that keep trying there? maybe we should close/stop that? [14:58] hi, tried to register a new project which is hosted on Google Code, but LP doesn't accept the issues link as bug URL - what can I do ? [14:59] and if it needs syncing , http://git.gnome.org/browse/dasher/ might be a better place.. [15:01] is there a possibility to leave bug URL empty ? [15:02] vish: You're welcome to register a new import. [15:03] benste: So just leave it blank for now [15:03] maxb¦ hmm, well, i'm not interested in an import , but rather wondering why we are importing.. [15:03] sinzui, can you help benste? [15:04] vish: Well, anyone can ask launchpad to import anything public [15:04] benste, I think you are saying you are trying to import a branch for a project you have already registered [15:04] maxb¦ but that seems to have been started in 2005 , and do we need to be running imports? isnt it a waste? [15:05] vish, If someone requested the import, makes sense to leave it (but it ought be up-to-date) [15:05] benste, sorry, you are trying to register a bug tracker for registered project [15:05] We can't know that nobody is using bzr to work against the package on LP and pushing to somewhere private. [15:05] oh! [15:05] sinzui: no I'm about to register the project itself [15:05] as it didn't exists yet [15:06] benste, form does not ask for a URL [15:07] oh, benste are you on a bug page trying to report an upstream bug & register a project? [15:07] sinzui: yes [15:07] oh well, thought I'd be saving the planet a bit ;p , but if it is needed sure, I was just curious [15:08] benste, the form is trying to locate a matching bug tracker or to register one, but it cannot identify the type. [15:08] don't know [15:08] issues for the projrct are [15:08] here [15:08] http://code.google.com/p/eid-mw/issues/list [15:08] benste, I think you may need to try registering the bug tracking in an other browser tab, then try registering. [15:09] and I thought i could simply enter this URL in the bug url label [15:09] ah :-) [15:09] where can I register it ? [15:09] benste, gmb, allenap, deryck: I do not think Lp has bug watch support for google so it will not be possible to register a project & link the bug to upstream [15:10] sinzui: Right, no support for Google yet. [15:10] and If i want to link it upstream only possibility is to add the url in the description ? [15:10] sinzui, that's correct. [15:11] k [15:11] thanks for you help [15:11] benste, deryck, allenap, sinzui: Ah, but... [15:11] Accoring to the code, we should be able to at least register google code bug watches (we just don't update them). [15:11] right [15:12] so you can register a useless watch against Google code :-) [15:12] deryck: Well, it's not useless to say "This LP bug is actually this Google Code bug" [15:12] right, was being inappropriately sarcastic. [15:12] benste: Ah, sorry, just read the scrollback. That's what you've already discovered. Ignore me then. [15:12] Just meant it's not obvious it won't be a completely working bug watch. [15:13] * gmb in trying-to-answer-question-that-was-already-answered shocker [15:13] deryck: That's true. We should probably actually tell people that when they're registering the bug watch. [15:13] wouldn't it be possible to add a message in upstream LP if google - give following error strin ? [15:13] g [15:14] gmb: guess we're talking about the same idea :-) [15:14] btw. why not asking google for an API and implement Google Code as uptream bug watch ... [15:14] gmb, and in order to do full syncs... we would need some support from Google code for that, i.e. and API or some such? [15:15] benste: Ah, no we're not. [15:15] So, carry on ignoring me. [15:15] :-P [15:16] deryck: Well, we could screen scrape. That worked for Sourceforge for about six months. [15:16] wishing you all the best for your discussion, enjoy your evening - and thanks for your help - see you next time :-) [15:16] deryck: But logically, yes, an API is what we need. Though a CSV or XML export wouldn't be the worst starting place. [15:16] gmb, right. And yeah, I'd like to never do screen scraping again if we can help it :-) [15:17] Indeed. === dendrobates is now known as dendro-afk === dendro-afk is now known as dendrobates === ivoks-afk is now known as ivoks [15:43] in mercurial import, it says that only 'tip' branch will be imported [15:43] what can we do if there's no 'tip' branch? [15:50] abentley: can you help ivoks please? [15:50] bigjools: :) thanks [15:51] ivoks: you could create a new mercurial repository that has a tip branch. [15:51] abentley: that's was my plan [15:51] abentley: thanks [15:51] ivoks: np. === Lcawte|Away is now known as Lcawte [16:36] ivoks: Every mercurial repository has a tip branch by definition, unless it contains zero revisions. [16:38] well, those that i'm interested in, don't [16:38] they have a tip, which is a snapshot of the tree, but default branch is called 'default' [16:38] ivoks: They either contain a tip, or zero revisions. That's an invariant of being a Mercurial repository [16:39] maxb: http://hg.clusterlabs.org/pacemaker/1.1/ <- then i'm missing something [16:39] The 'tip branch' is the branch whose ancestry descends from the tip revision [16:41] anyway, i can't import this repository [16:42] no? [16:43] maxb: http://launchpadlibrarian.net/57675304/ivoks-server-daily-builds-trunk.log [16:46] Indeed. Seems like bzr-hg must have a bug [16:49] or that :) === salgado is now known as salgado-lunch === ivoks is now known as ivoks-afk === dendrobates is now known as dendro-afk === matsubara is now known as matsubara-lunch === dendro-afk is now known as dendrobates [17:30] How can i buy a launchpad voucher to make a project private ? It seems to be absent from the canonical shop where it used to be before. === deryck is now known as deryck[lunch] [17:36] mrevell: can you help? ^ [17:37] bigjools: I can but alopenerp has gone. I'll email her/him. [17:37] ah d'oh === ivoks-afk is now known as ivoks === matsubara-lunch is now known as matsubara === deryck[lunch] is now known as deryck === salgado-lunch is now known as salgado === Lcawte is now known as Lcawte|Away === dendrobates is now known as dendro-afk === dendro-afk is now known as dendrobates [20:05] deryck, ping [20:05] SEJeff_work, pong === ivoks is now known as ivoks-afk [20:22] hi, its been about 4 hours, and im still having download issues with lp, bzr is branching at 1-5 KBps and pull-lp-source downloads at 10 KBps [20:24] everything else is downloading at 70 KBps [20:25] pushing branches seem to be doing fine === dendrobates is now known as dendro-afk === dendro-afk is now known as dendrobates [21:27] hm, how long is it supposed to take before succesfully built packages get published in a PPA ? [21:28] 5 hours still normal? === dendrobates is now known as dendro-afk === yofel_ is now known as yofel [21:35] JanC: before it starts building or how long once completed? [21:35] JanC: Should be <5 minutes. [21:35] Do you have a counterexample? === LinuxJedi is now known as LinuxJedi|away [21:46] Hey LP-ers. I just filed a group project request, and since it's EST almost 5 on a Friday, wondering if I could get some love on it before everyone leaves over the weekend [21:47] https://answers.launchpad.net/launchpad-registry/+question/129666 <-- for those at home keeping score [22:00] wgrant: https://launchpad.net/~janc/+archive/ppa/+packages --> build finished 3 & 5 hours ago [22:00] (those are packages I copied from another PPA, if that matters) [22:01] JanC: Is the Publish flag on https://launchpad.net/~janc/+archive/ppa set? [22:02] JanC: You'll need to hit "Change details" [22:02] you mean in https://launchpad.net/~janc/+archive/ppa/+edit ? no? [22:02] That, yeah. [22:02] I meant to type that originally, but forgot. [22:03] it was never set, that didn't stop things from getting published AFAIR ? [22:03] It should, since the publisher skips archives without that flag set. [22:04] eh, what's the point of archives that can't be used? === Lcawte|Away is now known as Lcawte [22:05] The flag is useful internally, but I'm not sure why it's exposed to normal users. [22:06] I don't remember changing that, but always possible it happened accidentally ☺ [22:06] thanks for pointing at the meaning of that setting ;) [22:07] I would have thought it was related to publishing it on the site instead [22:07] (for other users, I mean) === dendro-afk is now known as dendrobates === dendrobates is now known as dendro-afk === matsubara is now known as matsubara-afk