[00:53] <Rabbid> So, who can I talk to if i want to delete the code branches associated to my project? (I want to start clean, i.e i don't need the vcs-imports anymore)
[00:55] <Rabbid> nobody here?
[00:59] <Ursinha> Rabbid, i guess that if you're the owner you can do that yourself
[01:00] <Rabbid> How?
[01:00] <Ursinha> let me open mine to see
[01:00] <Rabbid> I've tried a lot of things, but never really found anything out.
[01:01] <beuno> Rabbid, you want to delete branches you created
[01:01] <beuno> or is it an import?
[01:01] <wgrant> You'll have to ask a question on answers.launchpad.net to get an admin to delete it.
[01:01] <Rabbid> I have to branches, one i own lp:blogbox and one i dont; the vcs-import.
[01:01] <Rabbid> wgrant: ok
[01:01] <Ursinha> beuno, isn't it possible for him to delete using the UI?
[01:01] <wgrant> Ursinha: He doesn't own the branch.
[01:01] <beuno> Rabbid, if you own them, go the the branch and find a red button to delete them
[01:02] <beuno> for vcs, as wgrant said, you need to file a question
[01:02] <beuno> Ursinha, :)
[01:02] <Ursinha> wgrant, i've placed that "if you're the owner" :)
[01:03] <Rabbid> beuno: yay i found it. i didn't see that button before.
[01:03] <beuno> Rabbid, it's not located as well as it could  :)
[01:03] <Ursinha> beuno, that's exactly where i was trying to lead him :)
[01:04] <beuno> Ursinha, I guess I have more practice!
[01:04] <Ursinha> beuno, surely :)
[01:04] <Rabbid> Should i ask in the VCS imports team of somewhere else?
[01:05] <beuno> Rabbid, file a question to delete it, they'll get to it soon-ish
[01:13] <Rabbid> where should i ask if i wanted to delete an project? if possible?
[01:14] <Ursinha> Rabbid, in answers.launchpad.net
[01:15] <Rabbid> Ursinha: yes but in which "project"?
[01:16] <Ursinha> Rabbid, launchpad
[01:17] <Rabbid> ok, i just found it out right before you said so, sorry for the inconvenience
[01:19] <Ursinha> no problem!
[01:22] <Rabbid> Thanks for all the help, now i can get started rearranging my code, and joining all the little pieces at launchpad.
[01:23] <Ursinha> cool :)
[01:23] <Ursinha> happy to help somehow
[01:46] <bododo> hi folks :)
[05:57] <ScottK-laptop> It would be handy if at least some of the 6 lpia buildd's not currently building packages for PPA could start building stuff....
[05:58] <jml> kiko: I've just filed a couple of project-related requests. I'd be so happy if you could make them happen.
[06:02] <persia> It would also be handy if zirconium could start building stuff for the non-PPAs :)
[06:06] <stdin> wow, how long have there were that many PPA buildd's? last time I looked there were 8 :p
[07:59] <wgrant> Has slave-scanner died?
[07:59] <wgrant> It looks rather dead.
[09:13] <jml> wgrant: looks like it to me (I'm getting emails saying it's not running)
[09:14] <wgrant> jml: Ah, so people actually get told when things die now?
[09:14] <wgrant> So LP won't vanish for a weekend with no way to fix it again?
[09:15] <jml> wgrant: we've had script failure announcements for the last 1.5 years at least.
[09:15] <Hobbsee> wgrant: the problem seem sto be more whether anyone actually *looks* at them.
[09:15] <wgrant> jml: The appservers routinely take a break over the weekend.
[09:15] <jml> wgrant: sadly, I've got the same level of access to the production servers as you have :)
[09:16] <wgrant> jml: Are we likely to see it fixed before Monday?
[09:17] <jml> wgrant: I couldn't say. At the least, I'll try to contact a sysadmin.
[09:17] <jml> although the one in my tz is probably in an aeroplane right now :\
[09:19] <wgrant> Unfortunate.
[09:19] <wgrant> Isn't LOSA+IS coverage fairly good now?
[09:20] <jml> wgrant: there was a LOSA sprint in London this week.
[09:20] <wgrant> ...
[09:21] <wgrant> Convenient.
[09:26]  * Hobbsee notes that people deactivation mails have no X-Launchpad headers on them at all.
[09:26] <Hobbsee> (damn, as they're some of the ones that I most want to ditch)
[09:32]  * jml texts someone.
[09:33] <wgrant> That's not automated?
[09:34] <jml> wgrant: I honestly don't know.
[09:35] <jml> wgrant: but I feel honor-bound to act given it's causing you such grief.
[09:35] <wgrant> Um...
[09:36] <Hobbsee> oh, is launchpad down again?  is this all of it?
[09:36] <wgrant> Hobbsee: Just the buildds.
[09:36] <Hobbsee> ah
[09:37] <wgrant> Well, the slave-scanner, so effectively the buildds.
[09:37] <wgrant> For all we know the buildds could be down.
[09:37] <Hobbsee> oh, tasty.
[09:37] <Hobbsee> 222 i386 builds, including KDE.  Would be nice to see that fixed.
[09:38] <Hobbsee> based on the upcoming alpha 6, and all.
[09:40] <spiv> wgrant: why the "um"?  jml isn't a soyuz developer or clairvoyant, so there's a limit to his knowledge...
[09:41] <wgrant> spiv: Oh, I wasn't complaining about that.
[09:41] <jml> well I was being a little cheeky.
[09:41] <wgrant> Just confused as the level of sarcasm in his statement.
[09:41] <jml> not sarcastic, just cheeky.
[09:41] <spiv> wgrant: ah.  That's where clairvoyance would be handy, of course.
[09:42] <jml> I really do want Launchpad to never ever go down. :)
[09:42] <wgrant> spiv: Of course.
[09:42] <wgrant> I find it a little odd that part of a service which wants to rule the world can go down for hours without people fixing it.
[09:43] <wgrant> of course, SourceForge.net doesn't set a great example, but they generally give some warning.
[09:43] <jml> wgrant: if we were perfect we'd rule the world already :)
[09:43] <persia> jml: If you were perfect, you'd not want to :)
[09:43] <jml> persia: true.
[09:44] <wgrant> jml: I think the two big issues holding you back from world domination are being non-free and only supporting bzr. But most the former.
[09:44] <Hobbsee> wgrant: everyone knows that people only require working stuff during the european and US working day.
[09:44] <wgrant> *mostly
[09:44] <Hobbsee> wgrant: for the rest, launchpad is doing a favour, and is encouraging people to go and have a weekend.
[09:45] <persia> Hobbsee: That's not necessarily a favour.  Some of us work during the week, and only have the weekend for stuff.
[09:45] <Hobbsee> persia: i was being (mostly) sarcastic.
[09:46]  * persia takes off the rose-tinted glasses
[09:46] <wgrant> IRC does need a good sarcasm detector.
[09:46] <jml> Hobbsee: on the flip side, you're likely to get awesome codehosting support ;)
[09:46] <Hobbsee> persia: one of the reasons I pestered repeatedly to get buildd admin access was so that this problem - at least, in terms of locked up buildds and the need to retry these, would be averted.
[09:46] <jml> except on weekends when sometimes I'm not writing papers.
[09:46] <wgrant> Except when vostok decides to be similarly absent.
[09:47] <Hobbsee> jml: cool!  Is there a guide for developers on "this is bzr.  here's what you should do with it, and this is what you need to know", without all the extra bits?
[09:47] <persia> Hobbsee: Makes sense.
[09:47] <jml> Hobbsee: what extra bits?
[09:47] <Hobbsee> jml: i'm not sure.  branching, merging, and variosu other pieces that i don't need to use?
[09:47] <wgrant> bzr init && bzr add && bzr ci
[09:47] <Hobbsee> wgrant: i've got that much down.
[09:47] <wgrant> That's all you need to know for basic usage.
[09:48] <wgrant> It's wonderful.
[09:48] <qense> The launchpad code browser is very clear about reading and pushing branches
[09:48] <qense> You can just copy the commands it gives if you don't know what to do
[09:48] <jml> Hobbsee: for me, branching and merging are bread and butter.
[09:48] <Hobbsee> jml: oh, and how it nicely works for ubuntu source packages - if we should be keeping .orig.tar.gz's in br or not.
[09:48] <wgrant> jml: It really depends on your VCS heritage.
[09:48] <Hobbsee> jml: i guess i'm more asking for the guide for those of us who are *not* doing projects on launchpad, as such.
[09:48] <jml> Hobbsee: for MOTUs, basically?
[09:48] <wgrant> It takes a while to get used to doing things with branches, but once you do you can't live without them.
[09:48] <Hobbsee> jml: something like that.
[09:49] <Hobbsee> jml: core devs too, but yes :)
[09:49] <persia> Generally, a guide for distro developers.
[09:49] <wgrant> Didn't james_w do something like that approximately a day ago?
[09:50] <Hobbsee> i've no idea.  i didn't see it announced on LP users :)
[09:50] <wgrant> It was announced in more Ubuntu fora.
[09:50] <wgrant> Planet, IIRC.
[09:51] <persia> james_w definitely seems like the most knowledgeable about that sort of thing, although I'm still waiting for the promised infrastructure to make it trivial.
[09:52] <spiv> Yeah, I think the key idea is "guide for $audience"
[09:52]  * jml really needs to get his packaging-freak on.
[09:52] <wgrant> Distro branches will be good.
[09:52] <spiv> Because which bits are extra really depends on why you are using it :)
[09:52] <wgrant> Real NMSP will be even better.
[09:52] <wgrant> james_w showcases some Ubuntu-specific bits which make it much nicer.
[09:52] <persia> Yeah.  Distro branches and soyuz integration suddenly make it *heaps* easier to work with.
[09:53] <jml> yeah. I'd start working on them now except that having a real weekend makes me more productive :P
[09:53] <Hobbsee> oh, i've not looked at planet much.
[09:56] <persia> See, this is why people should put *important* things on the fridge.
[09:56] <jml> this reminds me of a similar question
[09:57] <wgrant> Does the Fridge have anything except UWN?
[09:57] <jml> where's a good guide for telling me how to make a package of a Python library
[09:57] <persia> wgrant: Only when someone asks something to go there.  UDS sponsorship went there.
[09:57] <jml> without all of that extra stuff :P
[09:57] <wgrant> I hasn't even got Alpha 4 or 5.
[09:57] <persia> jml: What do you mean "without all that extra stuff".  You want dead-simple?
[09:57] <wgrant> distutils makes it dead-simple.
[09:58] <wgrant> One-line rules is nice.
[09:58] <persia> http://wiki.debian.org/DebianPython/NewPolicy : CDBS + distutils
[09:58] <jml> persia: as little maintenance work as I can get away with.
[09:59] <jml> hmm. I'll need a basic packaging guide to go along with that. Maybe I'll watch that dholbach vid :)
[09:59] <persia> jml: That would be it.  You still have to do copyright, control, and changelog, but the last is nearly automated with dch, control is fairly straightforward, and copyright is only as complicated as your library.
[09:59] <jml> bigjools: hi.
[10:00] <wgrant> This sounds like good news.
[10:12] <persia> \o/  Thank you bigjools
[10:13] <jml> is it back?
[10:13] <persia> It's back.  The builds are flowing.
[10:14] <jml> good.
[10:14] <wgrant> Thanks jml, bigjools.
[10:15] <jml> wgrant: np.
[10:16] <jml> so, if I'm packaging my own software, should I put a debian/ directory in my trunk?
[10:16] <wgrant> No no no.
[10:16] <wgrant> That only causes trouble.
[10:17] <jml> ok. but I'm also physically incapable of working on text files without a vcs. what do I do?
[10:17] <RAOF> jml: Have a 'packaging' thread in a loom?
[10:17] <RAOF> Or a packaging branch.
[10:17] <wgrant> jml: Create a different branch.
[10:18] <wgrant> Merge your upstream branch into that.
[10:18] <wgrant> That basically how we do things.
[10:18] <jml> RAOF, wgrant: ok. that sounds reasonable.
[10:18] <wgrant> I can't type tonight.
[15:20] <Kuhrscher> Hi, do you know if or when KDE's upstream translations will be imported to Launchpad for Intrepid?
[15:34] <persia> On which component should I file a bug about https://launchpad.net/+builds ?  Soyuz?
[19:08] <_steven_> How do I get the revision author on Launchpad to link to my launchpad user page? Right now it just shows my bzr whoami ouput with no link.
[19:08] <_steven_> see https://code.launchpad.net/~linuxdcpp-team/linuxdcpp/trunk
[19:11] <intellectronica> _steven_: i'm not entirely sure, but i think you have to sign the revision with the same key you have in LP
[19:15] <_steven_> they are the same
[19:16] <intellectronica> in that case, i obviously don't know what i'm talking about
[19:28] <emma> anyone here know about canonical rules as far as using the ubuntu font ?
[19:36] <beuno> hi emma
[19:37] <emma> Hi there.
[19:37] <emma> Do you happen to be a Canonical Lawyer? :)
[19:37] <beuno> you should probably contact the trademark department to make sure
[19:37] <beuno> oooh, no, not at all
[19:37] <beuno> let me find you an email you can send that question to
[19:38] <beuno> emma, here's some information and a contact email: http://www.ubuntu.com/aboutus/trademarkpolicy
[19:39] <beuno> I *think* any restrictions just apply to the Ubuntu trademark, but I could be wrong
[19:43] <emma> hey sabdfl
[19:44] <emma> sabdfl - do you know if there is anything wrong with using the ubuntu font on an unofficial ubuntu fan site?
[19:49] <gour> hi, is there any limit on size for bug report?
[19:50] <gour> i'm asking 'cause it looks that bug reported via email with a crash-log didn't go through
[19:51] <intellectronica> emma: see http://www.ubuntu.com/aboutus/trademarkpolicy
[19:51] <intellectronica> emma: if in doubt, ask gerry.carr@canonical.com
[19:53]  * intellectronica should read the entire conversation before answering :-/
[19:54] <intellectronica> gour: yes, iirc there is a limit (though i can't remember exactly what it is off the top of my head)
[19:55] <emma> I didn't see anything pertaining to the font on that page.
[19:55] <intellectronica> gour: in any case, you are encouraged to submit logs as attachments, rather than as the bug description. it makes life a lot easier for the people dealing with the bug later
[19:56] <intellectronica> emma: yeah, i wouldn't know what to tell you. i suggest that you drop a line to gerry carr to be sure
[19:56] <emma> Okay.
[19:57] <emma> I guess I'm sort of curious in general about how much freedom there is for groups of Ubuntu fans to make ubuntu related sites at all.
[19:57] <emma> That trademark policy looks onerous in some ways, concerning to me, and I don't really agree with all of it.
[20:01] <gour> intellectronica: can one submit attachment when reporting new bug as well?
[20:17] <stgraber> gour: yes
[20:20] <gour> stgraber: without (optional) description?
[20:21] <stgraber> gour: https://edge.launchpad.net/ubuntu/+filebug-advanced
[20:23] <gour> stgraber: i'm curious how to do it via email interface?
[20:49] <alex-weej> hello
[20:50] <alex-weej> is there something blocking Launchpad from being able to automatically open upstream issue reports?
[20:51] <beuno> alex-weej, some plugins are being released to do so
[20:51] <beuno> what software are you referring to?  bugzilla?  trac?
[20:52] <beuno> http://news.launchpad.net/releases/launchpad-218-bugzilla-and-trac-plugins-now-available-plus-karma-for-commits
[20:53] <alex-weej> Launchpad and GNOME Bugzilla
[20:54] <beuno> well, the plugin is available, so it's just a matter of gnome installing it
[22:33] <sabdfl> emma: should be no problem
[22:34] <emma> sabdfl: oh that's great. Thanks. We are making a non-commercial community of people who like Ubuntu called club-ubuntu.org and we just made a nice logo for it. :)