[00:03] <gianmt> hi guys, I've updated my local repo with bzr upgrade --dirstate-tags and everything went fine, now while upgrading the remote repo it says bzr: ERROR: The branch format Bazaar-NG meta directory, format 1 is already at the most recent format.
[00:04] <gianmt> but... if I try to push my local version bzr: ERROR: Tags not supported by BzrBranch5................you may be able to use bzr upgrade --dirstate-tags.
[00:18] <ddaa> gianmt: maybe try upgrading through sftp instead of bzr+ssh
[00:19] <ddaa> or, you could also just use a sftp client to remove the remote .bzr and use "bzr push --existing-dir" to upload it again in the new format.
[00:20] <ddaa> (and by "a sftp client", I mean nautilus or lftp, not sftp)
[00:24] <gianmt> ddaa, you are my hero
[00:24] <gianmt> done, thanks 
[00:41] <ubotu> New bug: #176243 in soyuz "dpkg pre-depends binary REJECT check needed for lzma" [Undecided,New] https://launchpad.net/bugs/176243
[01:35] <ubotu> New bug: #176247 in launchpad-bazaar "Branch vocabulary doesn't search owner names or project names" [Medium,In progress] https://launchpad.net/bugs/176247
[07:35] <gspr> cprov: Yeah, I can understand the frustration with all the deletions, but I think the reason Fujitsu gave is the most common.
[07:35] <gspr> cprov: I know I at least did things just for testing before I knew about the lack of a delete feature
[09:50] <soren> jml: I said you succesfully checked out that branch, I mentioned yesterday... Which version of bzr did you use?
[09:51] <soren> jml: I just tried with 1.0, and I seems to not work.
[10:03] <mwhudson> soren: the difference is checking out versus simply branching
[10:03] <soren> Ooohhh..
[10:06] <mwhudson> :(
[10:06] <mwhudson> fortunately there's an easy workaround
[10:06] <mwhudson> branch, then bind
[10:06] <soren> Sure.
[10:07] <soren> Is bzr branch supposed to take a really long time before it actually starts doing anything at all?
[10:07] <Peng> Yeah, there's a "sleep(600)" at the beginning of it. ;P
[10:08] <soren> Well, as long as there's an explanation :)
[10:08] <Peng> It isn't doing anything at all? No CPU, no disk, no network?
[10:09] <soren> "bzr branch bzr+ssh://bazaar.launchpad.net/~ubuntu-core-dev/debian-installer/ubuntu d-i" just sits there.
[10:09] <soren> Nope.
[10:09] <soren>  Neither
[10:09] <Peng> Nice.
[10:09] <Peng> Anything in .bzr.log?
[10:11] <soren> I'm stracing the ssh process, and there's really not much at all going on. I'm using bzr+ssh, so it might just be that the server is doing a lot of the hard work for me, and it's taking its time.
[10:12] <soren> Using fetch logic to copy between RemoteRepository(bzr+ssh://bazaar.launchpad.net/%7Eubuntu-core-dev/debian-installer/ubuntu/.bzr/)(remote) and KnitRepository('file:///home/soren/src/bzr/foobar/.bzr/repository/')(<RepositoryFormatKnit3>)
[10:12] <soren> fetch up to rev {cjwatson@canonical.com-20071211152540-209wf0ovbcy7qa5m}
[10:12] <soren> From .bzr.log.
[10:12] <soren> It'll probably get around to it eventually.
[10:13] <spiv> soren: "bzr -Dhpss ..."
[10:13] <spiv> soren: that will log the smart protocol conversation to the .bzr.log
[10:15] <soren> spiv: Ah.. Yes, that gave me a looooooong list of revisions.
[10:20] <soren> spiv: ....and still not much else.
[10:21] <soren> Oh, there it goes:    result:   398.889s  'ok',
[10:22] <soren> And the data is trickling down the pipes. All good things come to those who wait.
[10:47] <spiv> soren: ah, I know what's going on there.
[10:47] <spiv> soren: I think that'll be better in 1.1
[10:49] <soren> spiv: Ok. It's the server that is taking its time, isn't it?
[10:50] <spiv> Yeah.
[10:50] <spiv> It's buffering the result before sending it.
[10:51] <spiv> In 1.1 it should stream it as it generates it.
[10:51] <soren> spiv: So as soon as LP's bzr smart server thing is updated, all will be good. The clients won't need to do anything?
[10:52] <spiv> soren: it's a protocol change unfortunately, so the clients will need upgrading too.
[10:52] <soren> spiv: Oh, ok.
[10:58] <kiko> morning!
[11:04] <mantiena-baltix> Hi all
[11:05] <mantiena-baltix> who is responsible for bugs management in launchpad ?
[11:05] <mantiena-baltix> I'm talking about bug tracking system interface
[11:10] <gmb> mantiena-baltix: Well, it's a team effort.
[11:10] <gmb> mantiena-baltix: Can I help at all?
[11:10]  * gmb is one of the LP Bugs team
[11:11] <mantiena-baltix> gmb: I understand, but I simply wanna talk with one of this team about one pretty important issue
[11:11] <gmb> mantiena-baltix: Okay, fire away and I'll see if I can help :)
[11:17] <mantiena-baltix> why away ? ;)
[11:17] <gmb> :)
[11:18] <mantiena-baltix> so, problem is, that lots of ubuntu users always reports/assingns bugs against first distribution from distro list.
[11:19] <mantiena-baltix> Look for example at this URL - https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/157642/+distrotask
[11:19] <ubotu> Launchpad bug 157642 in gimp "gimp 2.4 *final*  in gutsy" [High,Confirmed]  - Assigned to Mantas Kriaučiūnas (mantas)
[11:19]  * gmb looks
[11:20] <gmb> mantiena-baltix: Ah, yes. I see the problem. :/
[11:20] <mantiena-baltix> if user simply press button "Continue" then bug is assigned to Baltix
[11:20] <kiko> gmb, mantiena-baltix: that's a known bug and there's an easy fix. why don't we fix it?
[11:20] <kiko> just default to ubuntu
[11:20] <kiko> or have an unselected default, which mpt won't like but which can solve the immediate problem
[11:20] <gmb> kiko: Bug 58040, right?
[11:20] <ubotu> Launchpad bug 58040 in malone "Also affects: distribution should select current distro by default (dup-of: 50018)" [Undecided,New] https://launchpad.net/bugs/58040
[11:21] <ubotu> Launchpad bug 50018 in malone "Linux Distribution field should be a neutral default" [High,Fix released] https://launchpad.net/bugs/50018 - Assigned to Björn Tillenius (bjornt)
[11:21] <gmb> Or that one, in fact :)
[11:21] <kiko> yeah, that one.
[11:22] <gmb> Hmm. It's marked fix released. Which it patently isn't.
[11:22] <mantiena-baltix> Yes, just set default to Ubuntu or set default to nothing - force user to choose some distro manually
[11:22] <mantiena-baltix> I'm main Baltix developer, so I'm too many work now - I must close lots of non-Baltix bugs and reopen bugs, which belogs to Baltix, but are closed by Ubuntu developers
[11:22] <gmb> mantiena-baltix: Ouch.
[11:25] <gmb> mantiena-baltix: It looks like this was previously fixed and has now regressed somehow. I'll look into it for you.
[11:25] <BjornT> gmb: bug 50018 is already fixed! it's about filing new bugs. you're looking for bug 151014
[11:25] <ubotu> Launchpad bug 50018 in malone "Linux Distribution field should be a neutral default" [High,Fix released] https://launchpad.net/bugs/50018 - Assigned to Björn Tillenius (bjornt)
[11:26] <ubotu> Launchpad bug 151014 in malone ""Also affects" distribution defaults to Baltix" [Undecided,Confirmed] https://launchpad.net/bugs/151014
[11:26] <gmb> BjornT: Ah, right. My mistake.
[11:26] <gmb> No wonder I was confused :)
[11:26] <mantiena-baltix> Ubuntu developers prety often closes Baltix bug, because they think, that users assigned these bug to Baltix by accident
[11:29] <mantiena-baltix> It's nice, when they close non-Baltix bugs, but it's not good, when Ubuntu developers close bugs, assigned to Baltix by Baltix developers ...
[11:29] <gmb> mantiena-baltix: Yeah, I can see how that would be a problem.
[11:29] <gmb> mantiena-baltix: Okay. I'll take a look at getting that fix for your post haste.
[11:29] <gmb> *fixed.
[11:34] <mantiena-baltix> gmb: I just wrote comment at bug #151014
[11:34] <ubotu> Launchpad bug 151014 in malone ""Also affects" distribution defaults to Baltix" [Undecided,Confirmed] https://launchpad.net/bugs/151014 - Assigned to Graham Binns (gmb)
[11:35] <gmb> mantiena-baltix: Right, thanks.
[11:36] <mantiena-baltix> gmb: thank you for helping :)
[11:36] <gmb> mantiena-baltix: No problem. It's what we're here for :)
[11:37] <mantiena-baltix> >:-)
[11:37]  * mantiena-baltix is tries to scare launchpad developers
[11:40] <gmb> mantiena-baltix: It says 'fearless' on the job spec ;)
[11:44] <mantiena-baltix> btw, is there a way to remove Baltix from "Affects" column ? Now we simply set status of accidently filled bugs to "Invalid" but it's not so good - it would be better for us if there would be ability to remove such bugs from Baltix-bugs at all
[11:47] <kiko> mantiena-baltix, not right now
[11:47] <mantiena-baltix> kiko: but it's planned ?
[11:48] <kiko> yeah, I'm thinking about this today actually
[11:48] <kiko> to allow deleting invalid bugtasks if there is more than one task open
[12:08] <mantiena-baltix> kiko: how many tasks is needed to allow new milestones/releases registration in https://bugs.edge.launchpad.net/baltix/+milestones or https://bugs.edge.launchpad.net/baltix/+series ?
[12:22] <bigon> is lp currently working? I cannot reach the server form belgium, http://pastebin.be/7480
[12:22] <bigon> maybe an isp issue
[12:25] <kiko> bigon, it's working for me, hmm
[12:25]  * Hobbsee waves
[12:26] <kiko> looks on a loop on your end
[12:27] <LarstiQ> kiko: bazaar-vcs.org was unreachable for a while from .nl, now it works again
[12:27] <bigon> LarstiQ: does'nt work from here either
[12:27]  * bigon contacts his isp
[12:27] <bigon> :o
[12:59] <Kmos> MOTU Q&A session in 6 minutes in #ubuntu-classroom
[15:45] <Hobbsee> kiko: https://bugs.edge.launchpad.net/~sisfire2006 appears to be spamming
[16:11] <ubotu> New bug: #176376 in launchpad "python-lxml should be included into launchpad-dependencies" [Undecided,New] https://launchpad.net/bugs/176376
[16:30] <ubotu> New bug: #176381 in launchpad "Staging provides deb links when listing cdmirrors" [High,New] https://launchpad.net/bugs/176381
[16:35] <ubotu> New bug: #176384 in launchpad "Staging when displaying ftp only mirrors incorrectly provides deb links" [High,New] https://launchpad.net/bugs/176384
[16:45] <ubotu> New bug: #176387 in launchpad "Staging deb links default to Hardy for archive mirrors" [Undecided,New] https://launchpad.net/bugs/176387
[16:46] <soren> Hm... When trying to commit to bzr+ssh://bazaar.launchpad.net/~ubuntu-dev/ubuntu-dev-tools/trunk/, bzr hangs and says 'No handlers could be found for logger "bzr"'.. I can't completely rule out that possibility that I may have had interrupted bzr during a commit about 20 minutes ago. I don't know if that could have caused it.
[16:46] <jelmer> soren: I think this is a known issue, but one of the lp developers can perhaps comment better
[16:50] <ubotu> New bug: #176388 in launchpad "Deleting official mirrors from Launchpad" [Undecided,New] https://launchpad.net/bugs/176388
[16:51] <soren> Hmm... Now it works again.
[16:51] <soren> Oh, well.
[17:00] <ubotu> New bug: #176390 in launchpad "Request enght of time mirrors have been disabled be displayed" [Undecided,New] https://launchpad.net/bugs/176390
[17:10] <ubotu> New bug: #176394 in launchpad "Mirror prober email is in beta." [Undecided,New] https://launchpad.net/bugs/176394
[17:15] <ubotu> New bug: #176396 in launchpad "Deleting mirrors should return to Pending-Review" [Undecided,New] https://launchpad.net/bugs/176396
[17:31] <ubotu> New bug: #176397 in launchpad "Sorting none official mirror lists" [Undecided,New] https://launchpad.net/bugs/176397
[17:36] <ubotu> New bug: #176399 in launchpad "Mirrors displayed as "Unknown status"" [Undecided,New] https://launchpad.net/bugs/176399
[17:41] <ubotu> New bug: #176402 in launchpad "bugs for teams" [Undecided,New] https://launchpad.net/bugs/176402
[17:46] <ubotu> New bug: #176406 in launchpad "Disabled mirrors report last known freshness of mirror incorrectly" [Undecided,New] https://launchpad.net/bugs/176406
[20:45] <ubotu> New bug: #176431 in launchpad "Better organization/segregation of wishlist items" [Undecided,New] https://launchpad.net/bugs/176431
[21:46] <ubotu> New bug: #176437 in launchpad "Conditional searching with tags" [Undecided,New] https://launchpad.net/bugs/176437
[21:51] <ubotu> New bug: #176438 in launchpad "DTDs in Atom feed may break some readers" [Undecided,New] https://launchpad.net/bugs/176438
[22:05] <ubotu> New bug: #176444 in launchpad "Customize search report list" [Undecided,New] https://launchpad.net/bugs/176444
[22:24] <Seq> Hi all. I have a package I have built locally, in a local repository, which works fine. When I upload the source to my ppa, the package also builds fine (though md5 sum is off from my local build), but it always shows up in synaptic as a package to update. Does anybody have any ideas?
[22:25] <Seq> the package installs clean (no errors, etc), but is asked to be "upgraded" to the same version continually.
[22:31] <Hobbsee> it's a launchpad bug.
[22:33] <Seq> Do you have a bug number?
[22:33] <LordRedyen> hi
[22:33] <Fujitsu> There are a couple of bugs.
[22:34] <Fujitsu> Seq: What's your Launchpad username, and which package is it?
[22:34] <LordRedyen> i need to know wich e-mail is of https://launchpad.net/~lordredyen (sorry by my english)
[22:35] <LordRedyen> i think i register that but i dont remember wich e-mail
[22:35] <LordRedyen> so i cant recovery mi pàssword
[22:35] <Fujitsu> You'll need a Launchpad administrator to do that.
[22:36] <Fujitsu> Probably best to ask a question on the Launchpad project (https://answers.launchpad.net/launchpad), as I don't think there are admins around at the moment.
[22:36] <LordRedyen> So is ther  a Launchpad administrator?
[22:36] <Seq> Fujitsu: chrisirwin and the package is linux-image-2.6.22-generic (linux-headers-2.6.22-generic seems to do it too)
[22:38] <Fujitsu> Seq: Looking.
[22:40] <Fujitsu> Seq: It is because the binary package has a Recommends field. Launchpad doesn't put that in the Packages file yet, so apt thinks it is a different version of the package.
[22:40]  * Fujitsu digs up a bug #.
[22:43] <Fujitsu> Bug #165230 is one of them. Bug #172308 is probably more correct, but it's private.
[22:43] <ubotu> Launchpad bug 165230 in soyuz "PPA generates an endlessly upgrading package" [Undecided,In progress] https://launchpad.net/bugs/165230 - Assigned to Celso Providelo (cprov)
[22:43] <ubotu> Bug 172308 on http://launchpad.net/bugs/172308 is private
[22:47] <Seq> Fujitsu: bug #165230 says to "avoid the fields mentioned in bug 172308 if you can". Can you update this bug with those fields for those of us who do not have access to the private bug?
[22:47] <ubotu> Launchpad bug 165230 in soyuz "PPA generates an endlessly upgrading package" [Undecided,In progress] https://launchpad.net/bugs/165230 - Assigned to Celso Providelo (cprov)
[22:47] <ubotu> Bug 172308 on http://launchpad.net/bugs/172308 is private
[22:47] <Fujitsu> Seq: I don't have access to it.
[22:48] <Seq> oh, i thought you did as you said it was more correct.
[22:48] <Fujitsu> I think I sighted a list elsewhere though, or it might have just been that I saw it before the bug was made private.
[22:48] <Fujitsu> Aha, found a list.
[22:49] <Fujitsu> Build-Conflicts(-Indep), Pre-Depends, Recommends, Enhances, Breaks, Essential
[22:49] <Fujitsu> Avoid those, and all will be good. Or hopefully wait for Launchpad 1.1.12.
[22:50] <ubotu> New bug: #176449 in launchpad "More bug management widgets on bug "control panel"" [Undecided,New] https://launchpad.net/bugs/176449
[22:51] <Fujitsu> Partial dupe.
[22:51] <Seq> Fujitsu: Mind if I update that bug, or did you want to do it?
[22:52] <Fujitsu> Seq: I'll do it.
[22:53] <Seq> Fujitsu: Thanks.
[23:10] <Seq> Fujitsu: I removed the affected tags and have re-uploaded. Thanks.
[23:11] <Fujitsu> Seq: No problem. This should be fixed in Launchpad 1.1.12, which is targetted for 2007/12/19.
[23:11] <Seq> Fujitsu: awesome.