[12:41] <AlanBell> o/ dholbach
[12:41] <dholbach> hey AlanBell
[12:42] <AlanBell> dunno if you saw my little raspberry pi cluster project?
[12:42] <AlanBell> http://www.indiegogo.com/projects/a-raspberry-pi-build-cluster-for-ubuntu/x/5206923
[12:43] <AlanBell> we are planning to rebuild all the ubuntu source packages for the arm6 hf architecture
[12:43] <AlanBell> do you think I have to pick apart all the packages for trademark stuff?
[12:45] <dholbach> AlanBell, maybe it'd be worth bringing it up with infinity, doko and cjwatson?
[12:46] <AlanBell> ok, will do, thanks
[13:43] <cjohnston> mhall119: can you please work on bug #1243270
[13:43] <ubot2> Launchpad bug 1243270 in Summit "Cannot open summit due to different account" [Undecided,Confirmed] https://launchpad.net/bugs/1243270
[13:48] <jcastro> hey we start in 15 minutes right?
[13:51] <dholbach> jcastro, we do
[13:52] <jcastro> I picked a heck of a time to run out of caffeine!
[13:52] <dholbach> jcastro, #ubuntu-uds-plenary is not quite like #ubuntu-release-party yet, but people start showing up
[13:57] <chilicuil> anyone has all the uds channels in one place (for copying and pasting)
[14:32] <balloons> chilicuil, all of them?
[14:32] <balloons> chilicuil, I use #ubuntu-uds-plenary, #ubuntu-uds-community-1, #ubuntu-uds-community-2
[14:33] <chilicuil> balloons: cool, I think it will be enough =)
[14:46] <cjohnston> ouch.. calling jono out
[14:46] <jono> lol
[14:46] <jono> fair
[14:46] <jono> :-)
[14:57] <jcastro> jono, schedule says 9 mintue btw
[14:57] <jcastro> 5 after
[14:57] <jono> jcastro, ahhh ok
[14:57] <jono> jcastro, I am sure people can figure it out :-)
[14:57] <jcastro> after the metrosexual comment I feel like the floodgates have been opened
[14:58]  * popey gets tea
[17:45] <dholbach> dpm, are you going to be in community-2 now?
[17:45] <dholbach> balloons, community-1?
[17:45] <dholbach> then I'd do appdev-2
[17:45] <dpm> dholbach, yea
[17:45] <dpm> *yeah
[17:46] <dholbach> mhall119, appdev-1?
[17:46] <mhall119> yes
[17:46]  * mhall119 figures he'd have appdev-1 all day
[17:47] <dholbach> yeah, I'm jumping around between sessions/rooms a little bit
[17:48] <mhall119> summit could use some feature work to add a "Host" field for virtual meetings, and then a "Hosting Schedule" page for us who are doing it
[18:30] <iBelieve> Does anyone know if someone under 18 is allowed by Google to join the vUDS sessions? Nothing in the agreements I saw when clicking "I agree" said anything about it, but this post seems to say I can't: http://smartboyhwubuntu.wordpress.com/2013/08/27/google-please-let-me-join-vuds/
[18:32] <popey> iBelieve: Hangouts On Air are not available to under 18's on their own G+ account.
[18:32] <asomething> iBelieve, it looks like it is up to who starts the hangout https://support.google.com/plus/answer/1650353?hl=en
[18:33] <popey> https://support.google.com/plus/answer/2459411?hl=en
[18:33] <popey> "No, only users 18 years and over can participate in Hangouts On Air."
[18:33] <asomething> When I start a hangout, i see a checkbox with "Restrict minors from joining this video call"
[18:34] <asomething> popey, got it. it's different for the on air ones
[18:34] <popey> ya
[18:34] <iBelieve> popey: so I'm not allowed to join? That's really disappointing.
[18:35] <popey> yeah, bummer
[18:45] <dholbach> jono, can you run community-2 next?
[18:45] <dholbach> I'm going to be in appdev-2 and balloons will do community-1
[18:46] <jono> dholbach, I wanted to hit the app dev session
[18:46] <jono> who owns the roundtable session?
[18:46] <jono> I can set the link up for them
[18:46] <dholbach> jono, launchpad.net/~ove-risberg
[18:46] <popey> dholbach: are you doing appdev-2 next?
[18:46] <popey> the click package one?
[18:47] <dholbach> popey, yep, at least be part of it
[18:47] <dholbach> I'm happy to run it
[18:47] <popey> ok, magic.
[18:47] <jono> dholbach, ok, I will see if I can set up the enterprise session
[18:48] <dholbach> thanks
[18:52] <jono> dholbach, I can't get OveRisberg to respond
[18:52] <dholbach> urgh, hang on
[18:52] <dholbach> there was another guy
[18:52] <jono> I am going to join the appdev session and if anyone has an issue with the enterprise session we can try and fix it
[18:56] <dholbach> jono, I think 'ballock' (on IRC) also ran one of those sessions the last time
[18:56] <jono> dholbach, thanks
[19:05] <dpm> dholbach, jono, balloons, who's starting the Enterprise session on community-2 in the end? I'd like to join the app dev session, but I could start the enterprise one if noone else can
[19:06] <jono> dpm, can you?
[19:06] <dpm> ok, on it, then
[19:06] <jono> actually, you should bein the app dev sessions
[19:06] <jono> dpm, if no one volunteers to run the session, I guess it wont happen
[19:07] <dpm> jono, yeah, I'd prefer to be in appdev, but we can't leave the session not run
[19:09] <jono> dpm, I think you should join the HTML session
[19:09] <jono> ahh you are there :-)
[19:09] <dpm> :)
[19:42] <dholbach> bah, and it was the last session of the day - I was just getting warmed up!
[19:42] <dholbach> jono, ^ 24h UDSes next!
[19:42] <dholbach> no complaints about timezones
[19:42] <jono> lol
[19:43] <dholbach> everything squeezed in one day!
[19:43] <elfy> or having to work while you're all chatting ...
[19:43] <dholbach> all right, we wrapped up the store session a bit early
[19:44] <dholbach> have a great rest of your day and see you tomorrow! hugs!
[21:51] <bkerensa> jcastro: http://noshavingindecember.org/


