[00:00] Which bug? The bug in Qt? [00:00] yes [00:00] No [00:02] It was suggested I install 4.8.5.. since the bug is in 4.8.2, it doesn't seem likely that anyone will care. [00:05] except we've decided to support 12.04 LTS for another three years.. [00:06] that's the story yes [00:10] Lord, there's page after page after page of how to report a bug and I've yet to find the link to actually report the bug. [00:10] apb1963: try: ubuntu-bug konversation [00:12] And is that different from https://bugs.kde.org/show_bug.cgi?id=329793 [00:12] KDE bug 329793 in general "Krash!" [Crash,Resolved: upstream] [00:12] apb1963: yes, that would be filed in the launchpad bug tracker, where probably ScottK would find it and look into it.. [00:13] great. Thank you for that. [00:13] ugh [00:13] apport crashed [00:13] o_O [00:14] you very well might have a funky system, hehe. is there anything informative in dmesg or /var/log/ about it? [00:14] (I had a system with machine check exceptions, it wasn't much fun..) [00:16] you mean besides neverending dhcp requests? No. [00:17] :( [00:17] so... ubuntu-bug apport then? [00:17] worth a shot, it just might work.. :) [00:18] (it _should_ work, but it already crashed once on you..) [00:18] wait.... just noticed this.... prepare for minor flooding [00:18] ubuntu-bug konversation [00:18] python: ../../src/xcb_io.c:529: _XAllocID: Assertion `ret != inval_id' failed. [00:18] KCrash: Application '' crashing... [00:18] KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit [00:18] sock_file=/home/apb/.kde/socket-asterisk.saveabunny.com/kdeinit4__0 [00:18] QSocketNotifier: Invalid socket 68 and type 'Read', disabling... [00:19] here's how I came to be... first I installed the mini iso for i386... then I installed kubuntu-desktop... and other stuff. [00:19] apb1963: Have you updated? [00:20] Every 20 minutes [00:20] apt-cache show apport [00:20] Which version do you have? [00:20] Version: 2.0.1-0ubuntu17.6 [00:21] Hmm, yeah, you're updated. [00:21] Depends: python (>= 2.6), python-apport (>= 2.0.1-0ubuntu5), lsb-base (>= 3.0-6), python-gi, gir1.2-glib-2.0 (>= 1.29.17), sysv-rc (>= 2.86.ds1-14.1ubuntu2), upstart-job [00:22] You might want to take this to #ubuntu. This is a development channel. [00:22] That's where I started 6 hours ago [00:22] Or maybe even #kubuntu. [00:23] So crashing software is not a development problem [00:23] Well, it's more of a support problem if it's not occurring in a development release. [00:23] yeah, they both passed the buck [00:25] as did #kde, #kde-devel, #plasma and #konversation... though admittedly it's a library issue so it's amazing they were among the most helpful. [00:26] Until finally someone said: [00:26] I mean, I thought the idea behind LTS was 'get bigfixes really long' [00:26] [Tuesday, January 14, 2014] [03:46:24 PM] *bugfixes [00:26] [Tuesday, January 14, 2014] [03:47:00 PM] fsvo "bugfixes" [00:26] [Tuesday, January 14, 2014] [03:48:03 PM] actually, 4.8.5 isn't available even in the latest ubuntu [00:26] [Tuesday, January 14, 2014] [03:50:43 PM] who normally takes care of something like that? [00:26] [Tuesday, January 14, 2014] [03:52:37 PM] ubuntu developers [00:27] And so I came here [00:28] apb1963: well, you can start with this: https://bugs.launchpad.net/ubuntu/+source/konversation/+filebug -- be sure to refernce the kde.org bugreport you filed earlier; it'd be a help if you could copy and paste the traceback, too. [00:29] apb1963: once it's done, run "apport-collect " -- and see if that runs or crashes.. [00:30] i'm actually installing debug symbols now [00:30] what do I fill in for ? [00:31] whatever bug number you get from filing the bug manually at https://bugs.launchpad.net/ubuntu/+source/konversation/+filebug [00:35] got it [00:38] not positive since I got no feedback... but I think it's done. [00:38] still waiting on debug symbols for apport [00:39] apb1963: what bug number? [00:41] apport-collect 1269199 === zz_mwhudson is now known as mwhudson [02:21] bdrung: https://github.com/YokoZar/ppa-stats <-- What do you think for inclusion in ubuntu-dev-tools ? [02:22] (gets download counts for a PPA) === mwhudson is now known as zz_mwhudson [04:19] mfisch: Are you around? === timrc is now known as timrc-afk === doko_ is now known as doko [06:05] barry, for simple rebuilds which require 3.4 as the default we now have the https://launchpad.net/~ubuntu-toolchain-r/+archive/python3 ppa. [06:43] Good morning [06:49] infinity, RAOF: can you please set an exfail for colord 1.0.5-1's autopkgtest? colord newer worked [06:49] (holding up systemd) [06:49] Bah, sorry. [06:53] pitti: I don't know how to set an exfail, sorry. [06:53] pitti, do you feel good enough to look at zeitgeist test failures? [06:54] RAOF: right, that was more like a CC: [06:54] https://launchpad.net/ubuntu/+archive/test-rebuild-20140108/+build/5433297 [06:55] seiflotfy__: ^ [06:56] seiflotfy__: not very verbose, thanks to that silly automake parallel runner :( [06:56] which timezone is he? [06:56] British or Central European, I think [06:56] so, still a bit early for hackers [06:58] doko: i thought i fixed thoise [06:58] let me have a closer look [06:58] vala keeps changing and zeitgeist keeps breaking [06:58] seiflotfy__, seen in a test rebuild, so you need to update to trusty [07:00] thi is based on the latest release not git right? [07:00] seiflotfy__, what you find in trusty [07:00] 0.9.14-0ubuntu3 [07:03] where can i find the source of this package? [07:05] doko: [07:06] nm [07:06] apt-get source zeitgeist, if you are running trusty [07:06] or dget [07:06] seiflotfy__: it's upstream 0.9.14 plus a few patches: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/zeitgeist/trusty/files/head:/debian/patches/ [07:07] seiflotfy__: the first two patches are harmless, http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/zeitgeist/trusty/view/head:/debian/patches/pre_populator.patch looks more interesting [07:07] ouh nice [07:10] seiflotfy__: more generally, I think there was a way to make failures less ridiculously useless with the automake 1.13 parallel runner [07:10] i. e. more than just "FAILhahagofigure" [07:10] i think i know what it is [07:11] but cant do patching right now [07:11] some "verbose" flag, if only I could remember [07:12] doko: pitti can one of view try someting for me please? [07:13] seiflotfy__: sure [07:13] pull the latest code from git and tell me if it works for you "make check" [07:13] because we had a "not building" issue when vala 22 came out and we fixed it just recently [07:15] pitti: ? [07:16] seiflotfy__: yes, on it; currently in daily dist-upgrade, need to wait until I get apt again for its build deps [07:16] ok cool [07:16] http://cgit.freedesktop.org/zeitgeist/zeitgeist/ ? [07:19] seiflotfy__: I try building the package with http://cgit.freedesktop.org/zeitgeist/zeitgeist/commit/?id=42f0f6b0f17a584b703981b8a392c3225c7a8e98 until the git checkout finishes (that takes a while) [07:20] yes sir [07:20] thats the patch [07:21] seiflotfy__: indeed, that helps quite a bit [07:22] now test/c has two failures [07:22] test/direct now succeeds [07:22] oh man, vala can really take a toll on me sometimes [07:22] ok upgrading a vm here test this [07:23] seiflotfy__: git checkout done, building trunk here [07:23] seiflotfy__: the previous patch doesn't look like a vala-ism, though? [07:23] it is [07:23] because it worked with vala 20 [07:23] but not with vala 22 [07:23] we did not commit any changes in 6 months [07:23] so we did this to fix it for vala 22 [07:24] oh, you disabled optimize_variant_allocation() [07:24] yes sir [07:24] trunk "make check" WFM [07:25] show me the failure print out for test/c [07:25] i have thin i know what it is [07:26] could be because package build runs tests under fakeroot or something; "fakeroot make check" fails early, but our package has some "disable_failing_tests.patch" for that AFAICS; hang on [07:26] pitti, which b-d am I missing when I see [07:27] telepathy-farstream/Makefile.am:69: HAVE_INTROSPECTION does not appear in AM_CONDITIONAL [07:27] seiflotfy__: http://paste.ubuntu.com/6754838/ [07:28] doko: probably "gobject-introspection"? [07:29] thanks [07:29] pitti: fixing it [07:30] seiflotfy__: oh, you have an idea? it happens during package build, but not with a plain "make check", even in our package tree [07:30] probably the package build cleans the environment [07:30] seiflotfy__: ah -- "env -i make check" in trunk reproduces it [07:30] seiflotfy__: for you, too? [07:31] yeah [07:31] it stilly [07:31] in test/c/test-event.c line 29 [07:31] 39 [07:31] sorry [07:32] setting the xdg directory fails [07:32] it used to be [07:32] if (old_xdg_data_dirs != NULL) [07:32] old_xdg_data_dirs = g_getenv ("XDG_DATA_DIRS"); [07:32] but that segfaulted when i did make checks [07:33] seiflotfy__: oh, so in teardown() the g_setenv() gets a NULL [07:33] yeah [07:33] seiflotfy__: indeed, no XDG_DATA_DIRS during package build [07:33] so that's a simple fix [07:33] can you send me a patch or so [07:33] i need to shower and dress up (and get spanked at work) [07:35] pitti: ^ [07:35] seiflotfy__: yes, on it [07:37] seiflotfy__: http://people.canonical.com/~pitti/tmp/0001-Fix-unit-test-failure-if-XDG_DATA_DIRS-is-not-set.patch [07:37] seiflotfy__: want me to attach that to a bug report, or can you just push it? (it's trivial) [07:38] bug if poosible [07:40] seiflotfy__: https://bugs.freedesktop.org/show_bug.cgi?id=73651 [07:40] Freedesktop bug 73651 in Engine "tests fail if $XDG_DATA_DIRS is not set" [Normal,New] [07:45] doko: zeitgeist fix upstreamed ^ and test-built in sbuild, uploaded [07:48] pitti, seiflotfy__: nice! [07:54] pitti, fyi, http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20140108-trusty.html [07:54] will send an announcement later today [08:03] good morning [08:07] hey dholbach [08:08] hey pitti [08:17] doko: looking at cdbs test failures -- is dh_python2 supposed to stop moving files to /usr/share/pyshared/ ? [08:18] the package calls dh_python2 and then expects /usr/share/pyshared/testing/foo.py; but there is only ./usr/lib/python2.7/dist-packages/testing/ [08:18] doesn't it still create symlinks? [08:18] I could be wrong, though [08:18] pitti, yes, disabled that. upstream did start working around it for some reason [08:18] that's what I thought; file in /usr/share/pyshared/ [08:18] and symlinks in /usr/lib/python* [08:19] had to revert some upstream commits [08:19] need to forward and propose that to debian [08:19] hm, I remember http://bugs.python.org/issue19352, but that was only for unittests, not general module loading [08:20] doko: forward the reversion of upstream commits, or drop the /usr/share/pyshared/ moving? [08:20] doko: in other words, should I adjust cdbs' tests to not expect /pyshared any more, or will pyshared reappear soon? [08:21] pitti, no, it should not reappear. but when you forward, please say that this is not yet in debian [08:21] ack [08:22] doko: ah, from https://launchpad.net/ubuntu/+source/dh-python/1.20131021-1ubuntu5 ? [08:24] yes [08:25] pitti, looks like you were even involved with that: http://bugs.python.org/issue19352 ;p [08:25] doko: right, what I wrote 5 mins ago; but that was only for unittest [08:26] doko: and I uploaded a reversion of that patch to fix that (you said "go ahead" with that back then) [08:26] sure [08:27] Is there a standard place in a lp ppa that says "this isn't in main because

" ? [08:28] Specifically I'm looking at https://launchpad.net/~arminha/+archive/python-aosd-release and I can't see such a thing; plan B is to email the maintainer (who is also upstream) and ask him. [08:28] doko: http://paste.ubuntu.com/6755022/ works now; does the changelog entry make sense? [08:29] pitti, sounds fine [08:29] doko: ack, uploading and forwarding [08:29] twb: no, there is no standard for that - better to do your plan B [08:29] OK, thanks. [08:29] pitti, does the test succeed without and with it? [08:29] twb: PPAs don't care much about components [08:30] doko: sorry, without what? [08:30] pyshared [08:30] doko: tests currently fail because dh_python doesn't do pyshared any more [08:30] that's the reason for the FTBFS [08:30] pitti, right, but does your updated version succeed in debian too? [08:31] i. e. dpkg -c | grep -q '/usr/share/pyshared/testing/foo.py' [08:31] fails [08:31] doko: I'll sbuild it in sid as well to make double-sure, but I don't see why not -- there's still the symlink, right? [08:31] yes [08:32] good morning :-) [08:32] if that file wouldn't exist, python couldn't import it; that's how I wrote the changelog [08:32] hey zyga [08:48] doko: looking at pkgbinarymangler, too [09:06] hmm [09:06] anyone using debmirror? I started getting "rsync error: error in rsync protocol data stream (code 12) at io.c(605) [Receiver=3.0.9] [09:06] Warning: failed to use rsync to download extra files. [09:06] " lately [09:07] Laney: I was using it extensively until recently [09:07] Laney: which repository caused that problem for you? [09:07] yeah, the cronspam doesn't say sadly [09:07] Laney: (though I never saw anything like that) [09:07] it's doing ubuntu, ports and debian [09:08] Laney: hmm, well, I haven't kept my mirror up to date for a few weeks so I don't know [09:08] Laney: but I should be able to tell you if I see that later today [09:08] okay [09:18] pitti, the folks ftbfs looks vala related === shuduo is now known as shuduo|afk === shuduo|afk is now known as shuduo [09:29] doko: pkgbinarymangler FTBFS fix uploaded [09:53] -/win 22 [10:15] hum [10:15] Your mail to 'ubuntu-devel' with the subject [10:15] Post by non-developer to moderated list. [10:15] I sent from didrocks@ubuntu.com [10:17] didrocks, demoted ;p [10:18] doko: seems so ;) === tsdgeos_ is now known as tsdgeos [10:18] pitti: your patch works fine [10:18] pitti: trying to release a new package [10:18] didrocks, you can re-enable that by fixing ten ftbfs issues ;) [10:18] no, still in it seems: https://launchpad.net/~ubuntu-core-dev/+members#active ;) [10:18] seiflotfy__: ah, good; I added the patch to our package, it built fine now [10:18] doko: can I get a cookie then? ;) [10:18] but it keeps complaining about install -D ../../../doc/libzeitgeist/zeitgeist-gtkdoc-index.sgml docs_c/zeitgeist-2.0-docs.xml [10:18] install: cannot stat ‘../../../doc/libzeitgeist/zeitgeist-gtkdoc-index.sgml’: No such file or directory [10:18] seiflotfy__: so, no urgency from my side [10:19] didrocks, not only one, ten! [10:19] seiflotfy__: hm, autogen.sh'ed without --enable-gtk-doc or so? [10:19] heh [10:19] o hyeah [10:19] my bad [10:19] ok will roll out a release then :D === tkamppeter_ is now known as tkamppeter [10:27] pitti: will release on friday? is this ok? can you guys use the current git status... [10:27] ? [10:27] seiflotfy__: as I said, not urgent for us, I added the patch to our package already [10:29] ok cool [10:48] @pilot in === udevbot changed the topic of #ubuntu-devel to: Trusty Tahr Alpha 1 released! | Archive: open | Devel of Ubuntu (not support or app devel) | build failures -> http://qa.ubuntuwire.com/ftbfs/ | #ubuntu for support and discussion of lucid -> saucy | #ubuntu-app-devel for app development on Ubuntu http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://bit.ly/lv8soi | Patch Pilots: pitti [11:11] mlankhorst, do you care about the libxcb transition? [11:12] erm why? [11:13] mlankhorst, soname change? [11:13] hm not particularly care, but it sounds like something that would need solving :/ [11:13] then please do [11:15] did any soname change then? I thought it was just adding present/dri3 [11:16] mlankhorst, http://packages.qa.debian.org/libx/libxcb/news/20131227T000024Z.html has "Rename libxcb-sync0 for SONAME bump. " [11:16] oh indeed [11:17] libqt5gui5 and kde-window-manager depend on it, it seems [11:17] mlankhorst, honestly you should be aware of such changes *before* you upload ;p [11:21] if it was anything important or commonly used thing I would have noticed at least [11:22] seb128, do you know why nobody added the ubuntu fonts to the fontconfig conf? [11:22] doko, I guess because nobody is actively maintaining fontconfig [11:22] seb128, then why are you uploading new upstreams? ;-P [11:25] doko, because nobody else does and that's better than nothing ;-) [11:26] seb128, could you merge the debian changes? would like to avoid interaction ... [11:27] doko, is there anything in there we specially need? [11:27] that merge is non trivial and I would prefer to let it to somebody who knows fontconfig a bit better than me [11:31] I don't know that it's safe to add the Ubuntu font there yet [11:31] sladen or someone knowledgable on the subject would be better to ask [11:32] Laney, thanks for getting the cogl transition rolling ;) [11:32] darkxst: np, it's basically done now [11:32] looking at the last issue [11:33] Laney, well, why not? the ubuntu fonts are not that new. is sladen still working on these? [11:33] somewhat [11:34] It's whether they can be substituted for other fonts without it looking weird [11:34] why don't you try it on your system? [11:34] well, it's not easy to try if you don't know what to look for [11:34] like you might need to look at office documents to see if it impacts on layouting there [11:35] Laney, send me a patch and I'll check. just was looking at why openjdk didn't use these. and it's using fontconfig now [11:35] nice try :P [11:36] how do I get to a BPPH on launchpad's web interface? [11:37] https://launchpad.net/ubuntu/trusty/i386/groff-base [11:37] ta [11:37] You can search from the distroarchseries I think, but I find memorising the URL pattern easier :) [11:37] ok that doesn't help [11:38] (OK, you need to append the version to get the BPPH as such) [11:38] What are you looking for? [11:38] what happened to toonloop/arm64? [11:38] cogl transition, see update_output [11:39] That was in p-m's output before the cogl transition [11:39] update_excuses is clearer in this case; it's depending on things not ported yet [11:40] so it never migrated on arm64 [11:40] ? [11:40] Indeed [11:41] If it weren't built on arm64/ppc64el at all, it would be OK, but since it is it isn't allowed to increase the uninstallable count [11:41] It might actually be simplest to port gstreamer0.10-plugins-bad and mencoder [11:41] (Haven't looked at what's blocking those) [11:44] Hi, I need some advice on bug 1269203. If the package tries to overwrite files in libqt4-dbus:[ARCH], is Breaks/Replaces on libqt4-dbus (<< ...) not enough? [11:44] bug 1269203 in qt4-x11 (Ubuntu) "package libqtdbus4 4:4.8.5+git192-g085f851+dfsg-2ubuntu3 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libQtDBus.so.4', which is also in package libqt4-dbus:amd64 4:4.8.4+dfsg-0ubuntu22" [Undecided,New] https://launchpad.net/bugs/1269203 [11:45] Do I need Breaks/Replaces on libqt4-dbus:any in that case? [11:51] * s1aden reads scrollback re Laney and doko === _salem is now known as salem_ === s1aden is now known as sladen [11:53] Laney: there are certainly some fallbacks we could set to eg. have the monospace fallover to other monospace fonts, (rather than to something proportional in cases like arabic) [11:54] Laney: I guess it was not necessary to add it, since external documents coming are requesting things like "Times" "Helvetica", and those are what you need to provide substitutes for [11:54] Laney: whereas something asking for Ubuntu, on an Ubuntu system is likely wanting Ubuntu [11:55] Laney: (and going to suceed) === MacSlow is now known as MacSlow|lunch [11:56] sladen, I was reading #937200 and #1003857 [11:57] so should apps asking for serif or sans get dejagnu or ubuntu? [11:59] dejavu even [12:08] ok just a rebuild bump for qtbase-opensource-src and kde-workspace is enough for the libxcb-sync transition [12:08] abi didn't even changed, just some symbols were removed and that triggered the soname bump [12:15] cjwatson: oh, it migrated anyway [12:17] happyaron: should I sponsor bug 1266520, or are you on it? (also relevant for Debian) [12:17] bug 1266520 in ibus-pinyin (Ubuntu) "ibus-setup-pinyin aborts with ImportError" [High,Triaged] https://launchpad.net/bugs/1266520 [12:41] mlankhorst: give us a ping if there's a change to be merged into kde-workspace packaging branch [12:44] hello, I see nothing difference between 13.10 and 14.04 for the moment [12:44] at least your system isn't broken :P [12:45] * ogra_ sees massive differences ... on his phones and tablets :) [12:46] hello, I see nothing difference between Ubuntu and OS X for the moment [12:46] * mitya57 hides [12:46] we have a modern bash version [12:46] mitya57, you forgot to mention the versions :P [12:47] Riddell: ok [12:47] And gcc :P [12:47] Riddell: no change rebuild incoming :P [12:47] is it normal that the ubuntu sound is lower at starting dvd? [12:48] streulma, see the channel topic, this is no support channel, please go to #ubuntu for support [12:48] the tamtam is different from earlier versions [12:48] I speak about trusty :p [12:48] try #ubuntu+1 [12:48] right [12:52] mlankhorst: got a debdiff? [12:53] https://launchpad.net/ubuntu/+source/kde-workspace/4:4.11.5-0ubuntu2 somewhere [12:54] :) === MacSlow|lunch is now known as MacSlow [13:36] doko: ping [13:52] tjaalton, mlankhorst: is https://code.launchpad.net/~mitya57/ubuntu/trusty/xkeyboard-config/2.10.1-1ubuntu1/+merge/200141 something you want to handle in your team? (e. g. a two-way merge with Debian, some of our changes are useful for Debian as well) [13:52] I thought xkeyboard was generic low level stuff, not x specific? [13:53] I don't know -- it's just a question [13:53] I'm happy to review/sponsor it, too [13:54] hmm, could push some of that to debian [13:55] mlankhorst: it's on package-status.html, and x-swat is sub'd to the bugs ,) [13:55] ;) [13:56] well if you want to take it [13:56] I didn't forward my changes to Debian because I prefer to get them applied upstream first [13:57] erm for debian the changes should go into upstream first, because of policy :P [13:57] Didn't know about that, but I agree :) === timrc-afk is now known as timrc [13:58] i'm fine with pushing the merge to trusty as-is [13:59] but stuff like multiarch and split xkb-data-i18n could probably be used by debian as well [13:59] yeah [13:59] mitya57: are you a member of pkg-xorg on alioth? [13:59] I'm testing why I get a kernel panic with nouveau from time to time atm [13:59] tjaalton: No :( [13:59] mitya57: it's trivial to get accepted [13:59] Please push it yourself if you can (and agree with the changes) [14:00] sure [14:00] but we host our git branches there as well [14:01] so you could just merge there and directly ask us to sponsor (we're on #ubuntu-x) [14:01] in the future I mean :) [14:01] ok, will know [14:02] yeah git is preferred :) [14:04] pitti: thanks for sponsoring all my packages! [14:06] mitya57: yw! [14:08] mlankhorst, just ask [14:09] doko: how do I use hardening-wrapper in xorg-server? [14:09] mlankhorst, ugh ... never did use this. maybe ask jdstrand or mdeslaur? [14:10] mlankhorst: sbeattie can provide guidance when he arrives [14:12] tjaalton, mitya57: ok, not touching xkeybaord-config then? [14:12] pitti: nah feel free to [14:12] ack [14:22] pitti: don't know who is responsible for platform-api ... but it sits in component-mismatches, and I doubt we want lcov in main [14:25] hallyn: https://code.launchpad.net/~raharper/qa-regression-testing/scripts-test-qemu-fixups -- this passes all 22 tests on a trusty vm -- I'm going to run against the previous releases next to make sure I didn't regress any tests [14:27] doko: that was tvoss, I think [14:30] rharper: awesome, thanks [14:30] np [14:30] hallyn: once I confirm I didn't regress, should I propose for merging ? [14:31] rharper: yeah that'd be good [14:31] cool [14:31] rharper: we can ask whether jdstrand wants to review it, if not I *think* I can merge it [14:32] ok [14:32] jdstrand: speaking of reviews, who should I be bribing^Wasking about getting a security review of the cgmanager package at lp:~serge-hallyn/+junk/cgmanager ? [14:33] jdstrand: aside from a security review of the code,I'd also like to re-review the design to discuss whether I'm opening up any possibilities for unprivileged users to abuse privileged ones [14:34] jdstrand: so if anyone from security team will be in london we could do it in person there perhaps [14:34] re that merge> isn't that going to fail on earlier releases? [14:34] pitti: colord hint bumped. Is there a Debian bug, or anyone with an urge to fix it? :P [14:35] hallyn: re cgmanager> probably sarnold (code mostly) and mdeslaur (design mostly) [14:35] hallyn: we won't be [14:35] infinity: thanks; RAOF looked into it recently, but there's still one failure left (no bug ATM) [14:36] jdstrand: I haven't looked at the merge proposal yet for qrt [14:36] rharper (and hallyn): it seems the test-qemu.py fixes need to be made trusty-specific and remain unchanged for earlier releases. we use these scripts for security updates [14:36] jdstrand: thanks, I'll ping them both then [14:37] jdstrand: rharper: right, so the changes need to be put under checks for the lsb_release, as is done throughout that file (and in http://people.canonical.com/~serge/qrt-qemu.diff) [14:37] biab [14:38]