[00:06] <shadeslayer> *facepalm*
[00:21] <shadeslayer> debfx: around?
[00:40] <shadeslayer> debfx: Quintasan JontheEchidna i've pushed my kdelibs branch over here : https://code.launchpad.net/~rohangarg/kdelibs/ubuntu
[00:41] <shadeslayer> now i'm off to study for my last couple of exams :)
[00:41] <shadeslayer> cya
[00:43] <ScottK> FYI, Bug #789708
[00:48] <JontheEchidna> this is horrifying: http://www.theopensourcerer.com/2011/05/28/ubuntu-uk-loco-cds/
[00:49] <JontheEchidna> :'(
[00:52] <ScottK> Someone who lives on the relevant island should arrange a rescue.
[00:52] <ScottK> Where is Riddell when you really need him?
[00:55] <valorie> AlanBell actually runs kubuntu, at least sometimes
[00:55] <valorie> he's just exposing the hens to good computing!
[00:56] <ScottK> Maybe time for seaLne to the rescue ...
[00:56] <valorie> lol
[00:58] <ScottK> So it's definitely after 0001UTC, right?
[00:59] <ScottK> No.  3 more minutes
[00:59] <ScottK> Two even
[01:00] <ScottK> So I can finish the KC election as soon as we hit Sunday UTC.
[01:01] <valorie> how many voted, ScottK?
[01:01]  * ScottK decides to wait an extra minute or two in case someone saw that and went "oops, forgot to votee."
[01:02] <valorie> thank you for running the election, btw
[01:02] <ScottK> 34 of 57 eligible.
[01:02] <ScottK> No problem.  The only annoying part was getting the email addresses out of LP.
[01:02] <ScottK> No one voted in the last two or three days.
[01:02] <valorie> indeed
[01:02] <valorie> hmmm, just over half
[01:03] <valorie> voting like Americans
[01:03] <ScottK> Not bad considering many of them aren't very active anymore.
[01:03] <ScottK> OK.  Time.
[01:03] <ScottK> http://www.cs.cornell.edu/w8/~andru/cgi-perl/civs/results.pl?id=E_714f581d4fc2dad7
[01:04] <ScottK> Congratulations apachelogger, JontheEchidna, and DarkwingDuck
[01:06]  * DarkwingDuck chuckles
[01:14] <ScottK> OK.  Results announced.
[01:17] <ScottK> DarkwingDuck: Since you're the newbie, you get to schedule a meeting for next week to review/approve specs and process any memberships.
[01:18] <ScottK> Doodle poll is the usual method.
[01:21] <ScottK> I mailed Riddell and asked him to adjust team membership.
[01:27] <claydoh> w00t! congrats to apachelogger DarkwingDuck and JontheEchidna !!
[01:28] <ScottK> Unsubscribed from kubuntu-users ML.  If anyone from there bitches about the election and I need to know, someone please tell me.
[01:30] <ScottK> apachelogger: While your busy not setting up the ice cream magic on our arm boxes, would you please have a look at Bug #773062 and see if maybe there's a fix we can cherrypick for an SRU?
[02:04] <claydoh> ScottK: from the lack of any response to the poll om the -users list, should be no problem. Heck not many Kubuntu users in there imo lol
[02:05] <claydoh> also lack of response in the forums iirc as well, tho most there do use kubuntu  :D
[02:05] <ScottK> Yeah, I didn't figure it was high risk to go ahead and unsubscribe.
[06:58] <Linkmaster> Hey, popping in here for two things, first is, I wanted to say thanks for all your work on Kubuntu, its my favorite OS since I picked it up, so yeah. thanks!
[06:59] <ScottK> Thanks.
[07:34] <tsimpson> aww, seems no one likes poor old me :(
[07:34] <tsimpson> but seriously, congrats to apachelogger, DarkwingDuck and JontheEchidna :D
[08:12] <yofel> apachelogger, DarkwingDuck, JontheEchidna: congratulations :D
[09:15] <bambee> morning
[09:25] <bambee> JontheEchidna: when you write "in bzr" on merges.u.c , what do you mean ? I don't find these packages into our repositories (kubuntu-ninjas, kubuntu-ppa)
[09:27] <yofel> that should be lp:~kubuntu-packagers/<package>/ubuntu
[09:27] <yofel> bzr means bzr, not PPA
[09:34] <bambee> ah o_O
[09:34] <bambee> that's why I did not find them... xD
[09:35] <Quintasan> apachelogger, JontheEchidna, DarkwingDuck: Grats
[10:04] <Quintasan> ScottK: Thanks for running the elections
[10:41] <apachelogger> debfx, ScottK: what package were you talking about WRT update-alternatives > dpkg-divert and debconf?
[10:41] <debfx> apachelogger: kdesudo
[10:41] <bambee> apachelogger, JontheEchidna, DarkwingDuck: congrats btw ;)
[10:41] <debfx> but I think we should keep update-alternatives
[10:42] <apachelogger> uhm, overlord again \o/
[10:42]  * apachelogger hugs the members
[10:47] <apachelogger> debfx: we are upstream to debian, if debian thinks diverging from upstraem is good then that is not our fault :P
[10:48] <apachelogger> incidentially there is a good reason for using update-alternatives ... try looking for divert kdesudo on launchpad bugs
[10:48] <apachelogger> there are approx 5000000 of those
[10:48] <apachelogger> there constantly went stuff wrong, making the kdebase/runtime upgrade fail ever so often
[10:58] <apachelogger> JontheEchidna, DarkwingDuck: congrats
[12:21] <bambee> the debian version for kdenetwork contains this .install file http://paste.ubuntu.com/614523/
[12:21] <bambee> however, these files are not built and do not exist in debian/tmp/ o_O
[12:22] <bambee> (fileshare_propsdlgplugin.so and kcm_kcmsambaconf.so for example)
[12:22] <bambee> and the only patch in debian/patches has nothing to do with that... wtf ?
[12:24] <debfx> afaik we have backported samba related stuff form 4.7
[12:49] <apachelogger> ScottK: that cmake bug looks like fun btw
[12:50] <apachelogger> also I do not think it is a cmake issue at all
[12:50] <apachelogger> or perhaps it is, but only partially
[12:51] <apachelogger> in particular it is probably falling over the fact that cxx has a cmd and a arg, which generally speaking of course is a bit of a bogus situation
[12:55] <apachelogger> yeah
[12:55] <apachelogger> gcc got three args with -d
[12:55] <apachelogger> cmake does not call either
[12:56]  * apachelogger runs cmake with tracing
[12:57] <apachelogger> /usr/share/cmake-2.8/Modules/Platform/UnixPaths.cmake(32):  EXECUTE_PROCESS(COMMAND dpkg-architecture -qDEB_HOST_MULTIARCH OUTPUT_VARIABLE CMAKE_ARCH_TRIPLET OUTPUT_STRIP_TRAILING_WHITESPACE )
[12:57] <apachelogger>    Called from: [4]	/usr/share/cmake-2.8/Modules/Platform/UnixPaths.cmake
[12:57] <apachelogger>                 [3]	/usr/share/cmake-2.8/Modules/Platform/Linux.cmake
[12:57] <apachelogger>                 [2]	/usr/share/cmake-2.8/Modules/CMakeSystemSpecificInformation.cmake
[12:57] <apachelogger>                 [1]	/home/me/src/git/libechonest/CMakeLists.txt
[12:57] <apachelogger> /usr/bin/ccache: invalid option -- 'd'
[12:57] <apachelogger> 5 bucks that call comes from a patch
[12:57] <debfx> eh, why do we have a security patch from 2009 in kde4libs that is not applied upstream :O
[12:57] <apachelogger> me@osiris:/tmp/cmake-2.8.4+dfsg.1$ grep -ri dpkg-architecture .
[12:57] <apachelogger> ./debian/patches/ubuntu_multiarch_library_directory.diff:+EXECUTE_PROCESS(COMMAND dpkg-architecture -qDEB_HOST_MULTIARCH OUTPUT_VARIABLE CMAKE_ARCH_TRIPLET OUTPUT_STRIP_TRAILING_WHITESPACE)
[12:58] <apachelogger> jr strikes again :P
[12:58] <debfx> what's wrong with it?
[12:59] <apachelogger> well, it causes ccache -dumpmachine to be called
[12:59] <apachelogger> leading to an eror in ccache
[12:59] <apachelogger> as obviously the call should be ccache gcc -dumpinfo
[12:59] <apachelogger> eh
[12:59] <apachelogger> dumpmachine
[13:01] <apachelogger> debfx: perhaps the patch was applied differently upstream?
[13:01] <debfx> it wasn't applied at all, upstream doesn't care about multiarch (yet?)
[13:03] <debfx> how does ccache hook into the buildsystem? does it modify $PATH?
[13:05] <apachelogger> no
[13:05] <apachelogger> you set a new CXX and CC env var
[13:06] <apachelogger> debfx: multiarch is something gcc, that should totally be implemented in cmake upstream
[13:06] <apachelogger> anyhow
[13:06] <apachelogger> for some reason dpkg-architecture calls:
[13:06] <apachelogger> execve("/bin/sh", ["sh", "-c", "${CC:-gcc} -dumpmachine"], [/* 50 vars */]) = 0
[13:06] <apachelogger> resulting in
[13:06] <apachelogger> execve("/usr/bin/ccache", ["/usr/bin/ccache", "-dumpmachine"], [/* 50 vars */]) = 0
[13:06] <apachelogger> which then produces crap outs
[13:08] <apachelogger> I believe cmake pokes the env around a bit
[13:08] <apachelogger> I know that it definitely stores CC/CXX as a combo of command + argN
[13:09] <apachelogger> so if cmake were to set its envrionemnt so that CC only contains the command and no the arg (which is generally sane behaviour I suppose), that would screw over the poor old dpkg-architecture
[13:21] <debfx> merging is so confusing :/
[13:35] <bambee> debfx: I was talking about this patch http://paste.ubuntu.com/614543/ ?
[13:37] <debfx> bambee: yes, that patch clearly removes those kcms
[13:41] <debfx> kde4libs is almost ready
[13:42] <bambee> debfx: I know, but this is the patch commited into kubuntu-packagers/kdenetwork/ubuntu :D
[13:42] <bambee> look at http://bazaar.launchpad.net/~kubuntu-packagers/kdenetwork/ubuntu/view/head:/debian/patches/kubuntu_05_samba_sharing.diff then
[13:43] <bambee> - should be replaced by + I guess
[13:46] <debfx> why is that?
[13:46] <debfx> but it reminds me, we need to adapt that patch to call qapt
[13:48] <debfx> bambee: that patch removes some old crappy kcms and adds a new plugin
[14:00] <yofel> does someone know if there's a reason kdesdk is built against an explicit version of boost in kubuntu?
[14:03] <bambee> debfx: ohh I understood. the debian kdenetwork-filesharing.install is too old
[14:04] <bambee> debian kde team did not backport this patch ?
[14:08] <bambee> well apparently not
[14:09] <yofel> we added that ourselves, ask them if they want the patch
[14:10] <yofel> they might not even know it exists
[14:11] <bambee> ok
[14:14] <apachelogger> c2tarun: Tarun K. Mall (c2tarun) has accepted the invitation to make Kubuntu
[14:14] <apachelogger> Mobile Team (kubuntu-mobile) a member of UBUNTU - AL (linux-traipu).
[14:14] <apachelogger> WTH
[14:14] <apachelogger> ?
[14:14] <c2tarun> ??
[14:14] <c2tarun> apachelogger: actually I dont exactly know what is it. I thought you guys are starting something new
[14:15] <yofel> all ninjas are kubuntu-mobile admins for some reason, you usually shouldn't touch it
[14:15] <apachelogger> c2tarun: in that case you probably should not touch things?
[14:16] <c2tarun> yofel, apachelogger: sorrrryyy :(
[14:17] <c2tarun> apachelogger: sorry, this question might be irrelevant for this channel, but I dont know where to ask. being a KDE-developer is there a way to directly contribute to kubuntu?
[14:18] <apachelogger> yofel: can you undo this, because I can't for one reason or another
[14:18] <yofel> let me try...
[14:18] <apachelogger> rbelem: could you please transfer ownership of ~kubuntu-mobile to kubuntu-members or kubuntu-council
[14:21] <apachelogger> hm, kubuntu-kdesudo also could use an ownership change
[14:22] <apachelogger> wgrant: can you poke https://launchpad.net/~linux-traipu in the nose or something for inviting half of launchpad teams to become member?
[14:23] <yofel> meh, I don't get how to leave the team either :S
[14:23] <apachelogger> ah
[14:23] <apachelogger> kubuntu-dev and kubuntu-ninjas are admin of kubuntu-mobile
[14:23] <apachelogger> that is bogus
[14:24] <yofel> at least make that members, not ninjas. Ninjas have nothing to do with -mobile
[14:25] <apachelogger> well
[14:25] <apachelogger> quite frankly I do not see the point in having members be admin
[14:25] <yofel> true
[14:25] <apachelogger> dev and council  as admin should be sufficient, members as member of the team
[14:26] <apachelogger> there is big issue of trust with the ninjas team as anyone willing enough can become member, thus having ninjas have access to anything official direclty is a dangerous thing IMHO
[14:27] <apachelogger> yofel: I think launchpad has a usability fail ^^
[14:27] <yofel> agreed
[14:28] <apachelogger> ah well
[14:29] <apachelogger> kubuntu-members membership is not even necessary
[14:29] <apachelogger> kubuntu-mobile has no branches
[14:29] <apachelogger> so other than a sense of belonging therewould not be much gain
[14:30] <apachelogger> yofel<EMAIL_ADDRESS>[14:30] <apachelogger> wth
[14:31] <yofel> I'm getting tired of the answer to crappy usability being "But rest assured, you can do it by API!" *-.-
[14:33]  * apachelogger files launchpad question
[14:36]  * ryanakca thinks the admin of the UBUNTU - AL team needs a talking to. I don't understand why he's invited some twenty or so unrelated teams to join.
[14:38] <apachelogger> debfx: how about we retire kdesudo and make kdesu work properly instead?
[14:39] <apachelogger> ryanakca: interestingly enough I believe this very much a scam
[14:39] <bambee> https://code.launchpad.net/~bambi/kdenetwork/debian-merge-4.6  <--- Do I propose a merge ? (into kubuntu-packagers/kdenetwork/ubuntu)
[14:40] <yofel> bambee: changelog is crap
[14:40] <apachelogger> ryanakca: calling the team a loco while it is not actually a loco is not very reassuring
[14:41] <apachelogger> also the excessive use of capslock even though it is not capslockday makes me eyes burn
[14:41] <bambee> yofel: I need to merge the debian changelog too ? (at least for 4.6.3)
[14:41] <yofel> a) you didn't use merge-changelog b) junk my UNRELEASED changelog and keep what's necessary from there
[14:43] <bambee> I don't know what merge-changelog is
[14:45]  * bambee slaps himself and installs ubuntu-dev-tools ^^
[14:45] <yofel> a script that merges the ubuntu changelog with the debian changelog
[14:46] <yofel> so the changelog entries are in the right order
[15:12] <bambee> yofel: done
[15:13] <ryanakca> apachelogger: *nod*
[15:13] <yofel> bambee: remove my 4.6.3-0ubuntu1 changelog and add what you think is needed from there to your changelog
[15:13] <yofel> bambee: you didn't keep any of our changes?
[15:14] <bambee> I kept our changes
[15:14] <yofel> your changelog doesn't say that, see 4:4.5.2-0ubuntu1 changelog
[15:14] <bambee> ok
[15:15] <yofel> you changelog entry should list all changes between our package and the debian one
[15:15] <yofel> *your
[15:19] <debfx> apachelogger: upstream kdesu is quite scary
[15:22] <debfx> so I guess we'll drop the patch numbering as well to be consistent with debian
[15:25] <yofel> was just wondering the same as I'm merging kdesdk patches right now
[15:26] <yofel> so from kubuntu_01_name to kubuntu_name ?
[15:26] <debfx> yofel: yep
[15:40] <bambee> yofel: something like that ? http://bazaar.launchpad.net/~bambi/kdenetwork/debian-merge-4.6/view/head:/debian/changelog :)
[15:42] <yofel> change "Merge with Debian git remaining changes" into "Merge with Debian. Remaining changes:" - this is a regular merge, not from git.
[15:42] <yofel> also remove Taruns changes, all of that was done in debian. Also drop my first entry
[15:43] <yofel> bambee: why do you have "- Bump Standards-Version to 3.9.2; no changes needed." in your changelog o.O?
[15:43] <bambee> I just merged this change from debian
[15:43] <bambee> don't know :\
[15:44] <yofel> urgh, you misunderstood something. Your changelog should have all changes that WE applied to the DEBIAN package
[15:44] <yofel> meaning the diff between 4.6.3-1 and 4.6.3-1ubuntu1
[15:45] <yofel> since you used the debian package and applied all changes that we want to keep to it
[15:52] <bambee> yofel: I just added changes from debian into our package. so there are no remaining changes. All our previous changes are listed in this changelog
[15:52] <bambee> (like our patches)
[15:53] <yofel> which means you did the wrong way, you don't apply the debian changes to our package, you take the debian package and apply our changes to it
[15:53] <yofel> since the ideal case would be dumping our package and using the debian one
[15:54] <yofel> so start with: pull-debian-source kdenetwork
[15:54] <yofel> and apply our changes to the package
[15:55] <bambee> no I downloaded our changes (ie bzr branch lp:~kubuntu-packagers/kdenetwork/ubuntu), compute differences between kdenetwork/ubuntu and kdenetwork/debian and apply these changes into kdenetwork/ubuntu (into my own branch)
[15:55] <bambee> s/our changes/ our debian directory/
[15:55] <kubotu> bambee meant: "no I downloaded  our debian directory (ie bzr branch lp:~kubuntu-packagers/kdenetwork/ubuntu), compute differences between kdenetwork/ubuntu and kdenetwork/debian and apply these changes into kdenetwork/ubuntu (into my own branch)"
[15:56] <yofel> hm, meaning you took the diff, threw our debian/ folder away and applied the diff to the debain/ folder from debian and then commited that into bzr?
[15:56] <shadeslayer> debfx: yeah, i was wondering why the CVE wasn't applied upstream
[15:57] <yofel> well, let me look at the other files, but at least the changelog is wrong
[15:59]  * debfx uploads kde4libs
[15:59] <shadeslayer> w00t
[15:59] <bambee> yofel: basically, I did "diff -u <our_debian_dir_from_kubuntu> <the_real_debian_dir_from_debian.org>", I only took the interesting changes, and then I applied them to our debian (from kubuntu)
[15:59] <yofel> \o/
[16:00] <shadeslayer> debfx: anything else that needed changing?
[16:00] <yofel> bambee: wrong way, you take the diff, and apply anything interesting to the debian folder (from DEBIAN!!)
[16:00] <shadeslayer> ( that diff is HUGE )
[16:00] <yofel> we want the debian package, except whatever changes we really need to keep
[16:01] <bambee> :\
[16:01] <shadeslayer> bambee: you should read the merging procedure on the wiki :)
[16:02] <shadeslayer> merging is one PITA
[16:02] <yofel> yeah, spent half the day merging kdesdk :/
[16:02] <shadeslayer> there are like a bazillion things that can go wrong
[16:02] <shadeslayer> yofel: i spent 2 nights on kde4libs xD
[16:03] <yofel> yeah, I noticed that much
[16:03] <shadeslayer> and now i'm all sorts of unprepared for tommorows exam :P
[16:04] <shadeslayer> debfx: did you push to bzr as well?
[16:04] <shadeslayer> and kdelibs bzr needs upgrading btw
[16:04] <debfx> shadeslayer: I had to change quite a few things
[16:04] <yofel> to what?
[16:04] <shadeslayer> yofel: newer bzr format
[16:05] <shadeslayer> debfx: oh .. minor/major mistakes?
[16:05] <bambee> shadeslayer: https://wiki.ubuntu.com/UbuntuDevelopment/Merging ?
[16:05] <shadeslayer> bambee: yes
[16:05] <bambee> ok
[16:05] <bambee> thanks
[16:05] <shadeslayer> np :)
[16:06]  * yofel backports pkg-kde-tools for natty into ninjas
[16:06] <shadeslayer> yofel: wait, wasn't pkg-kde-tools going into backports?
[16:06] <yofel> I said ninjas, put it wherever you want later
[16:07] <bambee> sorry but.. if we apply the above changes to the debian folder from debian.org... why commit them into bzr ?
[16:07] <yofel> but I can't testbuild anything right now with natty having too old pkg-kde-tools and oneiric not having all 4.6.3 deps for kdesdk right now
[16:07] <shadeslayer> yofel: no i mean, pkg-kde-tools was going into ubuntu-backports
[16:07]  * bambee is reading the wiki
[16:07] <yofel> ah, I don't have that enabled here, lemme check
[16:07] <shadeslayer> afaik it's not been uploaded to ubuntu-backports yet
[16:08] <yofel> it's not, and I need it now
[16:08] <shadeslayer> alright
[16:10] <debfx> shadeslayer: that's the diff: http://paste.ubuntu.com/614581/
[16:11] <shadeslayer> debfx: diff from my merge? or diff from debian?
[16:11] <debfx> from your merge
[16:11] <shadeslayer> ( my internet connection is complete crap right now )
[16:11] <shadeslayer> wow
[16:13] <yofel> why did you drop the kde4libs (4:4.4.1-1) experimental; urgency=low entry? or was that twice in there?
[16:13] <debfx> yofel: yes
[16:13] <yofel> ah
[16:17] <shadeslayer> uhm
[16:17] <shadeslayer> debfx: why did you remove the install icons line from debian/rules?
[16:17] <debfx> shadeslayer: they aren't used anymore
[16:17] <debfx> the patch that needed them has been long disabled and I've dropped it completely now
[16:18] <shadeslayer> ah okay
[16:21] <yofel> hm, our pbuilder list missing hook still depends on cdbs
[16:21] <yofel> apachelogger: can you fix that? ^
[16:24] <apachelogger> yes, I do not have time though
[16:25] <apachelogger> it is not like it matters much, is it?
[16:26] <yofel> true, take your timem
[16:26] <yofel> *time
[16:58] <DarkwingDuck> Morning
[17:12] <DarkwingDuck> Do the Kubuntu meeting notices get sent to kubuntu-users as well as kubuntu-devel?
[17:15] <JontheEchidna> just -devel
[17:16] <DarkwingDuck> Thank ye. JontheEchidna mind looking at the doodle to ensure I idn't mess this up too bad before I send it? :D
[17:16] <JontheEchidna> sure
[17:16] <DarkwingDuck> http://www.doodle.com/89xsm8fw2y6v8qqs
[17:17] <DarkwingDuck> I'm not sure how timezones work with doodle...
[17:17] <DarkwingDuck> I copied the times for meeting from the last one AFAIK
[17:17] <JontheEchidna> iirc it's UTC
[17:17]  * DarkwingDuck nods
[17:18] <DarkwingDuck> I didn't know if Doodle autochanged for timezone
[17:18] <DarkwingDuck> What times does it show for you?
[17:18] <JontheEchidna> 3-12 PM
[17:19] <yofel> here too
[17:19] <debfx> DarkwingDuck: afaik you need to enable timezone support when creating the poll
[17:22] <DarkwingDuck> debfx: I went back through the settings, I can't find a TZ support anymore... Those are the same times that the last poll was.
[17:23] <debfx> DarkwingDuck: it's on the time suggestions page
[17:26] <debfx> ScottK: kde4libs is waiting on libdlrestrictions now. since when is the MIR team so pedantic about binary package promotions?
[17:28] <JontheEchidna> probably when a binary packages controls library loading
[17:36] <DarkwingDuck> debfx: http://imagebin.org/155768 not there anymore.
[17:36] <JontheEchidna> shadeslayer: looking at your merge, Kubuntu Developers should be kept as the maintainer with Debian Qt/KDE as the XSBC-Original-Maintainer
[17:37] <yofel> JontheEchidna: debfx already merged kdelibs
[17:37]  * debfx forgot to push :(
[17:37] <debfx> DarkwingDuck: is it there when you create a new poll?
[17:38] <DarkwingDuck> debfx: no.
[17:38] <JontheEchidna> oh, ok
[17:38] <DarkwingDuck> debfx: It used to be... that's what confused me.
[17:39] <debfx> DarkwingDuck: it's still there for me: http://i.imgur.com/50v11.png
[17:39] <DarkwingDuck> debfx: nevermind, it's there. I'm rebuilding
[17:40] <DarkwingDuck> the times are listed in UTC Correct?
[17:41] <DarkwingDuck> ahhh, this is better (I think)
[17:41] <DarkwingDuck> These times look better? http://www.doodle.com/nvfgrvpg6p2vzqpp
[17:42] <JontheEchidna> 11 AM to 8 PM
[17:43] <JontheEchidna> offset 4 hours from the last numbers, so it looks pretty UTC
[17:44] <DarkwingDuck> So, it's supposed to be 11A to 8P UTC?
[17:45] <JontheEchidna> I think so. Those look like pretty sane times for me
[17:47] <DarkwingDuck> JontheEchidna: one more shot eh? http://www.doodle.com/diamdzurqp87app6
[17:48] <JontheEchidna> ah, yeah. Better. Come to think of it I am -5 UTC, not -4
[17:48] <JontheEchidna> the confusing bit is that in daylight savings we're -4
[17:48] <DarkwingDuck> :D
[17:48] <JontheEchidna> or something
[17:48] <DarkwingDuck> Okay, I'll use that last one.
[17:48] <yofel> burn DST with fire
[17:49] <DarkwingDuck> Aye
[17:49] <DarkwingDuck> DST is so dumb
[17:50] <JontheEchidna> Arizona is about the only sane state in the US, in regards to DST (or the lack thereof)
[17:50] <JontheEchidna> Unfortunately they're a bit crazy in other regards :P
[17:51] <DarkwingDuck> Arizona, Hawaii and half of Indiana
[17:53] <QuintasanDroid> sup
[17:53] <DarkwingDuck> Sup QuintasanDroid
[17:54]  * QuintasanDroid reinstalls Natty
[17:54] <QuintasanDroid> utterly borken here
[17:54] <QuintasanDroid> sigsegvs on everything
[17:55] <QuintasanDroid> sigoops on apt
[17:55] <QuintasanDroid> lol
[17:55]  * QuintasanDroid needs to spin his own mix of Kubuntu
[17:56] <QuintasanDroid> shadeslayer: do you know any tools to remaster CD?
[17:56] <QuintasanDroid> they have to work unlike remastersys
[17:57] <shadeslayer> QuintasanDroid: you just download the cd -> extract it and chroot into it
[17:57] <shadeslayer> and do whatever you want then :)
[17:58] <QuintasanDroid> chroot into squashfs you mean?
[17:58] <QuintasanDroid> and then I put it back into iso?
[17:58] <shadeslayer> one sec
[17:59] <shadeslayer> QuintasanDroid: https://help.ubuntu.com/community/LiveCDCustomization
[17:59] <shadeslayer> QuintasanDroid: you use mkisofs and point it to your extacted chroot
[18:00] <shadeslayer> QuintasanDroid: in that guide, "sudo mksquashfs edit extract-cd/casper/filesystem.squashfs -nolzma" won't work, use the command below that
[18:03] <ScottK> debfx: Dunno.  If that's all it needs, upload it and let it FTBFS and then I'll bit more.
[18:04] <debfx> ScottK: I've already uploaded, it's in dep-wait
[18:05] <ScottK> debfx: Great.
[18:06]  * QuintasanDroid will spin Ultimate Kubuntu
[18:08] <QuintasanDroid> shadeslayer: if, by any chance we get debdelta support in Launchpad this year, we are spinning Neon LiveCD
[18:08] <QuintasanDroid> NO WAY
[18:09] <QuintasanDroid> installer crashed at grub install
[18:09] <QuintasanDroid> it is the official iso
[18:09] <QuintasanDroid> ...
[18:12] <ScottK> apachelogger: I already complained to LP people.  They told me to go see the Community Council (re the team spam).  Someone should do that.
[18:12]  * QuintasanDroid notes that GRUB is broken on CD
[18:13]  * QuintasanDroid wonders why that was not sorted out
[18:15] <DarkwingDuck> Grub is broken?
[18:15] <QuintasanDroid> installer crashed at it
[18:15] <QuintasanDroid> and manually running the command yelps around about aufs
[18:15] <DarkwingDuck> hmmz,
[18:15] <QuintasanDroid> that was reported already
[18:15] <QuintasanDroid> though there is no known fix
[18:16] <QuintasanDroid> workaround is to chroot
[18:16] <QuintasanDroid> ...
[18:16]  * QuintasanDroid cant boot his install
[18:16] <ScottK> QuintasanDroid: I find people have no end of trouble with 64 bit desktops.  I say don't bother.
[18:17] <QuintasanDroid> using 32 bit is not acceptable workaround
[18:17] <ScottK> debfx: I've begged for libdlrestrictions1 and libdlrestrictions-dev to be promoted.  Now we'll see.
[18:17] <DarkwingDuck> Only issue I had with grub is when I tried to install on hardware RAID.
[18:17] <DarkwingDuck> I had to disable HDW RAID from BIOS to install with a software RAID
[18:17] <debfx> ScottK: you've gone that far? :)
[18:17] <debfx> thanks
[18:17] <ScottK> Begged is probably a little strong, but I did ask.
[18:17]  * QuintasanDroid curses his computer
[18:18]  * DarkwingDuck has a vision of Scott on his knees
[18:19] <QuintasanDroid> DarkwingDuck: That's not happening :P
[18:19] <DarkwingDuck> QuintasanDroid: Oh I know... He said begged and that flashed in my mind for a moment. But, I'm sure that stern look with a expressionless face is more like it.
[18:20] <QuintasanDroid> not many people can make ScottK so powerless, he wields wide influence
[18:20] <QuintasanDroid> I mean, you see ScottK wanting something and that gets done asap :P
[18:21] <ScottK> Unfortunately this one thing you can't do unless you are employed by Canonical.  It requires shell access in their data center.
[18:21] <DarkwingDuck> ScottK: Ahhh
[18:21] <ScottK> The is where the lack of jr really hurts.
[18:21] <DarkwingDuck> Yeah.
[18:21] <DarkwingDuck> Or another employee that works with Kubuntu that knows someone.
[18:22] <QuintasanDroid> hmmmmmmm
[18:22] <QuintasanDroid> shadeslayer: ping
[18:23] <QuintasanDroid> shadeslayer: go to #bzr, wave at Riddell and sent him link to the oom bug in LP when importing branches
[18:23] <QuintasanDroid> :P
[18:23] <QuintasanDroid> oh,
[18:23] <QuintasanDroid> and run
[18:24] <DarkwingDuck> lol
[18:24] <QuintasanDroid> no, seriously
[18:24] <QuintasanDroid> noone wants to have anything in common with bzr on LP
[18:24] <QuintasanDroid> brrr
[18:25] <QuintasanDroid> bzr > git
[18:25]  * QuintasanDroid hides
[18:25]  * DarkwingDuck snickers
[18:25]  * DarkwingDuck waits for someone to pop up for OPS
[18:26] <QuintasanDroid> DarkwingDuck: You dont want to get in apachelogger's line of fire when he sees the statement above
[18:26] <QuintasanDroid> :P
[18:27] <QuintasanDroid> meh
[18:27] <QuintasanDroid> I need to get this retarded hardware sorted out asap
[18:27] <DarkwingDuck> hehehe
[18:27] <QuintasanDroid> why it wont boot after a power off? -_-
[18:27] <DarkwingDuck> ?
[18:27] <QuintasanDroid> I can soft reboot it
[18:27] <QuintasanDroid> if I power it off and on again
[18:28] <QuintasanDroid> I get no POST, no display, no power on USB
[18:28] <QuintasanDroid> but fans turn normally and hardware gets power
[18:28] <QuintasanDroid> if I wait 20 minutes or so
[18:28] <QuintasanDroid> and then power it on
[18:28] <QuintasanDroid> then it works
[18:28] <QuintasanDroid> stupid, isnt it.?
[18:29]  * apachelogger smacks QuintasanDroid with IL (δ, ω , if eq?(IX(delta, env, P redArg1(exp)), IX(delta, env, P redArg2(exp)))then IX(delta, env, T henP art(exp)) else IX(delta, env, ElseP art(exp))) = IL (δ, ω , IX(delta, env, ElseP art(exp))
[18:29] <DarkwingDuck> ROFL
[18:29] <QuintasanDroid> ohshi-
[18:29] <QuintasanDroid> what the hell?
[18:29] <QuintasanDroid> dont tell me thats GIT source code
[18:30] <QuintasanDroid> apachelogger--
[18:31] <DarkwingDuck> QuintasanDroid: I think you just got hit by a driveby
[18:31] <tsimpson> I never did like functional programming
[18:31]  * QuintasanDroid hurls the aforementioned equation back at apachelogger
[18:31] <apachelogger> ok
[18:31] <apachelogger> now you asked for it
[18:31] <apachelogger> QuintasanDroid: IL (δ, ω , IX(delta, env, [CALL GGT [IV S X1][IV S X2]])) =IL (δ, ω , DoCall(delta, omega, [CALL GGT [IV S X1][IV S X2]])) =IL (δ, ω , IX(delta, NewEnv(F ormP ar(delta, F N P art([CALL GGT [IV S X1][IV S X2]])), EvalList(delta, env, ArgP art([CALL GGT [IV S X1][IV S X2]]))), Body(delta, F N P art([CALL GGT [IV S X1][IV S X2]]))))
[18:32] <apachelogger> incidentially enough GGT = GCD in german
[18:32] <apachelogger> so if I pasted the other 300 lines of interpretation you'd have something useful
[18:33]  * QuintasanDroid hurls it back at apachelogger anyways
[18:33] <QuintasanDroid> bleh, this looks worse than pyth0rn
[18:33] <DarkwingDuck> Congrats apachelogger
[18:34] <jussi> QuintasanDroid: apachelogger have your units hsipped yet?
[18:34] <apachelogger> for making a language worse than pyth0rn, I am not sure that is something you should congratulate people on
[18:34] <QuintasanDroid> jussi: Do not kid me, it will stay at least a week at Polish customs office :/
[18:34] <DarkwingDuck> no silly, re-election
[18:35]  * QuintasanDroid 's package got from Japan to Poland in 3 days
[18:35] <apachelogger> actually it is a much saner language, as it reduces only to integers, predicates, conditionals and lists
[18:35] <QuintasanDroid> it was being held at customs for 3 weeks
[18:35] <QuintasanDroid> jussi: ^ Magic of Poland
[18:36] <QuintasanDroid> jussi: I am not able to track the package now since my Kubuntu is borked
[18:36] <yofel> reinstall asap
[18:36] <yofel> more like now
[18:37] <QuintasanDroid> trying
[18:37] <QuintasanDroid> it wont boot after install
[18:37] <QuintasanDroid> :/
[18:37]  * QuintasanDroid will try recovery mode in 20 minutes
[18:37] <QuintasanDroid> :S
[18:37] <yofel> the only issues I had with natty and installing was a kernel oops when starting parted and there is a existing btrfs somewhere in sight
[18:38] <yofel> other than that it worked fine
[18:38] <QuintasanDroid> no btrfs here
[18:38] <QuintasanDroid> ext4 on root
[18:38] <DarkwingDuck> QuintasanDroid: What about installing Grub from LiveCD?
[18:38] <QuintasanDroid> DarkwingDuck: it is broken
[18:38]  * yofel alwasys chroots so he never hit *that* bug
[18:38] <QuintasanDroid> you need to chroot from LiveCD to install it
[18:40] <DarkwingDuck> QuintasanDroid: http://bit.ly/91F2wh
[18:40] <DarkwingDuck> QuintasanDroid: You don't *have* to chroot to do it.
[18:40] <QuintasanDroid> you do lol
[18:41] <QuintasanDroid> otherwise I get cannot stat 'aufs' module
[18:42] <DarkwingDuck> ahhhhh
[18:42] <jussi> apachelogger: you may want to reply to the mail on the -devel list (ubuntuone kde). The guy could do with a little help by the looks of things, and Id say you would have a couple of answers?
[18:44] <JontheEchidna> jussi: oh!  :P
[18:45] <JontheEchidna> jussi: What does Mortal Kombat and a church in Helinski have in common?
[18:45] <jussi> no idea...
[18:45] <JontheEchidna> Finnish Hymn!
[18:45] <jussi> Hah!
[18:46] <QuintasanDroid> lol
[18:47]  * yofel didn't get that...
[18:48]  * QuintasanDroid makes his install lighter via chroot
[18:48] <JontheEchidna> When you've almost killed somebody in the game Mortal Kombat, the announcer says "Finish him!"
[18:48] <JontheEchidna> In a church in Finland, you would most likely sing Finnish Hymns
[18:49] <yofel> lol
[18:49] <yofel> ^^
[18:52] <ScottK> DarkwingDuck: It needs to be an employee who's also an archive admin.
[18:56] <DarkwingDuck> ScottK: I'll remember that if I land this job.
[18:57] <ScottK> debfx: Was there anything from the kde4libs merge that needs to go back to Debian?
[18:57] <ScottK> If so, I think MoDaX wants us just to commit to git.
[18:59] <debfx> ScottK: no, except maybe some patches
[18:59] <debfx> but that needs investigating
[19:00] <ScottK> OK.  Someone should do that ...
[19:00] <QuintasanDroid> :d
[19:06] <apachelogger> jussi: no shipping yet, also that mail on -devel requires looking into the code, otherwise I could only guess, and that guess would be a) API change on the server b) no auth
[19:07] <jussi> apachelogger: ooh, mines already in .de :)
[19:07] <jussi> or in transit from .de...
[19:07] <debfx> kubuntu_cmake_install_paths.diff: can probably be dropped. kde sequence should take care of that. changelog doesn't even mention the patch ...
[19:07] <jussi> May 29, 2011 3:15 AM Departed FedEx location KOELN DE
[19:08] <apachelogger> well, I only ordered on friday... ;)
[19:08] <debfx> kubuntu_CVE-2009-2702.diff: needs investigating why it's not upstream
[19:09] <QuintasanDroid> k
[19:09] <QuintasanDroid> it works
[19:10] <debfx> kubuntu_useragent.diff: could be changed to use dpkg-vendor or something
[19:12] <debfx> the rest are backports or can't go to debian
[19:16] <debfx> apparently we have that cve from fedora
[19:16] <debfx> and the fedora spec file says: "Not Upstreamed? why not ? -- Rex"
[19:18] <ScottK> Maybe rdieter knows by now?
[19:19] <ScottK> In any case it sounds like worth pushing to Debian with the CVE reference.
[19:20] <debfx> debian closed the CVe bug saying it's fixed in version 4.3.2
[19:20] <ScottK> I have a vague recollection of this.
[19:20] <ScottK> I think it used to be a larger patch.  Part went upstream and part they didn't take.
[19:20] <ScottK> ENOCLUE why.
[19:20] <apachelogger> debfx: how would dpkg-vendor be useful there?
[19:21] <ScottK> I'm probably guilty of cargo culting the patch along.
[19:21] <ScottK> apachelogger: Your cmake/ccache commentary was TLDR.  What was the bottom line?
[19:21] <debfx> apachelogger: then we could push it to debian (if they are interested)
[19:21] <apachelogger> ScottK: I made two comments, the latter is the bottom line
[19:22] <ScottK> In the bug?
[19:22] <apachelogger> no way to SRU because it is not even clear what exactly breaks it
[19:22] <apachelogger> I mean, a patch breaks it, but other than that little is known
[19:22] <JontheEchidna> I think keeping  a CVE patch unnecessarily is much better than accidentally removing it
[19:22] <JontheEchidna> e.g. no so much cargo culting
[19:22] <apachelogger> what we know is that dpkg-architecture causes the fail, why exactly it does that is the big unkown
[19:24] <apachelogger> Nightrose: apparently the calligra member of my team of awesome made a pitstop in our channel of awesome for like 6 hrs, without saying anything though ;)
[19:24] <apachelogger> not that I had been awake between 0:22 and 6:38
[19:49] <JontheEchidna> Quintasan: project neon question in #kubuntu
[19:49] <JontheEchidna> [14:48:01] <BajK> when I install Project Neon it installs to /opt, so I can just run sudo /opt/project-neon/bin/kdm and I can use the KDE master?
[19:51] <debfx> unit test of the day: QCOMPARE( randObject.nextByte() == randObject.nextByte(), false );
[19:51] <JontheEchidna> haha
[19:52] <debfx> in qca2
[19:52] <JontheEchidna> it's checking if a byte and its next byte are the same?
[19:52] <debfx> yes, then it obviously can't be random :P
[19:53] <JontheEchidna> :P
[19:53] <JontheEchidna> http://xkcd.com/221/
[19:53] <JontheEchidna> obligatory xckd
[19:53] <debfx> that really makes me question if I want to run the test suite
[19:54] <debfx> JontheEchidna: the unit test has probably been written in response to that xkcd :D
[19:57] <Quintasan> no seriously
[19:57] <Quintasan> WHY THE HELL DO I GET SEGFAULTS
[19:58] <yofel> run memcheck
[19:59] <Quintasan> huh?
[19:59] <Quintasan> once in libpthread-2.13.so[7f56bdc36000+18000]
[19:59] <Quintasan> dpkg got it at libperl.so.5.10.1[7fa7a76ad000+162000]
[19:59] <Quintasan> :/
[20:00] <shadeslayer> Quintasan: why do we need debdelta for a Neon CD?
[20:00] <shadeslayer> also lol @ bzr > git
[20:01] <Quintasan> because if we ship neon live cd user will have to downloadan over 9000mb everyday even though he might not want it
[20:01] <Quintasan> debdelta will greatly reduce the downloading
[20:01] <ScottK> JontheEchidna: It'd have been funnier if the RFC reference was real.
[20:02] <Quintasan> rekonq crash!
[20:02] <Quintasan> yay
[20:02] <shadeslayer> i wash my hands off rekonq :P
[20:02] <shadeslayer> Quintasan: complaint to upstream
[20:05] <bambee> debfx: it's checking that the same object cannot return the same value twice, as it's random. (assuming it's an object which generates random values)
[20:05] <bambee> what is wrong ?
[20:06] <debfx> bambee: it fails if two subsequent random numbers are the same
[20:07] <debfx> that means the test fails every 256 time (assuming the rng is perfect)
[20:11] <JontheEchidna> Presumably the object has several random bytes. nextByte() would return the next byte in line, and advance to the next one which would be returned when you call it again
[20:14] <bambee> what does the method when there is no next byte? (because all of them have been used)
[20:15] <debfx> bambee: it's a PRNG that can generate an endless stream of bytes
[20:15] <bambee> PRNG ?
[20:16] <bambee> ohh
[20:16] <debfx> pseudorandom number generator
[20:32] <QuintasanDroid> yofel: I got 7 errors on memtest
[20:32] <QuintasanDroid> is it bad?
[20:33] <QuintasanDroid> well this is shit
[20:33] <QuintasanDroid> I bought this pc one year ago and it is breaking down
[20:33] <QuintasanDroid> lol
[20:34] <QuintasanDroid> yofel: I got 7 errors on memtest
[20:34] <QuintasanDroid> is it bad?
[20:34] <yofel> well, any memory damage has potential of kernel doing nonsense and the filesystem writing crap to the disk
[20:34] <QuintasanDroid> it cant be repaired?
[20:34] <QuintasanDroid> :/
[20:34] <QuintasanDroid> memory dying after one year
[20:34] <QuintasanDroid> wtf
[20:35] <ScottK> Memory is not the place to try and save money on a system.
[20:35] <yofel> not that I know of, I encountered the same case at a friends laptop, he thought he had a virus in windows until I ran memtest from a usb stick ^^
[20:35] <QuintasanDroid> I did not save money on them
[20:35] <QuintasanDroid> I did not save money on any part of that computer
[20:35] <ScottK> Doubly unfortunate then.
[20:36] <QuintasanDroid> yet it breaks down :S
[20:36] <ScottK> Still under warranty?
[20:36] <yofel> thankfully it was a simply 1GiB DIMM
[20:36] <QuintasanDroid> ScottK: no idea, I'll have to look for the whole box
[20:36] <yofel> *simple
[20:36]  * QuintasanDroid put all papers inside
[20:36] <QuintasanDroid> if its gone then Ill have to buy new ones
[20:37] <QuintasanDroid> oh well, I am going to bed
[20:37] <QuintasanDroid> good night
[20:37] <yofel> well, memory is affordable today. Be thankful you don't need to go back to year 2000 and get a 32MiB DIMM of EDO RAM
[20:37] <yofel> and gone..
[21:21] <ScottK> debfx: libdlrestrictions1 and libdlrestrictions-dev promoted.  So we should get a kde4libs build starting in 80 minutes.
[23:00] <ScottK> kde4libs building now.
[23:28] <debfx> yay


[00:00] <sinzui> wallyworld_, wgrant. yes it is my fault https://lpbuildbot.canonical.com/builders/lucid_lp/builds/1647/steps/shell_6/logs/summary
[00:01] <wallyworld_> sinzui: np. i'll fix
[00:01] <wgrant> Were the two branches landed in the wrong order?
[00:01] <sinzui> wgrant, bingo
[00:01] <wallyworld_> so no fix required, just restat bb?
[00:01] <wallyworld_> restart
[00:01] <sinzui> but they are both in place I  think, but they were landed independent too
[00:01] <wallyworld_> so it's my fault for messing up the dependencies :-)
[00:02] <wgrant> I guess run the tests locally to confirm.
[00:02] <wallyworld_> i had to resubmit both mps due to the first failure
[00:02] <wallyworld_> and something messed up i guess
[00:02] <sinzui> wallyworld_, we want to move account status to IPersonPublic...
[00:03] <wallyworld_> sinzui: from iPersonRestrictedView from memory
[00:03] <sinzui> this is another case were I considered placing it there since teams do not have accounts, then thought no, I do not want to clutter the interface
[00:03] <wallyworld_> oh for person and team to be separated properly
[00:05] <sinzui> wallyworld_, iPersonRestrictedView probably work, I was thinking public based on a from a discussion with flacoste. Public are attrs that are obvious from the knowledge that the team exists. It is as team, it is valid, and it does not have accounts (in this case)
[00:05] <wallyworld_> sinzui: just looked at the stdout - ec2 did indeed flag the tests as failing i think
[00:06] <wallyworld_> sinzui: i agree with the rationale you just outlined. IPersonPublic seems thebest place i think
[00:06] <sinzui> yep, I was watching buildbot independent of wgrant since I believed the issue was a cause by the branch landing before its dep
[00:07] <wgrant> sinzui, wallyworld_: It needs to public.
[00:07] <wgrant> Otherwise traversal to a private team will 403 instead of 404.
[00:08] <wallyworld_> sinzui: so given there's a code change, can i just to a testfix and lp-land, or do i need to rollback and do the ec2 dance again?
[00:08] <sinzui> land it as a testfix, but you need to do it after the failure
[00:08] <wallyworld_> please don't make me rollback again :-)
[00:08] <wallyworld_> sure
[00:09] <sinzui> buildbot does not notice a pre-emptive testfix :(
[00:09] <wallyworld_> understood. the wait will give me time to get it prepared
[00:09] <wgrant> sinzui: It should notice it.
[00:09] <sinzui> wallyworld_, and pqm-submit it
[00:09] <wallyworld_> sinzui: yes, i just do a bzr lp-land in such cases
[00:09] <wgrant> Even if it doesn't, you can just force.
[00:09] <sinzui> wgrant, I tried a preemptive fix a few months ago and it did not work
[00:10] <wgrant> sinzui: Hmm.
[00:10] <wallyworld_> wgrant: aren't you meant to be awol?
[00:10] <wgrant> sinzui: You have to add [no-qa], but it should work.
[00:10] <sinzui> wgrant, noted
[00:10] <mwhudson> wallyworld_: i don't think it's possible to be meant to be awol :)
[00:11] <wallyworld_> mwhudson: semantics!
[00:11] <mwhudson> wallyworld_: yes!
[00:11] <mwhudson> (sorry)
[00:11] <wallyworld_> i was being very lose with my use of the english language :-)
[00:11] <wallyworld_> no need to apologise, i'm normally a stickler for that sort of thing
[00:12] <wallyworld_> eg i HATE how the word "decimate" is misused all the time
[00:13] <sinzui> wallyworld_, once the tests are fixed, you can do this to skip the 4-6 hours in ec2: http://pastebin.ubuntu.com/768498/
[00:13] <wallyworld_> sinzui: bzr lp-land does the same thing :-)
[00:13] <sinzui> I did not know
[00:13] <mwhudson> wallyworld_: you are an epicentre of linguistic correctness!
[00:13]  * mwhudson hides
[00:14]  * wallyworld_ lols
[00:14] <sinzui> anything else I need to know wgrant, wallyworld_. Perhaps something about how to make buildbot complete in 1 hour?
[00:14] <wallyworld_> mwhudson: i bet you can't say that last sentence you just typed 10 times quickly :-D
[00:15] <wallyworld_> sinzui: the parallelisation of the test suite should help :-P
[00:15] <sinzui> PS. when I say awesome, Id not not mean as in hotdogs with mustard, I mean god-fearing awe
[00:18] <wallyworld_> noted :-)
[00:18] <StevenK> sinzui: Removing 80% of the test suite would get buildbot to an hour.
[00:19] <wallyworld_> i reckon the layer startup/teardown times contribute to a large slice of the time taken too, no?
[00:20] <lifeless> over the whole test suite, not so much
[00:20] <StevenK> Like 6 minutes of 4+ hours?
[00:20] <lifeless> the per-test setup/teardown overheads are pretty large though
[00:20] <wallyworld_> yes :-(
[00:23] <wallyworld_> sinzui: i think account_status_comment should also move, just to keep it with account_status. agree?
[00:23] <wgrant> "Total duration of profiled methods 3152.6 seconds."
[00:24] <wgrant> So there's only a little under an hour of layer (test)?{setup,teardown}
[00:24] <wgrant> DatabaseLayer.testTearDown                    13721 calls taking 2051.7s.
[00:24] <StevenK> An hour of setup and teardown? Faaaark
[00:25] <StevenK> 35 minutes removing and creating databases. Thanks lifeless.
[00:25] <wgrant> Not lifeless' fault.
[00:25] <wgrant> He only changed the names.
[00:25] <StevenK> Aw
[00:25] <wgrant> And added an extra template.
[00:25] <wallyworld_> StevenK: that setp/teardown is what i was alluding to earlier
[00:46] <huwshimi> erm http://blog.launchpad.net/
[02:55] <wallyworld_> lifeless: private team. i am the owner. i make someone else the owner, but in so doing i cannot see the team anymore. so at the end of the process, the owner has changed but i see a "you are not authorised" page. should we display a one-off "this has succeeded but you cannot see the team anymore" page?
[02:57] <wallyworld_> btw, this is after a change to allow owners to view the private team even if they are not members
[03:00] <lifeless> wallyworld_: just show the page normally; same as for bugs
[03:00] <lifeless> wallyworld_: erm, or actually, just redirect to launchpad.net/
[03:00] <lifeless> wallyworld_: perhaps with a notification explaining why
[03:00] <wallyworld_> lifeless: right. good idea. thanks
[03:06] <StevenK> So I have a private team. I have invited a public team to be a member. That should show up as a pending invitation, should it not?
[03:12] <wallyworld_> StevenK: i would have thought so
[03:13] <wallyworld_> what does it do in actuality?
[03:13] <wallyworld_> bear in mind i've discovered a few things today about team behaviour by reading to code so my knowledge is patchy
[03:14] <StevenK> wallyworld_: It doesn't seem to show it at all
[03:15] <StevenK> I'm wondering if that is expected before I dive into our security adapter
[03:15] <wgrant> It's expected.
[03:15] <lifeless> if the private team invites a public team, the private team should be listed on the public teams invitations list.
[03:15] <wgrant> Only members, private PPA subscribers and Launchpad admins can see private teams.
[03:15] <wgrant> That's changing.
[03:16] <lifeless> it won't be showing today, but it it should. :)
[03:16] <lifeless> there is a bug for this
[03:16] <wgrant> lifeless: But only shown to the public team's admins?
[03:16] <lifeless> right
[03:16] <lifeless> optional the public teams members too
[03:17] <lifeless> but not to the general public
[03:17] <wgrant> Right, which is not what you said :)
[03:17] <lifeless> (by optionally, I mean whatever falls out of the code cleanest)
[03:17] <lifeless> wgrant: EBRAINISTOAST
[03:17] <wgrant> Yeah.
[03:17] <lifeless> my config change has landed
[03:18] <lifeless> \o./
[03:18] <wallyworld_> ii thought when StevenK said "pending invitation" it mean that the private team would see a list of invitees who had not accepted yet. but is it the other way around?
[03:18] <wgrant> But you've seen what happens when one doesn't make completely unambiguous statements about privacy.
[03:18] <lifeless> hilarity?
[03:18] <wgrant> Pretty much.
[03:18] <lifeless> wallyworld_: both directions gain visibility
[03:19] <wallyworld_> ok
[03:20] <lifeless> slightly different rules about who sees what
[03:20] <lifeless> members can see superteams
[03:20] <lifeless> admins can see subteams
[03:20] <lifeless> something mumble mumble
[03:20] <lifeless> there is a bug
[03:23] <wallyworld_> several perhaps
[03:27] <StevenK> wgrant: Okay, so I'm seeing expecting behaviour -- I can test for it, or I can fix it.
[03:31] <StevenK> lifeless: ^
[03:32] <lifeless> EPARSE
[03:33] <wgrant> lifeless =1
[03:33] <wgrant> +1
[03:34] <nigelb> wgrant: Did you just reassign lifeless? :P
[03:34] <nigelb> Also, Morning!
[03:34] <wgrant> A regrettable mistake.
[03:34] <wgrant> Afternoon.
[03:34] <StevenK> wgrant: So, fix it?
[03:34] <wgrant> StevenK: I don't understand what you mean.
[03:35] <StevenK> wgrant: So, I have two choices. I can test that the current behaviour is correct. Or, I can fix it so that pending private teams are shown to the team admins and write tests for that case.
[03:36] <wgrant> Or you can leave the behaviour undefined until we finish defining the complete set of new private team behaviours.
[03:36] <StevenK> No test at all?
[03:36] <StevenK> Fair enough.
[03:37] <StevenK> This branch should fix the Person:+index MixedVisibilityErrors as it stands.
[03:43] <StevenK> Guido van Rossum  -  11:05 AM (edited)  -  Public
[03:43] <StevenK> Why do Python classes have both _mro_ and mro() ? What was I thinking at the time? Does anyone remember?
[03:43]  * StevenK laughs.
[04:35]  * StevenK breaks buildbot into small pieces
[05:00] <StevenK> Can haz review? https://code.launchpad.net/~stevenk/launchpad/person-index-mixed-visibility/+merge/85427
[05:36] <wallyworld_> StevenK: looking now
[05:38] <wallyworld_> StevenK: you should use  "if check_permission('launchpad.LimitedView', team)" in your super_teams method
[05:39] <wallyworld_> since this by default delegates to launchpad.View
[05:39] <wallyworld_> and is the required permission to know of a team's existence
[05:39] <StevenK> Why LimitedView?
[05:39] <wallyworld_> with LimitedView, a user can know of a team's existence and name, displayname etc
[05:39] <wallyworld_> but not any other private details
[05:40] <wallyworld_> so for bug subscribers etc, i precache launchpad.LimitedView permissions
[05:40] <StevenK> But these are super teams -- teams that the team in question is a member of
[05:40] <wallyworld_> ah, ok
[05:40] <StevenK> If you can see the team, you can see everything, so .View is the right choice
[05:40] <wallyworld_> yes, sorry. i think you are right
[05:41] <wallyworld_> so what was the issue before your branch?
[05:42] <StevenK> wallyworld_: People would see <public team>, <hidden>, <hidden>, <public team>
[05:42] <StevenK> When I added MixedVisibilityError, those <hidden> started raising them
[05:42] <wallyworld_> if the team in question (the one being viewed) is a member of those <hidden> teams, why weren't they visible?
[05:43] <StevenK> The person viewing the team page may not have permission to see the team
[05:43] <StevenK> But members of the team view their own page do.
[05:44] <wallyworld_> ok, so the user is viewing a public team that may be a member of a private team?
[05:44] <wallyworld_> and the user may not be able to see that private team
[05:44] <wallyworld_> ?
[05:44] <wallyworld_> so in that case we would render <hidden>?
[05:45] <StevenK> And raise a MixedVisibilityError, yes.
[05:45] <wallyworld_> if my assertions above are correct, i do think we should be using LimitedView permissions then
[05:45] <StevenK> The formatter uses View, and gives a link
[05:46] <wallyworld_> since moving forward, we will be looking to allow a user to view the existence of a private team that is in any public relationship the user can see
[05:46] <wallyworld_> the formatter should change to use limitedview
[05:46] <StevenK> And not link them?
[05:47] <wallyworld_> limitedview by default just delegates to view, so it's the same net effect
[05:47] <wallyworld_> they should still be linked
[05:47] <StevenK> And the user gets a 404 when they click the link?
[05:47] <wallyworld_> but for now, if a user with just limitedview clicks on the links, they get a 404
[05:47] <StevenK> That's what I'm trying to prevent
[05:47] <wallyworld_> we are yet to solve that one
[05:48] <wallyworld_> there's 2 issues - not rendering <hidden>, and making the link work
[05:48] <StevenK> Besides, the private team isn't in a public position
[05:48] <StevenK> It just has a public team as a member
[05:48] <StevenK> It doesn't have to be disclosed by that action
[05:48]  * wallyworld_ thinks
[05:49] <wallyworld_> which is different to a private team subscribing to a bug? yes, perhaps?
[05:49] <wallyworld_> or maybe not, since members of the public team should be able to know who the parent team is?
[05:49] <StevenK> It is, yes
[05:50] <wallyworld_> ok, so let's leave it as view for now and we can revisit later if required?
[05:51] <StevenK> I'm happy with that
[05:51] <wallyworld_> thought you'd say that :-)
[05:51] <wallyworld_> i thought it better to ask the question though just in case....
[05:51] <lifeless> or clarity 'disclosed' is -always- contextual
[05:52] <lifeless> you can disclose to the public, disclose to a team, disclose to project etc
[05:52] <wallyworld_> so here we are possibly disclosing to a team i guess
[05:54] <lifeless> anytime in a discussion if someone says 'disclose' unconditionally, you all have to drink.
[05:54]  * StevenK finishes his glass of water
[05:54] <StevenK> Is that what you had in mind?
[05:54] <StevenK> lifeless: What time is your flight, out of interest?
[05:55] <lifeless> StevenK: tomorrow?
[05:55] <StevenK> lifeless: Yah
[05:56] <lifeless> 0955 departure
[05:56] <lifeless> but I route via akl
[05:56] <lifeless> I arrive 1430
[05:56] <StevenK> It's what, 30 minutes to AKL?
[05:56] <lifeless> at which point I will be tearing vodafone a new hole amongst other .au business
[05:56] <StevenK> ... why?
[05:57] <lifeless> because, a year after I closed my postpay account with them and moved countries, they started emailing me invoices
[05:57] <StevenK> Haha
[05:57] <lifeless> now, 1 month after, I could understand, and would have paid without much thought.
[05:57] <lifeless> a year later? WTF.
[05:57] <lifeless> actually 14 months or some odd number.
[05:57] <lifeless> Anyhow, lots.
[05:58]  * lifeless is extremely unimpressed
[05:58] <lifeless> I woul dhave rung from here, but their phone system is worse than loading a 3d game on a 16Kb spectrum
[05:58] <lifeless> I didn't want to use all my skypeout credit for a year while on hold
[05:59] <wallyworld_> StevenK: with the test_private_superteams_shown() test, i'd like to see another team created that would be <hidden> but is filtered out, since the other tests simply check if the portlet is there or not
[06:00] <wallyworld_> i guess the tales does that though
[06:00] <wallyworld_> ie indirectly tests that code path
[06:00] <StevenK> lifeless: When I moved to Parramatta, I called Telstra and cancelled the landline service, as well as getting a new service for the new place. Fast forward two months, and I get a bill for the landline at the old place, filled with calls after I moved out.
[06:00] <lifeless> StevenK: win
[06:01] <StevenK> lifeless: I rang up and said "Please explain" and was told that they "forgot" to action my cancelation
[06:01] <StevenK> As way of apology, they wrote off the entire bill, which had one charge for the new landline on it.
[06:02] <StevenK> wallyworld_: So the TALES won't even show the portlet if there are no visible super teams
[06:02] <wallyworld_> StevenK: yes, i came to that conclusion too so i think it's ok
[06:03] <wallyworld_> StevenK: for a "proper" unit test, the super_teams() property on the view object really should be tested
[06:04] <wallyworld_> rather than relying on the template logic to indirectly test it
[06:04] <StevenK> wallyworld_: I'm happy to add an assert for that
[06:04] <StevenK> self.assertEqual([], view.super_teams) effectivelty
[06:04] <StevenK> *effectively
[06:04] <wallyworld_> StevenK: that would be great; hopefully there's an existing unit test for the view object you can add to simply
[06:05] <wallyworld_> ah, yes, that works too
[06:06] <wallyworld_> StevenK: r=me
[08:41] <cjwatson> wgrant: P-a-s> ah, OK, thanks.  Maybe if I get some time over the holidays ...
[08:42] <wgrant> cjwatson: That's likely the only way it's going to get fixed unless I get bored, yeah.
[08:42] <wgrant> :/
[08:57] <adeuring> good morning
[09:10] <mrevell> Mornin;
[09:11] <mrevell> oh, I fail at typing
[10:14] <jtv> allenap: ndt deployment request underway.  Liam is on it.  Thanks for dealing with that branch.
[10:15] <allenap> jtv: Tip top, ta :)
[11:36] <cjwatson> oh my, I didn't realise that maintenance-check.py relied on http://people.canonical.com/~ubuntu-archive/germinate-output/
[11:37] <cjwatson> I think I'll need to convert that to python-germinate as well for sanity and testability
[12:30] <cjwatson> bigjools: is it possible that r11088 fixed bug 599412?  It looks as though it ought to have done
[12:30] <_mup_> Bug #599412: populate-archive --component main doesn't work <derivation> <lp-soyuz> <Launchpad itself:Triaged> < https://launchpad.net/bugs/599412 >
[12:35] <bigjools> cjwatson: yes, the commit msg says so :)
[12:35]  * bigjools fixorates
[12:36] <cjwatson> refers to bug 600165 instead, actually, so unnoticed dup
[12:36] <_mup_> Bug #600165: COPY archive creation ignores the specified component <derivation> <lp-soyuz> <qa-ok> <Launchpad itself:Fix Released by julian-edwards> < https://launchpad.net/bugs/600165 >
[12:37] <bigjools> yeah
[12:37] <bigjools> thanks for noticing
[12:37]  * cjwatson has been looking through soyuz bugs for things that might improve Ubuntu's life that are accessible to me to fix
[12:38] <bigjools> sounds like you need a rotation :)
[12:39] <cjwatson> the thought has crossed my mind, but I think I want to remain focused on things specifically beneficial to Ubuntu rather than LP as a whole; plus Steve might object :)
[12:39] <cjwatson> might consider it in a year or so
[12:48] <StevenK> cjwatson: I won't object, but I know you don't mean me. :-)
[13:11] <jtv> StevenK: actually I was wondering why you would ever object!
[13:11] <jtv> So a good thing you said it.
[13:18]  * cjwatson tests germinate 2.3 on mawson and confirms that the only differences are as expected
[13:19] <cjwatson> so I've followed up to that ticket to say that it's OK to upgrade cocoplum/germanium
[13:20] <cjwatson> jtv: can https://code.launchpad.net/~cjwatson/launchpad/refactor-cron-germinate/+merge/84624 be Status: Approved as well as having your Approved review?  It's still waiting on a buildbot upgrade before we can land it, but apart from that ...
[13:24] <jtv> cjwatson: coming
[13:25] <jtv> cjwatson: done
[13:29] <sinzui> I think I need to rollback 3 non-sequential revisions :(
[13:30] <cjwatson> jtv: ta
[13:33] <jtv> bigjools, wgrant: care to review?  https://code.launchpad.net/~jtv/launchpad/bug-903688/+merge/85485
[13:40] <bigjools> jtv: I can
[13:40] <jtv> That'd be great, thanks
[13:59] <jtv> Anyone know why I would get this error during "make schema" on a db-devel branch?  duplicate key value violates unique constraint "launchpaddatabaseupdatelog_pkey"
[14:03] <nigelb> someone broke something?
[14:03] <nigelb> I hope no one broke sampledata.
[14:04] <jtv> nigelb: maybe I did — don't know.
[14:04] <jtv> But I re-generated the updated sampledata based on db-devel sampledata, and it doesn't help.
[14:06] <jelmer> benji: hi
[14:06] <benji> hi jelmer
[14:07] <jelmer> benji: Are you still working on bug 808930 ?
[14:07] <_mup_> Bug #808930: Timeout running branch scanner job <escalated> <linaro> <oops> <Launchpad itself:In Progress by benji> < https://launchpad.net/bugs/808930 >
[14:07] <jelmer> I've got a bug fix in that area, and I'd like to make sure our changes don't clash.
[14:07] <benji> jelmer: gmb has taken the helm of that one
[14:07]  * benji goes to fix the assignee in LP.
[14:07] <jelmer> gmb: Hey!
[14:07] <jelmer> benji: thanks
[14:08] <benji> np
[14:08] <gmb> jelmer: Hi. I'm only just getting up to speed on this bug, so it may well be that I have to tap on benji's shoulder a couple of times. But anyway.
[14:09] <jelmer> gmb: ok
[14:09] <jelmer> gmb: I've got a fix for the branch scanner which should at least make the bzr part of things no longer O(size-of-branch-history)
[14:10] <jelmer> gmb: that should help with the bug, but it will also likely clash with any changes you've already made
[14:10] <gmb> jelmer: Okay. So, I'd be inclined to tell you to get your branch landed; I'm not ready to land anythign yet, so I'm happy to clean up any clashes.
[14:11] <jelmer> gmb: Great, thanks.
[14:11] <jtv> Anyone know what would make a "make schema" on a db-devel branch violate unique constraint launchpaddatabaseupdatelog_pkey?
[14:13] <abentley> deryck: Do you think now is the right time to generalize ListingNavigator as we discussed with wallyworld?
[14:14] <deryck> abentley, jumping on call…. give me a minute to think about that.
[14:14] <abentley> deryck: sure.
[14:21] <deryck> abentley, I'm sorry, but I'm blanking on remembering the discussion with wallyworld_.  is this an email discussion?
[14:22] <abentley> deryck: Yes.  Let me see if I can dig up the subject.
[14:22] <abentley> deryck: "batch navigation question"
[14:23]  * deryck is looking at email
[14:24] <deryck> abentley, ok, right.  I absolutely think now is the time to do that work.
[14:24] <abentley> deryck: cool.
[14:26] <deryck> there are a couple minor bugs we still need to fix, but these are fairly shallow.  I may see if rick_h_ can be enlisted for this, to keep you free for this.
[14:27] <stub> (21:21:48) stub: jtv: Hmm... might need to add a step to reset the sequence.
[14:27] <stub> (21:22:19) stub: jtv: The value of the sequence would have been set from production with the new baseline?
[14:27] <stub> (21:24:45) stub: jtv: Although 'make schema' shouldn't care because the table will be empty...
[14:27] <stub> (21:25:24) stub: jtv: Have you rebuilt sample data and ended up with the contents of launchpaddatabaseupdatelog in it? That would make it explode (and would be a bug - need to exclude that table from sampledata too, along with launchpaddatabaserevision)
[14:28] <nigelb> wow. I did guess right. sampledata has some brokeness.
[14:30] <jtv> stub: yes, on two occasions I did “make newsampledata” and both times got 1 record for launchpaddatabaseupdatelog per database.
[14:30] <jtv> I'm about to try it with an unmodified db-devel schema.
[14:31] <stub> thought the sequence reset magic would take care of it?
[14:32] <jtv> Frankly I can't even find where the table gets created.
[14:32] <jtv> Whoops — the sampledata I build from db-devel is broken.
[14:33] <stub> jtv: The table is in the db baseline - launchpad-2209-00-0.sql
[14:34] <jtv> Looked there.  It's basically empty.
[14:34] <jtv> I figured the guts had moved somewhere else.
[14:36] <jtv> stub: broken baseline?
[14:36] <jtv> I thought the baseline used to be in that patch — but now I don't see that for 2208 either.
[14:37] <jtv> Ah wait — launchpad-2209-00-0.sql.  I was looking at patch-2209-00-0.sql.
[14:37] <stub> If you are on db-devel, 2208 shouldn't exist
[14:37] <stub> yer
[14:39] <jtv> I was just cross-checking with devel.
[14:42] <jtv> stub: fwiw I also looked for launchapddatabaseupdatelog in the sample data for devel & db-devel and did not find any mention.
[14:44]  * stub waits for trees to sync
[14:53] <jtv> bigjools: my buildfarm fix has passed soyuz & buildmaster tests.  Think that's enough for a landing?
[14:53] <bigjools> jtv: yes
[14:53] <jtv> Yee-haw.
[14:53] <bigjools> well - code perhaps
[14:54] <jtv> OK, running that too.
[15:01] <stub> jtv: So with a fresh tree and make schema, I get LaunchpadDatabaseUpdateLog with one entry with id 1 (from patch-2209-00-2.sql) and nextval('launchpaddatabaseupdatelog_id_seq') is 2.
[15:02] <jtv> I get the entry; haven't tried the sequence.
[15:02] <jtv> Presumably that's the part that's wrong.
[15:02] <jtv> But didn't you say that the table shouldn't be in the sample data at all?
[15:04] <stub> jtv: There is no need for it to be there.
[15:04] <jtv> Then how did it get there?
[15:05] <stub> jtv: I neglected to add it to the blacklist filter in database/schema/Makefile.
[15:05] <jtv> Is that something you could fix at the moment?
[15:05] <stub> sure
[15:06] <stub> jtv: So patches get applied, then we load sampledata. And if the sampledata contains rows they will conflict with any created by upgrade.py
[15:06] <sinzui> bac: gary_poster is it time to discuss milestones?
[15:07] <bac> sinzui: yes, sorry, our call ran long.  i'll skype you now
[15:07] <jtv> stub: thanks for working it out.  Got branches blocked on this, and tomorrow's my last day for the year.
[15:09] <stub> http://paste.ubuntu.com/769038/ should be the fix
[15:09] <stub> jtv: Want me to land that?
[15:10] <jelmer> gmb: actually, looking at the only OOPS for bug 808930 that I can find, it seems like that is in the access of the bzr graph
[15:10] <_mup_> Bug #808930: Timeout running branch scanner job <escalated> <linaro> <oops> <Launchpad itself:In Progress by gmb> < https://launchpad.net/bugs/808930 >
[15:10] <jtv> stub: yes please, assuming it's correct.  :)
[15:10] <jtv> stub: is the whitespace you removed significant?
[15:10] <gmb> jelmer: benji's theory, AIUI, is that the OOPS is a death-by-SQL problem.
[15:11] <stub> jtv: You can apply that locally and rebuild your sampledata while waiting to confirm (and even revert the change afterwards - the problem with your branch is the generated sampledata and you can land it without the makefile fix)
[15:11] <jtv> Right.  I'll try that.
[15:11] <gmb> jelmer: So I'm not sure whether your fix will help or not...
[15:11] <jelmer> gmb: yeah, that seems like the most likely cause indeed.. storing a giant (HUUUUGE) graph in a SQL table seems like a bad idea
[15:11] <stub> jtv: Seems to be working. I'll do a self approved landing now.
[15:12] <gmb> jelmer: Ssssh, you'll make whoever came up with that idea feel silly....
[15:12] <sinzui> bac: https://launchpad.net/glade/3.10
[15:12] <sinzui> bac: https://launchpad.net/grub/grub2
[15:13] <jelmer> gmb: IIUC it's that way because that's how bzr originally behaved
[15:14] <gmb> Yeah, I think that's the case.
[15:15] <jelmer> gmb: I'm sure you've seen https://dev.launchpad.net/Code/BranchRevisions ?
[15:16] <gmb> jelmer: Yes, I had. (I had repressed it)
[15:16] <jelmer> hehe
[15:16] <sinzui> bac: lifeless reported this https://bugs.launchpad.net/launchpad/+bug/644977
[15:16] <_mup_> Bug #644977: ProjectMilestone is inconsistent, confusing ui, can we just delete it? <confusing-ui> <lp-registry> <Launchpad itself:Triaged> < https://launchpad.net/bugs/644977 >
[15:18] <rick_h_> benji: ping, have some time to do a voice chat on an api bug: https://bugs.launchpad.net/launchpad/+bug/808952
[15:18] <_mup_> Bug #808952: NoCanonicalUrl using api to fetch bug comments <api> <oops> <Launchpad itself:Triaged by rharding> < https://launchpad.net/bugs/808952 >
[15:18] <allenap> gmb: Got time for a tiny review? https://code.launchpad.net/~allenap/launchpad/bugnomination-timeout-bug-874250-heat-death/+merge/85497
[15:18] <gmb> allenap: Sure thing
[15:18] <allenap> Ta
[15:18] <benji> rick_h_: sure.  Skype?
[15:19] <rick_h_> benji: sure, mitechie is my username
[15:19] <benji> rick_h_: calling
[15:24] <jelmer> gmb: Do you have time to review that avoid-revision-history branch? It should now be up at https://code.launchpad.net/~jelmer/launchpad/avoid-revision-history-2/+merge/85501
[15:25] <gmb> jelmer: I'll take a look once I've finished with allenap's.
[15:29] <jtv> stub: I seem to have working sample data now, thanks
[15:30] <stub> np. by branch has landed too.
[15:56] <sinzui> bac: https://launchpad.net/launchpad-project/+milestones is a mess
[15:56] <sinzui> while your idea is about declaring them to prevent the cruft from appears
[16:05] <jelmer> gmb: Merci
[16:06] <gmb> jelmer: De rien.
[16:26] <jtv> bigjools: lot of blockers on the deployment report tonight.  If we're going to get my fix out, looks like we'll have to cowboy.
[16:26] <bac> sinzui: regarding vouchers, the API they provide is not showing you having anything, which is consistent with the db dump neil provided.  so it looks like a problem between the shop and salesforce
[16:27] <sinzui> bac: I was replying to that. I was even going to take a screencap of a check out, but I cannot do that at the moment.
[16:27] <bac> sinzui: i'll buy some too and see if they materialize
[16:28] <sinzui> Maybe the ridiculous free gift has broken checkout for users that redeem vouchers
[16:47] <jtv> bigjools: arrrrgh.  Broken test in archiveuploader.  The ordering of a two-item recipients list on a notification email has changed.  :(
[16:47] <bigjools> hmmm
[16:47] <bigjools> sounds spurious, which is worse
[16:48] <jtv> Oh, yes it is worse: I was accidentally running that one on devel!
[16:48] <jtv> lp.archiveuploader.tests.test_uploadprocessor.TestUploadProcessor.testUploadToFrozenDistro
[16:53] <bigjools> yay?
[16:56] <jtv> bigjools: is that the sort of yay that conveys no joy at all?
[16:56] <bigjools> jtv: Archeryay
[16:57] <jtv> Ah, _that_ yay
[16:57] <jtv> Absolutely correct.
[17:02] <rick_h_> deryck: I've gotten this the last two times I tried to land the inline editor stuff: +bzr+ssh://bazaar.launchpad.net/~launchpad-pqm/launchpad/devel
[17:03] <rick_h_> deryck: the test email comes back success, but that's the PQM test email?
[17:03] <rick_h_> deryck: sorry, bad paste https://pastebin.canonical.com/57048/
[17:03] <deryck> rick_h_, you need to look at the log file attached to the email from pqm.
[17:04] <deryck> rick_h_, either testfix or merge conflict most likely.
[17:04] <rick_h_> deryck: my bad, totally missed the attachments
[17:04] <deryck> given buildnot's record, you can guess what you'll get ;)
[17:05] <rick_h_> ah, actually getting that it doesn't like my commit message. Will check it out then. Thanks, blind today
[17:15] <deryck> rick_h_, can you look into bug 894726?  Should be trivial to linkify the tags listed.
[17:15] <_mup_> Bug #894726: Tags not linked on bug listing <bug-columns> <Launchpad itself:Triaged> < https://launchpad.net/bugs/894726 >
[17:16] <rick_h_> deryck: sure thing
[17:17] <deryck> mrevell, for that bug ^^ do you care if we just link to the tag list from the new feature lists?
[17:17] <deryck> rick_h_, that's what I'm thinking, a simple link, rather than all the fancy filtering talk in the bug.
[17:17] <rick_h_> deryck: ah ok. Yea I was thinking that it's a bit more to do that.
[17:18] <sinzui> bac, did you succeed in checking out?
[17:19] <cjwatson> jtv: oh!  good, it's yay for me, it means that it isn't the fault of my new-python-apt branch
[17:19] <deryck> rick_h_, the link is just "?field.tag=$TAGNAME" -- though we *may* have some helper method to get you the link.
[17:19] <rick_h_> deryck: ok, I'm finishing getting my notes together for this bug report and I'll peek at it in a few
[17:20] <cjwatson> jtv: soyuz-set-of-uploads and xx-queue-pages fail for the same reason, and are harder to work around since they're doctests.
[17:20] <deryck> rick_h_, ok, thanks!
[17:20] <jtv> cjwatson: I fixed the test that broke for me.  With doctests I usually just sort to get deterministic output.
[17:23] <jtv> bigjools: I also ran tests for translations and archiveuploader, since they had (mentions of) BuildFarmJob.  Still, having that one test fail made me nervous about landing without waiting for the outcome of the full test run.
[17:23] <deryck> rick_h_, I'm also going to assign bug 894740 to you.  Should be a shallow js error fix.
[17:23] <_mup_> Bug #894740: bug heat contextual help opens in a new tab in chromium <bug-columns> <exploratory-testing> <regression> <ui> <Launchpad itself:Triaged> < https://launchpad.net/bugs/894740 >
[17:24] <rick_h_> deryck: sounds good
[17:31] <cjwatson> jtv: yeah, it's just awkward in this case since the doctests are testing the entire formatted e-mail
[17:31] <deryck> adeuring, do we have a bug yet for the "only showing one order by button" bug?
[17:31] <bac> sinzui: trying now
[17:33] <rick_h_> deryck: benji just fyi, summary of the findings: https://bugs.launchpad.net/launchpad/+bug/808952
[17:33] <_mup_> Bug #808952: NoCanonicalUrl using api to fetch bug comments <api> <oops> <Launchpad itself:Triaged> < https://launchpad.net/bugs/808952 >
[17:35] <mrevell> deryck, re tags: Yeah, that seems like a good solution.
[17:35] <deryck> mrevell, thanks!
[17:40] <bac> sinzui: did you report the broken checkout?  mine broke too
[17:46] <adeuring> deryck: no, not yet, but I'll file one
[17:50] <deryck> adeuring, thanks!
[17:56] <cr3> is it supposed to take a while, like hours, after stopping emails for a subscription to actually stop receiving mail from that subscription?
[18:05] <lifeless> cr3: it could, under exceptional circumstances. More likely is that you have multiple subscription paths to the mails you are getting
[18:05] <jtv> cjwatson: got another spurious failure — archivesubscription-views.txt.  What happened?
[18:06] <cr3> lifeless: I've been cross checking with the Launchpad-Rationale in the email header, so I think I have the multiple subscription problem down. I'll be a bit more patient and check again tomorrow
[18:07] <cjwatson> jtv: that's odd, I don't think I got that failure and I ran all the soyuz tests
[18:09] <deryck> abentley, adeuring, rick_h_ -- FWIW, I'm done with looking over the bugs again (boy, did that take longer than expected!)
[18:09] <deryck> abentley, adeuring, rick_h_ -- and short of a few little UI issues that are easy to fix, we're in pretty good shape.
[18:09] <abentley> deryck: Yes, I agree.  Looked over them yesterday myself.
[18:09] <jtv> cjwatson: I'm not getting it on my local system either, or running just the soyuz tests in EC2.  Sounds like isolation problem.
[18:10] <abentley> deryck: A lot of the bugs are $foo is not linked.  Do we know if we actually want to link everything?
[18:12] <deryck> abentley, I don't think we know, so those are all marked low, except the tags one.  I don't think we should worry about them, unless mrevell and company have design ideas.
[18:12] <deryck> abentley, as I understand it, product team pushed back on linking everything, not knowing how to style the links.
[18:16] <benji> rick_h_: was eating lunch, looking now
[18:18] <rick_h_> benji: np, let me know if you think I should add anything else. Basically the type of object going in there was just Message and nothing else like I had hoped
[18:19] <jtv> bigjools: I landed my fix on devel as revision 14499.  But there's some real weirdness going on: a test that shouldn't have been affected failed for me once in EC2, and I can't seem to reproduce it.  I'll need to pack it in for the night though.
[18:19] <benji> rick_h_: so which branch in message_to_canonical_url_data is taken?
[18:19] <rick_h_> benji: it's the bugs.count() branch
[18:20] <rick_h_> benji: IMessage has a bugs property
[18:20] <bigjools> jtv: ok, get some sleep, rest well
[18:21] <jtv> thanks, see you tomorrow!
[18:22] <benji> rick_h_: so... the message isn't associated with a bug?  That seems strange.
[18:22] <sinzui> benji, that is historic cruft I think
[18:23] <rick_h_> benji: right, most messages are extended and assiciated through a tying table, bugmessage, butattachment do the tying to a bug
[18:23] <rick_h_> benji: but these are just plain messages created for the record it appears
[18:25] <benji> hmm, if we can figure out a way for message_to_canonical_url_data to figure out which bug is related then it could return an BugMessageCanonicalUrlData instance and all would be right with the world
[18:36] <abentley> benji: these messages aren't bug comments.  Are you sure they have (or should have) URLs?
[18:37] <benji> abentley: they don't now, but exposing them to the REST API may be the thing to do to fix this bug
[18:38] <rick_h_> abentley: benji yea, I mean they are messages viewable via the web and while not bug comments, might be useful/might expose kind of things
[18:38] <abentley> benji: I don't think we really want to track all the notifications that e.g. a bug status changed in the API.
[18:39] <benji> abentley: you might be right; in that case we'll have to figure out how to hide the notifications from the part of the API that can "see" them now (which is the source of the bug rick_h_ is working on)
[19:23] <bigjools> webops: when qastaging updates, does the bzr server restart? I already established that the librarian does not ...
[19:23] <bigjools> echan
[19:24] <thedac> bigjools: I will check
[19:49] <rick_h_> what's the right replacement for dir() on an object instance I can use to interrogate things?
[19:55] <abentley> rick_h_: dir(zope.security.proxy.removeSecurityProxy())
[19:56] <rick_h_> abentley: cool thanks
[20:00] <abentley> deryck: I'm thinking of switching "var namespace = Y.namespace('lp.app.listing_navigator');" to "var module =…" for consistency with the test code.  Thoughts?
[20:08] <rick_h_> abentley: does the server side mustache stuff allow for the {{#field}}{{.}}{{/field}} syntax?
[20:09] <abentley> rick_h_: Yes, AIUI, the dot is supported.
[20:11] <deryck> abentley, yeah, I like module better than namespace.
[20:12] <lifeless> abentley: deryck: so, after using moustache for a bit; do you like it? has it saved time / costed time but added features / <other> ?
[20:14] <deryck> lifeless, I find it tremendously easier to edit than tal. that seems time saving to me.
[20:15] <deryck> lifeless, it has it's own syntax oddities to me.  but generally, I've liked using it a lot.
[20:15] <abentley> lifeless: Like JavaScript, I like the capability it gives, without being a big fan of the language itself.  Both the JavaScript and Python implementations have bugs that entail pretty gross hacks, and the JavaScript implementation is noticeably slow.
[20:16] <lifeless> abentley: do we need to fix those before we advocate for wider use; or should we look for a better alternative with the same capabilities?
[20:18] <rick_h_> the nice thing is that handlebars (mustache improved) will be included in YUI 3.5 as Y.handlebar and the 3.5 PR1 was released today
[20:18] <abentley> lifeless: The JavaScript slowness is potentially a dealbreaker.  Other than that, I'd cautiously recommend it.
[20:18] <rick_h_> I'm not sure though on a pure python implementation
[20:18] <abentley> rick_h_: There's no pure Python implementation, AFAICT.
[20:18] <lifeless> of handlebars ?
[20:18] <abentley> rick_h_: I would be very reluctant to use handlebars on the client side while using mustache on the server side.
[20:19] <abentley> lifeless: right.
[20:19] <rick_h_> abentley: agree
[20:19] <lifeless> how big is the delta? could we sensibly tweak moustache (python) into handlebars (python) ?
[20:19] <deryck> I thought handlebars was the same as mustache,  but more performant.  that compatibility-wise they were the same.
[20:20] <abentley> lifeless: handlebars is a superset of moustache, if what I've read was true.
[20:20] <abentley> lifeless: So the risk would be accidentally using handlebar-specific features.
[20:20] <abentley> lifeless: And then having them break server-side.
[20:20] <lifeless> http://thinkvitamin.com/code/getting-started-with-handlebars-js/ is a post from the handlebars author
[20:22] <lifeless> it appears to be totally separate but inspired by
[20:23] <rick_h_> lifeless: well the front page of handlebars says "Mustache templates are compatible with Handlebars, so you can take a Mustache template, import it into Handlebars, and start taking advantage of the extra Handlebars features."
[20:23] <rick_h_> but yea, you'd get used to all the good bits of handlebars and then lose them on the server side
[20:23] <lifeless> intruiging
[20:23] <lifeless> so the question to me, is how big is that delta
[20:23] <rick_h_> so might not work out after all, I had secretly hoped there was something server side for it
[20:23] <rick_h_> lifeless: I'm going to guess a bit since handlebars allows things like moving up/down the call stack
[20:24] <lifeless> we could use node.js on the server
[20:25] <rick_h_> just skip the server side initial rendering ;-)
[20:25] <lifeless> thats harder to swallow
[20:25] <lifeless> per code.google.com/web/ajaxcrawling/docs/getting-started.html which flacoste dug up the other day
[20:26] <lifeless> one thing we could do is dev/test with moustache.js but use handlebars as an accelerator in [qa]staging+prod
[20:26] <lifeless> that has its own risks, of course
[20:26] <rick_h_> I still think the answer isn't to get the bug listings crawled, but the bugs themselves and that there should be a way to get that information to a crawler without being visible
[20:26] <rick_h_> a paginated list of bugs is going to change around over short periods of time and not be a good landing/search page result anyway
[20:27] <lifeless> yes and no
[20:27] <lifeless>  /+bugs is reasonably constant
[20:27] <lifeless> and we want its changes to be indexed anyhow because of 'heat'
[20:27] <lifeless> other arbitrary searches - yeah, 'meh'. OTOH they don't have much juice today.
[20:27] <rick_h_> I thought that was going away/getting altered though
[20:28] <lifeless> what is a concern though is ensuring that the bugs get indexed
[20:28] <lifeless> rick_h_: its been less special cased.
[20:28] <lifeless> rick_h_: but as a page its not going away
[20:28] <lifeless> gotta run. great chatting - sounds like fun stuff to play with. Ciao.
[20:28] <rick_h_> ic, I'll have to look sometime though. I wonder if there's a better way to note/point the robot to something like a canonicalurl for all bugs on the page
[20:28] <rick_h_> have fun lifeless
[20:43] <deryck> gah!  I just want to run tests in lazr.batchnavigator and have no clue how to build it.  it hates me.
[20:44] <deryck> gary_poster, perhaps you can help here ^^ ?
[20:44] <deryck> just looking for simple build instructions for a lazr package.
[20:45] <benji> deryck: I think it's buildout-based, you'll want to bootstrap it and then run bin/buildout and then bin/test will run the tests
[20:45] <gary_poster> deryck, I dunno that package.  we used to have instructions to put a file on how to build the package
[20:45] <gary_poster> deryck, and it would link to this wiki page:
[20:46] <deryck> benji, yeah, I tried that.  both with symlnks to download-cache and eggs and not.  it blows up regularly and angrily :)
[20:46] <gary_poster> deryck, https://dev.launchpad.net/HackingLazrLibraries
[20:46] <deryck> benji, I think it's expecting something installed system wide and I can't work out what.
[20:46] <gary_poster> deryck, I think the file was HACKING.txt
[20:46] <deryck> gary_poster, thanks for the link.  looking....
[20:46] <gary_poster> Dunno if that is there
[20:46] <gary_poster> welcome
[20:47] <benji> deryck: it may actually be the opposite, it may be assuming that you're using a clean Python (or virtualenv)
[20:47] <deryck> ah hmmmm
[20:50] <rick_h_> abentley: doesn't appear that it supports the {{.}}, had to convert things to a dict and use the key and that works
[20:53] <wallyworld_> sinzui: jcsackett: can we make the standup 30 minutes earlier today? i have a denist appt with the kids i need to get to
[21:07] <sinzui> wallyworld_, sure
[21:07] <sinzui> wallyworld_, 1. the nasty rollback is in build bot
[21:08] <sinzui> wallyworld_, 2. I have sent of the non-feature test refactoring to ec2
[21:08] <sinzui> wallyworld_, 3. i have reproduced the traversal issue I saw in qastaging
[21:09] <sinzui> wallyworld_, do you have time to mumble now about how we want to test this non-obvious issue in the future
[21:10] <deryck> benji, that was it!  Had to use virtualenv for clean env, and all is well.  Thanks!
[21:11] <benji> deryck: cool; many buildout-based projects are like that, depending on a clean environment for sane reproducable builds
[21:26] <wallyworld_> sinzui: sorry, just was having breakfast. we can discuss on the call
[21:27] <sinzui> okay
[22:01] <sinzui> jcsackett, mumble?
[22:02] <jcsackett> sinzui: oh, right. be on in just a moment.


[00:02] <RAOF> ebroder_: You can manually start X and run gnome-session in it?
[00:24] <penguin42> what happens to all the session stuff if you do that?
[00:25] <RAOF> Oh, yeah.  That's right.
[00:26] <RAOF> You want to run /etc/X11/Xsession or somesuch.
[01:48]  * freeflying
[04:48] <RAOF> Oh, oh!  Can someone else reproduce bug #656037?  If so, this should be a release blocker.
[04:54] <bladernr> RAOF:  I can try in a few... gotta build a usb key for netbook first
[04:55] <bladernr> I really should stop soon... I've been at this since 0900 :/
[04:58] <RAOF> That needs to be qualified with a timezone to mean anything; I've been at this since 0830 :)
[04:59] <bladernr> EDT
[04:59] <bladernr> heh
[04:59] <bladernr> so... roughly 15 hours
[04:59] <bladernr> well about 12 hours (dinner and lunch break)
[05:04] <bladernr> FWIW, I've got a 32bit Kubuntu install done w/ network and it looks like all the repos are present (main, universe and multivers + restricted)
[05:07] <ogra_ac> -7join #ubuntu-release
[05:08] <ogra_ac> hmpf
[05:08] <RAOF> Heh.
[06:22] <cdbs> How long after the release will natty open?
[06:22] <micahg> cdbs: usually one to 2 weeks
[06:23] <cdbs> micahg: ah, thanks
[06:23] <RAOF> cdbs: Depends on how many electric shocks you apply to the foundations team! :)
[06:40] <NCommander> pitti: ping, I need some help with apport-retracer when you have some time
[06:57] <bladernr> RAOF:  I confirm... sources.list on netbook is hosed.  Though only on netbook images, it seems
[06:58] <RAOF> bladernr: Yeah.  I think I've identified the problem, and I've brought it to the attention of ubuntu-release and the ubiquity guys.
[07:03] <bladernr> excellent...
[07:03] <bladernr> now I shall pass out for a few hours...
[07:03] <bladernr> cheers
[07:25] <dholbach> Good Morning!
[07:25] <soren> Mr. Holbach!
[07:25]  * soren hugs dholbach
[07:25]  * dholbach hugs soren back
[07:25] <dholbach> man! how are you doing?
[07:26] <soren> Great, but busy :)
[07:26] <dholbach> :-)
[07:26] <soren> Trying to get a release out the door and celebrating my daughter's two-year birthday at the same time.
[07:27] <dholbach> woohoooo!
[07:27] <soren> On that note, I have to go wake her up. She's celebrating by sleeping in, apparently.
[07:27] <dholbach> have a great party :)
[07:27] <soren> Ta ;)
[07:46] <pitti> Good morning
[07:46] <pitti> RAOF: doesn't startx do that?
[07:46] <RAOF> pitti: Not last time I tried.
[07:46] <RAOF> Or, at least, not to my rememberance :)
[07:47] <pitti> ebroder: gdm doesn't have that much overhead, but if you want to start it directly, then something like "ck-launch-session startx" ought to do
[07:47] <pitti> NCommander: what's  up?
[07:56] <RAOF> Hm.  Why doesn't this live session have a shutdown option?
[10:40] <jibel> mvo, Hi, could you have a look at bug 639933, it seems to affect only kubuntu upgrades.
[10:41] <mvo> jibel: sure
[10:41] <jibel> mvo, thanks
[11:35] <planetcall|web> does ubuntu need dotnet skills?
[11:40] <Laney> some applications are based on mono, if that is what you are asking
[11:40] <Laney> These tend to be written in C#
[11:41] <Tm_T> Laney: he is gone already (:
[11:42] <Laney> oh
[11:42] <Laney> oh well
[12:06] <NCommander> pitti: reinstalled apport-retracer on kakadu, I try running crash digger but it just hanged when it starts retracing, and doesn't seem to be calling apport-retrace
[12:06] <pitti> NCommander: I suppose it needs some firewall rules
[12:07] <pitti> NCommander: there were some network adjustments necessary on ronne, for working around bug 620458
[12:07] <pitti> NCommander: but I don't know about the details unfortunately (I was on holiday)
[12:10] <NCommander> pitti: shouldn't that just error out and not hang?
[12:10] <NCommander> Or is that a bug in the retracer?
[12:10] <pitti> NCommander: TCP timeouts somewhere?
[12:11] <NCommander> pitti: 10/07/10 04:12:27: retracing #625408
[12:11] <NCommander> That was about 5 hours ago ...
[12:11] <NCommander> Something should have timed out by now :-)
[12:16] <pitti> ok, then it seems somethign deep in launchpadlib/lazr/etc. should time out
[12:16] <pitti> but anyway, I think the reason are the firewall settings
[12:16] <pitti> NCommander: you could attach strace to it and see what it's hanging on?
[12:17] <NCommander> pitti: I posted IS, and will wait to see if that just magically resolves it (and may just throw the retracer up on <IP_ADDRESS> to see if its actually firewall related)
[12:17] <NCommander> pitti: will do, though probably not tonight.
[12:20] <seb128> you can try retracing a public bug to see if it works
[12:21] <seb128> without the firewall tweak the retracers were crashing on timeout after minute or so
[12:24] <wgrant> FWIW, we have a proper private attachment which is awaiting testing.
[12:28] <ScottK-droid> seb128: Would you please review cairo-dock/plugins in the queue? Go ahead and accept them if you think they are OK.
[12:28] <seb128> ScottK-droid, ok
[12:28] <ScottK-droid> Thanks.
[12:29] <seb128> yw
[12:31] <chrisccoulson> lamont, is there any way i can debug processes which hang in the buildd's?
[12:31] <chrisccoulson> i had a firefox build hang last night: http://tinyurl.com/3yz6gen
[12:31] <chrisccoulson> and i'm not sure what to do, it's not reproducible locally
[12:33] <lamont> chrisccoulson: I don't even have any way to reach into a ppa builder and see what it's doing, other than via the web UI on launchpad
[12:33] <chrisccoulson> hmmm, that's a bit of a pain
[12:33] <lamont> if it's hanging on the archive buildds, poke someone to look at it during that 2.5 hour window is about the best answer
[12:34] <lamont> chrisccoulson: definitely a pain
[12:34] <chrisccoulson> i was hoping that i could resolve these issues before i upload to the main archive next cycle :/
[12:55] <chrisccoulson> lamont, there's not anything running on port 8888 in the PPA builders is there?
[13:06] <lamont> prolly not
[14:44] <smb> Who would be currently in charge for network manager again?
[14:52] <pitti> smb: Mathieu (https://launchpad.net/~mathieu-tl)
[14:55] <smb> pitti, Ok, thanks
[15:32] <pitti> mdeslaur: so, postgresql-8.4/maverick couldn't be synced (too late); want me to provide a maverick-security upload, or do you already have one in the pipe? (it's just the Debian sid package with an adapted version number, and perhaps a bug ref in the changelog)
[15:33] <mdeslaur> pitti: I'm actually publishing the dapper-lucid ones as we speak :(
[15:34] <mdeslaur> pitti: could you create a maverick-security package, and I'll release it next week?
[15:34] <pitti> mdeslaur: ah, so we'll do a followup USN for maverick?
[15:34] <mdeslaur> pitti: yeah, I'll release a -2
[15:34] <pitti> mdeslaur: yep, can do
[15:34] <mdeslaur> pitti: cool, thanks
[15:34] <pitti> mdeslaur: I guess I don't need to do it "right now", then, and "by tomorrow" is enough?
[15:34] <mdeslaur> pitti: I won't publish it before tuesday anyway, so no rush
[15:45] <pitti> mdeslaur: btw, should I include the orig.tar.gz into the .changes? it's the same orig.tar.gz as for karmic/lucid
[15:45] <pitti> mdeslaur: but if you upload it to a PPA first, you might need it
[15:46] <pitti> (uploading without one for now)
[15:47] <mdeslaur> pitti: That's okay, I'll grab it from the other releases. thanks
[15:47] <pitti> URL sent to the bug
[15:48] <pitti> (you wouldn't have guessed it :) )
[15:48] <mdeslaur> hehe
[16:16] <ari-tczew> when natty will be open?
[16:16] <micahg> ari-tczew: 1-2 weeks after release generally
[17:39] <mdeslaur> pitti: have you run the postgresql test suite on maverick?
[17:39] <dpm> hi mvo, a translator had been doing some work on the ddtp templates, and some of his translations are now gone. He's asking if the strings are now stable or if he should wait for a bit...
[17:39] <mdeslaur> pitti: it's asking me for a password, which it doesn't do on previous releases...
[17:49] <mdeslaur> pitti: never mind, seems I had cruft in my /var/lib/postgresql directory
[18:01] <sabdfl> do we really have a 0-day ssl issue? aieeee :-)
[18:06] <highvoltage> hmm, if what sabdfl say is true, then we'll probably have another rebuild
[18:07] <highvoltage> and testers should probably be given some kind of heads-up that there will be a rebuild
[18:07] <mdeslaur> highvoltage: no, it's been published in -security
[18:07] <mdeslaur> highvoltage: no need to rebuild
[18:08] <highvoltage> mdeslaur: ok
[18:08] <ScottK> mdeslaur: From reading the USN, it wasn't clear to me if both issues were risk of code execution with privileges of the calling application or potentially something worse?
[18:09] <mdeslaur> ScottK: only the second issue applied to Maverick, and while it's marked as a code execution, our hardening features turns it most likely into a simple denial of service
[18:10] <hallyn> slangasek: cjwatson: so regarding bug #622762, does it sound like something worth having in release notes?  (about backward compatibility of cryptsetup from lucid to maverick)
[18:10]  * ScottK goes to re-read the USN.
[18:11] <ebroder> Who am I supposed to talk to to get a room at UDS? Do I just book it with the hotel directly?
[18:11] <ScottK> mdeslaur: Thanks.
[18:12] <slangasek> hallyn: yes
[18:12] <hallyn> slangasek: is there something i should do, like add a tag to the bug?
[18:12] <slangasek> hallyn: open a task against the ubuntu-release-notes project
[18:23] <highvoltage> https://wiki.ubuntu.com/TechnicalBoardAgenda needs an update on next meeting time.
[18:25] <hallyn> slangasek: ok thx
[18:30] <kees> highvoltage: I've updated the date.
[18:32] <highvoltage> kees: thanks!
[18:41] <kees> highvoltage: np :)
[19:35] <mvo> dpm: some are gone .( why that?
[19:35] <mvo> dpm: vanished packages?
[19:35] <mvo> dpm: they should be stable now
[19:59] <dpm> mvo, I don't know which ones exactly vanished. I'll ask the translator tomorrow. Thanks, I'll tell him now that they should be stable
[20:23] <Dev^Null> Hey all I have a disk image of ubuntu 9.10 that I replicate to about 500 different machines. I am having an issue with the 70-persistent-net.rules becuaes it wants to name the nic based of the mac address while this changes with each machine. I would like to set it up to look if ATTR{operstate}=="up" then  call that car eth1 I have 2 nic's in each box and only one is ever used. how would I do this.
[20:23] <kibibyte> hi
[20:23] <kibibyte> why nobody fixed bug with icons disappering fom right top menu? this bug exists since 1 or more years. Only solution to it is rm -rf .gconf*  and then set desktop from scratch!#
[22:03] <rmrfslash> How/where is networking started on boot in Ubuntu?
[22:03] <rmrfslash> I don't see any init scripts in runlevels other than 0,6
[22:03] <rmrfslash> clearly is must be started from somewhere else, I'd just like to know the best place to put an iptables-restore
[22:06] <kklimonda> rmrfslash: check /etc/init/
[22:06] <rmrfslash> /etc/init.d?
[22:06] <kklimonda> no, /etc/init/
[22:07] <kklimonda> see for example how is ufw started
[22:07] <rmrfslash> woops
[22:09] <rmrfslash> so I should probably put rules in user.rules
[22:11] <kklimonda> if you decide to use ufw it's pretty well documented
[22:11] <kklimonda> see man ufw-framework
[22:12] <kklimonda> user.rules are, afair, added by the ufw itself
[22:12] <kklimonda> you should edit before.rules and after.rules
[22:12] <kklimonda> rmrfslash: *
[22:12] <kklimonda> ech, missed ^
[22:13] <rmrfslash> i c
[22:13] <rmrfslash> thanks
[22:35] <ScottK> barry: Would you be able to take a look at https://bugs.launchpad.net/bugs/656541 and see if the proposed patch is correct?
[22:44] <cwillu> while trying to build compiz form source, dpkg-buildpackage dies with "gtk-window-decorator.c:50: fatal error: libwnck/libwnck.h: No such file or directory"
[22:44] <cwillu> this is odd, given that cwillu@dominubuntu:~/work/compiz/compiz-0.8.6$ ls -lh /usr/include/libwnck-1.0/libwnck/libwnck.h
[22:44] <cwillu> -rw-r--r-- 1 root root 1.3K 2010-05-31 01:44 /usr/include/libwnck-1.0/libwnck/libwnck.h
[22:45] <poolie> in that case i guess autoconf/pkg-config isn't finding the right path
[23:06] <cwillu> poolie, thanks.
[23:06]  * cwillu starts reading potentially relevant man pages
[23:07] <cwillu> poolie, pkg-config --list-all has an entry for libwnck-1.0, which would seem correct
[23:11] <cwillu> ugh, stray copy in /usr/local/ from before I knew how of dpkg-buildpackage's existence
[23:13] <poolie> that'd be it
[23:14] <poolie> cwillu: you might like to use sbuild or pdebuild to do your package builds isolated from your regular system
[23:18] <cwillu> poolie, I use similar for my arm packages;  for my desktop stuff (incidently, how do I go about getting some of these fixes actually applied?), them breaking in this fashion is a sign that I did something wrong, and I'd rather have the symptom
[23:19] <cwillu> for instance, current compiz with snapping is unusable on slower systems, as it warps the mouse pointer back to the last window move location faster than you can move it
[23:26] <poolie> how do you mean getting them applied?
[23:26] <poolie> best thing is to create a merge proposal on lp
[23:28] <cwillu> so, first step is to actually set up a ppa or such?
[23:43] <poolie> cwillu: no, you don't have to
[23:43] <poolie> just put them in a bzr branch, push that to launchpad, then propose a merge