[08:13] <cimi> tsdgeos, got dragged on a bricked vegeta last night :D
[08:15] <tsdgeos> k
[08:15] <cimi> tsdgeos, matthieu flashed a krillin image on a vegeta :D
[08:16] <cimi> tsdgeos, trying to recover now
[08:19] <cimi> hey tsdgeos, I don't understand some of your C++
[08:20] <cimi> tsdgeos, in the .cpp you comment out the args of your function like PreviewStack* Scope::preview(QVariant const& result, QString const& /*categoryId*/) but declare them in the header?
[08:20] <duflu> cimi: Then you still have your soul
[08:20] <duflu> Congrats!
[08:20] <cimi> duflu, lol, I am just not very good at C++ :P
[08:21]  * duflu was sure Cimi's name was on a lot of Unity source code
[08:21] <cimi> duflu, because unity had so many bugs? :D
[08:34] <tsdgeos> cimi: what's the question?
[08:34] <tsdgeos> cimi: is the question "why do you have categoryId at all"?
[08:34] <cimi> tsdgeos, why in the cpp the argument is under comment
[08:35] <cimi> tsdgeos, to avoid compile warnings?
[08:35] <tsdgeos> cimi: yes
[08:35] <cimi> tsdgeos, fair enough
[10:35] <cimi> tsdgeos, https://code.launchpad.net/~aacid/unity8/dash_activation_no_special_casing/+merge/264024
[10:38] <tsdgeos> tx
[10:42] <tsdgeos> cimi: it's two times we have the reset code, not three, but whatever, i'll make the function
[10:46] <tsdgeos> cimi: pushed the fixes
[10:47] <cimi> tsdgeos, yeah I realised
[10:59] <cimi> tsdgeos, is it possible that
[10:59] <cimi> 114	+        onPreviewRequested: { // (QVariant const& result)
[10:59] <cimi> 115	+            if (result [10:59] <cimi> tsdgeos, result is undefined and if is true?
[11:00] <cimi> tsdgeos, shall we protect against undefined?
[11:01] <tsdgeos> pstolowski: ↑↑↑
[11:01] <tsdgeos> if the lower layers do that it's a bug
[11:01] <tsdgeos> i don't think we out to try to make it invisible
[11:02] <tsdgeos> pstolowski: ↑↑↑↑
[11:03] <cimi> tsdgeos, with your code, we enter the if is result and maybePreviewResult are the same... so not sure we should check for null/undefined
[11:04] <cimi> in case weird weird things happen on the backend
[11:04] <tsdgeos> yes i know
[11:04] <tsdgeos> i understand whta you say
[11:04] <tsdgeos> if the backend is broken
[11:04] <tsdgeos> fix the backend
[11:06] <tsdgeos> cimi: but if you're going to block on this i can change the if to do whatever you want
[11:16] <cimi> tsdgeos, block on this? no
[11:16] <cimi> tsdgeos, it's a question, what shall we do?
[11:16] <tsdgeos> i mean i don't care that much
[11:16] <tsdgeos> honestly i think we should do nothing
[11:16] <tsdgeos> worst thing is
[11:16] <tsdgeos> if the backend is broken
[11:16] <pstolowski> tsdgeos, cimi not it's not possible, we internally use proper Result instances and only wrap them into variant before emiting the signal
[11:16] <tsdgeos> the user gets a empty preview
[11:17] <tsdgeos> he goes back, reports a bug, fixed :D
[11:17] <tsdgeos> and pstolowski says it can't really even happen
[11:22] <pstolowski> tsdgeos, i'm happy with this silo and haven't spotted any regressions. i can mark it ready when the MP is approved
[11:24] <tsdgeos> pstolowski: you'll have to rebuild since i did a minor change because of cimi's comments
[11:25]  * cimi feels guilty
[11:25] <pstolowski> tsdgeos, cimi ok, np
[11:26] <pstolowski> tsdgeos, and is it approved now?
[11:26] <cimi> pstolowski, very soon
[11:35] <pstolowski> cimi, shall i hold on with rebuilding to give you some more time to review?
[11:37] <tsdgeos> pstolowski: it's approved now
[11:37] <tsdgeos> pstolowski: retrigger the build!
[11:37] <pstolowski> thanks
[11:38] <tsdgeos> food
[12:31] <a1fa> http://i.imgur.com/O7K8KAo.png
[13:21] <greyback> a1fa: what is that showing us? a new terminal instance missing window decoration?
[13:26] <tsdgeos> cimi: come on top approve https://code.launchpad.net/~aacid/unity8/expandable_test_fixes/+merge/266875 and https://code.launchpad.net/~aacid/unity8/testExpandableHeights/+merge/266876 ! :D
[13:26] <tsdgeos> cimi: and if you have time https://code.launchpad.net/~aacid/unity8/more_autotests_dash/+merge/265401 needs reviewing too
[13:27] <a1fa> greyback: existing terminal that i focused to, and menu bar dissapeared
[13:30] <cimi> tsdgeos, forgot to top approve
[13:30] <cimi> tsdgeos, done
[13:31] <cimi> tsdgeos, still no idea why my checked branches have issues with tags, but running the command remotely works
[13:31] <cimi> maybe Saviq ?
[13:32] <greyback> a1fa: well that's something I've never seen. bregma does that look familiar? ^^
[13:32] <a1fa> http://i.imgur.com/O7K8KAo.png
[13:32] <tsdgeos> cimi: if he has time
[13:41] <bregma> a1fa, looks like a bug in the window decorations, you should probably file a bug https://bugs.launchpad.net/unity/+filebug
[14:10] <cimi> preview in order or autotest first?
[14:10] <cimi> ops he quit
[14:21] <cimi> tsdgeos, preview in order or autotest first?
[14:22] <tsdgeos> cimi: test first i'd say
[14:22] <cimi> ojk
[14:22] <tsdgeos> should be easier
[14:22] <tsdgeos> i hope :D
[16:09] <seb128> hey there
[16:09] <seb128>  when moving to another app on the phone, what's the state of bg apps?
[16:09] <seb128>  Qt.ApplicationInactive or Qt.ApplicationSuspended ?
[16:09] <seb128> unsure if that's a qt, sdk, qtmir, unity thing?
[16:23] <greyback> seb128: inactive I think
[16:23] <seb128> is that wanted?
[16:23] <seb128> see #sdk discussion
[16:24] <seb128> basically  http://doc.qt.io/qt-5/qml-qtqml-qt.html states
[16:24] <seb128> "Qt.ApplicationSuspended - The application is suspended and not visible
[16:24] <seb128> to the user. On mobile platforms, the application typically enters this
[16:24] <seb128> state when the user returns to the home screen or switches to another
[16:24] <seb128> application."
[16:58] <greyback> dandrader: one final nit with noQtSensors-lp1481389 reported, then is good to go
[17:00] <dandrader> greyback, done
[17:03] <greyback> nice, thanks
[19:27] <mterry> lp:unity8/overlay is ftbfs on an overlay phone because it's looking for unity-shell-application=5, but 6 is installed
[19:38] <dandrader> mterry, merge trunk?
[19:39] <mterry> dandrader, trunk being unity8/overlay?  I just branched it now
[19:39] <dandrader> mterry, lp:unity8
[19:39] <mterry> It hasn't changed since 8/1
[19:40] <mterry> dandrader, maybe I don't understand what the various series are used for
[19:40] <dandrader> anyway, I probably don't know what I'm saying. It
[19:40] <mterry> dandrader, I assumed trunk was wily, overlay was vivid+overlay
[19:40] <dandrader> It's the first time I hear about this overlay branch
[19:40] <mterry> https://code.launchpad.net/unity8/
[19:40] <mterry> I don't know what rtm-14.09 is still used for (it's more updated than overlay)
[19:41] <dandrader> don't ask me :)
[19:41] <mterry> :)
[19:41] <dandrader> I always use lp:unity8 and ignore those
[19:42] <mhall119> is ctrl+tab when running `make tryShell` going to be what alt+tab does in actual use?
[19:42] <dandrader> mzanetti would know but he's on leave
[19:42] <dandrader> (about the unity8 branches I mean(
[19:42] <dandrader> mhall119, I think so
[19:42] <mhall119> dandrader: cool, thanks it's looking good
[19:46] <greyback_> mterry: right now lp:unity8 is trunk for both vivid+overlay & wily
[19:47] <mterry> greyback_, really?  it requires libunity-api-dev (>= 7.98) which isn't in vivid+overlay
[19:50] <greyback_> mterry: hmm, I wonder if this is it blocked: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#unity-api
[19:51] <mterry> greyback_, ah ok.  thanks, I should have guessed it was gcc5 nonsense
[19:52] <greyback_> mterry: but I don't understand how a gcc5 thing could impact vivid+o
[19:52] <mterry> (how are people compiling unity8 then?)
[19:52] <greyback_> I've no idea
[19:52] <greyback_> something is wrong
[19:52] <mterry> greyback_, it's not...  I was trying to build for v+o and trying to find the right branch to build from.  lp:unity8 was suggested, but that is borked on gcc5
[19:53] <greyback_> none of our branches have a hard dependency on any gcc version
[19:53] <mterry> greyback_, well unity-api does when built against gcc5
[19:53] <greyback_> yeah, but that shouldn't happen on vivid+o
[19:53] <mterry> greyback_, right.  it's not
[19:54] <greyback_> I'm very confused right now :)
[19:54] <mterry> greyback_, but lp:unity8 does require the wily version of unity-api
[19:54] <mterry> greyback_, I'm just trying to build ANY branch of unity8 on v+o
[19:54] <mterry> greyback_, lp:overlay has a build problem of some sort
[19:54] <greyback_> mterry: yep, but unity-api *should* be released for both v +o& w, usually simultaneously
[19:55] <greyback_> mterry: I've never heard of that overlay branch, ever
[19:55] <mterry> greyback_, lp:u8/rtm-14.09 is NEWER than lp:u8/overlay for some reason (do we still use it?  I'm leery of trying to build it)
[19:55] <mterry> greyback_, OK.  So everyone is just using lp:u8.  got it
[19:55] <greyback_> mterry: that should be the case.
[19:55] <mterry> greyback_, it may be held back on v+o because it's held back on wily
[19:55] <mterry> But that leaves me with a problem building
[19:56] <greyback_> I would have thought unity8 could not migrate then
[19:56] <greyback_> if unity-api couldn't
[19:56] <mterry> greyback_, I'm not building from packaging.  I'm building from trunk
[19:56]  * mterry should try packaging I guess
[19:56] <mterry> older u8, but it will build
[19:56] <greyback_> my unity-api trunk has 7.98
[19:56] <mterry> greyback_, yup.  But I wasn't trying to recompile unity-api trunk
[19:57] <mterry> That might be a way around it too
[19:57] <greyback_> I know. I'm just surprised it has landed for wily, but not for v+o
[19:57] <mterry> greyback_, it hasn't landed in either I don't think
[19:57] <greyback_> ah you're right, it's proposed for wily
[19:58] <mterry> So I either recompile unity-api (and who knows what else) from trunk or just use the version of u8 that's in v+o archive (I'll do that)
[19:58] <mterry> greyback_, thanks for coming with me on this journey  :)
[19:59] <greyback_> unity-api 7.98 is in v+o
[20:00] <greyback_> but stuck in proposed for w
[20:00] <mhall119> mterry: greyback_: I compiled Unity 8 fine on vivid+overlay
[20:00] <mterry> mhall119, now you're just bragging  :)
[20:00] <mhall119> maybe --setup pulls the wily version of that package?
[20:00] <mterry> greyback_, what?!  hmm
[20:01] <greyback_> https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay/+packages?batch=75&memo=75&start=75
[20:01] <greyback_> I see it there
[20:01] <mterry> greyback_, it's not in an apt-cache policy
[20:02] <mterry>  *** 7.97+15.04.20150611-0ubuntu1 0
[20:02] <mterry>        1001 http://ppa.launchpad.net/ci-train-ppa-service/stable-snapshot/ubuntu/ vivid/main armhf Packages
[20:02] <mterry> greyback_, you're using stable-phone-overlay... I have stable-snapshot
[20:02] <mterry> I installed from ubuntu-touch/stable/ubuntu
[20:02] <mterry> I should probably do rc-proposed or some such...
[20:03] <greyback_> mterry: yeah, you're working off the last stable release, which does fall behing
[20:03] <greyback_> rc-proposed the usual channel I use
[20:03] <mterry> greyback_, yeah I didn't consider my need to build when I picked a channel
[20:03] <mterry> :(
[20:03] <mterry> greyback_, OK thanks, I'm sure that will sort me
[20:03] <mterry> thanks mhall119!
[20:03] <greyback_> oh well, tragedy averted :)
[20:04] <mhall119> greyback_: better luck next time :)
[20:04] <greyback_> :)
[20:27] <mhall119> is there a tag for bitesize bugs in unity8?
[20:27] <mhall119> ah,ignore me, I just didn't see it at first
[20:31] <mhall119> hmmm, they don't seem overly bitesized though
[22:27] <hehehehe> is there a way to compile unity without the launcher bar on ubuntu 14.04?


[07:19] <wayland> is anyone here having any problems with wayland?
[13:14] <lindol> hi all
[13:27] <JockeTF> Hellopaca, lindol.
[13:28] <lindol> JockeTF, haha long time no see :)
[13:28] <lindol> how are you? :)
[13:28] <lindol> Korea is very cold... =_=
[13:28] <JockeTF> I'm fine. :)
[13:29] <JockeTF> You?
[13:29] <lindol> haha Yes, I am cold
[13:31] <lindol> by the way..
[13:31] <lindol> I am thinkg about getting Macbook air 2015
[13:31] <lindol> Could i use Ubuntu GNOME on mac?
[13:35] <JockeTF> If you get Linux to run on it.
[13:47] <lindol>  haha


