[00:27] <xnox> Why has the https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1241539 not been released to trusty yet?
[00:27] <xnox> (all linked branches)
[00:28] <xnox> I need those fixes in the distro for the desktop installer (touch unrelated), shall I cherry-pick indicator-profile configs and upload into the archive?
[00:29] <Mirv> xnox: I believe we're still in manual mode, ie. you need to add to the Landing Asks page
[00:30] <Mirv> plus a lot of stuff was blocked by Mir transition which has now been just released (in proposed)
[00:30] <xnox> ogra_: didrocks: please release indicators, including changes introduced by merge proposals linked on the bug 1241539.
[00:30] <xnox> Mirv: I see, thanks for the head's up.
[00:31] <xnox> ogra_: didrocks: and / or schedule it on the landing as appropriate. I care about my changes =) which in that bug are non-touch.
[00:46] <didrocks> xnox: it's getting landing starting tomorrow
[00:47] <didrocks> xnox: we needed to unscrew mir
[00:47] <didrocks> which is the case now
[00:51] <Mirv> didrocks: should we suggest landing indicators to sil2100 now that mir is resolved?
[00:56] <didrocks> Mirv: right, now that discussion is over, I'm trying to put that on the landing ask
[01:04] <Mirv> mir "INARCHIVE" \o/
[01:07] <xnox> cihelp
[01:08] <cjohnston> xnox: ?
[01:09] <xnox> cjohnston: i thought some magic will happen and a bot will talk to me. Apperantely there is indicators-sound landing ask required to be filed (to land my change) and i'm not sure where/how to do that.
[01:09] <cjohnston> xnox: there was an email sent about it
[01:10] <xnox> cjohnston: the very old one - talk to your techlead and/or manager? both of them are sprinting in 7h timezone difference.
[01:11] <xnox> " 3. CI/trunk components:
[01:11] <xnox>      - continue to use Landing Asks sheet for the time being"
[01:11] <Mirv> xnox: the page to add to is https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0Au6idq7TkpUUdGNWb0tTVmJLVzFZd0doV3dVOGpWemc#gid=1
[01:11] <cjohnston> AIUI they are still the only ones with commit access
[01:11] <cjohnston> s/commit/edit
[01:12] <cjohnston> xnox: but a large portion of the landing team is in Oakland right now too
[01:12] <cjohnston> or atleast a decent
[01:12] <xnox> cjohnston: i am a core dev working on ubiquity in my spare time (non-company time) and there is a savere regression in saucy installer of not showing any indicators, which is now fixed.
[01:13] <xnox> cjohnston: when the rest of indicators are landing from https://launchpad.net/bugs/1241539 they should land with changes across the board from that bug (all are tested & merged into trunk)
[01:13] <xnox> Affects	Status	Importance	Assigned to	Milestone
[01:13] <xnox> 	 indicator-bluetooth (Ubuntu) Remove
[01:13] <xnox> Triaged
[01:13] <xnox> High
[01:14] <xnox>   Dmitrijs Ledkovs  Edit
[01:14] <xnox> Target to milestone
[01:14] <xnox> 	 indicator-keyboard (Ubuntu) Remove
[01:14] <xnox> Triaged
[01:14] <xnox> High
[01:14] <xnox>   Dmitrijs Ledkovs  Edit
[01:14] <xnox> Target to milestone
[01:14] <xnox> 	 indicator-session (Ubuntu) Remove
[01:14] <xnox> Triaged
[01:14] <xnox> High
[01:14] <xnox>   Dmitrijs Ledkovs  Edit
[01:14] <xnox> Target to milestone
[01:14] <xnox> 	 indicator-sound (Ubuntu) Remove
[01:15] <xnox> cjohnston: is there an email queue for landing ask at all?
[01:15] <cjohnston> xnox: not to my knowledge
[01:15] <xnox> note that i'm not the team/"owner" of the said components i need to get released to unbreak installer. *sigh*
[01:16]  * xnox will go and upload something into debian.
[01:18] <cjohnston> xnox: sorry I don't have anything better to tell you. I'm not very familiar with the process to know if there is anything else you could do
[01:19] <xnox> cjohnston: ok. thanks alot. I've requested it via my tech lead. And added reminder to check upon it in couple of weeks.
[01:20] <cjohnston> thanks xnox
[01:33] <cjwatson> xnox's request is landing ask #216 now
[09:14] <ogra_> sil2100, where do we stand with unity8, mir and friends ? should i trigger a new image ?
[09:17] <sil2100> ogra_: hi! You didn't get any message from Didier?
[09:18] <sil2100> ogra_: from what he e-mailed me, it seems that mir + unity8 is tested and works, I have some landing asks TODO but these already use the new mir and unity8
[09:21]  * ogra_ didnt see any message
[09:21] <ogra_> so you mean i should wait til your stuff has landed ?
[09:21] <sil2100> ogra_: no no, I guess we can spin a new image with the new mir + unity8 I guess
[09:21] <ogra_> awesome, going to then ...
[09:21] <sil2100> ogra_: btw. what image are we on now?
[09:22] <sil2100> Since my stuff is targetted for image 7
[09:22] <ogra_> proposed is on 6, trusty is on 5
[09:22] <ogra_> ah, the next build would be 7 ... so re-target to 8
[09:22] <sil2100> ACK ;)
[09:23] <ogra_> [10:22] <vila> ogra_: I used the 'adb shell system-image-cli -c trusty -b 0 -b' to switch channels. I had to resest clock from epoch to make it work but it's good now.
[10:22] <ogra_> why the second -b ?
[10:23] <vila> ogra_: it's my french accent, read it as -v ;)
[10:23] <ogra_> haha
[10:23] <vila> ogra_: yet, I want #6 or even #7, should I redo that with s/trusty/trusty-proposed/' ? (yeah, yeah, s/-b$/-v/ too ;)
[10:24] <ogra_> if you want to be on proposed, yes, do that
[10:24] <vila> ogra_: ok, I'll stick to OTA from there
[10:24] <vila> ogra_: and thanks !
[10:24] <ogra_> np :)
[11:00]  * psivaa is seeing 'ERROR:phablet-flash:Installation is taking too long or an error occured along the way.' when flashing with image 7
[11:00] <psivaa> ogra_: ^
[11:01] <psivaa> installing one locally to confirm
[11:07] <ogra_> psivaa, check if there are any crash files ... if apport kicks in on first boot it might time out before it finished
[11:17] <psivaa> ogra_: i can't connect to the devices that failed in this way.. probably a consequence of the bad flash
[11:17] <ogra_> hmm, yeah
[11:18] <ogra_> what device is that ?
[11:18] <ogra_> mko or maguro
[11:18] <ogra_> *mako
[11:18] <psivaa> both
[11:18] <ogra_> oh
[11:19] <psivaa> yea, there are 5 devices now i could not connect in the lab
[11:20] <psivaa> all had attempted to install image 7
[11:20] <psivaa> mixture of mako and maguro
[11:20] <ogra_> well, image 7 isnt existent yet
[11:21] <ogra_> hmm, unless my terminal lies
[11:21] <ogra_> (teh build command didnt return yet in the terminal i started it in)
[11:21] <ogra_> bah
[11:21] <ogra_> you are right, 7 is there
[11:21]  * ogra_ tries an OTA upgrade on maguro
[11:26] <ogra_> there was an adbd update from xnox, but i think plars tested that
[11:28] <ogra_> ok, UI is up here ... no adb
[11:28] <ogra_> xnox, !!
[11:28] <ogra_> no mtp either
[11:28] <ogra_> hmm
[11:29]  * ogra_ wonders if this is a subjective feeling or if maguro really got faster
[11:32] <ogra_> bah and now unity crashed
[11:33] <ogra_> and this time maliit ... hard to get any logs in the terminal-app if everything crashes all the time
[11:36] <ogra_> sigh
[11:36] <ogra_> so adbd doesnt start and maliit crashes after thre chars in the terminal-app
[11:37] <sil2100> popey: hi!
[11:37] <sil2100> popey: are you around?
[11:47] <sil2100> ogra_: do you have a moment for a packaging diff ACK?
[11:48] <sil2100> ogra_: https://jenkins.qa.ubuntu.com/view/cu2d/view/Head/view/Indicators/job/cu2d-indicators-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_indicator-sound_12.10.2+14.04.20131029.1-0ubuntu1.diff
[11:50] <xnox> sil2100: looks good to me.
[11:51] <sil2100> xnox: awesomage, thanks!
[11:52] <ogra_> what xnox said
[11:53] <ogra_> xnox, so image 7 doesnt start adb ... nor does it start mtp ...
[11:54] <xnox> ogra_: i'm upgrading grouper to image 7 at the moment.
[11:54] <ogra_> k
[11:54]  * ogra_ tries to grab logs via recovery
[11:55] <ogra_> android-tools-adbd stop/pre-start, process 2027
[11:55] <ogra_> thats what i see in the upstart log
[11:56] <ogra_> so it seems to hang in pre-start
[11:57]  * ogra_ wishes it would be easier to access the ro image from recovery :(
[11:57] <ogra_> xnox, !
[11:58] <ogra_> typo
[11:58] <ogra_> pre-start script
[11:58] <ogra_> 	if [ -d /sys/class/android_usb ]
[11:58] <ogra_> 	then
[11:58] <ogra_> missing semicolon
[12:03] <ogra_> hmm, definitely not enough
[12:04] <xnox> hm? is /sys/class/android_usb present ?
[12:04] <ogra_> no idea
[12:04] <ogra_> i have no chance to get in at all
[12:04] <ogra_> cant start ssh because the kbd dies
[12:05] <xnox> ogra_: right so from terminal.app "sudo adbd" does get me adbd
[12:05] <ogra_> i cant type that
[12:06] <ogra_> dies after three chars for me
[12:06] <ogra_> but it looks like you completely reversed the logic for the pre-start script
[12:06] <xnox> ogra_: true and the qemu grep is killing it.
[12:07] <ogra_> why did that work during testing ?
[12:07] <xnox> grep qemu /proc/cmdline is killing it.
[12:07] <xnox> let me reboot and make the image writable
[12:08] <ogra_> phew, i'm in via ssh
[12:10] <sil2100> Ok guys, I go for lunch and changing locations, be back in ~2h
[12:11] <xnox> ogra_: testing http://paste.ubuntu.com/6323631/
[12:11] <ogra_> root@ubuntu-phablet:~# grep -q qemu /proc/cmdline || echo foo
[12:11] <ogra_> foo
[12:11] <ogra_> ah, yeah, that might work
[12:13] <ogra_> xnox, works
[12:13] <ogra_> though i wonder why you also broke mtp
[12:13] <ogra_> seems that died alongside
[12:14]  * ogra_ reboots with the change added
[12:14] <ogra_> lest see
[12:14] <ogra_> probably just a coincidence
[12:15] <ogra_> xnox, what i dont get is why it worked for the testers yesterday
[12:15] <ogra_> hmm, adb still works, mtp still broken after reboot
[12:15] <ogra_> ah
[12:15] <ogra_> i spoke to soon
[12:15] <ogra_> works :)
[12:17] <xnox> ogra_: i did $ watch -d adb devices
[12:18] <xnox> ogra_: on the host & rebooted, grouper briefly appears and disappears
[12:18] <ogra_> yeah
[12:18] <ogra_> the fix is fine, please upload
[12:18] <ogra_> i'll roll a new image
[12:18] <xnox> ogra_: which is very odd, since in the past once up, it stayed up.
[12:18] <ogra_> under ubuntu ?
[12:19] <ogra_> we dont use persistent properties yet
[12:19] <ogra_> so that theoretically cant work
[12:19] <ogra_> (it used to work before we flipped the conatiner though, but teh flip broke that part )
[12:20] <ogra_> xnox, dont forget the semicolon btw :)
[12:20] <xnox> ogra_: where a semicolon, and why.
[12:20] <ogra_> (or does the linewrap suffice there ?)
[12:21] <ogra_> xnox, after the if condition, before then
[12:21] <xnox> it should be needed. I've tested the patch as it is here http://paste.ubuntu.com/6323631/
[12:21] <ogra_> ok
[12:21] <ogra_> mine had the semicolon added after ]
[12:22] <ogra_> but if the linewrap is sufficient then i'm fine
[12:27] <xnox> ogra_: how does mtp suppose to work? and why is it sometimes flacky?
[12:35] <ogra_> xnox, it works through the same gadget device
[12:36] <ogra_> xnox, by setting additional properties for the device
[12:51] <sergiusens> cjohnston, hey having a license problem with renato_ on a build here
[12:52] <cjohnston> sergiusens: I'll need more info please
[12:52] <sergiusens> cjohnston, this is the result http://paste.ubuntu.com/6323802/ if I add Collabora to the allowedlicenses in http://bazaar.launchpad.net/~private-ps-quality-team/pbuilderjenkins/trunk/view/head:/hooks/A10checklicenseheaders.in
[12:52] <sergiusens> cjohnston, but I'm not sure what the proper solution would be for the other bits
[12:52] <sergiusens> the allowedlicenses thing seems weird though; I'd imagine a list of GPL, LPGL, ...
[12:53] <sergiusens> cjohnston, this is the job btw https://code.launchpad.net/~renatofilho/address-book-service/fork-dummy/+merge/192964
[12:53] <cjohnston> sergiusens: looking
[13:04] <cjohnston> sergiusens: we are investigating and will get back to you hopefully shortly
[13:04] <sergiusens> cjohnston, get back to renato__ directly if you want; he just pinged me as I used to do this for him ;-)
[13:04] <cjohnston> ok
[13:04] <ogra_> hmm, so rmadison thinks android-tools is in ...
[13:05]  * ogra_ gives it another 10min to be 100% sure ...
[13:05] <ogra_> hmm, no sil2100 ...
[13:06] <ogra_> i'll mess up his image planning with my build :/
[13:07] <renato__> ogra_, hi, I would like to know if you have plans to update  folks and EDS packages  on "Trusty"
[13:07] <ogra_> me ?
[13:08]  * ogra_ has no plans regarding this ...arent we getting that via sync from debian ?
[13:08] <renato__> ogra_, yes bill told me to ping you :D
[13:08] <ogra_> s/sync/autosync/
[13:08] <ogra_> renato__, traditionally seb128 (or his team) maintained eds
[13:09] <ogra_> he should be online soon (at the sprint)
[13:09] <renato__> ok thanks
[13:10] <plars> ogra_, xnox: hi... so was the adbd that went into 7 different somehow from the one I tried yesterday?
[13:10] <ogra_> plars, well, not sure
[13:10] <ogra_> i havent looked inside the deb yesterday
[13:11] <ogra_> but appraently it was different. yes
[13:16] <xnox> ogra_: android-tools is in release pocket.
[13:17] <ogra_> xnox, i know
[13:17] <ogra_> it is since a while
[13:17] <ogra_> xnox, prob is that sil2100 is gone
[13:17] <xnox> ok =) sorry.
[13:17] <xnox> ogra_: ah, fair enough.
[13:17] <ogra_> and he has pending stuff according to the spreadsheet
[13:17] <ogra_> waiting for him to return from lunch
[13:19] <cjwatson> You don't need to wait once rmadison says it's in
[13:19] <cjwatson> It's definitely fine for image building then
[13:19] <ogra_> looking at the sheet it seems only the hud fixes didnt get in yet
[13:19] <ogra_> cjwatson, k
[13:19]  * ogra_ thinks we can afford one more build later this evening and just kicks off image #8 now
[13:28] <ogra_> popey, do you know if we will revisit the app categories  at some point ? the options the store offers are really odd imho
[13:29] <popey> i hope so, but that's more bueno's dept
[13:40] <xnox> popey: ogra_: it feels like at the moment it's offering categories as as for .debs / from debian policy. (so copy&paste from the non-click app store)
[13:41]  * xnox ... maybe not policy, but wherever debian lists all possible categories.
[13:43] <ogra_> yeah
[14:02] <dobey> fginther: https://bugs.launchpad.net/jenkins-launchpad-plugin/+bug/1214970 <- this is "fix released" now right?
[14:06] <fginther> dobey, yes, that's been fixed
[14:06] <fginther> was a configuration issue, not an actually code change
[14:09] <dobey> right
[14:11] <dobey> i'm doing some work to get tarmac back up to par, for where we need it to be
[14:24] <ogra_> [14:24] <ogra_> psivaa, plars ^^^ that one should work again
[14:25] <plars> ogra_: you rock!
[14:25] <plars> rfowler_: are the devices back up?
[14:25]  * ogra_ upgrades
[14:31] <ogra_> ogra@chromebook:~$ adb shell
[14:31] <ogra_> root@ubuntu-phablet:/#
[14:31] <ogra_> looks good
[14:31] <ogra_> xnox, ^^^
[14:32]  * popey updates to 8
[14:53] <didrocks> hey sil2100, how are you?
[14:54] <didrocks> hey ogra_!
[14:54] <ogra_> sil2100, we had an issue with image 7 ... we fixed it and rolled #8 a bit earlier
[14:54] <didrocks> ogra_: ah nice, you kicked an image!
[14:54] <didrocks> (that was my question)
[14:54] <ogra_> sil2100, i updated the spreadsheet for your stuff
[14:54] <didrocks> what was wrong with image 7?
[14:54] <ogra_> didrocks, adbd didnt start
[14:55] <didrocks> ah, not nice!
[14:55] <ogra_> issue with the upstart job
[14:55] <didrocks> mir was in image 7 as well?
[14:55] <ogra_> it was tested by two people ...
[14:55] <ogra_> yeah
[14:55] <didrocks> ok…
[14:55] <ogra_> new mir and unity8
[14:55] <didrocks> excellent!
[14:55] <ogra_> not sure how the tests did succeed though
[14:55] <didrocks> thanks ogra_, /me won 10 minutes :)
[14:55] <didrocks> ogra_: tests succeed?
[14:55] <ogra_> (for the broken adbd)
[14:55] <didrocks> I see no result on the dashboard
[14:56] <didrocks> ah
[14:56] <didrocks> yeah, this was landing ask #?
[14:56] <ogra_> yeah, #7 didnt start ... no adb :)
[14:56] <ogra_> and #8 is there since 20min only
[14:56] <sil2100> Hello!
[14:56] <didrocks> ogra_: I mean, I don't see the adb upload
[14:56] <didrocks> hey sil2100 ;)
[14:56] <sil2100> ogra_: ok, thanks :)
[14:56] <didrocks> ogra_: in the landing plan
[14:56] <ogra_> didrocks, oh, that was xnox , i think we might have missed adding it
[14:57] <ogra_> but he asked popey and plars for testing ... sorry, i should have taken care of the spreadsheet
[14:57] <fginther> plars, rfowler_, any issues getting our devices restarted to flash to image 8?
[14:57] <ogra_> (but it was late last evening and i forgot)
[14:57] <plars> fginther: it looks like they are still not up, for image testing at least
[14:58] <ogra_> hmm
[14:58] <didrocks> ogra_: no worry, thanks for tracking that to the end
[14:58] <ogra_> so Mir on maguro is *a lt* snappier after reboot
[14:58] <didrocks> sil2100: how is the landing going? Seems well from what I see
[14:58] <didrocks> ogra_: yeah, there is still some mem leaks
[14:58] <ogra_> but gets really awful after starting a few apps
[14:58] <didrocks> (visible on mako as well)
[14:58] <ogra_> like, worse than before imho
[14:58] <didrocks> oh really?
[14:58] <didrocks> possible, quite a bunch of code entered
[14:58] <ogra_> its lots and lots better after a fresh boot
[14:59] <popey> yeah, feels quite sluggish
[14:59] <sil2100> didrocks: rather well, I also tested indicator-datetime, no regressions with AP unity8 but I'm not sure how the fix is supposed to work
[14:59] <ogra_> nearly as smooth as mako
[14:59] <popey>  3386 phablet   20   0  284180  53304  37700 S  99.3  2.8   0:37.20 camera-app
[14:59] <sil2100> didrocks: I set up an alarm and didn't see any indication of it alarming
[14:59] <ogra_> but as soon as i have a few apps open it crawls
[15:01] <didrocks> sil2100: argh, checkig with upstream as well?
[15:01] <ogra_> didrocks, since youre at it, can you add robru's seed change to the plan too ?
[15:01] <didrocks> sil2100: basically, instead of having the day, you should have a generic message
[15:01] <ogra_> so we finally get that off the plate
[15:02] <didrocks> ogra_: well, I want that backward compatibility to be discussed properly here before we take a decision
[15:02] <didrocks> ogra_: I try to have that happens, it's hard for them to see that blocking us :p
[15:02] <ogra_> at the sprint you mean ?
[15:02] <didrocks> yep
[15:02] <ogra_> yeah, we need a defined process how to change the API
[15:02] <ogra_> but that one is actually safe
[15:02] <ogra_> 3D directional audio is definitely not used by any app yet :)
[15:03] <didrocks> right, but imagine someone start developping today
[15:03] <didrocks> basing on our sdk 1
[15:03] <xnox> sil2100: i open indicator, and it says "... Battery, Sound, Tuesday, Network, ..." which is plain odd =)
[15:03] <plars> fginther: haven't heard back yet, but it looks like the devices on the image testing side are up now at least. Just started the tests
[15:03] <xnox> (that's with old image)
[15:03] <didrocks> they will have a surprise :)
[15:03] <plars> ogra_: ^
[15:03] <plars> fginther: can you check yours?
[15:03] <ogra_> plars, great
[15:03] <popey> ogra_: didrocks #8 seems to have broken the music app?
[15:04] <popey> I get a white screen on mako
[15:04] <ogra_> popey, oh ?
[15:04] <sil2100> xnox: ah, this is ok
[15:04] <sil2100> didrocks:  ^
[15:04] <ogra_> popey, works on my maguro
[15:04] <popey> hmm
[15:04] <ogra_> (well, i have no music on it ... )
[15:04] <sil2100> didrocks: I mean, the Tuesday -> now it's Upcoming
[15:05] <fginther> plars, all are still off-line. I'll follow up with rfowler_ in case he's not aware they need attention
[15:05] <sil2100> didrocks: but there was also a mention about the alerts being fixed
[15:05] <ogra_> popey, "please import music and restart the app" ... on mako as well
[15:05] <popey> ogra_: for me it started the first time after a reboot, showed some music and then fell over
[15:05] <popey> ah, add some music
[15:06] <sil2100> didrocks: I'm waiting for upstream to comment
[15:06] <didrocks> sil2100: oh that one, yeah
[15:06] <ogra_> so its more the scanning than the app
[15:06] <didrocks> sil2100: sounds good, put it in red
[15:06] <popey> dunno
[15:06] <sil2100> didrocks: in the meantime, I check the hud maybe
[15:06] <popey> scanning is separate
[15:06] <popey> it could be something inside the app reading from mediascanner
[15:06] <ogra_> yeah, that shouldnt cause a white sceeen
[15:06]  * popey reboots and tries again
[15:07] <popey> #5 is fine
[15:07] <didrocks> sil2100: yeah, sounds good!
[15:08] <ogra_> popey, musci app is native C++ right ?
[15:09] <popey> nope
[15:09] <popey> qml + plugin
[15:09] <ogra_> k
[15:10] <ogra_> popey, coudl you check #6 ?
[15:10] <popey> /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene: unrecognized option '--file='
[15:10] <popey> /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene: invalid option -- 'I'
[15:10] <popey> QUbuntu: Could not create application instance
[15:10] <ogra_> http://people.canonical.com/~ogra/touch-image-stats/20131025.changes
[15:10] <popey> http://paste.ubuntu.com/6324436/
[15:10] <ogra_> i see mediascanner was updated in #6
[15:11] <popey> yeah
[15:11] <popey> ok, will test #6
[15:12] <popey> phablet-flash ubuntu-system -d mako --revision 6
[15:12] <popey> ?
[15:12] <ogra_> -b  6
[15:12] <ogra_> oh
[15:12] <ogra_> phablet-flash
[15:12] <ogra_> yeah
[15:13] <popey> ah, needed channel too
[15:13]  * ogra_ is so focused on system-image-cli nowadays
[15:13] <popey> INFO:phablet-flash:Flashing revision 6 from channel trusty-proposed
[15:13] <popey> yay
[15:13] <popey> i like that it tells me now
[15:13] <ogra_> :)
[15:13] <popey> shame it whizzes past so fast
[15:14] <ogra_> WOAh
[15:14] <ogra_> system-settings just crashed in my face
[15:15] <ogra_> and doesnt start anymore now
[15:16] <ogra_> and again
[15:20] <popey> ogra_: music app works in #6
[15:20] <ogra_> popey, can you try if system-settings behaves for you ?
[15:20] <popey> on #6?
[15:20] <ogra_> it just vanishes for me after clicking around in it a bit
[15:20] <ogra_> on 8
[15:21]  * ogra_ wonders if anyone actually checked the impact of the boots transition for out toolkit
[15:21] <ogra_> *boost
[15:21] <ogra_> *our
[15:21] <popey> i have visited every pane in system settings on #6
[15:21] <popey> no problems
[15:23] <ogra_> hmm, doesnt for me anymore either
[15:23] <ogra_> but i'm at the tenth try or so
[15:25] <ogra_> oh
[15:25] <ogra_> and now the G+ app crashed
[15:32] <ogra_> wow
[15:32] <ogra_> apps are super crashy on #8
[15:33] <ogra_> didrocks, do you know if anyone from the SDK team asessed the impact of the boost transition on our stuff ?
[15:34] <ogra_> haha
[15:34] <sergiusens> ogra_, how does the whole landing ask work for the android tree?
[15:34]  * ogra_ just tried to start the ubuntu desktop tour on the ubuntu website in the browser
[15:34] <cjwatson> Didn't the boost transition predate the previous good image?
[15:35] <sergiusens> ogra_, can I just push stuff to the repo?
[15:35] <cjwatson> Please could you find out whether it's actually related before implicating it
[15:35] <ogra_> cjwatson, oh, right, it was all boost updates, not the transition itself
[15:35] <ogra_> http://people.canonical.com/~ogra/touch-image-stats/20131029.1.changes
[15:35] <cjwatson> There's a boost change in this image, but it's not the transition, indeed
[15:36] <ogra_> ah, no
[15:36] <ogra_> http://people.canonical.com/~ogra/touch-image-stats/20131029.changes
[15:36] <ogra_> its also bumping from 1.53 to 1.54
[15:36] <cjwatson> Wasn't #7 good?
[15:36] <ogra_> (image 7 was broken)
[15:36] <ogra_> no, adb was messed up
[15:36] <ogra_> so the tests couldnt run
[15:37] <cjwatson> Oh.  Well, please still find out whether it's related before we go trying to unwind a complxe transition
[15:37] <cjwatson> *complex
[15:37] <ogra_> cjwatson, i only wanted to know if someone from the SDK team actually checked the potential sisk for us
[15:37] <ogra_> *risk
[15:37]  * ogra_ didnt mean to point fingers or anything
[15:38] <cjwatson> That looks like only a small part of the boost transition - most of it was already done
[15:39] <cjwatson> I think that was just lucene++?
[15:39] <thomi> sil2100: hey man, I wonder if you could comment on this please? https://bugs.launchpad.net/autopilot/+bug/1244089
[15:39] <ogra_> cjwatson, yeah, my path of thought wa more going towards if we potentially need to rebuild any native apps
[15:40] <ogra_> or if thats covered on the Qt level for us
[15:40] <cjwatson> There's more in http://people.canonical.com/~j-lallement/touch/changes/20131025.html, but there's also quite a lot else
[15:40] <cjwatson> (that was #6 - looks like the last promoted image was #5?)
[15:40] <ogra_> 25 was image 6
[15:41] <ogra_> i ran that fro a few days without issues
[15:41] <cjwatson> OK
[15:41] <ogra_> the breakage came between 6 and 8
[15:42] <sergiusens> xnox, do you know what the process is for committing/pushing to the android repo these days?
[15:43]  * ogra_ thought that process was called rsalveti
[15:43] <sergiusens> ogra_, I have push rights; just want to know how it plays with the landing asks and all that
[15:43] <rsalveti> sergiusens: you need to push, wait for the tarball to be out, and upload
[15:44] <rsalveti> sergiusens: the tarball is done at every hour
[15:44] <ogra_> sergiusens, ah
[15:44] <rsalveti> but you need to sync with the landing team
[15:44] <sergiusens> rsalveti, ok, I just want to push the revert for mtp
[15:44] <rsalveti> sergiusens: or just ask either me or xnox to sponsor it
[15:44] <cjwatson> ogra_: FWIW I just unpacked everything from http://people.canonical.com/~ubuntu-archive/click_packages/click_list and none of those have any direct linkage to boost
[15:44] <rsalveti> sergiusens: which patches?
[15:44] <ogra_> sergiusens, you need to mount / rw and replace the android img file i think ... to test it
[15:45] <cjwatson> ogra_: I would have expected direct linkage to boost from apps to be strictly forbidden - the SDK team doesn't like that kind of thing :)
[15:45] <ogra_> inside the ubuntu-system.imd
[15:45] <sergiusens> rsalveti, http://people.canonical.com/~sergiusens/mtp/0001-Revert-Disabling-mtp-for-manta.patch
[15:45] <sergiusens> rsalveti, remember :-)
[15:45] <ogra_> cjwatson, well, system-settings is native iirc
[15:45] <ogra_> cjwatson, as well as the browser
[15:45] <rsalveti> sergiusens: yeah, I can check it now :-)
[15:45] <rsalveti> got the new laptop in place
[15:45] <sergiusens> ogra_, I know how to test; I have my changes locally
[15:45] <ogra_> cjwatson, i meant less the click packages ...
[15:46] <rsalveti> sergiusens: will review your other mrs today as well
[15:46] <cjwatson> ogra_: It neither directly build-depends nor depends on boost
[15:46] <sergiusens> ogra_, I just need to know what the bureaucratic part is
[15:46] <ogra_> cjwatson, k
[15:46] <cjwatson> ogra_: Likewise webbrowser-app
[15:46] <ogra_> sergiusens, landing ask ... have someone from the team move it to landing plan ...
[15:46] <cjwatson> ogra_: So I suppose it's *possible* something obscure there is going on but it doesn't seem like the highest-probability cause ...
[15:47] <ogra_> cjwatson, yeah ... Mir and unity depend on it, if there is breakage its more likely in them, thanks for checking the apps !
[15:49] <ogra_> hmm
[15:49] <ogra_> gallery-app looks really bad on the dashboard
[15:50] <ogra_> 50% fail rate
[15:50] <xnox> cjwatson: can you grep for dlopen? =)
[15:53] <ogra_> funny, locally it is actually rock solid
[15:53] <cjwatson> xnox: no matches
[15:54] <sil2100> thomi: sure, give me a moment ;)
[16:10] <plars> ogra_: yeah, on mako and maguro too
[16:11] <ogra_> right
[16:11] <sergiusens> ogra_, are you not on canonical irc for a reason?
[16:11] <ogra_> sergiusens, erm, no reason except not noticing that i dropped
[16:29] <thomi> sil2100: I assigned you to the bug, and marked it as incomplete. Feel free to change the status once that information is added. Thanks!
[16:29] <sil2100> thomi: sure! Thanks, will test the branch whenever it's possible
[16:45] <thomi> ok, I figured there was an automated system for that
[16:45] <thomi> thanks for your help
[16:48] <sil2100> Mirv: tested HUD, publishing if all is ok in cu2d
[16:56] <Mirv> sil2100: cool, and morning!
[16:57] <Mirv> cyphermox: could you pre-ack packaging change http://<IP_ADDRESS>:8080/view/cu2d/view/Head/view/Phone/job/cu2d-phone-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_dialer-app_0.1+14.04.20131029.1-0ubuntu1.diff ?
[16:57] <Mirv> sil2100: so you got unity8 AP also working?
[16:58] <cyphermox> hrm, sure...
[16:58] <sil2100> Mirv: yes \o/
[16:59] <sil2100> Mirv: some tests are failing, but re-runs help
[16:59] <ogra_> plars, given the crashyness of apps, i dont think it is worth to give back anything on image 8
[16:59] <sil2100> Mirv: those seem like problems with introspecting unity8 in overall sometimes
[16:59] <plars> ogra_: agree, tests are still running so if there's anything you're curious about we can do retries in a bit, but I don't think it looks good
[16:59] <Mirv> sil2100: yeah being able to run unity8 tests now with the new Mir with just one command is great
[16:59] <sil2100> Mirv: btw. we have a lot of failures for one machine for HUD - you think it's still ok to publish? Other platform is better, below threshold
[17:00] <ogra_> plars, yeah, its not woth it, we need a fix for Mir first
[17:00] <Mirv> sil2100: I don't know, better do some validating of those?
[17:01] <cyphermox> Mirv: all good for dialer-app
[17:01] <cyphermox> I'd be a bit wary of running that on a "live" phone though :)
[17:01] <Mirv> sil2100: have you looked that there are _1400_ autopilot errors in unity stack?
[17:01] <cyphermox> Mirv: the autopilot tests themselves scare me ;)
[17:02] <Mirv> yeah I wouldn't suggest running the autopilot tests with SIM card..
[17:03] <slangasek> ci help
[17:03] <thomi> slangasek: :)
[17:03] <cjohnston> doanac: ^
[17:04] <cjohnston> slangasek: no space between the two... but if there is a vanguard, they are even better :-)
[17:04] <slangasek> oh
[17:04] <slangasek> cihelp?
[17:04] <doanac> slangasek: works. what's up?
[17:04] <cjohnston> slangasek: that's the one
[17:04] <slangasek> doanac: hi :)  Just testing the system that ev is briefing us all on :-)
[17:04] <Mirv> ticket resolved :)
[17:05] <doanac> slangasek: also a tip: the channel topic includes some information about who's vanguard and what critical issues are known
[17:05] <sil2100> Mirv: I vaildated that those are not regressions if anything, still wondering why those fail
[17:05] <sil2100> Mirv: oh, didn't look at unity stack ;p
[17:05] <sil2100> 1400?!
[17:05] <sil2100> :O
[17:05] <Mirv> sil2100: maybe related to the unity stack problem...
[17:05] <cjohnston> slangasek: tell ev to explain to ping the vanguard if there is one instead of cihe*lp please :-)
[17:05] <sil2100> Mirv: :O
[17:06] <slangasek> doanac: ack - but ev didn't tell us to look at the topic, he just said to type 'ci help' ;)
[17:06] <doanac> slangasek: makes sense. we should update our alert patterns to catch that also
[17:06] <slangasek> too late, the moment has passed, we'll have to clarify this by email later ;)
[17:06] <doanac> :)
[17:06] <Mirv> sil2100: yeah, slight problems, looks like dbus also with autopilot 1.3? (you e-mailed about autopilot 1.4)
[17:06] <Mirv> doanac: maybe support also "ci help", "CI Help!" and so on :)
[17:07] <cjohnston> Mirv: there is a reason it's what it is. :-)
[17:07] <cjohnston> not all clients support things like spaces
[17:07] <Mirv> right
[17:15] <sil2100> didrocks: ACK please! http://<IP_ADDRESS>:8080/view/cu2d/view/Head/view/HUD/job/cu2d-hud-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_hud_13.10.1+14.04.20131029.1-0ubuntu1.diff
[17:16] <didrocks> sil2100: +1 of course
[17:16] <sil2100> \o/
[17:16] <didrocks> thanks dude!
[17:16] <ogra_> didrocks, bug 1245958
[17:17] <ogra_> FYI
[17:17] <ogra_> didrocks, no way to promote that one
[17:17] <didrocks> ogra_: argh, Mirv can you handle that? ^
[17:18] <ogra_> didrocks, kdub and alan_g discuss it in -touch atm
[17:19] <ogra_> but i wont be around late today so wont be able to drive that
[17:19] <Mirv> didrocks: ok, I'll at least poll on them to get the news on a fix
[17:20] <didrocks> ogra_: ah nice!
[17:20] <didrocks> thanks :)
[17:21] <Mirv> I do have some crash files in /var/crash for apps too, although from user perspective one doesn't see that much it seems
[17:22] <didrocks> ok
[17:22] <Mirv> marked the bug as critical as it prevents image promoting
[17:30] <ogra_> sergiusens, added landing #288 to the landing plan for you
[17:35] <sergiusens> ogra_, thanks
[17:38] <popey> oooh Mirv https://codereview.qt-project.org/#change,69368 via https://bugreports.qt-project.org/browse/QTBUG-32225
[17:42] <kenvandine> Mirv, sil2100: i've added a reference to the bug report for Mir causing lots of app crashes in image 8 to the old unity team work spreadsheet, so we prevent to much duplicate work
[17:44] <Mirv> popey: \o/ for progress
[17:44] <Mirv> kenvandine: thanks
[17:44] <Mirv> vila: can you glance at http://<IP_ADDRESS>:8080/job/autopilot-trusty-daily_release/216/ - all AP tests failing because of a dbus problem?
[17:47] <vila> Mirv: EOD, doanac ? ^
[17:47] <doanac> looking
[17:47] <doanac> seems limited to unity8?
[17:48] <vila> doanac: thanks
[17:56] <Mirv> doanac: unity7, not unity8
[17:56] <doanac> Mirv: sorry those keys are too close together
[17:56] <Mirv> doanac: I noticed upgrading to that trunk unity install xpathselect 1.4, maybe it's related?
[17:58] <Mirv> doanac: I also saw an e-mail from Chris Lee related to problemws with Autopilot 1.4 (but we use 1.3 in the PPA) about that Unity7 "hasn't been updated to use thenewer 1.4 DBus wire protocol (Unity7 a unique beast in that the functionality that isusually provided by libautopilot-qt/gtk is part of the Unity7 source tree.)" - it says dbus but does that mean xpathselect instead?
[17:58] <doanac> Mirv: possibly. i was worried some of those DBUS errors seemed unrelated. but that seems feasible.
[17:59] <Mirv> ah right
[17:59] <Mirv> https://code.launchpad.net/~3v1n0/unity/xpathselect-1.4 - so maybe this?
[18:01] <Mirv> I filed bug #1245988 now, updates welcome
[18:01] <doanac> Mirv: both 1.3 and 1.4 are getting installed for xpath
[18:02] <Mirv> doanac: the new unity-autopilot only depends on libxpathselect1.4
[18:02] <fginther> doanac, Mirv, i think that's the culprit. unity is speaking 1.4, autopilot is listening to 1.3
[18:04] <thomi> hi guys
[18:05] <fginther> thomi, o/
[18:05] <thomi> so, Marco and I were looking at those branches yesterday - I didn't think he'd merged them yet though
[18:05]  * thomi pulls unity
[18:05] <Mirv> it seems https://code.launchpad.net/~townsend/unity/fix-lp1243529/+merge/192381 got merged
[18:05] <fginther> thomi, it's been merged
[18:05] <thomi> oh
[18:05] <thomi> well
[18:05] <thomi> this is the problem we face - landing autopilot 1.4 and *all* the test suites at the same time takes som serious coordination :)
[18:05] <Mirv> so is this a chicken and egg problem with moving to autopilot 1.4?
[18:06] <thomi> right - either we land AP 1.4 and fix the tests later, or we try and do everything at the same time
[18:07] <thomi> We were trying to do everything at once, but I guess I should have been clearer with Marco
[18:07] <thomi> so I guess the options are either to revert the unity7 change, or go ahead and land AP. I know which one I'd rather do, but I'll leave that to you guys :)
[18:08] <fginther> I vote for reverting the unity7 change
[18:08] <thomi> ಠ_ಠ
[18:10] <doanac> i'm pretty sure asac would prefer to revert
[18:10] <fginther> of course now I see the bug that was addressed: https://bugs.launchpad.net/unity/+bug/1243529
[18:11] <fginther> appears that unity7 fails to build with xpathselect 1.3?
[18:12] <thomi> fginther: should build fine once marcos branch is reverted
[18:13] <thomi> I mean, it used to build against 1.3, marco merged code to build it against 1.4
[18:14] <fginther> thomi, ok, I see that 1.4 isn't in trusty anymore
[18:14] <fginther> hang on
[18:15] <doanac> so are there 2 changes that would need reverting:  https://code.launchpad.net/~townsend/unity/fix-lp1243529/+merge/192381 and http://bazaar.launchpad.net/~unity-team/unity/trunk/revision/3581 ?
[18:15] <fginther> thomi, ah. libxpathselect 1.4 is still in the daily-build ppa
[18:16] <fginther> that's causing unity7 not to build (https://launchpadlibrarian.net/154760401/buildlog_ubuntu-trusty-amd64.unity_7.1.2%2B14.04.20131023-0ubuntu1_FAILEDTOBUILD.txt.gz), hence the bump
[18:19] <thomi> fginther: I see.
[18:21] <thomi> fginther: I'm not really sure what makes it land in the PPA
[18:21] <thomi> I guess it's some cu2d config?
[18:21]  * thomi shrugs
[18:22] <fginther> thomi, yes. whoever added the autopilot 1.3-trusty branches probably didn't realize that xpathselect was a dependency
[18:23] <thomi> :(
[18:23] <thomi> We never expected 1.3 to land in trusty. I guess the config was written assuming 1.4 would get released there
[18:24] <fginther> thomi, most likely
[18:30] <fginther> doanac, mirv, wokring on a suggestion, one moment
[18:31] <balloons> psivaa, plars just an update on filemanager.. 4 errors are bugs, the rest I think I've fixed
[18:31] <plars> balloons: awesome, is it more consistent now too? or are the 4 bugs things that don't happen every time?
[18:32] <balloons> plars, the 4 remaining failures have to do with seemingly the clipboard not working
[18:35] <Mirv> fginther: ok. indeed xpathselect was probably not in radar when reverting to AP 1.3 for trusty.
[18:36] <psivaa> balloons: are the fixes in already with image 8?
[18:36] <fginther> doanac, Mirv, thomi, so we have two options: 1) add xpathselect 1.3 to trusty and revert the unity7 MP or 2) Land autopilot 1.4 in trusty and update the remaining autopilot tests
[18:36] <balloons> psivaa, no, i'm working on a branch
[18:37] <psivaa> balloons: ack, thank you :)
[18:37] <balloons> trying to get everything working :-)
[18:37] <fginther> either way 2) needs to happen eventually
[18:37] <doanac> 2 is probably less total work also.
[18:38] <fginther> with 2 there will be test failures for the image and for upstream merger, but this might put more pressure on getting them resolved
[18:38] <doanac> fginther: who makes the decision? asac?
[18:40] <fginther> doanac, this might be didrock's team. they did the original change to get 1.3 into trusty
[18:41] <fginther> doanac, this is probably a landing pipeline descision
[18:41] <doanac> yeah
[18:43] <doanac> fginther: given they are probably in meetings, should I send off an email to summarize?
[18:43] <fginther> doanac, good idea
[19:16] <slangasek> didrocks: clearly, that subtitle should have been written 'quickly improve'
[20:26] <Mirv> fginther: it should be a revert - as discussed before all AP 1.4 changes should land at once, otherwise we block various stacks for undetermined amount of time
[20:28] <Mirv> ogra_: are you about? the qtmultimedia/audioengine seed changes are finally greenlighted now
[20:31] <fginther> Mirv, I can start on the cu2d-config changes. Once that's done, can you remove the xpathselect 1.4 packages from the daily ppa?
[20:37] <Mirv> fginther: yes, I can remove it then
[20:42] <fginther> Mirv, doanac, can you review: https://code.launchpad.net/~fginther/cupstream2distro-config/xpathselect-trusty-1.3/+merge/193133
[20:43] <doanac> fginther: looks good
[20:45] <Mirv> +1, deleting the PPA build of xpathselect 1.4
[20:56] <fginther> Mirv, doanac, now to revert the unity7 bump of xpathselect: https://code.launchpad.net/~fginther/unity/revert-libxpathselect1.4/+merge/193137
[21:01] <doanac> fginther: reading
[21:02] <Mirv> thanks for that, hopefully we'll get desktop AP results after that. as an example, because of the problem I had to dedicate my laptop to running unity7 AP:s manually so that it would be possible to validate an libunity release, instead of getting the desktop results from jenkins.
[21:02] <fginther> Mirv, you remember to pack a spare laptop just for this purpose, right? :-)
[21:07] <Mirv> yeah, my draggable trusty 5y old Dell is so fun to travel with :)
[22:29] <thomi> doanac: ping?
[22:30] <thomi> doanac: can you please explain to me what the three touch images are? There's "touch_sf4p", "touch", and "touch_custom". Why are there several images, and what do they mean?
[22:32] <thomi> cihelp
[22:32] <thomi> ^^
[22:33] <cjohnston> thomi: one sec
[22:33] <thomi> thanks :)
[22:34] <cjohnston> touch == mir
[22:34] <cjohnston> custom is a custom variant
[22:35] <cjohnston> sf4p iirc is mir disabled
[22:35] <cjohnston> thomi: ^
[22:36] <thomi> cjohnston: any idea what's different on the custom image?
[22:36] <cjohnston> thomi: tis a question for achiang
[22:36] <thomi> ok
[22:37] <thomi> thanks charles
[22:37] <thomi> oops
[22:37] <thomi> thanks cjohnston
[22:37] <cjohnston> ya, him too
[22:37] <cjohnston> lol
[22:38] <charles> thomi: no problem at all
[22:38] <charles> thomi: anytime


