[00:01] <nhandler> lifeless: I just got an OOPS-1707ED2083 for that link that mlaci posted
[00:02] <nhandler> The issue is still there even on non-edge: OOPS-1707M1769
[00:02] <lifeless> well non-edge is generally worse
[00:02] <lifeless> need to wait a few minutes for the oops to sync
[00:05] <lifeless> ok
[00:05] <lifeless> Page-id: Archive:+packages
[00:06] <lifeless> https://bugs.edge.launchpad.net/soyuz/+bug/607934
[00:07] <lifeless> there is a nuts query there
[00:07] <lifeless> LIKE '%' || '' || '%'
[00:07] <lifeless> thats going to chew cpu and be slow
[00:07] <lifeless> I'm going to file a new bug on it
[00:07] <lifeless> mlaci: did you manually create that url
[00:07] <lifeless> mlaci: or did launchpad generate the link to it ?
[00:20] <lifeless> mlaci: https://bugs.edge.launchpad.net/soyuz/+bug/629921
[00:21] <lifeless> mlaci: fixing that may not be enough to fix your PPA, you have a lot of builds there.
[00:21] <lifeless> mlaci: but I'm sure it will help.
[00:42] <Ddorda> hey guys, any idea why i get this error when doing bzr branch lp:ubuntu-drupal-theme ?
[00:42] <Ddorda> the error: bzr: ERROR: Not a branch: "bzr+ssh://bazaar.launchpad.net/~ubuntu-drupal-devs/ubuntu-drupal-theme/6.x-2010/".
[00:54] <maxb> Ddorda: it seems to work for me
[00:59] <lifeless> Ddorda: have you done 'bzr launchpad-login'?
[00:59] <lifeless> maxb: it may be an explicit stacking rule, incompatible with http if Ddorda doesn't have bzr+ssh setup
[00:59] <lifeless> maxb: just a theory
[01:12] <maxb> oh... I thought lp was supposed to fix those up
[01:15] <wgrant> I don't think it even did it back when it mirrored branches.
[01:17] <lifeless> maxb: no, they need to be relaitve paths always
[08:06] <ricotz> hello, could someone have a look at this build https://launchpad.net/~xorg-edgers/+archive/ppa/+build/1945560 which shows this error "dpkg-deb: failed to create directory: No space left on device"
[08:07] <ricotz> wgrant, hi ^
[08:58] <LinuxJedi> oh, nice.  Launchpad seems to have mixed up my account and one I used to use several years ago :(
[09:02] <freedo> morning
[09:02] <LinuxJedi> ah, ok, it seems launchpad reverted email logins to the state of a month or so ago
[09:02] <freedo> i have a strange error when trying to build a package on launchpad: it complains the i386 builder cannot find a compatible libstdc++
[09:03] <freedo> amd64 builds fine though
[09:03] <freedo> can anyone advise how to fix that?
[09:29] <bilalakhtar> Why does my +karma show that my karma has expired? Shouldn't it have become less than expiring completely?
[09:33] <nigelb> freedo: ppa? #ububntu-packaging might be agood place
[09:33] <bilalakhtar> People, the e-mail interface of lp is down.
[09:33] <nigelb> bilalakhtar: weekend is not the perfect time since most losa's might be away, you can file a question against lp about it
[09:33] <nigelb> err, that was about the +karma query
[09:34] <bilalakhtar> both are problems :(((((
[09:34] <bilalakhtar> Is anyone else over here having the same e-mail interface problem?
[09:36] <lifeless> bilalakhtar: you haven't described your problem
[09:36] <lifeless> so its impossible to say
[09:36] <lifeless> perhaps you should describe it
[09:36] <lifeless> as for karma, it degrades over time and then expires completely.
[09:36] <bilalakhtar> lifeless: One is unable to comment by sending an e-mail to nnnnnn@bugs.launchpad.net or whatever
[09:36] <lifeless> it takes years to do this (I forget the exact time frame)
[09:36] <lifeless> bilalakhtar: more details please
[09:36] <bilalakhtar> Second case
[09:37] <bilalakhtar> requestsync  in the ubuntu-dev-tools package is failing to file sync requests when using the e-mail interface
[09:37] <lifeless> bilalakhtar: what happens, do you get an error, do you get a non delivery report
[09:37] <bilalakhtar> lifeless: nothing at all
[09:37] <lifeless> bilalakhtar: there are many possible causes for that; check your mail logs to make sure that the mail has actually been sent
[09:37] <bilalakhtar> however requestsync works okay using --lp options
[09:37] <nigelb> do you have the bug numbere with happened?
[09:38] <nigelb> s/with/where
[09:38] <lifeless> the most common cause is mail not being sent
[09:38] <bilalakhtar> bug #625239
[09:39]  * nigelb sees a coment from you
[09:39] <bilalakhtar> nigelb: That was a comment using the Web UI
[09:39] <bilalakhtar> and I have 2 comments pending from around 2 hours using the e-mail interface
[09:39] <nigelb> which email ID did you mail from?
[09:40] <nigelb> i.e. are you sure its from one of those you have registered with LP?
[09:40] <bilalakhtar> The mail was sent at Sat, 04 Sep 2010 10:28:09 +0300 from bilalakhtar@ubuntu.com
[09:40] <bilalakhtar> yes I have been sending many e-mails to bugs from that and it never failed
[09:40]  * nigelb wonders if ubuntu.com mail server is working
[09:40] <Laibsch> Is there anything wrong with the targets http://paste.debian.net/87721/ in ~/.dput.cf?  Whenever I upload a particular package to them it is refused with "The source apt-cacher-ng - 0.5.4-1 is already accepted in ubuntu/lucid and you cannot upload the same version within the same distribution."
[09:40] <Laibsch> that's strange for two reasons.  1) I'm uploading to maverick 2) even the lucid source in that ppa has been deleted about 24 hours ago
[09:41] <bilalakhtar> nigelb: ubuntu.com e-mail server doesn't need to work for sending mails
[09:41] <bilalakhtar> nigelb: the mails have a modified From: header but they are actually sent from yahoo or gmail or whatever is your preferred address
[09:42] <nigelb> d'oh, right
[09:42] <bilalakhtar> Laibsch: that's wrong
[09:42] <Laibsch> bilalakhtar: what's wrong?
[09:42] <bilalakhtar> Laibsch: try using the dput ppa:FOO/BAR <source.changes> syntax
[09:43] <Laibsch> OK
[09:43] <Laibsch> doing as you suggest now
[09:43] <Laibsch> let's see what happens
[09:44] <Laibsch> nonetheless, if the .dput.cf is invalid, I'd like to fix that of course
[09:44] <Laibsch> FWIW, this pattern has been working for me for years all the way to lucid
[09:44] <bilalakhtar> Laibsch: incoming = ~r0lf/ubuntu/maverick should be incoming = ~r0lf/ppa/ubuntu
[09:45] <bilalakhtar> Laibsch: no need to specify the distro release here, its specified in changelo
[09:45] <bilalakhtar> *changelog
[09:45] <Laibsch> nope
[09:45] <Laibsch> that's the reason I have it there
[09:45] <Laibsch> to force upload to a particular release
[09:46] <Laibsch> no matter the changelog
[09:46] <bilalakhtar> Laibsch: You cannot force an u
[09:46] <bilalakhtar> sorry
[09:46] <Laibsch> nonsense
[09:46] <Laibsch> sorry ;-)
[09:46] <Laibsch> you can
[09:46] <Laibsch> and it's documented somewhere
[09:46] <bilalakhtar> Laibsch: you might be able to, but you need to use ~r0lf/ppa/ubuntu/maverick then
[09:46] <Laibsch> OK
[09:46] <Laibsch> let me try that
[09:47] <Laibsch> let's wait for the latest upload
[09:47] <Laibsch> to see what happens
[09:48] <bilalakhtar> Laibsch: its documented here https://help.launchpad.net/Packaging/PPA/Uploading#Using%20packages%20from%20other%20distributions
[09:49] <Laibsch> thank you
[09:49] <Laibsch> sed to the rescue
[09:52] <Laibsch> bilalakhtar: uploading to incoming = ~r0lf/ppa/ubuntu/maverick now
[09:52] <Laibsch> same result
[09:53] <bilalakhtar> Laibsch: then I cannot help
[09:54] <lifeless> bilalakhtar: so, again, check your logs that the mails have been sent
[09:54] <bilalakhtar> lifeless: ah, I checked it soo many times, it HAS been sent
[09:55] <bilalakhtar> lifeless: and it was signed by my registered GPG id
[09:55] <bilalakhtar> lifeless: and I have been sending mails this wasy for quite a long time
[09:55] <Laney> lifeless: I have seen it too: my mail was certainly sent
[09:55] <lifeless> Laney: ok
[09:56] <Ddorda> maxb, lifeless: i am logged in and not able to download it
[09:56] <bilalakhtar> lifeless agreed when Laney said but didn't believe me
[09:56] <Laney> Message-ID: <20100903165931.GK17896@ubuntu.lan>
[09:56] <Laibsch> bilalakhtar: thanks.  let's see if another dev has anything to say.
[09:56] <Laney> one incident could be user error, two is probably a problem
[09:56] <bilalakhtar> Now, its 2 hours since my mail was sent
[09:57] <bilalakhtar> pity this had to happen on a weekend
[09:57] <lifeless> bilalakhtar: I would have advised Laney as I advised you, when there are two distinct reports the probability of a single user problem goes down and a system one goes up
[09:58] <Ddorda> lifeless: i'm not sure why, but bzr branch doesn't work to me. i know it works in other computers
[09:58] <Laibsch> @all: why does an upload to "incoming = ~r0lf/ppa/ubuntu/maverick" get rejected based on "the source being already accepted in ubuntu/lucid" (which in fact is not even the case)?
[09:58] <lifeless> Laney: whats the changelog suite set to ?
[09:58] <bilalakhtar> Laibsch: is the same source package with same version already in ubuntu/lucid?
[09:58] <lifeless> blah
[09:58] <lifeless> Laibsch: ^
[09:59] <lifeless> so, I don't see any oopses from mail processing
[09:59] <Laibsch> bilalakhtar: no
[09:59] <Laibsch> and even then it would be strange
[09:59] <lifeless> which means it is likely to be a datacentre incoming mail issue
[09:59] <Laibsch> because I'm uploading to maverick!
[09:59] <lifeless> I'm just going to ping the sysadmins
[09:59] <Laibsch> bilalakhtar: the source used to be there yesterday, but I deleted it about 24 hours ago.  so it should be cleared.
[10:02] <lifeless> ok, I've asked in our sysadmin channel
[10:02] <lifeless> I'll pop back in a wee bit and see if anyone asnwered, and failing that escalate
[10:02] <Laney> thanks
[10:03] <lifeless> what mail provider did you send via
[10:03] <lifeless> bilalakhtar: ^ and you?
[10:04] <bilalakhtar> lifeless: yahoo
[10:04] <lifeless> Laney: ^
[10:04] <Laney> lifeless: I run my own MTA
[10:04] <lifeless> ok
[10:04] <Laney> logs indicate it was sent
[10:05] <lifeless> Laney: do you do direct delivery, or via ISP etc ?
[10:05] <bilalakhtar> lifeless: mail is certainly going; I just sent it to the bugcontrol list (also hosted on launchpad) and it got into the list
[10:05] <Laney> lifeless: direct
[10:05] <bilalakhtar> and since I am subscribed, I got it back
[10:05] <lifeless> Laney: ok, so you have an ack from the canonical server
[10:05] <lifeless> suggests a mail processing issue
[10:05] <lifeless>  / cron job issue
[10:05] <Laney> I never got a bounce or anything, indeed
[10:06] <Laney> they could check their logs for that message ID I gave you
[10:06] <lifeless> Laney: different folk can look at different bits
[10:06] <lifeless> but yes, thanks.
[10:06] <bilalakhtar> lifeless: Message-id: <1283585289.2528.1.camel@bilal-laptop> is my message id
[10:07] <bilalakhtar> I've sent 2 mails to be precise, this is the id of the first one
[10:08] <lifeless> bbiab
[10:28] <lifeless> I've escalated
[10:29] <rajee> hai need help
[10:30] <rajee> im unable to publish my openPGP key keyserver.ubuntu.com
[10:30] <nigelb> rajee: what error do you get?
[10:31] <rajee> im receiving error as gpgkeys: HTTP post error 7: couldn't connect to host
[10:31] <rajee> gpg: keyserver internal error gpg: keyserver send failed: keyserver error
[10:31] <rajee> i trying for past three days
[10:31] <rajee> but im repeated with same errors
[10:34] <nigelb> might want to raise a ticket at rt.ubuntu.com uname=ubuntu,password=ubuntu
[10:36] <rajee> okay
[10:36] <rajee> i logged in
[10:36] <nigelb> just write the problem and the error
[10:37] <rajee> okay
[10:38] <rajee> where i need to write the problem ?
[10:39] <nigelb> click on 'New Ticket'
[10:39] <nigelb> top right bar I think
[10:39] <rajee> yes. done
[10:39] <shadeslayer> hi
[10:39] <shadeslayer> what header does lp send when you click  on https://edge.launchpad.net/ubuntu/+source/kdenetwork/4:4.5.1-0ubuntu2/+build/1945735/+files/buildlog_ubuntu-maverick-amd64.kdenetwork_4%3A4.5.1-0ubuntu2_FULLYBUILT.txt.gz
[10:45] <rajee> nigelb : i explained my issue in the new ticket
[10:46] <nigelb> do you have a number?
[10:46] <nigelb> A ticket number that is
[10:46] <rajee> but in requestors  field, cc field what i need to add ?
[10:47] <nigelb> rajee: in requestors, put your email ID
[10:47] <rajee> okay
[10:47] <nigelb> so you get updates on the issue, leave the cc empty
[10:47] <rajee> okay
[10:50] <lifeless> shadeslayer: why? (You can just look in your browser)
[10:50] <shadeslayer> lifeless: i just found out the right place to look D
[10:50] <nigelb> rajee: just talked to a sysadmin, keyservers do seem to work
[10:50] <shadeslayer> :D
[10:50] <rajee> nigelb : a ticket number is generated
[10:51] <nigelb> rajee: yes, I saw and I asked an admin too
[10:51] <rajee> nigelb : okay
[10:51] <bilalakhtar> lifeless: You filed a new ticket in RT? Do we need to file a bug?
[10:51] <rajee> nigelb : so what i have to proceed for publishing the key ?
[10:52] <lifeless> bilalakhtar: huh?
[10:52] <bilalakhtar> lifeless: about the incoming bug mail issue
[10:53] <lifeless> no
[10:53] <lifeless> neither
[10:53] <thopiekar> how is support for 'nest-part' going foreward?
[10:53] <lifeless> its being looked at
[10:58] <nigelb> rajee: what is the command you're trying again?
[10:59] <rajee> gpg --send-keys --keyserver keyserver.ubuntu.com followed by my key
[10:59] <nigelb> rajee: behind a firewall or something?
[11:00] <thopiekar> james_w`: ping
[11:00] <rajee> nigelb : no
[11:00] <nigelb> rajee: can you try gpg --keyserver keyserver.ubuntu.com --search-keys 'nigelbabu@ubuntu.com'
[11:01] <nigelb> if that works it could still be a problem with push
[11:01] <rajee> yes one sec
[11:02] <rajee> the same error
[11:02] <rajee> gpg: searching for "nigelbabu@ubuntu.com" from hkp server keyserver.ubuntu.com
[11:02] <rajee> gpgkeys: HTTP search error 7: couldn't connect to host
[11:02] <rajee> gpg: key "nigelbabu@ubuntu.com" not found on keyserver
[11:02] <rajee> gpg: keyserver internal error
[11:02] <rajee> gpg: keyserver search failed: keyserver error
[11:02] <nigelb> rajee: ah, something's wrong at your end
[11:02] <nigelb> that command works fine for me
[11:03] <rajee> oh okay
[11:09] <rajee> nigelb : thanks yar
[11:10] <nigelb> np
[11:16] <lifeless> Laney: bilalakhtar: elmo thinks its fixed.
[11:17] <bilalakhtar> lifeless: That was quick!
[11:17] <Laney> lifeless: sweet, thanks! Was there a problem then?
[11:17] <bilalakhtar> Must have been ^^
[11:18] <lifeless> appears to have been an index file that caused a large malloc when parsing/processing it on an internal mail server.
[11:18] <lifeless> we don't know if that was just a pathological internal structure, bug, corruption or any other cause possibility you could come up with.
[11:19] <bilalakhtar> hmm, now 2 new dup bugs are going to be filed for package gkdebconf
[11:19] <bilalakhtar> and 2 more comments on a plymouth bug
[11:38] <lifeless> is it ok?
[11:50] <lucidfox> I've uploaded the Russian ru.po translation file for my project, but it's listed as "Needs Review", and both "Approved" and "Imported" are greyed out
[11:50] <lucidfox> any idea why?
[11:51] <lucidfox> (well, not uploaded, it was auto-imported from bzr)
[12:10] <bilalakhtar> lucidfox: wait for it to get auto-approved (up to a day)
[12:10] <bilalakhtar> I have also faced similar problems
[12:36] <G> wow is it just me or is mail from launchpad delayed a little
[12:37] <G> oh not as bad now
[14:08] <oo> How does a bug become associated with a particular ubuntu version, would I do that by tagging "maverick" for example?
[15:46] <Laibsch> oo: this is a question for #ubuntu-bugs
[15:47] <Laibsch> but to answer your question, any open ticket is always meant to be open against the latest development version, maverick in this case
[15:48] <Laibsch> I tag with maverick or lucid if I've verified it exists in that particular release
[16:10]  * shadeslayer points to bug 630259
[17:53] <JoshBrown> What kind of credit do you give a patch submitter? Do you author the commit in their name, add a comment `patch by Bob` to the commit, or what?
[18:06] <shadeslayer> JoshBrown: patch by Bob
[18:06] <shadeslayer> one sec
[18:07] <shadeslayer> JoshBrown: https://edge.launchpad.net/ubuntu/+source/k3b/2.0.1-1ubuntu2
[18:12] <JoshBrown> shadeslayer: Thanks.
[18:12] <shadeslayer> np