[00:02] <Riddell> mdeslaur: new qt security debdiffs on bug 1259577
[01:36] <mdeslaur> Riddell: awesome, thanks, I'll take a look tomorrow
[05:15] <pitti> Good morning
[08:28] <dholbach> good morning
[08:56] <xnox> is there a way to query all mailing list subscriptions for lists.ubuntu.com of a given email address?
[08:56] <xnox> maybe barry ^
[09:09] <rbasak> xnox: it is possible to change the settings for all subscriptions all at once, if that's what you're after. You can do that from any single control page.
[09:10] <xnox> rbasak: ok, thanks.
[09:57] <tseliot> didrocks: just FYI the new nvidia-prime is trusty
[09:58] <didrocks> tseliot: ok, so we have a mismatch with bbswit*
[09:58] <tseliot> didrocks: mismatch?
[09:59] <didrocks> tseliot: bbswitch needs to be promoted, right?
[09:59] <tseliot> didrocks: yep
[09:59] <tseliot> ok, so that kind of mismatch
[09:59] <didrocks> tseliot: I'll do it once I have a second
[09:59] <didrocks> yep ;)
[09:59] <tseliot> didrocks: ok, thanks a lot :)
[09:59] <didrocks> yw!
[10:14] <didrocks> tseliot: promoted btw :)
[10:14] <tseliot> didrocks: thanks again :)
[10:14] <didrocks> yw!
[10:24] <psivaa> pitti: cjwatson: I remember you were discussing the fix for bug 1256695 in terms of permissions etc..
[10:25] <psivaa> We now have an issue as stated in bug #1258245 impacting the VM provisioning in the smoke tests
[10:25] <psivaa> Would help if you could have a look when you have some time
[10:25] <pitti> psivaa: that doesn't sound like a regression, though?
[10:25] <pitti> the syslog user has never been meant to be in the dialout group
[10:26] <psivaa> pitti: but i guess rsyslogd was not run as syslog in the past? (before the big upgrade of rsyslog in trusty)
[10:26] <pitti> psivaa: ah, right
[10:44] <lifeless> cjwatson: btw, I probably won't be able to follow through and test that grub2 recogniser test; due to running out of space I've had to replace the system with one with more drive bays and migrate everything over
[10:45] <lifeless> cjwatson: I'll see if I can give it a spin before I complete the migration, but keeping home systems up is likely going to take priority
[10:46] <cjwatson> lifeless: which one is that, sorry?
[10:46] <cjwatson> the dmraid striping thing?
[10:48] <lifeless> cjwatson: failing to recognise mdadm when the end of the partition isn't accessible (but none of the needed data is above the 2TB mark)
[10:48] <lifeless> so the layers don't come in and the kernel etc aren't accessible
[10:49] <cjwatson> oh, right, that
[10:50] <lifeless> yeah, 'that' :)
[10:50] <lifeless> aka robert likes finding corner cases
[11:36] <doko> cjwatson, about lockdev. not sure if I should care about a symbols file, hardening defaults, things like cross buildability, if we demote it anyway in the future?
[11:40] <cjwatson> Oh, I didn't see Roger's comment
[11:40] <cjwatson> Yeah, probably not a big deal then
[11:54] <Riddell> tseliot: ping
[11:54] <tseliot> Riddell: pong
[11:54] <Riddell> tseliot: I'm looking at nvidia-persistenced  in New which seems to have been overlooked for over a month, were there problems with it?
[11:55] <Riddell> tseliot: how come it's Section: contrib/x11 ?
[11:55] <Riddell> tseliot: there is a COPYING file which says GPL but all the individual files give an MIT type licence, any idea why?
[11:56] <tseliot> Riddell: not really, I made the changes requested by the review but nobody reviewed it again
[11:56] <tseliot> Riddell: let me check...
[11:59] <tseliot> Riddell: ok, I can fix the licence and the section (it's really a tool as much as nvidia-settings)
[12:00] <Riddell> tseliot: I take it the COPYING file was added by upstream?
[12:01] <tseliot> Riddell: yep https://github.com/NVIDIA/nvidia-persistenced
[12:01] <Riddell> tseliot: stuff in common-utils/ is GPL so I guess you need two blocks in debian/copyright  one for Files: * as GPL  and one for Files: list-each-file  as MIT
[12:02] <Riddell> tseliot: lovely, I'll reject this, fix those and I'll accept
[12:02] <tseliot> Riddell: ok, thanks
[12:03] <tseliot> Riddell: oh, and shall I keep the COPYING file?
[12:03] <Riddell> tseliot: yes it realates to any file which doesn't list itself as MIT I guess
[12:06] <tseliot> Riddell: ok, thanks
[12:27] <doko> pitti, jibel: I hear that the debian buildds use ekeyd-egd-linux for some entropy. not sure if we use it on our buildds. but maybe you want to use it for the autopkgtests, instead of disabling all failing tests ...
[12:28] <pitti> doko: I already tried with haveged, I don't think it's missing entropy; I think it's because the VM doesn't have a fine enough clock resolution to guarantee that 1.000 UUID1 generated in a row are actually unique
[12:28] <pitti> doko: (I wrote some details a few days ago)
[12:30] <doko> ok
[12:35] <doko> zul, your neutron upload waits for a MIR for python-psutil
[12:39] <KoalaYeung> Hello
[12:40] <KoalaYeung> Anybody here  knows how to make an Ubuntu Software Center with an image icon?
[12:44] <infinity> jamespage: Yo.  Two days ago, you mangled libusbx to wiggle build-deps around.  The bug you referenced was bogus.  Can you remember what the actual issue was?
[12:50] <infinity> jamespage: Oh, I'm guessing because older dpkg-buildpackage called "build" instead of "build-arch".  But do you really need to backport libusbx?
[13:01] <jamespage> infinity: sorry - I had to many bug windows open that day
[13:01] <jamespage> infinity: yes that was the issue
[13:02] <infinity> jamespage: So, more to the point, WHY is it an issue?  Why do you care if the source can be backported unmodified to a previous release?
[13:02] <infinity> jamespage: (I'm asking because I just ran into that build-dep being wrong during a bootstrap and it annoyed me :P)
[13:03] <infinity> So, I fixed it, and when I went to document it in the changelog, I realised it was a delta you'd added only two days earlier...
[13:03] <jamespage> infinity: urgh - sorry
[13:03] <xnox> infinity: cloud-archive? but then again why would it be using libusbx....
[13:03] <jamespage> have to duck out for a bit; lets discuss when I get back
[13:03] <jamespage> but yes cloud archive
[13:03] <jamespage> xnox, qemu I suspect
[13:04] <infinity> Surely, cloud archive has modified backports in it.  Trying to support crusty old build tools forever isn't fun.
[13:06] <infinity> Anyhow, I've worked around it locally for now anyway, it's just irritating. :P
[13:34] <zul> doko:  ping python-psutil had a MIR previously but its universe now, i filed a new one https://bugs.launchpad.net/ubuntu/+source/python-psutil/+bug/1259928
[13:34] <sergiusens> jamespage, this is just speculation, but I can't seem to build packages that use dh_golang with the latest go
[13:34] <sergiusens> saw you uploaded 1.2
[14:41] <smoser> hey.
[14:41] <mdeslaur> xnox, zul: can one of you please merge samba 4.0.13?
[14:41] <smoser> can someone verify for me  https://launchpad.net/ubuntu/+source/euca2ools/3.0.2-1/+build/5321133
[14:41] <smoser> i think that is dependency wait because python-requestbuilder is not in main ?
[14:41] <smoser> in the past i would have thought that would still build and go in and then appear in component-mismatches.
[14:41] <xnox> mdeslaur: please, not me.
[14:41] <mdeslaur> xnox: sure. zul, you're it! :)
[14:42] <xnox> mdeslaur: and did you mean 4.0.13, or 4.1.3?
[14:42] <zul> mdeslaur:  sure
[14:42] <xnox> mdeslaur: zul: there is 4.1.3 in NEW
[14:42] <xnox> zul: mdeslaur: important packaging fixes, I see.
[14:42] <xnox> and CVEs....
[14:43] <cjwatson> smoser: no, in the past it would have done just the same thing
[14:43] <zul> xnox:  ill either get to it today or tomorrow but its on my todo list
[14:43] <xnox> cool.
[14:43] <cjwatson> smoser: you're thinking of run-time dependencies, not build-dependencies
[14:43] <mdeslaur> yeah, I'm good with either 4.1.3 or 4.0.13
[14:43] <smoser> cjwatson, ok. so i need to request MIR for python-requestbuilder ?
[14:43] <mdeslaur> zul: cool, thanks.
[14:43] <cjwatson> smoser: yes
[14:45] <smoser> cjwatson, thanks.
[14:49] <barry> xnox: yes.  looks like rbasak answered your question!
[14:49] <xnox> barry: cheers ;-)
[14:54] <jamespage> infinity: unmodified backports == 0 work; which is why we have been trying to push un-intrusive changes back into trusty; this is probably not one of those - that was my bad
[14:55] <jamespage> sergiusens, hmm - I'd hope not - that was a merge from Debian
[14:55] <jamespage> but its quite possible
[14:55] <jamespage> infinity: I'll revert my delta and hold it in the cloud-archive instead if that makes your life easier
[14:55] <sergiusens> ok, I'll dig into it
[14:59] <jamespage> sergiusens, do you have a build log?
[14:59] <jamespage> for a failuer
[15:02] <seb128> slangasek, cjwatson: bug #1185092 ... should we still do what Steve suggested ("the new libgtksourceview-3.0-common to Conflicts/Replaces libgtksourceview-3.0-0, to hint the upgrade.")?
[15:03] <seb128> e.g is that useful for LTS upgrades, or was that only a saucy thing?
[15:03] <cjwatson> TBH I can't quite remember the differences between within-release upgrades with update-manager and full between-release upgrades
[15:03] <cjwatson> I would default to assuming it's useful across the board
[15:04] <seb128> ok, it doesn't hurt to have it in any case
[15:04] <seb128> I'm going to add that to the upload I'm about to do
[15:04] <cjwatson> ok, thanks
[15:04] <seb128> yw
[15:05] <sergiusens> jamespage, http://paste.ubuntu.com/6556395/
[15:21] <Cimi> seb128, cannot reproduce https://bugs.launchpad.net/ubuntu/+source/overlay-scrollbar/+bug/1086494
[15:22] <seb128> Cimi, it happens to me 1 every few times I do "gedit something" where something is a document with enough content to scroll
[15:22] <Cimi> ok
[15:22] <Cimi> let me try
[15:22] <seb128> like start/close it in loop for a few times
[15:23] <Cimi> seb128, not happening :-\
[15:23] <seb128> that's a timing thing, it might not happen often for you
[15:23] <Cimi> seb128, ok now after 4th time
[15:23] <Cimi> seb128, thx
[15:23] <seb128> yw
[15:36] <sergiusens> jamespage, just tried to sbuild on sid; same results
[15:44] <Cimi> seb128, I think the patch breaks another thing
[15:44] <Cimi> seb128, if you change overlay mode
[15:44] <seb128> Cimi, like?
[15:45] <Cimi> from overlay-auto to normal
[15:45] <Cimi> in dconf
[15:45] <seb128> oh, I didn't test that
[15:45] <Cimi> the scrollbar does not work anymore
[15:47] <seb128> Cimi, well, you are welcome to find a better fix for the warnings ;-)
[15:58] <Cimi> seb128, that branch does not fix the warning
[16:00] <Cimi> what it does it hiding the widget when the scrollbar mode changes
[16:00] <Cimi> so might have just been good luck
[16:01] <seb128> Cimi, well, I get those warning 15 times a day and I didn't get any in 10 days since I'm running it, so whatever it's doing makes the warning goes away as well
[16:01] <Cimi> seb128, try reverting overlay scrollbars
[16:02] <Cimi> seb128, it does not make sense this branch
[16:02] <seb128> Cimi, well, I did that yesterday and got my command line spammed with warnings again so I reinstalled it
[16:02] <Cimi> no idea why
[16:02] <Cimi> the scrollbar mode does not chsnge
[16:02] <Cimi> this function does not get called
[16:02] <seb128> well, you managed to trigger the warning as well no?
[16:04] <seb128> Cimi, well, it seems it happens at init?
[16:04] <seb128> Cimi, what function?
[16:05] <Cimi> seb128, scrollbar_mode_changed_unload_gfunc
[16:05] <Cimi> seb128, the function touched by the patch
[16:05] <Cimi> seb128, add printf ("hello world");
[16:05] <Cimi> seb128, nothing is printed, the function is not called, it cannot fix the bug
[16:08] <seb128> Cimi,
[16:08] <seb128> ** (gedit:8552): WARNING **: scrollbar_mode_changed_unload_gfunc has been called
[16:08] <seb128> Cimi, it's called (had to try 6 times, it's like the warnings)
[16:09] <Cimi> seb128, not here, weird
[16:09] <seb128> did you get the warnings?
[16:09] <Cimi> might be dconf
[16:09] <Cimi> I get the warning without the print :-\
[16:09] <seb128> I used a g_warning
[16:09] <seb128> let me try a printf
[16:09] <seb128> maybe your code eats stdout?
[16:09] <Cimi> °_°
[16:09] <Cimi> maybe
[16:12] <seb128> Cimi, right, printf doesn't work, g_warning does
[16:12] <Cimi> seb128, ok
[16:12] <Cimi> good
[16:12] <seb128> Cimi, I added both, only the g_warning is displayed
[16:12] <seb128> $ gedit overlay-scrollbar_0.2.16+r359+14.04.20131129-0ubuntu1_i386.build
[16:12] <seb128> ** (gedit:14485): WARNING **: scrollbar_mode_changed_unload_gfunc
[16:12] <seb128> (gedit:14485): Gtk-WARNING **: GtkScrolledWindow 0x8d012a8 is mapped but visible child GtkScrollbar 0x8d03480 is not mapped
[16:13] <seb128> oh
[16:13] <Cimi> seb128, I'll dig into it
[16:13] <seb128> Cimi, shrug, it's me being stupid and not having a \n in the printf
[16:13] <seb128> Cimi, your fault for giving me a line to copy without it as well
[16:14] <Cimi> ahah
[16:14] <Cimi> seb128, qml does not need \n
[16:14] <Cimi> seb128, I forgot all that
[16:14] <seb128> g_warning neither
[16:14] <Cimi> my fault
[16:14] <seb128> ;-)
[16:19] <seb128> Cimi, if you do "com.canonical.desktop.interface scrollbar-mode" this function is called/the warnings are displayed
[16:19] <seb128> ups
[16:19] <seb128> Cimi, $  gsettings reset com.canonical.desktop.interface scrollbar-mode
[16:19] <seb128> Cimi, that's an easy way to trigger it
[16:19] <seb128> it might make debugging easier
[16:20] <Cimi> seb128, it does
[16:20] <seb128> Cimi, gdb says scrollbar_mode_changed_cb calls it
[16:21] <Cimi> seb128, yep got that
[16:57] <Cimi> seb128, I think we should maintain another list with scrollbars that need to be set visible true or false
[16:57] <seb128> Cimi, list of what?
[16:57] <Cimi> seb128, we cannot call hide() like in the branch
[16:57] <Cimi> seb128, we need to keep track
[16:57] <seb128> of what?
[16:58] <Cimi> if you see lars branch
[16:58] <seb128> well, I don't know what that code is doing
[16:58] <Cimi> ok
[16:58] <seb128> but I trust you to find a solution ;-)
[17:49] <Cimi> seb128, ok I'll tell lars tomorrow, I forgot a little of those C stuff data types :)
[17:49] <Cimi> seb128, but I knw how to fix it
[17:52] <seb128> Cimi, great, thanks
[17:53] <seb128> Cimi, btw gtk 3.10 landed to trusty, we might need some theme tweak/the hack from larsu on https://code.launchpad.net/~larsu/ubuntu-themes/dont-set-all-bgs/+merge/197234 to be merged in
[17:53] <seb128> Cimi, without that stuff like infobar (e.g trash location in nautilus) don't have a background (or right click on an icon in nautilus)
[19:28] <Noskcaj> Can someone take a look at https://code.google.com/p/prpltwtr/issues/detail?id=88 and tell he how much more work needs doing for this to be release worthy in ubuntu?
[19:29] <xnox> Noskcaj: what do you mean by "release worthy" ?
[19:30] <Noskcaj> xnox, We could include it, since we used to have pidgin-microblogger, but a twitter update killed it
[19:31] <xnox> Noskcaj: as far as I can see that library is not packaged at all https://launchpad.net/ubuntu/+search?text=prpltwtr and if it's broken well no point in re-introducing it.
[19:31] <xnox> Noskcaj: pidgin is not default in most flavours, and furthermore most have other default microblogging clients.
[19:32] <Noskcaj> xnox, I would package it as a replacement, even if just in the archives, it would be nice to have a working version
[19:32] <Noskcaj> ok
[19:32] <xnox> Noskcaj: if you want to package / maintain it, please do it via Debian ITP
[19:32] <Noskcaj> of course
[19:32] <xnox> Noskcaj: then why do you ask here?! =)
[19:33]  * xnox is still confused by "release worthy" =)))))) but meh, if it's auto-synced it's auto-synced.
[19:33] <slangasek> Laney: harfbuzz> I know this problem is actually courtesy of Debian, and not your merge, but please take care that libraries in Ubuntu that rename without changing the soname use Conflicts, not unversioned Breaks (which are wrong)
[19:33] <Noskcaj> to see what would be needed to include it on the cd, like pidgin-microblogger was for my flavors
[19:34] <slangasek> Laney: update-manager can't automatically figure out what to do with such a lib... and I see this happening several times a cycle.  I'm not picking on you, just trying to spread the word bit by bit :)
[19:35] <dobey> Noskcaj: i guess you'd need to get pidgin back on the cd first :)
[19:35] <Noskcaj> dobey, I wasn't sure if ubuntu still had it, i know other flavors still do
[19:38] <xnox> Noskcaj: to be included on the cds, it needs to be available in the archive first. otherwise it's a very hypothetical discussion =)
[19:39] <xnox> Noskcaj: $ seeded-in-ubuntu pidgin
[19:40] <xnox> Noskcaj: says that pidgin is on lubuntu, ubuntustudio and xubuntu.
[20:48] <bdmurray> @pilot in
[21:25] <infinity> jamespage: I've reverted it for you. :)
[21:25] <jamespage> infinity: thankyou!
[21:25]  * jamespage goes to make a branch
[21:26] <infinity> jamespage: Is the cloud archive for precise going to keep being updated for the full 5y LTS, or is the plan to move focus entirely to 14.04 (except for security fixes, of course) once it's out?
[21:26] <jamespage> infinity: this one is the last one for 12.04
[21:27] <infinity> jamespage: Cause if the latter, I guess this isn't a problem you need to worry about much longer.
[21:27] <jamespage> its gets support until the end of 12.04 (by virtue of being based on the same packages that are in 14.04)
[21:28] <jamespage> for u-series we start the dance all over again for 14.04
[21:37] <infinity> jamespage: Right, but at least 14.04's dpkg has the arch/indep split sorted out, so no one will be moving BDI to BD to "fix" things. ;)
[21:54] <hallyn_> infinity: mvo: hi, do you guys know how sandbox-upgrader is being used (if it all) these days?
[21:56] <infinity> hallyn_: No idea.
[21:58] <hallyn_> hm
[21:59] <hallyn_> it has no rdeps...
[21:59] <hallyn_> kirkland: soren: ^ do you know where sandbox-ugprader may be in use?
[21:59] <hallyn_> guess i should jsut wait for mvo :)
[22:02] <bdmurray> hallyn_: you might ask jibel as he is looking at auto upgrade testing
[22:06] <hallyn_> rbasak: could you look at auto-upgrade-tester and sandbox-upgrader - there should be no reason why they couldn't switch from vmbuilder to your uvt right?
[22:06] <hallyn_> jibel: (please ping me if you do in fact use sandbox-upgrader or auto-upgrade-testing)
[22:15] <kirkland> hallyn_: I've never heard of it
[23:38] <xnox> Laney: looks like unity7 ftbfs with new gtk? https://launchpadlibrarian.net/159516409/buildlog_ubuntu-trusty-amd64.unity_7.1.2%2B14.04.20131106.1-0ubuntu1_FAILEDTOBUILD.txt.gz
[23:38] <xnox> or is this already being looked at.
[23:38] <xnox> ?