[16:22] <ccprog> Just a question: is there really aneed for that google-analytics script on the wiki pages?
[16:23] <ccprog> For the last hour pages are not shown unless I deactivate JS - only because that script cannot be loaded.
[16:29] <frank_> ccprog: it works for me.


  Appimage is where it's at.
[00:08] <Scary_Guy> I heard they were actually working on version 5 of ReiserFS.  I'm not really sure it's necessary though with BTRFS and ZFS.
[00:10] <Scary_Guy> https://i.imgur.com/vJKgPmn.jpg
[00:11] <Scary_Guy> https://geekz.co.uk/lovesraymond/wp-content/ep057.jpg
[16:25] <jrwren> TIL: https://systemd.io/PORTABLE_SERVICES/
[17:54] <cmaloney> “Portable services” do not provide a fully isolated environment to the payload, like containers mostly intend to. Instead, they are more like regular system services, can be controlled with the same tools, are exposed the same way in all infrastructure, and so on. The main difference is that they use a different root directory than the rest of the system
[17:54] <cmaloney> So they're essentially jails at the systemd level
[17:55] <cmaloney> I feel like I should hate this
[18:25] <jrwren> systemd has already had systemd-nspawn https://www.freedesktop.org/software/systemd/man/systemd.nspawn.html
[18:33] <jrwren> portable services is kinda like an even lighter version of that. yeah, it is really an image based chroot for system services.


