[01:26] <Jucato> moin Hobbsee && Hobbsee|1emote
[01:32] <Hobbsee_> thanks to whoever fixed my multimedia keys!
[01:32] <Hobbsee|1emote> hey Jucato
[01:33] <Jucato> lol
[01:33] <Jucato> which Hobbsee do I talk to? :)
[01:33] <Hobbsee> Jucato: whichever.   this one
[01:33] <Hobbsee> Jucato: the other is in a screen session on stevenk's computer, so...
[01:33] <Jucato> ah
[01:34] <Hobbsee> most of the time, i'm not there
[01:34] <Jucato> Hobbsee: getting kernel panic in feisty using 2.6.19-6-generic kernel. normal? known? or I'm just screwed up?
[01:34] <Hobbsee> Jucato: i dont know about it, more info required.
[01:34] <Hobbsee> Jucato: what'd the /var/log/syslog say about it?
[01:35] <Jucato> er... lol forgot to check :)
[01:35] <Jucato> it's on VMWare btw
[01:35] <Hobbsee> it was something i was testing...
[01:35] <Jucato> (if that matters)
[01:35] <Hobbsee> ahh - bit hard to mount hte drive on that basis, probably
[01:36] <Jucato> hm... but the 2.6.17 kernel works fine... it's the only one I can use right now in feisty...
[01:37] <Hobbsee> i dont know if it supports vmware - no idea
[01:37] <Jucato> oh ok :)
[01:45] <Jucato> Hobbsee: lol! now it works...
[01:45] <Hobbsee> Jucato: :)
[01:46] <Jucato> after, around 7 tries, it finally boots into the feisty kernel :)
[01:46] <Hobbsee> hehe
[01:49] <freeflying> morning all
[01:49] <Jucato> morning freeflying
[01:50] <Hobbsee> hey freeflying!
[02:00] <DaSkreech> Hiya
[02:05] <Hobbsee> heya
[02:12] <DaSkreech> What were you getting to kernel panic?
[02:13] <Jucato> DaSkreech: dont' know anymore... coz for some strange reason, after the nth try, it works
[02:13] <DaSkreech> Hm msounds like my installation of sawfish
[02:20] <DaSkreech> whats the deal with propietary drivers by default?
[02:20] <DaSkreech> does that mean really really really easy enable of them or if they are detected at install they are installed?
[02:20] <apokryphos> there's a spec about it
[02:20] <apokryphos> the latter
[02:21] <apokryphos> https://blueprints.launchpad.net/distros/ubuntu/+spec/accelerated-x
[02:21] <DaSkreech> Man  that's depressing :(
[02:22] <Jucato> ... :(
[02:22] <apokryphos> it's pretty much necessary for them to get beryl/compiz in by default on the widerscale
[02:23] <Hobbsee> hey apokryphos
[02:23] <apokryphos> hiya Hobbsee
[02:23] <DaSkreech> I'd so much rather a really easy button?
[02:23] <DaSkreech> It's feels so much like giving up
[02:23] <Jucato> ditto DaSkreech
[02:24] <Jucato> I'd rather they develop someway to make the installation of drivers and beryl easy and painless
[02:25] <DaSkreech> Isn't this in direct contravention to the Ubuntu phiosphy?
[02:25] <DaSkreech> I can see people carving up the Ubuntu=MS stamps now
[02:25] <Jucato> not according to sabdfl
[02:25] <apokryphos> not entirely. They've said from the beginning that they'd include proprietary things when it's "practical"
[02:26] <DaSkreech> I'm not sure bling bling is practical in a OS or a general life sense
[02:26] <Jucato> and the commitment/philosophy is to provide a free OS. it's still free, although not in the FSF sense of the term
[02:26] <apokryphos> DaSkreech: in truth they're not doing much new by doing this now. The GPL is also not violated because of the way things are set up (SLA security, etc)
[02:26] <DaSkreech> Then why can't Korroa ship?
[02:27] <DaSkreech> (spelling is wrong)
[02:28] <apokryphos> Ubuntu's going to, like Novell, through the reproduction burden onto the user
[02:28] <apokryphos> *throw
[02:28] <apokryphos> but again, that's not new. That's exactly how nvidia-glx works right now
[02:34] <DaSkreech> Konvi krashed
[02:34] <Jucato> ouch
[02:34] <DaSkreech> apokryphos: Sorry you were saying?
[02:34] <DaSkreech> Jucato: Naw History is a great thing :)
[02:39] <DaSkreech> What reproduction burden?
[03:15] <seele> wow, lots of feedback about grub
[03:15] <seele> people must really want a tool to configure it :)
[03:16] <Jucato> :)
[03:16] <Hobbsee> hey seele!
[03:17] <seele> hihi
[03:17] <Hobbsee> seele: is there any feedback you still need?
[03:17] <Jucato> seele: in your blog post?
[03:17] <seele> Hobbsee: i havnt had time to go through all the comments yet, but if you have something to say, feel free :)
[03:17] <seele> Jucato: ja
[03:17] <Hobbsee> seele: neither have i, hence i probably dont have things to say :P
[03:17] <Jucato> ah nice. I read the post... didn't read the responses :)
[03:19] <Jucato> afaik, Mandriva/PCLOS has a nice (a.k.a. working) GRUB GUI editor
[03:26] <imbrandon> moins Jucato , seele , and Hobbsee !
[03:26] <Hobbsee> hey imbrandon!
[03:26] <Jucato> hi imbrandon@
[03:26] <Jucato> er.. s/@/!
[03:27] <imbrandon> seele: yea they really do, there ahev been requests for a LONG time for it
[03:27] <Jucato> GRUB eye candy... :)
[03:45] <Hawkwind> w00t, Feisty is now installed and running :)
[03:49] <Hobbsee> yay :)
[03:51] <jdong> and speaking of a lot of bugs
[03:51] <jdong> (j/k)
[03:52] <Hobbsee> :P
[03:53] <Hobbsee> Riddell: is there any plans to switch back to using media:/ instead of /media/ ?
[03:54] <Hobbsee> media:/ seems to be working for more people, looking at these bug reports
[03:54] <Hobbsee> that being said, i like how /media/ is taking the drive names, instead of just how big they are, as media:/ does
[03:54] <robotgeek> i hate media:/ as it did not work in nonkde apps, how is that handled now?
[03:58] <Hobbsee> robotgeek: i'm not sure. that's a point.  then i guess that they use /media/
[03:59] <robotgeek> Hobbsee: yeah, it blows to have a save dialog and it not working
[04:14] <imbrandon> Hobbsee: no there isnt plans to go back
[04:14] <Hobbsee> right
[04:15] <imbrandon> robotgeek: yea that was the main reason for it , because it breaks no kde apps
[04:15] <robotgeek> it is very frustrating, cause you can see the damn thing there, but not save it!
[04:16] <crimsun> fools shouldn't be using non-kde apps nohow.
[04:16] <imbrandon> yup, thus media:/ is gone ( only from kde3 for us ) but kde4 wont have it at all
[04:16] <robotgeek> crimsun: i use firefox when konqueror does not render properly
[04:17] <crimsun> ('twas a joke if you couldn't tell by the syntax ;)
[04:17] <imbrandon> crimsun: heheh
[04:17] <imbrandon> robotgeek: i thought you just booted into OSX when it dident work ( just kidding )
[04:18] <robotgeek> imbrandon: no, i dont ever boot into OS X anymore, just run it from withing linux
[04:18] <imbrandon> :)
[04:18] <imbrandon> ugh phone again
[04:18] <imbrandon> brb
[07:13] <lengau> Hi
[07:15] <lengau> Does anyone know where to go to request packages for future releases?
[07:23] <nixternal> lengau: https://wiki.ubuntu.com/MOTU/Packages/Candidates
[07:23] <lengau> nixternal: Thanks. I've been looking all night, but it never dawned on me to check the obvious place :)
[07:27] <nixternal> hehe
[07:27] <nixternal> no problem
[07:33] <Hobbsee> Jucato: because no one packaged it, probably
[07:33] <Jucato> aw... not popular enough? :)
[07:34] <Jucato> Hobbsee: is the Ubuntu Packaging Guide the recommended way to compile from source and build packages? (alternative to make install/checkinstall?)
[07:35] <Hobbsee> Jucato: for private use, or to go into repos?
[07:35] <Jucato> both :)
[07:35] <Hobbsee> the former
[07:36] <Jucato> ok.  S.O. not recovered from your last cooked meal?
[09:51] <nixternal> xS.O. ;)
[09:52] <crimsun> I hope I'm not shoving my foot in my mouth
[09:52] <nixternal> ahh the family pooch might have just started her journey to a better place
[09:52] <crimsun> oh, right
[09:52] <nixternal> right as I was heading up, i heard the old man freaking out yelling the dogs name
[09:53] <nixternal> he took off for the animal hospital
[09:54] <crimsun> hope she's in less pain, then
[09:54] <nixternal> ya, me too
[09:54] <nixternal> i was holding her while he got his stuff ready and she started to convulse..that was enough for me..im a weakling to that stuff
[11:00] <Enola_Gay> hi all
[11:00] <Enola_Gay> Does anyone know why klik isn't integrated in Kubuntu?
[11:00] <Enola_Gay> Or at least in the repository?
[11:02] <Riddell> security and technical issues
[11:03] <Enola_Gay> Riddell: ok, thanks
[11:06] <Enola_Gay> cu
[11:07] <Jucato> oh cool, the python-sip4 problem seems to be fixed already :)
[11:15] <Riddell> Jucato: well, one of them
[11:15] <Jucato> :)
[11:47] <Jucato> the current version of KOffice in fesity is 1.5.2?
[11:49] <Riddell> yes, I uploaded 1.6.0 but it failed and I'm not fixing it since I'm working on 1.6.1 now
[11:50] <Jucato> ah cool 1.6.1 :)
[12:44] <Tonio__> hi
[12:44] <Hobbsee> hey Tonio__
[12:44] <Tonio__> Riddell: just saw your comments on jabbin.... I'll have a look at the qca-tls, but that looks like optional stuff...
[12:45] <Tonio__> Riddell: and concerning dolphin I missed that it was in debian (wasn't when I did the package in fact)
[12:45] <mhb> hi all
[12:45] <Hobbsee> hey mhb!
[12:49] <MidMark> guys there is a big problem in usb storage management in kubuntu
[12:49] <MidMark> if you umount a pen drive that has still some writing data in cache the icon in kde disappears before it finish to write to the usb storage
[12:50] <MidMark> a person think that can take off the usb but will destroy for certain data
[12:50] <MidMark> is it known?
[12:51] <Tonio__> MidMark: yes
[12:51] <Tonio__> MidMark: I don't know if the issue is in our patches or in kde but that's a known issue
[12:51] <MidMark> this doesn't occur with Dapper
[12:52] <MidMark> Tonio__: is already reported in launchpad? number?
[12:52] <Tonio__> MidMark: I don't know for launchpad, but that is known and already discussed here
[12:53] <MidMark> ok, it's a pitty, every release of Kubuntu has a dozens of critical bugs unresolved...
[12:54] <Hobbsee|Remote> Tonio__: it's reported in launchpad, too
[12:54] <Hobbsee> MidMark: feel free to start fixing
[12:54] <MidMark> I think 6 month cycle (4 for Edgy) it's a little too fast cycle, produce cutting edge
[12:54] <Tonio__> Hobbsee hope you know the bug id :)
[12:54] <Hobbsee> Tonio__: i can find it, in a sec
[12:55] <MidMark> Hobbsee: I'm a bug report and bug fuzz, take a look to my bug reported list
[12:55] <MidMark> this take time too
[12:55] <Hobbsee> Tonio__: https://launchpad.net/distros/ubuntu/+source/kdebase/+bug/61946
[12:55] <Ubugtu> Malone bug 61946 in kdebase "umount progress dialog missing in Edgy" [Undecided,Confirmed]
[12:55] <Hobbsee> various other umount stuff broken as well
[12:55] <Tonio__> yep this one :)
[12:56] <Tonio__> hum it looks like I packaged jabbin and dilphin too fast hehe :)
[12:57] <mhb> it's probably known that the documentation (k-d-g, release notes) in Edgy is only in English ... is it planned to fix it in an update?
[12:57] <Hobbsee> mhb: do they have translations for it in rosetta?
[12:58] <mhb> Hobbsee: 100%. it's just not in Edgy help center
[12:58] <mhb> Hobbsee: it was translated before the deadline, but somehow it hasn't been included in Edgy
[12:59] <Hobbsee> mhb: ah right.  *pokes nixternal*
[01:00] <Hobbsee> mhb: absolutely no idea why, i dont tend to deal in translations
[01:00] <mhb> I think it was mentioned somewhere, but I don't know any LP bug number
[01:00] <Hobbsee> it's probably in the great lot of kdebase.
[01:02] <mhb> Hobbsee: I know it's neither your area of expertise nor your fault .o)
[01:02] <mhb> I'll wait for nixternal probably
[01:04] <Hobbsee> MidMark: i cant search for your reported bugs, if you didnt give a LP ID
[01:04] <MidMark> Hobbsee: ah sorry I'm Cimmo on launchpad
[01:05] <Hobbsee> ah, which is why i wouldnt have guessed
[01:05] <MidMark> s/Cimmo/cimmo
[01:05] <MidMark> also I'm a vast list of subscribed ones
[01:09] <Tonio__> Riddell: concerning jabbin and libqca, that looks like optionnal feature and isn't a compilation option, so it probably should be recommended and not be set as a dependancy right ?
[01:10] <Jucato> Tonio__: will kpkgmanager be in your repo soon? I'll be glad to test it on feisty :)
[01:10] <Tonio__> Jucato: bah it was rediscussed....
[01:10] <Tonio__> Jucato: it looks like unmaintained for a year in fact
[01:10] <Jucato> aw.. :(
[01:10] <Tonio__> so we will probably not spend time on this
[01:11] <Jucato> oh well, more time to focus on Adept, eh? :)
[01:11] <Tonio__> Jucato: yes... ;)
[01:13] <workmorn> what?
[01:13] <workmorn> i'll release 2.2 when it's ready
[01:14] <Jucato> hi workmorn/mornfall :)
[01:14] <workmorn> afternoon
[01:15] <Tonio__> workmorn: bah in fact we were comparing the functionnalities of kpkgmanager to adept, and it was interesting to get kpkgmanager in the repos too
[01:15] <workmorn> what's kpkgmanager
[01:15] <Tonio__> workmorn: but as it is unmaintained, there is probably no interest to put that in, even universe
[01:16] <Tonio__> workmorn: a simple component that can be installed and used with kio-apt
[01:16] <workmorn> ah ok, so it's the one i have seen
[01:16] <Tonio__> workmorn: it is efficient and works well, but is unmaintained
[01:16] <Tonio__> but the idea is pretty good
[01:19] <Tonio__> workmorn: are you aware we tested the debconf/qt thing ? it works well :)
[01:19] <workmorn> which debconf/qt thing? :)
[01:19] <Tonio__> the only thing is that it would be nice if the env variable to make debconf use "kde" was set be adept when launched
[01:20] <workmorn> you know, it is :)
[01:20] <Tonio__> workmorn: ah ? in the wip stuff ?
[01:20] <workmorn> no, in released version
[01:21] <Tonio__> workmorn: hehe is it in edgy ?
[01:21] <Tonio__> s/edgy/feisty ?
[01:21] <workmorn>     if (cache::Global::get().packages()
[01:21] <workmorn>         .packageByName( "libqt-perl" ).isInstalled())
[01:21] <workmorn>         putenv( "DEBIAN_FRONTEND=kde" );
[01:21] <Tonio__> we had to dpkg-reconfigure debconf to get it to work when testing
[01:21] <Tonio__> workmorn: hehe cool
[01:21] <workmorn> Tonio__: it's there since dapper or so
[01:22] <workmorn> unless you changed name of libqt-perl somehow :)
[01:22] <Tonio__> workmorn: hum, I'll look at that since it didn't ork for us, even with libqt-perl installed
[01:23] <workmorn> Tonio__: it doesn't work because kdesu borks xauth
[01:23] <workmorn> Tonio__: or that was the case last time i checked
[01:23] <Tonio__> workmorn: hum yes maybe
[01:23] <Tonio__> I think we had to perform an xhost+
[01:23] <Tonio__> if my remembering is correct
[01:24] <Tonio__> workmorn: let me test ;)
[01:24] <workmorn> xhost + EWW
[01:25] <Tonio__> workmorn: confirmed, that doesn't work due to kdesu
[01:26] <workmorn> Tonio__: i think it worked in debian, so it was sudo related, but it probably won't work these days anyways
[01:26] <workmorn> no matter
[01:26] <Tonio__> workmorn: interesting
[01:26] <Tonio__> workmorn: well we'll rediscuss thislater, we have time to get that in
[01:26] <workmorn> i had it definitely tested, so who knows :)
[01:27] <Riddell> Tonio__: if it's a compilation option it should be a build-dep most likely
[01:27] <Tonio__> Riddell: it is "not" a compilation option
[01:27] <Tonio__> Riddell: and that's not required for jabbin to work
[01:27] <Tonio__> Riddell: it is used as a "plugin" in fact
[01:28] <Tonio__> Riddell: so should be recommended eventually, but not a dep or builddep
[01:28] <Riddell> ah, so yes recommended sounds right
[01:28] <Tonio__> Riddell: this is the reason I didn't put that as a builddep
[01:28] <Tonio__> Riddell: concerning the amd64 issue........ I cannot test unfortunately
[01:28] <Tonio__> Riddell: I'll correct all I can, unsure it builds on i386 and reupload
[01:29] <Riddell> I'll try it on my powerpc and see what happens
[01:29] <Tonio__> Riddell: okay ;)
[01:30] <Tonio__> Riddell: concerning the licence, it is one of those stupid copy/paste with klipper ;) sometimes it doesn't take the last copied thing as the clipboard
[01:30] <Tonio__> and concerning dolphin, it wasn't in debian when I did the package, but now of course I'll request for a sync
[01:32] <Tonio_> Riddell: okay ftbfs on i386 aswell now
[01:32] <Tonio_> Riddell: it worked 2 weeks ago :)
[01:32] <Tonio_> lib version issue or something, I'll have a look at this
[01:34] <Tonio_> Riddell: I'll also check at qt-x11-free-dbg today
[01:35] <gnomefreak> Tonio_: did you remove kpkgmanager from your repo?
[01:35] <Tonio_> Riddell: the "letters with combinason" doesn't work anymore (again !)
[01:35] <Tonio_> gnomefreak: yep
[01:35] <gnomefreak> ah ok
[01:35] <Tonio_> ^e i
[01:35] <Tonio_> :'(
[01:51] <Tonio_> hum the issue is xorg this time....
[01:51] <Tonio_> not qt-x11
[01:52] <Riddell> what issue?
[01:53] <Tonio_> Riddell: combinason keys don't work
[01:54] <Tonio_> Riddell: ^e e ^o
[01:54] <Tonio_> Riddell: fails in a tty even after a dpkg-reconfigure xserver-xorg
[01:55] <Tonio_> Riddell: I fixed that error in edgy in qt-x11-free package, but the problem looks like related to X this time
[01:56] <Tonio_> and don't tell me "use english keyboard !" ^^
[01:58] <Riddell> keyboard layout is an X issue
[01:59] <Tonio_> yes but in edgy the issue was with the qt-x11 package, I just had to sync with debian to resolve the issue...
[01:59] <Tonio_> not this time
[01:59] <Tonio_> I have to quit for 15 minutes (electricity down)
[02:09] <gnomefreak> Riddell: ty for the python-qt fix ;)
[02:11] <Riddell> mmm, now I need to work out how to fix pyqt3 and pykde
[02:12] <Hobbsee> heh
[02:12] <Hobbsee> need my long pointy stick to help with that?
[02:12] <Hobbsee> Riddell: how's it broken?
[02:12] <Jucato> ooh jpatrick
[02:12] <Hobbsee> hey jpatrick!  LTNS!
[02:13] <jpatrick> hi Jucato
[02:13] <Jucato> ooh LTNS.. :)
[02:14] <jpatrick> Hobbsee: yeah, I've got mately with the kubuntu-es dudes again
[02:14] <Hobbsee> fun :)
[02:14] <jpatrick> I wonder... Riddell: ping
[02:14] <Riddell> hi jpatrick
[02:15] <jpatrick> Riddell: Hi again, the guys at kubuntu-es.org are asking me if it were possible to get the subdomain of es.kubuntu.org
[02:16] <Riddell> what for?  you already have kubuntu-es.org
[02:16] <Riddell> which seems to redirect to some other random domain
[02:17] <jpatrick> they say "to look like we're closer to the official kubuntu"
[02:17] <jpatrick> yeah, tmp hot
[02:17] <jpatrick> host*
[02:17] <Jucato> heh :)
[02:18] <Riddell> doesn't canonical host that site now?
[02:18] <jpatrick> we're in the process of moving (right now)
[02:18] <Riddell> moving to canonical?
[02:18] <Jucato> doesn't kubuntu-es.org follow the LoCo naming policy more closely than es.kubuntu.org?
[02:18] <jpatrick> a canonical server
[02:19] <Riddell> I think canonical has a policy of giving out the -xx.org domains which presumably means they don't do xx.foo.org domains
[02:19] <jpatrick> ok, I'll tell them that
[02:21] <Riddell> gnomefreak: by the way have you tested hwdb-kde with the new pyqt4?
[02:21] <gnomefreak> Riddell: no im just now installing kubuntu-desktop
[02:22] <Riddell> let me know if it actually works
[02:22] <gnomefreak> i will look at it as soon as the downloading/installing it done
[02:23] <Hobbsee> Riddell: seems to work.
[02:23] <Hobbsee> Riddell: the hardware testing database, where it tests for sound and display and all that, right?
[02:23] <Hobbsee> it's working
[02:24] <Riddell> Hobbsee: yes, great, thanks :)
[02:24] <Jucato> working here, too :)
[02:25] <Jucato> lol said that too when I ran hwdb on Edgy a while ago
[02:34] <Tonio_> re
[02:34] <Jucato> will edgy-commercial have packages?
[02:36] <Riddell> not sure
[02:36] <Riddell> seems logical that it should but i
[02:36] <Riddell> if it doesn't have anything at the moment, I guess not
[02:38] <Jucato> ah
[02:42] <Tonio_> Riddell: I'm starting to merge (all the day)
[02:42] <Tonio_> Riddell: no problem if I do adept ?
[02:42] <Riddell> Tonio_: I'm working on pyqt and pykde
[02:42] <Tonio_> Riddell: okay
[02:42] <Riddell> not at all, go ahead
[02:42] <Riddell> ping here when you start working on something so we don't duplicate stuff
[02:43] <Tonio_> Riddell: that's what I wanted to do indeed
[02:43] <Tonio_> Riddell: second thing will be kdebindings, I'll try to fix the build issue on feisty
[02:46] <Riddell> good luck :)
[02:47] <Tonio_> Riddell: hehe, yeah I know :)
[02:47] <Tonio_> Riddell: concerning guidance, I'll probably build from svn instead of syc with debian, that's the way we usually do
[02:49] <Riddell> sync the packaging with debian
[02:49] <Jucato> speaking of guidance... doesn't the description (and System Settings) probably need to be updated to include mention of the wineconfig module?
[02:51] <Riddell> I didn't enable wineconfig because it had various issues
[02:51] <Riddell> for example it should be disabled if you don't have wine installed
[02:52] <Hobbsee> Jucato: can you confirm https://launchpad.net/distros/ubuntu/+source/kdepim/+bug/73003 ?
[02:52] <Ubugtu> Malone bug 73003 in kdepim "korganizer does not start from K Menu -> run dialog" [Undecided,Unconfirmed]
[02:52] <Jucato> Hobbsee: I think I already did
[02:52] <Hobbsee> ah right
[02:52] <Jucato> er wait.. different bug
[02:54] <Riddell> Hobbsee: that's a known bug
[02:54] <Riddell> oh
[02:54] <Jucato> it might be related to the other korganizer bug
[02:54] <Jucato> dang
[02:55] <Tonio_> Riddell: okay I'll sync with debian then
[02:56] <Tonio_> Hobbsee|Remote: confirmed
[02:56] <Jucato> confirmed too
[02:56] <Tonio_> Hobbsee|Remote: same issue when clicking the systray icon, doesn't start
[02:56] <Jucato> Tonio_: that's bug 68341
[02:56] <Ubugtu> Malone bug 68341 in kdepim "Korganizer icon in the System Tray doesn't start Korganizer" [Unknown,Fix released]  http://launchpad.net/bugs/68341
[02:57] <Tonio_> Jucato: okay I'll have a look toonight, after my merging day :)
[02:57] <Jucato> thanks! :)
[02:57] <Jucato> btw, hasn't that "KDEinit could not launch <appname>" been a bug for a long time?
[02:58] <Tonio_> Riddell: concerning guidance, I'll sync the packaging but what about the tarball ? Shouldn't I take it from svn as we usually do ?
[02:58] <Jucato> happens everytime I launch KInfoCenter through Katapult
[02:58] <Tonio_> Jucato: hum confirmed too, can you post a launchpad bug plz ?
[02:59] <Jucato> Tonio_: ok. I'll try digging for a KDE bug report too
[02:59] <Tonio_> Jucato: thanks
[03:01] <Tonio_> Jucato: concerning kinfocenter, that's a katapult issue, so please report the bug for katapult :)
[03:02] <Jucato> no, it happens in Alt+F2, also
[03:02] <Tonio_> Jucato: ah
[03:02] <Jucato> might be related to the korganizer bug Hobbsee mentioned
[03:02] <Jucato> bug for kdelibs?
[03:02] <Tonio_> Jucato: bug for kinfocenter then, it doesn't like to be launched without any parameter
[03:02] <Riddell> Tonio_: if you want, but it's quite fiddly to do (need to get all the translations out too)
[03:03] <Jucato> although in kinfocenter's case, it launches despite the error. in korganizer's case, it doesn't launch at all
[03:03] <Jucato> ok
[03:03] <Tonio_> Riddell: yeah I know but don't mind, I'm used to it, I already synced guidance several times
[03:03] <Tonio_> svn2dist is my friend :)
[03:04] <Tonio_> Jucato: I would say an issue in the desktop file for kinfocenter
[03:04] <Tonio_> Jucato: just report the bug and I'll try to fix it
[03:05] <Jucato> Tonio_: sure thing :)
[03:11] <Jucato> Tonio_: excuse me, what package should I select for the bug report? kdebase? (kinfocenter doesn't exist in Ubuntu)
[03:14] <Tonio_> yes
[03:15] <Jucato> Tonio_: https://bugs.launchpad.net/distros/ubuntu/+source/kdebase/+bug/73008
[03:15] <Ubugtu> Malone bug 73008 in kdebase ""KDEInit could not launch 'kinfocenter'" when launching KInfoCenter from Katapult or Run Command" [Undecided,Unconfirmed]
[03:18] <Jucato> btw, both bugs about korganizer aren't present in Feisty
[03:19] <Tonio_> Jucato: aren't ?
[03:19] <Tonio_> Riddell: just done kipi-plugins while adept is building, fyi
[03:19] <Jucato> Tonio_: yes. I can launch Korganizer from Alt+F2 normally, and the system tray icon behaves normally
[03:20] <morn|off> Tonio_: adept is still building? oh dear :)
[03:20] <Tonio_> morn|off: yes :'(
[03:20] <Riddell> Tonio_: going to change it to recommend graphicsmagick?
[03:21] <Tonio_> Riddell: hum does it work with it ? I though it was still using imagemagick
[03:21] <Riddell> Tonio_: yes, but actually it'll need graphicsmagick-imagemagick-compat
[03:22] <Tonio_> so I may recommend both in fact
[03:22] <Riddell> I guess so, graphicsmagick-imagemagick-compat | imagemagick
[03:22] <Tonio_> yep that's what I thought about :)
[03:23] <Tonio_> okay let's do that
[03:29] <Tonio_> Jucato: hum, the korganizer issue has been resolved somehow, I cannot reproduce it anymore
[03:30] <Jucato> Tonio_: in Edgy or in Feisty?
[03:30] <Tonio_> Jucato: feisty
[03:30] <Tonio_> Jucato: but that didn't work a couple of days ago
[03:30] <Jucato> oh...
[03:30] <Tonio_> yes, maybe rebuilding kdelibs or kdebase in the last days fixed it somehow...... weird anyway
[03:31] <freeflying_> Riddell: any good news about qt-3.3.7?
[03:31] <Jucato> there were some kdepim updates a while ago
[03:32] <Tonio_> Jucato: yes but not in the past days when the issue has been resolved I think
[03:32] <Jucato> ah
[03:32] <Tonio_> I don't remember seeing a kdepim upload (maybe I'm wrong btw)
[03:33] <Riddell> freeflying_: I've not had a chance to look at it yet, and I'm not sure I will be able to before I go away at the weekend
[03:33] <Riddell> freeflying_: it's strange, there shouldn't be anything changed
[03:35] <freeflying_> Riddell: :) it's really strange
[03:36] <Riddell> freeflying_: you could try recompiling it without the patch for visibility
[03:37] <freeflying_> Riddell: okay, I'll recompile it this weekend
[03:48] <fabo> Riddell, Tonio_ if you have time to upload icecc-monitor : http://revu.tauware.de/details.py?upid=3515
[03:48] <Tonio_> fabo: let me look
[03:48] <fabo> thks
[03:50] <Tonio_> fabo: is it waiting for debian or is that already i unstable ?
[03:50] <fabo> it's in etch/sid
[03:51] <Tonio_> fabo: okay :) I'm revuing and uploading
[03:51] <Riddell> so it can just be synced rather than a separate upload?
[03:51] <fabo> right
[03:51] <Tonio_> Riddell: let me look at the changelog
[03:51] <Riddell> Tonio_: check it compiles and runs, then file a sync request
[03:51] <Tonio_> yup no change.... can just be synced
[03:51] <Tonio_> Riddell: yeah I'm doing this
[03:51] <fabo> on my recent upload to revu, all are sync except strig
[03:52] <fabo> i
[03:52] <Riddell> fabo: why not strigi?
[03:53] <fabo> Riddell: a minor linda fix requested by Hobbsee ;)
[03:54] <fabo> Tonio_: if you are motivated -> kbarcode and kscope to sync too
[03:54] <fabo> i'm reviewing kde-extras package right now for feisty ...
[03:55] <Tonio_> fabo: later probably ;)
[03:55] <Tonio_> fabo: I have a bunch of merges to perform today
[03:55] <fabo> k np ;)
[03:55] <fabo> kile FTBFS on feisty, while it build nicely on sid ...
[03:56] <fabo> i don't know why ... yet
[04:04] <Tonio_> Riddell: stupid question but wich package to post the bug for a sync request for a new package, not already in launchpad ? :)
[04:04] <Riddell> Tonio_: you can file bugs without a package
[04:05] <Tonio_> Riddell: hehe, okay, didn't knew since I never did this before, only for existing packages so... :)
[04:06] <Riddell> but if the package doesn't already exist, it should get sycned automatically
[04:06] <Tonio_> Riddell: in theory yes, but no idea when ?
[04:06] <Tonio_> is that done for example every week or so ?
[04:07] <Riddell> Tonio_: not sure actually
[04:07] <Tonio_> k
[05:00] <Tonio_> Riddell: the kdebindings issue is probably related to our libqt3-jni, still 3.5.4
[05:00] <Tonio_> Riddell: I'm trying to merge this and then kdebindings
[05:01] <Tonio_> grmpf, nope it is the same source package hehe
[05:01] <Tonio_> grmpf
[05:28] <fdoving> hmm.. anyone got any good suggestions on the FTBFS(powerpc,i386) kopete in feisty? https://launchpad.net/+builds/+build/275832
[05:29] <fdoving> sparc and amd64 are ok.
[05:29] <fdoving> same package builds fine in edgy.
[05:30] <Tonio_> Riddell: I forgot kdebindings at the moment, I'm starting kdebluetooth (lots of changes there, might take a while
[05:32] <Tonio_> Riddell: the interesting thing is that this version includes a passkey-agent for dbus
[05:32] <Tonio_> we will not have to workarround now
[05:32] <Riddell> Tonio_: kdebindings has a new release out which uses a new bluetoothe library
[05:32] <Riddell> Tonio_: you'll need to ask dholbach if the gnome stuff can also use that new library version
[05:32] <Tonio_> Riddell: ah ? cool
[05:33] <Tonio_> Riddell: the problem with kdebindings is that we have an external issue, since even the previously built version ftbfs now......
[05:33] <Tonio_> Riddell: kdebindings and kbluetooth ? I'm not sure to understand
[05:34] <Tonio_> Riddell: wheren't you talking about new bluez and kdebluetooth instead ?
[05:34] <Riddell> er, yes
[05:34] <Riddell> s/kdebindings/kdebluetooth/
[05:34] <Tonio_> yes in fact gnome already uses this
[05:35] <Riddell> oh, sorted
[05:35] <Tonio_> the passkey-agent is used with bluez/dbus
[05:35] <Tonio_> Riddell: I'm just testing the debian package...... the problem is that the packaging is completly different (doesn't use cdbs anymore)
[05:35] <Tonio_> I'll probably have to re-cdbs it
[05:36] <Tonio_> but as the souces changed a lot, it'll take time to test all patches etc.....
[05:37] <Tonio_> let go !
[05:39] <fdoving> hmm.. does the package uploaded to edgy-proposed need a accept from the archive admins before it's buildt?
[05:40] <Riddell> fdoving: yes
[05:41] <fdoving> Riddell: ok. glad i'm not an archive-admin. I've poked them alot lately :)
[05:45] <Riddell> _Sime: any idea if pykde should work with python 2.5?   Nice to know you can count on them
[05:51] <nixternal> haha right
[05:51] <nixternal> it is no biggy to me, as it is my test machine
[05:51] <nixternal> so i can always reinstall
[05:52] <nixternal> i need to start imaging that machine though..i would rather take 5 minutes instead of 1 getting it back
[05:52] <nixternal> s/1/1 hour
[05:52] <Tonio_> Riddell: hum, the new kdebluetooth debian package is an horrible mess (removed cdbs, conflict files with bluez-utils etc.......)
[05:53] <Riddell> Tonio_: don't use it then
[05:53] <Tonio_> Riddell: I'll probably simply update the kubuntu package with new tarball and make it to work
[06:02] <apokryphos> heh
[06:03] <jpatrick> I thought he was clay, not water
[06:05] <Riddell> claydoh: ahem
[06:05] <DaSkreech> Well he just got banned
[06:05] <apokryphos> temporarily, to avoid floods
[06:05] <DaSkreech> yeah I figure. guess flooding gets muddy with him
[06:06] <jpatrick> DaSkreech: my point exactly
[07:11] <Tonio_> Riddell: I'm giving a good clean to the kbluetooth package too since it is currently very messy (mixing cdbs and pure debhelper stuff etc.......)
[07:12] <Riddell> cool
[07:14] <Tonio_> I just hope the dbus stuff works correctly
[08:27] <_Sime> Riddell: what's up?
[08:28] <Riddell> _Sime: pykde doesn't like python 2.5 http://kubuntu.org/~jriddell/tmp/pykde.text
[08:30] <_Sime> Riddell: which  version of SIP?
[08:31] <_Sime> Riddell: I'm not sure if Jim has updated PyKDE for Python 2.5.
[08:49] <Riddell> _Sime: sip 4.5
[08:51] <_Sime> Riddell: I don't think Jim has updated PyKDE for Python 2.5. He has been very busy/quite lately.
[08:52] <Riddell> _Sime: right.  I think the plan is to have 2.5 as default in feisty, but I'm not sure when that change will happen
[08:54] <_Sime> Riddell: the errors you've got there don't look fatal.
[08:54] <_Sime> Riddell:  http://mail.python.org/pipermail/python-dev/2006-September/068944.html
[08:55] <Tonio_> Riddell: hum the latest kdebluetooth debian version doesn't use dbus in fact. I'm trying to package from svn instead, this was dholbach plan for feisty
[08:56] <Tonio_> seems to be working nicelly since opensuse already uses this
[09:00] <_Sime> Riddell: if possible, it is best to get a fixed version from Jim. But it does look fixable without Jim's help. It is just a PITA.
[09:01] <_Sime> Riddell: some "int"s need to be replaced with "Py_ssize_t" in some of the hand written parts.
[09:01] <Riddell> Tonio_: what's in svn that isn't in beta 2?
[09:01] <Riddell> _Sime: ok, I've posted to pykde so we'll see if Jim answers, and we can worry about it if the python2.5 switch comes without hearing from him
[09:02] <Tonio_> Riddell: there is another development branch
[09:02] <_Sime> Riddell: good.
[09:02] <Tonio_> Riddell: http://websvn.kde.org/branches/work/kdebluetooth-dbus-integration/
[09:02] <Tonio_> this one includes all the dbus stuff to work with bluez 3
[09:02] <Tonio_> Riddell: the beta2 debian uses version doesn't, and still needs to be patched to use kbluepin correctly (but it works too)
[09:03] <Tonio_> Riddell: I finished the merge with beta2, but as dholbach plan was to use this new version instead, and as opensuse already uses it, I though it was probably better to work on that directly, and eventually submit the package to debian if it works
[10:50] <Riddell> Mez: around?
[10:50] <Mez> for 10 mins
[10:50] <Mez> sup
[10:51] <Riddell> Mez: I'm looking at katapult
[10:51] <Riddell> it's all blurg
[10:51] <Mez> ... ?
[10:52] <jdong> "
[10:52] <jdong> Noun, a small little known organ in the human body, located slightly medial and dorsal to the vermiform appendix, also referred to as the "love muffin."
[10:52] <Riddell> cool!
[10:53] <Riddell> but not what I ment
[10:53] <jdong> LOL
[10:53] <DaSkreech> Alt+spcae word:blug
[10:53] <Riddell> Mez: I can't see any difference in kubuntu_07_work_with_non_english.diff
[10:53] <Mez> Riddell, will tlak tomorrow
[10:58] <Riddell> infact it does add changes which are already in that file
[11:00] <Riddell> and the change to kubuntu_03_spellingcatalog.diff is already in kubuntu_07_work_with_non_english.diff
[11:02] <fdoving> diffs on diffs are nice :)
[11:07] <fdoving> Riddell: can you please upload kopete to feisty? -> http://ubuntu.lnix.net/feisty/kopete/ - fixes ftbfs on ppc and x86.
[11:07] <Riddell> fdoving: sure, in a bit
[11:14] <ryanakca> Riddell: d'you know of a "good" howto type thing for merging? the one on the MOTU school wiki doesn't really explain much...
[11:15] <Riddell> ryanakca: download ubuntu package, download debian package
[11:15] <Riddell> check if the ubuntu changes are still needed, if they aren't file a sync request
[11:16] <Riddell> if they are port the ubuntu changes to the debian package
[11:16] <Riddell> voila
[11:16] <ryanakca> ok... and how will I know if they're still needed? kindof a "It is or it isn't" obvious type thing?
[11:17] <Riddell> you need to search through the changelog to find out what the changes are
[11:17] <Riddell> and decide if the reson for adding the change is still a good reason
[11:17] <Riddell> usually you want to keep the change unless it has been included in debian
[11:18] <ryanakca> and "port the ubuntu changes to the debian package"... that means copying the patches over?
[11:19] <Riddell> yes, if its a patch in debian/patches, or it might be a packaging change, e.g. a lot of packages have dh_iconcache added to their debian/rules file
[11:20] <ryanakca> kk
[11:21] <ryanakca> thanks :)
[11:25] <Tonio_> Riddell: I'm merging koffice-i18n 1.6
[11:26] <Riddell> Tonio_: don't
[11:26] <Riddell> Tonio_: I have the 1.6.1 packages on my hard disk
[11:26] <Tonio_> Riddell: okay
[11:26] <Riddell> but it's not released yet
[11:26] <Tonio_> hum should be removed of the merging list then :)
[11:26] <Tonio_> perfect, I won't touch this and wait, ping me if you need testers
[11:27] <DaSkreech> Does ubiquity handle sata drives?
[11:27] <Riddell>  deb http://kubuntu.org/packages/not-koffice-161/ edgy main
[11:27] <Tonio_> Riddell: merging guidance packaging + sync from svn then
[11:27] <Riddell> DaSkreech: the live CD does, I wouldn't be surprised if qtparted got confused
[11:27] <Tonio_> I just hope the new icons are on the svn
[11:27] <Riddell> they should be
[11:29] <DaSkreech> So qtparted would not be helpful in fixing the problem?
[11:31] <lnxkde> DaSkreech: sup?
[11:32] <Riddell> DaSkreech: I don't know what your problem is
[11:32] <DaSkreech> Riddell: can you peek in the main chan?
[11:32] <Riddell> main chan?
[11:33] <DaSkreech> #kubuntu
[11:56] <fdoving> Riddell: there is a badly named patch in kdepim. attachment.cgi?id=17264&action=view
[11:57] <Riddell> fdoving: in fesity?
[11:57] <fdoving> Riddell: yes.
[11:57] <Riddell> that'll be my fault, but it won't cause any harm
[11:57] <fdoving> just FYI.
[11:57] <Riddell> thankks
[11:57] <Riddell> so, kopete
[11:57] <Riddell> where was that again?
[11:57] <fdoving> .. and i'm test-building with the kpilot fix.
[11:57] <Riddell> ooh, good plan
[11:58] <fdoving> http://ubuntu.lnix.net/feisty/kopete/
[12:01] <Riddell> fdoving: where did you get the patch from?
[12:01] <fdoving> Riddell: debian package.
[12:01] <Riddell> clever debian :)
[12:03] <fdoving> I don't have a palm, so i can't test,  but uploading to feisty won't hurt, i guess?
[12:04] <Riddell> I think seaLne has a palm?
[12:06] <fdoving> I'll continue this tomorrow. have to sleep.
[12:06] <fdoving> bye.
[12:06] <Riddell> sleep well fdoving
[12:06] <Riddell> I'm compiling kopete now and I'll upload it when it's done
[12:06] <fdoving> thanks :)


