[18:24] <cprofitt> here cjohnston
[18:24] <cjohnston> cprofitt: i have a bug for you if you like
[18:24] <cprofitt> sure.
[18:29] <cjohnston> cprofitt: bug #892436
[18:29] <ubot4> Launchpad bug 892436 in loco-team-portal "Broken link on http://loco.ubuntu.com/about/ (affects: 1) (heat: 8)" [Undecided,Confirmed] https://launchpad.net/bugs/892436
[18:31] <cprofitt> what is the new url?
[18:31] <cjohnston> ~ltp-devs
[18:34] <cprofitt> I may have to work on this when I get home...
[18:34] <cprofitt> I do not have my keys on my work machine
[18:34] <cjohnston> thats fine..
[18:34] <cjohnston> an easy way for getting you in and started though s what i figured
[18:35] <cprofitt> yes, then you can show me how to do the merge process
[18:35] <cprofitt> which is a step I have not done
[18:35] <cjohnston> not a problem
[18:35] <cjohnston> super easy
[18:35] <cjohnston> im not sure what my availability will be tonight but ping and ill try to be around
[18:36] <cprofitt> alright
[18:36] <cprofitt> I have a cub scout pack meeting to attend too
[18:37] <cprofitt> but I will try to ping you when I am free
[18:38] <cprofitt> wait...
[18:39] <cprofitt> cjohnston: is this the link on the wiki or inside the portal?
[18:39] <cjohnston> should be inside the portal
[18:39] <cjohnston> the team name changed
[18:39] <cjohnston> which should 404  alink or two
[18:40] <cprofitt> k
[18:45] <svwilliams> cjohnston, and cprofitt there are links to loco-directory-devs in the wiki too I think
[18:45] <cjohnston> svwilliams: ok.. if you guys run into them, please feel free to fix :-)
[18:46] <svwilliams> ok
[18:49] <cprofitt> cjohnston: I only found one example of that changed url
[18:49] <cjohnston> very possibly true
[18:49] <cprofitt> it was in /loco-directory/templates/about.html
[18:50] <cjohnston> we dont link to it alot afaik
[18:50] <cjohnston> and that is the right page
[18:50] <cprofitt> alright... so I will get setup at home later tonight and you can teach me the merge
[18:50] <cjohnston> the bzr part or the lp part or both
[18:51] <cprofitt> both
[18:51] <cprofitt> I have not done either
[18:51] <svwilliams> I should make sure I'm on for the lesson :-)
[18:51] <svwilliams> I haven't done it yet either
[18:51] <cprofitt> I know I have to change the file... then there is a process to upload it via bzr
[18:51] <cjohnston> svwilliams: you have done it all
[18:52] <cjohnston> you could teach it already
[18:52] <svwilliams> yup the light clicked on
[18:52] <cjohnston> i have the emails to prove it
[18:52] <svwilliams> he is talking about the up to lp
[18:52] <svwilliams> propose for merge
[18:52] <svwilliams> I was thinking a bzr merge
[18:52] <svwilliams> if that is even possible ... it is in git
[18:52] <cjohnston> ya.. he is talking about commit/push
[18:53] <svwilliams> ahh ok cprofitt if cjohnston's not on and I'm on I can try and help
[18:53] <svwilliams> I should be on tonight
[18:53] <cprofitt> sounds goog
[18:53] <cprofitt> good even
[18:53] <cprofitt> ;-)
[18:53] <cprofitt> I used bzr to pull the code... is it not on bazaar anymore?
[18:54] <cjohnston> cprofitt: it is
[18:54] <cprofitt> k
[18:55] <svwilliams> :-) sorry cprofitt we use git at work so I get confused by which system allows for each commands
[18:55] <svwilliams> all lp projects are bzr right?
[18:55] <svwilliams> except the kernal team
[20:55] <cprofitt> cjohnston: ping
[20:55] <cjohnston> sir
[20:55] <cprofitt> just about ready for some help if you have time
[20:56] <cjohnston> i have probably 8 minutes
[20:56] <cprofitt> looks like I need to make a new branch
[20:57] <cjohnston> ok.. so you already pulled it and made the changes?
[20:57] <cprofitt> pulled it, changes are seconds from happening
[20:57] <cjohnston> then you need to commit
[20:58] <cjohnston> bzr commit -m "enter text about your commit here"
[20:58] <cjohnston> then you would push
[20:58] <cjohnston> bzr push lp:~yourlpusername/loco-team-portal/some-name-or-bug-number-here
[20:59] <cjohnston> so if your working on bug # 123 bzr push lp:~cprofitt/loco-team-portal/123   would work
[20:59] <cprofitt> do I need to cd in to the loco-directory folder on my machien?
[21:00] <cjohnston> you can do it either in the directory that was created or the sub directories
[21:00] <cjohnston> its not specific
[21:01] <cprofitt> hmm... I get a connection error
[21:02]  * cprofitt looks at ssh keys
[21:02] <cprofitt> I wonder if I restored these
[21:04] <cprofitt> got that resolved
[21:04] <cprofitt> bzr: ERROR: Permission denied: "+branch/cprofitt/loco-team-portal/892436/": : Project 'cprofitt' does not exist.
[21:04] <cprofitt> do I need to register a branch first?
[21:05] <cprofitt> nvr mind
[21:05] <cprofitt> I see I was missing the ~ before my name
[21:05] <cprofitt> cjohnston: should be up ther enow
[21:05] <cprofitt> I see it
[21:06] <cprofitt> thanks for walking me through that
[21:08] <cprofitt> cjohnston: was that it?
[21:10] <cprofitt> mhall119: should I propose a merge or is that something you guys review and propose?
[21:11] <cjohnston> cprofitt: link it to the bug
[21:11] <cjohnston> then propose a merge
[21:11] <cjohnston> on the propse a merge page
[21:11] <cjohnston> there is a button for extra options
[21:11] <cjohnston> under extra options
[21:11] <cjohnston> fill out the commit message
[21:12] <cjohnston> i know it seems like your doing it twice, but if you have multiple commits to one branch, you need to do a commit message for the entire branch
[21:12] <cjohnston> we use Tarmac to do our merging for us, so without the commit message entered on LP, Tarmc wont work
[21:15] <cprofitt> k
[21:16] <cprofitt> do I choose a reviewer?
[21:16] <cjohnston> nope
[21:16] <cprofitt> and what do I fill out in the commit message?
[21:16] <cjohnston> just leave that blank
[21:17] <cjohnston> a description.. ex "Updated link to LoCo Team Portal Developers to reflect new URL."
[21:17]  * cjohnston is out
[21:17] <cprofitt> thanks cjohnston
[21:17] <cjohnston> if you have more questions, ill be back in a few hours
[21:17] <cjohnston> thank you cprofitt
[21:17] <cjohnston> sorry for rushing off
[21:17] <cprofitt> np


[08:51] <harmw> smoser: ok
[08:52] <harmw> but if you're into muddling with busybox, adding in some ipv6 tools would be very helpfull as well