[08:33] <meena> turova: what do your logs say?
[12:50] <turova> meena it looks like it loads a network-config file from the mounted cloudinit drive that has correct values, but those never get to their destination
[12:52] <turova> it reads from /etc/cloud/cloud.cfg.d/50-curtin-networking.cfg, finds that it has no interfaces to rename (maybe because I already did that) and then just writes the blank config over
[13:28] <meena> iiiiiinteresting.
[13:41] <turova> it supposedly works with the premade proxmox OS templates, so I guess I'll just pull one of those down and see what the differences are when I have some time
[14:06] <meena> *nod *nod *nod
[14:06]  * meena has never worked with proxmox
[15:29] <otubo> Odd_Bloke: Hi! I've already signed the CLA, can you take a quick look at https://github.com/canonical/cloud-init/pull/70 whenever you have time? Should I update the branch?
[16:23] <robjo> no assigned reviewer yet for https://github.com/canonical/cloud-init/pull/162 can we please get some eyes on this? thanks
[16:24] <blackboxsw> robjo: I'll give first pass today
[16:24] <blackboxsw> thanks
[16:26] <meena> robjo: i have read your email to the list… and i like it.
[16:27] <meena> robjo: do you think you could outline what a refactoring would look like in my document?
[16:29] <robjo> meena: I think the step before such an outline is to get conceptual agreement, i.e. rharper blackboxsw, smoser and others would have to agree that this rather large change is the way forward w.r.t. network config writing
[16:29] <meena> robjo: i meant… in words.
[16:30] <robjo> Well it would basically the same as what I stated in e-mail. I thought about whether I wanted to comment in the doc or via e-mail and then decided to go with the e-mail approach
[16:33] <meena> robjo: aye.
[16:34] <meena> robjo: so, my main issue re writing network config is that right now, a lot of code for reading and *directly* manipulating (Ephemeral*) network only works on linux.
[16:34] <meena> so Goneri created a cool patch for FreeBSD, but it only works for DataSources that don't rely on the network.
[16:37] <robjo> I get that. The question for me becomes do we want to add another way of handling it on the side YOUR_FAVORITE_BSD rendereror are we better of to stick this stuff with the distro implementation
[16:38] <Goneri> yes, we should have a method in distros/freebsd.py to set-up a temporary network.
[16:38] <robjo> based on the way things look ATM I think there is a good argument to be made that the network config rendering belongs with the distribution implementation in some way, i.e. the distro implementation knows how it should render the network config rather than the network config is generic and considers distribution needs as a side effect
[16:40] <Goneri> on BSD, Yes. On Linux, it's different.
[16:40] <Goneri> this is the reason why the NetBSD and OpenBSD PR come with their own net renderer too.
[16:40] <robjo> The temporary network setup, while it works, is not linux generic either. It depends on the dhcp-client package which is no longer supported in SUSE
[16:41] <meena> i believe i did mention that somewhere…
[16:41] <meena> but it might have just  been IRC, so: lost in noise
[16:42] <Goneri> Naive question, I'm under the impression the Ephemeral network thing is just here to handle some corner-cases. Is it really the case?
[16:42] <robjo> A generic way for the temporary network setup is to have Python code in cloud-init that sends a basic dhcp4 and or dhcp6 request
[16:42] <robjo> smoser: was exploring that at som epoint
[16:43] <robjo> this would make the temporary network setup generic and should really be the first step
[16:50] <meena> i've looked at dhcp implementations in python at one point, and i didn't like what i saw.
[16:51] <meena> it would be cool if the OS had standard network library, which exposed dhcp that we could wrap in ctypes and call
[16:54] <Goneri> well, we should port NetworkManager on the BSD :-)
[16:55] <blackboxsw> otubo: thanks! I think you probably need to use util.del_file() https://github.com/canonical/cloud-init/pull/70/files#r365882842  and I just added a couple of minor nits in review as well.
[16:55] <blackboxsw> otubo: other than the nits, it looks good to go
[16:56] <blackboxsw> and we can merge that today when you get a chance to resolve or respond/reject comments.
[16:56] <meena> Goneri: when i suggested we port netplan, you were against it!
[16:59] <Goneri> I was joking in both cases, the real solution being systemd-networkd :-)
[17:26] <smoser> meena: python-scapy was the only thing that I thought could relaly get us there.
[18:21] <meena> smoser: scapy looks powerful… dangerously so.
[18:26] <smoser> meena: well.. doing a dhcp client really *should* be easy.
[18:26] <smoser> but, almost hilariously, all example dhcp clients in python assume there is already an ip address on the interface.
[18:27] <smoser> from memory... they do not use raw sockets and would need to to actually do a dhcp request on a nic that did not have an ip yet.
[18:29] <meena> soooooo, that's why it needs libpcap?
[20:11] <meena> okay, so, how do we get buy-in? i think maybe i'll be able to attend tomorrow's meeting and try to "sell" robjo's idea?
[20:19] <robjo> Well the ISC reference implementation for DHCP is Mozilla Public License 2.0 thus we cannot subsume it and wrap a Python interface around it. I am afraid if we are going to be independent of any external tool for the temporary network setup someone has to sit down and write the code in Python and send a PR
[20:20] <robjo> That would resolve the issue on *BSD for the temporary network setup, and would resolve the issue on SUSE w.r.t. depending on an unsupported package
[20:21] <robjo> After that the second step is to decide on the renderer approach
[20:21] <robjo> From my perspective there is buy in for step 1 already
[20:25] <rharper> replacing the EphemeralDHCP with a scapy (or something else) aka- cloud-init-dhclient is definitely something we're interested in; it allows us to drop the dhclient package from newer images, and sounds like it can be more portable to non-linux distros as well
[20:27] <rharper> for renderers and net module refactoring; I'm certainly on board with the goal of enhacing cross platform and cross distro support for the cloudinit.net module and additional renderers (and robjo distro variant support within a renderer class)
[20:47] <meena> i feel like a giant but should be coming out of rharper any second now
[21:01] <meena> gon… damn.