[03:54] <ashishk> .
 Forwarded from Mr.: Hello anyone there
 Forwarded from Mr.: Pls help me I'm in serious trouble
 Forwarded from Mr.: I installed lubuntu
 Forwarded from Mr.: Erased everything
 Forwarded from Mr.: I gave password 11digit
 Forwarded from Mr.: But in login page it's allowing me only 10digit
 Forwarded from Mr.: And if I enter first 10 digit it shows login failed
 Forwarded from Mr.: Pls help me😭
[18:54] <kryten> I'm guessing it's a keyboard layout issue really.
 In what way did it stop you from entering all 11 digits?
[18:55] <kryten> Or NumLock being turned off.
 Like ,after entering 10digits it stops taking characters (re @kc2bez: In what way did it stop you from entering all 11 digits?)
 That may be all that shows in the dialog box but I bet it takes all 11. Enter your complete password and press enter.
 Wait I'll send u the pic
 https://matterbridge.lubuntu.me/5ebd496a/file_2551.jpg
 https://matterbridge.lubuntu.me/65c4f5e2/file_2552.jpg
 It's allowing only 10 digits
 Right, but it will accept all 11 even if it doesn't show.
 No , it's not taking 😞
 It's allowing only 10
 Any other ways
 is that particular key still functional?
 Mean?
 the 11 digit
 the key you press
 does that key still work?
 Yup ,but it takes only 10
 is it possible to install an other login manager using tty and login via the new login manager?
 Right now I have only lubuntu
 I erased completely
 While partition
 @kc2bez
 could this be a solution? (re @Michaël: is it possible to install an other login manager using tty and login via the new login manager?)
 I find it odd that it doesn't work with 11 digits, I have used larger passwords multiple times. I would probably circle back to the keyboard layout.
 we can check the keyboard layout using tty
 Mr.  could try to type his password in the user name space
 not pressing enter of course
 but the keyboard layout is visible then
 right, good idea on the tty.
 Mr. do you know how to open the tty?
 Nope sir ,how ?
 I never heard of it
 press ctrl+alt+f2
 it'll ask for you user name
 in that field you can test your keyboard layout
 I'm there
 try your keyboard layout
 it's possible even when even the led from num lock is on num lock is off
 so you might want to press that num lock key
 https://matterbridge.lubuntu.me/cf1eb342/file_2553.jpg
 that the tty :)
 in there you can test your keyboard layout
 What Should I type in login
 Username?
 in your case your password
 see you password appears on the screen as you want it to be
 if not
 it could be related to your keyboard layout
 don't press enter
 In login: I entered the password
 And pressed enter
 does the password appear as you want it to be?
 Yes
 did you reboot your machine after you encountered this the first time?
 But when I press enter it takes me to the second line asking password:
 Yes (re @Michaël: did you reboot your machine after you encountered this the first time?)
 doesn't matter in our case now (re @Mr.: But when I press enter it takes me to the second line asking password:)
 you could login in using tty
 but you'll be left with terminal then
 of your login manager doesn't accept an 11th digit
 I don't know what to do with that
 Can't I do anything boot manager  and other options
 to humor me
 could you just give it a try
 login using tty
 and reboot
 so first enter your user name
 and next it'll ask for the password
 when you're logged in
 type reboot
 Steps?
 Now ,I'm in tty
 Page
 It's asking for login:
 yes
 login is the question to enter your user name
 What should I enter
 i'd think it's aston (re @Mr.: )
 i think that's your user name
 Yup
 next it should be asking for your password
 Wait. Wait
 I entered aston in login:
 Should I press enter
 yes
 you want to confirm your pc that's the whole user name
 I entered password in password:
 ok
 like you did with the user name
 confirm you're finished typing your password by pressing enter
 It's showing login incorrect
 where you ever able to login after installation?
 No
 In lubuntu safe I installed lubuntu and I erased windows
 do you think it's possible while you where installing and you had to enter your preferred password the first time that it went wrong there?
 In tty the underscore cursor is not moving while entering password
 I remember it asked me two times (re @Michaël: do you think it's possible while you where installing and you had to enter your preferred password the first time that it went wrong there?)
 Password and retype the password
 that's not an odd thing (re @Mr.: In tty the underscore cursor is not moving while entering password)
 many more distro's act in this way
 And I saw a green tick (re @Mr.: Password and retype the password)
 When I retuped the password
 In installation process
 I don't think the underscore moves, it is actually a security measure so that folks looking over your shoulder don't know the length of the password. (re @Mr.: In tty the underscore cursor is not moving while entering password)
 Pardon i didn't know (re @kc2bez: I don't think the underscore moves, it is actually a security measure so that folks looking over your shoulder don't know the length of the password.)
 I'm new to lonux
 I don't know why the hell it's not allowing 11 characters
 In password
 Mr. do you recall wether numlock was on or not during installation?
 because standard it's turned off
 I didn't have any numbers in my password
 personally i do not see any option left but to reinstall :/
 How can I do that
 the way your installed Lubuntu
 repeat the process
 I don't have other os left
 do you have your installation media with you?
 Like?
 I have my pendrive
 use your pendrive to reinstall
 Were you able to login using the tty?
 no (re @kc2bez: Were you able to login using the tty?)
 Nope
 Ah,
 Now how should I reintall
 what did you do the first time?
 you have to repeat that
[19:42] <Maik> @Mr. reset your password, also in case you forgot it: https://easylinuxtipsproject.blogspot.com/p/forgotten-password.html
[19:42] <Maik> hope it helps
 Wait
 I pressed ESC while the lap was starting
 And then I arrived at boot manager
 And clicking usb hard drive
 F9 (re @Mr.: And then I arrived at boot manager)
 Is it applicable for lubuntu also (re @lubuntu_bot: (irc) <Maik> @Mr. reset your password, also in case you forgot it: https://easylinuxtipsproject.blogspot.com/p/forgotten-password.html)
[19:51] <Maik> Of course
 Thank you ❤  I'm reinstalling lubuntu
 And it's working
 ❤❤❤
 💯😭
[20:38] <mario_> olá


[06:10] <mat_benjut> hai all
[06:10] <mat_benjut> how to get ubuntu cloack? should i talking with the operator?
[06:55] <pangolin> !cloak
[06:56] <mat_benjut> hai pangolin
[06:56] <mat_benjut> i already registered my nick
[06:56] <mat_benjut> should i ask / talk with the op? or?
[06:56] <mat_benjut> to get the cloak
[06:57] <pangolin> have you applied for ubuntu membership already?
[06:57] <mat_benjut> yes
[06:57] <mat_benjut> launchpad?
[06:58] <pangolin> please link to your launchpad account
[06:58] <mat_benjut> https://launchpad.net/~oktav-android
[06:59] <pangolin> ok, you do not appear to be a approved Ubuntu member.
[06:59] <pangolin> !membership
[06:59] <mat_benjut> oh
[06:59] <mat_benjut> i see
[06:59] <mat_benjut> thanks for ur info
[06:59] <pangolin> take a look at that info ubottu just linked
[07:00] <mat_benjut> yap
[07:00] <mat_benjut> thanks pangolin
[07:00] <mat_benjut> :)
[07:00] <pangolin> very welcome
[09:15] <Myrtti> jpds: hi
[09:16] <jpds> Myrtti: Hello.
[09:16] <Myrtti> jpds: have you seen the cries for help about the ubottu clones?
[09:17] <jpds> Myrtti: Yes; just got back from holiday.
[09:17] <Myrtti> jpds: great, just checking :-) hope you had a good one
[09:17] <Myrtti> great timing btw
[09:17] <jpds> It was brilliant; getting back into action now.
[09:45]  * popey hugs jpds
[09:48]  * jpds hugs popey
[10:13] <elky> omg, it's alive
[17:02] <AlanBell> jpds \o/
[17:24] <Myrtti> lubotu3: !info htop
[20:22] <Nafallo> ubot2 is going down for a little hardware maintenance.
[20:22] <ubot2> Nafallo: Error: I am only a bot, please don't think I'm intelligent :)
[20:22] <Nafallo> jpds: ^--


