[00:00] <Bioinforomed> wgrant: I've added the -dev team as the driver and subscribed the -dev team to the branch.  Is that what you meant or is there more?
[00:00] <wgrant> Bioinforomed: You should probably change the ownership of the branch to the team, so the team can upload to it.
[00:00] <wgrant> Morning cprov.
[00:01] <wgrant> bdrung: I might look at that shortly.
[00:01] <cprov> wgrant: morning, how is your Sunday going so far ?
[00:01] <wgrant> bdrung: Why did you add dvipng to Depends when it was already in Recommends, when you gave us the new upstream version during Hardy?
[00:02] <wgrant> cprov: Very young yet, but so far not bad.
[00:02] <wgrant> cprov: Is production's CSS often being missing a sysadmin-calling event?
[00:02] <bdrung> wgrant: good question.
[00:02] <wgrant> bdrung: That brings in huge amounts of TeX :(
[00:03] <wgrant> And Debian appears to have since adopted that change.
[00:03] <wgrant> Even though they dropped it to Recommends in the first place.
[00:03] <cprov> wgrant: uhm, let me check, I'm using edge w/o problems.
[00:03] <wgrant> cprov: Right, edge works fine. But production often returns None for the revision, so no CSS.
[00:04] <cprov> wgrant: right, just happened :(
[00:04] <wgrant> It's not as bad as it used to be without CSS, fortunately.
[00:04] <Bioinforomed> wgrant: I've now associated the -dev team with the project.  Is there a way to do that for the -users?
[00:04] <wgrant> Bioinforomed: I'm not sure that there's an appropriate field for that.
[00:05] <cody-somerville> Bioinforomed, associate -users with the project and add -dev to the -users team
[00:05] <lagenar> how much time takes launchpad to scan a branch for the first time?
[00:05] <wgrant> cprov: bdrung and Bioinforomed have reported it so far, and it seems just a few hours old.
[00:05] <wgrant> cody-somerville: But there's no appropriate field for a user team.
[00:05]  * cprov hates Sundays 
[00:06] <Bioinforomed> cody: I've associated -dev by making it the driver... I'm not sure I want to do that for -users.  Adding -dev to -users makes perfect sense, though.
[00:06] <wgrant> lagenar: Normally just minutes, but there appears to be a bug in bzr which is making things very slow. Expect it to be faster within a couple of days.
[00:06] <Bioinforomed> I was hoping for the -users mailing list to get annoucenments and the like
[00:06] <wgrant> lagenar: Scanning just affects what is displayed in the user interface - all functionality is still available.
[00:06] <lagenar> ok great then
[00:06] <cprov> wgrant: no bugs yet, though.
[00:07] <wgrant> cprov: Surprising.
[00:07] <cprov> I will file one
[00:09] <Bioinforomed> Next beginner question for LP: Is there some sort of Wiki I can use to provide an overview for my project and the resources or must I host that myself elsewhere?
[00:10] <wgrant> Bioinforomed: You can add some content to your project's Launchpad home page, but there is no wiki service at this time.
[00:11] <cprov> wgrant: https://bugs.launchpad.net/launchpad/+bug/250190
[00:12] <wgrant> cprov: Great, hopefully somebody will notice soon enough...
[00:12] <Bioinforomed> wgrant: How do I post files to the project for source and binary releases?  These will be .tar.gz archives and various Python .egg files and Windows installers.
[00:14] <wgrant> Bioinforomed: You can create a release series and a release, and upload files to that release.
[00:14] <bdrung> wgrant: dvipng is needed for building matplotlib, but you can use it without dvipng.
[00:14] <wgrant> bdrung: Right, but you made it depend on it.
[00:14] <bdrung> wgrant: while matplotlib configures: OPTIONAL USETEX DEPENDENCIES: dvipng, ghostscript, latex, pdftops
[00:15] <wgrant> It should be in Build-Depends, but not Depends.
[00:16] <bdrung> wgrant: we should change this back. matplotlib was the first package i worked on. so my knowledge was about zero.
[00:16] <wgrant> bdrung: Thanks for clarifying that. Can you fix that in your merge?
[00:16] <bdrung> yes
[00:17] <bdrung> wgrant: should i change it to Recommends or Suggests?
[00:18] <wgrant> bdrung: I think Recommends, because otherwise nobody will be able to work out why TeX stuff isn't working.
[00:18] <Bioinforomed> wgrant: Thanks again for all of your help.  I have to head off for a bit, but I'm making a lot of progress thanks to you.
[00:18] <wgrant> Recommends are now installed by default.
[00:18] <wgrant> Bioinforomed: np
[00:19] <bdrung> first time i found a bug in gnome-terminal
[00:28] <bdrung> wgrant: there are EXPERIMENTAL CONFIG PACKAGE DEPENDENCIES in the configuration, should i move the listed packages from depends to recommends or suggests?
[00:28] <bdrung> because they are experimental, i would prefer suggests
[00:28] <wgrant> Suggests sounds good.
[00:29] <wgrant> Just make sure it works without them installed if it was configured with them.
[00:29] <bdrung> now i can fix my faults :)
[00:29] <wgrant> Actually, it's probably best to not change them in a merge.
[00:29] <wgrant> dvipng should be fixed, because it was moved in a merge in the first place.
[00:29] <wgrant> But we still want to keep the diff minimal.
[00:30] <bdrung> dvipng was introduced by me and configobj and enthought.traits too
[00:30] <wgrant> Ah.
[00:30] <bdrung> and were adopted by debian without checking it.
[00:31] <wgrant> How strange.
[00:35] <bdrung> may be we should ask Morten Kjeldgaard. he mentored the packaging.
[00:36] <wgrant> He's not around at the moment.
[00:36] <bdrung> i saw it.
[00:36] <wgrant> And hmm, we should be in #ubuntu-motu.
[01:51] <Mecha25> anybody out there know why my code.launchpad.net page isn't reflecting my bzr push but my bazaar.launchpad.net page is?  it's been an hour since the push, I don't want to e-mail a link to the branch until I'm sure the code's been uploaded
[01:52] <wgrant> Mecha25: There is apparently a bug making branch scanning very slow, so the code.launchpad.net page might be out of date. If it's on bazaar.launchpad.net, it's fine.
[01:52] <Mecha25> alright, thanks, any idea when this bug will be solved?
[01:53] <wgrant> I believe they have a fix, and it should be fixed within a couple of days.
[01:53] <Mecha25> cool, thanks a ton, 2 solid weeks of dev work can finally pay off
[01:53] <Mecha25> peace
[02:52] <ScottK> https://bugs.launchpad.net/ubuntu/+source/vte/+bug/89660/comments/33 is spam and needs to be removed.
[03:00] <wgrant> ScottK: But it is  EMERGENCY !
[03:01] <wgrant> And LP speaks invalid RFC2822 at times, it seems. Bad LP.
[03:21] <Hobbsee> file a question.
[03:22] <wgrant> Hobbsee: It'll just get expired.
[03:29] <Hobbsee> wgrant: likely true, but then you can jus tkeep reopening it with more terse comments, and email the mailing list again about how woeful this solution is.
[03:30] <Hobbsee> OTOH, this was discussed reasonably on LP users.
[03:30] <Hobbsee> so whether they actually get any better remains to be seen.
[03:30] <wgrant> Hobbsee: RSN, as usual.
[03:32] <Hobbsee> heh
[03:33] <Hobbsee> ah yes, here we go
[03:33] <Hobbsee> Yes, this is actually on my roadmap to begin when my second triage
[03:33] <Hobbsee> resource arrives and is trained up.
[03:33] <Hobbsee> So, a few weeks.
[03:34] <wgrant> Correct.
[04:37] <ScottK> The Feedback page lists here as one valid way to report spam: https://help.launchpad.net/Feedback
[08:41] <emet> launchpad is exploding
[08:41] <Hobbsee> ...exploding?
[08:44] <wgrant> s/exploding/dropping CSS often/, I would posit.
[08:54] <emet> it still hasn't "scanned" my damn BZR branch
[08:54] <emet> :o
[08:54] <emet> Grrr!
[08:55] <wgrant> emet: The branch scanner is running very slowly at the moment. Note that branch scanning does nothing but update the web UI, so it's not important, but should be fixed within a couple of days.
[08:56] <emet> okay
[08:56] <emet> BZR is quite nice though
[08:58] <wgrant> Indeed, it is very very nice.
[10:05] <thumper> emet: you can blame me for the branch scanner
[10:05] <thumper> emet: sorry
[10:06] <thumper> I find it often helps to have someone to yell at :)
[10:08]  * wgrant wonders who we yell at about one of the appservers forgetting which revision it is running.
[10:16] <wgrant> thumper: We've had an awful lot of people complain about the branch scanner today.
[10:17] <thumper> wgrant: I can only apologise
[10:17] <wgrant> Even more than those complaining about the lack of CSS, oddly enough.
[10:17] <thumper> wgrant: it appears that it wasn't tested fully before the last rollout
[10:17] <thumper> wgrant: and I should have made sure it was
[10:17] <mwhudson> i found the problem about an hour before the rollout :/
[10:17] <mwhudson> the fun of performance issues
[10:18] <wgrant> Is that what delayed it by a couple of hours?
[10:18] <thumper> no, that was something else
[10:18] <wgrant> (somebody might have wanted to amend the topic, but it's probably a bit late now)
[10:18] <mwhudson> well there were two problems
[10:18] <thumper> I didn't realise that it was as bad as it was
[10:18] <thumper> otherwise I would have pushed harder for an earlier update
[10:18] <mwhudson> there was a configuration issue that stopped it working at all for a little while
[10:19] <wgrant> mwhudson: Something was timing it out?
[10:19] <thumper> when our admin guy starts AU am, I'll try to get the update out
[10:19] <mwhudson> but now it's running, but very slowly
[10:19] <mwhudson> wgrant: no, some apache thingummy, really not very interesting
[10:19] <wgrant> Is it really really slow, or is it a bit slower than usual but with an enormous queue?
[10:19] <wgrant> Aha.
[10:19] <mwhudson> it's really slow
[10:19] <thumper> I've noticed a number of bugs and questions about it
[10:19] <mwhudson> really really slow
[10:19] <thumper> on the plus side, people are using LP codehosting :)
[10:20] <mwhudson> the code is in place to make it a bit faster than it was before, we just need a sysadmin :)
[10:20] <mwhudson> thumper: yeah, indeed, if people complain when we break stuff, that's sort of a good sign
[10:22] <wgrant> Particularly as this is normally only noticeable on new branches.
[10:22] <wgrant> Unless you look closely.
[10:26] <Hattory> Hi all... Why the background of favicon is not transparent?
[10:40] <thumper> Hattory: my guess is because the grey doesn't have a good contrast with many browsers default colour
[10:45] <wgrant> The white background looks awful in the Hardy theme, but not too bad with Intrepid's.
[10:45] <wgrant> I preferred the logo as the favicon.
[10:48] <Hattory> wgrant: you're right but in many browsers it looks  so bad... IMHO
[10:48] <wgrant> It does.
[10:49] <wgrant> With a bit of tweaking the logo looks fine.
[10:51] <evilissimo> hmm, I try to use staging.launchpad.net to try it out but it seems like i won't get the registration mail, or does it take remarkably longer than on the mainsite? On the mainsite i'm registered already
[10:53] <evilissimo> ok found the answer
[10:55] <evilissimo> although having to wait so long is a bit disturbing and could lead to ignore staging at first place and go over and just create a project :S
[11:12] <thumper> evilissimo: staging doesn't send email out
[11:12] <evilissimo> yeah I read it
[11:12] <thumper> evilissimo: at least not somewhere where you could see it :)
[16:33] <xFallen> hey guys
[17:13] <dash> hi. is there a way to delete a blueprint?
[17:31] <megabyte405> Has anyone had problems with the PPA not always packaging all the files produced for an arch-independent package/
[17:32] <cprov> megabyte405: do you have an example ?
[17:32] <megabyte405> yes - http://launchpad.net/~abiword-stable/+archive - look at the hardy package before the rebuild finishes
[17:32] <megabyte405> there should be a ton of files in /usr/share/abiword-2.6 in the abiword-common package
[17:33] <megabyte405> but it seems to package them only every other time I build
[17:33] <megabyte405> (I test-built that package on my personal PPA, where it worked on the second try, then I copied the source to the AbiWord Stable ppa, where it built wrong)
[17:33] <megabyte405> now I am rebuilding in AbiWord Stable to see if I can get it to work again
[17:34] <megabyte405> The package is actually the new one from debian, I worked with the maintainer to build i, and he said he's seen that kind of thing happen only a few times when the system was screwed up
[17:34] <cprov> megabyte405: I can't see how the packaging procedure can be different in PPAs
[17:35] <megabyte405> Yeah, I have no idea why it's not working, but it's frustrating because it worked when I tested it, then when I pushed the package to many abiword users, it broke
[17:35] <megabyte405> and it works on my own system
[17:35] <megabyte405> it just fails half the time in the PPA, and it just started doing this
[17:35] <cprov> megabyte405: it needs further investigation, file a bug
[17:37] <megabyte405> cprov: ok, downloading some of those packages to attach and will file a bug
[17:38] <cprov> megabyte405: good, then we can find out why it's happening.
[17:45] <megabyte405> https://bugs.launchpad.net/launchpad/+bug/250293
[18:51] <bbyever> hi
[18:51] <bbyever> usually how long does it take for a branch tu be updated on the website after its been pushed to?
[18:58] <beuno> bbyever, usually, a few minutes
[18:58] <beuno> but the code scanner is a bit delayed
[18:59] <beuno> so it may take a day or two
[18:59] <beuno> what's the URL?
[18:59] <bbyever> beuno: https://code.edge.launchpad.net/~ubuntu-mx-marketing/ubuntu-mx-podcast/dev
[19:00] <beuno> bbyever, http://bazaar.launchpad.net/~ubuntu-mx-marketing/ubuntu-mx-podcast/dev/changes
[19:00] <beuno> branch is fine, just need to give code scanner a while to catch up
[19:00] <beuno> you can use it normally, pull/push/branch
[19:00] <bbyever> beuno: ah ok. thanks!
[19:06]  * beuno wonders if any admin can add to the topic that code scanner is delayed
[19:07] <Peng_> Um, actually, i don't think the channel is +t, so anyone can do it.
[19:07] <beuno> Peng_, you're right, thanks  :)
[19:07] <Peng_> :)
[19:08] <Peng_> The next meeting is 3 days and 8 minutes ago?
[19:08] <beuno> uhm, yeah. Time travel is the latest and greatest in Ubuntu  :p
[19:09] <Peng_> Darn, I really need to upgrade to Hardy.
[19:09] <beuno> it's much easier if you have meetings when you already know what's going to happen
[19:19] <Peng_> Like in the Doctor Who episode "Blink"? :)
[19:20]  * beuno never saw Doctor Who
[22:57] <nycerine> rosetta need better navigation imo
[22:57] <devfil> hi to all
[22:58] <devfil> why piemontese, franco-provencal etc... are languages for translation?
[23:02] <thumper> devfil: no idea
[23:02] <thumper> but then I don't have anything to do with translations :)
[23:02] <devfil> it is really bizzarre
[23:04] <devfil> however, I'm the admin of a project on lp, but I cannot set googlecode as bug tracker, how I can set it?
[23:08] <thumper> I don't think googlecode is a bugtracker option (from what I looked at)
[23:09] <thumper> (in "Change details" of the project)
[23:09] <devfil> thumper: but I should
[23:09] <thumper> I didn't realise that googlecode had a bug tracker
[23:09] <devfil> s/I/it/
[23:10] <devfil> thumper: for example http://code.google.com/p/msn-pecan/issues/list is a bug tracker
[23:10] <mwhudson> pretty sure there is a bug or two on launchpad for this
[23:11] <mwhudson> https://bugs.edge.launchpad.net/malone/+bug/78395
[23:12] <emet> hey
[23:12] <emet> the scanner is still the brokens
[23:13] <mwhudson> emet: in progress
[23:13] <mwhudson> (really!)
[23:13] <emet> :)
[23:17] <devfil> the new lp on edge is finished?
[23:17] <Peng_> mwhudson: Has it changed from "waiting for an admin"?
[23:17] <mwhudson> Peng_: yes
[23:17] <Peng_> Oh, good.
[23:28] <devfil> the new lp is finished?
[23:28] <mwhudson> devfil: when is software ever finished?
[23:29] <devfil> mwhudson: when it works
[23:29] <emet> when is spawns a computer god which takes over the universe
[23:30] <devfil> mwhudson: I don't like the grey bar for edge on header
[23:31] <devfil> I prefer it attacked to the border of the window
[23:31] <mwhudson> devfil: i don't think the current round of ui tweaks is finished yet, no
[23:31] <mwhudson> devfil: i am totally not the right person to talk to about it
[23:31] <mwhudson> however