=== salem_ is now known as _salem
[01:51] <Noskcaj> Should brasero's tracker support be re-added now tracker's in main?
=== infinity changed the topic of #ubuntu-devel to: Archive: Feature Freeze | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of lucid -> trusty | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots:
=== alexlist` is now known as alexlist
[08:47] <mitya57> bdmurray: first, I tested it myself; second, upstream reporter tested 5.0 and said that it worked there.
[08:47] <mitya57> (the patch for 4.1 is a minimal version of a patch for 5.0)
[08:56] <Mirv> mlankhorst: cjwatson: bzoltan: Re: qtcreator-plugin-ubuntu autopkgtest GLX error. I see a similar error in the unit tests of Qt. The previous successful build was on Wednesday, before the Mesa 10.3 upload.
[08:58] <Mirv> the autopkg test error is at https://jenkins.qa.ubuntu.com/view/Utopic/view/AutoPkgTest/job/utopic-adt-qtcreator-plugin-ubuntu/lastBuild/ARCH=amd64,label=adt/console
[08:58] <Mirv> and the Qt error at https://launchpadlibrarian.net/185821388/buildlog_ubuntu-utopic-amd64.qtbase-opensource-src_5.3.0%2Bdfsg-2ubuntu8~utopic1~test1_FAILEDTOBUILD.txt.gz
[09:05] <Mirv> filed bug #1374355 about it
[09:05] <ubottu> bug 1374355 in mesa (Ubuntu) "GLX error with the new Mesa 10.3" [Undecided,New] https://launchpad.net/bugs/1374355
[09:19] <Mirv> /me notices bug #1374131 already filed earlier
[09:19] <ubottu> bug 1374131 in mesa (Ubuntu) "qtcreator-plugin autopkg test fails on AMD64 mesa mesa_10.3.0" [Critical,New] https://launchpad.net/bugs/1374131
=== ahodzic is now known as fooctrl
[10:13] <brainwash> grub-common installs /etc/init.d/grub-common (Record successful boot for GRUB), but no systemd service file yet. should I file a report and request it?
[10:19] <cjwatson> brainwash: if you can work out how to express it in systemd sure
[10:20] <cjwatson> it's an "as late as possible after pretty much everything else has started" kind of thing, which is tricky to express
[10:20] <cjwatson> brainwash: file it in Debian though please
=== greyback__ is now known as greyback
=== smow is now known as pfsmorigo
[11:11] <infinity> mlankhorst: I know you don't work on Fridays, but put on a community hat and pretend it's not work, you have some people to answer to for that mesa upload. :P
=== MacSlow is now known as MacSlow|lunch
=== ara_ is now known as ara
[12:12] <kgunn> mlankhorst: hey any chance you could help us out ?
[12:17] <lool> cjwatson: hey, latest mesa upload in utopic-proposed (FFE bug #1364003) breaks other packages; should we revert this with an upload of the previous version to unblock them?
[12:17] <ubottu> bug 1364003 in mesa (Ubuntu) "[FFE] mesa 10.3" [High,Fix committed] https://launchpad.net/bugs/1364003
[12:17] <lool> cjwatson: seem mlankhorst isn't around today to debug the issue
=== MacSlow|lunch is now known as MacSlow
[12:20] <lool> kgunn: did someone reproduce the issue outside of the testbed? do we have any details about it? (only thing in jenkins log is Could not initialize GLX)
[12:22] <kgunn> lool: nope, i couldn't find anyone to help, altho... Mirv might have ? i see he added a comment that it was effecting another package
[12:22] <Mirv> kgunn: there's a duplicate bug report now attached to yours, showing how qtbase also now fails to build (or actually, fails running a certain unit test) similarly
[12:23] <kgunn> lool: so there you go ^
[12:23] <lool> kgunn: that's still the same symptom though
[12:23] <cjwatson> lool: sorry swamped
[12:23] <cjwatson> lool: oh I don't see why you need to reupload though
[12:23] <cjwatson> lool: it's only in -proposed, we could remove it
[12:24] <lool> cjwatson: ok, let's do that then
[12:24] <lool> I'll reopen the FFE
[12:24] <cjwatson> lool: BUT
[12:24] <lool> there's always a butt
[12:24] <cjwatson> lool: can you check that nothing else in -proposed depends on the updated version?
[12:24] <cjwatson> lool: you don't need to reopen the ffe, it's only fix-committed
[12:24] <cjwatson> that's not a closed state
[12:25] <lool> I'll check
[12:28] <caribou> Laney: stgraber: xnox: any easy way to find out if my upload rights have been granted ?
[12:29] <caribou> i.e. similar than https://ftp-master.debian.org/dm.txt
[12:34] <lool> cjwatson: I've searched for 10.3.0 versioned deps or build-deps in utopic-proposed {main,universe} for amd64/source and didn't find any; there was a mention in the FFE that this mesa upload would allow demoting llvm, but that has not been uploaded yet afaics
[12:40] <rbasak> caribou: there's a command called "ubuntu-upload-permission" in ubuntu-dev-tools.
[12:41] <caribou> rbasak: tks, will check that out
[12:44] <netforyou1337> Anybody know how i can change the System Details? For example: MyName OS
[12:48] <netforyou1337> Anybody know how i can change the System Details in Settings? For example: MyName OS
[12:50] <cjwatson> lool,mlankhorst: removed with a reference to bug 1374131
[12:50] <ubottu> bug 1374131 in mesa (Ubuntu) "qtcreator-plugin autopkgtest fails on AMD64 mesa mesa_10.3.0" [Critical,Confirmed] https://launchpad.net/bugs/1374131
[12:50] <lool> cjwatson: thanks
[12:50] <lool> kgunn: ^
[12:51] <lool> kgunn: do you know how to retrigger the apt?
[12:51] <cjwatson> will retry the autopkgtests in a bit; remind me when mesa/utopic-proposed vanishes from rmadison
[12:51] <lool> ah thanks
[12:51] <cjwatson> lool: you can't yet
[12:51] <cjwatson> they're still in the published archive
[12:52] <lool> I didn't know whetehr I had permission at all
[12:52] <cjwatson> I have no idea
[12:52] <lool> will ping you when it's really gone
[12:52] <cjwatson> you should have, I think core-devs do, but it can be a bit non-obvious to find because HI JENKINS THANKS A BUNCH
[12:53] <netforyou1337> Anybody know how i can change the System Details? For example: MyName OS
[12:58] <zul> pitti:  ping
=== _salem is now known as salem_
[13:22] <LocutusOfBorg1> can libjpeg-turbo be synced from debian?
[13:22] <LocutusOfBorg1> or we are just too late?
[13:30] <Laney> caribou: lp:ubuntu-archive-tools edit-acl -p launcpad-id -S utopic query
[13:31] <caribou> Laney: ubuntu-upload-permission did answer my query : my PPU access rights have not been implemented yet
[13:32] <Laney> oh, I'm not aware of that script
[13:32] <Laney> stgraber: ^ could you grant them please?
[13:32] <caribou> Laney: in ubuntu-dev-scripts as rbasak said
[13:32] <Laney> cool
[13:32] <caribou> I didn't know about it either
[13:41] <sil2100> mitya57: hey! Thanks for driving the appmenu-qt5 landing ;)!
[13:48] <lool> cjwatson: mesa is gone from rmadison, mind kicking autopkgtests again?
[13:49] <lool> cjwatson: qtcreator-plugin-ubuntu woudl be one, not sure which others
[13:51] <cjwatson> lool: qtcreator-plugin-ubuntu done
=== rickspencer3_ is now known as rickspencer3
[14:02] <stgraber> caribou, Laney: add the ACLs and added you to ~ubuntu-dev
[14:02] <Laney> ty
[14:04] <caribou> stgraber: thanks
[14:14] <bdmurray> mitya57: it wasn't clear to me the upstream reporter tested the version in trusty-proposed
[15:28] <Riddell> mvo: how about changing the bash-completion to say use apt rather than apt-get ?
[15:29] <mvo> hey Riddell, yes https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747094
[15:29] <ubottu> Debian bug 747094 in bash-completion "bash-completion: [patch] add support for the new "apt" command" [Wishlist,Open]
[15:29] <mvo> Riddell: open since 5 may :(
[15:34] <Riddell> mvo: one little delta from debian won't hurt will it? :)
[15:35] <rbasak> "Ubuntu gets apt ahead of Debian"
[15:36] <mvo> Riddell: heh :) I think I will just include it in apt directly and we both get it
[15:36] <mvo> Riddell: my co-maintainer complained that it does not belong into apt directly but given the state of maintenance of bash-completion I think he is wrong :)
[15:37] <ogra_> rbasak, nah, not clickbaity enough ... "Ubuntu gets new apt, leaving debian behind in desparation !!!11!"
[16:37] <jdstrand> hallyn: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1373555/+attachment/4216305/+files/lxc_1.1.0%7Ealpha1-0ubuntu5.debdiff
[16:37] <ubottu> Launchpad bug 1373555 in lxc (Ubuntu) "please restrict signal, ptrace and unix mediation to the container" [High,Triaged]
[16:38] <mitya57> sil2100: actually, it was Mirv — thank him :)
[16:38] <jdstrand> hallyn: I built it locally and did my local tests
[16:38] <jdstrand> hallyn: I'm happy to upload it if you are
[16:39] <mitya57> bdmurray: he tested 5.0, I tested the version in -proposed, isn't that enough?
[16:40] <bdmurray> mitya57: in the bug you don't mention that you yourself tested it with the version of the package in -propsed. The upstream reporter didn't test the version of the package in -proposed so that isn't enough.
[16:41] <T0rch> hello guys
[16:41] <T0rch> im having a bad day ...
[16:41] <T0rch> bash version 4.3-9ubuntu3
[16:41] <T0rch> env ls='() { echo vulnerable; }' bash -c ls
[16:42] <T0rch> and the result is that im still vulnerable ...
[16:42] <T0rch> http://seclists.org/oss-sec/2014/q3/741
[16:43] <mdeslaur> T0rch: that's perfectly normal
[16:43] <hallyn> jdstrand: looks good, thanks
[16:44] <hallyn> (that is, please go ahead and upload :)
[16:45] <jdstrand> hallyn: cool, thanks
[16:45] <cjwatson> the link above is AFAICS wrong about setuid/setgid scripts, since bash doesn't import functions from the environment in that case
[16:46] <cjwatson> (though I'd be all for killing the stupidity that is imported functions altogether, e.g. https://lists.debian.org/debian-devel/2014/09/msg00784.html - it just involves rather more work sadly)
[16:48] <T0rch> ok, so i understand now that im safe
[16:49] <T0rch> thanks you!
[16:50] <cjwatson> though scripts called by set-id scripts might have a problem, I'm not sure
[16:52] <cjwatson> so I don't know that I'd say "safe", but no more vulnerable than anyone else at the moment :-/
[16:55] <T0rch> yeah, at least from the other two we are now!
[16:55] <T0rch> i have to say im very happy with the packages from the last branch (utopic). im trying to learn more and trying to get more involved in the future!
[16:56] <T0rch> Thank you for all the support!
[17:05] <mdeslaur> cjwatson: yes, I'm waiting to see what upstream bash says about the imported functions before making a decision or possibly using red hat's patch
[17:43] <hallyn> rharper: stgraber: infinity:  https://wiki.ubuntu.com/QemuPTMigration  This is the summary of what I'm about to create FFE bugs for.
[17:43] <rharper> reading
[17:44] <cjwatson> mdeslaur: is that the one that goes to BASH_FUNC_foo() ?
[17:44] <mdeslaur> cjwatson: yeah
[17:47] <rharper> hallyn: when we talk about using migrating from P -> T  and then T -> U;  are we expecting the pc-1.0-precise to also work on U (via the P -> T -> U) ?  or would we require users to migrate P -> T, switch machine type from pc-1.0-precise to pc-i440fx-trusty, to migrate from T -> U ?
[17:47] <rharper> for some reason, I feel we need to discuss the EOL for the machine type (pc-1.0-precise) ...
[17:48] <rharper> ie, when will we no longer accept/support that machine type
[17:49] <rharper> and at that point, the solutuion is to "upgrade" the machine by updating the machine type used (and dealing with any issues that arise from that transition, like re-registering windows, as needed)
[18:06] <ChrisTownsend> hallyn: Hi, I'm having some issue creating a cgroup in a container and stgraber said you might be able to help.  Are you available to discuss and is this a good channel?
=== roadmr is now known as roadmr_afk
[18:44] <hallyn> rharper: I'm happy to discuss EOL for machine types, makes our lives easier.  Until we do so, I was imply assuming we'd have to carry that machine type forward.  So U would know about pc-1.0-precise.
[18:45] <hallyn> I think it's reasonable to say that when precise goes EOL, pc-1.0-precise goes EOL
[18:45] <rharper> yeah, I realized that P will be around while U is here
[18:45] <rharper> hallyn: agreed
[18:45] <hallyn> right, and even 16.04.  But at lesat we coudl drop it at 17.04
[18:45] <rharper> yeah
[18:45] <hallyn> rharper: how abvout we mention this at the next server irc meeting?
[18:45] <rharper> I think that's a good idea
[18:46] <rharper> now, if ppa testing goes well, are we going to push that qemu into P T and U ?
[18:46] <hallyn> I'll add it to the agenda
[18:46] <hallyn> yeah.
[18:47] <hallyn> If we get FFEs in time, we could push into U without an SRU :)
[18:48] <hallyn> ChrisTownsend: sure, here's good.  (or #ubuntu-server)  what's going on?
[18:48] <rharper> cool
[18:57] <ChrisTownsend> hallyn: So I have a container where I'm trying to create a cgroup.   This is a Trusty host and Utopic in the container.  Here is a pastebin of some relevant info: http://pastebin.ubuntu.com/8434980/
[18:58] <ChrisTownsend> hallyn: So I'm not sure why I'm getting that error and we thought you might have a clue.
[19:00] <hallyn> ChrisTownsend: just to be sure...  try 'sudo cgm create all x1'
[19:00] <ChrisTownsend> hallyn: A little back story is that we are trying to get a Unity8 desktop session working in the container which works for the most part.  However, a recent change to how apps are started in Unity8 use the cgroup freezer directive in the upstart script.
[19:00] <ChrisTownsend> hallyn: Ok, I'll try that.
[19:01] <ChrisTownsend> hallyn: Same error
[19:03] <hallyn> lxc/unity8-lxc
[19:03] <hallyn> gr
[19:03] <hallyn> ChrisTownsend: it looks like you have the same block of lxc.mount.entry's twice in the container config?
[19:04] <hallyn> in fact the whole config seems duplicated.  can you cull it down?
[19:04] <hallyn> i don't think that should be messing with cgmanager, but who knows
[19:05] <hallyn> ChrisTownsend: then, when that still fails, can you pastebin ls -l /sys/fs/cgroup both in container and on host
[19:05] <ChrisTownsend> hallyn: Umm, not sure why that looks like that.  It's not supposed to any ways.
[19:05] <ChrisTownsend> hallyn: I'll fix that up.
[19:05] <hallyn> ChrisTownsend: given that you're not even doing any id mappings, i can't imagine what's actually going wrong
[19:07] <ChrisTownsend> hallyn: Oh, I think I hit paste twice accidentally in the pastebin.
[19:08] <ChrisTownsend> hallyn: http://pastebin.ubuntu.com/8435028/
[19:09] <hallyn> ok liemme fire up a digitalocean instance to try to reproduce under
[19:09] <ChrisTownsend> hallyn: Ok
[19:09] <hallyn> the utopic container is just straight-up utopic, no systemd pid 1 or anything funky?
[19:10] <ChrisTownsend> hallyn: It's pretty much straight up utopic.  It's the Unity 8 desktop preview ISO that has been unpacked.
[19:11] <ChrisTownsend> hallyn: http://cdimage.ubuntu.com/ubuntu-desktop-next/daily-live/current/
[19:20] <mlankhorst> cjwatson: if it mentions qxl i bet it's a stupid configuration issue or something :/
[19:23] <dupondje> Any chance nouveau & hdmi gets fixed before final?
[19:23] <hallyn> ChrisTownsend: ok, I guess cgmanager on trusty is older than i'd throught.  it doesn't support 'all'.
[19:24] <hallyn> so you need to create for each controller separately.
[19:24] <hallyn> not sure if i could get that feature in through an SRU, as not having that for the next 4.5 years of support is gonna hurt
[19:25] <hallyn> cgm could gain code to check the apiversoin and do 'all' by hand if need be, but that's added complexity and doesn't help all the other places we have to do that (lxc, libvirt, logind, etc)
[19:25] <hallyn> i suppose cgproxy could do it.
[19:26] <hallyn> that feels potentially fragile...  but better than doing it in al the clients
[19:26] <hallyn> i'm already gonna be owing some libations to release team over the various qemu migratoin ffe's going by, not sure i can swing cgmanager too :)
[19:29] <hallyn> ChrisTownsend: so something lie:
[19:29] <hallyn> awk -F: '{ print $2 }' /proc/self/cgroup | while read line; do sudo cgm create $line c2; done
[19:34] <ChrisTownsend> hallyn: Ok, I'll try that.  Sorry if I'm a little laggy in response.  I'm having to help take care of a sick toddler.
[19:35] <ChrisTownsend> hallyn: That seems to work.
[19:35] <ChrisTownsend> hallyn: Yeah, seems not having 'all' is going to hurt on Trusty.
[19:38] <ChrisTownsend> hallyn: I can probably take your awk script there and modify to suit my needs.
[19:41] <ChrisTownsend> hallyn: Thanks for your help.
[20:01] <hallyn> ChrisTownsend: cool.  Well I think I'll do the next upstream cgmanager release and then see waht i can do about upping the trusty version
[20:02] <hallyn> I htink there's an argument to be made that we have hgue amounts of testing of recent stuff, wehereas supporting newer features with older cgmanager is going to only expose more breakages like this
[20:02] <hallyn> (plus, afte rthe next release, it's "feature complete" in my book :)
[20:05] <hallyn> rharper: filed bugs 1374612, 1374617, 1374622
[20:05] <ubottu> bug 1374617 in Ubuntu Trusty "[FFE] New package: ipxe-precise" [High,New] https://launchpad.net/bugs/1374617
[20:05] <ubottu> bug 1374622 in libvirt (Ubuntu Trusty) "Support migration from 12.04" [High,New] https://launchpad.net/bugs/1374622
[20:05] <ubottu> bug 1374612 in qemu (Ubuntu Trusty) "[FFE] add pc-1.0-precise machine type" [High,New] https://launchpad.net/bugs/1374612
[20:30] <rharper> hallyn: nice!
=== davmor2_ is now known as davmor2
=== roadmr_afk is now known as roadmr
[21:08] <sl1rpy> im bored... does anyone need help with something?
[21:12] <Noskcaj> sl1rpy, What do you want to do? What can you do?
[21:13] <sl1rpy> well im fairly new with C++ and I want to learn how to make GTK applications but i couldn't find a decent book on it.
[21:14] <sl1rpy> im better with Java / C#
[21:15] <Noskcaj> sl1rpy, A good way to start (since you have programming skills) is find and fixing a bug in an app you use
[21:16] <Noskcaj> bugs.launchpad.net/ubuntu and bugs.debian.org would have a few
[21:16] <Noskcaj> What desktop do you use?
[21:17] <sl1rpy> unity
[21:20] <Noskcaj> I'm not fully sure where to start with it. I'm sure some of it's devs are around if you want to work on it
[21:20] <Noskcaj> But find a bug that you think you can fix, then i'll walk you through getting the fix into ubuntu (I can't code properly, but have done a lot a packaging)
[21:22] <sl1rpy> Noskcaj, someone pointed out i could work on bugs but most of the stuff is beyond me.
[21:23] <dobey> if you want to hack on unity, #ubuntu-unity is where to look at
[21:23] <Noskcaj> ok. Unfortunately, most of our work is bugfixes for the next month or two
[21:23] <dobey> sl1rpy: why do you want to write gtk+ apps in c++?
[21:24] <dobey> it's not the best language for writing gtk+ apps really
[21:24] <sl1rpy> dobey, really?  what is? C?
[21:25] <dobey> Vala is probably the best language for it, depending on what you want to build
[21:25] <dobey> if you want to build apps for Ubuntu, the best thing to use is probably c++/qt and the ubuntu sdk stuff
[21:26] <dobey> to build apps that work on phone, tablet, pc, or TVs
[21:27] <dobey> #ubuntu-app-dev might be a good channel for you to hang out in, if you want to write new apps (i think that's the channel name)
=== Ursinha is now known as Ursinha-afk
=== Ursinha-afk is now known as Ursinha