[02:05] <imgbot> [03:30] <imgbot> [03:30] <imgbot> [06:49] <Mirv> kdub: camako: robru: mir is still stuck in proposed
[06:49] <robru> Mirv: ugh. Valid candidate my ass!
[06:51] <robru> Mirv: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt i dont even
[06:51] <Mirv> robru: yeah that update_output looks like "the world will fail if trying to update mir"
[06:52] <robru> Mirv: and yet it passed silo verification...
[06:53] <robru> Mirv: lol, abiword to zenity. ZENITY. HOW DO YOU BREAK ZENITY.
[06:53] <Mirv> :D
[06:54] <robru> Mirv: but seriously I don't have a clue how to fix that
[06:55] <Mirv> yeah, I'm trying to update manually and see if it makes any sense, as soon as apt update would succeed
[06:58] <Mirv> so, someone has capped my bandwidth to archive.ubuntu.com to like 512kbit/s. hello 90's!
[06:59] <Mirv> oh, actually, in 1999 I had 100/10..
[06:59] <Mirv> hello 80's!
[07:00] <Mirv> in 80's I had ZX Spectrum and loaded from cassette at around 1500 bit/s, or sometimes the crazy hackers made it to 2600 bit/s turbo if you had really high quality cassette
[07:30] <Mirv> kdub: camako: so far we've only understood that update_output claims Mir would break everything, while in practice everything seems and upgrades fine (I've now installed all binary packages from source mir, from -proposed, on my laptop). we might need a wizard like cjwatson to check it eventually.
[09:02] <cjwatson> Mirv: you probably have a remaining dependency on a removed binary.  zenity breaking suggests that's probably in the vicinity of gtk.
[09:14] <cjwatson> Mirv: new libmirclient8 still Depends: mir-client-platform-mesa | mir-client-platform-android, both of which have been removed in favour of *2.  Furthermore, new libmirserver30 Depends: mir-platform-graphics-mesa | mir-platform-graphics-android, both of which have been removed in favour of *2.
[09:15] <cjwatson> kdub,camako: ^- mir bug
[09:16] <cjwatson> Mirv: when you're simulating the install for this kind of thing, check closely to make sure that it's possible to remove all the binary packages that the source package in question no longer builds.  proposed-migration pretends that they no longer exist when doing its calculations
[09:16] <infinity> Mirv: The simplest way to test that sometimes is just to hop in a chroot and "apt-get install (new packages) (broken package) remove1- remove2-"
[09:17] <infinity> Mirv: ie: tell apt "no, you can't install the ones we're removing" and see what happens.
[09:18] <infinity> In this case, "apt-get install libmirclient8 mir-client-platform-mesa- mir-client-platform-android-" was more than enough to show the issue.
[09:18] <cjwatson> Mirv: Oh, also, ubuntu-touch depends on mir-graphics-drivers-android.
[09:19] <cjwatson> Somebody should update the seeds, but the automatic update script probably won't work in this situation where the new thing is stuck in -proposed, so it's probably best to edit the metapackage directly.
[09:20] <cjwatson> Fortunately that's not rocket science.
[09:20] <infinity> cjwatson: It would be awfully nice if the try/pass/fail output gave a "would remove: bin1 bin2" line under the list of source package it's attempting an upgrade on, though.  Would be much easier to plug "apt-get install (list of fail) remove1- remove2-" into a console.
[09:21] <cjwatson> Yeah, I guess ...
[09:21] <cjwatson> patches welcome :)
[09:21] <infinity> cjwatson: I mean, I assume uploaders know what packages they're removing, but when I'm debugging someone else's fail, I need to look at diffs. :P
[09:25] <infinity> cjwatson: Who maintains britney upstream these days?  I feel like little formatting improvements like that should probably just go to Debian if I'm bothering to do them.
[09:25] <cjwatson> Niels Thykier mostly, I think
[09:25] <cjwatson> debian-release anyway
[09:26] <cjwatson> but: the NBS removal thing is a bit of an Ubuntuism to start with IIRC
[09:26] <infinity> cjwatson: My other consistent complaint (again, coming from doing "apt-get install (fail list)" is the unnecessary commas in the list, leading to the inevitable "echo list | sed 's/,//g' | xargs" which is silly.
[09:26] <cjwatson> I don't remember whether something like that would apply on either side
[09:26] <cjwatson> you'll have to see how closely it ties into the partial unstable handling
[09:27] <infinity> Though, with the complete illegality of commas as input to apt, maybe I can just make Michael accept them in the package list. :P
[09:27] <cjwatson> see also dpkg-checkbuilddeps
[09:27] <infinity> Yup.
[09:28] <infinity> checkbuilddeps has the excuse that it's control format, though.
[09:28] <infinity> And "foo (1.0) bar" is confusing without the commas.
[09:29]  * infinity takes what's left of his flu back to bed.
[10:06] <Mirv> cjwatson: infinity: thanks for all the advice. so indeed I didn't notice this "these packages are still in the archive but should be removed, and something depends on those"
[10:11] <Mirv> mir-platform-graphics-mesa/android has been replaced with *1, while mir-client-platform-mesa/android is at *2
[10:36] <Mirv> rsalveti: ^ if you're around, feel free to publish now that it does not seem anything scary, after it has built and some sanity testing. https://launchpadlibrarian.net/198975118/mir_0.12.0%2B15.04.20150227-0ubuntu1_0.12.0%2B15.04.20150228-0ubuntu1.diff.gz
[19:46]  * rsalveti waves
[22:08] <charles> rsalveti, want to approve the MP? :)
[22:08] <rsalveti> charles: yup, testing, reviewing and landing :-)
[22:08] <rsalveti> if all goes well
[22:08] <rsalveti> charles: can land the other one we got there as well
[22:08] <rsalveti> for indicator-datetime
[22:17] <rsalveti> mir finally landed :-)
[22:46] <robru> Sweet jeebus!