[04:49] <Kilos> morning guys
[05:35] <Kilos> lo nuvolari ???
[06:58] <Kilos> Maaz, coffee on
[06:58]  * Maaz starts grinding coffee
[07:02] <Maaz> Coffee's ready for Kilos!
[07:07] <Kilos> Maaz, ty
[07:07] <Maaz> You are welcome Kilos
[07:22] <Kilos> morning superfly
[07:23] <Kilos> magespawn_, whats with the tail
[07:23] <Kilos> hehe
[09:28] <WOLFEYES> Good day all.
[09:40] <Kilos> google kde wallet keeps opening on kubuntu 12.04
[09:40] <Kilos> oops
[09:40] <Kilos> Maaz, google kde wallet keeps opening on kubuntu 12.04
[09:40] <Maaz> Kilos: "google chrome - How to migrate passwords from Kwallet to the ..."  :P
[17:53] <charlvn> ah i had the Westmalle Dubbel Bruin and the Chimay Tripel
[17:53] <charlvn> both highly recommended
[17:53] <charlvn> yeah it's literally the case
[17:53] <charlvn> i could literally drink a different type of beer every day of the year
[17:54] <Kerbero> i like corsendonck bruin
[17:54] <charlvn> i had some coffee and apple tart here: http://www.degrootewittearend.be/
[17:58] <charlvn> oh yes and i went here: http://nl.wikipedia.org/wiki/Paleis_op_de_Meir
[17:58] <smile> charlvn: you went everywhere ;)
[17:58] <charlvn> oh i went here: http://www.thechocolateline.be/
[17:58] <charlvn> that was the chocolate shop
[17:58] <charlvn> just found it myself now
[17:58] <charlvn> the website
[18:01] <charlvn> i had a problem getting there, the train between tilburg and breda wasn't going so i had to go by bus, it delayed me by about two hours
[18:02] <charlvn> i ended up coming back via schiphol (antwerpen -> schiphol and then to the city where i live)
[18:02] <charlvn> the ns hispeed goes between antwerpen and amsterdam centraal
[18:02] <charlvn> so i got off almost at the end
[18:02] <Kerbero> yeah i was on that trajek once before too
[18:03] <Kerbero> in both directions
[18:03] <Kerbero> *line <- i guess is the english word for it
[18:03] <charlvn> it's a nice drive, i like the fast trains
[18:03] <Kerbero> hehe
[18:03] <charlvn> no idea what the english is
[18:03] <Kerbero> but it stops in rotterdam
[18:03] <charlvn> yes
[18:03] <Kerbero> and some more places
[18:03] <Kerbero> which delays it a lot
[18:04] <charlvn> can't recall, i was sleeping part of the way
[18:04] <Kerbero> and it is not THAT fast
[18:04] <charlvn> much faster than the stoptrein :P
[18:04] <Kerbero> yes
[18:04] <charlvn> even the schiphol <> berlin train doesn't feel too fast for me
[18:04] <Kerbero> the train i take the most is the one from schiphol to haren
[18:04] <charlvn> and i would have expected it to be much faster
[18:04] <Kerbero> which is only a stoptrein between zwolle and groningen
[18:05] <Kerbero> the only train that i know is fast is the thalys
[18:05] <Kerbero> i took it once retoer from köln to paris
[18:05] <charlvn> nice
[18:05] <Kerbero> very fast between brussel and paris
[18:05] <charlvn> never been on that one before
[18:05] <Kerbero> i had my gps on
[18:06] <Kerbero> and it actually did do 300km/h
[18:06] <Kerbero> the train vibrates at that speed
[18:06] <Kerbero> a little scary actually
[18:06] <charlvn> the ns hispeed train that goes to antwerpen feels ancient
[18:07] <charlvn> the passenger carriages look very old
[18:07] <Kerbero> yes!
[18:07] <Kerbero> i thought so too
[18:07] <charlvn> i didn't know there were trains that were still going like that
[18:07] <Kerbero> charlvn: what do you think of antwerpen's station?
[18:07] <charlvn> antwerpen's station has amazing architecture
[18:07] <Kerbero> indeed
[18:07] <charlvn> i have never seen such a beautiful old station
[18:07] <Kerbero> and it is three levels of tracks
[18:07] <charlvn> it's huge too
[18:07] <Kerbero> it is really amazing
[18:08] <charlvn> yeah i have never seen that before either
[18:08] <Kerbero> it is the first thing i think of when i hear antwerpen
[18:09] <charlvn> the dutch trains are so ugly, i can't believe the person who designed those trains had no sense for aesthetics
[18:09] <charlvn> i was in germany today and the trains look so nice there
[18:09] <Kerbero> haha
[18:09] <charlvn> so clean and neat
[18:09] <charlvn> out trains are gross
[18:09] <charlvn> *our
[18:10] <charlvn> westfalenbahn has these nice blue trains
[18:10] <Kerbero> so did you visit antwerpen for work or pleasure?
[18:10] <charlvn> no i did it for the lulz
[18:10] <Kerbero> ok
[18:10] <charlvn> i got cheap tickets from the ns spoordeelwinkel
[18:10] <Kerbero> o nice
[18:11] <charlvn> i think it cost me 28 euro or something
[18:11] <charlvn> and that included the coffee and apple tart
[18:11] <Kerbero> wow
[18:12] <charlvn> and from where i live in the east of the country it's quite some distance to go to belgium because you have to travel via roosendaal
[18:12] <charlvn> so you basically spend more time traveling through NL than through BE
[18:12] <charlvn> the trip from rosendaal to BE was quick
[18:12] <charlvn> to antwerpen i mean
[18:12] <Kerbero> i once took the train groningen->schiphol->antwerpen->lille on one day
[18:13] <Kerbero> it was a long day
[18:13] <charlvn> it's doable but then you come home and you are totally kapot
[18:13] <Kerbero> no it was only one direction
[18:13] <charlvn> ah ok
[18:13] <charlvn> no because i almost went kapot after coming back from antwerpen
[18:14] <charlvn> but that was in both directions of course
[18:14] <Kerbero> i did some other far trips too though
[18:14] <Kerbero> göttingen->rostock
[18:14] <Kerbero> and münster->paris (thalys part of it)
[18:15] <Kerbero> it is much nicer than driving self though
[18:15] <Kerbero> did a George -> Stellenbosch by car today
[18:16] <charlvn> that is also quite far
[18:16] <charlvn> 400KM?
[18:16] <Kerbero> 400km, about 6/7 hours
[18:16] <charlvn> yup
[18:16] <Kerbero> start of the school holiday
[18:16] <charlvn> i did the george -> cape town route myself a few days
[18:16] <Kerbero> taday
[18:16] <charlvn> but that also screws me up, sitting for so long in a car
[18:16] <charlvn> then i'll rather do the train
[18:16] <Kerbero> exactly
[18:16] <Kerbero> driving yourself is stressful
[18:16] <charlvn> i don't know why it's so bad in a car, but even as a passenger i have trouble
[18:16] <charlvn> i don't like it
[18:17] <Kerbero> train is nice relaxing and there are toilets
[18:17] <charlvn> i used to live in george and then work in cape town, so i had to do it frequently
[18:17] <Kerbero> and you can walk around and stand up
[18:17] <Kerbero> ahh ok
[18:17] <charlvn> well there isn't always toilets ;)
[18:17] <charlvn> that depends on the train
[18:17] <Kerbero> my parents live in george
[18:17] <Kerbero> hehe
[18:17] <charlvn> actually i have never used a wc on a train before
[18:17] <charlvn> oh same here, or at least one of my parents
[18:17] <Kerbero> wow
[18:17] <Kerbero> o
[18:18] <Kerbero> surname? (pm)
[18:18] <charlvn> van niekerk, same as me? :)
[18:18] <charlvn> no secret
[18:18] <Kerbero> meijers
[18:18] <charlvn> dunno
[18:18] <Kerbero> if your parents are dutch and lived/lives in george they should know that surname
[18:18] <charlvn> nope
[18:19] <Kerbero> o ok
[18:19] <Kerbero> all the old george dutch families knew eachother
[18:19] <charlvn> are you referring to the dutch-flemish cultural organisation?
[18:19] <Kerbero> no not even that
[18:19] <charlvn> i have been to one of two of their fests
[18:20] <charlvn> there was this super tall guy called bart
[18:20] <Kerbero> but that is in pinelands (CPT)
[18:20] <charlvn> he used to run it i think but he passed away a number of years ago
[18:20] <Kerbero> o
[18:20] <Kerbero> you are not talking about huis der nederlanden?
[18:21] <charlvn> not sure what that is
[18:21] <Kerbero> might be something different
[18:21] <charlvn> unless you're talking about orange-nassau
[18:21] <Kerbero> nope
[18:21] <Kerbero> hehe
[18:21] <Kerbero> too many of them
[18:24] <charlvn> the dutch consulate in cape town is in disarray though
[18:24] <charlvn> the dutch embassy in pretoria has their stuff together
[18:24] <Kerbero> i agree
[18:24] <charlvn> but i have not often dealt with a bunch of fools like at the consulate
[18:24] <charlvn> somebody needs to do something about that
[18:24] <charlvn> you talk to 4 people and each person has a different story
[18:25] <Kerbero> phoning or mailing pretoria works much better
[18:25] <charlvn> yeah, until they find out you're from the coast and then they get angry at you
[18:25] <Kerbero> hehe
[18:25] <charlvn> but the consulate it so complete and utterly useless that you have no other choice
[18:26] <charlvn> the people at the cape town consulate have very well been assimilated to south african government culture :)
[18:26] <Kerbero> lol
[18:26] <charlvn> the people in pretoria at least still act like europeans
[18:29] <charlvn> ok lemme make dinner, the kartoffel i ate in germany today is out of my stomach by now :P
[18:29] <charlvn> bbl
[18:30] <smile> bye :)
[19:42] <kilos> hi all
[19:50] <kilos> night all. sleep tight