[01:45] <hads> That's interesting. I just did a reinstall on my oldest slave backend and somehow the tuner on my master backend got deleted.
[02:52] <mersault> hmmm... I selected to install the vnc service when installing my backend, but how do I enable and use it?
[03:08] <mersault> Does mythmusic work with storage groups, or is it still necessary to grab that off a local directory or NFS mount?
[03:08] <mersault> in 9.10, that is
[03:22] <hads> No mythmusic doens't
[03:46] <rcampbel> ubuntu 9.04 x64 clean reinstall. Moving to 0.22... added mythbuntu repo. installed most mythtv 0.22 pkgs. config incomplete. Now, I see upgraded mkgs available, but many of the want to remove existing pkgs - are there dep probs with the 0.22-fixes for jaunty?
[03:46] <hads> Why not go with Karmic?
[03:47] <tgm4883> rcampbel, hmm, which repo?
[03:48] <tgm4883> superm1, ping
[03:49] <tgm4883> hads, rcampbel looks like the PPA's are backed up
[03:49] <rcampbel> hads: because its my living room entertainment ctr, i.e. production host
[03:53] <tgm4883> rcampbel, I would hold off on upgrading for a few days. Looks like the PPA's are backed up from the release. It should all be sorted after a while
[03:53] <tgm4883> basically what happened is all the amd64 packages built, but we are still waiting on i386
[03:54] <rcampbel> I'm trying a new install on 0.22 on 9.04 from the PPAs on X64
[03:54] <rcampbel> not as smooth as in the past
[03:54] <tgm4883> and IIRC, mythtv-common is a arch independent package, thus built on the i386 servers
[03:54] <tgm4883> well, it's only not smooth, because the PPA's are so backed up
[03:54] <tgm4883> which is because they moved some servers for release
[03:55] <mersault> a new install of 9.10 is WAY smoother than a new install of 9.04 was
[03:55] <tgm4883> either way, don't upgrade from the mythbuntu-repos if you are on 64-bit for a few days
[03:56] <mersault> tgm4883: will that affect us 9.10 users as well?
[03:56] <tgm4883> mersault, yes
[03:57] <tgm4883> well, let me check, but probably
[03:57] <hads> If you were using Karmic then you don't need to bother with PPAs
[03:57] <tgm4883> looks like it is affecting karmic, jaunty, and intrepid
[03:57] <tgm4883> hads, not even for the latest mythtv builds?
[03:58] <tgm4883> hads, the PPA should contain newer packages than karmic has
[03:58] <hads> Yeah but nothing much has changed since 0.22.0+fixes22594 really.
[03:58] <hads> i.e. it works.
[03:59] <tgm4883> what about RC2?
[04:02] <hads> rc2 isn't in karmic but what I'm saying is that not a whole lot has changed. So a general user could just use karmic without issues.
[04:02] <mrand> I don't know... I'd prefer running the latest on the rc2 branch.  there are some bug fixes, with more to come still: http://svn.mythtv.org/trac/changeset?new=22679%40branches%2Frelease-0-22-fixes&old=22594%40branches%2Frelease-0-22-fixes
[04:04] <mrand> (that diff ignores a ton of documentation changes 2 days ago)
[04:04] <mrand> s/rc2/fixes
[04:04] <hads> That diff isn't much really.
[04:05] <hads> Theme fixes, and a couple of crashes that a general user may not ever run into.
[04:06] <mrand> You're correct, each is not huge - but at the same time, each is also important enough that they it was worth holding up the release even longer to make the changes.
[04:06] <mrand> the problem is that our user base is so large, some users WILL run into it.
[04:06] <hads> *shrug*
[04:06] <hads> Least it's installable.
[04:07] <mrand> Then we'll be stuck dealing with bug reports on things that have already been fixed.
[04:18] <Essobi> or it's for leopard
[04:20] <Essobi> Should I have to use AppleHDA patcher?
[04:26] <Essobi> Mmm.. doesn't look like it.
[04:44] <mersault> Just so I make sure, if I want jamu to be it's most effective then I should make sure all the tv shows I have have all the data in their filenames necessary to find them (title - 1x01 - subtitle.avi, for instance), because it doesn't look at the folder structure at all, correct?
[04:50] <Essobi> MEh... I've gotten no where.
[04:57] <Essobi> lol.. wrong window
[05:07] <styelz> hi, since upgrading to 9.10, i have an issue with audio sharing (i think). if i have Mythfrontend open i cant use any other app to access audio. is that normal?
[05:13] <mrand> styelz: see https://bugs.launchpad.net/bugs/460579 for potential work-arounds
[05:18] <styelz> wow, thanks mrand. worked
[05:27] <mrand> styelz: No problem.  Thank the users that found that work-around.  Hopefully 9.10 will have audio (finally) sorted out.
[05:44] <hads> 10.04?
[05:45] <mrand> indeed, hads.  thanks.
[12:50] <superm1> tgm4883, pong
[13:13] <oobe> ping
[17:17] <Ray1> hello, thanks in advance for any help...I have just upgraded to mythbuntu 9.10 and it is working great.  I noticed the mythweb streaming via flowplayer works great, with one exception.  Is there a way to skip around within the video?  If I try, it starts the video over at the begining
[17:20] <mrand> Ray1: I'm not 100% sure, but I seem to recall that seeking is not currently supported.
[17:44] <Ray1> thanks mrand, i will keep an eye out for news on this...is there a low-flow rss feed that annouces these sorts of things?
[17:49] <MythbuntuGuest60> I am trying to install Mythbuntu over Vista 64. I can't make a bootable Live CD.  I downloaded mythbuntu-9.10-desktop-amd64.iso and burned it to a CD, I tried extracting to a CD too. No joy. The PC ignores the cd and boots Vista. I made both boot drives the CD to force the issue and then I get a non system disk error.  What am I doing wrong?
[17:59] <superm1> running away after 4 minutes without an answer
[18:15] <mishehu> superm1: you weren't quick enough!  how dare you be busy with other things!  *grin*
[18:20] <superm1> hehe
[18:22] <duffrecords> I think I have some incorrect information in my mythconverg database.  I can watch a particular channel, but if I try to record it, this error is in the log: Could not find channel 9_1 in TVCT
[18:22] <duffrecords> the other channels are fine
[18:44] <MythbuntuGuest23> I submitted my question, I don't understand how this chat works to return an answer (then I guess I won't get this one either)
[18:49] <mrand> MythbuntuGuest23: there are (sometimes) other people in this channel that might know the answer to your question and will answer it.
[18:49] <mrand> Other times, either no-one is near their computer, or they don't know the answer.
[18:50] <mrand> As for your CD, are you trying to install Mythbuntu within a Windows NTFS partition?
[18:55] <MythbuntuGuest23> Yes
[18:56] <mrand> If you put the CD in the drive after Windows has booted up, and you open an explorer window to "my computer", you should see all your drives, including the CD drive.  What happens when you double click the drive there?
[18:57] <superm1> https://help.ubuntu.com/community/BurningIsoHowto would be useful
[18:57] <superm1> pending your response, it sounds like you just might have been burning incorrectly
[18:58] <MythbuntuGuest23> I get a list of folders and files including Wubi.exe
[18:58] <superm1> what tool were you using to burn?  the boot sector of the image won't get properly added if you just "extract" to the DVD
[18:59] <MythbuntuGuest23> I used the windows tool and just told it to extract to the CD.
[18:59] <superm1> Yeah, that won't work
[18:59] <superm1> follow that link i posted above, and it will explain to you a couple of ways to do it from windows
[19:00] <superm1> if you have a spare USB stick w/ at least 1 gig free, it's also got directions on how to do it from a USB stick
[19:01] <MythbuntuGuest23> Great, thanks, My USB stick is too small for that.
[20:42] <williammanda> The screen saver stays enabled during the use of mythtv videos & recordings. My frontend log says that DPMS is disabled. Also I installed ubuntu 9.10 then mythtv via the mythtv control center. This is the first time for this problem over several mythtv versions. Any ideas?
[20:43] <williammanda> Also the problem is occuring on two computers in my mythtv network.
[21:04] <MythbuntuGuest60> need help, I'm adding a 2nd hard drive to my mythbuntu 8.04 with .21 svn updates, and I want to put videos into it so mythvideo will show both locations, I have read lvm is an option, what is my simplest option to do this
[21:05] <hads> The easyest way would be just using the two drives separately.
[21:06] <hads> In the mythtv settings just add the paths like so; /mnt/videos:/mnt/new-drive
[21:06] <hads> Hmm, easiest.
[21:19] <MythbuntuGuest60> cool, thanks
[21:20] <MythbuntuGuest60> will doing it by adding one path on 1 hard drive, the other on #2 hard drive, and when i go to the video page, it will show videos in both paths?  Does this also work for mythtv files?
[21:21] <hads> No for recordings you use storage groups
[21:23] <MythbuntuGuest60> ok, so Storage groups when I start using mythtv for recordings, and this method for videos.  My blu-ray's are filling my drive, but I want to keep it, so I'm just adding another TB tonight, thanks.
[21:23] <hads> When using 0.22 you would use storage groups for both
[21:24] <MythbuntuGuest60> i'll have to check, i had to do the vdpau updates, I thought it was .21, maybe it is .22
[21:24] <hads> If you're using 8.04 it will be 0.21
[21:24] <MythbuntuGuest60> is there a link on setting up storage groups?
[21:24] <MythbuntuGuest60> ok, so I do have .21 then, thx
[21:25] <MythbuntuGuest60> do you know if current myth updates support HD-DTS soudn?
[21:25] <hads> Storage Groups page on the mythtv wiki should tell you
[21:25] <hads> I magine so
[21:26] <MythbuntuGuest60> i haven't seen it in any supported lists yet, so i have to strip the sound down to dts to make it work
[21:32] <MythbuntuGuest60> Anbody know how to make HD-DTS sound from a ripped blu-ray show up with 8.04 and .21 svn updates, all else is well and stripping sound down works fine
[21:36] <hads> Maybe it doesn't
[21:37] <MythbuntuGuest60> i use the mythfrontend player, "i think", but i'm wondering if ffmpeg or mplayer has fixed this, as the problem seems to be ffmpeg can't see it, it is a known issue, just not sure if it is resolved
[22:39] <superm1> williammanda, there is an open bug on that
[22:39] <superm1> it's a bug in gnome-screensaver
[22:39] <superm1> it's not properly responding to --poke
[23:20] <hads> Odd that I'm not running into it with the frontend that's using gnome here.


[16:52] -SwissBot:#ubuntu-news- ::Softpedia:: Debian GNU/Linux 9.9 Released with over 120 Bug Fixes and Security Updates @ https://news.softpedia.com/news/debian-gnu-linux-9-9-released-with-over-120-bug-fixes-and-security-updates-525803.shtml (by Marius Nestor)
[19:45] -SwissBot:#ubuntu-news- ::Softpedia:: Parrot Security 4.6 Ethical Hacking OS Officially Released, Here's What's New @ https://news.softpedia.com/news/parrot-security-4-6-ethical-hacking-os-officially-released-here-s-what-s-new-525805.shtml (by Marius Nestor)
[20:07] -SwissBot:#ubuntu-news- ::Softpedia:: Debian GNU/Linux 9.9 "Stretch" Live & Installable ISOs Now Available to Download @ https://news.softpedia.com/news/debian-gnu-linux-9-9-stretch-live-installable-isos-now-available-to-download-525806.shtml (by Marius Nestor)


[00:24] <koukou> iam having trouble installing audacity can anybody help
[00:33] <koukou> hi do i have to install ubuntu software center
[11:50] <xc_> hi, can I change how ubuntu mate runs cli applications such as gcc?
[11:50] <xc_> they currently open in xterm and I want them to use mate terminal instead
[12:13] <Astro7467> xc_: check the control centre
[12:14] <Astro7467> there is a default apps control and one is for the terminal
[12:16] <xc_> tried that, but when I run a launcher made from "Create Launcher" option in the context menu it still opens in xterm
[12:19] <Astro7467> @ terminal ;
[12:19] <Astro7467> sudo update-alternatives --config x-terminal-emulator
[12:20] <xc_> . /usr/bin/mate-terminal.wrapper is selected there
[12:21] <xc_> still no luck
[12:22] <Astro7467> either the file extension has been explicitly set to use xterm, so a left click.. Open with on the file in caja will let you change
[12:25] <xc_> ok i'll try that
[12:26] <Astro7467> alternatively edit the launcher properties to run "mate-terminal -e <origfile>"
[12:26] <Astro7467> not at a machine to explore further
[12:27] <xc_> thanks
[13:20] <finexbeer> is the Pentium p6100 good for programing
[13:37] <finexbeer> hi
[13:47] <lothar_> hier ist ja was los ...
[13:52] <finexbeer> hi
[13:54] <finexbeer> can you help me
[16:01] <ubuntu-mate> Hello
[16:01] <ubuntu-mate> Just trying the live CD
[17:02] <_pepe> hey everyone, I'm having issues with last week's update, I get a freeze at login. One thing I notice is that linux-image-generic is a different version number (4.4.0-64.68) than linux-image-extra and linux-image-4.4.0-64 generic (4.4.0-64.85). Does this cause an issue or require a package to translate?
[17:50] <edseville> hi mate-fans (supose you are) ... I just installed mate on rasberry pi3 and I need to resize the root (got 66MB on a 64GB sd !!!) ..
[17:51] <edseville> this seems somehow criptic to me: Re-size file system
[17:51] <edseville> Since Ubuntu MATE 16.04.2 the root parition is automatically resized, to fully utilise the all available space on the microSD card, on first boot.
[17:52] <Akuli> well, first of all you can't resize a partition while you have booted from it
[17:54] <edseville> well I thougt that also but read this also criptic entrance at : https://www.raspberrypi.org/forums/viewtopic.php?f=91&t=138968 from  Wazburi » Fri Mar 11, 2016 10:38 pm
[17:56] <edseville> seems interesting but if the information at http://ubuntu-mate.org/raspberry-pi/ is correct (I pastet it above) then that should be obsolete and I should not have any problems I have
[18:00] <Akuli> to be honest i don't know
[18:00] <Akuli> i don't have a raspberry pi
[18:09] <edseville> never mind, maybe someone knows and tells me ...      ;-)
[18:09] <edseville> thanks anyway
[18:10] <Akuli> yes, it's good idea to be patient and wait
[18:10] <Akuli> people often come up with a solution after 10 minutes or so :)
[18:12] <edseville> I know ... using ubuntu since I threw windows awy since more than 10 years ...
[18:14] <edseville> Akuli: do you know if there is a special chanel for the rasberry Mate ???
[18:15] <Akuli> i don't think so
[18:15] <Akuli> you'll probably find a raspberry pi channel though
[20:35] <tim> sapper