[18:54] <EoflaOE> I have installed Ubuntu 19.10 on VirtualBox after setting necessary settings. Everytime I boot to Ubuntu, it is stuck with the moving dots, but if I made it show messages by arrow keys, it boots instantly to the log-in screen.
[18:55] <lotuspsychje> EoflaOE: did you press F1 to see the text its stuck on?
[18:58] <EoflaOE> lotuspsychje: No.
[18:58] <lotuspsychje> you can switch to text boot at the dots with F1
[18:59] <EoflaOE> OK. I will reboot with pressing F1 to see the text.
[19:00] <EoflaOE> Pressed F1, and it won't switch from the stuck Ubuntu logo to the text that it's stuck on.
[19:02] <lotuspsychje> the dots dont move anymore?
[19:03] <EoflaOE> They are still moving
[19:03] <lotuspsychje> weird you cant switch text then
[19:03] <EoflaOE> Yes, I can't switch.
[19:04] <EoflaOE> Do I start Ubuntu again with nosplash? Or do something else?
[19:04] <lotuspsychje> you can try nomodeset sure
[19:04] <lotuspsychje> !nomodeset
[19:04] <lotuspsychje> or "quiet splash" edit to "" for text boot
[19:05] <EoflaOE> OK. I will reboot with these parameters.
[19:06] <EoflaOE> But my Ubuntu boots to GRUB and then to Ubuntu so fast I can't get it to open the menu using Shift.
[19:12] <EoflaOE> Finally managed to edit /etc/default/grub to remove "quiet splash" parameters, and updated GRUB, but when I reboot, it shows messages and it boots normally. Verified with the second restart, and it again booted.
[19:13] <lotuspsychje> the magic of ubuntu :p
[19:14] <lotuspsychje> was that already on 5.2 kernel EoflaOE ?
[19:14] <EoflaOE> Yes. On Linux 5.2,
[19:14] <EoflaOE> By the way restored "quiet splash", and it booted normally.
[19:15] <lotuspsychje> lovely
[19:16] <EoflaOE> Thanks so much! By the way before this problem occurred, when downloading updates for packages, an electrical outage caused Ubuntu to boot this weird way.
[19:17] <lotuspsychje> ah breaking updates is indeed never a great happening
[19:18] <EoflaOE> It's at the "downloading" stage at the event of the outage, the stage where "apt" should get all the files from the Internet (Ubuntu repo) before installing all.
[19:21] <EoflaOE> One question: Does Ubuntu have dark theme?
[19:22] <Bashing-om> EoflaOE: No fun ^^ ! Did you clean up and clear the cache - update and ' sudo apt -f install ;sudo dpkg --configure -a ; sudo dpkg -C ' to make sure all is good now ?
[19:22] <lotuspsychje> EoflaOE: the dark theme i use on 18.04 is adwaita-dark
[19:22] <lotuspsychje> EoflaOE: install gnome-tweak-tool to easy manage themes
[19:23] <Bashing-om> EoflaOE: dark theme - xubuntu does :) can not say about (u)buntu.
[19:23] <EoflaOE> Bashing-om: The apt -f install one did not do anything (it is all good; no interrupted install), and the two commands returned nothing (also good) | lotuspsychje: Will install that tweak tool.
[19:25] <Bashing-om> EoflaOE: Good to go :P
[19:26] <EoflaOE> lotuspsychje: Thanks! I have set the theme to Yaru-dark. | Bashing-om: Thanks!
[19:26] <lotuspsychje> great EoflaOE
[19:27] <EoflaOE> Thank you! Ubuntu is awesome on new machines.
[19:27] <lotuspsychje> EoflaOE: my favs packages at fresh install: sudo apt install preload haveged vlc gnome-tweak-tool qbittorrent
[19:28] <EoflaOE> lotuspsychje: Nice. I know vlc, gnome-tweak-tool, and qbitorrent, but what is "preload" and "haveged"?
[19:30] <lotuspsychje> !info preload
[19:30] <lotuspsychje> !info haveged
[19:30] <lotuspsychje> EoflaOE: both for faster/smoother experience
[19:31] <EoflaOE> lotuspsychje: Thanks. Will consider installing them tomorrow. I have to go to rest then sleep, because it's night on my timezone (UTC+02:00, 10:31 PM)
[19:33] <lotuspsychje> nite
[19:33] <EoflaOE> Good night.


 As I did few of the last upstream update I wanted to push the changes
