[00:49] <rCX> Bug #411322 has been fixed at bugzilla but the remote watch still says "New". Is there a way to update this manually?
[01:12] <thumper> rCX: I don't think so
[01:12] <thumper> rCX: whould catch up when the bugwatch notices
[01:12] <rCX> thumper: thanks
[01:14] <spm> rCX: fwiw, the checkwatches script was in gaga land; I've killed that and left it to run again. so hopefully... "soon"
[01:16] <rCX> spm: thanks
[01:54] <jjardon> Hello, I get lot of tarball in the glib page: https://launchpad.net/glib/
[01:54] <jjardon> How can I fix that?
[01:55] <jjardon> Also, tarballs are not shown in the history view
[02:05] <thumper> jjardon: what history view?
[02:07] <jjardon> thumper, in the "Series and milestones" graph
[02:08] <thumper> jjardon: I'm afraid I don't understand your problem
[02:09] <jjardon> thumper, https://launchpad.net/glib/ -> "Series and milestones" graph. Compare it with the graph of https://launchpad.net/gtk: you can see 2.21.1, 2.21.2, 2.21.3 ... there
[02:11] <thumper> jjardon: the extra bits you see on the gtk graph are the releases and milestones attached to the series
[02:11] <thumper> jjardon: glib doesn't have any milestones or releases on the series
[02:12] <jjardon> thumper, that is my problem: there are some glib releases but they doesnt appear in the graph
[02:13] <thumper> jjardon: I think that someone has to add the releases to the project on Launchpad, as it doesn't automagically add them
[02:15] <jjardon> thumper, I've already fill the Release URL pattern: https://launchpad.net/glib/2.24
[02:15] <thumper> jjardon: ok, this is out of my current understanding
[02:16] <thumper> jjardon: I've not worked on this bit
[02:16] <jjardon> ok, thanks anyway
[02:16] <thumper> jjardon: best way to chase it up would to be to ask a question on launchpad
[02:17] <thumper> https://answers.edge.launchpad.net/launchpad/+addquestion
[02:17] <wgrant> jjardon: It should automatically pull those releases in. When did you add the pattern?
[02:17] <jjardon> wgrant, several day ago
[02:18] <wgrant> Hm. It's meant to run daily.
[02:18] <jjardon> how anoyning me is that the gtk ones works well
[02:18] <lifeless> thumper: is build from build usable by randoms now ?
[02:19] <wgrant> Oh.
[02:19] <wgrant> jjardon: The releases are all on the 'head' series.
[02:19] <wgrant> It has a pattern of http://ftp.gnome.org/pub/GNOME/sources/glib/*/glib-*.tar.bz2
[02:20] <jjardon> wgrant, yeah, I tried to delete that branch but I can't
[02:20] <jjardon> (timeout error)
[02:20] <jjardon> anyway, that branch is disabled
[02:20] <wgrant> jjardon: You should probably move the existing releases.
[02:20] <wgrant> To the relevant series.
[02:20] <wgrant> And remove the release URL.
[02:20] <jjardon> (the same works without problems in the gtk case)
[02:20] <wgrant> Then you can delete the series.
[02:23] <jjardon> wgrant, https://launchpad.net/gtk/+series
[02:24] <jjardon> I get a timout error when trying to remove https://launchpad.net/gtk/all
[02:24] <wgrant> Probably due to the huge number of releases on it.
[02:24] <wgrant> if you don't want them, perhaps delete them first.
[02:25] <thumper> lifeless: you mean build branch to archive?
[02:25] <thumper> lifeless: should be
[02:25] <lifeless> great
[02:25] <thumper> lifeless: it has some issues, as you would expect from beta bits
[02:25]  * lifeless makes a note to make bzr nightlies use it.
[02:25] <wgrant> lifeless: Apart from the massive build queues, but they're resolving now.
[02:25] <wgrant> And some distroseries don't work.
[02:29] <jjardon> wgrant, ok, I'll try that
[02:29] <doctormo> hello jjardon
[02:30] <jjardon> doctormo, hello
[02:34] <doctormo> jjardon: Busy evening? 4th of july etc? http://pahul.deviantart.com/art/Tigon-170079418
[02:37] <jjardon> doctormo, no US citizen here
[02:37] <doctormo> jjardon: Where are you from?
[02:37] <jjardon> Spain
[02:43] <doctormo> jjardon: I'm from England, where you at UDS Barcelona?
[02:44] <jjardon> doctormo, no
[02:44] <doctormo> shame, we could have met.
[02:45] <jjardon> unfotunately I've never been on any UDS
[10:07] <copernic> can launchpad be used for project management aswell, I diden't see a personal todo/milestone/project overview?
[10:08] <copernic> personal overview
[10:08] <lifeless> sure
[10:09] <copernic> yeah maybe that's only for registered developers?
[10:10] <lifeless> well you need an account on LP
[10:10] <lifeless> or how can it generate a list for you ? :)
[10:10] <copernic> I'm a member of the ubuntu launchpad
[10:12] <copernic> never you mind :)
[10:14] <copernic> I should RTFM
[10:14] <copernic> sorry, thx anyways lifeless
[10:14] <lifeless> de nada
[11:21] <d3xter> hi, i've deleted my PPA but it is still listed as "deleted". I would like to undelete it. Is it possible?
[11:21] <bigjools> d3xter: as it said in the warning that was on that depage
[11:21] <bigjools> oops
[11:21] <bigjools> d3xter: as it said in the warning that was on that deletion page, the deletion is permanent
[11:23] <d3xter> but it was a lie, because it is not really deleted
[11:23] <d3xter> it is still there but marked as "not active"
[11:25] <d3xter> bigjools: i don't want to recover the files from PPA. I just want to use the same PPA name
[11:31] <bigjools> d3xter: yes, it's deleted.  None of the files are available any more, just the history is kept.  No, you can't re-use the name, there's a bug that prevents that.
[13:27] <dholbach> hiya
[13:27] <dholbach> is http://launchpadlibrarian.net/51409763/dholbach-xwax-trunk.log a known problem?
[13:30] <maxb> dholbach: In the absence of jelmer, I think your best option is to check bzr-git and dulwich bugs, and file if you don't find one
[13:31] <dholbach> thanks maxb
[13:34] <dholbach> it might be bug 580188
[13:34]  * dholbach shrugs
[16:14] <aboudreault> Hi. I wonder if it's "normal" than my package uploaded the 1st of july, has not been build yet ? Is it because servers are loaded ?
[16:16] <aboudreault> I've seen "Start in 4 seconds"...... but then "Start in 1 minute" ...etc..
[16:16] <aboudreault> now it goes back to 10 minutes.
[16:24] <bigjools> aboudreault: it will start soon
[16:24] <bigjools> the estimates for starting are very hand-wavy
[16:25] <aboudreault> ok, good. I see i386 is started now. thanks.
[17:02] <rioch> I have a bzr branch on my machine. On launchpad, I've not created anything. Do I create the branch on launchpad first, then push, or will it create it for me?
[17:03] <mwhudson> rioch: you need to create the project on launchpad, but not the branch
[17:04] <rioch> mwhudson: ok. so if I just push to it, it will create the correct branch for me, so that in future I can do bzr push lp:project-name?
[17:05] <mwhudson> rioch: it will create the branch, you need to hook the branch up as the 'development focus' in the web site for it to be lp:project-name though
[17:06] <rioch> ahhh ok. thanks.
[17:11] <rioch> this may be a stupid question, but what name should I give the branch?
[17:12] <maxb> 'trunk' is common for the main branch of a project
[17:13] <rioch> thanks
[17:13] <rioch> I was looking at examples, but I wasn't sure if that was a launchpad thing or not.
[17:15] <rioch> so what's the difference between the main branch and a release branch?
[17:16] <rioch> I see some projects have development focus on a series
[17:19] <RuediiX> The main branch is current development, the release branch is either the current significant release, or the branch that is working towards that release
[17:22] <RuediiX> Either way the release branch is more stable, and less prone to failure due to changes.
[17:32] <rioch> RuediiX: is it really necessary to have a trunk? You could just have a branch for each release, right?
[17:40] <rioch> Let's say I develop on my trunk branch and want to release. I would create a branch for this release, and then push the code to that branch as well, or is there a funky way to copy it?
[17:45] <RuediiX> I'm not too familiar with it, I'm still a beginner, but I've seen it done lots of ways.  I've rarely seen EVERY release having a branch made, but I've seen quite a few projects make 2 branches for each currently worked on release.
[17:47] <RuediiX> There are lots of guides.  I really wish Launchpad would better link their documentation to the appropriate areas of their main site.
[17:48] <rioch> yeah, I agree
[17:49] <rioch> I'll use trunk for now and cross the other bridges when I get to them
[17:53] <rioch> ok, and another error. I set my username using bzr launchpad-login, but when I try to push I get: Permission denied (publickey).
[17:53] <rioch> bzr: ERROR: Connection closed: Unexpected end of message. Please check connectivity and permissions, and report a bug if problems persist.
[18:48] <Muscovy> Is there a limit to the number of PPAs a group or user can own?
[18:48] <jml> not that I know of
[20:39] <mirak_> hi
[20:39] <mirak_> the lpia architecture isn't part of the "any" ?
[20:41] <doctormo> mirak_: nope
[20:43] <mirak_> doctormo, ok so I must add "amd64 i386 lpia"
[20:45] <doctormo> mirak_: Your any means "really this doesn't need to be compiled", the problem your having I think is that PPAs don't compile for lpia
[20:46] <lifeless> erm
[20:46] <mirak_> doctormo, I though they where compiling for atom
[20:47] <mirak_> doctormo, this needs to be compiled.
[20:47] <doctormo> For main and universe, but I don't think so for PPAs
[20:47] <maxb> mirak_: Yes, the lpia architecture is part of "any"
[20:47] <mirak_> doctormo, I think it's "all" who means no compile needed
[20:47] <lifeless> all is arch indep
[20:47] <maxb> However, the lpia archive does not exist in lucid and maverick
[20:47] <lifeless> any is 'must be compiled on each arch'
[20:47] <jpds> mirak_: I think it's only available for karmic.
[20:47] <mirak_> ha ok, this changed then
[20:47] <doctormo> lifeless: I stand corrected
[20:47] <lifeless> doctormo: ^ - I think you have your wires crossed ;)
[20:47] <mirak_> doctormo, yes
[20:47] <lifeless> no probs :)
[20:48] <mirak_> doctormo, ayne idea why it was removed from lucid ?
[20:48] <mirak_> lpia is atom right ?
[20:48] <maxb> There was an email to ubuntu-devel-announce, I think
[20:48] <mirak_> ok
[20:48] <mirak_> I don't care anyway, I don't own one
[20:49] <mirak_> and since I am selfish
[20:49] <mirak_> what is the generic cpu type for the amd64 arch ?
[20:50] <mirak_> ifneq (,$(filter amd64,$(DEB_BUILD_ARCH_CPU)))
[20:50] <mirak_>          MAKE_OPTIONS += PARALLEL=PARALLEL_128_SSE2 CPUOPT=amd64
[20:50] <mirak_> endif
[20:50] <mirak_> I am trying to do this but it doesn't work. CPUOPT is wrong.
[20:50] <mirak_> for march
[20:52] <maxb> For that you should consult the gcc documentation
[20:56]  * maxb sighs at the irony of a build which has been "Start in 4 seconds" for several minutes
[21:08] <lantash2> I wonder whether the LP builders will be able to keep up with the additional workload caused by daily builds. I'm currently in the process of setting up daily builds for the LottaNZB project.
[21:08] <lantash2> A test build requested on July 1st is still in the queue (even though the archive test rebuild seems to have been completed/canceled by now) and the ETA is essentially random.
[21:14] <lantash2> Nobody expects the builder admins to implement a Shortest Job First scheduling policy, but waiting 5 days for a 3-minute-build to complete is certainly not desirable. ^^
[23:12] <wbf> hey guys,  can you upload just a script to a ppa? and that script would automatically go in /usr/bin and get updated like any other program?
[23:14] <lifeless> if you package it, yes.
[23:16] <wbf> so i package it like i would any other program, the only source being the script?
[23:16] <lifeless> yes
[23:17] <wbf> cool
[23:17] <wbf> seems a bit like overkill, but cool
[23:32] <MTecknology> I have one package in my PPA that shows as deleted, but still shows up - and hasn't gone away in a long time - any ideas why?
[23:37] <MTecknology> Is it possible to cancel a build? It's in the queue but once it hits it'll already be superceded
[23:40] <maxb> It will auto-cancel when it reaches the head of the queue IIUC
[23:41] <MTecknology> ok