[02:04] <imgbot> [03:54] <imgbot> [03:54] <imgbot> [07:57] <pstolowski> trainguards hello, can landing 012 get landed? is there still a problem with this silo?
[08:07] <ev> In case that wasn't enough to catch your eye, the CI Lab is being moved today at 1300 UTC. Expect no tests to run at this time, but no action needed on your part once services are restored. See Larry's email for the full details.
[08:16] <pstolowski> ev, ack. thanks
[08:22] <sil2100> pstolowski: let me take a look at it in the meantime
[08:24] <Mirv> pstolowski: it is landed already, it's just stuck in proposed
[08:24] <Mirv> sil2100: I asked you or robru to try to take the Oxide silo to finish on Friday, but that is essentially what's blocking 012 and others
[08:24] <Mirv> I don't now have upstream approval but I do have core dev approval
[08:25] <sil2100> Mirv: sadly, I wasn't able to take care of that, I wanted after the evening meeting but then some personal matters appeared
[08:26] <Mirv> sil2100: yeah, no problem, I just would have wanted for someone to catch up with Chris. but I think I can now land that soon with raof's ack on it.
[08:26] <Mirv> sil2100: in the morning I realized he could have noticed it better if I'd have proposed a branch in addition to just filing the bug.. but earlier I didn't even know where the Oxide packaging branch is.
[08:27] <sil2100> I actually thought this was a revert, but I see it's actually a fix
[08:27] <Mirv> sil2100: the revert would have been easy to push, but then it would have (again) broken all Click cross-compilation for vivid
[08:27] <Mirv> so that's why at the last minute I made that zoltan's suggested fix/workaround for the problem
[08:30] <Mirv> ... which then took the usual 5h to build :)
[08:30] <sil2100> ...;)
[08:36] <pstolowski> Mirv, sil2100 thanks
[09:25] <sil2100> brendand: hey! How many QA people do we have for silo testing today in the EU tz?
[09:26] <brendand> sil2100, all of them :)
[09:26] <sil2100> Good, since I see silo 007 has a fix for one of the criticals
[09:26] <sil2100> Would be nice to have this one handled
[09:28] <jibel> sil2100, I guess there is no discussion about silo 16? it's a major change and risk is very high.
[09:28] <davmor2> brendand: the correct answer then would of been None we have all gone on strike
[09:29] <sil2100> jibel: silo 16 is very important to land - very risky, but required
[09:30] <jibel> sil2100, okay, so we test it and build a separate image with just this fix?
[09:30] <jibel> s/fix/new version/
[09:30] <sil2100> For sure we'll build an image once this lands
[09:31] <sil2100> I remember on Friday someone mentioning some issues with the silo installing cleanly, but I don't remember what that was
[09:31] <jibel> sil2100, right, but just with upower 0.99?
[09:31] <sil2100> jibel, brendand, Mirv: I'll be right there on the HO
[09:31] <sil2100> Need to restart the browser
[09:32] <sil2100> hmm, no ogra on the channel!
[09:48] <mzanetti> sil2100: hi. when you have a minute, could you please assign me a silo for row 32
[09:49] <sil2100> mzanetti: sure, looking
[09:49] <sil2100> mzanetti: ah, sorry, can't do that - still waiting for silo 12 to migrate...
[09:50] <mzanetti> sil2100: ah ok. no prob.
[09:50] <sil2100> mzanetti: but the good news is: it will migrate soon!
[09:52] <davmor2> sil2100: hmmm I wonder unity-plugin-scopes:armhf from 0.5.4+15.04.20141128-0ubuntu1 to 0.5.4+15.04.20141205-0ubuntu1 in image 45 :)
[09:57]  * sil2100 checks the commitlog
[09:58] <davmor2> sil2100: http://people.canonical.com/~davmor2/scopes-all-v44.png image 44 scopes are there moving onto 45
[10:03] <sil2100> robru: hm, did you change anything in the train that made the released package versions not appear?
[10:05] <sil2100> robru: yeah, I see pkgversionlist gone from the JSON blobs
[10:05] <sil2100> robru: this breaks commitlogs...
[10:06] <sil2100> Now we can't keep track of what landed in what image ;/
[10:06] <seb128> time for revert!
[10:10] <sil2100> seb128: if you meant the train, it's not so easy anymore! ;) I would need IS to do it for me..!
[10:10] <seb128> oh?
[10:10]  * sil2100 has absolutely no control over the train deployments anymore
[10:10] <seb128> "great"
[10:11] <seb128> so you can get stuff broken but not fixed
[10:11] <sil2100> But I won't be ranting about this, did enought of that last week
[10:11] <seb128> improvements?
[10:14] <davmor2> Saviq: y u break the scopes
[10:15] <Saviq> davmor2, no me, pstolowski!
[10:16] <bzoltan> sil2100:  may I ask for a reconf - silo9
[10:16] <davmor2> Saviq: I don't care I'm blaming you, you probably told him to land it ;)  I've just confirmed though that it is definitely 45 that broken 44 works fine :)
[10:17] <sil2100> bzoltan: sure!
[10:17] <sil2100> bzoltan: what changed? :)
[10:17] <Saviq> davmor2, ah right, sorry, yes, my fault
[10:17] <sil2100> Ah, gles
[10:17] <sil2100> bzoltan: reconfiguring
[10:34]  * Mirv rerunning autopkgtests
[10:36]  * Mirv was apparently too early, tries again later
[11:14] <sil2100> Mirv: any luck? ;)
[11:15] <sil2100> davmor2: are you also doing silo sign-off today?
[11:16] <Mirv> sil2100: ^ qtdeclarative already migrated. the other autopkgtest now also finished so I expect the rest to follow inside 30 mins or so!
[11:16] <davmor2> No I'm reviewing the sanity suite adding a testcase for the scopes issue and testing the latest images
[11:16] <sil2100> davmor2: ACK, since all should be fixed once we have the new unity8
[11:16] <Mirv> sil2100: the bad news was that chrisccoulson informed the change is not wanted, and I filed bug #1400275 to summarize the whole situation. my error was also that I thought Chris was in US...
[11:16] <ubot5`> bug 1400275 in oxide-qt (Ubuntu Vivid) "Fix oxide-qt codecs dependencies (continued)" [Critical,New] https://launchpad.net/bugs/1400275
[11:17] <sil2100> He's not?
[11:17] <sil2100> Oh
[11:17] <Mirv> :)
[11:17] <davmor2> sil2100: indeed but it is still a good testcase for the future :)
[11:17] <sil2100> Damn, we should have checked
[11:18] <davmor2> sil2100, Mirv: no chrisccoulson is about 25 miles from me, if you'd of asked I could of told you that :P
[11:18] <chrisccoulson> hi :)
[11:19] <Mirv> davmor2: it's probably by luck that I didn't use the phrase "because Chris is in the US" during the meeting..
[11:19] <Mirv> chrisccoulson: hi :)
[11:19] <davmor2> chrisccoulson: hey there how is Solihull :)
[11:20] <Mirv> chrisccoulson: my next idea would be to revert the ordering change but try that RAOF's guess of using arch specific Replaces lines.. otherwise I'm out of ideas though.
[11:29] <Mirv> Saviq pstolowski: vivid 012 now migrated to release pocket too, feel free to go ahead with next landings ^
[11:29] <Saviq> Mirv, thanks
[11:29] <Saviq> Mirv, can you assign line 32 a silo please
[11:30] <Mirv> Saviq: yep, although it seems pstolowski would also want to grab unity8 again (on the last line), I wonder if it could be merged into yours or if he needs to just wait
[11:30] <Saviq> Mirv, ah indeed, merge
[11:31] <Mirv> Saviq: wow, indicator-power in silo 4
[11:31] <Saviq> um
[11:32] <Mirv> Saviq: seems pretty inactive though
[11:32] <Saviq> Mirv, indeed, I hope to land before charles and tedg wake up ;)
[11:33] <Saviq> Mirv, ok, line 32 has it all
[11:34] <Mirv> Saviq: assigned, but reconfiguring still since you added the new one
[11:34] <Saviq> Mirv, thanks
[11:35] <Mirv> Saviq: ready now
[11:35] <Saviq> Mirv, thanks
[11:41] <jibel> sil2100, nothing landed in RTM since 173?
[11:43] <sil2100> jibel: nothing, just checked the changes list
[11:44] <sil2100> Mirv, Saviq: what do you guys say for building a new vivid image to get rid of some of the breakages?
[11:44] <Saviq> sil2100, definitely
[11:44] <pstolowski> Mirv, thanks!
[11:45] <Saviq> pstolowski, actually, I left your silo request be, there's some doubts on Albert's MP
[11:45] <Mirv> sil2100: sounds like a good idea with all that migrated now
[11:45] <Saviq> pstolowski, but Mirv, feel free to assign a silo for pstolowski if you have the space
[11:45] <pstolowski> Saviq, i was going to say exactly that..
[11:45] <Saviq> we'll make sure to coordinate
[11:45] <Mirv> even my qtdeclarative crasher fixes might be happily received by some
[11:45] <pstolowski> Saviq, my silo may take a bit longer to get green light, i need tsdgeos tomorrow
[11:46] <Saviq> pstolowski, yup, I gathered as much
[11:46] <Mirv> Saviq: pstolowski: yes sure, I forgot about it. we've plenty of silos nowadays, I wonder if people are having golden image hangover...
[11:47] <Mirv> or well rtm has many silos, maybe then for vivid not all teams have a feature roadmap of what to actually implement in addition to just fixing ota-1 bugs.
[11:48] <Mirv> hmm, how did that https://code.launchpad.net/~aacid/unity8/deparment_jumping/+merge/243639 come back to the line 42... removing
[11:49] <Mirv> Saviq: I don't see it anymore on your line either
[11:49] <Saviq> Mirv, waait
[11:49] <Mirv> did the spreadsheet revert itself?
[11:49] <Saviq> Mirv, no
[11:49] <Saviq> Mirv, I split the silo up after all
[11:49] <Saviq> Mirv, as pstolowski's not gonna be ready until tomorrow at least
[11:50] <Mirv> Saviq: oh.. ok, makes sense. so, assining by ignoring conflicts.
[11:50] <Saviq> Mirv, yes please
[11:50] <Saviq> thanks and sorry for the confusion :)
[11:50] <Mirv> and pstolowski will rebuild unity8 tomorrow
[11:50] <Mirv> no problem
[11:51] <pstolowski> yup, thanks
[12:25] <brendand> sil2100, silo 16 ready to go
[12:30] <Mirv> brendand: \o/
[12:31] <Mirv> sil2100: publishing
[12:32] <Mirv> and acking a core-dev's own packaging change
[12:33] <davmor2> Saviq: for when you fix it unless there is one already https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1400296
[12:33] <ubot5`> Launchpad bug 1400296 in unity8 (Ubuntu) "No scopes are visible in the all page of the manage scopes page" [Critical,New]
[12:34] <Saviq> davmor2, it is
[12:34] <Saviq> davmor2, fixed I mean
[12:34] <davmor2> Saviq: yeah I had assumed it was :)
[12:35] <Saviq> pstolowski, can you please set the correct task statuses ↑?
[12:45] <davmor2> Saviq: thanks for updating it :)
[12:46] <pstolowski> Saviq, done
[12:51] <Saviq> pstolowski, << 8.02!
[12:53] <pstolowski> Saviq, grr. ok, fixed
[13:11] <jibel> sil2100, can you build an image with the changes to support new upower only (upower, powerd, system-settings, indicator-power) ?
[13:12] <sil2100> jibel: let me check if anything else landed
[13:12] <jibel> I didn't see anything
[13:13] <sil2100> Ok, it seems only this landed
[13:13] <sil2100> Mirv: don't publish anything for now
[13:13] <jibel> sil2100, so then we can continue landing stuff and have a build with upower 0.99 isolated.
[13:15] <sil2100> jibel: ok, ogra will kick it off in a minute
[13:16] <sil2100> We don't have imgbot so we won't get any notification though
[13:16] <jibel> sil2100, thanks
[13:29] <Mirv> sil2100: ok
[13:29] <sil2100> Mirv: once the rootfs for the new image is ready, we'll resume landings
[13:29] <sil2100> jibel, brendand: just in case, please continue with silo testing btw. - we'll simply not publish
[13:30] <sil2100> jibel, brendand: although I would recommend skipping any system-settings silos from sign-off
[13:30] <sil2100> Since we need to rebuild those now that silo 16 landed
[13:37] <davmor2> sil2100, Saviq: the fix for the scopes issue is there anyway to get that landed and in an image today, that way we could look at another promotion for vivid tomorrow image 47 is way better that anything to date :)
[13:45] <sil2100> davmor2: so all the previous issues with media playback and such are gone? :)
[13:46] <davmor2> sil2100: indeed :)
[13:46] <sil2100> \o/
[13:47] <davmor2> sil2100: it's not rebooting constantly either?
[13:48] <pstolowski> Mirv, hey, silo 12 landed but libunity-api from that silo still not in vivid?
[13:49] <Mirv> pstolowski: yes it is? https://launchpad.net/ubuntu/+source/unity-api/7.94+15.04.20141205-0ubuntu1
[13:50] <pstolowski> Mirv, ah, ok that version looks good.. somehow I still can't update to it.. mirror not up to date I guess
[13:56] <Mirv> pstolowski: probably so. I've given up mirrors to get 30min faster updates ;)
[14:33] <brendand> Mirv, what do i need to install as a minimum to build qt packages?
[14:34] <brendand> Mirv, i need to build that test app from lorn
[14:40] <Mirv> brendand: I built it on my mako from a fresh flash. let me summarize it as: apt install qtbase5-dev build-essential , export QT_SELECT=qt5 , qmake , make , ./InternetCheckercmd ( I didn't test it for real yet other than launching )
[14:55] <rsalveti> Mirv: sil2100: are you guys planning another rtm build soon?
[14:55] <rsalveti> just because of the latest upower related changes
[14:56] <sil2100> rsalveti: we had one already
[14:56] <rsalveti> hm, guess the bot is dead then
[14:56] <rsalveti> let me try downloading it
[14:56] <sil2100> rsalveti: we built a new image when these migrated, but from what ogra mentioned all platforms got imported besides krillin
[14:56] <sil2100> And we're not sure why
[14:56] <rsalveti> haha, right
[14:57] <rsalveti> that's it then
[14:57]  * sil2100 waits for stgraber to pop up
[14:57] <sil2100> ;)
[15:08] <sil2100> Ursinha: hey! I just remembered something that we need in the spreadsheet replacement that we missed most probably during all the discussions previously
[15:10] <Ursinha> sil2100: go ahead
[15:10] <Ursinha> I
[15:10] <Ursinha> I'm "listening"
[15:11] <Ursinha> :)
[15:11] <sil2100> Ursinha: we have a column in the spreadsheet, column 'S', which includes information about which packages and versions have been released with the given landing
[15:11] <sil2100> Ursinha: this is being used by many tools to get information on what landing did what
[15:12] <sil2100> (like the commitlogs)
[15:12] <sil2100> Ursinha: once a package is published from the silo, it gets included there in the format "source_name=1.2.3"
[15:12] <sil2100> Currently it's space separated
[15:16] <sil2100> plars: btw. the full lab move is not happening today, right?
[15:17] <plars> sil2100: no, it IS happening today
[15:18] <sil2100> plars: oh, ok, since I saw an e-mail from psivaa_ mentioning it was postponed
[15:18] <plars> sil2100: postponed from last week
[15:18] <sil2100> Aaaaah, crap, ok
[15:18] <sil2100> I think I was really sleepy when I read that
[15:25] <Ursinha> sil2100: so you're saying that is information about the sources that were published to the main archive?
[15:25] <Ursinha> just so I can understand when is that information used
[15:26] <sil2100> Ursinha: yes, information about what version of which package this silo has released to the archive after publishing
[15:27] <Ursinha> sil2100: and that's used after the landing is completed and the silo is gone
[15:27] <sil2100> Basically yes
[15:30] <Ursinha> sil2100: so that is already part of the ticket information, if a package in a silo was published I can say for sure that it was the latest version of that package in the silo PPA, right?
[15:32] <sil2100> Ursinha: yes - if this information is persistent even after the silo is freed and accessible by some API, then I have all we need
[15:32] <sil2100> kenvandine: hey!
[15:32] <kenvandine> hey sil2100
[15:33] <sil2100> kenvandine: since silo 16 landed, I think we need to rebuild one of the 2 silos with system-settings
[15:33] <sil2100> kenvandine: which one would you like to land first?
[15:33] <kenvandine> cool!
[15:33] <kenvandine> 4
[15:33] <kenvandine> i'll do a rebuild
[15:33] <sil2100> Let's set the other one to untested then, to make sure we don't pick it up by accident
[15:34] <sil2100> Done
[15:34] <sil2100> kenvandine: thanks :)
[15:34] <Ursinha> sil2100: :) can you have a look at the spreadsheet and tell me if there are any other cases like that? just so we can avoid surprises on missing features we overlooked
[15:36] <sil2100> Sure, I suppose those are all the cases from my side, need to think about if anyone else was using it as well
[15:38] <kenvandine> sil2100, oh... it hasn't been merged yet
[15:38] <kenvandine> i'll need to rebuild again
[15:39] <sil2100> huh?
[15:39] <sil2100> silo 16?
[15:39] <sil2100> hmmm
[15:39] <kenvandine> sil2100, yeah, it's still in proposed and not merged
[15:40] <sil2100> CRAP
[15:40]  * sil2100 checks that
[15:41] <sil2100> kenvandine: so there seems to be a problem with it, looking at update_output.txt now
[15:42] <kenvandine> uh oh
[15:42] <sil2100> popey: what issues did you have with installing silo 16?
[15:42] <sil2100> popey: you mentioned it was 'non-trivial'
[15:42] <kenvandine> i think you have to install it in the chroot from recovery or something
[15:43] <sil2100> leading: upower,ubuntu-system-settings
[15:43] <sil2100>     * armhf: account-plugin-ubuntuone, firefox-testsuite, gnome-control-center, gnome-session-bin, gnome-settings-daemon, indicator-bluetooth, libonline-accounts-plugin-dev, powerd, ubuntu-desktop-next, ubuntu-push-autopilot, ubuntu-system-settings, ubuntu-system-settings-online-accounts, ubuntu-system-settings-wizard, ubuntu-touch, unity-control-center, unity-control-center-signon, unity-scope-click, unity-settings-daemon
[15:44] <sil2100> hmmm
[15:44] <sil2100> Mirv, robru: ^ don't publish anything for now
[15:47] <kenvandine> sil2100, ok, now silo 4 won't build because it needs the merge of the upower branch
[15:47] <kenvandine> i'll just sit tight and rebuild after i see that is sorted out
[15:49] <sil2100> I wonder what's going on
[15:54] <popey> sil2100: pmcgowan has a guide
[16:00] <brendand_> Mirv, 22 does seem to makes things better but there's still some curious behaviour i'm unsure of
[16:00] <brendand_> lpotter, are you around?
[16:00] <pmcgowan> silo 16 landed?
[16:01] <brendand_> pmcgowan, yes
[16:01] <pmcgowan> kenvandine, did you see my comment, it all worked fine and helps greatly but settigns till processes events on wakeup, just many fewer it seems
[16:01] <pmcgowan> brendand_, good
[16:02] <pmcgowan> kenvandine, I wonder if we need to also filer those events in settings, throw all but the last one out or something
[16:02] <pmcgowan> filter
[16:03] <sil2100> pmcgowan: actually it didn't land yet
[16:04] <sil2100> It's released, but blocked in -proposed
[16:04] <pmcgowan> ok
[16:06] <sil2100> kenvandine: I think it might be related to libupower-glib3 :|
[16:06] <kenvandine> pmcgowan, yeah, not sure what's happening there
[16:06] <sil2100> kenvandine: libupower-glib1 changed to libupower-glib3 and all the rdeps weren't rebuilt
[16:06] <kenvandine> we can debug that further, it might not be related
[16:06] <kenvandine> sil2100, yeah
[16:06] <pmcgowan> kenvandine, I suspect we get some set of power events, just a reasonable number
[16:06] <sil2100> So those might now be uninstallable on rtm
[16:06] <kenvandine> but there shouldn't be many in rtm?
[16:08] <kenvandine> sil2100, my build failure is because to build with the new upower, it needs that branch that hasn't merged yet
[16:08] <sil2100> account-plugin-ubuntuone, firefox-testsuite, gnome-control-center, gnome-session, gnome-session-bin, gnome-settings-daemon, indicator-bluetooth, libonline-accounts-plugin-dev, powerd, ubuntu-desktop-next, ubuntu-push-autopilot, ubuntu-session, ubuntu-system-settings, ubuntu-system-settings-autopilot, ubuntu-system-settings-online-accounts, ubuntu-system-settings-online-accounts-autopilot, ubuntu-system-settings-wizard, ubuntu-touc
[16:08] <kenvandine> so it's trying to build silo 4 with upower 0.99
[16:09] <kenvandine> but without the fix to build with upower 0.99
[16:10] <seb128> sil2100, kenvandine, there is gnome-session gnome-control-center gnome-settings-daemon unity-settings-daemon unity-control-center which are using -glib1 in the rtm serie
[16:10] <kenvandine> why are those even in the rtm series?
[16:10] <seb128> dependencies
[16:11] <seb128> like unity8 uses unity-schemas which comes from unity7 which depends on u-c-c
[16:11] <seb128> well, making that one up
[16:11] <seb128> but it's things like that
[16:11] <kenvandine> understood
[16:11] <kenvandine> surprised about gnome-session and gnome-control-center
[16:11] <seb128> well
[16:12] <kenvandine> i guess when we checked the rdepends, we checked it from an rtm device
[16:12] <kenvandine> maybe we don't have all of those for armhf?
[16:12] <seb128> we do
[16:12] <seb128> I just built the list I gave you by running rdepends on my krillin rtm
[16:18] <om26er> renato___, Hi!
[16:18] <om26er> renato___, I am testing silo for bug 1390128
[16:18] <ubot5`> bug 1390128 in Canonical System Image "[address-book] is stuck on contacts sync dialog & becomes unusable" [Critical,Confirmed] https://launchpad.net/bugs/1390128
[16:19] <om26er> renato___, with the bug fixing silo step 7 is a bit different. Now the sync dialog does not appear at all. Is that expected ?
[16:24] <sil2100> kenvandine: we need the all i386 dependencies resolved as well
[16:24] <sil2100> kenvandine: will you take care of pushing all package rebuilds to the rtm archive?
[16:26] <sil2100> kenvandine: I can give you a silo, but I suppose we can just push that directly to the archive
[16:30] <kenvandine> sil2100, isn't there a way to create a silo just to trigger rebuilds?
[16:31] <sil2100> kenvandine: sadly, you would have to dput those to the silo PPA directly, or submit no-change merges etc.
[16:31] <kenvandine> i need to step away for a few, bbs
[16:32] <sil2100> kenvandine: so I guess it's faster to just dput to the archive, since you're a core-dev :)
[16:38] <renato___> om26er, the dialog only apppear at the first time if there is no contacts
[16:38] <renato___> om26er, if you create a contact the dialog will not appear anymore
[16:39] <om26er> renato___, aah, ok.
[16:47] <sil2100> Ok, maybe in the meantime I'll try resolving those
[16:49] <seb128> ^ how do I talk to "QA" about testing that one?
[16:49] <seb128> it's not really something that can be tested
[16:50] <seb128> the change makes the package build generate a .pot for launchpad to import
[16:50] <seb128> so you can't really "test" that on the device
[16:50] <seb128> I tried to explain that in the test plan column, but feel free to ping me if you have questions
[17:04] <seb128> om26er, ^ do you know?
[17:07] <kenvandine> sil2100, so no udd branches for 14.09?  i need to fetch sources the old fashion way?
[17:07] <om26er> seb128, no, not really, however brendand_ may know
[17:08] <brendand_> seb128, i think it's clear
[17:08] <seb128> brendand_, ok, thanks
[17:16] <sil2100> kenvandine: I would do apt-get source normally, and deal with bzr later ;)
[17:16] <sil2100> (if needed)
[17:16] <kenvandine> yeah, figured
[17:17] <kenvandine> but then i have to add rtm to my sources :)
[17:17] <kenvandine> i'll figure it out :)
[17:18] <sil2100> You mean, to dput.cf?
[17:18] <kenvandine> i bet we have a script for this sort of thing
[17:18] <kenvandine> no...
[17:18] <kenvandine> to checkout the source
[17:18] <kenvandine> not checkout, download :)
[17:19] <kenvandine> i wonder if any of those needed changes when they did the transition in vivid
[17:19] <sil2100> We can try building this in a silo PPA first then
[17:19] <sil2100> To make sure
[17:19] <kenvandine> yeah, lets do that
[17:19] <kenvandine> can you create me a silo?
[17:20] <sil2100> kenvandine: sure, doing :)
[17:20] <kenvandine> thx
[17:21] <sil2100> kenvandine: assigned!
[17:22] <kenvandine> thx
[17:35] <boiko> trainguards, can I get rtm silo 003 reconfigured? I added a new component there
[17:35] <robru> boiko: on it
[17:39] <boiko> robru: thanks!
[17:39] <robru> boiko: you're welcome!
[17:46] <sil2100> kenvandine: any luck? :)
[17:47] <kenvandine> well, i just had my first upload to the ppa rejected :/
[17:47]  * sil2100 doesn't see any packages in teh silo
[17:47] <kenvandine> bad distro series 14.09?
[17:47] <kenvandine> should i just set that to utopic?
[17:47] <sil2100> kenvandine: remember to suffix the version with rtm
[17:47] <sil2100> hm, should work
[17:47] <sil2100> Are you pushing to the ubuntu-rtm PPA for sure?
[17:48] <kenvandine> well, i was versioning it like an SRU... since there are updates in utopic that are later
[17:48] <kenvandine> oh... i copied the dput line from LP
[17:48] <kenvandine> forgot those are wrong
[17:48] <sil2100> kenvandine: yeah ;)
[17:48] <sil2100> kenvandine: well, I usually do it like this:
[17:48] <kenvandine> what should it look like?
[17:48] <sil2100> kenvandine: if the ubuntu version is 0ubuntu3, I change it to 0ubuntu3rtm1
[17:48] <sil2100> Not sure if that's super correct though :)
[17:48] <kenvandine> ok
[17:49] <kenvandine> i did 3.9.90-0ubuntu13.1
[17:49] <kenvandine> i can change it though
[17:50] <kenvandine> sil2100,  how do i specify the rtm ppa?
[17:52] <sil2100> kenvandine: well, I would be afraid with such a version number when in utopic we make an SRU or somewhere else, there's risk that we can get the same version number
[17:52] <sil2100> kenvandine: usually using ppa:team-name/ubuntu-rtm/ppa-name should be enough
[17:53] <kenvandine> true, i changed the version
[17:55] <kenvandine> ppa:ci-train-ppa-service/ubuntu-rtm/landing-014
[17:55] <kenvandine> sil2100, ^^
[17:55] <kenvandine> sil2100, also failed, this time can't find suite 'ubuntu'
[17:56] <kenvandine> maybe i need to tweak my dput.cf
[17:59] <sil2100> hmmm
[17:59] <sil2100> kenvandine: how does your global dput.cf look like in the [ppa] section?
[18:00] <kenvandine> sil2100, i had that in my own .dput.cf
[18:01] <kenvandine> old stuff
[18:01] <kenvandine> i removed mine... lets see if that helps
[18:06] <sil2100> kenvandine: did it help?
[18:07] <kenvandine> yeah, all uploaded now
[18:07] <robru> sil2100: so I got that set_package_version_list in trunk, just waiting to get ahold of IS to deploy that for us
[18:09] <kenvandine> sil2100, so once all these build, i need to do a watch only build on the silo right?
[18:09] <sil2100> robru: thanks :)
[18:09] <sil2100> kenvandine: yes
[18:09] <robru> sil2100: you're welcome
[18:09] <sil2100> kenvandine: if! We don't get any failures ;p
[18:11] <kenvandine> sil2100, have confidence :)
[18:25] <robru> sil2100: hey I just got the publish fix in production, do you have anything publishable to test with?
[18:25] <robru> (I mean it totally is guaranteed to work, I just like to see it working while I have the IS guy's attention...)
[18:26] <sil2100> robru: not yet, since we have some ubuntu-rtm stuff ready but we're waiting for unblocking -proposed and getting an image ;/
[18:27] <robru> sil2100: ok well when you do finally publish something just keep an eye out for the published version list thing working and if not, ping me and I'll investigate why it didn't work (but it really has to work since it's just a single function call to a tested function, so i can't imagine anything going wron)
[18:27] <sil2100> robru: I just hope it'll serialize to JSON nicely
[18:27] <sil2100> And in this case we'll have to modify the spreadsheet scripts
[18:28] <sil2100> Since they're not expecting a list of versions (probably)
[18:29] <robru> sil2100: funny because the function was named set_package_version_list all along ;-)
[18:30] <robru> sil2100: ah so indeed set() isn't valid json
[18:30] <robru> sil2100: good call
[18:30] <robru> ;-)
[18:30] <robru> what could go wrong?
[18:30] <sil2100> robru: that's why I changed it to a dictionary originally, since I didn't know about the usage of a set there - and I was worried it won't JSONize
[18:31] <robru> sil2100: ok I'll fix that
[18:31] <sil2100> (by usage of a set I mean I didn't know about the dual-landing requirements of that ;) )
[18:38] <sil2100> kenvandine: we have failures :|
[18:39] <kenvandine> bugger!
[18:39] <sil2100> :|
[18:40] <kenvandine> sigh... we'll need to pull in some utopic fixes :/
[18:40] <kenvandine> or vivid actually
[18:40] <sil2100> https://launchpadlibrarian.net/188684555/gnome-control-center_1%3A3.12.1-5ubuntu2_1%3A3.12.1-5ubuntu3.diff.gz
[18:41] <sil2100> This seems to help for g-c-c
[18:44] <kenvandine> sil2100, no, g-c-c in rtm is 3.8.6
[18:44] <kenvandine> not 3.12.1
[18:44] <alexabreu> trainguards can you reconfigure RTM silo 13 (L39) ?
[18:44] <robru> sil2100: right. defaultdict json-izes into a dict but you're right that set() doesn't json-ize. just pushed a fix for that
[18:44] <sil2100> :<
[18:44] <kenvandine> none of the packages are in the touch images, maybe we could just sync them from vivid?
[18:45] <robru> alexabreu: one sec
[18:45] <sil2100> kenvandine: might be a good idea, but... I hope they won't require any new deps
[18:45] <sil2100> kenvandine: let's try that, give me a moment to prepare the sync line
[18:46] <kenvandine> sil2100, thanks... i appreciate that
[18:46] <robru> alexabreu: done
[18:46] <alexabreu> robru, thx
[18:46] <robru> alexabreu: you're welcome
[18:46] <robru> sil2100: ok try publishing something now ;-)
[18:47] <sil2100> robru: we'll have something soon (I hope!)
[18:47] <sil2100> kenvandine: ok, syncing
[18:47] <sil2100> Damn it ;/
[18:48] <sil2100> kenvandine: ok, huston, we might have a problem
[18:48] <sil2100> kenvandine: sync silos won't work here :<
[18:50] <sil2100> kenvandine: need to wait for the silo to stop preparing packages, but we'll have to prepare those packages manually
[18:50] <sil2100> kenvandine: CI Train, when doing synces, appends ~rtm to the upstream version number by default, so now we'll have b0rken package numbers in the silo
[18:51] <sil2100> Check out the PPA later and tell me if you think we can use those
[18:54] <sil2100> Grrrrr
[18:54] <sil2100> Why so many problems?!
[18:54] <robru> sil2100: ok I'm gonna grab some food quickly, brb. I promise nothing can go wrong with the publish job (both hotfixes had tests) ;-)
[18:55] <kenvandine> sil2100, so i bet some of these gnome bumps will be missing deps :/
[18:55] <sil2100> robru: ok, have fun!
[18:55] <sil2100> kenvandine: ;/
[18:55] <kenvandine> what a mess...
[18:55] <sil2100> kenvandine: let's see how these ugly-versioned syncs build, we'll be prepared for that at least
[19:03] <sil2100> kenvandine: ok, they're in the PPA - take a look at those broken version numbers, so sad :<
[19:03] <sil2100> But we'll see if new deps will be needed
[19:09] <kenvandine> Missing build dependencies: libgrilo-0.2-dev
[19:09] <kenvandine> sil2100, ^^
[19:09] <kenvandine> Missing build dependencies: libgnome-desktop-3-dev (>= 3.9.91)
[19:10] <sil2100> ...
[19:10] <kenvandine> sil2100,  does that ppa not pull from -proposed?
[19:11] <kenvandine> Missing build dependencies: libupower-glib-dev (>= 0.99.1)
[19:11] <sil2100> It should
[19:11] <sil2100> Yeah, it's says it uses proposed
[19:13] <sil2100> hmmmm
[19:13] <sil2100> kenvandine: ok...
[19:13] <sil2100> kenvandine: I see another thing :<
[19:13] <sil2100> kenvandine: the reason for this is that the version we have in -proposed is 0.99.1~rtm-3
[19:13] <sil2100> kenvandine: since it was a sync from vivid
[19:14] <sil2100> And 0.99.1~rtm is smaller than 0.99.1
[19:14] <kenvandine> yeah
[19:14] <sil2100> kenvandine: all in all, I must say that silo 16 is a catastrophy right now ;p And it has nothing to do with any of your changes ;p
[19:14] <sil2100> We're doing everything wrong!
[19:15] <kenvandine> yeah... i really wasn't prepared to try to land that transition :-/
[19:16] <sil2100> Same here...
[19:17] <sil2100> I think we might want to re-publish upower with a proper version number
[19:17] <kenvandine> that's only part of the problem though
[19:18] <sil2100> Yeah
[19:18] <sil2100> And then, we need to decide if we want to continue this big transition, or we'll just fix the packages to build
[19:18] <sil2100> With hacky patches
[19:18] <kenvandine> all of the desktop stuff, is going to be like peeling an onion
[19:19] <sil2100> So maybe we can simply fix the FTBFS?
[19:19] <kenvandine> or... maybe change the build depends binary to libupower-glib3-dev ?
[19:20] <kenvandine> so the packages that haven't been ported can still build against the old
[19:20] <kenvandine> that's different than vivid though
[19:20] <sil2100> Which ones?
[19:21] <kenvandine> change the binary from libupower-glib-dev to libupower-glib3-dev
[19:21] <kenvandine> then change the build depends for indicator-power, settings, etc
[19:21] <kenvandine> but leave all the desktop packages alone
[19:22] <sil2100> uuuh
[19:22] <sil2100> Sounds hacky! ;)
[19:22] <kenvandine> yeah :)
[19:22] <kenvandine> shortest road to fixing the rtm archive though
[19:23] <kenvandine> i still hate it
[19:23] <sil2100> Are you sure that would help though?
[19:23] <kenvandine> sure, if the other packages still depend on the old binary
[19:23] <kenvandine> that binary is still in the archive
[19:23] <kenvandine> and doesn't conflict
[19:23] <kenvandine> they depend on libupower-glib1
[19:24] <kenvandine> they shouldn't even need to be rebuilt
[19:24] <kenvandine> but if they were to be rebuilt, they would need to build against the old upower
[19:24] <sil2100> But this does seem to reveal a certain risk, that even with the new upower in the rtm archive, all non-modified packages would depend on the old one
[19:24] <sil2100> And this would potentially mean that we're unsyncable for those components as well, hmm
[19:24] <kenvandine> yeah, the version they are linked with
[19:24] <kenvandine> yeah
[19:25] <kenvandine> none of which are in the image though
[19:25] <kenvandine> we didn't see any problems with those installing upower from the silo
[19:26] <kenvandine> and actually, if we sync those packages, they will come from vivid anyway
[19:26] <sil2100> kenvandine: right!
[19:27] <kenvandine> the rename of the build depends blows
[19:27] <sil2100> kenvandine: ok, so if you feel brave enough, please proceed! I suppose that you as a core-dev have more feeling of what's appropriate as well :)
[19:27] <kenvandine> but without it those desktop packages will FTBFS if we ever tried rebuilding
[19:27] <sil2100> kenvandine: in the meantime, I'll prepare a different silo for you
[19:27] <kenvandine> well... why exactly is it held in proposed?
[19:27] <sil2100> kenvandine: since this one is blown anyway, since we cannot push versions lower than what's in there
[19:28] <kenvandine> since we aren't removing the old lib
[19:28] <kenvandine> i'm just wondering if we have a hard breaks there keeping you from installing the 2 versions
[19:28] <sil2100> kenvandine: I didn't see that in the package, hm, right
[19:29] <kenvandine> do we have an excuses page for ubuntu-rtm?
[19:34] <sil2100> kenvandine: yeah
[19:35] <sil2100> http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt
[19:35] <sil2100> Wait, no
[19:35] <sil2100> Wrong paste
[19:35] <sil2100> http://people.canonical.com/~ubuntu-archive/proposed-migration/ubuntu-rtm/update_output.txt
[19:45] <sil2100> kenvandine: any leads?
[19:52] <kenvandine> sil2100, not really... according to rmadison there is no libupower-glib1 in 14.09-proposed
[19:52] <kenvandine> oh... of course there isn't :)
[19:53] <kenvandine> the update tests should be able to resolve that from 14.09 though
[19:54] <sil2100> jibel: let's postpone the announcement of the new rules until tomorrow, ok?
[19:54] <jibel> sil2100, okay
[19:59] <kenvandine> sil2100, ok... this isn't good
[19:59] <kenvandine> powerd and indicator-power was promoted to release
[19:59] <kenvandine> but they should have been built against the new upower
[20:00] <kenvandine> so those will be uninstallable
[20:01] <sil2100> Wait, they weren't built against the new upower? They were in the same silo?
[20:01] <sil2100> Ah, no deps for 0.99?
[20:01] <kenvandine> yes, in the same silo
[20:02] <kenvandine> ah, they depend on upower
[20:02] <kenvandine> not libupower-glib3
[20:03] <kenvandine> so i guess they will be installable
[20:03] <kenvandine> but... probably blow up
[20:03] <kenvandine> probably really depends on the dbus interface
[20:07] <kenvandine> sil2100, i don't know what to do... since those went to release we're pretty committed to getting the other 2 to release asap
[20:07] <kenvandine> it'll break the images
[20:07] <kenvandine> but then that causes some sort of update issue for those desktop packages in rtm
[20:07] <kenvandine> none of which should affect the image
[20:08] <kenvandine> sil2100, i guess we just don't know if powerd and indicator-power gracefully falls back to the old dbus API or not
[20:08] <kenvandine> i know we needed updates to those to handle the dbus api changes, but never looked at them
[20:11] <sil2100> kenvandine: so maybe we'll revert the upower+powerd landing for now?
[20:12] <sil2100> And re-release once all is clear?
[20:13] <kenvandine> sil2100, well half of the landing is in release already
[20:13] <kenvandine> harder to revert
[20:13] <sil2100> kenvandine: no no, since we'd revert those exactly, just use the reverter and push directly to the archive :)
[20:14] <sil2100> You know, reverts should instantly pop up in the archive I suppose
[20:14] <kenvandine> fine with me, just need someone who can sort out the transition
[20:14] <sil2100> But hm, the version numbers would be ugly
[20:14] <kenvandine> i hadn't planned any time for that
[20:14] <sil2100> But bleh
[20:14] <sil2100> Yeah, ok, let me revert today or tomorrow (at max) and we'll take care of this tomorrow
[20:14] <kenvandine> we don't want broken images, that's more important than version numbers
[20:14] <kenvandine> :)
[20:16] <kenvandine> i suspect images created now would be pretty broken
[20:18] <kenvandine> sil2100, so if we're reverting, could i just publish what's in silo 4 and squash what went to -proposed?
[20:18] <kenvandine> assuming QA gives it an ack
[20:22] <sil2100> kenvandine: I suppose that might be a good idea, but let me first revert - will do that once I'm back from a quick errand
[20:22] <kenvandine> ok, thanks
[20:23]  * kenvandine tries to remember what he was fixing before all hell broke loose :-D
[21:07] <Saviq> Ursinha, hey, looks like I can't get rid of the Resync trunk commits after all https://code.launchpad.net/~mir-team/qtmir/trunk :/
[21:19] <sil2100> Saviq: that's still happening?
[21:19] <sil2100> robru: ^
[21:20] <robru> what?
[21:20] <Saviq> sil2100, well, there's two things - a) the 5 before previous release got brought back somehow
[21:20] <sil2100> robru: check the qtmir trunk above, it seems CI Train is again pushing 'Resync trunk' commits there all the time
[21:20] <Saviq> sil2100, and b) there's an empty "Resync trunk" at the tip as well
[21:21] <sil2100> I need to revert the breakage now and finally EOD
[21:21] <robru> sil2100: Saviq: the qtmir silo isn't even published? merge&clean job can't be running to cause this
[21:21] <sil2100> Saviq: yeah, the last thing is worrying...
[21:23] <sil2100> kenvandine: what we'll do is, I'll ask some archive admin to remove the 2 packages from proposed, and revert the other two back with our reverter
[21:23] <sil2100> And everything will be super clean
[21:23] <kenvandine> sil2100, ok
[21:26] <Saviq> robru, that's vivid
[21:26] <Saviq> robru, the silo just got published some time ago
[21:26] <robru> Saviq: 2 hours ago?
[21:26] <Saviq> robru, possibly, row 29
[21:27] <robru> Saviq: I mean if this problem was back, there'd be a new resync trunk commit every 5 minutes, as that's how often it tries to merge & clean
[21:27] <Saviq> robru, https://ci-train.ubuntu.com/job/check-publication-migration/72793/console
[21:27] <robru> since there's only one resync trunk commit, this must be some different but similar issue
[21:27] <Saviq> robru, I'm not saying it's the same problem
[21:28] <Saviq> robru, similar result, yes (and I don't know where it took the previous 5 empty commits, too
[21:28] <Saviq> does it keep a cache of the trunk between landings or something?
[21:28] <robru> Saviq: oh right, so what happens is, citrain checks the revno of trunk when the silo is prepared. you deleted a bunch of commits and citrain was like 'hey, revno at trunk is different, let's merge what we have with what they have'
[21:28] <robru> Saviq: yes, the silo keeps a copy of the branch locally which it then pushes later
[21:28] <Saviq> robru, but not *between* silos
[21:29] <robru> Saviq: so now that the silo is free you should be able to delete those commits and --overwrite the branch, next silo will honor that
[21:29] <robru> Saviq: not between silos no... only inside the silo itself
[21:29] <Saviq> robru, if only bzr allowed deleting commits...
[21:30] <Saviq> robru, I'll have a think about what to do
[21:30] <robru> Saviq: I'm pretty sure you can branch the trunk, check out an earlier revision, cherry pick a couple commits that are real, and then `bzr push --overwrite` to get those ugly commits out of the trunk
[21:31] <Saviq> robru, sure I can, not the cleanest way to do things, though...
[21:33] <robru> Saviq: the only other option I'm aware of is to just leave those commits in place. ¯\_(ツ)_/¯
[21:34] <Saviq> robru, yeah, /me hates, overwritten
[21:36] <robru> Saviq: not that this matters to you, but amusingly this issue wasn't caused by my recent refactorings... when I implemented automatic merge&clean, I didn't make any changes to the merge&clean job for that... so merge&clean always had this bug, just exacerbated by the creds explosion and running the script automatically every 5 minutes...
[21:36] <Saviq> robru, yup
[21:51] <sil2100> kenvandine: hey, maybe you're willing to do a dput for me? :)
[21:51] <sil2100> kenvandine: http://people.canonical.com/~lzemczak/packaging/ <- the powerd* files there
[21:51] <brendand> lpotter, need a quick chat about silo 22 if that's ok
[21:51] <kenvandine> sure
[21:51] <sil2100> kenvandine: (nothing else needs reverting, the indicator-power landing only touched translations, so it's safe)
[21:51] <sil2100> kenvandine: thanks!
[21:51]  * sil2100 needs to really EOD now
[22:02] <kenvandine> what's the secret sauce to dput directly to 14.09?
[22:03] <kenvandine> robru, do you have any idea? ^^
[22:05] <robru> kenvandine: dput to a ppa or the archive?
[22:05] <kenvandine> archive
[22:05] <robru> kenvandine: sorry I only know how to dput to the ppas.
[22:05] <kenvandine> trying to upload the package from sil2100 for that revert
[22:05] <kenvandine> he said to dput it directly to 14.09... then ran off :)
[22:05] <robru> kenvandine: I guess use copy-package?
[22:07] <kenvandine> he said dput...
[22:07] <kenvandine> and gave me the sources for his package
[22:07] <kenvandine> sigh...
[22:08] <robru> kenvandine: I've never dput'ed to archives. usually when the train has problems publishing I hear core-devs talk about using copy-package from the PPAs to the archive.
[22:08] <kenvandine> yeah
[22:13] <kenvandine> whew... figured it out :)
[22:14]  * kenvandine heads out too
[23:04] <tedg> trainguards, Can I get a silo for line 46 please?
[23:07] <robru> tedg: ah, you have silo 0 ;-)
[23:07] <tedg> robru, Hah, now I'm curious if zero is the non-silo ;-)
[23:07] <tedg> robru, Thanks!
[23:08] <robru> tedg: you're welcome
[23:08] <tedg> robru, I think that vivid silo 4 fell off the spreadsheet…
[23:09] <tedg> robru, It's tested, can you just publish it?
[23:09] <robru> tedg: ok
[23:10] <charles> ted, robru, thanks :)
[23:10] <charles> s/ted/tedg/
[23:11] <robru> charles: you're welcome
[23:11]  * tedg curses the person who has "ted" of freenode!
[23:11] <tedg> on…
[23:11] <charles> ted kulp
[23:11] <tedg> Yeah, don't know who that is. Clearly a bad person because he took my nick.
[23:12] <robru> tedg: heh
[23:12] <charles> apparently, he wrote this: http://www.cmsmadesimple.org/
[23:15] <tedg> Bet it's written in PHP, the devil's language.
[23:15] <tedg> :-)
[23:31] <robru> cjwatson: ping
[23:31] <cjwatson> robru: Please tell me what you want and I'll reply when I'm around.
[23:31] <robru> heh
[23:32] <robru> cjwatson: if it's possible can you install python-six on snakefruit? http://people.canonical.com/~ubuntu-archive/cicopy.log
[23:33] <cjwatson> robru: Could you RT that, please?  It'd make more sense to have IS install it than for me to unpack another thing in our home directory.
[23:33] <cjwatson> (And chase with IS directly, assuming you need this to get the train running properly.)
[23:33] <robru> cjwatson: ah ok. yeah publications are blocked on this right now
[23:33] <robru> cjwatson: it is snakefruit right?
[23:33] <cjwatson> Yes.
[23:33] <robru> cjwatson: thanks
[23:34] <cjwatson> I've unpacked a few things in ~ubuntu-archive, but only when they're newer than what's available in packaged form for snakefruit's current release, or similar.
[23:34] <cjwatson> But six.iteritems should be available in 1.1.0-2 IIRC which is what's available.
[23:35] <cjwatson> Yeah, looks like it.
[23:35] <robru> cjwatson: oh jeez. yeah I've hit a few spots where python-six 1.1 wasn't new enough
[23:35] <robru> cjwatson: but if it has iteritems it should be good for this
[23:36] <cjwatson> It does, I checked my git history.
[23:36] <robru> cjwatson: ok thanks
[23:44] <robru> cjwatson: no, wait
[23:44] <robru> cjwatson: the line preceding the failing import is 'from six.moves import range as gen_range'
[23:44] <robru> cjwatson: so python-six is installed, but six.iteritems isn't available
[23:46] <cjwatson> Oh, so it is.
[23:46] <robru> cjwatson: can you pull in a newer version then? I guess 1.5 would have it, 1.8 is latest.
[23:47] <cjwatson> Yeah, working on it.
[23:47] <robru> cjwatson: thanks
[23:51] <robru> cjwatson: actually, looking at that traceback there's a sort of funny import chain going on there. if I were to shuffle around where some functions and classes are defined, I could probably avoid copy2distro needing to import silomanager at all, avoiding that import. does that sound like a better solution to you? or is that just kicking the can down the road
[23:51] <robru> until the next time a file grows a dep on six?
[23:53] <cjwatson> robru: *shrug* it should have six 1.8.0 there now
[23:54] <cjwatson> (I just cloned the Debian packaging branch, symlinked six.py into $HOME/python/ which is used for other things, and set PYTHONPATH="$HOME/python" in ~/cu2d/run.sh
[23:54] <robru> cjwatson: alright thanks.
[23:54] <cjwatson> )
[23:54] <robru> cjwatson: we'll see in a minute if it worked ;-)
[23:55] <cjwatson> Apparently not.
[23:55] <robru> cjwatson: no? the traceback disappeared
[23:55] <cjwatson> Reload.
[23:55] <robru> i... what?
[23:55] <robru> cjwatson: I swear I reloaded and the traceback was gone. how is it back?
[23:56] <cjwatson> Because it was still busy writing the file when you reloaded first.
[23:56] <robru> ah
[23:57] <cjwatson> Weird, that sequence of imports works when I run it by hand at a python prompt.
[23:57] <robru> cjwatson: so why didn't that work if you set pythonpath? citrain files append to sys.path but don't overwrite it
[23:57] <cjwatson> I don't know, kind of on vacation here. :P
[23:57] <robru> cjwatson: bah, python import magic
[23:57] <robru> barry!!
[23:58] <robru> cjwatson: ok well I'll do a branch where I shuffle things.
[23:59] <cjwatson> (Pdb) sys.modules['six']
[23:59] <cjwatson> <module 'six' from '/home/ubuntu-archive/cu2d/cupstream2distro/six.pyc'>
[23:59] <cjwatson> Nuked that .pyc, should be better in a moment.
[23:59] <robru> cjwatson: oh right, leftover from when I'd committed a stub to trunk...


[00:47] <brokenfingers> VERIFY REGISTER brokenfingers dpgkncouoxye
[00:47] <brokenfingers> whoops!
[00:52] <penguin42> oops
[15:21] <penguin42> ubuntu-bug won't let me report a problem with adobe-flashplugin but that seems to be the partner way to install flash? Is the right thing to remove that, put flashplug-installer back in and try again?
[16:07] <penguin42> right, looks like <IP_ADDRESS> flash is broke on that machine - bug 1008132
[16:07] <ubot2`> Launchpad bug 1008132 in flashplugin-nonfree "<IP_ADDRESS> fails every time (nothing displayed, but shows in about:plugins), 11_1r102_62_32bit_debug works" [Undecided,New] https://launchpad.net/bugs/1008132
[16:21] <Ologn> Is it just my system, or does the "barrage" package not launch at all on 12.04?  I should warn people beforehand, it also seems to mess up the display to where you have to go to displays and reset your screen size
[16:21] <Ologn> I reported a bug anyhow...
[16:27] <penguin42> Ologn: Hmm, not happy for me either - I get a black screen witha  light blue bit to the left
[16:28] <Ologn> penguin42: Are you x86-64 or x86?
[16:28] <Ologn> penguin42: And you're 12.04?
[16:29] <penguin42> yep, kubuntu 12.04
[16:29] <Ologn> x86-64?
[16:29] <Ologn> or x86?
[16:29] <penguin42> 64
[16:30] <penguin42> what's your bug number?
[16:30] <Ologn> https://bugs.launchpad.net/ubuntu/+source/barrage/+bug/1008011
[16:30] <ubot2`> Launchpad bug 1008011 in barrage "Barrage does not open - crashes with SIGABRT" [Undecided,New]
[16:31] <Ologn> I did the dbgsym for the sdl packages and barrage
[16:32]  * penguin42 has mediumised it for you
[16:34] <Ologn> cool, thanks
[18:36] <brokenfingers> bug 813134 Has Anyone looked into this? It's pretty serious, but I don't know what to make of it or why there is relitively no activity
[18:36] <ubot2`> Launchpad bug 813134 in ubiquity "[DATALOSS] ubiquity overwrites luks-formatted device without warning" [Critical,New] https://launchpad.net/bugs/813134
[18:37] <penguin42> brokenfingers: Thing is I thought it was fixed - I remember a discussion from a few months about it
[18:38] <brokenfingers> Yah. I just looked and like 5 people (inexperienced) had fooled with the status
[18:40] <brokenfingers> penguin42: The asignee assigned themselves the day they joined LP and just abandoned launchpad and people thought it was fixed :(
[18:42] <penguin42> brokenfingers: Ah ok, so I see why I remember it, see bug 762636 that links to a thread I commented on and then to bug 420080 that has a fix released
[18:42] <ubot2`> Launchpad bug 762636 in ubiquity "Ubuntu installer kills LUKS partitions without warning" [Undecided,New] https://launchpad.net/bugs/762636
[18:42] <ubot2`> Launchpad bug 420080 in partman-crypto "Configure encrypted volumes destroys existing data" [Critical,Fix released] https://launchpad.net/bugs/420080
[18:44] <brokenfingers> punguin42: Oh, the I'll take care of changing bug 813134 and bug 762636 to FixRel and mark as duplicates
[18:44] <ubot2`> Launchpad bug 813134 in ubiquity "[DATALOSS] ubiquity overwrites luks-formatted device without warning" [Critical,New] https://launchpad.net/bugs/813134
[18:44] <ubot2`> Launchpad bug 762636 in ubiquity "Ubuntu installer kills LUKS partitions without warning" [Undecided,New] https://launchpad.net/bugs/762636
[18:45] <penguin42> brokenfingers: Yeh, I'd just dupe them to 420080
[18:45] <brokenfingers> penguin42: Im on it
[18:46] <penguin42> brokenfingers: actually, it might be worth checking....
[18:46] <brokenfingers> penguin42: how?
[18:46] <penguin42> brokenfingers: I mean the fixes in 420080 were in partman-crypto that was what the alternate installer used, is that the case in the graphical installer - I don't think the graphical installer used to be able to do encrypted stuff?
[18:47] <brokenfingers> penguin42: Oh... I see what you mean. What should I do? Dupe them?
[18:50] <penguin42> brokenfingers: I'd dupe 813134 and 762636 then add a comment that it looks like 420080 - but with a 'is it the same' - and add that comment to both your dupe and a comment on 420080
[18:51] <brokenfingers> pengin42: K. What about the status? Leave in "New" in Ubiquity?
[18:52] <penguin42> brokenfingers: It seems to me a confirmed since at least 2 people are suffering from it
[18:53] <brokenfingers> penguin42: Whitch One? 813134 and 762636 only affect 1.
[18:53] <penguin42> brokenfingers: One each, and when you dupe them together they'll affect 2
[18:54] <brokenfingers> penguin42: Oh yeah. That's right!  Can you chnge it?
[18:59]  * penguin42 scratches head - ok, so the intent is to dupe 762636 to 813134?
[19:00] <brokenfingers> penguin42: No, can you change it to cofirmed and then I'll dupe it?
[19:01] <penguin42> ok, try that - I took 813134 out of the dupe
[19:01] <penguin42> and set 762636 to confirmed
[19:02] <brokenfingers> penguin42: Ahhh.. THank you!
[19:02] <penguin42> np
[19:02] <brokenfingers> penguin42: sometime in the future I should prabably join Bug-cont myself tho.
[19:03] <penguin42> brokenfingers: Feel free to apply
[19:03] <penguin42> brokenfingers: are you a member of bug-squad?
[19:03] <brokenfingers> penguin42: Yes.
[19:03] <penguin42> ok
[19:04] <brokenfingers> penguin42: am I experienced enogh?
[19:06] <penguin42> brokenfingers: The criteria/knowledge is here: https://wiki.ubuntu.com/UbuntuBugControl   if you already can say yes to all those and feel experienced enough then apply
[19:08] <brokenfingers> penguin42: Ithink I can, I'll try applying
[19:08] <penguin42> good luck!
[19:08] <brokenfingers> Thank you
[20:00] <Kus> hello
[20:01] <Kus> i have a bug reported, but need to follow instructions for details, https://bugs.launchpad.net/ubuntu/+bug/1007765
[20:01] <ubot2`> Launchpad bug 1007765 in ubuntu "brightness adjusting crashes system" [Undecided,Incomplete]
[20:02] <Kus> what is the key combination? i do not know Sysrq+r e i s u b (reisub one letter at time)
[20:02] <Kus> what is Sysrq?
[20:32] <jtaylor> ctrl alt print
[20:32] <jtaylor> http://en.wikipedia.org/wiki/Magic_SysRq_key
[20:32] <jtaylor> reisub will reboot your system
[20:32] <jtaylor> (raising elephants is so utterly boring :) )
[21:02] <brokenfingers> penguin42: I'm writing my aplication now, I have a question, If I don't exactly have 5 AMAZINGLY SPECTACULARLY FABULOUS bugs, and I've never forwarded upstream(but I know how to), what do I do?
[21:04] <penguin42> brokenfingers: They don't have to be amazingly spectacular - they just have to show you're applying the rules and making decisions appropriately
[21:05] <brokenfingers> penguin42: Mmmm, but do they have to see 1 thats forwarded upstream? (bugzilla.gnome.org is down right now)