[08:39] <didrocks> seb128: I have a message for you from vuntz: "you are not kind at all for not coming" :)
[08:39] <seb128> ah ah ah
[08:39] <mvo> seb128: yes, slept half of it :) so it went by pretty fast
[08:39] <didrocks> seb128: I met james_w, keybuck, and some other (but few) canonical boy.
[08:40] <seb128> didrocks: lool was there too no?
[08:40] <mvo> I do a clutter update in my ppa and will package metacity-clutter - or did anyone look at this already?
[08:40] <didrocks> so, appart from sharing my room for 2 days with huats, everything were really enjoyable
[08:40] <didrocks> (joking :))
[08:40] <mvo> haha
[08:40] <crevette> :)
[08:40] <seb128> mvo: the mail from pitti suggested that the code is no ready to be shipped yet
[08:40] <didrocks> seb128: yeah, I just saw him, but not talk with him
[08:40] <seb128> oh, huats was there too
[08:41] <mvo> I would have loved to come, but it conflicts with the sprint for me
[08:41]  * pitti hugs seb128, mvo, and didrocks, good morning
[08:41] <seb128> I'm wondering if he will manage to get this gnome-keyring update done one day ;-)
[08:41] <seb128> he's working on it for 3 weeks now
[08:41]  * seb128 hugs pitti
[08:41] <didrocks> Hi pitti :)
[08:41] <mvo> seb128, pitti: the mail I have about metacity-clutter is that someone should have a look at it, no?
[08:41] <didrocks> seb128: well. He fights with it :) Even he asks something about it to vuntz
[08:42] <pitti> mvo: just whether someone has an opinion about its readiness
[08:42] <didrocks> seb128: I know that his libgda update is ready, but he does not know how to test it
[08:42] <pitti> mvo: if you want to play around with it, I won't stop you, of course :-P
[08:42] <mvo> :)
[08:42] <mvo> I will, should be quick (I hope)
[08:42]  * crevette is working on libopenobex-1.4 and he has some pain :)
[08:42] <seb128> mvo: there is an another thread going where you are not cc-ed, and pitti states that's mirco said it's not ready to be used yet
[08:43] <mvo> aha
[08:43] <seb128> didrocks: to be honest I don't care about libgda, gnome-desktop is stopping GNOME updates where libgda is not really used
[08:43] <didrocks> seb128: appart for my python-gnome-extras update :)
[08:44] <seb128> didrocks: btw were you supposed to work on the gnome-python update too?
[08:44] <didrocks> seb128: yes, I will do it tonight, as well as on gtkmm
[08:44] <seb128> ok
[08:44] <didrocks> but I fell that gtkmm will be a pain as everything is patched inline...
[08:44] <seb128> ?
[08:44] <mvo> james_w: hi! I hope you had a good trip. did you seed apt-transport-https already? if not, I can do it here
[08:45] <seb128> it's not
[08:45] <didrocks> seb128: sure ? Let me look at the diff.gz
[08:45] <seb128> didrocks: it's package in the pkg-gnome svn where only the debian directory is stored so if there is changes not in the diff.gz that's an error
[08:47] <seb128> mvo, pitti: btw extra hand on desktop sponsoring are welcome if you have some time this week, I've been fighting the queue a bit during the sprint but there is still lot
[08:47] <pitti> right, on my list
[08:47]  * seb128 hugs pitti
[08:47] <pitti> seb128: I'm currently fixing pkgstriptranslations to not break the publisher on parallel builds
[08:47]  * crevette is feeding the sponsoring queue
[08:47] <crevette> :)
[08:47] <pitti> seb128: I think the buildds set DEB_BUILD_OPTIONS=parallel or so
[08:47] <seb128> pitti: oh, you found the bug?
[08:47] <pitti> seb128: which makes glib2.0 create broken translations.tar.gz
[08:48] <didrocks> seb128: http://paste.ubuntu.com/115888/
[08:48] <mvo> seb128: sure, is all on the sponsoring queue?
[08:48] <seb128> mvo: yes
[08:48] <pitti> seb128: looking at the build log and debian/rules, it's the only explanation I have (things do run in parallel there)
[08:48] <didrocks> seb128: there is a lot of autotools changes but also other one (like gtkmm-1.2.10/src/gtk--/base.h
[08:49] <seb128> mvo: just pick anything on dholbach's page if you want, I commented on totem-pl-parser but didn't start on it so you can do and totem or anything else there
[08:49] <seb128> didrocks: it just seems that whoever did the previous update screwed his autoreconf patch build
[08:49] <didrocks> seb128: can autoreconf changes .h files?
[08:50] <seb128> didrocks: is it using a patch system or not?
[08:50] <seb128> didrocks: why not, if there is a corresponding .in and a rule to update those or if those are automatically build by some tools
[08:51] <didrocks> seb128: it's not using one apparently (I have to check further, btw)
[08:51] <didrocks> seb128: as we are in sync with debian, setup one is not a great idea, is it?
[08:51] <seb128> didrocks: the 2.14.1 copy on my disk uses simple-patchsys in its rules
[08:52] <didrocks> seb128: ok, so, I will run it and make it clean
[08:52] <seb128> didrocks: ok good
[09:05] <lool> didrocks: You should have said hi!
[09:06] <crevette> hello lool
[09:06] <lool> Hey
[09:13] <seb128> lut lool
[09:13] <seb128> lool: how was fosdem this year?
[09:15] <lool> It was packed with people, but I saw less familiar faces as usually
[09:16] <lool> I was relatively unlucky in my talk attendance in that the interesting ones were happening together and the others I had seen a couple of times already
[09:16] <lool> But it was great to see a bunch of people and some interesting presentations nevertheless!
[09:16] <lool> Less so to get my luggage stolen afterwards though
[09:17] <mvo> lool: oh? someone stole your stuff :( ?
[09:17] <mvo> at fosdem?
[09:19] <seb128> lut huats
[09:19] <huats> hello seb128
[09:19] <seb128> huats: how is gnome-keyring going?
[09:19] <lool> mvo: No, in the train station  :-/
[09:20] <huats> seb128: not much to say
[09:20] <seb128> lool: oh :-(
[09:20] <lool> With some dev hardware in it unfortunately (as I wasn't flying)
[09:20] <huats> the upstream seems to be unable to fix the LDFLAGS stuffs
[09:20] <mvo> lool: right, that sucks :(
[09:21] <lool> In practice, I didn't lose any non-replaceable stuff or personal or company data, but I did lose some expensive devices sadly
[09:23]  * seb128 hugs lool
[09:23] <seb128> not lucky
[09:24]  * seb128 notes to not let unattended luggage at train station either
[09:25] <lool> It was on my side, like 2 cms away (really) but I was buying a book in a press shop and the guy just took it as if it was his
[09:26] <lool> I noticed 30 seconds later, but outside everybody has a luggage
[09:26] <didrocks> lool: I am so shy, you know :p But I will not miss next time, promess (I just saw you far far away on the opening conf)
[09:26] <huats> lool: oh... that sucks !
[09:27] <didrocks> lool: In Bruxelles train station?
[09:28] <didrocks> lool: yeah, that really sucks :/
[09:28] <lool> didrocks: Yes, in Bruxelles Midi
[09:46] <crevette> salut huats
[09:48] <seb128> pitti: btw http://svn.gnome.org/viewvc/seahorse?view=revision&revision=2774
[09:50] <seb128> crevette: you are working on the obex server update?
[09:50] <crevette> obex-data-server ? done, and in lp
[09:50] <huats> hello crevette
[09:50] <seb128> crevette: ah cool, I though other libs updates were required
[09:51] <crevette> it needs eventually libopenobex 1.4 which is not packaged yet, but it seems too hard for me, anyway I'm trying to package it
[09:51] <pitti> seb128: rocking!
[09:51] <crevette> seb128: but I didn't check symbols differences
[09:52] <seb128> crevette: is the lib required or not?
[09:52] <crevette> which one ?
[09:52] <seb128> libopenobex
[09:52] <crevette> it can be built against the libopenobex we have in ubuntu now
[09:53] <seb128> crevette: oh, that's just a lib update?
[09:54] <seb128> slomo: hey, gst-plugins-good0.10 should be synced?
[09:55] <crevette> seb128: https://bugs.edge.launchpad.net/ubuntu/+source/obex-data-server/+bug/327103
[10:45] <mvo> seb128: I just checked the updated by chris and its a bit inconvienient to apply them to bzr, I think I wait for him to appear and ask if he can either do debdiffs or a bzr branch
[10:45] <seb128> ok
[10:45] <seb128> what is inconvienient?
[10:46] <seb128> can't you diff the debian directory between version and commit that for the upgrade?
[11:07] <mvo> seb128: sure, its still a bit inconvinient, a debdiff could be applied right into bzr
[11:08] <seb128> right
[11:08] <seb128> you don't want a debdiff though
[11:08] <mvo> seb128: for the other, I first need to get the tarball, build the source deb, get the old deb, debdiff and then apply that into bzr
[11:08] <seb128> but a debian directory debdfiff rather
[11:09] <seb128> right, just try to point him to bzr so he knows for next update, he's quite active on desktop updates and bug triage but I think he's not used to use bzr yet
[11:09] <mvo> seb128: sure, I added it into one of the bugreport, when he is online I will be happy to mentor him for the bzr stuff
[11:09] <seb128> ok good
[11:10] <mvo> I think he is US timezone based
[11:10] <james_w> mvo: https://code.launchpad.net/~james-w/ubuntu-seeds/platform.jaunty.apt-transport-https
[11:10] <seb128> not sure but he's usually on IRC in evening european hours
[11:10] <james_w> mvo: I was going to ask Colin to review
[11:12] <mvo> james_w: aha, thanks! I leave it to him then
[11:39] <didrocks> hey james_w ;)
[11:40] <james_w> hey didrocks, home safely?
[11:41] <didrocks> james_w: yes, a little bit late, but no problem :) and you?
[11:41] <james_w> fine thanks
[11:54] <slomo> seb128: yes
[12:17] <seb128> slomo: ok good ;-)
[12:55] <crevette> hey seb128, thanks for the update
[12:56] <seb128> crevette: you're welcome, thank you for the work ;-)
[12:56] <crevette> seb128: bah it's a minor package
[12:56] <seb128> crevette: should the gnome-user-share upload wait until the mdns things is updated?
[12:56] <crevette> 0.4.4 was just released :)
[12:57] <seb128> crevette: another update for you then ;-)
[12:57] <crevette> seb128: yes, IIRC mdns 0.6 is required
[12:57] <seb128> how did you build and test the update?
[12:57] <crevette> seb128: yeah
[12:57] <crevette> I talk with debian openobex developper
[12:58] <crevette> the 1.5 was released yesterday, and he should buid it b y the middle of feb, is it okay for ubuntu ?
[12:58] <crevette> seb128: not really
[12:58] <crevette> let me try
[13:00] <seb128> crevette: buid it?
[13:00] <seb128> ah
[13:00] <seb128> he will upload to debian you mean ?
[13:00] <seb128> yes, that should be alright
[13:00] <crevette> yeah I build it myself
[13:01] <seb128> didrocks: there?
[13:02] <seb128> didrocks: what update do you still have on your todolist?
[13:03] <crevette> seb128: wonderful it works and fixes another issue
[13:03] <crevette> :)
[13:03] <crevette> now you'll see one feature I've worked on and people never seen
[13:04] <didrocks> didrocks: I have gnome-python-extras which waits for libgda, gnome-python & gtkmm that I will handle tonight, and evince that is waiting for sponsoring
[13:05] <seb128> didrocks: oh evince is waiting for review, good, let me do that now
[13:05] <seb128> didrocks: is gnome-python-desktop also on your list?
[13:05] <didrocks> seb128: you can see some additional information there: https://wiki.ubuntu.com/DidierRoche/MOTU/bugsaction
[13:05] <seb128> just cleaning tarballs which are not uptodate
[13:05] <didrocks> (for evince)
[13:06] <didrocks> and no, but I can take it
[13:06] <seb128> ah right you told me about that the other day
[13:06] <seb128> I was in berlin sprinting though and didn't look at it
[13:06] <didrocks> seb128: no problem, you told me it wasn't possible for you to review it then :p
[13:06] <seb128> didrocks: ok good, if you don't feel overworked already it's for you ;-)
[13:06] <didrocks> seb128: I get used to gnome-python* ;)
[13:06] <seb128> didrocks: sometimes I tell things which make sense ;-)
[13:07] <didrocks> seb128: only sometimes? That's no usually the case? :D
[13:07] <seb128> didrocks: this wikipage is amazing, how many centuries did you spend on writing it? ;-)
[13:07] <didrocks> seb128: it was to "record" my sponsors :-)
[13:07] <didrocks> seb128: as you can see, most of them aren't described
[13:08] <didrocks> seb128: but it was really useful for my first package
[13:08] <seb128> right, most people don't do a such detailled job, it's quite impressive ;-)
[13:08] <didrocks> seb128: I think it was a real gain to avoid forgetting things
[13:09] <seb128> didrocks: I don't understand your gconf note there
[13:09]  * crevette is packaging ods .0.4.4
[13:09] <didrocks> seb128: hum didn't updated it
[13:09] <seb128> crevette: good ;-)
[13:09] <didrocks> seb128: one sec, let me have a look at debian/rules first
[13:09] <didrocks> (to avoid telling bad things ;))
[13:10] <crevette> seb128: you seems to be interested by ods, why? just to fix bugs or you'" using bluetooh now ?
[13:10] <crevette> :)
[13:10] <seb128> crevette: not especially interested but we had a gvfs bug where obex was not working on a nokia phone which is fixed in the new version
[13:11] <crevette> which bug ?
[13:11] <seb128> bug #324246
[13:11] <seb128> I already closed it
[13:11] <crevette> I admit I don't test all use caseq, like obex://
[13:11] <didrocks> seb128: that's there. There is something I didn't understand in the package. Let me explain:
[13:12] <didrocks> seb128: so, I changed the DESTDIR from debian/evince to debian/tmp
[13:12] <seb128> crevette: don't worry it's still early in the cycle and the upstream diff looks alright
[13:12] <didrocks> the gconf schemas were in debian/tmp/etc. In evince.install I added debian/tmp/etc/gconf
[13:13] <seb128> didrocks: you can as well drop the line
[13:13] <didrocks> seb128: ok, I will know that's a possibility :)
[13:13] <seb128> it was there from the time where evince-gtk was built I think, the default is tmp when you have several binaries
[13:13] <Laney> (btw, f-spot might ftbfs and if it does you probably need to add CSC=/usr/bin/csc to the configure arguments)
[13:14] <didrocks> seb128: when building it, with dh_gconf I thing, the gconf schemas are in debian/evince/etc AND in debian/evince/usr/share...
[13:14] <didrocks> but finally, in the package, it just remains in /usr/share...
[13:14] <didrocks> (and there is no rm -rf debian/evince/etc...)
[13:14] <didrocks> in debian/rules
[13:14] <didrocks> so, this was a strange behavior I can't explain
[13:16] <didrocks> seb128: I tried as well not putting in evince.install file this reference (debian/tmp/etc/gconf), but we don't get debian/evince/usr then...
[13:17] <seb128> didrocks: listing the etc directory is correct
[13:17] <seb128> dh_gconf does move those to usr
[13:17] <didrocks> seb128: I use the pbuilder hook to log when the package is built
[13:18] <didrocks> and I see as well debian/evince/etc/gconf and debian/evince/usr/share/gconf
[13:18] <seb128> Laney: due to some new changes in the mono stack?
[13:18] <didrocks> but only the latter is present in the package
[13:18] <seb128> didrocks: see that where?
[13:18] <crevette> seb128: I would like to push packaging of ods into VCS, who should I contact
[13:18] <seb128> didrocks: those are installed in etc and then moved to use when dh_gconf is run
[13:18] <seb128> crevette: it's already in a vcs apparently, see the control
[13:18] <didrocks> seb128: where I build my packages...
[13:19] <Laney> seb128: I'm not sure, but it got dropped in Debian from my Ubuntu patch.
[13:19] <didrocks> let me check again, but I am almost sure of it
[13:19] <seb128> Laney: I will sponsor the debdiff on launchpad and we will see what happens ;-)
[13:19] <seb128> that's the lazy way
[13:19] <seb128> I will let one of you guys fix it if that breaks
[13:19] <Laney> heh
[13:19] <Laney> give it a test build?
[13:19] <seb128> or get the fix in debian and we can sync the new revision ;-)
[13:20] <Laney> I asked meembey to upload, we'll see if he does it soon
[13:20] <Laney> meebey*
[13:20] <seb128> Laney: I can do that but I need to wait on the new binaries to be published then
[13:20] <Laney> k
[13:20] <Laney> I don't think that build-dep version is a problem btw, we have 2.0 in Jaunty anyway
[13:20] <seb128> didrocks: not sure, I never really bothered about checking the build dir I just look at the debs
[13:20] <seb128> didrocks: what I now is that upstream uses etc and dh_gconf move the schemas to usr
[13:21] <seb128> you should have the etc directory in the tmp location
[13:21] <crevette> seb128: yeah I know, but I wanted to have it merge rather
[13:21] <seb128> but the evince dir should have only the etc one after the build
[13:21] <seb128> crevette: well ask mvo for bzr questions ;-)
[13:21] <didrocks> seb128: yes, but I have another one etc/gconf in debian/evince :)
[13:22] <didrocks> so, I was surprised to not see it also in the resulting package
[13:22] <seb128> didrocks: let me review and testbuild your upload so we can continue this discussion
[13:22] <didrocks> let me check again, two minutes :)
[13:22] <crevette> seb128: you 'll a lot of handful people to build packages now :)
[13:22] <didrocks> yes
[13:22] <didrocks> seb128: oki
[13:22] <seb128> crevette: that's nice isn't it ;-)
[13:22] <seb128> desktop team rocks!
[13:23] <mvo> crevette: I'm around if you have a bzr question
[13:23] <didrocks> seb128: yes it really rocks \o/
[13:23] <crevette> a build-farm
[13:23] <crevette> mvo: I seen that obex-data-server and bluez packaging we're not pushe recently
[13:24] <seb128> that would be bad citizen work
[13:24] <crevette> 1) if if want to push changes, should I do a commit per version to fill the gap, or should I just get the latest version and do that in one commit ?
[13:24] <crevette> seb128: I'm guilty too
[13:25] <mvo> crevette: just do it with one commit, that will make your work a lot easier I htink
[13:25] <crevette> mvo: as usual I push it to my branch and you'll do the merge ?
[13:26] <mvo> crevette: yes, that sounds fine
[13:29] <seb128> didrocks: one build later
[13:29] <seb128> $ find debian -name schemas
[13:29] <seb128> debian/tmp/etc/gconf/schemas
[13:29] <seb128> debian/evince/usr/share/gconf/schemas
[13:29] <seb128> didrocks: not, it's not duplicated there
[13:29] <seb128> didrocks: dunno how you do your builds ...
[13:30] <didrocks> seb128: I am currently building it again, mayve my memory is very bad :)
[13:30] <didrocks> maybe*
[13:30] <didrocks> seb128: if so, that makes sense that dh_gconf do what it claims to do :)
[13:30] <didrocks> does*
[13:31] <seb128> didrocks: otherwise the binaries look mostly ok
[13:31] <didrocks> # find debian -name schemas
[13:31] <didrocks> debian/evince/etc/gconf/schemas
[13:31] <didrocks> debian/evince/usr/share/gconf/schemas
[13:31] <didrocks> debian/tmp/etc/gconf/schemas
[13:31] <didrocks> in my pbuilder
[13:31] <didrocks> I am not crazy \o/
[13:32] <seb128> didrocks: you probably want to install the documentation in the corresponding binaries, ie /usr/share/gtk-doc/html/libevdocument in libevdocument-dev and not evince
[13:32] <didrocks> (and I check again, the binary does only contains /usr/share..)
[13:33] <seb128> didrocks: is the directory empty in etc?
[13:34] <didrocks> seb128: no: http://paste.ubuntu.com/116065/
[13:34] <seb128> didrocks: weird
[13:34] <didrocks> seb128: really, isn't it?
[13:35] <seb128> didrocks: did you run dh_install --list-missing there?
[13:35] <didrocks> seb128: yes, it was listing .a and .la files
[13:35] <seb128> didrocks: it would recreate it
[13:35] <didrocks> but not listing this one
[13:35] <seb128> ok, so that's due to it
[13:35] <didrocks> ?
[13:36] <seb128> the dh_install call redo the install
[13:36] <seb128> but you don't run dh_gconf after that
[13:36] <seb128> so you reinstall in etc but don't move those
[13:36] <seb128> rm the etc dir
[13:36] <didrocks> ok, that's understable :)
[13:36] <seb128> run dh_install --list-missing
[13:36] <seb128> and look it's back there
[13:36] <seb128> dh_install do its job
[13:36] <didrocks> let me try
[13:37] <didrocks> (I was think dh_install --... would not launch dh_install only)
[13:37] <seb128> dh_* tools don't call other dh_tools
[13:37] <seb128> that's why you get everything listed in debhelper packages for example
[13:37] <crevette> mvo: I don't understand, I can 't specify bluez and cannot specify bluez-4.x, what should I do ?
[13:38] <didrocks> seb128: yes, you right :) that's just strange that dh_install --list-missing is not listing debian/tmp/etc (other it knows from dh_gconf that can be moved)
[13:39] <didrocks> seb128: thanks a lot for the explanation! What about the documentation, you told me?
[13:39] <seb128> didrocks: you're welcome
[13:39] <crevette> mvo: sorry I forgot the pastebin link http://pastebin.com/m22823088
[13:39] <seb128> didrocks: you should move the api documentation in the corresponding binaries, not in the evince binary
[13:40] <didrocks> (seb128: I told you I like to understand weird stuff ;))
[13:40] <seb128> didrocks: and your symlinking in the rules are weird
[13:40] <seb128> don't do that
[13:40] <didrocks> seb128: ok for the place (I thing this is an option for dh_installdoc)
[13:40] <didrocks> seb128: for symlinks?
[13:40] <seb128> why do you want to change the location?
[13:40] <didrocks> It was what were used in evince-dbg
[13:41] <seb128> right, not sure why it's there but that's wrong for libs
[13:41] <seb128> especially that you install those html in the evince binary which can be not installed
[13:42] <didrocks> seb128: you just told me to change the location for libevdocument, no?
[13:42] <seb128> just installed /usr/share/gtk-doc/html/libevdocument in libevdocument-dev and not evince
[13:42] <seb128> do the same for the other library
[13:42] <seb128> and drop those weird rules call
[13:42] <didrocks> even for -dbg one?
[13:42] <seb128> no, let the dbg the way it is
[13:42] <seb128> that's coming from debian
[13:42] <seb128> and doesn't hurt
[13:42] <seb128> the dbg depends on the binary anyway
[13:42] <seb128> the libs don't depends on evince
[13:43] <seb128> just drop your rules hack
[13:43] <seb128> and update the 3 .install to list only the html api corresponding to each binary
[13:43] <seb128> each libevince*-dev its documentation
[13:43] <mvo> crevette: try bzr push --create-prefix lp:~bmillemathias/+junk/bluez-ubuntu for now, look like LP madness
[13:43] <seb128> evince has /usr/share/gtk-doc/html/evince
[13:44] <didrocks> seb128: and for libevince* (without -deb)?
[13:44] <didrocks> -dev*
[13:44] <seb128> didrocks: in evince
[13:44] <seb128> or what do you mean?
[13:44] <crevette> mvo: it's been like that for few days
[13:44] <didrocks> hum, -dev has a dependency on libev..., that's why I thought a symlink was good
[13:45] <seb128> but what do you try to get there?
[13:45] <crevette> mvo: thanks you can get the branch for bluez
[13:45] <seb128> didrocks: I don't understand what you try to solve
[13:46] <didrocks> seb128: like for -dbg stuff, a symlink from the -dev documentation on the corresponding binary library doc
[13:46] <seb128> didrocks: the documentation are installed in debian/tmp/usr/share/gtk-doc/html and used correctly there
[13:46] <didrocks> right
[13:46] <seb128> didrocks: install the documentation directly in the libevince*-dev that's how it's done usually
[13:46] <seb128> no need of any symlink this way
[13:47] <seb128> the -dbg hack is just to spare CD space I guess or similar
[13:47] <seb128> since evince and evince-dbg are similar
[13:47] <didrocks> seb128: and in the binary library (not -dev), just evince documentation?
[13:47] <seb128> there is no specific documentation for the dbg
[13:47] <seb128> didrocks: no, nothing in the libs, library should not conflict on soname changes
[13:47] <seb128> didrocks: there is 3 html directory, one for evince binary and one for each library
[13:48] <seb128> didrocks: in library you only put the library itself since you want no common files when the soname is changed
[13:48] <didrocks> seb128: ok, so the documentation for each library must only be put in -dev
[13:48] <seb128> right
[13:49] <seb128> if you need to api documentation you probably have the dev installed anyway
[13:49] <didrocks> seb128: ok, I will note it in my "logging wiki page" :) let me handle that and push a new version
[13:49] <didrocks> seb128: it was not mentionned in the library classroom, that's the reason I made this way
[13:50] <seb128> didrocks: oh btw please drop the hildon patch and the lpia build-depends while you are at it
[13:50] <seb128> didrocks: I got the request from a mobile team guy during the sprint
[13:50] <didrocks> it's not needed anymore?
[13:50] <didrocks> ok
[13:50] <didrocks> I thought that the mobile team added extra patch in some way :)
[13:50] <seb128> the patch was moved out of the patches directory and not used for a while
[13:50] <didrocks> that's why I kept it :)
[13:50] <didrocks> no problem*
[13:50] <seb128> and they don't plan to rewrite it now
[13:50] <didrocks> oki
[13:50] <seb128> and the build-depends are outdated and they want to clean some of those packages now
[13:51] <seb128> so just drop those and the patch in the update
[13:51] <didrocks> seb128: I will do all that stuff just after a meeting :)
[13:51] <seb128> didrocks: ok, otherwise pretty good work for a first library split!
[13:51] <didrocks> seb128: thanks! ;)
[13:52] <seb128> didrocks: update the descriptions too btw
[13:52] <seb128> didrocks: "Document (postscript, pdf) viewer - debugging symbols" is the short description for the new libraries ;-)
[13:53] <didrocks> seb128: ok, wrong copy-paste :-)
[13:53] <seb128> didrocks: description are usually no fun to write but drop at least the debugging symbols there which is wrong ;-)
[13:53] <didrocks> yeah, I'm sorry for this :)
[13:53] <seb128> that's ok
[13:54] <seb128> didrocks: you could also add libs and libdevel section to those binaries
[13:55] <seb128> didrocks: and you can also probably remove the cleaning line in the rules for evince and update the .install no to list *.so in the nautilus directory for example but that's a detail
[13:55] <seb128> didrocks: I think that's all for my comments ;-)
[13:55] <didrocks> seb128: it was also not mentionned in the classroom too. I have to write a wiki page about it :)
[13:55] <seb128> where is huats now, he needs to hand me work too ;-)
[13:56] <didrocks> remove the claning lines in the rules? it will add a new change from debian
[13:56] <didrocks> cleaning*
[13:56] <seb128> didrocks: well, reading the comment it was meant to be there because there was no lib split
[13:57] <seb128> you can let it too if you want that's a detail
[13:58] <crevette> mvo: is there some kind of branch per ubuntu release ?
[13:59] <didrocks> seb128: yes. I will try to push those diff to debian back
[13:59] <seb128> didrocks: they will probably not start on 2.25 now
[13:59]  * didrocks just finished a copy/paste to be sure to forget anything :)
[13:59] <didrocks> seb128: but I can still push to aliot svn, right?
[14:00] <seb128> not really
[14:00] <didrocks> and once they will want to take it, after lenny release, they will, no?
[14:00] <seb128> they split by distribution usually
[14:00] <seb128> ie, if there is already an unstable and an experimental version and want to stay on 2.24 for experimental
[14:00] <seb128> there is no really a stagging right now there
[14:01] <seb128> you can try to squeeze that somewhere
[14:01] <seb128> on send your work as a 2.26 update when 2.26 will be available
[14:01] <didrocks> ok, and they will only update to 2.26, when unstable will be "Squeeze"?
[14:02] <seb128> not especially, they could do 2.24 to 2.26 in experimental too
[14:03] <didrocks> seb128: ok, but only stable GNOME release
[14:03] <didrocks> so, we push back only stable version, right?
[14:03] <didrocks> (for GNOME)
[14:03] <didrocks> in unstable/experimental
[14:04] <seb128> usually yes
[14:04] <didrocks> ok
[14:05] <didrocks> a lot of things to note/triage/make clear on the wiki :)
[14:05] <didrocks> seb128: I will keep you updated when all of this stuff is done
[14:05] <seb128> ok
[14:05] <seb128> thanks for the work
[14:06] <seb128> let me know when the package is updated, I'm rather interested in that than in your wiki documentation ;-)
[14:06] <didrocks> seb128: thanks to you :)
[14:06] <didrocks> seb128: yes, I'm sure, you prefer binaries or source :p
[14:13] <crevette> seb128: https://bugs.edge.launchpad.net/ubuntu/+source/obex-data-server/+bug/327188 :)
[14:13] <seb128> crevette: thanks
[14:14] <fta2> seb128, evo crashes when i tag a message as junk. known?
[14:14] <seb128> dunno, I don't use tagging or junk
[14:14] <seb128> fta2: copy your stacktrace on /usr/share/gtk-doc/html/libevdocument in libevdocument-dev and not evince
[14:14] <seb128> update
[14:14] <seb128> fta2: http://bugzilla.gnome.org/dupfinder/simple-dup-finder.cgi
[14:18] <fta2> gnome bug 569700
[14:19] <fta2> in my case, it's when i junk a message while it's not completely loaded (tons of images)
[14:19] <seb128> fta2: that's a frequent crasher, I triggered it several times by deleting spams in inbox
[14:21] <fta2> just started today for me
[14:23] <crevette> seb128: before doing the sponsor hold a bit if you can I need to add a lp bug being fixed
[14:23] <seb128> crevette: I was looking at it
[14:23] <seb128> fta2: right, you probably just upgraded to 2.25.90 today
[14:23] <seb128> crevette: which one do you want?
[14:23] <crevette> seb128: 291043
[14:23] <seb128> bug #291043
[14:26] <seb128> crevette: seems there is no patch to consider there
[14:27] <crevette> seb128: no, but at least the bug is corrected in gnome-user-share
[14:27] <crevette> hey cassidy
[14:27] <seb128> crevette: well do you want to do changes to ods?
[14:28] <crevette> which changes? to the changelog?
[14:29] <seb128> crevette: dunno you asked me to wait before uploading, what do you want to change?
[14:29] <crevette> I wanted to add that it fixes the bug I gave you
[14:29] <seb128> crevette: but it doesn't
[14:29] <seb128> crevette: at least 0.4.4 doesn't
[14:29] <crevette> it did for me
[14:29] <seb128> 0.4.3 to 0.4.4?
[14:29] <seb128> ie 0.4.3 was not working?
[14:30] <crevette> and on the upstream bug I had a confirmation it is fixed by another reporter
[14:30] <seb128> that's weird
[14:30] <seb128> there is almost no change there
[14:30] <crevette> 0.4.3 is fixing the bug
[14:30] <seb128> ok, that has already been uploaded
[14:30] <seb128> just close the bug on launchpad
[14:30] <crevette> yep but I didn't noticed that
[14:30] <seb128> well listing it as a 0.4.4 fix would be wrong
[14:30] <crevette> seb128: nothing to expect for intrepid ?
[14:30] <seb128> just close the bug saying 0.4.3 fixed it
[14:31] <seb128> no, that's too much of a detail, we got almost no user complain and intrepid is not a lts
[14:32] <seb128> uploaded
[14:32] <crevette> thanks a lot
[14:32] <seb128> you're welcome
[14:45] <crevette> seb128: sorry for being dumb but how can I close a bug telling it is fixed, perhaps I don't have enough power for that ?
[14:45] <seb128> click on one of the small arrows in the corresponding line?
[14:46] <seb128> it should give you an area to write comments and change settings, if some are locked you don't have the bugtriage rights
[14:47] <crevette> I did set the status for each product in bug 291043, but is ther a way to close the bug globally ?
[14:48] <seb128> no, that's ok this way
[14:49] <crevette> hello mclasen
[14:50] <mclasen> morning
[14:57] <crevette> seb128: does it exist a script for request sponsorship, because I'm tired to do it manually :)
[14:58] <seb128> crevette: not that I know but maybe dholbach has one
[15:17] <seb128> huats: !!!
[15:17] <seb128> ;-)
[15:17] <huats> seb128: !!!
[15:18] <huats> seb128: I haven't forgotten you
[15:18] <huats> :)
[15:18] <seb128> good ;-)
[16:21] <pitti> I'll upload totem{,-pl-parser}? from the sponsoring queue now
[16:35] <Davedan> I accedently draged the toolbar to the right. how do I put it back in the top of the screen?
[16:36] <didrocks> Davedan: you can drag and drop it to the top
[16:37] <didrocks> (just clic in a empty space of the bar)
[16:37] <Davedan> ok thanks
[16:38] <didrocks> you're welcome :)
[16:54] <crevette> hello gentlemen
[16:57] <huats> hello crevette
[16:59] <crevette> hey huats
[16:59] <crevette> tx seb128
[17:27] <pitti> seb128: just got to sponsoring totem and -plparser, sorry; will do more tomorrow morning
[17:27] <pitti> tomorrow was too much other stuff going on
[17:27] <seb128> pitti: thanks, don't worry there is nothing urgent ;-)
[17:27]  * seb128 hugs pitti
[17:54] <seb128> hey chrisccoulson
[17:54] <chrisccoulson> hi seb128
[17:54] <seb128> didrocks: was that you who I pinged about pidgin some days ago, I'm not sure now?
[17:54] <seb128> chrisccoulson: good work on those deskop changes ;-)
[17:54] <chrisccoulson> you're welcome:)
[17:55] <seb128> chrisccoulson: you should talk to mvo about using bzr btw ;-)
[17:55] <chrisccoulson> i'll put those changes in to bzr in a bit if they haven't been done already. i didn't realise they were maintained there :/
[17:55] <seb128> chrisccoulson: since you seem to be looking at f-spot maybe you could have a look at trying to get the other patches which are waiting for sponsoring to debian?
[17:56] <seb128> chrisccoulson: there is some listed on http://people.ubuntu.com/~dholbach/sponsoring/index.html
[17:56] <chrisccoulson> yeah, i'll take a look at those in a bit
[17:56] <seb128> thanks
[17:56] <seb128> apt-get source tell you when something is maintained in bzr
[17:56] <seb128> easy to not notice if you are used to not read the log though ;-)
[17:57] <chrisccoulson> yeah, and i tend to just manually download the sources instead of using apt-get at the moment, as i still do most things on my intrepid machine, and i don't know if i can use apt-get to download the jaunty sources
[17:59] <seb128> you can
[17:59] <seb128> just add a jaunty deb-src source
[17:59] <seb128> it will get the most recent source
[17:59] <chrisccoulson> i never thought of that ;) i'll give that a try in a bit
[17:59] <chrisccoulson> thanks
[17:59] <seb128> you're welcome
[17:59] <chrisccoulson> what i really need to do is upgrade this machine to jaunty though, without my partner noticing
[18:01] <chrisccoulson> is anything happening with the fast-user-switch-applet this cycle?
[18:01] <seb128> no
[18:01] <seb128> no switch to the new gdm no change to the applet for jaunty
[18:01] <seb128> the dxteam is busy working on other things and jaunty is planned to be mostly a bug fix cycle
[18:02] <chrisccoulson> i was looking at a few bugs for the existing applet and was going to try and fix them, just as long as the applet wasn't going to change much over the next few weeks
[18:03] <seb128> good idea
[18:03] <seb128> but the applet will probably change a lot next cycle
[18:03] <chrisccoulson> yeah, i can imagine. will a lot of our existing patch-set need porting across?
[18:03] <seb128> if we switch to the new gdm, they rewrote it basically and have different dbus api, different codebase, etc
[18:04] <seb128> that's to define, it seems people don't agree on the way to go right now
[18:04] <seb128> the fedora guys are adding status api to gnome-session but there is already some software doing that job correctly
[18:05] <seb128> so it's not clear what will be used
[18:05] <chrisccoulson> yeah, it's a little messy at the moment. and the existing applet has some weaknesses (such as no policykit support. i actually work around this at home by patching the applet to just call the session dialog)
[18:05] <seb128> you can talk to tedg about it, he's the one who worked on the ubuntu changes and is following the upstream discussions
[18:10] <chrisccoulson> i've just noticed totem failed to build
[18:11] <chrisccoulson> i missed a Makefile.in from the autotools patch
[18:11] <seb128> did you test build it?
[18:11] <seb128> is that one of those cases where autotools get ran when installed which make you not notice build issues? ;-)
[18:12] <seb128> when using quilt you want to find . -name | xargs quilt add
[18:12] <chrisccoulson> i built it, but then made a last minute (what i thought was a minor) change before i submitted it
[18:12] <seb128> or use cdbs-edit-patch to update your changes
[18:13] <seb128> ok
[18:13] <seb128> I've to run now but I will have a look to it later if mvo is not quicker ;-)
[18:14] <chrisccoulson> that's really odd
[18:14] <chrisccoulson> its actually building at home
[18:15] <seb128> what I said
[18:15] <seb128> autotools get ran locally if installed
[18:15] <seb128> look to your build log
[18:15] <crevette> seb128: while you're still here, I have a question about nautilus-sendto for universe
[18:15] <crevette> I didn't had time to look at it
[18:16] <seb128> crevette: sure
[18:16] <chrisccoulson> yeah, i'll do that once it's finished. i'll prepare a fix for that though in the meantime
[18:16] <crevette> how can I do to just have the two *.so of the plugins, should I run a rm on all files I don't want
[18:16] <crevette> ?
[18:17] <seb128> crevette: either that or install to tmp and use a .install to move what you want to the deb
[18:18] <seb128> got to go
[18:18] <seb128> bbl
[22:54] <seb128> asac: you have some trivial sponsoring bugs waiting you should review those one day ;-)
[22:56] <asac> seb128: heh
[22:57] <asac> ;)
[22:57] <asac> anything particular you have in mind/spotted?
[22:57] <seb128> asac: I'm just looking through the sponsoring list
[22:57] <seb128> bug #295788
[22:57] <asac> yes. didnt i fix that long ago;)?
[22:57] <seb128> it's a one liner in a .desktop waiting for a month
[22:58] <seb128> dunno the bug is still listed
[22:58] <asac>   * fix LP: #268803 - Ubuntu Intrepid: Both Knetworkmanager and Network
[22:58] <asac>     Manager load on startup; fix xdg autostart .desktop file to
[22:58] <asac>     "OnlyShowIn=GNOME;XFCE;"
[22:58] <asac>     - add debian/patches/lp268803_xdg_autostart_gnome_xfce_only.patch
[22:58] <asac>     - update debian/patches/series
[22:58] <asac> thats from -- Alexander Sack<EMAIL_ADDRESS>Mon, 01 Dec 2008 14:05:51 +0100
[22:58] <asac> maybe they want SRU?
[22:58] <seb128> asac: that's not the autostart there but the menu item for the configuration dialog
[22:59] <asac> heh :)
[22:59] <seb128> asac: http://launchpadlibrarian.net/21173925/network-manager-applet_lp_295788.patch
[22:59] <seb128> asac: bug #283416 too
[22:59]  * asac should probably not work now ;)
[23:00] <seb128> asac: the debian maintainer says they have that option, either copy that or upload the patch or decide that still needs discussion and unsubscribe the sponsoring team there
[23:00] <asac> seb128: hey, i know how to process that ;)
[23:00] <seb128> asac: would be nice to clean the sponsoring list a bit so dholbach doesn't get depressed ;-)
[23:01] <seb128> it's over a screen for main right now
[23:01] <asac> true
[23:04] <huats> seb128: hey
[23:04] <seb128> lut huats
[23:04] <huats> I am finishing my last build of gnome-keyring right now
[23:04] <huats> ...
[23:04] <seb128> huats: ohh ;-)
[23:04] <huats> I have asked upstream for any opinion
[23:04] <seb128> huats: the upstream change is working?
[23:05] <huats> haven't tested yet
[23:05] <huats> (sorry)
[23:05] <huats> I will do another one after that one :)
[23:05] <huats> seb128: I have found that mandriva has included the ui files
[23:05] <huats> so I have added them too :)
[23:06] <seb128> ;-)
[23:06] <huats> (ok I know it is bad to look over his neighbour shoulder)
[23:21] <seb128> huats: open source is about sharing experience ;-)
[23:43] <cj> seb128: hey there
[23:44] <cj> seb128: I'm jhbuilding up so I can build a patch to put gtkglarea in gtk-shallow/gtk/gtkglarea.[ch]
[23:44] <cj> I'll go re-read your comments on the bug.  :)
[23:45] <seb128> ?
[23:45] <seb128> I don't think I know about any gtkglarea bug
[23:45] <seb128> I do comments on hundred of bugs every week so some context is usually useful
[23:45] <cj> bug 119189
[23:46] <cj> I thought for certain I saw your name on it somewhere...
[23:46] <seb128> not likely
[23:46] <seb128> that is a linux bug
[23:46] <seb128> I'm working on desktop packages usually
[23:46] <cj> no, sorry.  gnome bug 119189
[23:47] <cj> looks like your name is not on it, though
[23:47] <cj> ubottu: botsnack, but improve in the reading my mind area
[23:47] <seb128> no, and as said I don't know about gtkglarea
[23:48] <cj> well, then!  disregard :)
[23:48] <seb128> ;-)
[23:50] <seb128> enough work for today see you tomorrow
[23:50] <cj> sleep well!
[23:51] <pochu> good night seb128
[23:55] <seb128> huats: don't work too much I will not upload the update before tomorrow now ;-)
[23:57] <huats> sure
[23:57] <huats> I will finish it no
[23:57] <huats> w
[23:58] <seb128> huats: 'night