[01:25] <blizzz> are there issues with printing in jaunty?
[01:39] <daskreech> Such as?
[03:09] <daskreech> kb9vqf: Torrents working again btw
[03:10] <daskreech> Haven't checked how many people are downloading though
[03:10] <daskreech> WEll "working"
[03:34] <daskreech> Nightrose: are there 2.1 beta jackalope debs ?
[03:52] <metellius> repost from #kde-devel, since I think I might have more luck here:
[03:52] <metellius> im still trying hard to build my kdebase-runtime, but phonon not finding some includes ruins the build. could someone (preferably a ubuntu user) post their cmakecache.txt for kdebase-runtime so I can see where my cmake installation went wrong?
[03:53] <metellius> maybe even if someone could point me towards kubuntu ppa build logs/files so I can look at them
[03:54] <ScottK> metellius: Are you trying to build from source or build a debian package?
[03:54] <metellius> its a trunk build
[03:57] <ScottK> metellius: What architecture (I'll get you the build log)?
[03:57] <metellius> i386
[03:59] <ScottK> metellius: Here's the i386 build log for the most recent Jaunty upload: https://launchpad.net/ubuntu/+source/kdebase-runtime/4:4.2.2-0ubuntu1/+build/926508/+files/buildlog_ubuntu-jaunty-i386.kdebase-runtime_4:4.2.2-0ubuntu1_FULLYBUILT.txt.gz
[04:01] <daskreech> ScottK: do you know if Amarok 2.1 beta packages are being worked on or is freeze taking the priority ?
[04:07] <ScottK> daskreech: I don't know of anyone working on them, but I've been mostly offline this week.
[04:08] <daskreech> ok
[04:08] <metellius> ScottK: thanks a lot, that revealed what I believe to be the problem here.
[04:09] <ScottK> metellius: You're welcome.
[04:10] <kb9vqf> daskreech: thanks for the torrent update; I've actually had quite a few leechers, but no one is bothering to seed :-(
[04:11] <kb9vqf> daskreech: other than you, of course
[04:14] <daskreech> kb9vqf: 3 people have agreed to seed
[04:20] <daskreech> which package has the systray plasmoid ?
[04:52] <metellius> I found the problem confusing my build
[04:52] <metellius> what is the deal with lrwxrwxrwx 1 root root 9 2008-12-04 17:16 /usr/include/qt4/phonon -> ../phonon/
[04:53] <metellius> is that a debian/ubuntu symlink?
[04:53] <metellius> FindPhonon.cmake will see that, and assume that KDE-phonon stuff is also in /usr/include/qt4/KDE, while it is actually in /usr/include/KDE
[06:49] <kishore> Is there a PPA or amarok 2.1 in jaunty?
[07:29] <Mamarok> kishore: patience?
[07:29] <Mamarok> Easter Holiday?
[07:31] <jussi01> Mamarok: easter holiday... meh :P
[07:35] <kishore> Mamarok: :)
[09:35] <apachelogger> Mamarok: sounds like an excuse :P
[09:35] <apachelogger> jefferai: any progress on taglib-extras building?
[09:39] <apachelogger> JontheEchidna: I like how much the amarok tarball saves with lzma :D
[09:44] <Mamarok> apachelogger: I know :)
[09:52]  * apachelogger kicked off a testbuild
[09:58] <Quintasan> hi
[10:06]  * jussi01 waves to Quintasan
[10:07] <Quintasan> hmm I will try compiling amarok 2.1
[10:09] <Mamarok> you mean, packaging?
[10:10] <Quintasan> oh, right
[10:10] <Quintasan> packaging
[10:13] <Quintasan> no way
[10:13] <Quintasan> I guess I will wait for someone to do it :/
[10:16] <Mamarok> taglib-extras?
[10:30] <apachelogger> Quintasan: Build started 8 minutes ag
[10:30] <apachelogger> +o
[10:31] <Mamarok> apachelogger: great :)
[10:31] <apachelogger> Quintasan: you could do the backport though
[10:31] <apachelogger> ultimately you would get taglib-extras backported first though ;-)
[10:57] <apachelogger> it is the small things that make me wanna cry
[10:58] <apachelogger> apprently no-one packaged qtscriptgenerator
[10:59] <Sput> Mamarok: there is no easter holiday today :P
[11:06] <Mamarok> Sput: yeah, but people are away anyway, since yesterday till Tuesday, like every year
[11:13] <jussi01> yay, another firefox crash...
[11:14] <jussi01> can anyone reproduce? go to http://brandal.mybrute.com/ type a name, click validate....
[11:15] <apachelogger> wah
[11:15] <apachelogger> JontheEchidna, Riddell: kpk associates with rpm and offers to install them ... I really think we should remove rpm from the desktop file
[11:16] <jussi01> apachelogger: hehe, really?
[11:18] <tsimpson> jussi01: no crash, but I lost :(
[11:18] <jussi01> tsimpson: grrr...
[11:18] <jussi01> I click validate and firefox dies...
[11:19] <tsimpson> I have FF 3.0.8+nobinonly-0ubuntu3 and flash <IP_ADDRESS>ubuntu2
[11:19] <apachelogger> ewwww
[11:19] <apachelogger> qtscriptgenerator got the most awkward build structure
[11:19] <jussi01> hrm... I should check my flash... think it m ight be the 64bit from adobes site...
[11:20] <jussi01> jussi@galaxy:~$ apt-cache policy firefox
[11:20] <jussi01> firefox:
[11:20] <jussi01>   Installed: 3.0.8+nobinonly-0ubuntu3
[11:20] <jussi01> likely flah's fault then
[11:20] <tsimpson> isn't adobe's 64bit flash still in testing?
[11:22] <jussi01> yeah, probaby...
[11:22] <jussi01> http://labs.adobe.com/downloads/flashplayer10.html
[11:35] <jussi01> ok, seems a problem with the 64bit plugin... just deleted it and installed the one from the repos which works...
[11:38] <Mamarok> jussi01: just got a link to that: http://clintbrothers.blogspot.com/2008/11/64bit-flash-on-ubuntu.html
[11:38] <Mamarok> seems to work for him
[11:39] <Mamarok> hm, that blog is form November...
[11:41] <jussi01> Mamarok: yeah, flashplugin was working fine for youtube and the like, just that one site kept crshing
[11:46] <jussi01> oh, and while I have people, can anyone else not sign into msn with kopete atm?
[11:46] <jussi01> it kind of signs in, ie. signs me out of the oter client, bu then nothing happens...
[14:14] <apachelogger> https://wiki.kubuntu.org/HelpingKubuntu needs update and structure and pictures ....ö
[14:31] <apachelogger> Quintasan: please make your stuff on revu match the new requirements (especially karmic instead of jaunty in debian/changelog) ... unless you target 9.04 of course :P
[14:36]  * apachelogger is wondering whom to poke
[14:37] <apachelogger> jussi01: *poke*
[14:41]  * jussi01 prods apachelogger
[14:41] <apachelogger> hum
[14:41] <apachelogger> ah right
[14:41] <apachelogger> jussi01: I suppose you want to do some fancy work?
[14:41] <apachelogger> leading to praise from ScottK and virtual cookies from me
[14:44] <jussi01> apachelogger: that depends...
[14:44] <jussi01> what is it?
[14:45] <apachelogger> a bit of poking people and a bit of being creative
[14:45] <jussi01> yes... so what is it?
[14:45] <jussi01> :D
[14:45] <apachelogger> https://wiki.kubuntu.org shows ubuntu page rather than kubuntu page
[14:46] <apachelogger> https://wiki.kubuntu.org/Kubuntu got loads of useless links in the navigation ... which either should be filled with content or be removed
[14:46] <apachelogger> https://wiki.kubuntu.org/HelpingKubuntu could be a resource for the former
[14:47] <apachelogger> although it is seriously out of date and looks like crap
[14:47] <jussi01> apachelogger: hrm... Ill have a look at it when I get back from the store, but maybe I can do something...
[14:47] <apachelogger> ah, the image on the "join us in #kubuntu..." notice underneat the navigation is broken for years
[14:48] <apachelogger> jussi01: that and the first issue I mentioned just need to be filed as request tickets at the sysadmin's
[14:48] <apachelogger> and maybe some additional poking to get it done quicker ;-)
[14:48] <jussi01> right
[14:49] <jussi01> apachelogger: Im just headed out... too many bottles and not enough food in my house... so Ill have a look when I get back
[14:49] <jussi01> see you soon
[14:49] <apachelogger> aye aye
[16:27] <jefferai> apachelogger: erm, no...I'll look at it right now
[16:57] <neversfelde> is there an english kubuntu based quassel user guide somewhere?
[16:59] <ScottK> claydoh had a good blog post that would server.
[17:00] <ScottK> server/serve
[17:05] <neversfelde> found it, I added Quassel to https://help.ubuntu.com/community/InternetRelayChat. Maybe we should use claydohs post to get a general guide to join #kubuntu and #kubuntu-devel. I can't see how to use these links on https://wiki.kubuntu.org/Kubuntu, they should be deleted.
[17:06] <neversfelde> mhh, wiki is down
[17:07]  * Mamarok despairs about some users in the ML :(
[17:22] <neversfelde> oh no, wiki.kubuntu.org is unusable slow, they should really use MediaWiki :)
[17:48] <dtchen> is pulseaudio now installed by default in Kubuntu?
[17:48] <dtchen> i don't have a current daily-live to check
[17:49] <dtchen> if so, that presents some interesting regressions that need to be fixed ASAP
[17:51] <ScottK> dtchen: It's not, but the lib gets pulled in due to some depends issues.
[18:13] <jefferai> apachelogger: r952369
[18:49] <Quintasan> apachelogger: will do, but after I get back from church :/
[18:49]  * Quintasan hates going to church
[18:51] <daskreech> why?
[18:59] <dtchen> ScottK: an increasing number of kubuntu users are reporting problems against pulseaudio, which means me wonder what's actually causing pulseaudio to be installed
[19:00] <ScottK> dtchen: Dunno.  AFAIK just the lib gets pulled in on install.  Of course if they have both ubuntu-desktop and kubuntu-desktop, that would do it.
[19:01] <dtchen> right, integration mess :(
[19:02] <ScottK> Yep
[19:02] <daskreech> rdepends the lib ?
[19:06] <dtchen> daskreech: yes, it comes from phonon.
[19:06] <daskreech> Qt phonon ?
[19:07] <dtchen> the messy bit is how to work around it for a particular session
[19:08] <daskreech> right Qt is integrating with Gtk stuff so they would need pulseaudio
[19:08] <daskreech> pulseaudio is a near requirement for Gnome now isn't it?
[19:08] <ScottK> It is for Ubuntu
[19:10] <dtchen> ScottK: if you're heading to UDS, we should schedule some time to work out these backend kinks
[19:10] <dtchen> ^ Riddell
[21:51] <_Groo_> hi JontheEchidna
[21:51] <_Groo_> hi/2 all
[21:51]  * jefferai looks forward to apachelogger's scriptgenerator package :-)
[21:52] <_Groo_> jefferai: i did the scripgenerator package also, for amarok 2.1, but im having trouble pleasing my ppa. so i didnt publish amarok 2.1 so far
[21:52] <jefferai> ah, ok
[21:52]  * jefferai looks forward to that then
[21:52] <jefferai> :-)
[21:53] <_Groo_> jefferai: apachelogger is the guy to do it anyway, since it involves adding stuff the to qt path, which is a system package..
[21:54] <_Groo_> jefferai: thats why i didnt publish it yet.. im scared it might break some qt stuff
[21:54] <_Groo_> didnt for me but...
[21:55] <_Groo_> JontheEchidna: are you alive?
[22:06] <JontheEchidna> hi
[22:07] <_Groo_> hi JontheEchidna
[22:07] <_Groo_> remember the flash webkitpart bug i talked about the other day? cant you do a tinny little test?
[22:08] <JontheEchidna> sure
[22:09] <mcas> JontheEchidna: what about the meeting next week?
[22:09] <_Groo_> JontheEchidna: go the the konki settingd and change the plguin load to on demand, then go to any flash site and change to webkit.. when the load button appear, click on it.. flash should work fine then. if you change the settings to on the fly plugins, it will load behind the white layer as usual
[22:10] <JontheEchidna> mcas: nevermind about my email. We should schedule the meeting based on the most popular vote
[22:10] <mcas> JontheEchidna: ok because we have a clear vote for tuesday
[22:11] <mcas> is this ok for the encryption issues?
[22:12] <JontheEchidna> We decided that it wouldn't be worth it to update the svn snapshot, since it's just as broken there
[22:12] <JontheEchidna> _Groo_: it works!
[22:13] <JontheEchidna> oh, forgot to switch to webkit
[22:13] <_Groo_> JontheEchidna: i already added the workaroung to my bug report in bugs.kde, lets see if the webkitpart devs have anythng to say
[22:13] <neversfelde> I remember a doodle vote for the meeting?
[22:13] <_Groo_> JontheEchidna: it will work :)
[22:14] <mcas> neversfelde: yes but there was a request on the mailing-list
[22:14]  * neversfelde looks
[22:14] <JontheEchidna> _Groo_: start plugin is greyed out in webkit mode
[22:15] <_Groo_> JontheEchidna: strange, it works for me.. webkit + start plugin..
[22:15] <_Groo_> JontheEchidna: but im using svn code from today anyway
[22:15] <JontheEchidna> yeah, maybe that's it
[22:16] <_Groo_> JontheEchidna: thanks for the test.. lets wait for proper answers from teh devs
[22:26] <_Groo_> JontheEchidna: maybe it would be a good idea to update the webkitpart package in jaunty to latest dev?
[22:38] <jjesse> question:  i am not getting notified of any updates available for jaunty until i run apt-get update
[22:38] <jjesse> once i ran apt-get update i was notified by software updates that i had 186 updates
[22:47] <neversfelde> jjesse: automatic infos of updates work for me, at least till this morning
[22:47] <jjesse> neversfelde: i only get updates if i run apt-get update first
[22:48] <jjesse> running jaunty amd64 if it mtters
[22:53] <_Groo_> JontheEchidna: jon just did packages for rekonq 0.0.4 and arora 0.6... interested?
[22:54] <JontheEchidna> the thing about updating packages right now is that it's a serious pain to have them be uploaded, even for bugfix releases
[22:54] <JontheEchidna> since we are in final freeze
[22:54] <_Groo_> JontheEchidna: even for universe?
[22:55] <JontheEchidna> yeah, aside from the Feature Freeze exception we'd probably need for webkitkde, we'd also need a MOTU-council person to OK it
[22:55] <_Groo_> JontheEchidna: maybe you ould send me an email with proper paths to uploading packages since i dont have that much time to go through the bureocracy
[22:56] <_Groo_> so i can contribute more after the feature freeze
[22:56] <JontheEchidna> uploading where?
[22:56]  * JontheEchidna is a bit confused
[22:56] <_Groo_> i have ready and tested packages for k3b 2.0 beta1 that should be out soon
[22:56] <_Groo_> JontheEchidna: uploading to the proper kubuntu queue for review and acceptance?
[22:57] <JontheEchidna> oh, that's the part that needs the beaurocracy :P
[22:57] <_Groo_> JontheEchidna: exactly.. what i mean is.. can i use you as a proxy?
[22:58] <_Groo_> JontheEchidna: at least in the inicial process. after a while some motu might ask, hey who is this groo that keeps apearing in the maintainer package control ;)
[22:58] <JontheEchidna> lol
[22:59] <JontheEchidna> to be honest, I have a somewhat sizable todo list of bugs to fix in the core KDE packages :(
[22:59] <JontheEchidna> I mean, I don't like saying no, but under the circumstances...
[23:00] <_Groo_> JontheEchidna: can you point any poor soul, err i mean volunteer that could proxy for me?
[23:01] <JontheEchidna> smarter has an interest in both webkitkde (he's the one that generally looks after it) and has expressed interest in seeing arora 0.6 in 9.04
[23:01] <JontheEchidna> you could try asking him & giving him free cake next time you see him ;-)
[23:01] <_Groo_> JontheEchidna: i dont mean webkit poackages for jaunty but uploading packages in general, it can wait after jaunty is launched
[23:02] <JontheEchidna> oh, new packages?
[23:02] <_Groo_> im a prolific package builder :P but since i have real work i can only dump them in the weekends
[23:02] <neversfelde> JontheEchidna: just wrote this interview, you remember?
[23:02] <JontheEchidna> neversfelde: I was beginning to wonder :P
[23:03] <_Groo_> like amarok 2.2 svn packages, new and newer arora, rekonq, webkitpart, k3b, k9copy, just to name a few
[23:03] <neversfelde> hehe, sorry, little time
[23:03] <JontheEchidna> neversfelde: ya, I understand :)
[23:03] <neversfelde> I will send it tomorrow, ok?
[23:03] <JontheEchidna> sure thing
[23:03] <neversfelde> sehr gut :)
[23:04] <JontheEchidna> _Groo_: ok, I've been a bit confused. lemme try to explain the current situation
[23:05] <JontheEchidna> New packages will have to be uploaded to revu for reviewing, which can be done any time during the cycle. (but can only be uploaded to ubuntu when it's open for development)
[23:05] <JontheEchidna> Updates for packages usually are uploaded to bug reports on launchpad for sponsorship
[23:06] <JontheEchidna> updates at this point in time would either need to: a) go through the beaurocracy for inclusion in jaunty
[23:06] <JontheEchidna> or
[23:06] <JontheEchidna> b) wait until Karmic is open for development next month for uploading
[23:07] <_Groo_> JontheEchidna: ok but i dont have the time to hunt the specifics down, so what i was sugesting is, send my packages to you or someone else, and you redirect them to the proper slots.. at least i can get the hang of the specific bureocratics
[23:07] <JontheEchidna> new packages will have to wait for karmic regardless
[23:07] <_Groo_> and by sendind to you, i was talking after karmic starts accepting
[23:08] <JontheEchidna> after karmic starts there isn't beaurocracy for packaging updates
[23:08] <JontheEchidna> new packages by you will have to be uploaded to revu by you
[23:08] <JontheEchidna> there's no way around that bit
[23:08] <_Groo_> what is the url then?
[23:09] <JontheEchidna> Here's a good link: https://wiki.ubuntu.com/MOTU/Packages/REVU
[23:10] <JontheEchidna> there's a little bit of signing up to do before-hand, but after that it's as simple as dputing it to revu
[23:10] <maco> using dimap w/ kmail to access gmail, anyone notice it sits there at "retrieving folder namespace" forever and then once you click "abort" it goes on fine? this is just since whatever update made dimap's syncing really fast
[23:11] <_Groo_> ok, checking
[23:11] <maco> new packager?
[23:12] <JontheEchidna> somewhat, he's done quite a bit of work for getdeb
[23:12] <maco> oooooo
[23:12] <JontheEchidna> just new to the ways of the Ubuntu ;-)
[23:12] <_Groo_> JontheEchidna: ahh easy :) gonna check this tomorrow :)
[23:12] <maco> getdeb was quite useful til i learned to package
[23:13] <_Groo_> maco: it will change to the repo way soon.
[23:13] <_Groo_> getdeb i mean
[23:13] <maco> (useful to me, i mean...for others still useful. for me, i just pbuild whatever i want anyway)
[23:13] <_Groo_> we are still studying the specifics
[23:13] <maco> ive never set up a deb repo before, just rpm *shrug*
[23:13] <_Groo_> maco: true, but thats the idea.. first you consume, then you argue, finally you contribute
[23:14] <maco> argue?
[23:14] <_Groo_> i mean .. hmm.. dammit.. whats the word
[23:14] <_Groo_> investigate,
[23:14] <maco> what, you mean the flamewars on development mailing lists?
[23:14] <_Groo_> hmm
[23:14] <maco> oh ok
[23:14] <maco> learn?
[23:15] <_Groo_> in the sense of learning but not quitte
[23:15] <_Groo_> when you start being curious about how packaging works
[23:15] <_Groo_> digging!
[23:16] <_Groo_> consume, dig, contribute
[23:16] <maco> most people dont get past "consume" ;)
[23:17] <_Groo_> maco: but the ones like ourselfs who do pass beyond the blue pill want to give back after a time..
[23:22] <_Groo_> well gotta go now, see ya JontheEchidnaim gonna go through the proper revu procedures, thanks again
[23:22] <maco> _Groo_: i get the impression there are people who want to but think they need to code
[23:22] <_Groo_> maco: maybe a better understanding of what is packaging might help..
[23:23] <maco> they dont realize that MOTU = developers = packagers
[23:24] <_Groo_> maco: you need at least bash scripting, but its not as hard as , say, learning qt/c++ , its feasible to the average power user
[23:24] <maco> not all packages even need maintainer scripts though
[23:25] <_Groo_> see ya all later... seeya maco
[23:25] <maco> bye
[23:25] <_Groo_> maco: true.. with cdbs our life got easier
[23:29] <neversfelde> JontheEchidna: questions send. Thank you :)
[23:30] <sebas> maco: there's actually an update hanging
[23:30] <maco> sebas: what do you mean?
[23:30] <sebas> Due to some socket timeout, cancelling it will indeed cancel that mailjack and procede to the next pending one
[23:31] <sebas> Happens after suspend for example, or if the network had problems
[23:32] <sebas> I think it's fixed in the latest kmail though, at least it didn't bother me lately
[23:32] <sebas> pff, s/mailjack/mailcheck btw :)
[23:32] <maco> dtchen says if you're right, it's te same issue i had in evolution
[23:32] <maco> he thought it was a libc issue
[23:33] <maco> ok he says i remember wrong
[23:33] <sebas> Not sure where the bug's exactly
[23:33] <maco> i thought he said something about libc when evo was having socket issues on resume that made me have to quit evolution and restart it, but he says he didnt say that
[23:34] <sebas> Ah, in kmail just cancelling the mail check is enough
[23:34] <maco> yeah evolution's not that smart
[23:35] <sebas> You mean "Evolution is not intelligent design"? ;)
[23:35] <sebas> gotta put the girl back to bed, woke up by a thunderstorm that went over