[14:29] <hank> hello, I noticed a new timestamp format in the focal OVAL feed, is that on purpose?
[14:30] <hank> it's usually `YYYY-MM-DD time`, this one is `YYYY-MM-DD time ??`
[14:30] <hank> the one I ran into is `PT`, which is odd because that's not a specific timezone
[15:19] <sbeattie> hank: hrm, can you point to where you see that?
[15:22] <sbeattie> oh containerd
[15:25] <mdeslaur> sbeattie: oh, does it not understand "PT"?
[15:26] <sbeattie> it's either PDT or PST, there is no PT.
[15:26] <mdeslaur> d'oh
[15:26] <sbeattie> I converted it to UST
[15:26] <hank> USN-5012-1
[15:27] <sbeattie> hank: I've fixed it in our tracker, the OVAL feed should pick it up in the next couple of hours. Thanks for pointing it out!
[15:31] <mdeslaur> sbeattie: thanks
[15:31] <hank> thanks!
[16:24] <TJ-> There may be a problem with th recent systemd 20.04 udate
[16:25] <TJ-> user in #ubuntu is reporting several server installs that have done unattended-upgrades have systemd-resolved spinning at 100% CPU and no name resolution
[16:27] <TJ-> user gave this info showing resolved timeout exceeded on the restart after installing the modified config file https://pastebin.com/mJh5N6HN
[16:27] <Guest80> Context: I received a report for some stale nodes (nodes that have not checked in to a central service) and upon investigation they stopped resolving hostnames right after some unattended upgrades. dpkg log for those upgrades: https://pastebin.com/mJh5N6HN
[16:29] <Guest80> A system reboot seems to clear it up, but some of these servers run data services, so I am also trying to find a way to prevent that. I've seen it happen in GCP and AWS.
[16:29] <TJ-> Guest80: from an affected system can you show us "pastebinit <( journalctl -u systemd-resolved --since="2 days ago" )"
[16:30] <Guest80> Failed to contact the server: <urlopen error [Errno -3] Temporary failure in name resolution>
[16:30] <Guest80> I'll create a pastebin manually
[16:30] <TJ-> ahhh
[16:31] <TJ-> Guest80: from an affected system can you show us "journalctl -u systemd-resolved --since="2 days ago" > /tmp/resolved.log" :)
[16:31] <TJ-> apologies for raw copy/edit/paste!
[16:31] <Guest80> No worries, thanks for looking at this
[16:31] <Guest80> https://pastebin.com/eF1wD2Lv ... there isn't a lot there
[16:32] <Guest80> I truncated it, as the restart loop continued
[16:33] <Guest80> I am going to sample some more nodes to see if they had the upgrades but are still able to resolve...
[16:36] <TJ-> Guest80: could it be this? Bug #1934221
[16:36] <TJ-> possibly not since that seems to be for 21.04 but... mentions resolved :)
[16:39] <TJ-> Guest80: the fact it is repeatedly timing out trying to start the service is clear enough
[16:41] <Guest80> Aye
[16:42] <TJ-> that patch is applied to the focal git repo but doesn't look like it has been published... and as it is a /fix/ for a fault, it could be at least related to your issue
[16:43] <Guest80> Yeah, interestingly starting /lib/systemd/systemd-resolved works when I do it via console, and systems start functioning.
[16:43] <TJ-> that is /weird/ !
[16:43] <Guest80> but the service is still stuck in the startup loop
[16:43] <TJ-> so, what is in the unit ("systemctl cat systemd-resolved"
[16:43] <mdeslaur> we've had other reports of similar issues, but we've been unable to reproduce so far
[16:44] <mdeslaur> Guest80: is that on a cloud provider? are you running k8s?
[16:44] <Guest80> We don't run k8s and I'm seeing it in both GCP and AWS
[16:46] <TJ-> Guest80: here's how to gather more debug info. Kill any systemd-resolved process that is running, and ensure the unit is stopped (even if marked failed)
[16:47] <Guest80> Ok, stopped.
[16:47] <TJ-> Guest80: then enable debug-level logging with "sudo kill -SIGRTMIN+22 1" (see "man systemd" and SIGRTMIN+22 - this puts the systemd services into log_level=debug". Then "systemctl start systemd-resolved" then collect logs "journalctl -b 0 --since "2 minutes ago" ") this will capture any related log info, not just resolved's, to correlate cause and effect
[16:49] <Guest80> Failed to umount /run/systemd/unit-root/dev: Device or resource busy
[16:51] <Guest80> There is a lot going on in the journal for systemd-resolved but it seems like it might be part of systemd itself
[16:52] <TJ-> Are you doing anything 'interesting' with namespaces?
[16:53] <TJ-> Guest80: yes; that signal enabled debug for all systemd components
[16:54] <Guest80> I don't understand the question, so probably not :)
[16:54] <TJ-> /run/systemd/unt-root/ is used as a temporary mountpoint in different namespaces for mounts before they're put in their final location. That error suggests the /dev/ (devtmps ?) is still active because something has a handle on it
[16:54] <Guest80> there are tons of snap.rootfs directories in /tmp
[16:55] <Guest80> ls /tmp/ | grep snap | wc -l
[16:55] <Guest80> 6087
[16:55] <Guest80> That seems odd to me
[16:55]  * TJ- blinks
[16:56] <TJ-> do they have understandable names as in /tmp/snap.<someappname>
[16:56] <Guest80> They are all snap.rootfs_83S1KD
[16:56] <Guest80> ish
[16:56] <Guest80> we don't use any snaps that are not baked in
[16:56] <Guest80> I think lxd or something might be there
[16:57] <TJ-> hmmm, this /may/ not be related to resolved but it feels suspicious
[16:57] <Guest80> well, in the logs for journalctl there was a ton of activity around those before resolved failed, so yeah, could be a red herring
[16:57] <TJ-> do you have LXD containers configured as well?
[16:58] <Guest80> I think that AWS has their ssm-agent running in a container; let me look
[16:58] <TJ-> since LXD is itself a snap nowadays, those may be related to LXD containers
[16:58] <TJ-> "lxc list" - but hope you don't see 6087 containers!
[16:59] <Guest80> Interesting
[16:59] <Guest80> cannot perform operation: mount --rbind /var/log /tmp/snap.rootfs_MlEUCG//var/log: Permission denied
[17:00] <Guest80> I didn't see any containers
[17:00] <TJ-> my feeling is that this is a resource exhaustion related issue, but without seeing the detailed log it is hard to make a better guess. Are you able to share the log when SIGRTMIN+22 was invoked?
[17:01] <Guest80> let me do that... and I agree.
[17:01] <Guest80> root cause is probably an error on our part with how we setup /var/log
[17:02] <TJ-> but it shouldn't fail mysteriously!
[17:02] <TJ-> i've been giving systemd a good kicking recently over a similar lack-of-info issue with networkd/udevd !
[17:02] <mdeslaur> I'm curious, are you setting up /var/log in a special way?
[17:03] <Guest80> Yeah, we attach it to local storage (ephemeral drives) when we detect those, so I think something might be there.
[17:04] <Guest80> incoming logs
[17:07] <Guest8036> Oops, got disconnected: https://pastebin.com/eF1wD2Lv
[17:08] <Guest8036> sorry, wrong paste, it's barking because the file is too large, 1m
[17:08] <TJ-> ha! I thought someone was flying between Starlink and me!
[17:09] <TJ-> ouch :)
[17:11] <Guest80> Ok, well I had to pare it down a bit
[17:11] <Guest80> https://pastebin.com/WuPj5VKf
[17:12] <Guest80> but there were thousands of remount messages about rootfs in tmp
[17:16] <Guest80> I'm going to try something
[17:21] <TJ-> Read most of it now and it is making sense. I think I can do an experimental reproducer here
[17:22] <TJ-> oh, and I should have told you, to cancel the debug logging "kill -SIGRTMIN+23 1"
[17:24] <Guest80> Oh thanks, I ended up rebooting that node. On another node I am manually unmounting and removing all those rootfs directories to see if I can reduce the noise there and assert if that has an impact here
[17:30] <TJ-> there's a workaround that may help in the interim - extend the timeout. "systemctl edit systemd-resolved" will create a drop-in override file. That command will open a text editor with an empty file. Add to it these lines and save "[Service]"  and  "TimeoutStartSec=500"
[17:31] <Guest80> Active: active (running) since Wed 2021-07-21 17:30:13 UTC; 42s ago
[17:31] <TJ-> I /think/ that may give enough rope for the service to start... it isn't far off when the system supervisor kills it because it has expired the default timeout
[17:31] <Guest80> Yep, yeah, unmounting and removing all those rootfs directories caused it to start
[17:31] <TJ-> but are all the affected nodes seeing the same mass of mounts?
[17:32] <Guest80> Yes, they are... so now I am moving onto that problem ;)
[17:32] <Guest80> by the way, thank you
[17:34] <Guest80> lxc list
[17:34] <Guest80> cannot perform operation: mount --rbind /var/log /tmp/snap.rootfs_I0jKoM//var/log: Permission denied
[17:34] <TJ-> I can understand why this is happening. My bet is at reboot this isn't an issue. But, due to masses of (failed) container mounts, any restart of systemd-resolved  - and likely other services - will hit this
[17:34] <Guest80> Yep, agree. The reboot is not a permanent fix
[17:34] <Guest80> so when I run that lxc command, that rootfs directory just stays in the /tmp directory
[17:35] <TJ-> is that recursive mount related to the ssm-agent you referred to earlier
[17:35] <TJ-> I've lost some connectivity here for some reason; most annoyingly web search (duckduckgo) and githubassets!
[17:37] <TJ-> looks like DDG in Ireland (msn network) is having a lay-down
[17:37] <Guest80> I'm not entirely sure if it's responsible, but /var/log is actually a symbolic link to another directory on another device.
[17:38] <Guest80> lrwxrwxrwx 1 root syslog 18 May  5 06:44 /var/log -> /mnt/ephemeral/log
[17:39] <TJ-> it could be since LXD being a snap, although privileged, may have some restrictions that prevent it accessing /mnt/
[17:39] <TJ-> possibly an apparmor profile for example
[17:39] <Guest80> ok, that is good stuff, let me look at that.
[17:40] <mdeslaur> Wow, this is interesting, nice debugging
[17:41] <Guest80> I'm not very familiar with apparmor, but I do see files related to snap-confine. I'll try the easy mode permissions first.
[17:45] <TJ-> Looking at the snap apparmor profile I see a couple of bits of interest
[17:45] <TJ-> mount options=(rw rbind) /var/log/ -> /tmp/snap.rootfs_*/var/log/,
[17:45] <Guest80> I'm seeing that too
[17:46] <TJ-> and, disproving my hypothesis about /mnt/ mount options=(rw rbind) /mnt/ -> /tmp/snap.rootfs_*/mnt/,
[17:46] <TJ-> but, this is the snap daemon itself; not clear what is applied for the LXD snap at present
[17:48] <Guest80> when I modify that line and restart snapd/apparmor and then run lxc again, it still has the old line
[17:51] <TJ-> if I recall correctly, it's stop, edit, start
[17:52] <Guest80> would that be fore apparmor?
[17:54] <TJ-> I think so ... a while since I had to wrestle with it.
[17:54] <Guest80> I'll do some research and see if I can get that error to go away
[17:57] <TJ-> I think the snapd apparmor profile is a red-herring - not implicated. Wht may be is any restrictions on LXD... but cannot get to the LXD source on github right now to chek
[18:00] <Guest80> https://askubuntu.com/questions/1222627/cannot-open-snap-apps-cannot-perform-operation-mount-rbind-dev-tmp-snap sounds oddly familiar
[18:05] <TJ-> found the apparmor lxd profile /var/lib/snapd/apparmor/profiles/
[18:08] <Guest80> I'll check that out
[18:08] <Guest80> So after running this: unlink /var/log && mkdir /var/log && mount --bind /mnt/ephemeral/log /var/log
[18:08] <Guest80> lxc commands didn't bark at me
[18:09] <Guest80> And I don't see dangling snap.rootfs mounts/folders in /tmp
[18:14] <Guest80> I don't really understand all the layers there, is it the lxc profile, lxd profile, snap profile? All of the above? Is the symlink the problem or is it permissions? If it's permissions it seems like we should be able to drop a file somewhere and /mnt/ephemeral would be available.
[18:20] <TJ-> the various snap.lxd* profiles (all basically the same) - I don't see anything obvious in them /except/ no mention of access to /mnt/ whereas snapd itself does - ommission may be issue here when following a symlink to /mnt/ - all those /tmp/rootfs_* are, I suspect, a bug in lxc when it cannot finalise mounts for a container and is retrying without cleaning up the previous attempt. May be
[18:20] <TJ-> worth checking for issues on the lxd project issue tracker on github
[18:21] <Guest80> I agree. I'm testing a few rules to give it access, but It does seem to be a resource leak bug as well.
[18:21] <Guest80> I'll create an issue there
[18:24] <TJ-> may be worth talking to  Stéphane Graber or other devs in #lxcontainers
[18:24] <TJ-> oh, it's #lxc now!
[18:25] <TJ-> going to dinner now - I'll keep a watch on the channels
[18:28] <Guest80> TJ- thank you for you help here. Enjoy your evening.
[18:29] <Guest80> https://github.com/lxc/lxd/issues/9029 hopefully this isn't noise for them
[19:12] <TJ-> Guest80: glad to see SG confirming it looks like a snap issue
[19:15] <Guest80> Yeah, I almost have a patch for us... only several hundred nodes to target ;)
[19:15] <Guest80> Thanks again for the help
[19:15] <TJ-> oooph!


