[03:12] <woodwizzle> How can I see a list of bugs i'm subscribed to? Under my profile there is a list subscribed bugs action but it doesn't list the closed bugs i'm subscribed to
[03:17] <jamesh> woodwizzle: from the subscribed bugs page, pick advanced search
[03:17] <bimberi> woodwizzle: Advanced Search -> [Check all Statuses]
[03:17] <jamesh> then select what statuses you want
[03:18] <woodwizzle> cool thanks
[04:16] <Ademan> sorry, i know this is OT but #zope is apparently dead,  mkzopeinstance shouldn't require root should it?
[04:17] <lifeless> no idea sorry Ademan 
[04:17] <Ademan> no problem, you guys have already been more responsive than #zope lol
[04:17] <lifeless> if thats a zope2 thing then I doubt anyone here has current knowledge of it
[04:18] <lifeless> zope2 and 3 are very different
[04:20] <spiv> Ademan: my dim memory is that it doesn't
[04:21] <Ademan> well i'm speaking specifically about zope3, and i agree, and so does a doc that mkzopeinstance doesn't require root, but it's blowing up unless i run it as root
[04:21] <thumper> Ademan: I don't think so no
[04:21] <thumper> Ademan: it configures some stuff and makes a sandbox, but no, I don't think it needs a reboot
[04:21] <thumper> Ademan: sorry misread ;-)
[04:22] <Ademan> lol thumper
[04:22] <thumper> Ademan: I think I filed a bug about that sometime ago, and I thought it was fixed
[04:23] <thumper> Ademan: but I agree, it shouldn't need root
[04:23] <Ademan> hrm
[04:23] <Ademan> if it helps i'm using ubuntu, maybe the package just sucks
[08:28] <N_I_E_L_S> \whois N_I_E_L_S
[08:57] <carlos> morning
[09:00] <mpt> Goooooooooooooooooooooood morning Launchpadders!
[09:07] <Hobbsee> morning carlos, mpt, mrevell 
[09:13] <mrevell> morning!
[09:35] <ignas> hi
[09:35] <ignas> does anyone know how to enable "hardy" in ones PPA ?
[09:35] <ignas> i have tried uploading a package for hardy
[09:35] <ignas> but it failed with a chroot problem
[09:35] <ignas> now i can see hardy in the list of distributions
[09:36] <ignas> but hardy directory is still not in there
[09:36] <cprov> ignas: try again, https://bugs.edge.launchpad.net/soyuz/+bug/196782
[09:36] <ubotu> Launchpad bug 196782 in soyuz "First build in a new PPA fails" [Medium,In progress]  - Assigned to Celso Providelo (cprov)
[09:36] <ignas> cprov: but http://ppa.launchpad.net/schooltool-owners/ubuntu/dists/
[09:36] <ignas> still does not have hardy in there
[09:37] <cprov> ignas: wait up to 20 minutes after you receive the upload acceptance email and it will be there.
[09:37] <ignas> so - i upload, get an error wait 20 minutes, then press "retry"
[09:41] <cprov> ignas: yes, pretty much it until it get this fixed (I'm working on it right now).
[09:42] <ignas> cprov: will i get in trouble if i'll try building 128 packages for hardy in my PPA?
[09:42] <cprov> ignas: no, this problem only affects the first build in the suite
[09:43] <cprov> ignas: after the 20 minutes it gone and your PPA can accept/build as many packages as you can upload ;)
[10:57] <ubotu> New bug: #220937 in launchpad "Restriction on bug subscriptions to avoid address gathering by spammers" [Undecided,New] https://launchpad.net/bugs/220937
[11:46] <Fujitsu> Is somebody going to fix samarium at some point?
[11:48] <silwol> i got a problem with bzr and paramiko installed in my home directory on a server without root access for me
[11:48] <silwol> installed paramiko using "python setup.py install --home ~"
[11:48] <silwol> did the same for bzr
[11:49] <silwol> when I want to branch from sftp url, I get
[11:49] <silwol> user@server:~/download/paramiko/paramiko-1.7.1$ bzr branch sftp://server/path/to/branch
[11:49] <silwol> bzr: ERROR: Unsupported protocol for url "sftp://server/path/to/branch": Unable to import paramiko (required for sftp support): cannot import name util
[11:49] <Fujitsu> cprov: Do PPA copies comply with version-ratchet?
[11:50] <silwol> anybody knows what the problem could be?
[11:50] <Fujitsu> silwol: Try #bzr, perhaps.
[11:51] <silwol> Fujitsu: thanks... tried it, but it was empty... was on the wrong irc server ;-)
[11:51] <Fujitsu> Haha.
[11:52] <silwol> i was surprised that nobody had created a bzr chan
[13:04] <cprov> Fujitsu: no, the versions are not checked. If you copy old packages they will simply get superseded.
[13:04] <Fujitsu> OK.
[13:05] <Fujitsu> cprov: I see you've brought the first PPA builds chrootwaiting bug forward. Thanks.
[13:06] <Hobbsee> Fujitsu: to when?
[13:07] <cprov> Fujitsu: yup, 1.2.4 issue.
[13:07] <Fujitsu> What cprov said.
[13:08] <ignas> the fact that i can add *anyone* as a subscriber to my branch, and can't remove the branch afterwards is a bug or a feature?
[13:09] <Fujitsu> ignas: YA LP misfeature.
[13:09] <Hobbsee> nice
[13:09] <ignas> and what would happen if someone would like add a branch, subscribe some huge launchpad group to it's checkins, and commit some lucrative comercial proposals involving nigeria and a few billions? ;)
[13:10] <Hobbsee> ignas: probably the same as showing propriatory milestones in all user search pages.
[13:10] <Fujitsu> Hm, can one subscribe others to one's own branches?
[13:10] <ignas> yes
[13:10] <ignas> and you can't unsubscribe them after that
[13:10] <soren> Yeah, just like you can subscribe anyone to your bugs.
[13:10] <Fujitsu> ignas: They can always unsubscribe themselves.
[13:10] <Fujitsu> But there are better ways to spam thousands of people.
[13:10] <Fujitsu> If you use a bug, for example.
[13:11] <ignas> problem is - i can't delete MY branch that I have added, because it has subscribers
[13:11] <ignas> because - only they have the permission to unsubscribe
[13:11] <Fujitsu> Hmm.
[13:12] <Fujitsu> I smell a bug-filing.
[13:12] <Hobbsee> ignas: report it as a bug, wait the required 6 months, and it might get fixed?
[14:17] <soren> Hobbsee, Fujitsu: Wow. You guys never get tired, do you?
[14:19] <Fujitsu> soren: Of what?
[14:20] <soren> trolling
[14:20] <Fujitsu> Where?
[14:20] <soren> ^ up there
[14:21] <Fujitsu> I'm not sure that calling ignas' lovely spam suggestion an LP misfeature is trolling.
[14:21] <soren> Had it been just a single incident, no.
[14:21] <Fujitsu> soren: I've not "trolled" much of late.
[14:21] <ignas> that, trolling?
[14:22] <ignas> it's not even close to trolling, at least by definitions of trolling that I know ;)
[14:22] <Fujitsu> soren: I admit having been rather too quick to criticise LP at times in the past. But not recently.
[14:23]  * Hobbsee wonders what soren's preferred method of saying "file a bug and wait" is, which does not class as trolling.
[14:23] <soren> Fujitsu: Ok. In that case, I apologise. I don't follow this channel very closely, but just happened to stop by and saw what I thought was "the usual" stuff going on.
[14:24] <ignas> being cynical is not the same as trolling ;)
[14:24] <Hobbsee> soren: it would be *really* nice if you could pay more attention, before shooting your mouth off in a public channel, thanks.  If you're not going to pay close enough attention, then you'd be wise to keep your mouth *shut*.
[14:24] <Hobbsee> Thank You.
[14:24] <soren> O_O
[14:25] <statik> this is really lame. i have to be in this channel, but it feels very unpleasant in here with all the constant complaining
[14:26] <soren> Sorry for the noise.
[14:26]  * soren wanders off and tries to make himself useful again
[15:06] <ignas> is it normal for packages to be stuck in "build will start in 41 seconds"
[15:07] <ignas> for like 10 minutes
[15:07] <ignas> https://edge.launchpad.net/~schooltool-owners/+archive/+builds
[15:07] <Fujitsu> The build start estimation stuff is very, very new.
[15:07] <Fujitsu> Not on production yet.
[15:07] <Fujitsu> And obviously a rather inexact science, particularly as your packages haven't been built before.
[15:08] <matsubara> "five minutes turkish"
[15:08] <ignas> i understand the part - "they don't know how long the build will take"
[15:09] <ignas> but not the "they don't know when they'll start building my packages" ;)
[15:09] <kiko> ignas, if we don't know how long builds will take, then how do we know when your build will start?
[15:09] <Hobbsee> ignas: they don't know exactly how long all the other builds will take
[15:09] <kiko> al-maisan, see above?
[15:09] <al-maisan> kiko: sure .. do you want me to comment?
[15:10] <ignas> i see, kind of makes sense I guess, just that I had 2 builders working for me for like 4 hours, and bam - theyr'e working for someone else now ;)
[15:10] <Fujitsu> Where has samarium run off to since the power outage?
[15:11] <kiko> al-maisan, what sort of question is that? of course. :)
[15:11] <al-maisan> kiko: fine :-)
[15:14] <Hobbsee> Fujitsu: abducted.
[15:14] <al-maisan> ignas: for packages that were built before we actually take the most recent build duration when estimating the build job start time ..
[15:15] <Hobbsee> kiko: FYI, the queue accepting bug is now non-critical for hardy (too late), but it would be great to see it fixed and tested for intrepid (particularly after the new annoucements)
[15:16] <al-maisan> .. for packages that are "new" (i.e. no previous build duration information) we analysed the historical build duration data and distilled a build rate (KB/second) ..
[15:16] <al-maisan> .. that we use in conjunction with the package size to estimate a build duration.
[15:17] <Fujitsu> How close is the correlation between size and build time? Would it be more useful to complain that there's insufficient data to calculate it?
[15:17] <ignas> i see, just that Pending (0)  and apparent lack of activity got me paranoid
[15:18] <al-maisan> This was one way to go about it but we felt that it diminishes the value of the feature ..
[15:18] <ignas> and there is no way to see how many other packages are in front of you
[15:19] <al-maisan> .. and we felt reasonably confident that the conclusions we drew from the historical build data were good enough for estimation ..
[15:20] <kiko> ignas, I think that's al-maisan's next step, providing a view on the queue.
[15:20] <ignas> i see
[15:20] <ignas> so there is no reason to worry and I should just keep waiting
[15:21] <kiko> Hobbsee, intellectronica wrote a patch yesterday that we'll CP today to try and see if the problem gets solved, so stay tuned for some testing tomorrow.
[15:21] <Hobbsee> kiko: \o/
[15:22] <kiko> Hobbsee, it doesn't fix the problem entirely -- i.e. the page may still be slow -- but I think it might be enough of a fix
[15:22] <kiko> (to stop the page from timing out)
[15:22] <ignas> Estimated build start:  	0 seconds ago :D (it still hasn't started)
[15:23] <ignas> but the message looks funny ;)
[15:23] <al-maisan> ignas: the software is brand new and not deployed on the production server yet..
[15:23] <Hobbsee> kiko: that'd be good
[15:23] <al-maisan> once version 1.2.4 is out it should work as expected
[15:23] <ignas> al-maisan: i know, i just don't have anything else to do while waiting for the last 2 packages ;)
[15:24] <al-maisan> OK :-)
[15:24] <ignas> al-maisan: i am going to get some food now ;)
[15:24] <ignas> see you ;)
[15:24] <al-maisan> Good idea .. :-)
[15:24] <al-maisan> see ya!
[15:46] <ubotu> New bug: #221037 in launchpad "Move webservice.txt to lazr/doc and make it run without any layers" [Undecided,New] https://launchpad.net/bugs/221037
[15:48] <dholbach> hiya
[15:48] <jtv> hi dholbach
[15:49] <dholbach> can somebody give me a hint what we could do in the team setup so the technical-board team would not get emails for people joining/departin the ubuntu-universe-contributors team which motu-council is owner of
[15:49] <dholbach> ?
[15:52] <Hobbsee> dholbach: i don't think you can.
[15:53] <Hobbsee> there's no mailing list for admins
[15:55] <dholbach> salgado: ^ can you think of something to fix that? or is there just "make somebody else the owner"?
[15:57] <Hobbsee> dholbach: that's all i've found.
[15:57]  * Hobbsee wonders if it sends directly to all the team owners individually, or to their team mail address
[15:58] <salgado> dholbach, just a minute
[15:59] <dholbach> salgado: take your time
[16:00] <salgado> dholbach, the technical-board team gets these notifications because motu-council has no contact address (thus Launchpad notifications are sent to all team members)
[16:01] <salgado> would it be a problem to add a contact address to motu-council?
[16:03] <dholbach> salgado: it seems that the team had a single owner before who did not get the notifications himself
[16:07] <salgado> dholbach, I don't see what you mean
[16:08] <dholbach> salgado: motu-council was just recently made owner of the team, it was a person before who did not get join/depart notifications - what might be the reason for that?
[16:09] <salgado> dholbach, maybe the old owner had left the team while still being the owner?  (that's currently possible)
[16:09] <dholbach> ahhh I see
[16:11] <ubotu> New bug: #221047 in launchpad "Project group milestone view broken" [High,Confirmed] https://launchpad.net/bugs/221047
[16:15] <crimsun> Ng: thanks for terminator, BTW.  </driveby>
[16:15] <Ng> :D
[16:23] <dholbach> salgado: seems he was member, owner and admin before. hmmm
[16:25] <salgado> dholbach, that's weird
[16:26] <dholbach> is there anything that changed in the admin/owner/team mail notification world?
[16:28] <salgado> nope
[17:09] <fta> samarium (xen-i386)   	NOT OK : (113, 'No route to host') (AUTO)
[17:15] <ubotu> New bug: #221079 in launchpad "Not obvious who receives team membership notification" [Undecided,New] https://launchpad.net/bugs/221079
[18:48] <kiko> Hobbsee, the patch has been cherry-picked. can you check the +queue page again when you have a moment?
[18:50] <mdz> kiko: I just got OOPS-844EC76 trying to look at a bug related to the 8.04 release
[18:50] <mdz> kiko: and ...77 on reload; it seems to be persistent
[18:51] <mdz> kiko: the page is https://bugs.edge.launchpad.net/ubuntu/+source/apt/+bug/220817
[18:51] <ubotu> Launchpad bug 220817 in openoffice.org "Xubuntu Hardy: ubiquity installs Open Office during installation" [High,In progress] 
[18:51] <kiko> mdz, is it a timeout or an oops proper?
[18:51] <mdz> kiko: timeout
[18:51] <kiko> mdz, fascinating.
[18:51] <mdz> 3x in a row now
[18:52] <kiko> there's something broken in that query.
[18:52]  * kiko grumbles
[18:53] <kiko> BjornT, hey
[18:54] <mdz> kiko: it was fine just a few minutes ago
[18:54] <kiko> mdz, a fix was just cherry-picked.
[18:54] <kiko> it regressed this I suspect.
[18:55] <kiko> mdz, I'm looking into it
[18:55] <mdz> kiko: thanks
[18:57]  * BjornT looks
[18:57] <kiko> BjornT, I have the problem
[18:58] <kiko> mdz, yuck. arguably a postgresql bug. ORs in the query breaking things up completely.
[19:00] <mdz> kiko: related to the cherrypick or coincidental?
[19:01] <kiko> no, related, definitely.
[19:02] <kiko> mdz, will have a fix cowboyed shortly
[19:02] <kiko> or perhaps it's just easier to revert, hmmm
[19:02] <mdz> kiko: I am a big fan of reverting in these situations
[19:02] <mdz> and testing a proper fix later
[19:03] <kiko> it depends on the process we need to follow, I'll chat with BjornT to figure it out
[19:03] <kiko> mdz, you can use lpnet, not edge, meanwhile.
[19:09] <kiko> mdz, you copy?
[19:09] <afflux> kiko: I got multiple timeouts (eg. OOPS-844EC88) when changing the status and adding a comment to https://bugs.edge.launchpad.net/ubuntu/+bug/220645/ , maybe that's related
[19:09] <ubotu> Launchpad bug 220645 in ubuntu "package ubuntu-desktop 1.102 failed to install/upgrade: dependency problems - leaving unconfigured" [Medium,Incomplete] 
[19:09] <kiko> yes
[19:09] <kiko> it is
[19:10] <afflux> fokay
[19:10] <mdz> kiko: will I not get automagically redirected?
[19:10] <afflux> huh, -f
[19:10] <afflux> mdz: you can disable that on http://launchpad.net, IIRC
[19:10] <kiko> mdz, afflux: visit https://launchpad.net/ and click on "disable"
[19:10] <mdz> kiko: I sent in my comment via email, presumably that worked OK
[19:10] <kiko> mdz, afflux: BjornT and I will have this fixed in a jiffy meanwhile
[19:11] <kiko> mdz, yes, it will.
[19:11] <afflux> kiko: thanks
[19:22] <smagoun> Is there an LP dev/admin around? I'm having trouble getting to bugs on edge.lp.net: 
[19:22] <smagoun> Error ID: OOPS-844EC100    Error ID: OOPS-844EA149
[19:23] <matsubara> smagoun: BjornT and kiko are working on a fix for it.
[19:23] <smagoun> matsubara: good to know, thanks for the prompt reply!
[19:23] <matsubara> smagoun: meanwhile you can disable the redirect to edge in https://launchpad.net and use the regular launchpad.net site
[20:31] <kiko> mdz, smagoun: fixed
[20:31] <smagoun> kiko: thanks!
[20:37] <Mez> can I request a new licence to be added to launchpad
[20:38] <Mez> (the WTFPL)
[20:38] <Mez> http://sam.zoy.org/wtfpl/COPYING
[20:39] <kiko> Mez, not really. come on! :)
[20:39] <laga> szmtag zaehler
[20:39] <Mez> kiko, why not? It's a valid OSS licence (what I'm planning to release my next project under)
[20:39] <laga> huh? where did that come from? sorry
[20:58] <mdz> kiko-afk: thanks for the quick turnaround
[21:06] <asabil> hi all
[21:06] <asabil> can any launchpad admin fix the svn repository for this: https://code.launchpad.net/vala/trunk ?
[21:09] <jcastro> is it pointing to the wrong thing?
[21:13] <asabil> yes
[21:13] <asabil> the trailing /vala needs to be removed
[21:13] <asabil> it is pointing to a subfolder in the project :/
[21:17] <matsubara> done asabil
[21:25] <andreas> in ppa, how do I interpret the "build score"? I searched help.launchpad.net but didn't find a meaning
[21:26] <cprov> andreas: it works like 'build priority', the higher the faster a build will be dispatched.
[21:27] <andreas> ok, the higher the better, but I don't know the other scores, so just a number doesn't mean much. I got 1005, for example
[21:28] <cprov> andreas: in 1.2.4 they will be converted in 'time_to_dispatch' and you will see 'will be dispatched in X minutes'
[22:22] <hollinch> BalaamsMiracle
[22:25] <sm> g'day all.. thanks for launchpad mail lists
[22:26] <sm> is there a way to use one for casual users and existing subscribers, without requiring them all to join launchpad and the team ?
[22:26] <sm> even if they are read-only ?