[05:27] <Unit193> bluesabre: Yeah I use  gpg-agent --daemon --write-env-file "${HOME}/.gnupg/gpg-agent-info"  somewhere else.
[12:54] <knome> bluesabre, flocculant: ?
[12:57] <knome> kryten, you still around?
[12:57] <kryten> Yes.
[12:57] <knome> you running xenial?
[12:58] <kryten> Nope.
[12:58] <knome> bah
[13:01] <knome> bluesabre, when you set --> APT::Periodic::Unattended-Upgrade "!"; <-- in /etc/apt-/apt.conf.d/20auto-ugprades, the "When there are security updates" dropdown box gets grayed out in Software & Updates -> tab Updates
[13:01] <knome> bluesabre, the stupid thing here is that it doesn't show any value there, so the user can't confirm they are installed daily unless they know to look in the aforementioned file
[13:03] <knome> ahhh, bug 1018367
[13:03] <knome> not old or anything
[13:04] <knome> ohh, a very good comment there "Is there a massively effective corporate (MS?) sabotage unit working inseide the core of linux community?"
[13:07] <knome> and yes, there it is, reported by flocculant in bug 1554099
[13:07] <knome> :D
[13:39] <knome> slickymaster, do we want to keep https://wiki.ubuntu.com/Xubuntu/Documentation ?
[15:26] <flocculant> knome: am now - and I see you found stuff
[15:27] <knome> yep
[15:27] <knome> that was it
[15:27] <flocculant> :)
[15:54] <dkessel> wow, i would have thought the tons of package installation errors on an upgrade to be gone at this time in the cycle.... :/
[15:55] <flocculant> dkessel: nope
[15:55] <flocculant> when it's not broken I'll mail the list about testing it again :)
[15:55] <dkessel> ok, reverting that VM then....
[15:55] <flocculant> anyone trying to upgrade 14.04 to 16.04 is in for a bumpy ride :p
[15:56] <flocculant> last I checked 15.10 to 16.04 worked
[16:04] <dkessel> well i just tried 15.10 to 16.04 ;)
[16:07] <flocculant> dkessel: it failed?
[16:08] <flocculant> 2 weeks ago 15.10 to 16.04 was working
[16:10] <dkessel> flocculant: yeah, i got all those systemd, init, xubuntu-desktop, etc. installation errors
[16:11] <flocculant> mmm
[16:11] <flocculant> davmor2: were you getting upgrade fails on 15.10 to xenial ?
[16:12] <davmor2> didn't get that far but I would imagine it would hit a similar issue
[16:12] <flocculant> mmm
[16:12] <flocculant> 2 weeks ago it was working - today not it seems
[16:13] <flocculant> at least a vanilla vm install did
[16:13] <davmor2> flocculant: yeah but that was the same with 14.04 it was working a week or two before feature freeze and then died horribly afterward
[16:14] <flocculant> davmor2: I've not got 14.04 to upgrade ever
[16:14] <flocculant> though it's not something we test really regularly
[16:14] <davmor2> indeed
[16:15] <flocculant> well - that's a stupid comment ... can only do it once every 2 years anyway lol
[16:15] <davmor2> :D
[16:15] <flocculant> dkessel: can you get at logs?
[16:16] <flocculant> if not I'll do something - would at least like to know where it fails and if it is the same
[16:16] <davmor2> flocculant: and between 10.06 and 12.04 and 14.04 there weren't as many lib changes and abi breaks as there are from 14.04 to 16.04 either
[16:16] <flocculant> yea
[16:17] <davmor2> gcc, bluez, amd gfx stack, nm when that lands and the list goes on
[16:18] <flocculant> he he he
[16:19] <dkessel> flocculant: logs are gone... just rolled back the vm
[16:19] <xubuntu84w> i need to make a bootable .iso of my usb drive live session. dd worked fine in ubuntu, but not in xubuntu.  how can i do this?
[16:19] <flocculant> the price of progress - grey hair or if really unlucky bald head
[16:19] <flocculant> xubuntu84w: #xubuntu is the support channel
[16:19] <xubuntu84w> bbut it's for rolling a distribution
[16:20] <flocculant> but if it doesn't work in xubuntu then I'd wonder what was going on as that deep - they are the same thing
[16:20] <xubuntu84w> i'm booting into a live session, making changes for my company, then turning that session into an .iso to be used again
[16:21] <flocculant> remastersys type thing - suppport is best for that
[16:21] <xubuntu84w> it isn't recognized as an .iso like when the dd command is done in ubuntu, but recognizes it as a raw dd image
[16:21] <xubuntu84w> okay
[16:21] <flocculant> and to be honest #ubuntu has more eyes if it's slow in #ubuntu
[16:43] <knome> flocculant, asking you again about the testing pages on the wiki - what do you want to do with them - should i just move them to the new wiki?
[16:45] <flocculant> knome: hardware profile is dead, team hardware never really got much traction or use
[16:45] <knome> flocculant, team hardware might be useful if it was linked in a sane way to the iso tracker...
[16:45] <knome> flocculant, that said, i think it should probably come from your LP account, which is out of our reach
[16:45] <flocculant> meant to discuss this the other day when I was editless on the wiki :p
[16:45] <knome> heh
[16:45] <flocculant> knome: the hardware option on the tracker is gone now
[16:46] <knome> i know
[16:46] <knome> so just delete the hardware page?
[16:46] <knome> or would it be useful to track this in some other way?
[16:46] <flocculant> well that or just move the used one to where we're moving
[16:46] <knome> ok
[16:47] <knome> i'll move it and we can then see what we want to do with it
[16:47] <knome> i think there are some good bits there, like GPU stuff
[16:47] <flocculant> no no
[16:47] <knome> no?
[16:47] <knome> :D
[16:47] <flocculant> I meant just leave the 3 at wiki.u.c/xubuntu/testing
[16:47] <knome> oh...
[16:47] <flocculant> only have the release note on at the xubuntu wiki
[16:48] <knome> i think that's actually the only one we want in the ubuntu wiki
[16:48] <knome> ...considering we will be releasing the release notes there
[16:48] <flocculant> why?
[16:48] <knome> that's mostly because the markup is different
[16:48] <flocculant> why aren't we moving that to ours?
[16:48] <flocculant> oh mmm
[16:48] <knome> not sure if the release team would be okay with that
[16:49] <knome> or to be more exact, if they would just have them in one place
[16:49] <flocculant> they aren't in one place :p
[16:49] <knome> if they don't mind, then i'm fine with moving it
[16:49] <knome> well, yeah...
[16:49] <knome> that's why i said "rather"
[16:53] <flocculant> https://wiki.ubuntu.com/WilyWerewolf/ReleaseNotes/Kubuntu
[16:53] <knome> right
[16:53] <knome> though they do have that page that links to another page
[16:54] <knome> so the main release notes page links to wiki.ubuntu.com
[16:54] <knome> the question is, can kubuntu, and could we, link directly to $something_else
[16:54] <knome> and the other thing we've discussed before is if we need separate announcement/notes
[16:54] <knome> clearly kubuntu doesn't do that (any more)
[16:54] <knome> and then also,
[16:55] <flocculant> well
[16:55] <knome> one thing just occurred to me, there's the added benefit to staying in the ubuntu wiki that we can include the common stuff
[16:56] <flocculant> if I was me looking in on the 2 of our things - the website 'ooh pretty' post would leave me cold - more inclined to want things like changes than that
[16:56] <knome> well yeah
[16:56] <knome> i do think that there's a place for both
[16:56] <flocculant> yea
[16:56] <knome> and they serve a different purpose (which are both okay)
[16:56] <knome> just bringing that up
[16:56] <flocculant> wiki for the detail, website for the sell
[16:56] <knome> yes
[16:56] <flocculant> and good point on includes
[16:57] <knome> or from other POV, wiki for the technical stuff, website for the non-technical
[16:58] <flocculant> yea that's my thinking
[16:58] <knome> yep
[16:58] <flocculant> thinking of includes though - then do we want to move the meeting stuff?
[16:58] <knome> yes, since we're only including the meeting minutes
[16:58] <knome> which should be moving too
[16:59] <flocculant> so we can include internal - external is a problem?
[16:59] <knome> yes
[16:59] <flocculant> ok
[16:59] <knome> or at least totally not so clean and dependable on
[16:59] <flocculant> then we have to leave release notes on wiki.u.c imo
[16:59] <knome> yes, that was what i was thinking
[17:00] <flocculant> or it'd be some bizarre mishmash of what kubuntu did and the includes
[17:00] <flocculant> which is meh
[17:00] <knome> yeah, let's not mix two wikis together
[17:00] <flocculant> nope
[17:01] <dkessel> +1 on not mixing two wikis (without reading the discussion :p )
[17:01] <flocculant> ha ha
[17:02] <knome> nice curry aroma here
[17:02] <knome> flocculant, anyway, about the other testing pages...
[17:03] <knome> flocculant, i would probably just remove the hw pages if those aren't actively used
[17:03] <knome> flocculant, that said, if we figure out an active use for them, we likely want to move them to the new wiki because that's so much faster and we can control the stuff ourself
[17:03] <flocculant> one is definitely pointless the other doesn't even have the QA lead on it
[17:03] <knome> yep
[17:04] <flocculant> ok
[17:04] <knome> we can point those pages to the contributor docs
[17:04] <knome> so people who access them aren't left in the cold
[17:04] <flocculant> move https://wiki.ubuntu.com/Xubuntu/Testing/TeamHardware to us
[17:04] <knome> mhm
[17:04] <flocculant> kill the https://wiki.ubuntu.com/Xubuntu/Testing/HardwareProfile
[17:04] <knome> ok
[17:05] <knome> flocculant, would http://docs.xubuntu.org/contributors/qa-team.html be a fair target for the redirect?
[17:05] <knome> anyway, dinner time
[17:05] <knome> bbiab
[17:05] <flocculant> not sure what you mean - ping me later
[17:15] <knome> flocculant, i mean that when i "delete" the page, i could instead just point it to some other location
[17:15] <knome> that would have somewhat relevant information
[17:15] <knome> if somebody ends up to that page
[17:16] <flocculant> can you not redirect to our wiki copy?
[17:16] <flocculant> rather than docs
[17:16] <knome> flocculant, for the "kill"?
[17:16] <flocculant> oh sorry - thought you meant the other :D
[17:16] <knome> no, that i will of course redirect to the new page
[17:16] <flocculant> hang on - I think it's a copy of something else :p
[17:16] <knome> haha
[17:16] <knome> ok
[17:17] <flocculant> https://wiki.ubuntu.com/QATeam/Hardware
[17:18] <flocculant> redirect to there :)
[17:18] <knome> i will
[17:18] <flocculant> you can see where I've been on that page pretty easily :)
[17:19] <knome> heh
[17:19] <flocculant> what our qa docs don't have is anything about ordinary testers really
[17:19] <knome> :)
[17:20] <flocculant> the qa team page is really really qa team
[17:20] <knome> yep
[17:21] <flocculant> might get one done soonish - so it can all be up to date by release time
[17:21] <knome> :)
[17:21] <flocculant> I have another thing to add to the team page responsibility wise
[17:21] <knome> remember we can update the website docs whenever we want
[17:22] <flocculant> I didn't know that :)
[17:23] <flocculant> I think I'll do that 'really' soon
[17:23] <flocculant> then include link to that moved page
[17:23] <knome> docs. is now on the dev server
[17:23] <knome> so if you need anything changed there, you can ping me, pleia2 or ubottu
[17:23] <knome> Unit193 rather
[17:24] <flocculant> :)
[17:24] <flocculant> ok - well I'll get this all done - then it can be updated, cos chapter 3 current is really chapter 6 ;)
[17:24] <knome> yep
[17:24] <knome> let's coordinate that then
[17:25] <flocculant> yep
[17:25] <flocculant> I'll make a start today on that
[17:25] <knome> :)
[17:25] <flocculant> I'll even add it as a task so I can look good :p
[17:26] <knome> hahah
[17:33] <flocculant> knome: mmm - so much of what I'll put in this tester page will link to places that exist in http://docs.xubuntu.org/contributors/common-reference.html#qa-team-links
[17:33] <flocculant> so that will then end up with next to nothing in it
[17:34] <flocculant> that's not referenced somewhere else - any need to keep that #qa-links do you think seperately?
[17:51] <knome> so let's see..
[18:10] <flocculant> knome: do you mean wait and see?
[18:10] <flocculant> wfm if so :)
[18:13] <knome> for you, yes
[18:13] <knome> http://wiki.xubuntu.org/qa/teamhardware
[18:13] <knome> adding the redirect next
[18:13] <flocculant> thanks
[18:14] <knome> and done
[18:14] <flocculant> mmm
[18:14] <flocculant> just thought of a relevant point here
[18:15] <knome> which is?
[18:15] <flocculant> if I say to people - hey there is this list which we use to point specific people at testing things - they can't edit it ...
[18:15] <flocculant> well
[18:16] <knome> true, but they can't edit in the ubuntu wiki either if they aren't on the right teams
[18:16] <flocculant> not as simply as people can wiki.u.c
[18:16] <knome> and the page is (at least so far) team hardware
[18:16] <flocculant> knome: yea - only really because way back it was a 'oh crud really need to get *this* tested on *that* - who in team can we pester
[18:17] <knome> yep
[18:17] <flocculant> but to be really useful it would be nice to tie active testers there
[18:17] <knome> practically i don't see this as a big problem - those who we can depend on situations where we need exact testing are limited in quantity
[18:17] <flocculant> I guess asking to edit that would lose the not active people
[18:18] <flocculant> yea - same point :)
[18:18] <knome> well, just tell them to be in touch with ~xubuntu-website and we'll create accounts for them
[18:18] <flocculant> and will have read the dev docs - so not *just* drive by testers
[18:18] <knome> yep
[18:18] <knome> we'll have to consider the registration
[18:18] <knome> but yeah
[18:19] <knome> so far point people to -web
[18:19] <flocculant> for the moment - not a major issue thinking more :D
[18:19] <flocculant> anyway - thanks for doing that - means I have the link :p
[18:19] <knome> yep, no
[18:19] <knome> *np
[18:19] <flocculant> :)
[18:19] <flocculant> dinner time now
[18:19] <flocculant> biab
[18:19] <knome> bon appetit
[18:22] <knome> flocculant, for when you get back...
[18:22] <knome> flocculant, since https://wiki.ubuntu.com/Xubuntu/Testing/ is practically orphan now, do you want it to be redirected to the website page it has a link to right now, or to the contributor docs?
[18:23] <knome> flocculant, or the new wiki landing page (which is quite quiet so far)
[18:24] <flocculant> knome: I just need to be able to get at https://wiki.ubuntu.com/Xubuntu/Testing/ReleaseNoteBase
[18:24] <knome> flocculant, i'll likely move it to Toolbox, but i'll poke you again then
[18:24] <flocculant> when I say dinner time - I mean in and out while I'm doing it
[18:24] <flocculant> ok
[18:24] <knome> and removing that page doesn't stop you from getting there anyway
[18:24] <knome> it's just a page without a parent
[18:24] <flocculant> yea ofc - just making it plain I need it :D
[18:24] <knome> well, a page with a parent that has a redirect...
[18:24] <knome> ack
[18:25] <knome> so where to point that?
[18:25] <flocculant> https://wiki.ubuntu.com/Xubuntu/Testing/ > contributor docs please :)
[18:25] <knome> http://docs.xubuntu.org/contributors/qa-team.html this one?
[18:25] <flocculant> nope
[18:26] <flocculant> it'll be qa-tester when it's there
[18:26] <knome> ah, ok
[18:26] <knome> i'll just point it there already...
[18:26] <knome> :P
[18:26] <flocculant> which will be chapter*1* of the qa stuff
[18:27] <knome> and done
[18:27] <flocculant> so testers - iso's - bugs - team
[18:27] <flocculant> is the order
[18:27] <knome> it's -tester now
[18:27] <knome> should it be +s?
[18:27] <flocculant> cool - ty :)
[18:27] <flocculant> the file is tester
[18:28] <knome> goodie
[18:28] <flocculant> but can be +s :)
[18:28] <knome> it's tester now! :P
[18:28] <flocculant> \o/
[18:28] <flocculant> or testerooney :D
[18:28] <knome> nooo
[18:28] <flocculant> ha ha ha
[18:28] <knome> neither testerole
[18:28] <knome> see what i did there
[18:28] <knome> tester(r)ooney
[18:29] <knome> tester(c)ole
[18:32] <flocculant>  :)
[18:46] <knome> bluesabre, interesting discussion on -release
[19:09] <flocculant> davmor2 dkessel - upgraded 15.10 to 16.04 without apparent issue here jfi
[19:11] <davmor2> flocculant: nice I'll do a run after I still think it is gcc that is biting us which would make sense as 14.04.4 is the much older version that is incompatible with the one in 15.10/16.04 but we'll see
[19:13] <flocculant> yep - just thought I would let you know :)
[19:14] <davmor2> flocculant: thanks
[19:35] <pavlushka> flocculant, you there?
[19:36] <flocculant> ish
[19:36] <pavlushka> busy?
[19:36] <flocculant> always - but often got time to talk to people as well :)
[19:37] <pavlushka> lol, if you please tell me a little in details about the email you sent to the mailing list about package tracker.
[19:38] <flocculant> pavlushka: have you been to the package tracker?
[19:38] <pavlushka> ya
[19:38] <flocculant> ok - so it is split into sections
[19:39] <pavlushka> yes
[19:39] <pavlushka> I can see that
[19:39] <flocculant> the top section - all of those 7 have bugs listed against them
[19:39] <pavlushka> different category, different priority.
[19:40] <pavlushka> yes
[19:40] <flocculant> basically test those applications - see if you can confirm the bug(s)
[19:40] <pavlushka> got it.
[19:40] <pavlushka> and?
[19:40] <flocculant> it's been a while since I called for package testing - there have been lots of updates since then
[19:40] <pavlushka> good.
[19:40] <flocculant> then report on the tracker - if you see the same bug - use the number listed
[19:41] <flocculant> for example
[19:41] <flocculant> http://packages.qa.ubuntu.com/qatracker/milestones/350/builds/105268/testcases/1559/results
[19:41] <flocculant> right at the bottom - all the bugs people have seen
[19:41] <flocculant> those need confirming again
[19:42] <flocculant> you can 'me too' a bug - but most importantly - report on the tracker
[19:42] <pavlushka> on it
[19:42] <flocculant> that is where I look
[19:42] <pavlushka> ok.
[19:43] <pavlushka> thanks
[19:44] <pavlushka> I might ask you if I had any confusions later about it.
[19:44] <flocculant> yea that's fine :)
[19:45] <pavlushka> that's great for me, :)
[19:45] <flocculant> :)
[19:45] <pavlushka> night.
[19:45] <flocculant> I'm about for
[19:45] <flocculant> sigh
[19:46] <flocculant> I'm about for ~2 or 3 hours
[20:17] <flocculant> knome: well that was hard work with me and bazaar for a minute there ... try and remember bzr add next time ...
[20:17] <flocculant> anyway - done that now - index is right too
[20:31] <knome> hahah :)
[20:42] <flocculant> knome: I assume that docs update will grab the newest dvd/encryption stuff too?
[20:43] <knome> yep
[20:43] <knome> well
[20:43] <knome> no
[20:43] <flocculant> ok ...
[20:43] <knome> because the 16.04 user docs aren't up already
[20:44] <flocculant> oh right
[20:44] <flocculant> but they are on the iso?
[20:44] <knome> don't know if bluesabre and slickymaster coordinated a docs upload already
[20:45] <knome> yeah, three days ago
[20:45] <knome> well i did know
[20:45] <knome> just didn't remember...
[20:46] <knome> and no, the dvd stuff isn't in yet
[20:46] <knome> that was merged after the upload
[20:46] <knome> bluesabre, doc string freeze is this thursday, let's do another -docs upload on wednesday
[20:46] <knome> flocculant, there ^
[20:47] <kryten> knome: That doesn't matter for that though.
[20:47] <flocculant> kryten: what doesn't matter?
[20:47] <knome> kryten, string changes aren't subject to string freeze? o.O
[20:47] <flocculant> knome: ack all that
[20:47] <kryten> Upload.
[20:47] <knome> kryten, i acknowledge they are "bug fixes", but otoh, the freeze is there also for translations
[20:47] <flocculant> k
[20:48] <knome> kryten, technically, it doesn't block translators from doing their thing, but socially, i think it's good to do the upload before the freeze
[20:49] <knome> we don't like others breaking freezes, and we shouldn't do that ourself, even if it only concerned us
[20:52] <flocculant> so the end result of that is 'Wednesday' I think :)
[20:52] <knome> yes
[20:52] <flocculant> :)
[20:53] <kryten> knome: I agree that it's nice to do an upload when the final translation period begins, but wouldn't it make more sense to do that *after* the freeze then? :P
[20:54] <knome> well, the process is that you do it before freeze because after that everything is frozen...
[20:54] <knome> that's just how it goes
[20:54] <kryten> The strings are frozen.
[20:54] <knome> nope
[20:55] <knome> well, for us, practically, yes
[20:55] <knome> but we can change them before thursday as much as we want
[20:56] <knome> i guess this is minutiae related to the freeze process and customs
[20:56] <flocculant> oh good
[20:56] <knome> all freezes work in the "upload before freeze" way
[20:56] <knome> if you want to land a feature, you will need to land it before the freeze
[20:56] <knome> not upload it after the freeze
[20:57] <knome> kryten, then there's of course the other freeze for translations
[20:57] <flocculant> going to change all the the's to teh's and see if kryten notices
[20:57] <knome> ;)
[21:00] <Unit193> knome: Right, but IMO that's a bit different, feature freeze that is.  String freeze is so translators don't have to hit a moving target.
[21:01] <knome> Unit193, ack, but as i said, i don't think the question is technical but social
[21:01] <knome> the fact that something is available and translatable somewhere is different than uploaded in the distro
[21:01] <Unit193> Sure, but that's to address the latter arguments.
[21:02] <knome> again practically not, but socially it means much that we put our work out and let everybody know what we're going with
[21:02] <knome> i understand your point and don't really even disagree
[21:02] <knome> but if we have upload permissions for the package and are not so limited in time that we really just can't get it in, it's good for all preparation to just do it
[21:28] <ochosi> bluesabre: obviously! it's the gtk3 port that goes along with xfce 4.14 ;)
[21:41] <knome> flocculant, Unit193, kryten: we should take it here though
[21:41] <knome> but a target for .1, what about that?
[21:41] <Unit193> flocculant: Right, and at this point can't really fine tune it anyway.
[21:41] <flocculant> Unit193: ack
[21:42] <flocculant> knome: *shrug*
[21:42] <knome> freeze periods are shorter for .1, so a lot of time to tune it too
[21:42] <knome> or it can be any other time we want to push it out, between main release and .1 too
[21:42] <flocculant> let's wait and see what happens this week
[21:42] <knome> sure
[21:42] <knome> again just laying out potential options we might have to consider
[21:43] <knome> so it's not "all lost" even we don't make main release day
[21:43] <flocculant> yea ofc
[21:43]  * knome wants things to happen more than find guilty people ;)
[21:43] <flocculant> myth didn't make release day with their 14.04
[21:43] <knome> yep
[21:43] <knome> that's been done before
[21:43] <knome> and this isn't ever our main image
[21:44] <flocculant> yea - same - couldn't care what *happened*
[21:44] <flocculant> just not going to say yea ok if I'm not happy is all :)
[21:44] <Unit193> Little time to fine tune so that's not really great from my/dev standpoint, and of course I'll defer to flocculant anyway.
[21:44] <flocculant> .1 would be August ish?
[21:45] <knome> julyish
[21:45] <knome> .2 februaryish
[21:45] <knome> at least if the schedule is sameish to 14.04.xish
[21:45] <Unit193> Point releases are created differently, sooo.  Will have to diff the manifest.
[21:46] <knome> Unit193, technical issue, that's overcomableish
[21:46] <flocculant> right so - given b2 is next week and release is only 6 weeks - not going to be fun
[21:46] <knome> :P
[21:46] <knome> yes, that's why i brought up .1 already, even if we got base for b2
[21:47] <flocculant> if it makes it easier from the dev side (assuming assumptions) to do it for April - then we can but try
[21:47] <flocculant> it depends on what response we get
[21:48] <flocculant> I'd be much less happy +1ing core with 2 or 3 reports than I would the main images
[21:48] <knome> yes
[21:48] <Unit193> flocculant: Know of "anything wrong" with the current installer?
[21:48] <knome> there's still a lot of variables, so releasing base with the main images in april totally isn't impossible either
[21:49] <flocculant> but if we managed to get it right pre RC - that's 2 weeks to hack at testing it
[21:49] <flocculant> Unit193: the normal image one - or the debian one ?
[21:49] <Unit193> ubiquity.
[21:49] <flocculant> nothing major that I know of
[21:50] <flocculant> vbox things - but I ignore those anyway
[21:51] <flocculant> swap issues for some
[21:52] <flocculant> encryption oddities
[21:52] <flocculant> but some of these are drive-by's - no idea who they are, no idea of the veracity of the claims
[21:53] <flocculant> some random guy called bluesomething had the swap issue
[21:53] <flocculant> :p
[21:53] <Unit193> blueninja, weird fella.
[21:53] <flocculant> for sure
[21:54] <flocculant> so - basically at this point - our main images from ubiquity are in good shape
[21:54] <flocculant> I can get 15.10 to upgrade
[21:54] <flocculant> no-one can get 14.04 to upgrade
[21:54] <flocculant> not looked at core for months so no real idea tbh
[21:54] <Unit193> Sorry for not giving details, but all I got is "attempted to install, but the installer crashed twice. It is a dual boot with Windows XP, with a custom /boot en / partition. Oh, and I installed from flash drive, vreated using Unetbootin 613."
[21:55] <flocculant> is more or less where we stand currently
[21:55] <Unit193> flocculant: Nono, that's fine.  Slicky has been really handy there.
[21:55] <flocculant> yep I know :)
[21:55] <flocculant> I do notice that stuff going on
[21:55] <flocculant> Unit193: ^^ that from the mail you got?
[21:56] <flocculant> to be frank - are we still install xubuntu-minimal or whatever the task is in tasksel from the mini.iso?
[21:56] <Unit193> flocculant: Yeah, rebuilding the iso then going to respond trying to get some deailts/logs.  Just figured I'd poke you first and see if you knew of a global issue.
[21:56] <flocculant> nope
[21:56] <flocculant> but doesn't it use d-i not ubiquity?
[21:57] <Unit193> My images.
[21:57] <flocculant> oh right - so ubiquity then
[21:57] <flocculant> I kind of ignored it waiting for the image to be built like the rest :)
[21:58] <flocculant> Unit193: where are they? I can run them tomorrow here on hardware
[21:58] <Unit193> flocculant: You really don't need to, my problem.  But, https://unit193.net/xubuntu/core/pending/
[21:59] <flocculant> not a problem running them to see where it stands :)
[22:00] <Unit193> New isos up any minute, when amd64 finishes.
[22:01] <flocculant> ok
[22:01] <Unit193> Well, thanks then.
[22:02] <flocculant> np :)
[22:05] <Unit193> I presume you don't need a CC?
[22:05] <flocculant> what's that?
[22:05] <Unit193> Sending a reply now anyway, could carbon copy you.
[22:05] <flocculant> oh right - nah
[22:06] <flocculant> if there's something I need to know I'm sure you'll tell me :)
[22:06] <flocculant> anyway - going to crash now, I'll zsync them both tomorrow and have a look see what gives :)
[22:07] <Unit193> G'night.
[22:13] <bluesabre> knome: I see some conversation re base and snappy, that?
[22:13] <knome> bluesabre, -docs upload before thursday?
[22:14] <knome> bluesabre, need to land a few things before that though
[22:15] <bluesabre> knome: yes, saw that ping here, will upload wednesday
[22:15] <knome> ta
[22:18] <ochosi> humm, i'm still reviewing the delta between the mimetype folders
[22:18] <ochosi> even just reviewing that is a fair amount of work
[22:18] <knome> :)
[22:19] <ochosi> also not sure what sizes to care about the most
[22:19] <ochosi> but i guess 48px
[22:39] <ochosi> think i'll merge and do some cleanups later...
[23:33] <bluesabre> ochosi: keep me posted


