/srv/irclogs.ubuntu.com/2009/12/20/#launchpad.txt

micahgshould I file a bug about karma not being updated?00:24
wgrantmicahg: Bug 49334900:25
ubottuLaunchpad bug 493349 in launchpad "Karma not updating" [Undecided,Fix released] https://launchpad.net/bugs/49334900:25
wgrantHm, closed. Odd.00:25
micahgwgrant: yeah, I thought this started after the bug was filed00:26
wgrantI suggest filing a new one.00:26
micahgin LP itself?00:27
wgrantLooks like it broke, worked for a day or two, then broke again.00:27
wgrantlaunchpad-registry00:27
micahgok, will do a little later00:27
micahgthanks00:27
micahgis launchpad now automatically adding itself to upstream bugzilla bugs?00:39
sinzuiwgrant: micahg: Something is not running. Lots of cron scripts have not run in 2+ days00:48
sinzuiNo karma updated until they run00:49
micahgsinzui: I filed bug 49865200:49
ubottuLaunchpad bug 498652 in launchpad-registry "karma is not updating daily" [Undecided,New] https://launchpad.net/bugs/49865200:49
sinzuiWe get daily reports. I am still waiting for a LOSA to investigate00:50
micahgwhich module handles the distro source package search by binary package?00:53
sinzuisomething is soyuz, possibly in lp/soyuz/browser/distribution. The search is for DistrioSeriesPackageCache I think00:55
micahgI was just wondering where to file the bug, sorry :)00:56
wgrantsinzui: But I thought I saw in the production meeting that stuff was no longer failing.01:05
wgrantsinzui: So Registry owns source packages, but not binary packages?01:06
sinzuiwgrant: correct. Soyuz make the binary01:36
sinzuiwgrant: The production script failure was not seen until Firday01:36
sinzuior firday01:36
sinzuiThe message I am getting says nothing is running. There is not failure. So either something is blocking them from starting or are not scheduled to run01:37
wgrantEw.01:42
=== nhandler_ is now known as nhandler
=== nhandler_ is now known as nhandler
lifelesswgrant: around?05:46
lifelesswgrant: nvm05:49
wgrantlifeless: I am.05:52
wgrantFighting with intricacies of Soyuz domination, but around.05:52
lifeless /+mailinglists had gone AWOL. I had forgotten autoapproval.05:53
wgrantAh, right.05:54
lifelessthe dev wiki still mentions it, for confusion win05:56
jmllifeless, have you changed the wiki page?06:08
=== nigel_nb_ is now known as nigel_nb
lifelessjml: no, I don't know what the replacement content should be06:26
lifelessjml: what are you up to this lovely weekend?06:33
nomnexhelp with a GPG command switch. I want to sign the Ubuntu code of conduct. I have 2 KEYS. the command: gpg --clearsign UbuntuCodeofConduct-1.1.txt select my default key, I need the other key. What's the switch?07:20
wgrantnomnex: Try '-u KEYID'07:22
nomnexwgrant: gpg -u keyid --clearsing... like this?07:22
wgrantnomnex: That should work, yes.07:23
nomnexwgrant: try that now, thanks07:23
balauI am debianizing an upstream package (that is not mine) and I want to put it into my PPA. What do I need to put (in debian/control) into Maintainer and XSBC-Original-Maintainer fields? The Ubuntu guide says to put a MOTU address and my address, but I'm not sure because MOTU are not involved and the upstream maintainer is not referenced11:14
wgrantbalau: The original maintainer (you) is the same as the current maintainer.11:16
wgrantSo you should put yourself in the Maintainer field, and not have an Original-Maintainer field at all.11:16
AnAnthello, what's the bzr format supported in LP ?11:16
AnAntis 2a supported ?11:17
wgrantAnAnt: LP supports all stable formats.11:17
wgrant2a is of course supported.11:17
balauwgrant, so the upstream developer isn't a debian maintainer... well it makes sense, I didn't think about it that way. lintian warns that the Maintainer field is not "ubuntu", but I think I can ignore it. Thanks!11:20
AnAntthanks11:20
=== AnMaster_ is now known as AnMaster
=== leoquant is now known as Hans
=== Hans is now known as Guest39290
=== Guest39290 is now known as hansbrinker
=== hansbrinker is now known as leoquant
=== Guest92635 is now known as nhandler
ChrisMorgan*sigh* Firefox crashed again, again just after opening a Launchpad bug...17:21
ChrisMorganI think that there's /something/ Launchpad's doing that sometimes Firefox doesn't like.17:21
ChrisMorganAlso I think the AJAXy stuff has been done a bit patchily in places.  Last time Firefox died (blue screen that time, cause unknown), I lost my bug report that I'd typed in due to the AJAXy stuff not being done with history control.17:23
ChrisMorganWhen Firefox sessions are restored, text in textboxes is saved for systems like Drupal pages: but it can't be restored to a Launchpad thing because the details textarea isn't there at or after page load, instead it's just the few word description thing and you've got to start again :-(17:24
ChrisMorganIt'd be really good if you'd implement AJAX history control, it'd make a number of things work better.17:24
ChrisMorganAlso things like the edit status AJAXy thing just don't work ideally, as you have to edit status and then add a comment, and it goes in two or three or four comment blocks or subscription mail messages - OR, go manually to ./+editstatus and then you can do them all at once... not sure how that'd be best fixed.17:26
ChrisMorganHowever, since Firefox's crashed, I'll take this opportunity to put my computer away rather than finding and reporting the issue in Launchpad... it'd probably crash Firefox again anyway ;-)17:27
=== ChrisMorgan is now known as ChrisMorgan|Away
AnAntsomething is wrong with bugs.launchpad.net17:59
AnAntI keep getting errors when replying bugs via email18:05
akgranerGood morning  :-) all18:09
AnAntHello18:09
akgranerI am working on Ubuntu Weekly News Bug stats18:09
akgranerand I guess there was code push last week that changed the little block where you all report the stats18:10
akgranernow I need to know to find all bugs ever reported now?18:10
akgranerany suggestions18:10
akgraneralso need to know total unassigned bugs18:14
akgranerplease advise  :-) Thank you in advance..18:15
=== nhandler_ is now known as nhandler
=== yofel_ is now known as yofel
crimsuncould someone look at OOPS-1450CEMAIL946, please?20:31
ubottuhttps://lp-oops.canonical.com/oops.py/?oopsid=1450CEMAIL94620:31
james_wcrimsun: "No handler registered for 'launchpad@mail.canonical.com'"21:04
elmohmm21:04
elmothat may be my fault21:04
elmoor not21:12
pmjdebruijnhi21:15
pmjdebruijnI uploaded a rather large set of sources yesterday21:15
pmjdebruijnhowever, I still haven't recieved a mail, the sources were accepted OR rejected21:16
mwhudsonpmjdebruijn: if they weren't signed properly sadly there's no way to know who to tell who to complain to21:17
pmjdebruijnhuh?21:19
pmjdebruijnif they get submitted to my ppa the complaint goes to my ppa, right?21:19
lifelessOOPS-1450CEMAIL115621:23
ubottuhttps://lp-oops.canonical.com/oops.py/?oopsid=1450CEMAIL115621:23
pmjdebruijnmwhudson: how can I verify the signature?21:23
mwhudsonpmjdebruijn: i'm not really sure to be honest21:24
pmjdebruijnI did this once before, but i forgot the command21:24
mwhudsonpmjdebruijn: gpg --verify maybe?21:24
pmjdebruijndoh21:24
pmjdebruijnI was looking for dpkg-... or deb... commands21:25
lifelesselmo: I see that too, for a regular new bug-via-mail.21:25
pmjdebruijnmwhudson: I think the signature should be oka21:25
pmjdebruijnokey21:25
elmolifeless: I'd like to blame myself, but i don't think I can21:26
elmolifeless: as in, my changes seem unrelated21:26
lifelesselmo: I can eyeball them, if that would help.21:26
elmobut if anyone who knows the mail system at all (not me) wants to help me I'd be happy to be proved wrong21:26
lifeless(if you're talking about lp config changes)21:27
elmonah, I'm talking about mail.c.c migrating to new hardware21:27
elmobut mail is coming into the new box, and I can see LP sucking it out just like it did before21:27
lifelessyeah, its reading it21:28
geserpmjdebruijn: does the LP know that the key you signed it with is yours?21:28
james_wwhat does the redirect from nnnn@bugs.launchpad.net to launchpad@mail.canonical.com?21:28
lifelesselmo: but its not understanding it21:29
mwhudsonelmo: in the oops report, the sent mail has X-Original-To: launchpad@mail.canonical.com21:30
elmomwhudson: so?21:30
mwhudsonelmo: could that have changed with the recent changes?21:31
elmonope21:31
mwhudsonelmo: launchpad seems to read that header to work out what to do with the mail21:31
elmoblink21:31
elmoSRSLY?21:31
lifelesselmo: yeah21:31
elmoAAAAAAAA21:31
lifelessipv12 ?21:31
elmoipvfail21:31
elmowait, *seriously*?21:32
elmothat's so freaking broken, it's not even funny21:32
elmoit only ever worked by complete luck21:32
mwhudsonbefore my time by about 45 internet years21:32
lifelesswe could deploy lamson these days :P21:32
* lifeless stops trolling, for a bit.21:32
mwhudsonhttp://bazaar.launchpad.net/~launchpad-pqm/launchpad/devel/annotate/head%3A/lib/canonical/launchpad/mail/incoming.py#L26721:33
elmofine, I'll disable the stupid process mail script till I can figure out what to do with it21:33
lifelesselmo: you might like to file a bug for a better process too21:35
lifelesselmo: if its something simple we could even monkey patch it.21:35
lifelessby we I mean 'mwhudson'.21:35
elmofuck21:36
mwhudsonelmo: i'm happy to make code changes you want, but what i know about email at this level can be written on the back of a postage stamp and shoved up a gnat's arse, as the saying goes21:36
elmowell, I mean, I have to fix this at the MTA level, fundamentally21:38
elmoany code change will be pointing it to a new X- header21:38
elmowhich honestly, I ought to be able to manage21:38
mwhudsonok, i can review and land it then :)21:38
wgrantmwhudson: Could you please approve https://code.edge.launchpad.net/~wgrant/multidistrotools/trunk for me, if you're not busy averting disaster?21:46
mwhudsonwgrant: done21:47
wgrantmwhudson: Thanks.21:47

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!