[08:32] <cloudy_nz> I had no idea this channel existed
[08:32] <lotuspsychje> cloudy_nz: :
[08:32] <lotuspsychje> :p
[08:32] <lotuspsychje> this is to chitchat about ubuntu
[08:33] <lotuspsychje> and nice to avoid crowdy offtopic
[08:33] <cloudy_nz> To Ubuntu, or not to Ubuntu, that is the question...
[08:33] <lotuspsychje> lol
[08:33] <lotuspsychje> to ubuntu of course
[08:34] <cloudy_nz> It's sad how people mock it as noobuntu
[08:35] <lotuspsychje> meaning?
[08:35] <lotuspsychje> keep on windows?
[08:35] <cloudy_nz> No, usually it's arch Linux snobs
[08:36] <lotuspsychje> well ubuntu is the most popular Os
[08:37] <cloudy_nz> Is it? Thought it was mint for linux
[08:37] <lotuspsychje> no, ubuntu has the most users


[02:07] <Xamusk> hello
[02:08] <Xamusk> is there a default page for the wiki's LaptopTestingTeam entries?
[02:18] <Xamusk> ok, I have already found it
[02:18] <Xamusk> thanks anyway
[08:56] <susscorfa> when i cant boot with the live cd, do i have change when i install with a alternate cd for having a working system (for a acer laptop)
[10:55] <KenSentMe> susscorfa: There's a good chance your installation with the alternate cd will work well