[09:50] <madhu> Hi I want to port xiaomi redmi1s
[09:53] <madhu> which is the sure method to flash?
[09:53] <madhu> online build or manujally download all and flash it?
[11:57] <madhu> hello


[00:13] <madnick> ochosi: should i make an assignee list and list myself?
[00:44] <ochosi> madnick: yup
[00:52] <madnick> gah i cant seem to do it right :P
[00:53] <madnick> there we go! :P
[00:54] <knome> heh
[00:55] <knome> i must say, the ubuntu wiki is VERY confusing when you try to organize things cleanly :(((
[00:55] <knome> bbl
[00:56] <knome> see you
[00:56] <madnick> cya
[01:03] <ochosi> unfortunately true...
[01:27] <ochosi> night everyone
[01:30] <madnick> night :)
[14:53] <GridCube> ochosi: can i get a link to the ristretto git?
[15:40] <mr_pouit> GridCube: git clone git://git.xfce.org/apps/ristretto, or you can download http://archive.xfce.org/src/apps/ristretto/0.3/ristretto-0.3.0.tar.bz2 (this is almost what's in git)
[15:43] <GridCube> :) thanks
[20:26] <nikolam> I experience radeon driver bug on 10.04 LTS amd64, console spitting errors. How to report it?
[20:27] <nikolam> Hardware amd690g x1250
[20:28] <nikolam> Or maybe there is no point reporting it since its old kernel and I have no idea quite how to reproduce?
[22:23] <scott-work> i don't remember which package it is, but is there a way to make the screensaver that xubuntu uses prettier?
[22:23] <micahg> we use xscreensaver
[22:24] <scott-work> that is what i thought, but wasn't sure
[22:27] <ochosi> scott-work: you can only edit the source. in fact i was discussing that with madnick
[22:28] <micahg> there are many choices for what's available
[22:29] <ochosi> micahg: what do you mean exactly?
[22:29] <micahg> we ship many screensavers in the xscreensaver package
[22:29] <ochosi> oh, did you really mean screensaver? sry, i read "lockscreen"...
[22:30] <ochosi> dunno why, guess it's getting late for me...
[22:30] <scott-work> aye, i meant "lockscreen"
[22:30] <ochosi> hah
[22:30] <ochosi> ok, so what i said was fine then ;)
[22:31] <ochosi> scott-work: we could cooperate on that if you're interested. i would advocate a rather generic improvement anyway (nothing xubuntu-specific with logo etc)
[22:32] <scott-work> i did find a patch that allowed themeing, don't know that it was lockscreen specific or not
[22:32] <scott-work> ochosi: i would love too, but i worry about the work load already for me this cycle
[22:33] <scott-work> i imagine that our (ubuntu studio) transition to using xubuntus' theme, UI, icons, et al will fall on me as well
[22:33] <scott-work> and i have enough other tasks already
[22:33] <ochosi> i see
[22:33] <ochosi> if you need help with theme icons etc let me know
[22:33] <ochosi> i'm usually taking care of that in xubuntu
[22:33] <scott-work> ochosi:  hehe, i expect to bug you about it ;)
[22:34] <ochosi> fine :)
[22:34] <scott-work> i want to get several other work items done across a few blueprints first, which may take a couple of weeks unfortunately
[22:34] <ochosi> btw, i was in fact working with cory kontros during the last cycle on a recoloring of greybird to ubuntu-studio colors
[22:34] <scott-work> ochosi: ooooh, interesting
[22:34] <scott-work> do you have a screen shot?
[22:34] <ochosi> well, in fact i was doing the work ;) but he got seemingly less and less interested, so the project fell asleep
[22:34] <scott-work> ochosi: would you also consider doing a grey scale of the ubuntu studio cof?
[22:35] <ochosi> (and i had a lot of other stuff to do)
[22:35] <scott-work> yes, yes...cory did do that unfortunately and i it is not unexpected to hear that
[22:35] <ochosi> hm, i don't have a screenshot, the theme is in the shimmerproject-github repo though
[22:35] <ochosi> (very unfinished though)
[22:36] <ochosi> i could do a greyscale, but where do you use the cof?
[22:37] <scott-work> ochosi: i have some rough ideas for changing some of the artwork for ubuntu studio, i don't have an overwhelmingly strong vision of it however
[22:37] <scott-work> one of the things i wanted to explore is a very minimalistic dekstop wallpaper with the cof very sublty placed in the bottom right corner
[22:37] <ochosi> ok, well we can easily cooperate on those things since we're in the same boat (xfce) now ;)
[22:38] <scott-work> unobstrusive, but would be missed if not present
[22:38] <ochosi> righty, we could talk about wallpapers with knome, he's good with inkscape
[22:40] <ochosi> scott-work: btw, what panel layout are you planning on using?
[22:42] <scott-work> ochosi: i was going to talk with you about that later after i looked at it more, but i was thinking something very similar to what is being used currently
[22:42] <ochosi> ok, sure, feel free to ping me anytime
[22:43] <scott-work> i think the changes i would like are very minor, like changing perhaps postions of certain elements or the format of the clock
[22:43] <scott-work> i think these are pretty easy at this point
[22:43] <ochosi> i was mainly wondering whether you're planning to keep AWN
[22:43] <scott-work> we aren't actually using AWN currently, it was a plan to move to it and remove practically all panels
[22:43] <ochosi> oh, then i misremembered that
[22:44] <scott-work> cory was certainly working towards that, but everythign fell apart last cycle
[22:44] <ochosi> sorry to hear that
[22:44] <scott-work> but given the size and scope of the team currently, we are moderating our goals and methods
[22:44] <ochosi> yeah, just wanted to ask about the status quo of your team
[22:45] <scott-work> we certainly want to update and fix things, but we realize we will be more effective by "stealing" stuff from xubuntu to make things happen
[22:45] <ochosi> :)
[22:45] <knome> http://open.knome.fi/2011/11/09/canonical-community-collaboration/
[22:45] <ochosi> it's a good thing to borrow from each other
[22:45] <scott-work> ochosi: the ones that are most active are me, astraljava, holstein
[22:46] <scott-work> astraljava and i are pretty knowledgeable, him probably more than i
[22:46] <scott-work> holstein doesn't do packaging or bug fixes at this point, but does a hell of a lot of testing and user support
[22:46] <scott-work> we have two or three others that can be persuaded at times to help out and some have pretty amazing skills
[22:47] <knome> like knome?
[22:47]  * knome hides
[22:47] <astraljava> Nah, those garden knomes are worth jacksh*t.
[22:47] <scott-work> falktx falls into the last cateogry, i wish i could get him to 1) particpate more often and 2) do it in such a way that it will be accepted into the repository without problems
[22:48] <knome> astraljava, "watch your language" ;)
[22:48] <ochosi> scott-work: right, then you're in a similar situation as xubuntu in a way
[22:48] <scott-work> falktx is amazing and accomplishes quite impressive things with his kxstudio and now his arch project as well
[22:48] <scott-work> ochosi: hopefully we can scaffold off of each other to make something better :)
[22:49] <ochosi> yup, i'm all for that
[22:49] <ochosi> knome: that post goes to the planet i hope?
[22:49] <knome> ochosi, yes
[22:49] <ochosi> knome: then i think: awesome! is the correct commentary ;)
[22:49] <knome> ;)
[22:50] <scott-work> knome: ochosi: is there something in particular with which you would like help or collaboration?
[22:50] <scott-work> several things have been mentioned but i'm not sure how much we can contribute
[22:50] <knome> scott-work, the installation stuff is something for what we don't have an assignee yet
[22:50] <scott-work> but it would be nice to identify something that we can do
[22:51] <ochosi> yeah, maybe we could set up a wiki-page and add items over the next week/s..?
[22:51] <knome> scott-work, so if you're going to pursue that, we could "pick some of the fruits"
[22:51] <ochosi> would that work for you?
[22:51] <knome> ochosi, good idea!
[22:51] <astraljava> Well, I was interested about Xubuntu even before we started leeching off of you, but now I'm more than eager to have an efficient collaboration between our projects. Just a word from myself on the matter.
[22:51] <astraljava> interested in*
[22:52] <knome> yes. collaboration seems so natural since we are sharing so much of the same stuff, and probably ideas about how things should look too
[22:52] <ochosi> personally i think there are a few areas in which we can collaborate: obviously appearance, fixing bugs caused by canonical, and then (maybe the most interesting part) there's helping upstream and collaborating with upstream (=xfce devs)
[22:52] <scott-work> astraljava reminded me of something, most of our feedback for going to xfce has included a lot of concern about regression or loss of functionality, at some point i want to email/blog about this point and challenge people
[22:53] <ochosi> mhm
[22:53] <ochosi> good idea
[22:53] <scott-work> of course, once we get closer to the end of this cycle and ubuntu studio improves quite a bit
[22:53] <scott-work> i think most of that is lack of education, they seemd to view xfce as something ugly from the 1980's or similar
[22:53] <knome> hah, yeah...
[22:54] <scott-work> knome, ochosi: i think a wiki page would be very easy to interface with and quite acceptable
[22:54] <knome> i think we've broken the myth with xubuntu with the last five releases
[22:54] <ochosi> knome: mind to set up a wiki-page for that? i'm rather tired-ish tonight and gotta go rest very soon...
[22:54] <scott-work> knome: that may be for those who have used it lately, but it still has a stigma from people who used it years ago :(
[22:55] <knome> scott-work, probably true
[22:55] <ochosi> scott-work: btw, do you have anyone working on gtk-themes or something like that?
[22:55] <scott-work> knome:  what is the "installation stuff" that you mentioned?
[22:55] <scott-work> ochosi: not really
[22:55] <knome> scott-work, you were talking about different sets of applications for audio, gfx and stuff
[22:55] <knome> scott-work, am i correct?
[22:56] <ochosi> scott-work: ok, well if anyone approaches you feel free to forward them and we can try to work together. atm i have a *lot* of work :) (gtk3-ports of existing themes, new themes, icons etc.)
[22:56] <scott-work> knome: yes!  absolutely
[22:57] <knome> scott-work, yeah. we thought of the possibility of adding sets like "core xfce only", "maximum accessibility" ...
[22:57] <scott-work> ochosi: perhaps later in the cycle you and i can have some extensive conversations as i have wanted to learn more about themes, icons, et al and how they operate
[22:57] <ochosi> scott-work: sure
[22:57] <ochosi> oh, yes, that installer-option-stuff would be very cool
[22:58] <scott-work> knome: this is our current information about the ubiquity patch (and livedvd): https://blueprints.launchpad.net/ubuntustudio/+spec/other-p-ubuntustudio-livedvd
[22:58] <scott-work> stephane from edubuntu is the one who wrote it
[22:58] <knome> ah, i know him
[22:58] <scott-work> i was hoping to document how i changed it for ubuntu studio for others to use
[22:58] <knome> yeah
[22:58] <ochosi> stephane = stgraber?
[22:58] <knome> ochosi, yes
[22:58] <scott-work> knome: he's amazing and involved in so many things
[22:59] <scott-work> including the iso tracker website
[22:59] <knome> i met him in london when canonical showed us a preview of the new visual style
[22:59] <ochosi> yeah, true, he seems like a really nice guy from how i know him (even though only very little)
[22:59] <knome> https://wiki.ubuntu.com/Xubuntu/UbuntuStudioCollaboration
[22:59] <knome> ochosi, yes, he is a little guy :P
[22:59] <scott-work> very, very nice guy, although i struggled sometimes to understand him completely due to his heavy accent
[23:00] <knome> heh, yeah, he speaks ver french-engligh
[23:00] <knome> *english
[23:00] <ochosi> hehe, nice
[23:00] <scott-work> okay, time to go home
[23:00] <ochosi> yeah, same here
[23:00] <knome> during the first minutes after you've met him, you wonder if he is speaking french or english
[23:00] <knome> then you start spotting words
[23:00] <ochosi> :)
[23:00] <knome> and then, "OH!"
[23:01] <knome> ;)
[23:01] <knome> cody-somerville, got my email?
[23:24] <knome> somebody feel like testing the ristretto-git?
[23:25] <micahg> why bother testing the git repo?  why not test the Debian package?
[23:26] <knome> is that as current?
[23:26] <knome> whatever the method, somebody should test >0.0.93 against the bugs in LP
[23:28] <micahg> I'll throw 0.3.0 in my backports PPA if that'll speed things up, but it'll be next week before it's in precise
[23:28] <knome> we probably need to test it in oneiric
[23:28] <micahg> right, I'd backport to oneiric
[23:28] <knome> :)
[23:30] <micahg> ah, can't do a simple backport, not high enough debhelper
[23:30] <knome> heh
[23:30] <knome> or maybe somebody will just test from git
[23:31] <knome> we just want to check if the bugs reported in LP still exist
[23:31] <knome> we know they don't, but let's make sure :P
[23:33] <madnick> i downloaded it, i will compile it