[09:27] <rmg51> Morning
[10:45] <ChinnoDog> morning
[10:46] <JonathanS> How's it going?
[12:08] <teddy-dbear> Morning peoples, dogs, turkeys, hamsters and everything else
[14:13]  * ChinnoDog sips his tea
[15:48] <ChinnoDog> I can not stop eating M&Ms from the dispenser at work.


[00:02] <mirespace> LocutusOfBorg: :( I got that with ubuntu2, for that reason I put the build depends in ubuntu3... I'll double check as the testing with that was ok for mantic... but I hope with your fix it would be ok, then
[04:13] <vorlon> tsimonq2: against git-ubuntu> heh, I hadn't noticed. thanks
[17:08] <tsimonq2> vorlon: against git-ubuntu> Of course, thanks for bringing it to my attention :)
[17:52] <tsimonq2> Someone just sent patch mail to ubuntu-motu, nice. :P


[04:48] <airtondeejay> oi
[04:49] <cfhowlett> airtondeejay, greetings
[04:50] <airtondeejay> qual o programa para fazer cd mixados ?
[04:50] <cfhowlett> !english|airtondeejay,
[04:50] <cfhowlett> !audacity
[04:51] <airtondeejay> tipo Acid Pro(sony)
[04:52] <airtondeejay> tem canal de video aula do ubuntu studio
[04:52] <airtondeejay> quero usar só ele agora mais não sei nada
[04:52] <cfhowlett> e n g l i s h
[04:53] <cfhowlett> !pr
[04:53] <cfhowlett> !br
[04:54] <airtondeejay> o audacity
[04:56] <XRS1> ardour or openshot maybe
[04:57] <al4nc4ds> lmms
[04:58] <al4nc4ds> hydrogen
[04:58] <al4nc4ds> ¨)
[04:59] <airtondeejay> oi ok
[10:32] <guest-Xm3YWV> äghh,h,lh,.h
[10:32] <guest-Xm3YWV> 'uh,yg,ltg
[10:32] <guest-Xm3YWV> tgltlgööäg.hl.jhlhk,olli.9nlbh,ouhhnn.
[10:36]  * cfhowlett thinks "what the deuce?"
[16:18] <wip> hi guys, i need a favor, like 1 minute to test a stream on linux with your configuration: http://pdpatchrepo.info <- do you see a video?
[16:19] <wip> you can also play with the knobs to interact with the stream
[18:20] <iUnify> hey guys can someone help me for 2 seconds pls?
[18:22] <iUnify> I have never had this issue before.  I'm exporting a track in audacity i just finished, the export comes out in like quad-time and than is static.  Only change I made to my PC since last nights last successful export was to install jack.  But, I just said, "sudo apt-get install jack" which is not the same qtljackctl so IDK f that had anything to do with it - did a remove/restart, same issue.   it plays FINE before export and this
[18:26] <OvenWerks> iUnify: jack and jackd are two different packages
[18:26] <iUnify> mm I realize now.
[18:27] <OvenWerks> Jack is a cd ripper
[18:27] <iUnify> ah
[18:27] <iUnify> so that didnt effect this
[18:27] <iUnify> Last night I exported a song fine
[18:27] <OvenWerks> I wouldn't think.
[18:27] <iUnify> Now its coming out very messy.
[18:27] <iUnify> I have no idea why this would be occuring suddenly or how to even begin to think of fixing it.
[18:29] <OvenWerks> Inwonder if installing jack changed one of the encoding tools (removing one and adding another)
[18:30] <iUnify> what could the fix be?
[18:30] <OvenWerks> How are you exporting it? Mp3? ogg? something else?
[18:30] <iUnify> If that were the case, it seems probable.
[18:30] <iUnify> mp3
[18:30] <iUnify> always
[18:32] <OvenWerks> I'm not on a machine where I can check much right now... doing iso testing
[18:32] <iUnify> ah
[18:32] <iUnify> Well, I appreciate the effort anyways, would uninstalling/installing audacity do the trick possibly?
[18:34] <OvenWerks> might,
[18:36] <iUnify> ...ok.... wish me luck!  :/
[18:36] <iUnify> lol hope your work goes smooth as well :) thanks man, later.
[18:36] <OvenWerks> Opps gone...
[21:00] <xfrmrs> anyone have experience in setting up live video server in precise ubuntustudio?
[21:01] <XRS1> only with RTMP or VLC
[21:02] <XRS1> VLC is a good way to go (not sure what your trying to do)
[21:02] <xfrmrs> have installed VLC, now what?  :_)
[21:03] <xfrmrs> i have a web app to which I want to stream live video from, say, a camcorder (specifically not using "webcam", but a high end video camera).
[21:05] <XRS1> https://wiki.videolan.org/Documentation:Streaming_HowTo/
[21:05] <xfrmrs> the web app is serverd locally
[21:05] <xfrmrs> thx, i'll check it out.
[23:41] <ubuntu-studio> hi folks. trying to install the new US 10 beta on my machine and grub fails. I'm just updating the live DVD then I'm going to retry the install. Should that work? or can't the beta be installed? cheers
[23:41] <ubuntu-studio> sb 13 not 10 sorry..
[23:49] <sirriffsalot> ubuntu-studio: did you do an md5check?
[23:49] <sirriffsalot> ubuntu-studio: md5sum*
[23:49] <sirriffsalot> ubuntu-studio: slightly intoxicated, sorry
[23:51] <XRS1> most problems i've encountered with installing studio were from slightly corrupted .ISO files or failing hard drives. corruption is common when torrenting files so it's always a good idea to force check the torrent once it's complete.
[23:52] <sirriffsalot> ubuntu-studio: in other words, [code] md5sum /path/to/.iso [code]
[23:56] <sirriffsalot> ubuntu-studio: if a good .iso file (good meaning identical md5sum serials) isn't working either, and you have a flash drive available, try making a bootable usb instead and see if that install works
[23:57] <XRS1> much faster to install from USB anyway
[23:58] <sirriffsalot> XRS1: what makes you say that?
[23:58] <ubuntu-studio> sirriffsalot,XRS1: thanks guys...will get there. like the new look of US btw.  how do I install a tool chain, or does it have one now?
[23:58] <XRS1> last few times i've installed from DVD, it took almost as long to boot the CD as it would to install from USB
[23:58] <sirriffsalot> XRS1: not sure what a tool chain is to be honest..
[23:59] <ubuntu-studio> sirriffsalot: build environment ;)
[23:59] <ubuntu-studio> i use git and svn a lot :)
[23:59] <sirriffsalot> ubuntu-studio: I'm surprised I gave you advice on installing lol :)
[23:59] <XRS1> you dont need anything special. just use unetbootin or linux live USB installer
[23:59] <ubuntu-studio>  tool chain to build from git is what I need sorry