[00:32] -SwissBot:#ubuntu-news- ::OMG!Ubuntu:: Enlightenment 0.24.2 Released with Bug Fixes, Updated Terminal App @ https://www.omgubuntu.co.uk/2020/07/enlightenment-0-24-2-released-with-bug-fixes-updated-terminal-app (by Joey Sneddon)
[00:33] <guiverc> "He Starts"  (closer look at pinebook pro)  ... will mention in gdoc shortly
[00:35]  * Bashing-om waits :P
[00:38] <guiverc> a version/versions suggested change too
[00:39] <guiverc> I've finished Bashing-om , looks good, two comments made
[00:39] <Bashing-om> guiverc: noted.
[00:42] <Bashing-om> guiverc: Looking and fixing :P
[00:52] <Bashing-om> UWN: 2 additional ^ edits completed.
[00:54] <guiverc> looks great to me, thanks Bashing-om
[00:57] <Bashing-om> guiverc: We four and all others are in this together - takes all of us to do this :P
[00:59] <guiverc> :)
[01:02] -SwissBot:#ubuntu-news- ::OMG!Ubuntu:: Want to Improve Firefox Performance on Linux? Turn This Setting On @ https://www.omgubuntu.co.uk/2020/07/firefox-enable-webrender-linux (by Joey Sneddon)
[04:28] -SwissBot:#ubuntu-news- ::Planet:: David Tomaschik: Security 101: Backups & Protecting Backups @ https://systemoverlord.com/2020/07/26/security-101-backups-protecting-backups.html
[14:15] -SwissBot:#ubuntu-news- ::Softpedia:: Mozilla Firefox 79 Is Now Available for Download on Windows, Linux, Mac @ https://news.softpedia.com/news/mozilla-firefox-79-is-now-available-for-download-on-windows-linux-mac-530633.shtml (by Bogdan Popa)
[19:11] <Bashing-om> UWN: Pulling "WIP" - logs reflect no additional changes, Time to push 20:00GMT.
[20:00] <Bashing-om> UWN: ubuntu-news@lists is away - doing the Forum post next. :D
[20:09] <Bashing-om> UWN: Forum post done - had to abridge the updates sections. Going the re-directs next.
[20:21] <Bashing-om> UWN: re-directs completed - Pending is release to the social medias and the cleanup.
[20:28] <Wild_Man> Bashing-om, I will do these real quick then I have to pack life is busy
[20:30] <Bashing-om> Wild_Man: Good that you can focus attention here :P
[20:31] <Wild_Man> Bashing-om, it is hard I have so much going on wife is a sleep she has appoints tomorrow and I have to drive my son two hours away in the morning to have surgery then I have to drive to San Antonio tomorrow night
[20:33] <Bashing-om> Wild_Man: I can relate - As I too have to run my wife and duaghter across country. We do what we must :P
[20:38] <Wild_Man> Bashing-om, yes we do
[20:52] <Wild_Man> http://fridge.ubuntu.com/2020/07/27/ubuntu-weekly-newsletter-issue-641/
[21:02] <Bashing-om> Fridge: Wild_Man: looks good and spot check - checks :D
[21:13] -SwissBot:#ubuntu-news- ::Planet:: The Fridge: Ubuntu Weekly Newsletter Issue 641 @ http://fridge.ubuntu.com/2020/07/27/ubuntu-weekly-newsletter-issue-641/
[22:17] <Wild_Man> Thanks Bashing-om
[22:18] <Bashing-om> Wild_Man: Twitter - FaceBook ? Clear now to wipe Gdoc ?
[22:19] <Wild_Man> Bashing-om, yes all is done
[22:19] <guiverc> :)
[22:19]  * guiverc enters room after completing bird feed...
[22:20] <Bashing-om> guiverc: Concurr to wipe Gdoc ? All done ?
[22:20] <guiverc> yep
[22:20] <Bashing-om> I dewww eeett :P
[22:25] <Bashing-om> UWN: We do issue 642 :D