[00:20] <ubotu> New bug: #159169 in launchpad "Launchpad SchoolTool translation page always down." [Undecided,New] https://launchpad.net/bugs/159169
[00:27] <blueyed> Should I file a bug report to ask for mass moving ~60 duplicates? Or is this kind of mass editing already possible somehow?
[00:28] <blueyed> bug #154771 has 60 dupes and is a dupe itself, of bug #153889.
[00:28] <ubotu> Launchpad bug 154771 in adept "Kubuntu 7.10 Upgrading to Kubuntu 7.10 and after gives error and says Distribution is Up To Date" [High,Fix committed] https://launchpad.net/bugs/154771
[00:28] <ubotu> Launchpad bug 153889 in adept "feisty dist upgrade check does not work" [High,Fix committed] https://launchpad.net/bugs/153889 - Assigned to Jonathan Riddell (jr)
[00:29] <Ubulette> waa, lpia in ppa !
[00:30] <Ubulette> + a full rebuild for it. problem is i'm still full, will I explode ?
[00:33] <Fujitsu> blueyed: You have to do it manually at the moment.
[00:33] <Fujitsu> Wooo, more PPA buildds.
[00:34] <blueyed> Fujitsu: then it's seems better to file a bug/request then opening 60 tabs, clicking there two times and pasting, no?
[00:34] <blueyed> But I would be happy to just change the desc and wait for the feature.. ^^
[00:34] <Fujitsu> Except most of them are broken for various reasons... hmm.
[00:35] <Fujitsu> blueyed: Possibly, or you could script it. Or just leave it as is 'cause it's too difficult.
[00:36] <blueyed> ah, there are launchpad python bindings, aren't there? :) but I'm not to eager - and it would cause more damage then good again at the end - DOSing launchpad and such..
[00:37] <Fujitsu> I'm not sure if said bindings to much editing at the moment.
[00:37] <Fujitsu> s/to/do/
[00:38] <blueyed> I've edited the desc of the bug noew.
[00:38] <blueyed> -e
[00:40] <Fujitsu> blueyed: Bug #78596
[00:40] <ubotu> Launchpad bug 78596 in malone "Automatically handle moving duplicates across when duplicating a bug with dupes" [High,Confirmed] https://launchpad.net/bugs/78596
[00:40] <blueyed> Fujitsu: just read that one, too.. :)
[00:42] <Fujitsu> Doesn't look like it will be fixed in the foreseeable future, and will just sit around like the rest.
[00:44] <blueyed> Is there a bug already about distinct color or icon for dupes in search results (if you search "all bugs reported")?
[00:44] <Fujitsu> I don't think so.
[00:45] <Fujitsu> Bug #3796 would fix that, though.
[00:45] <ubotu> Launchpad bug 3796 in malone "Display "Duplicate" as if it's a status" [Low,Confirmed] https://launchpad.net/bugs/3796
[00:47] <blueyed> Fujitsu: yes, thanks. Subscribed. But sooo old already..
[00:53] <Fujitsu> blueyed: That's what happens to bugs in Malone.
[00:54] <Fujitsu> A lot of them just sit around for years and years being annoying.
[00:54] <blueyed> Pity!
[00:56] <Ubulette> seems ppa builders are idle while there are tons of stuff in queue
[00:57] <Fujitsu> Ubulette: The new ones aren't fully set up yet.
[00:57] <Ubulette> i'm talking about samarium & promethium
[00:58] <Fujitsu> Ah.
[00:58] <Fujitsu> The queue-builder is probably running, so they should be OK again in a few minutes.
[00:58] <Ubulette> ~3h idle already
[00:59] <Fujitsu> Ah, something on cesium probably died when the new buildds were inroduced.
[00:59] <Fujitsu> lamont: Do you know anything about this? (I note some of your builds in the histroy of the new builders, so presume you're working on preparing them)
[01:05] <blueyed> The duplicate-bug-handling blueprint links to a non-public page: https://launchpad.canonical.com/DuplicateBugHandling - linked from https://blueprints.edge.launchpad.net/malone/+spec/duplicate-bug-handling
[01:05] <Fujitsu> blueyed: None of the Launchpad specs are public.
[01:06] <Fujitsu> So we always get a (quite often unpleasant) surprise when new features arrive.
[01:06] <blueyed> oh.. I knew I've seen non-public ones before.. I guess I should shut up then now..
[01:12] <somerville32> Has anyone been working on the bug where you can't have a product or team that starts with the letters lp?
[01:13] <Fujitsu> somerville32: Are you sure that's a bug?
[01:13] <somerville32> Fujitsu, My project starts with the letters lp. So, unless I use a different name I can't really make use of launchpad.
[01:13] <Fujitsu> Sounds like it's fairly deliberate, to avoid misleading names or namespace pollution.
[01:13] <Fujitsu> Although I could be wrong.
[01:14] <somerville32> I understand why they may have done it
[01:14] <somerville32> but it is preventing me from making use of launchpad infrastructure for my open source project legitimately 
[01:15] <Fujitsu> You might want to ask a question on the launchpad project.
[01:15] <mpt> somerville32, did you report the bug?
[01:15] <somerville32> I've filled a bug, yes.
[01:16] <mpt> ah, I see, bug 157164
[01:16] <ubotu> Launchpad bug 157164 in launchpad "Project names can not start with lp" [Undecided,New] https://launchpad.net/bugs/157164
[01:16] <mpt> somerville32, most of the Launchpad developers are in meetings this week and next, so it may be a couple of weeks before the bug is looked at
[01:17] <somerville32> mpt: Would you be able to manually create the teams + product for me?
[01:22] <mpt> somerville32, no sorry, I wouldn't have permission for exactly the same reason as you don't
[01:23] <somerville32> Alright. Kiko said that he would manually do it for me but I opted to file the bug so if it'll take a while to fix I'll just poke him when he is around again.
[04:55] <ubotu> New bug: #159203 in rosetta "my translations disappeared" [Undecided,New] https://launchpad.net/bugs/159203
[07:48]  * Hobbsee hopes for no ppa backlog
[08:17] <Hobbsee> no, no ppa backlog it seems - just no queued build.
[09:25] <ubotu> New bug: #159221 in launchpad "Page without Styles Often  Logins" [Undecided,New] https://launchpad.net/bugs/159221
[10:12] <JenFraggle> is there still a problem with edge?  I'm getting nothing but oops at the mo
[10:32] <effie_jayx> hello all... can anyone help with this. I think we finally solved it https://answers.edge.launchpad.net/rosetta/+question/7836
[11:47] <Diije> hi
[12:55] <dato> hello. I was subscribed by somebody to a spec. would it be possible to know who it was, to ask them if it was a mistake or not?
[12:56] <dato> (I'm user "adeodato" and the spec is "drinking-from-the-firehose")
[12:57] <intellectronica> dato: unfortunately, not yet. how important is it to know, are you just curious, or is it a serious issue?
[12:58] <dato> well, I'm mostly curious since I'm not involved in ubuntu development at all.
[12:59] <intellectronica> dato: it must be a mistake, then. being able to know who subscribed you, though, is an important feature. i hope we'll have it soon
[13:44] <Hobbsee> how does one get a list of all ubuntu bugs in universe?
[13:44] <Hobbsee> oh, found it
[14:15] <lamont> Fujitsu: (et al) there are several new buildds that were created, which are still in manual mode and should be lit up sometime soonish (this week? or next).  lpia buildds should get one running today (that's the current priority)
[15:05] <lamont> hrm... no cprov
[15:05] <LaserJock> is there any way to judge the backlog on samarium?
[15:05] <Ubulette> is there a way to see the queue of a builder (ppa) ?
[15:06] <Ubulette> lol, same question
[15:06] <LaserJock> heh
[15:06] <lamont> I'd be interested to see the answer to that as well.
[15:06]  * lamont walks off for a moment
[15:06] <LaserJock> there's a bug for having a PPA build queue
[15:06] <LaserJock> but with multiple build machines I think the queuing is sort of "as available"
[15:08] <LaserJock> right now though there's only 1 each for amd64 and i386 so it'd be nice to see
[15:08] <LaserJock> hopefully nobody uploaded OOo or lang packs ;-)
[15:09] <Ubulette> i think there are 3 builders per arch now
[15:10] <Ubulette> samarium+iridium+thallium for i386/xen
[15:10] <LaserJock> Ubulette: but only samarium is set to "automatic"
[15:10] <Ubulette> promethium+platinum+osmium for amd
[15:11] <Ubulette> yep but hopefully, that will change in a few days
[15:11] <LaserJock> yes, hopefully
[15:12] <lamont> ubotu: 3 builders, 2 of which are set to 'manual' --> not in use
[15:12] <lamont> I'm hoping to light those up today
[15:12] <Ubulette> that would be excellent :)
[15:13] <lamont> I just need to find out what other blockers there are.
[15:17] <alex_muntada> kiko: ping
[15:18] <alex_muntada> kiko: i'd like to talk with you about the project ubuntaires being disabled
[15:19] <LaserJock> alex_muntada: I'm not sure how around kiko is presently, he's at the Ubuntu Developer Summit
[15:20] <alex_muntada> LaserJock: oh, i see
[15:22] <alex_muntada> anyone else from the launchpad team available? i'd like to know a few details about that project disabling before discussing the issue tonight with the catalan locoteam
[15:23]  * alex_muntada was looking for kiko since he sent the notice about the project being disabled
[15:23] <LaserJock> yeah, he's probably the guy to talk to
[15:24] <alex_muntada> LaserJock: thanks anyway :)
[15:24] <LaserJock> alex_muntada: your email should at least get some attention, but I'm not sure if it'll be in time for your locoteam meeting
[16:05] <Ubulette> hm, samarium is dead
[16:05] <Ubulette> socket.timeout 
[16:27] <gnomefreak> is there something wrong with this? bzr push bzr+ssh://gnomefreak@bazaar.launchpad.net/~gnomefreak/iceowl/debian-0.x
[16:28] <Ubulette> no
[16:29] <gnomefreak> there seems to be
[16:29] <gnomefreak> bzr: ERROR: Not a branch: "/home/gnomefreak/iceowl/work/iceowl/iceowl-0.5/debian/".
[16:32] <gnomefreak> i think i know why
[16:32] <gnomefreak> notice im pushing the short path instead of full path
[16:33] <Ubulette> just cd ..
[16:34] <gnomefreak> i cant push this to save life
[16:34] <gnomefreak> even using the right path
[16:35] <gnomefreak> i dont have to commit to start a new branch right?
[16:35] <gnomefreak> and im assuming --create=prefix is assumed with push
[16:36] <LaserJock> I think you'd have to have something to push
[16:36] <LaserJock> and I think you need --create-prefix for a new branch
[16:36] <Ubulette> i need used --create-prefix
[16:36] <gnomefreak> i thought they did away with the need for --create-prefix but i will try it
[16:37] <Ubulette> i never used --create-prefix
[16:37] <LaserJock> hmm, maybe
[16:37] <LaserJock> it's been a while since I pushed a new branch ;-)
[16:37] <Ubulette> gnomefreak, do you have at least 1 rev in your branch ?
[16:37] <gnomefreak> no new branch
[16:38] <gnomefreak> i dont feel much like changing ubuntu over to debian
[16:38] <gnomefreak> but maybe i should
[16:38] <LaserJock> you have to have something to push
[16:39] <gnomefreak> ok lets try something ;)
[16:40] <Ubulette> gnomefreak, you don't have to have something new, just something (ie not an empty branch)
[16:40] <gnomefreak> yes i know like edit changelog :)
[16:40] <somerville32> Yeah, just create the branch and than commit.
[16:40] <somerville32> No need to actually edit any of the files
[16:40] <somerville32> But you might want to add the files first
[16:41] <gnomefreak> somerville32: for this im gonna have to as i have tried it that way already
[16:41] <somerville32> gnomefreak, Did you add the files though?
[16:41] <gnomefreak> no cant add files
[16:41] <gnomefreak> that would defeat the purpose seeing as it doesnt need anything to make it work
[16:42] <gnomefreak> cant just add files nad expect package to build
[16:43] <somerville32> The problem is that you can't push because you don't have a revision, right?
[16:43]  * gnomefreak wonders if branching from sunbird and replacing debian dir with iceowls
[16:43] <LaserJock> gnomefreak: the question is if you've actually got a branch
[16:43] <LaserJock> do you have the files added to the branch
[16:43] <LaserJock> did you commit
[16:44] <gnomefreak> it keeps telling me bleh is not a branch
[16:44] <LaserJock> do you have any revisioints
[16:44] <gnomefreak> even while commiting
[16:44] <jjesse> did you do a branch init?
[16:44] <gnomefreak> no never needed that before
[16:44] <somerville32> bzr init; bzr add -r *; bzr commit
[16:44] <gnomefreak> hmmmmmm
[16:45] <gnomefreak> somerville32: without a revision there is no need for bzr -r
[16:46] <somerville32> -r is for recursive
[16:46] <gnomefreak> new branch no revisions yet -r 1 willo be first
[16:46] <Ubulette> bzr add is enough, it's recursive by default
[16:46] <gnomefreak> ah thought you did bzr -r
[16:46] <somerville32> Ubulette, k
[16:48] <lamont> and we now have 3 i386 and 3 amd64 ppa buildds
[16:48] <lamont> that should help with the backlog a bit
[16:49] <Ubulette> lamont, but none seems to be doing anything at the moment. is that expected ?
[16:50] <Ubulette> ie, samarium stuck with socket.timeout 
[16:50] <LaserJock> lamont: \o/
[16:52] <lamont> Ubulette: hit reload?
[16:53] <lamont> not sure why the amd64 ppa buildds are all idle, though
[16:53] <Ubulette> \o/
[16:54]  * lamont was fixing all the ppa buildds, and that has a side effect of causing LP to decide they're dead if it scans them while I'm doing maintenance.  sorry.
[16:54] <Ubulette> so all are ok now ?
[17:01] <lamont> all the i386 and amd64 ppa buildds are on automatic and should be working.
[17:01] <lamont> OTOH, amd64 ppa buildds are all idle
[17:02] <lamont> lpia PPA buildds are all on manual - we have a little work to do there, and then we'll light those up
[17:15] <Ubulette> thx
[19:48] <pwnguin> i thought edge was a semi private beta?
[19:50] <pwnguin> for some reason im being directed to edge without being logged in. i suppose there could be a cookie thing though
[20:15] <Ubulette> another lang packs flood in ppa
[20:15] <Ubulette> let's see how the new builders cope with that
[22:09] <Odd_Bloke> I'm getting OOPS-670EB88 when trying to report a new bug...
[22:13] <Odd_Bloke> And now I'm not. :p
[22:42] <Fujitsu> cpro1: Some build-queueing thing seems to be rather broken...