[09:50] <davef> Fare ye well, I'm taking off in just over an hour.
[09:52] <zxmpi> safe flight o/
[14:47] <daftykins> zxmpi: ok let's get those jaffa cakes back on the shelves
[14:54]  * zxmpi stops rolling around in the boxes deep on the floor...
[14:55] <daftykins> :O
[15:42] <zxmpi> you haven't lived till you've jumped off diving board into a pool of jaffacakes :-D
[15:48] <daftykins> heh
[15:49] <zxmpi> doing it in gold coins is painful
[15:50] <daftykins> yeah Scrooge McDuck was definitely faking
[15:50] <daftykins> jelmer: connection woes need some attention
[15:50] <zxmpi> chocolate coins for sure
[21:35] <davef> Back in Canada. Not a single border officer checked my vaccine, PCR or ArriveCAN documents. A pointless process.
[21:35] <daftykins> noice
[21:36] <daftykins> i remember being confronted by the rows and rows of touchscreens
[21:38] <zxmpi> all bearing the fingerprints of the last 1000 people to cough on them
[21:38] <daftykins> yeah!
[21:41] <diddledani> I failed the canada border screens
[21:42] <diddledani> being blind as a bat without my glasses, and their insistence that I take em off meant I couldn't read the instructions
[21:43] <diddledani> step closer to try to focus and it gave "move away"
[21:43] <diddledani> "too close"
[21:43] <daftykins> i think i enjoyed similar!
[21:43] <daftykins> it's nuts when they say NO GLASSES PAL
[21:44] <diddledani> I failed so hard it didn't print my photo - I got it so annoyed it gave up and printed a white square where my photo should have been
[21:45] <daftykins> so you're Casper the friendly ghost, eh?
[21:45] <daftykins> "a wise guy!"
[21:45] <diddledani> yup?
[21:45] <daftykins> guess you could say you made it snap
[21:45] <daftykins> :o
[22:03] <davef> I have Nexus, so I get fast tracked through that.
[22:03] <daftykins> ah yeah i recall seeing that word lurking about
[22:54] <davef> About to take off again, final leg to Montreal.
[23:01] <daftykins> up, up and away!
[23:01] <daftykins> how empty are the flights?
[23:05] <zxmpi> safe flight o/