[02:11] <Bodsda> hey guys, im trying to upload some files to a branch on lp, but i get this error,. -- bod@bodubuntustu:~/tmpStuff/termtutor$ bzr push lp:termtutor
 bzr: ERROR: Cannot lock LockDir(http://bazaar.launchpad.net/%7Etermtutor-team/termtutor/termTutor/.bzr/branch/lock): Transport operation not possible: http does not support mkdir()
[02:12] <mwhudson> bzr launchpad-login <your lp username>
[07:23] <pkern> Is the new bugs page design for edge will to be deployed?
[07:23] <wgrant> pkern: s/will/still/?
[07:24] <wgrant> Edge won't update to RF for a little while yet.
[07:24] <wgrant> Maybe in 35 minutes, but I may have my timezones confused.
[07:24] <pkern> wgrant: Sorry for the typo.  Thanks.
[07:33] <jamesh> wgrant: edge isn't being automatically updated at the moment due to a few speed regressions
[07:34] <wgrant> jamesh: So, we've had this new feature announced 12 hours ago, and it won't be around for ages?
[07:38] <jamesh> wgrant: we're looking to fix the speed regressions and get things up and running again
[07:38] <jamesh> wgrant: staging will probably have it next update
[07:38] <jamesh> staging looks to be one rev too old
[07:39] <wgrant> jamesh: Ah. Might have been advisable to have given some estimation of when it was going to happen, then.
[07:39] <jamesh> wgrant: the decision to roll back edge was probably made after the announcement, unfortunately :(
[07:39] <wgrant> Ah.
[07:40] <wgrant> When does staging update?
[08:04] <jamesh> wgrant: docs say "once a night".  I don't know when that is exactly
[08:09] <wgrant> jamesh: OK, thanks anyway.
[10:27] <whs> intellectronica# "In the new design, you'll see that the 'Actions' menu has gone." but https://bugs.edge.launchpad.net/clubuntu/+bugs?search=Search&field.status=New&field.status=Incomplete&field.status=Confirmed&field.status=Triaged&field.status=In+Progress&field.status=Fix+Committed or https://bugs.edge.launchpad.net/clubuntu/+bug/224837 still have a Actions menu
[10:28] <intellectronica> whs: i know. sorry for the confusion. the new design is not yet in effect. i hope it will be soon
[12:00] <mpt> Gooooooooooooooooooooood afternoon Launchpadders!
[12:00] <Hobbsee> evening mpt!
[14:58] <jodok> am i right that launchpad.net is down?
[14:59] <intellectronica> jodok: yeah, seems like there's some kind of problem. we're checking it now. sorry for the inconvenience
[15:01] <jodok> intellectronica: thumbs up
[15:06] <intellectronica> jodok: looks like we're up again
[15:07] <jodok> perfekt intellectronica, thanks
[15:27] <Festor> I have a question about PPA. Can I use the same orig.tar for several packages of the same program in different versions of Ubuntu?
[15:27] <cprov-out> Festor: yes, that's why we have them, in first place.
[15:27] <Festor> how?
[15:28] <cprov-out> Festor: so you don't have to re-upload a fat tarball every time
[15:28] <Festor> PPA rejects myt packages
[15:28] <Festor> I should use dput -f ?
[15:28] <cprov-out> Festor: you have to use the same tarball already published in ubuntu.
[15:29] <Festor> aMule 2.2.1 is not published
[15:29] <Festor> in ubuntu at least
[15:38] <cprov-out> Festor: let me check why your upload in failing, one sec
[15:38] <cprov-out> Festor: are submitting 106406c373ffde93e6787e6c93081bce 5992137 x11 optional amule_2.2.1.orig.tar.gz ?
[15:40] <cprov-out> Festor: you PPA (~ppa1 version) has  194d698ae4d83cfb9bdf5928717a3e7c 5966518 x11 optional amule_2.2.1.orig.tar.gz
[15:40] <cprov-out> Festor: that's why it is failing.
[15:41] <jjesse> this may have been asked already, but is launchpad responding slow for others?
[15:49] <jboisture> how do you set your launchpad identity in bzr in ubuntu hardy?
[15:49] <beuno> jboisture, bzr launchpad-login
[15:50] <beuno> actually, bzr launchpad-login your_username  :)
[15:50] <jboisture> thanks
[15:50] <beuno> :)
[15:51] <jboisture> that worked great thanks
[15:56] <whs> in https://edge.launchpad.net/clubuntu I saw a blank iframe at the bottom (build 6480)
[15:59] <whs> seems that in every pages
[16:00] <intellectronica> whs: we're aware of that, and are working on a fix
[16:02] <whs> 6461 doesn't have this problem.
[16:35] <bdmurray> intellectronica: Do you know if there is an issue regarding openoffice.org bug watches?
[16:36] <intellectronica> bdmurray: i don't of anything, but if you suspect a problem, let's check
[16:37] <intellectronica> gmb: do you know anything about them ooo bugwatches? ^^^
[16:37] <bdmurray> bug 15451 shows a problem connecting
[16:38] <gmb> intellectronica, bdmurray: Looking...
[16:38] <bdmurray> the first 4 or 5 at https://bugs.launchpad.net/openoffice/+bugs do too
[16:40] <gmb> bdmurray, intellectronica: Ah, looks like the URL we have for the OOo issue tracker is wrong. Well, it's right, but it's redirected to another URL. It seems that we're not handling the redirect properly.
[16:40] <intellectronica> bdmurray: i can see some connection errors to the ooo bugtracker from two days ago
[16:40] <bdmurray> gmb: Okay, thanks.  Should I submit a bug?
[16:40] <gmb> bdmurray: No, I'll take care of it. Thanks for the heads-up.
[16:42] <bdmurray> gmb: great, thank you!
[16:42] <gmb> np.
[16:43] <\sh> guys, the http -> https forwarder is not working somehow...is it known?
[16:44] <mpt> \sh, works for me
[16:44] <mpt> \sh, what is an example of an URL that doesn't redirect?
[16:44] <\sh> mpt: forget about it...now it's working again...hopefully only a glitch at telemaxx 
[16:45] <gmb> bdmurray: I've fixed the URL. It should hopefully start updating properly soon.
[16:46] <bdmurray> gmb: wow, that was fast!
[16:46] <gmb> bdmurray: Well, it was an easy fix in this case ;). The underlying problem still exists. We shouldn't barf when we get redirected. Or at least we should barf in a more helpful manner.
[16:50] <gmb> Ah, that doesn't help. It's a meta refresh redirect rather than a straight HTTP one. So we're not doing anything wrong; we just can't get anything useful from the URL we were trying to get something useful from.
[16:51] <intellectronica> that's evil
[16:52] <gmb> intellectronica: Well, I guess it's predicated on the fact that they expect humans to be looking at the tracker rather than machines, which is a bit naive, but there you go.
[17:40] <gmb> bdmurray: Looks like the OO.o bug watchs are updating correctly now. Any that are still showing errors should get cleaned up within the next 24 hours.
[17:41] <bdmurray> gmb: great, thanks again
[17:44] <gmb> No worries.
[18:21] <calc> how hard would it be to add an icon in bug lists showing if a bug has been marked as upstream?
[18:22] <calc> similar to how milestoned and mentoring bugs are now