[05:02] <hikiko> hi
[05:29] <didrocks> good morning
[05:53] <pitti> bonjour didrocks !
[05:54] <didrocks> hey pitti, ça va ?
[05:54] <pitti> ça va bien, et toi ?
[05:54] <didrocks> maintenant que je peux reconstruire mes paquets, oui :)
[05:56] <pitti> :)
[06:05] <desrt> good morning, desktop!
[06:05] <pitti> hey desrt, how are you?
[06:05] <desrt> pretty good
[06:06] <didrocks> hey desrt, quite early for you, even in EST time! :)
[06:06] <desrt> have a nice bug i'm working on now and it's one of those ones where the solution is simple but tricky to get right
[06:06] <desrt> so i'm happy :)
[06:06] <desrt> didrocks: i'm in CEST
[06:14] <desrt> hikiko: good morning
[06:17] <didrocks> tjaalton: still crashing…
[06:17]  * didrocks almost lost 20 minutes of writing on my blog
[06:17] <didrocks> (for the Ubuntu Make release)
[06:17] <didrocks> fortunatly chrome is awesome
[06:18] <tjaalton> didrocks: file a new bug on xserver-xorg-video-intel, saying you have the latest
[06:18] <tjaalton> ickle (upstream) will have a look
[06:19] <tjaalton> and then you can switch to uxa (man intel)
[06:20] <didrocks> tjaalton: doing (just after blogging)
[06:21] <tjaalton> thx
[06:21] <tjaalton> you can assign it to me
[06:21] <didrocks> will do, thanks!
[06:22] <tjaalton> what does lspci -nn -s 0:2.0 say?
[06:22] <didrocks> 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09)
[06:24] <tjaalton> so sandybridge
[06:24] <tjaalton> hm, my t420s has one and wife is using it every day
[06:25] <tjaalton> on trusty but since the crashes happen there too..
[06:25] <didrocks> tjaalton: I never got the crashes before upgrading to wily here
[06:25] <didrocks> so maybe it was less frequent?
[06:26] <didrocks> vivid was fine as well
[06:26] <didrocks> it really started right after upgrading to wily
[06:26] <tjaalton> that's weird then since the driver didn't change, other than a few patches from debian. base version is the same
[06:30] <didrocks> weird, indeed…
[06:30] <tjaalton> maybe other bits make it easier to trigger then
[06:31] <didrocks> can be
[06:40] <desrt> aside: does anyone know when i arrive in heidelberg? :)
[06:40] <didrocks> you just wrote "train", so no :p
[06:40] <desrt> i seem to have temporarily misplaced my yubikey so i can't check the spreadsheet
[06:40] <desrt> i mean which day :)
[06:40] <didrocks> pitti: how to bypass already in apport the check for ubuntu genuine package as I want to report from the ppa? /me doesn't remember
[06:40] <didrocks> desrt: tomorrow
[06:41] <desrt> what?!
[06:41] <didrocks> as Laney and I IIRC
[06:41] <didrocks> let me recheck
[06:41] <desrt> zomg
[06:41] <didrocks> 14/08/2015
[06:41] <didrocks> yep
[06:41] <pitti> didrocks: APPORT_DISABLE_DISTRO_CHECK=1
[06:41] <desrt> insanity
[06:41] <desrt> thanks
[06:41] <didrocks> pitti: many thanks!
[06:41] <didrocks> desrt: I hope you know the time though :p
[06:41] <desrt> i should buy some train tickets or something
[06:42] <didrocks> ahah
[06:42] <didrocks> that was my guess ;)
[06:43] <didrocks> desrt: I arrive at half past 3, Laney at 4something IIRC
[06:43] <desrt> this makes me sad
[06:43] <didrocks> to see us tomorrow? I see :p
[06:43] <desrt> to leave the place where i am now
[06:43] <didrocks> are you going back after debconf?
[06:44] <desrt> back home
[06:49] <RAOF> pitti: Would you be able to upload colord at your leisure?
[06:50] <pitti> RAOF: sure!
[06:50] <pitti> RAOF: hm, the last three releases in git are UNRELEASED
[06:50] <RAOF> Yeah, please mark the last one as to unstable.
[06:50] <pitti> RAOF: can you merge the changelogs?
[06:51] <RAOF> I'm leaving that step to you, because last time I marked an upload as going to experimental it... didn't :)
[06:51] <pitti> ah, ok :)
[06:51] <RAOF> pitti: 1.2.11-1 has already been rejected from NEW, but I can certainly merge the changelogs if you want.
[06:52] <pitti> RAOF: ah, was 1.2.10-1 uploaded at all?
[06:52] <RAOF> No; it sat in my tree marked as “experimental”, and I thought I'd got it uploaded.
[06:53] <pitti> ok, so dch -r/debcommit -r/dput should be done by one person in one go; I'll do that after the changelog merge then
[06:55] <RAOF> Merged changelog entries.
[06:56] <pitti> RAOF: removing existing debian/1.2.11-1 tag FYI
[06:56] <RAOF> pitti: Yeah, good call.
[06:57] <pitti> W: colord source: out-of-date-standards-version 3.9.5 (current is 3.9.6)
[07:10] <pitti> RAOF: uploaded
[07:10] <RAOF> pitti: Ta.
[07:11] <RAOF> I'll fix those nits in git, so the next upload is lintian clean.
[07:11] <RAOF> Modulo manpages for internal binaries, because sod that.
[07:12] <pitti> RAOF: moving them to /usr/lib isn't an option?
[07:12] <RAOF> It probably is.
[08:03] <willcooke> o/
[08:04] <Laney> yo
[08:05] <willcooke> what up Laney
[08:05] <didrocks> morning willcooke, Laney
[08:06] <pitti> hey Laney, how are you?
[08:08] <Laney> hey willcooke didrocks pitti
[08:08] <Laney> doing good!
[08:08] <Laney> tried to watch out for some meteors last night
[08:09] <Laney> saw a few!
[08:09] <pitti> ah, the Perseides?
[08:11] <Laney> yeah - it was supposed to be the peak
[08:11] <Laney> Would have been better if I wasn't in the city though
[08:11] <seb128> good morning desktopers
[08:11] <seb128> hey willcooke Laney pitti
[08:11] <seb128> re didrocks
[08:11] <pitti> bonjour seb128 !
[08:12] <Laney> hey seb128
[08:12] <didrocks> re seb128
[08:26]  * didrocks goes for a run
[08:26] <seb128> didrocks, enjoy!
[08:27] <didrocks> seb128: thanks, especially knowing that the next one will be at debconf with Laney :)
[08:27] <seb128> hehe
[08:27] <seb128> you can jog next to his bike I guess :-)
[08:27] <Laney> oh I didn't know the word for running and cycling were the same in france :)
[08:27] <didrocks> seb128: that may be a way ;)
[08:28]  * didrocks really gone
[08:28] <Laney> get some skates and I can tow you
[08:28] <didrocks> that's not the goal of "exercising", you know ;)
[08:29] <Laney> it'll make *me* work harder
[08:43] <willcooke> The -desktop mailing list is now purged
[08:43] <willcooke> \o/
[08:49] <seb128> willcooke is in charge now, no need to worry anymore good desktop people, your emails are going to be moderated ;-)
[08:52] <willcooke> s/moderated/discarded more regularly
[08:52] <seb128> sounds about right!
[09:35] <willcooke> So it looks like LP sends messages to the mailing list for each commit etc.  Do we want those to be published?  They're held at the moment.  I don't think we want all of them on the list really.
[09:35] <willcooke> Any thoughts one way or the other?
[09:36] <willcooke> oh, except this messages is sent to look like it came from seb128 rather than LP
[09:36] <seb128> willcooke, yeah, launchpad sends comment like they were coming from the user
[09:36] <seb128> and no we don't want them on the list
[09:37] <seb128> usually that happens because somebody subscribed the wrong team to a bug
[09:37] <seb128> e.g ubuntu-desktop
[09:44] <willcooke> ahh
[09:44] <willcooke> right, yeah
[09:45] <willcooke> I guess I'll ignore them and flush the queue once in a while
[09:45] <seb128> +1
[09:45] <seb128> sometime those do reach the list because some of us are subscribed to the list so it goes through
[09:46] <seb128> I usually go to the bug and unsubscribe the team when that happens
[09:46] <willcooke> oki, I can do that
[10:40] <ochosi> hey seb128
[10:40] <ochosi> wanted to ping you quickly about that libreoffice packaging change we (xubuntu) wanted to propose
[10:41] <darkxst> hey desktopers
[10:41] <ochosi> seb128: so to be concrete, the packaging issue in libreoffice i wanted to ask you about is summarized here: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1483914
[10:44] <darkxst> Laney, can you take another look at the peripheral settings branches for u-s-d/u-c-c, given up on g-o-a patched g-c-c to not dep on g-o-a 3.16
[10:47] <seb128> hey darkxst ochosi
[10:47] <darkxst> hey seb128
[10:47] <Laney> darkxst: in theory but probably not in the next two days
[10:48] <seb128> darkxst, the goa demote only some binaries approach is not security team approved then?
[10:48] <seb128> ochosi, yeah, alternative recommends seems fine to me
[10:48] <ochosi> seb128: great! anything else we can do to move this ahead?
[10:48] <Laney> someone else would be more satisfactory probably
[10:48] <seb128> ochosi, submit a debdiff for sponsoring? ;-)
[10:49] <Laney> given next week is debconf :(
[10:49] <ochosi> seb128: heh, ok i will try to get that for you (shouldn't that be a one-liner though?)
[10:49] <seb128> ochosi, it should yes ;-)
[10:49] <Laney> bahaha
[10:49] <Laney> have you seen libreoffice's rules file?
[10:49] <seb128> Laney, darkxst, maybe robert_ancell can do revieew
[10:50] <seb128> Laney, no, trying to avoid it!
[10:50] <ochosi> Laney: nope
[10:50] <ochosi> is it *that* good? :)
[10:50] <Laney> have a drink on standby
[10:50] <Laney> seb128: think he declined to do it before?
[10:51] <seb128> yeah, I think he said he didn't have enough clue about the topic
[10:51] <seb128> so good luck to find a reviewer this week I guess...
[10:51] <Laney> join the club
[10:51] <ochosi> hummright
[10:52] <ochosi> so you're saying we should start prepping the FFe already? ;)
[10:53] <seb128> the alternative recommends should require a ffe
[10:54] <Laney> not you
[10:54] <Laney> talking about darkxst's change
[10:56] <seb128> yeah, I was replying to ochosi
[10:58] <Laney> still got a week
[10:58] <Laney> (!!! only a week)
[11:01] <ochosi> oh ok
[11:09] <mitya57> ted, hi, any chance you can top-approve https://code.launchpad.net/~albertsmuktupavels/libappindicator/watch-status-notifier-watcher-dbus-name/+merge/263694 ?
[11:10] <mitya57> this is a rebase of a branch you approved without the part you disapproved :)
[11:15]  * pitti rentre de courier -- trop chaud aujourd'hui !
[11:15] <Laney> desrt: I probably arrive at 18:45
[11:17] <didrocks> pitti: il fait meilleur ici au contraire, c'était facile de courir :)
[11:18] <didrocks> Laney: I think I'll be in the hotel lobby then
[11:19] <pitti> didrocks: c'était dur pour moi, j'ai perdu à aller dans le matin :/
[11:19] <Laney> didrocks: cool!
[11:19] <didrocks> pitti: oui, je me fais piéger aussi parfois
[11:20] <darkxst> seb128, apparently no one thought that out, need webkit binaries in main to build the other stuff! and that is too confusing!
[11:21] <Laney> darkxst: suggest asking robert_ancell again nicely :P
[11:23] <darkxst> Laney, he was not at all keen last time I asked
[11:24] <Laney> :/
[11:26] <Laney> I don't think any of us are likely to know about it, so we'll all have to spend some time getting up to speed
[11:26] <Laney> bleh
[11:26] <Laney> oh well
[11:38] <darkxst> Laney, I could setup a ppa, for testing, but not about to self sponsor without a second set of eyes looking over it
[11:38] <darkxst> but apparently only my eyes understand the patches ;(
[11:41] <Laney> I don't mind doing it, just struggling for time this week
[11:41] <Laney> Just wish someone else would be willing too
[11:46] <seb128> I would be happy to do it, but I want to land the bluez5 transition first and I'm doing sponsoring shift which is really needed and still have some other small things in backlog and debconf coming as well
[11:48] <seb128> darkxst, yeah, I didn't fully understand how that "demote binaries only" was supposed to work, but I had too many other things to try to understand it really or argue
[11:51] <darkxst> seb128, landing bluez5 first is fine, just so long as it gets through beore freeze (Athough I guess it will be a FFe)
[11:53] <darkxst> in theory it works, but only if webkit2 binaries are in main, its not like I have had huge amounts of free cycles to think about this either
[12:26] <seb128> happyaron, can you reply on https://code.launchpad.net/~gunnarhj/ubuntu/wily/libx11/pt_PT-compose/+merge/258526 ?
[12:30] <didrocks> tjaalton: FYI, 2 more crashes in 15 minutes
[12:31] <tjaalton> didrocks: switched to uxa yet?
[12:31] <didrocks> tjaalton: no, doing that now
[12:31] <didrocks> tjaalton: do you think I was using uxa in pre-wily?
[12:31] <tjaalton> no
[12:31] <tjaalton> it's something else triggering it
[12:34] <didrocks> creating a Xorg.conf, so last decade! :)
[12:34] <tjaalton> yep..
[12:52] <didrocks> tjaalton: after another crash, running UXA now…
[12:56] <tjaalton> cool
[15:05] <seb128> does anyone see a reason to not upload bluez5 now?
[15:06] <seb128> we got some testers that said it works fine and nobody came with an "hold on" on the list
[15:15] <seb128> willcooke, Laney, didrocks1, ^ no objection?
[15:15] <Laney> I didn't try it yet, but go for it if you're happy
[15:15] <Laney> there is time to fix stuff
[15:15] <seb128> cyphermox, ^
[15:15] <seb128> right
[15:15] <seb128> I tested it several times and didrocks1 did as well
[15:16] <cyphermox> ah, no objections, by all means it's way overdue :)
[15:16] <seb128> ;-)
[15:16] <seb128> ok, let's do that then
[15:16] <cyphermox> things should Just Work (tm)
[15:16] <cyphermox> though
[15:17] <cyphermox> are we likely to inconvenience the gcc5 transition in any way while fixing the inevitable small things that will break?
[15:17] <seb128> Laney, didrocks1, the transitions ppa is non virtual, is that good enough to archive copy include binaries?
[15:17] <Laney> does it build with proposed?
[15:18] <seb128> unsure, how do I tell?
[15:18] <seb128> https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/transitions/+edit doesn't have such details
[15:18] <Laney> in the options page for the PPA
[15:18] <seb128> ah
[15:18] <seb128> https://launchpad.net/~ubuntu-desktop/+archive/ubuntu/transitions/+edit-dependencies
[15:18] <seb128> no
[15:18] <Laney> and it doesn't follow archive comopnents
[15:18] <Laney> so probably good to rebuild
[15:19] <seb128> alright
[15:19] <seb128> Laney, thanks
[15:19] <Laney> np
[15:23] <didrocks1> seb128: do a source copy though
[15:23] <didrocks1> that will avoid the upload :)
[15:23] <seb128> didrocks1, right, what we just said
[15:23] <didrocks1> good
[15:23] <seb128> oh, you mean rather than a dput
[15:23] <seb128> yeah
[15:23] <didrocks> yep
[15:24] <didrocks> if the version is good for the archive, of course
[15:24] <didrocks> (and yeah, no objection for me)
[15:25] <willcooke> seb128, +1 BlueZ
[15:26] <seb128> didrocks, Laney, willcooke, cyphermox, thanks, bluez done, let's have fun ;-)
[15:26] <Laney> people were already complaining about wily phone being broken
[15:26] <didrocks> \o/
[15:26] <Laney> let's give them more
[15:26] <Laney> \m/
[15:26] <didrocks> Laney: heh
[15:26] <seb128> haha
[15:26] <seb128> desktop daily doesn't boot either
[15:27] <Laney> srsly
[15:27] <Laney> it got promoted
[15:27] <seb128> yeah
[15:27] <cyphermox> working on it
[15:27] <seb128> bug 1484571
[15:27] <Laney> can we stakeholderify some work to get those tests doing a little bit more?
[15:27] <seb128> Laney, jibel said
 seb128, actually installation works when the the system boots over pxe
