[10:09] <tumbleweed> SPAM: https://bugs.launchpad.net/hundredpapercuts/+bug/602676/comments/6
[10:09] <ubot5`> Launchpad bug 602676 in abe (Ubuntu) "Description: Abe's Amazing Adventure" [Low,Fix released]
[10:29] <tumbleweed> and another: https://bugs.launchpad.net/ubuntu/+source/oss4/+bug/519577/comments/24
[10:29] <ubot5`> Launchpad bug 519577 in oss4 (Ubuntu) "package oss4-dkms 4.2-build2002-2 failed to install/upgrade: oss4 kernel module failed to build" [Undecided,Fix released]
[11:29] <adeuring> tumbleweed: thanks for leting us know!
[13:20] <rick_h> adeuring: taking over, thanks
[13:20] <adeuring> rick_h: thanks!
[13:51] <scott__> hi all
[13:52] <scott__> i'm having some trouble using launchpad.
[13:52] <rick_h> what's up scott__ ?
[13:52] <scott__> I'm seeing what I believe to be this bug https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/597895 in oneiric
[13:52] <ubot5`> Launchpad bug 597895 in xorg-server (Ubuntu Natty) "X crashes on key press" [Medium,Fix released]
[13:53] <scott__> how can I open the bug on oneiric?
[13:54] <scott__> for example I've tried 'also affects project' and 'also affects distribution' but I can't seem to figure out how to re-open this bug on the oneiric package (I think it's a regression)
[13:54] <rick_h> looking
[13:57] <rick_h> adeuring: do you know how we could do this? I'm not seeing a way to attach to a series
[13:57] <ts2> you need to be a bug contact (right?)
[13:58] <rick_h> ts2: yea not sure, I've never done that and not seeing hte option on my end
[13:58] <rick_h> scott__: I am tempted to say that since this was marked fixed release that the best route might just be to file a new bug and start the process with your debug data
[13:59] <scott__> ah, okay.
[13:59] <rick_h> scott__: and if it does end up being this exact issue, it can be marked a dupe and tied back from the people that handle the bug
[13:59] <ts2> well I don't see the option either, but I do on one of the projects I am the driver/bug supervisor
[13:59] <rick_h> ts2: ok, thanks
[13:59] <rick_h> scott__: yea, I'd go with a new bug because if it ends up being different you want to have the overlap anyway
[13:59] <scott__> that's fine, I just wanted to make sure I wasn't missing something obvious
[13:59] <scott__> thanks for the help! :-D
[13:59] <rick_h> you can reference this bug that it sounds very similar for sure
[14:00] <scott__> rick_h: yup, will do.
[14:00] <adeuring> scott__, rick_h: there should be a way to add another bugtask for the existing bug; let me check
[14:04] <adeuring> scott__:, rick_h: ts2 s right: you must be a bug contact in order to add a bugtask for a distro series
[14:04] <scott__> adeuring: okay, thanks for that
[14:04] <scott__> I'll just create a new bug.
[14:05] <scott__> report.
[15:26] <Forage> It's now the 3rd day in a row that I'm unable to upload a package to launchpad because my e-mail address is considered invalid, which it is not.
[15:27] <Forage> Is someone available to have a look at it?
[15:27] <Forage> I already filed a bug but got no response so far: https://answers.launchpad.net/launchpad/+question/186189
[15:30] <dobey> Forage: what is the entry in debian/changelog? i think the entries have to be as "Name <email@foo.com>"; do you have only "email@foo.com" there?
[15:30] <EvilResistance> debian/changelog needs to be Name <email@foo.com>, yes
[15:30] <EvilResistance> case in point, mine: Thomas Ward <trekcaptainusa-tw@ubuntu.com>
[15:30] <EvilResistance> if its not in that format yo uget a reject
[15:31] <Forage> which change wil are we talking about exactly? the generated xxx_source.changes?
[15:31] <Forage> s/wil/file
[15:31] <dobey> Forage: in debian/changelog in the source package
[15:32] <Forage> ah
[15:32] <dobey> Forage: the line with the email/date on it, attributing the changes.
[15:32] <Forage> for some weird reason it has "Age Bosma <'agebosma@gmail.com'>" instead of "Age Bosma <agebosma@gmail.com>"
[15:32] <EvilResistance> that'd be problematic :P
[15:32] <dobey> yes
[15:33] <dobey> that's the problem then :)
[15:33] <EvilResistance> fwiw, you could use 'dch' to modify the changelogs
[15:33] <EvilResistance> Debian mentors pointed me to that thing :p
[15:33] <Forage> I don't understand how it happend, I used it before
[15:33] <EvilResistance> might be some update or something being more strict.
[15:33] <EvilResistance> but i'd have it just use <email> rahter than <'email'>
[15:34] <Forage> yeah, of course
[15:34] <EvilResistance> that *should* fix the thing, if it doesnt there might be something else going on
[15:34] <EvilResistance> granted, its been a while since i've been packaging, due to a linux implsoion :/
[15:34] <Forage> weird, in previous packages I uploaded the e-mail address is included fine
[15:35] <EvilResistance> <EvilResistance> might be some update or something being more strict.  <--
[15:35] <EvilResistance> i've seen worse :P
[15:36] <Forage> well, that would explain the failed upload, not the changed inclusion :-P
[15:38] <Forage> thanks guys, lets see what it does now
[15:41] <Forage> succes!
[15:41] <Forage> muchas gracias
[15:42] <EvilResistance> yep, but remember, the format of the changelog is in Debian policy: Name <email>
[15:42] <EvilResistance> so the ' chars wont help
[15:42] <Forage> I know, I removed the quotes now
[15:43] <Forage> If I would have seen it I would have considered it incorrect as well
[15:43] <EvilResistance> :)
[15:43] <Forage> consider it a RFE for launchpad to supply more correct/complete error massages ;-)
[15:44] <Forage> it does not have the quotes in the e-mail
[15:58] <dobey> Forage: i don't think the error is from LP. it's from an underlying packaging tool
[16:00] <Forage> ah
[16:00] <Forage> too bad
[16:01] <dobey> Forage: though i'm sure you could file a bug against whatever tool that is, and get the message improved
[16:01] <dobey> (i'm not sure what exactly generates that error message)
[16:02] <Forage> launchpad is a black hole too me, I have no clue what happens in the background by what
[16:03] <Forage> pbuilder did its job fine locally
[16:03] <dobey> there was almost certainly a lintian warning/error listed about the e-mail address though :)
[16:10] <deryck> rick_h, over to me now.
[16:12] <rick_h> deryck: ty
[16:24] <CarlFK> assuming I have a GPG key (which I need for pushing to a PPA, right?),  where would I find it?
[16:26] <EvilResistance> open up the program 'seahorse' in GNOME, it'll be able to access your keyrings, if you have one it'll be listed there
[16:26] <EvilResistance> (in Ubuntu_
[16:29] <deryck> CarlFK, look in .gnupg
[16:29] <CarlFK> I backed up /home, wiped, installed new OS and /home, mounted backup under ~/oldhome... so I have to drill into thtat
[16:29] <CarlFK> thanks
[16:29] <deryck> np
[16:30] <CarlFK> hmm, don't see that
[16:30] <CarlFK> yes I do
[16:31] <CarlFK> this should just work, right?  mv /home/carl/oldhome/carl/.gnupg /home/carl
[16:32] <CarlFK> it isn't dependent on anything system wide in /etc or something?
[16:34] <deryck> CarlFK, right, should "just work."  assuming file permissions are right.
[16:35] <CarlFK> hmm, I have a ~/.gnupg with 4 files: gpg.conf  pubring.gpg  secring.gpg  trustdb.gpg
[16:35] <deryck> yup, sounds right
[16:36] <CarlFK> can I dump those?
[16:37] <deryck> CarlFK, what do you mean by "dump"?
[16:37] <CarlFK> delete
[16:44] <CarlFK> how do I send someone my GPG key?
[16:44] <CarlFK> im not seeing soemthing to send
[17:16] <ndec> hi. my team has an ARM private PPA on LP (tiomap-dev/ti-omap-private), and I can see the following status on the PPA page: A recent upload has resulted in 6 pending builds.
[17:16] <ndec> i am not sure if this is a problem, or actually something expected ...
[17:17] <ndec> i never noticed this msg, but it might be normal
[17:19] <EvilResistance> ndec, if someone uploaded a source package, or a packaging recipe started, and the 6 builds are more-than-one-platform, then that'd be semi-suspected behavior
[17:20] <EvilResistance> at least, from the builders...
[17:22] <ndec> EvilResistance: i just got this comment from infinity on #ubuntu-arm, ndec, ogra_ : buildd-manager was down, hence the queued builds going nowhere.  Got fixed just a while ago.
[17:22] <ndec> is that it?
[17:23] <micahg> ndec: probably, there seem to be some private builds building ATM
[17:47] <kiko> danilos, how can I get somebody to fix a translation sharing setup?
[17:47] <kiko> https://translations.launchpad.net/stoq/master
 "This project series is sharing translations with abootimg in Ubuntu Precise."
[17:47] <kiko> stoq and abootimg have nothing to do with each other :)
[17:47] <danilos> kiko, that's derived from packaging links
[17:47] <danilos> kiko, so, you need to fix those
[17:47] <danilos> kiko, sharing-details page should include details of that
[17:54] <danilos> kiko, should be fixed now
[17:56] <kiko> danilos, thanks
[17:57] <danilos> kiko, do note that packaging links are still "crowd-sourced", so others will still be able to create them, I suppose someone did it by mistake, but you should be able to edit them as the project driver (or so I'd hope)
[17:59] <kiko> doesn't seem like it, it probably only checks permissions from the distro side