[01:34] <dsas> Why would a source record exist in LP when a packages has never been published in ubuntu
[01:34] <dsas> https://launchpad.net/ubuntu/+source/beryl-core
[01:47] <LaserJock> dsas: I think that's generally when a source package has been uploaded but not yet accepted
[01:49] <dsas> LaserJock: Hmm. People have been filing bugs on it for two months now. Does that mean the upload got rejected?
[01:49] <LaserJock> not necessarily, let me check
[01:51] <LaserJock> yep
[01:51] <LaserJock> beryl-core and beryl-plugins are in the Rejected queue
[01:53] <dsas> LaserJock: Ok, thanks for checking.
[01:54] <dsas> LaserJock: Is the rejected queue in LP somewhere
[01:55] <LaserJock> yeh
[01:55] <LaserJock> I see you rejected like 23 bugs against beryl-core :-)
[01:56] <dsas> LaserJock: Only a couple are mine :p, seb128 probably has loads
[01:56] <LaserJock> https://launchpad.net/ubuntu/feisty/+queue?queue_state=4&queue_text=beryl
[01:57] <LaserJock> that's kinda difficult though
[01:57] <LaserJock> as those bugs probably will affect the package once it finally makes it into Ubuntu
[01:58] <LaserJock> but people shouldn't be filing bugs against an non-existant package :-)
[01:59] <dsas> They're rejected, they'll not show up in bug listing etc in future.
[01:59] <LaserJock> what I'm saying is if they are real bugs that's a shame
[02:01] <dsas> LaserJock: Hmm, perhaps. if people go ahead and report them upstream (or where ever they get their packages from) then they'll hopefully be fixed if we ever get beryl.
[02:03] <LaserJock> ok, well this looks like soyuz bug #52549
[02:03] <Ubugtu> Malone bug 52549 in soyuz "please do not show SP that have never seen light in the system." [Medium,Confirmed]  https://launchpad.net/bugs/52549
[04:01] <rob> hi, if I have a svn repository here locally and not available to the out side world, how can I copy this to the Bazaar trunk for my project in launchpad?
[05:08] <Bhaskar> still problem in launchpad, for downloading po and mo file ???
[05:10] <LaserJock> I believe so
[05:10] <LaserJock> I think it might be Monday when it's fixed
[05:10] <LaserJock> but I'm not sure
[05:11] <Bhaskar> LaserJock: but i have urgent to get po file, i m waiting from friday
[05:12] <LaserJock> I know, but I'm not sure if anything can be done right now
[05:13] <Bhaskar> LaserJock: i hope people are working for fixing bug,right?
[05:13] <LaserJock> it's fixed I believe
[05:14] <LaserJock> it just takes a while to get it tested and rolled out
[05:14] <LaserJock> I think
[05:14] <LaserJock> I'm not a Launchpad developer
[05:14] <LaserJock> just a user
[05:15] <Bhaskar> LaserJock: me also same
[05:32] <Hobbsee> Bhaskar: those devs are employed by canonical - tend not to work weekends
[05:33] <Bhaskar> Hobbsee: so upto to when this bug will fixed?
[05:34] <Hobbsee> [15:10]  <LaserJock> I think it might be Monday when it's fixed
[05:37] <LaserJock> Bhaskar: I think the issue is that they can't just drop in a fix just one the spot
[05:37] <LaserJock> they have to roll out a new release which requires LP downtime and organization
[05:38] <Bhaskar> LaserJock:ok
[10:25] <Q-FUNK> guys, was there a recent change in functionality that makes a change on a bug's Affect link create a dupe instead of reassign to a package if the package name was changed?
[10:25] <Q-FUNK> until recently, going to Affects and changing the binary package's name resulted in the bug being reassigned.
[10:26] <Q-FUNK> now, this time, it created a dupe e.g. the same way we would if clicking on Also Affects.
[10:26] <Q-FUNK> as a result, I still receive notifications about a bug that doesn't concern my package.
[10:27] <Bhaskar> Q_Funk: when the bug will fixed? i mean how long time 
[10:27] <Q-FUNK> and there doesn't seem to be a way to kill my subscribtion/notification to the bug either.
[10:27] <Q-FUNK> Bhaskar: it was rejected both by myself and the maintainer of the correct package.
[10:29] <Bhaskar> Q-Funk: o we can not download po and mo 
[10:29] <Q-FUNK> hm?
[10:32] <Bhaskar> i mean problem on downloading po , mo from launchpad, this is the problem from friday
[01:15] <Fujitsu> Good evening, Launchpadders.
[01:16] <Fujitsu> I am wondering if the elimination of distros/, products/, etc. also works for Malone email access.
[01:16] <Fujitsu> (ie., will `affects /ubuntu/somepackage' work?)
[01:22] <Hobbsee> hey Fujitsu 
[01:22] <Fujitsu> Hi Hobbsee.
[02:07] <pochu> hi guys!
[02:07] <pochu> there seems to be a problem with the karma, don't know If you've noticed it
[02:08] <pochu> my specification karma has increased, though I haven't touched specs
[02:08] <pochu> however, my bug management karma increased very slow, though I've done a lot of bug management
[02:09] <Hobbsee> pochu: look at the calender, particularly the day of the week.  also, https://bugs.launchpad.net/launchpad/+bugs
[02:16] <pochu> Hobbsee: is there a page who explain the karma you win for each thing you can done?
[02:16] <Hobbsee> some of it.  search for karma in that list, and then look at some of the bugs
[02:16] <pochu> maybe I'm doing something that gives me specs points, and I don't know it
[02:29] <pochu> danilos: ping?
[02:31] <Hobbsee> [00:31]  [Whois]  danilos has been idle for 17 hours, 58 minutes, and 33 seconds.
[02:34] <pochu> Hobbsee: do you know if there is any rosetta admin connected?
[02:37] <Hobbsee> pochu: very unlikely.  it's a sunday in most countries.
[02:39] <pochu> :)
[02:39] <pochu> then I'll try it tomorrow
[06:00] <Ubugtu> New bug: #82002 in launchpad "Jabber ids look like email addresses, causing confusion" [Undecided,Unconfirmed]  https://launchpad.net/bugs/82002
[08:19] <Zic_> hello
[08:19] <Zic_> I have a problem : I lost my GPG key and I create a new
[08:19] <Zic_> But, since, My email is .. gone
[08:19] <Zic_> and if I'm loging
[08:20] <Zic_> I can see a padlock
[08:20] <Zic_> (on the left-hand of my email)
[08:24] <Zic_> oh, I'm an idiot :/ It's a problem in my main profile
[08:24] <Zic_> sory :)
[08:24] <ddaa> you're welcome :{
[08:24] <ddaa> duh!
[09:32] <thumper> morning all
[09:50] <ddaa> hello thumper
[09:51] <thumper> ddaa: howdy
[09:51] <ddaa> trying to make up for time I did not work on friday
[09:51] <ddaa> because I was busy saying goodbye to Eva
[09:51] <ddaa> s/Eva/Ewa/ duh!
[09:51] <thumper> :)
[09:53] <ddaa> I guess -> #launchpad-code for the specifics
[10:02] <ddaa> thumper: and wassup on your side?
[10:02] <thumper> finishing off branches made last week
[10:02] <thumper> ~foo/+branch/product/branch is being shortened
[10:03] <thumper> to remove +branch
[10:03] <thumper> (only on code.launchpad.net)
[10:03] <thumper> also working on other features
[10:03] <thumper> and products with branches page
[10:03] <thumper> that and continuing with the email stuff
[10:03] <thumper> and making sure jml has stuff to do :)
[10:03] <ddaa> thumper: shouldn't those pages be just _not_ accessible outside of c.l.n?
[10:04] <ddaa> or be permanent redirects?
[10:04] <thumper> +branch will still work with redirects
[10:04] <thumper> on any layer
[10:04] <thumper> but the traversal to branches is only for code layer
[10:04] <thumper> worked on this with jamesh
[10:05] <thumper> less pain that I thought
[10:05] <thumper> except for all the page tests which are now broken
[10:05] <ddaa> cool, I'm sure jamesh has very clear ideas on this.
[10:05] <thumper> but that is just drudge work fixing stuff
[10:05] <ddaa> thumper: btw, you noticed we'll have the mailman guy in the team soon
[10:06] <thumper> today isn't it?
[10:06] <thumper> tomorrow for you
[10:07] <ddaa> so I guess you'll end up working with him to make the branch email stuff a good citizen of the bigger launchpad mail thing
[10:07] <thumper> yeah, as it all gets integrated
[10:39] <manchicken> Here's a question... can launchpad spring bzr branches?
[10:40] <LarstiQ> sprintg?
[10:40] <ajmitch> morning thumper 
[10:40] <ddaa> manchicken: do you mean "creating new branches without having to upload all the data"?
[10:41] <manchicken> ddaa: Well, like I have a branch on launchpad, and I want to spring a branch from a branch already on launchpad.
[10:41] <LarstiQ> what is 'spring'?
[10:41] <ddaa> manchicken: right, at the moment you have to upload all the data again
[10:42] <ddaa> manchicken: the same way as how you created the first branch
[10:42] <manchicken> That's cool.
[10:42] <manchicken> It seems to have trouble with branches named "trunk"
[10:43] <ddaa> manchicken: I think that's suck, but if you think it's cool, that's great :)
[10:43] <ddaa> manchicken: no reason that the branch name should matter in any way. What is your specific problem?
[10:43] <manchicken> heh
[10:43] <thumper> ajmitch: morning
[10:43] <manchicken> bzr: ERROR: Transport operation not possible: This is not a LocalTransport, so there is no local representation for a path %
[10:44] <manchicken> That's the error I get when I try to create that branch named "trunk"?
[10:44] <ddaa> manchicken: I need the full command you typed, and the full output to make sense
[10:44] <ddaa> manchicken: the problem is likely something else... but it's almost certainly a bug in bzr.
[10:44] <manchicken> bzr branch sftp://manchicken@bazaar.launchpad.net/~manchicken/adept/support-indicator-tooltip sftp://manchicken@bazaar.launchpad.net/~manchicken/adept/trunk
[10:45] <manchicken> I've been branching each individual feature, and I wanted to have a branch that is just everything, that I can merge others' changes into as well.
[10:45] <ddaa> manchicken: please paste the full command and its full output in a pastebin
[10:45] <ddaa> it's little details that help us guess the problem in such cases
[10:46] <manchicken> That was the full command.
[10:46] <manchicken> Oh, in pastebin
[10:46] <manchicken> !paste
[10:47] <LarstiQ> wow, that was introduced in 0.9. Shows how often I do that sort of thing.
[10:47] <LarstiQ> manchicken: http://rafb.net/paste/
[10:48] <ddaa> LarstiQ: it's an unusual thing to do, but so far it looks like it should work.
[10:48] <ddaa> manchicken: btw, please paste the output of "bzr version" as well.
[10:49] <LarstiQ> ddaa: yeah, I bet bzr-svn shows up in the traceback
[10:49] <LarstiQ> ddaa: fyi, `bzr version` has a chance of being deprecated, in favor of only having `bzr --version`
[10:50] <ddaa> LarstiQ: I thought bzr eschewed dashdash ;)
[10:50] <manchicken> http://rafb.net/p/p3P0Bz63.html
[10:50] <LarstiQ> ddaa: what gave you that idea?
[10:50] <ddaa> LarstiQ: gnu arch joke, nevermind
[10:50] <LarstiQ> ohw :(
[10:51] <LarstiQ> manchicken: and the last traceback from ~/.bzr.log please?
[10:51] <ddaa> manchicken: okay, so that looks like a bzr bug (the traceback from .bzr.log will tell us for sure)
[10:51] <ddaa> manchicken: here's how you can try working around it
[10:52] <ddaa> just use push to create the new branch, then do a checkout of it
[10:53] <ddaa> "bzr branch something remote-path" is similar to "cd something ; bzr push remote-path"
[10:53] <manchicken> Where's the .bzr.log?
[10:54] <ddaa> ~/.bzr.log
[10:54] <ddaa> it's in your home directory
[10:54] <manchicken> It's pretty big.
[10:54] <manchicken> 18K lines
[10:54] <ddaa> that's what pastebins are for
[10:54] <ddaa> we'll sort it out ourselves
[10:55] <LarstiQ> 18K lines is more than one traceback :)
[10:57] <manchicken> So how do I extract the few lines you want?  I don't know which parts are pertinent.
[10:57] <ddaa> manchicken: just paste a large chunk at the end
[10:57] <ddaa> or the whole thing if you can
[11:02] <manchicken> Okay, I'm going to try creating a new branch again.
[11:02] <ddaa> manchicken: just do it with push
[11:02] <manchicken> the trace said something about bzr-svn and bzr-gtk.  I've removed those to see if it might be those.
[11:02] <manchicken> I did install those since last time I've made a successful branch.
[11:09] <manchicken> Looks like it's working.
[11:14] <LarstiQ> manchicken: I'd still like to see your .bzr.log if possible
[11:15] <manchicken> LarstiQ: I can DCC it to you if you want.  I don't know where one action stops and the next begins.
[11:15] <LarstiQ> manchicken: sure
[11:17] <manchicken> Offering.
[11:18] <LarstiQ> it's stalled
[11:19] <manchicken> Sucks.
[11:19] <manchicken> I'll pastebin it.
[11:22] <manchicken> LarstiQ: http://paste.ubuntu-nl.org/3240/
[11:26] <LarstiQ> manchicken: 17989 till 18014 is the relevant traceback
[11:27] <LarstiQ> and it's indeed bzr-svn where things go awry
[11:31] <manchicken> That's what I'm thinking.
[11:32] <manchicken> Things look like they're going fine now.
[11:32] <manchicken> DAMNIT!
[11:32] <LarstiQ> manchicken: bug 67281
[11:32] <Ubugtu> Malone bug 67281 in bzr-svn "Subversion plugin interferes with push to sftp locations" [Undecided,Fix released]  https://launchpad.net/bugs/67281 - Assigned to Jelmer Vernooij (jelmer)
[11:32] <manchicken> Or not.
[11:32] <manchicken> bzr: ERROR: sftp://manchicken@bazaar.launchpad.net/%7Emanchicken/adept/updater-changelog-viewer/.bzr/ is not a local path.
[11:33] <manchicken> wtf.
[11:40] <ddaa> manchicken: disable bzr-svn
[11:40] <manchicken> I apt-get removed it.
[11:42] <LarstiQ> ddaa: the first bug manchicken ran into has been fixed in newer bzr-svn, the second I can reproduce with bzr.dev without bzr-svn even
[11:43] <ddaa> manchicken: I leave you in LarstiQ's trustworthy hands
[11:43] <manchicken> heh