[15:27] <seb128>  seb128, which what utah does IITC
[15:27] <cyphermox> I don't know why it got promoted though, not booting should be critical enough for things to fail :)
[15:27] <seb128> cyphermox, ^
[15:27] <cyphermox> yeah
[15:27] <seb128> it boots over pxe
[15:27] <cyphermox> makes sense
[15:28] <seb128> so yeah, maybe we need a way to test that case as well
[15:28] <cyphermox> it's probably broken in isolinux or some such piece way before casper
[15:28] <Laney> i.e. get https://bugs.launchpad.net/ubuntu-test-cases/+bug/1477227 prioritised :)
[15:30] <Laney> willcooke: maybe we could get this on the QA team's $agile_term_for_things_to_work_on ?
[15:31] <willcooke> Laney, hrm, I already did.  I will do so again
[15:32] <jibel> Laney, it's already on our $whatever_you_name_the_agile_thing
[15:32] <willcooke> :D
[15:32] <Laney> jibel: nice
[15:32] <Laney> it's just not possible to tell that from looking at the bug :P
[15:54] <jibel> Laney, indeed, we have bug 1479064 blocking ubiquity tests which should have caught this problem. I'll have someone on it after OTA6 if it is not fixed earlier.
[15:54] <willcooke> thx jibel
[16:12] <didrocks> tjaalton: and crashed with UXA then…
[16:13] <tjaalton> didrocks: huh
[16:14] <tjaalton> didrocks: add a trace to the bug again
[16:14] <didrocks> tjaalton: hum, isn't what I've done?
[16:14] <didrocks> gdb.txt
[16:14] <didrocks> (see my comment)
[16:15] <tjaalton> yes, but that was with sna
[16:15] <tjaalton> the default
[16:15] <didrocks> ah, you want another one with UXA? ok
[16:15]  * didrocks cleans up /var/crash for next instance
[16:44] <dholbach> hey hey
[16:46] <dholbach> seb128 did quite a bit of sponsoring today, can somebody else help take a look at the remaining items on http://reqorts.qa.ubuntu.com/reports/sponsoring/?
[16:46] <seb128> dholbach, hey
[16:46] <dholbach> thanks again seb128
[16:46] <seb128> dholbach, yw!
[16:46] <dholbach> sorry ... above I meant remaining desktop-ish items
[16:47] <seb128> dholbach, you might want to chase up people on other channels than desktop ;-)
[16:47] <dholbach> there's even a few from your team mates
[16:47] <seb128> yeah
[16:48] <seb128> Laney, wasn't https://code.launchpad.net/~attente/unity-control-center/non-gnome-unity-ibus-support/+merge/238293 made for you? you could test it ;-)
[16:48] <Laney> I don't have this setup any more
[16:48] <Laney> but could do in theory
[16:49] <seb128> oh ok, well if you don't have the setup it's not easier for you than for somebody else
[16:49]  * Laney is all unity now
[16:49]  * Laney the company man
[16:51] <seb128> \o/
[16:57] <seb128> k, going for some exercice
[16:57] <seb128> have fun everyone, see you tomorrow
[16:57] <dholbach> have a great evening!
[16:57] <seb128> thanks, you too ;-)
[17:08] <Laney> right then, ttyl!
[17:08] <Laney> I won't be reliably online tomorrow
[17:08] <Laney> will be shuffling eastwards
[17:08]  * Laney hopes passport is in date
[17:09] <willcooke> g'night all - safe travels those of you travelling
[17:11] <Laney> happyaron: what's the weather like there?
[17:11] <Laney> holy crap, 32°?
[17:57] <seb128> woot, bluez5&co already migrated to wily, well handled transition ;-)
[18:00] <mitya57> \o/
[18:15] <seb128> bah, in fact no, some packages migrated that clean deprecated depends or enable support for both version but bluez is blocked on buggy boottest
[21:19] <happyaron> Laney: it's hot in the afternoon, but a bit cold at night
[21:21] <seb128> happyaron, hey, saw my ping about https://code.launchpad.net/~gunnarhj/ubuntu/wily/libx11/pt_PT-compose/+merge/258526 ?
[21:22] <happyaron> seb128: commented just now :)
[21:23] <seb128> happyaron, thanks ;-)