=== meetingology` is now known as meetingology
=== Logan_ is now known as Logan|Colbert
=== chu is now known as Guest51762
=== Logan|Colbert is now known as Logan_
=== Guest51762 is now known as chu
=== chu is now known as Guest39107
=== Guest39107 is now known as chu
[14:16] <LordOfTime> anyone on bug control here?
[14:16] <LordOfTime> or rather, can help me confirm whether this bug is invalid?  https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1019280
[14:16] <ubot2> Ubuntu bug 1019280 in metacity "[need-packaging] New Upstream Release" [Undecided,New]
[14:16] <LordOfTime> since its already in Debian (they only give a link to the sid package)
=== zyga is now known as zyga-food
[14:29] <bcurtiswx> LordOfTime, The currently Ubuntu version is lower than the one in sid it appears,
[14:29] <bcurtiswx> s/currently/current
[14:29] <LordOfTime> bcurtiswx: its marked, needs-packaging, what it needs is a sync
[14:29] <LordOfTime> is tagging as 'needs-packaging' valid for when a sync is needed?
[14:30] <hggdh> nope, but we can put this down as lack of knowledge from the OP. Just correct to a sync (or merge) as needed
[14:30] <bcurtiswx> If it were me, i would close the bug and ask the user to use 'requestsync' from the terminal
[14:31] <LordOfTime> ARGH!  Y U NO WORK LAUNCHPAD
[14:32] <LordOfTime> i agree with hggdh on this, but that's because right now my mood is such i dont want to close that bug
[14:32] <LordOfTime> unfortunately, LP crapped out on me right now
[14:32] <LordOfTime> so i cant do anything </annoyed.
[14:33] <bcurtiswx> LordOfTime, its entirely up to you. Your original question was whether it was valid, and it is. What you do from this point is up to you :)
[14:33] <LordOfTime> bcurtiswx: :P
[14:33] <LordOfTime> its also dependent on LP working
[14:33]  * bcurtiswx kicks LP
[14:33] <LordOfTime> but unfortunately for some reason i'm getting LP OOPS things
[14:33] <LordOfTime> (timeouts everywhere from this IP)
[14:34] <LordOfTime> the only thing i can see is my user page without a timeout
[14:34] <bcurtiswx> could be because it's cached
[14:34] <LordOfTime> *notices a few emails sitting in his inbox*
[14:34] <LordOfTime> ... ohh...
[14:34] <LordOfTime> "Network Maintenance"
[14:34] <LordOfTime> </rage>
[14:34] <bcurtiswx> haha, i'd still be raged, just more patient
[14:35] <LordOfTime> bcurtiswx: problem is the maintenance window
[14:35] <LordOfTime> ('tis a BIG WINDOW)
[14:36] <bcurtiswx> works fine 'ere
[14:36] <LordOfTime> yeah, the source is here
[14:36]  * LordOfTime now has standard HTTP timeout errors
[14:36] <bcurtiswx> sorry you're IT doesn't like you
[14:36] <LordOfTime> indeed
[14:46] <hggdh> oh, c'mon, IT does not like users, period
[14:46]  * hggdh knowns, been there
[14:49] <bcurtiswx> it's true, i think they're trained to loathe every user..
[14:53] <LordOfTime> except I work in IT
[14:53] <LordOfTime> :O
[14:53] <LordOfTime> :P *
[15:01] <hggdh> so did I, for quite a long time
[15:09] <LordOfTime> hggdh: i'm on ITSec though
[15:09] <LordOfTime> so...
[15:09] <LordOfTime> :P
[15:10] <hggdh> oh, even worse ;-)
[15:19] <LordOfTime> hggdh: heh
=== yofel_ is now known as yofel
=== zyga-food is now known as zyga
[17:15] <TheLordOfTime> is anyone on Ubuntu 12.04 able to check and confirm this?  https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1019341
[17:15] <ubot2> Ubuntu bug 1019341 in seahorse "Seahorse GUI does not display additional-identity email information on PGP keys " [Undecided,New]
[18:46] <hggdh> TheLordOfTime: I am running Quantal -- it works (but with a slightly different interface, the emails are listed below the GPG keys)
[21:44] <TheLordOfTime> hggdh:  ah, well its a 12.04 regression then, because that existed in 11.10 according to a few people around here
[21:44] <TheLordOfTime> (and it existed in 11.04)
[21:46] <hggdh> TheLordOfTime: it does sound as a regression. But, as Seb pointed out, might not be easy to fix. The best, I guess, would be to ping the seahorse developers at seahorse-list at gnome.org
[21:46] <micahg> if it's a regression, it should be flagged in LP as such
[21:47] <hggdh> TheLordOfTime: also what micahg points out -- add 'regression-release' as a tag to your bug
[21:47] <micahg> also needs targetting :)
[21:47]  * micahg gives a task
[21:48]  * micahg waits for the tag
[21:48]  * TheLordOfTime waits for signal strength to increase slightly
[21:49] <micahg> TheLordOfTime: make sure to include a comment about it being a regression from oneiric as well
[21:50] <TheLordOfTime> micahg:  i havent confirmed *personally* its a regression, as I skipped Oneiric (wouldnt run on this system)
[21:50] <micahg> TheLordOfTime: well, do you have a reliable source? :)
[21:50] <TheLordOfTime> micahg:  hang on, i might have an old oneiric VM lying around i can confirm in
[21:50] <micahg> if it works in oneiric and is broken in precise, it should be easier to fix
[21:51] <TheLordOfTime> *backs up an old multi-name key for testing*
[21:51] <micahg> if it's broke in both, that's more difficult
[21:51]  * micahg used that word easy too easily
[21:51] <TheLordOfTime> lol
[21:51] <micahg> as both precise and oneiric have 3.2.2
[21:52] <micahg> otherwise both releases should be noted as affected
[21:54]  * TheLordOfTime will have to personally test before marking that its a regression
[21:54] <TheLordOfTime> since apparently this VM is exploded