[01:33] <mikl> what am I doing wrong when bazaar.launchpad.net tells me "Permission denied (publickey)."
[01:38] <kiko> mikl, could be pushing to the wrong URL. or the wrong key in launchpad. tell me more.
[01:39] <mikl> kiko: Well, I've not played with this part of launchpad before, and I wanted to use your supermirror to host my development work on a small hobby project
[01:39] <kiko> mikl, sounds definitely like something we should do properly for you
[01:40] <mikl> kiko: so I did bzr push --create-prefix sftp://dev@bazaar.launchpad.net/~mikl/parade/parade.dev after creating a SSH key and adding it to my person in Launchpad
[01:40] <mikl> standing in my own branch, of course
[01:40] <kiko> okay
[01:40] <kiko> and that's all? 
[01:40] <kiko> ah, I think I know why
[01:41] <kiko> why are you using dev@bazaar?
[01:42] <mikl> kiko: your docs states "name is the short name of the branch..."
[01:42] <mikl> kiko: which was why I though dev made sense
[01:42] <LarstiQ> kiko: this will be the last time I bother you with this. Any resolution on the svn/OOo rosetta copyright assigment issue?
[01:43] <kiko> LarstiQ, actually, yes. what did I tell you the last time we chatted about it?
[01:43] <LarstiQ> kiko: that it was pending
[01:43] <kiko> LarstiQ, okay. danilo contacted a number of people with a proposed change in the text and clarifying intentions.
[01:43] <kiko> LarstiQ, were you one of the people contacted?
[01:44] <LarstiQ> I don't recall seeing any mail from danilo.
[01:44] <kiko> okay
[01:45] <LarstiQ> mikl: dev@bazaar should be lp-user@bazaar. In my case that's larstiq
[01:45] <LarstiQ> mikl: yours looks to be `mikl' :)
[01:46] <kiko> LarstiQ, best I can vouch for now is to ask danilo to send the email to you too
[01:46] <kiko> LarstiQ, so that you can comment before we decide to hit the hammer on the nail
[01:46] <kiko> LarstiQ, reasonable?
[01:46] <LarstiQ> kiko: reasonable.
[01:46] <mdke> kiko: i might have it, if it's the one I'm thinking of, I could forward it
[01:47] <kiko> LarstiQ, okay, emailing him now
[01:47] <mdke> guess not :)
[01:47] <kiko> mdke, that'd be cool - I will email danilo anyway so he is aware of this interaction though
[01:47] <mikl> LarstiQ, kiko: ah, yes... name in the explanation on https://launchpad.net/+code/ should definitely be changed to branch...
[01:49] <mdke> is it the one about all translations, or is this an openoffice specific thing?
[01:49] <kiko> mdke, about all translations.
[01:49] <mdke> ok, I have it yeah
[01:50] <mdke> LarstiQ: sent
[01:50] <LarstiQ> mikl: it has 'user' right now?
[01:50] <LarstiQ> mdke: thanks.
[01:51] <LarstiQ> mikl: oh, I see what you mean
[01:51] <kiko> LarstiQ, please reply with concerns or comments to danilo@canonical.com, ok?
[01:51] <mikl> LarstiQ: yeah, but below that, "name" is used in stead of "branch" (sftp://user@bazaar.launchpad.net/~registrant/product/branch) 
[01:51] <LarstiQ> kiko: will do
[01:51] <LarstiQ> mikl: you are right
[01:51] <kiko> thanks LarstiQ 
[01:52] <mikl> LarstiQ: it is a bit confusing - but then, if I'd read it properly...
[01:52] <mikl> in any case thank you both
[01:53] <LarstiQ> kiko: can I nominate the issue mikl raised for FiF? :)
[01:53] <LarstiQ> basically a one word change to the text on https://launchpad.net/+code/
[01:53] <kiko> LarstiQ, sure you could, but I have just emailed matt revell and ddaa about that.
[01:54] <LarstiQ> good, I can retire then.
[01:56] <kiko> not forever
[01:56] <kiko> just for tonight
[01:56] <kiko> we need you for thatforever
[01:56] <kiko> what evil a missing space can cause
[01:56] <mdke> fortunately not in this case
[01:59] <mdke> LarstiQ: your email address seems to be broken
[02:00] <mdke> ah.
[02:00] <mdke> bad paste
[02:01] <LarstiQ> mdke: ok, I saw it trying to deliver
[02:01] <mdke> ??
[02:01] <LarstiQ> mdke: I'll read it tomorrow, thanks :)
[02:01] <mdke> nope, I sent it to larstiq.dyndns.or (missing +g)
[02:01] <mdke> I've sent it now
[02:01] <LarstiQ> I mean just now
[02:01] <mdke> oh
[01:49] <alefteris> how do i know which code branch is used on the current edgy packages, for example for this https://code.launchpad.net/edgy-gdm-themes/+branches?field.lifecycle=Any+Status&field.lifecycle-empty-marker=1
[01:50] <alefteris> i think its the first one, but im not sure
[01:50] <alefteris> by Frank Schoep
[01:51] <alefteris> or is it the one by Ubuntu Core Development Team
[01:54] <kiko> alefteris, hmm, I think that's best asked on #ubuntu-devel
[01:54] <kiko> or #ubuntu-artwork
[01:55] <alefteris> ok thanks
[02:05] <Ubugtu> New bug: #80726 in malone "Dependencies inconsistent" [Undecided,Unconfirmed]  https://launchpad.net/bugs/80726
[03:34] <uriel> really stupid question, how can I create a new project? have been poking around and looking over docs for 10 min and could not figure it out...
[03:36] <uriel> ok, I see now: "Only the Launchpad administrators can register new projects." got it, it used to be different last year IIRC :)
[03:38] <kiko> uriel, no, no
[03:38] <kiko> uriel, /products/+new
[03:39] <uriel> yes, but I want a _project_
[03:39] <kiko> hmmm
[03:39] <uriel> :)
[03:39] <kiko> https://launchpad.net/projects/+new ?
[03:40] <uriel> Not allowed here
[03:40] <uriel> Sorry, you don't have permission to access this page. 
[03:40] <uriel> ^_^
[03:40] <kiko> interesting
[03:40] <kiko> I can create it for you, uriel 
[03:40] <kiko> email details to me
[03:41] <uriel> ok, can you rename an existing project? that would do too, a friend created v9fs-project when I think he was a bit confused about projects vs. products
[03:42] <uriel> but a new project would do too
[03:43] <kiko> I can rename one, sure.
[03:43] <kiko> uriel, I can also hand over ownership if Eric approves of it.
[03:44] <uriel> or maybe the owner can rename it? if so I will check with ericvh first
[03:44] <mdke> kiko: do you know if indirect members of teams can push to bzr branches hosted on launchpad where the team is the Author?
[03:45] <kiko> mdke, it should be possible, yes.
[03:45] <mdke> damn
[03:45] <uriel> well, I don't need ownership, it is just that I was going to add a bunch of new 9P products(libs, clients, etc) and thought it would be nice to put them all under the same 9P project
[03:45] <kiko> uriel, yes, he can rename it.
[03:45] <uriel> ok, thanks, then I will talk with him, that solves all I need :)
[03:45] <kiko> uriel, that's a great idea indeed. if he needs help I can assist.
[03:46] <uriel> don't want to whine about what you offer for free, but any chance mercurial repos will be supported in the future? ;)
[03:47] <kiko> uriel, that's... unlikely :-) you can use bzr free of charge, though :-)
[03:47] <uriel> (er., actually what I don't want is to create a bzr vs. hg flamewar :))
[03:47] <kiko> uriel, smart saturday move :)
[03:47] <uriel> kiko: yea, I know, I will look into seting a gateway in my end or something
[03:47] <kiko> mdke, why is that a bother?
[03:48] <uriel> (can sync hg into cvs and then cvs into bzr I guess)
[03:48] <kiko> uriel, it should be easier to move projects between the tools, really
[03:48] <kiko> but yeah, you could do that
[03:48] <mdke> kiko: well, might require some restructuring of the ubuntu-doc team, to make a ubuntu-doc overteam and a ubuntu-doc-bzr team for pushing rights
[03:49] <kiko> mdke, that shouldn't be too hard to do, though.
[03:49] <mdke> true, just a bit more complicated to have two teams
[03:50] <kiko> mdke, well.. teams are flexible for a reason. I guess the downside is that you sometimes need to adapt :-)
[03:50] <kiko> uriel, consider using Tailor, perhaps, for the hg-bzr thing.
[03:50] <mdke> actually it's probably more logical to have an overview team and a more specific team
[03:50] <kiko> yeah
[03:51] <uriel> kiko: yea, was just looking into it
[03:56] <uriel> not sure if I should file a bug about this, post to the mailing list or Blueprint, or just whine here, but it would be nice if things worked without javascript, so far the only thing that doesn't seem to work is the top-left menus/links
[04:37] <gnomefreak> mdke: you around still?
[04:38] <mdke> gnomefreak: yes
[04:39] <gnomefreak> mdke: i filed a support request on ubuntu should have been on LP. looking to make a add attachment link to suport requests
[04:39] <gnomefreak> is there a way to move it? i didnt see any way to
[04:39] <mdke> If you can't see it, I doubt I will be able to
[04:39] <mdke> what's the link?
[04:40] <gnomefreak> k let me get it
[04:40] <gnomefreak> https://launchpad.net/ubuntu/+ticket/3266
[04:41] <mdke> gnomefreak: that's not an appropriate subject for a support ticket at all, you should file a bug for that
[04:41] <mdke> but anyway, no, I can't see any way to change it to LP
[04:42] <gnomefreak> ok will file a bug. 
[04:48] <gnomefreak> ty mdke it filed 
[04:55] <Ubugtu> New bug: #80741 in launchpad "[request]  can we add a way to attach files to support requests?" [Undecided,Unconfirmed]  https://launchpad.net/bugs/80741
[07:35] <alefteris> how can a project use lanchpad for translations?
[07:35] <alefteris> any doc?
[07:35] <Ubugtu> New bug: #80760 in malone "when i rip a cd sound juicer crash" [Undecided,Unconfirmed]  https://launchpad.net/bugs/80760
[07:35] <mdke> alefteris: https://help.launchpad.net/RosettaFAQ
[07:37] <alefteris> thanks
[09:41] <jenda> Hello
[09:41] <jenda> LarstiQ: you around, by any chance?
[09:42] <somerville32> Try #bzr
[09:42] <somerville32> They are super helpful
[09:43] <jenda> right :)
[09:43] <LarstiQ> jenda: I am, yes
[09:43] <jenda> in #bzr, then :)
[11:01] <LaserJock> act
[11:18] <LaserJock> how long, generally, does it take for a LP bug marked "Fix Committed" to actually land?
[11:19] <mdke> LaserJock: depending on when it is marked, up to a week
[11:19] <mdke> rollout is on tuesday, iirc
[11:19] <LaserJock> ok
[11:19] <mdke> maybe the process has changed, that's what I recollect
[11:23] <LarstiQ> sometimes earlier, sometimes later
[11:27] <LarstiQ> mdke: you admin doc.ubuntu.com?
[11:27] <mdke> LaserJock: yes
[11:28] <LarstiQ> mdke: is upgrading bzr on there an option?
[11:29] <mdke> LarstiQ: yes, I mentioned to jenda already that we can upgrade it if there are no complicated dependency problems
[11:29] <LarstiQ> multipath communications!
[11:30] <LarstiQ> mdke: bzr doesn't have huge changes in dependencies I can think of. Main other thing would be paramiko
[11:31] <mdke> if you have a breezy-backports repository.... ;)
[11:31] <LarstiQ> mdke: we have an apt repository with a package built and tested on dapper, might that work?
[11:32] <mdke> yes
[11:32] <mdke> the one I have already is: 
[11:32] <mdke>  aizaiiy7ic
[11:32] <mdke> whoops, sorry
[11:32] <mdke> deb  http://people.ubuntu.com/~jbailey/snapshot/bzr/ ./
[11:33] <LarstiQ> deb http://bazaar-vcs.org/releases/debs/ ./
[11:34] <LarstiQ> jbailey hasn't done bzr packaging in a while, a protege of his does it for ubuntu now
[11:34] <mdke> I need a key for that repo
[11:34] <LarstiQ> (and Etienne uploads to the repository just mentioned, as well as ubuntu proper)
[11:34] <LarstiQ> Etienne Goyer's?
[11:34] <mdke> that repo
[11:35] <mdke> also, The following packages have unmet dependencies: bzr: Depends: python-paramiko but it is not installable
[11:37] <LarstiQ> feh.
[11:37] <LarstiQ> is paramiko packaged in breezy?
[11:37] <mdke> a python migration, maybe
[11:37] <LarstiQ> no, not yet
[11:37] <mdke> I mean between breezy and dapper
[11:37] <LarstiQ> that is an issue we're running into now, but from the other side
[11:37] <LaserJock> yeah, I think it was there, but deps are probably wrong
[11:38] <mdke> so it will be difficult to upgrade that
[11:38] <LarstiQ> depending on the version, you can take my word and snip the dependency :)
[11:38] <mdke> snip?
[11:39] <LarstiQ> mdke: delete the dependency, if the paramiko version is a known good one
[11:39] <LarstiQ> otherwise we'd need to backport paramiko
[11:40] <mdke> LarstiQ: what does "delete a dependency" mean?
[11:40] <LarstiQ> mdke: me editing debian/control and rebuilding a package would work
[11:40] <mdke> oh
[11:41] <mdke> jenda: how important is this? Aren't you migrating everything to the new site anyway?
[11:41] <LaserJock> mdke: if you give me a little bit to eat lunch I'll backport paramiko for you
[11:42] <mdke> LaserJock: well, see what jenda says. its up to you, obviously
[11:46] <jenda> mdke: I can, if you want.
[11:46] <jenda> mdke: the new site was going to use the bzr mirror as a database, it doesn't matter if it's at doc.ubuntu.com or not.
[11:46] <mdke> oh i see.
[11:46] <jenda> I'll check with our current host, if he'll accomodate it.
[11:46] <mdke> jenda: if you've got a server running something newer than breezy it will be a good idea to migrate it
[11:47] <mdke> also, doc.ubuntu.com wont' be around much longer, I think, so it would make sense to sort out alternative accomodation soonish
[11:50] <jenda> mdke: Why won't it be around?
[11:51] <mdke> jenda: we may be moving it off that server.
[11:51] <jenda> ok
[11:51] <mdke> is there more on there except for the bzr branch?
[11:55] <jenda> mdke: nope
[11:55] <jenda> mdke: we have everything else at diy.devubuntu.com
[11:56] <mdke> ok
[12:04] <mikl> The Bazaar supermirror is great...
[12:04] <LarstiQ> mikl: it is? :)
[12:05] <mikl> yeah, now I have the best of the decentralised SCM-world combined with a central repository - with secure access and all that jazz...
[12:05] <jenda> LarstiQ: btw, individual files in launchpad hosted bzr branches are not linkable yet, right?
[12:06] <LarstiQ> jenda: launchpad only hosts the branches, no working trees, if that is what you mean.
[12:06] <mdke> he means can you view the files in a web interface
[12:06] <LarstiQ> jenda: You can still manipulate them. Ala `bzr cat https://launchpad.net/bzr/0.14/NEWS`
[12:06] <jenda> Yep, that's what I mean :)
[12:07] <jenda> well, almost
[12:07] <LarstiQ> jenda: so, no, not really.
[12:07] <jenda> Being able to link to a file for http download is what I mean.
[12:07] <LarstiQ> Having a source browser is a priority though.
[12:07] <jenda> ok, cool.
[12:08] <jenda> To my unknowledgeable brain, it's hard to understand how it's possible to have the files there, and accessible online, and yet not accessible individually :)
[12:08] <LaserJock> jenda: you should try pushing a bzr repo sometime and then go look at what files are uploaded
[12:09] <jenda> I don't know what you mean, sorry. Go look where?
[12:09] <LarstiQ> it uploads files to .bzr/
[12:09] <jenda> ah ok
[12:10] <jenda> yes, I think I knew that...
[12:10] <LarstiQ> and it stores compressed deltas
[12:10] <jenda> mhm
[12:10] <mikl> yeah, it's not really human readable
[12:10] <jenda> ok
[12:10] <LaserJock> that got me at first
[12:10] <LarstiQ> so to build the version of NEWS in the bzr 0.14 branch, it does a couple of queries to fetch diffs and build up the full text
[12:10] <LaserJock> I pushed to my webserver machine
[12:11] <LaserJock> and I looked in there and all I saw was .bzr, and I thought "Where the heck did all my files go?"
[12:11] <LarstiQ> this is something a lot of people seem to expect, but it's not what bzr aims to do :/
[12:11] <LarstiQ> So we need to handle this better.
[12:11] <jenda> OK, I see.
[12:11] <jenda> :)
[12:11] <jenda> Thanks for the explanaition.
[12:11] <mikl> I suppose a code browser for Launchpad is in the works - the interface at code.launchpad.net certainly suggest that there should be code there ;)
[12:12] <LaserJock> :-)
[12:12] <jenda> I'm not sure what a code browser is... would that mean browsing the content of the branches (assuming it is code?)
[12:12] <jenda> (my branch has no code in it :))
[12:13] <LarstiQ> jenda: the contents yes, code or no code
[12:13] <jenda> ok, cool.
[12:13] <LarstiQ> jenda: but since that is what typically in them, that's how they get called
[12:13] <jenda> OK :)
[12:13] <mikl> jenda: like this: http://trac.turbogears.org/browser
[12:13] <LarstiQ> something like http://www.lag.net/branches/loggerhead/loggerhead_dev/files
[12:15] <jenda> yep, that's pretty much what I'm looking for.
[12:15] <mikl> or loggerhead, yeah...
[12:15] <jenda> Well, all I need is to be able to extract URLs for individual files in the branch, to use on diy.duvubuntu.com
[12:16] <jenda> an ftp dump would serve this purpose, i suppose, but it doesn't have the nice features of bzr.
[12:16] <jenda> Besides, someone insisted on us using launchpad as much as possible :)
[12:17] <mikl> Pythoneers need to eat their own dog food ;)
[12:17] <mikl> or want to, mostly ;)