[03:55] <sarnold> rbasak,teward, https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1262710/comments/6 -- I sure hope "please add a new binary package" isn't too large a hurdle for nginx. the core code looked really good.
[04:35] <teward> sarnold, the source of the problems will be the large number of users who have come to rely on the non-core modules.
[04:35] <teward> sarnold, that, and you're basically asking for a duplicate of upstream's repository
[04:35] <teward> which is broken at that
[04:35] <teward> s/broken/in violation of many policies/
[04:36] <sarnold> teward: those users can continue to rely upon the universe-supported package
[04:36] <sarnold> teward: I'd be content to support nginx-tiny if it dropped 'echo' -- if that's the easiest way to get nginx in main, that's fine by me.
[04:37] <teward> sarnold, as an aside, "those users" consists of a very large portion of the userbase of the debian packages, by my observations.
[04:37] <sarnold> teward: that's fine :)
[04:37] <sarnold> teward: they all use universe packages now..
[04:38] <sarnold> teward: .. and they can continue to use universe packages if they wish.
[04:38] <sarnold> teward: but we need some clear demarcation between what we can and can't support, and whatever we -can- support should go into 'main'.
[04:38]  * teward yawns
[04:40] <teward> sarnold, agreed, but i'm already imagining there being people being... I think the correct wording is "extremely displeased to an uncivil degree" if we drop, and Debian already has a... "poor view" of Ubuntu's support for nginx as it is.
[04:40] <teward> earliest i'd be starting to work on this is... what, saturday, I think...?
[04:40] <teward> i'm kinda busy with the new job so meh
[04:40] <sarnold> teward: I'm not saying -drop- the package -- I just want one new binary package with nothing but upstream nginx code. :)
[04:40] <teward> speaking of which, i need to get some sleep...
[04:41] <sarnold> teward: oh cool! congratulations :)
[04:41] <sarnold> teward: good night :)
[04:41]  * sarnold -> dinner
[04:42] <teward> sarnold, when you return, poke around at the nginx.org debian repository and look there.  that's upstream-only code, but that package breaks policies and user-friendliness
[04:42] <teward> sarnold, if the code base there is more to your liking I can *try* and replicate the admin-friendliness of nginx that the Debian packages have in a separate binary
[04:42] <sarnold> teward: ahhhhhh I think this might explain some of the disconnect...
[04:43] <sarnold> teward: I just hope that we can add a new paragraph to debian/control for a new nginx-upstream package, add a new debian/nginx-upstream.install file with a few paths, and get this thing done right quick :)
[04:43] <sarnold> I'm hoping the debdiff is ~75 lines, tops.
[04:43] <teward> probably gonna be higher than that
[04:44] <sarnold> probably, I'm always too optimistic :)
[04:44] <sarnold> teward: anywa, you need sleep ad I need food. :) have fun at the new job!
[04:44] <teward> sarnold, you're probably looking at the entire debian/ folder, butchered up from Debian, minus the third-party modules, plus the Ubuntu specific branding, and me slicing and dicing the debdiffs around to get something functional
[04:44] <teward> but by that point even I wouldn't run that :P
[04:44] <teward> not without MASSIVE amounts of testing
[04:44] <sarnold> haha
[04:44]  * teward volunteers YOU to run the testing :P
[04:45] <sarnold> oh believe me, we'll need some test cases. i'm sure I'll be writing plenty of tests.
[04:45] <sarnold> supporting this thing for five years ain't going to come cheap :)
[04:45] <teward> bleh, i've got enough crap with high-level sec reviews of 20 or so system updates for the *shudders* windows systems at work
[04:45]  * teward shivers
[04:45] <sarnold> teward: ugh. my condolances.
[04:46] <teward> sarnold, FORTUNATELY i only have to deal with the dell deployment appliance.  it's still windows though, so eurgh
[04:46] <teward> ANYWAYS
[04:46] <teward> good night
[04:46] <sarnold> eurgh indeed :)
[04:46] <sarnold> goodnight, thanks!
[04:46] <teward> sarnold, and forgive me if, say, i start condemning you over the next few days as i butcher down debian's debian/ directory a bit... that's no small feat.
[04:47] <teward> (and it's necessary to maintain the sites-available / sites-enabled admin friendliness that already exists in universe)
[05:08] <infinity> teward: What would be wrong with just dropping 'echo' from nginx-light and calling it done?  Or is that somehow required to make the other bits work?
[05:20] <pitti> Good morning
[07:10] <pitti> shadeslayer, Riddell, apachelogger, debfx_: just to triple-check, Kubuntu is not using jockey any more, but u-d-common, right?
[07:10] <pitti> I'm going to remove jockey from trusty
[07:11] <pitti> Task: kubuntu-active
[07:11] <pitti> is that still relevant?
[07:49] <dholbach> good morning
[08:06] <cff> Is Qt 4.8.x available in Ubuntu 12.04.x ?
[08:06] <cff> ubuntu backports, canonical qt edgers, ubuntu sdk ppa, don't have it
[08:07] <didrocks> cff: seems to be 4.8.5
[08:07] <cff> didrocks: where?
[08:08] <didrocks> on 14.04
[08:08] <cff> didrocks: I'm asking in 12.04
[08:08] <didrocks> not sure that we backport Qt on 12.04
[08:08] <cff> http://packages.ubuntu.com/precise-backports/allpackages no qt here
[08:09] <didrocks> cff: you can see the version of Qt4 for all supported ubuntu releases here: https://launchpad.net/ubuntu/+source/qt4-x11
[08:10] <didrocks> so, it's 4.8.1 in precise
[08:10] <infinity> We don't tend to backport libraries like that.  It's just asking for trouble.
[08:11] <infinity> If there's a reason you need bleeding edge versions, you likely don't want to be running an LTS.
[08:18] <apachelogger> pitti: kubuntu-active isn't built right now I think, and yes, jockey was replaced by kubuntu-driver-manager; good to remove
[08:18] <cff> alright thanks
[08:18] <pitti> apachelogger: thanks
[09:08] <soren> mdeslaur: A quick heads up: curl has a unit test that fails since Feb 1st, due to a cookie timing out on that day, so for the next security update, you'll need to update that as well.
[09:09] <soren> mdeslaur: I just spent way too much time thinking I caused a unit test to fail only to realise it also failed without my patch applied. I thought I'd save you the same trouble since you seem to be the one who does most of the curl security updates.
[09:23] <pitti> cjwatson: does https://code.launchpad.net/~pitti/britney/britney2-autopkgtest-fixes/+merge/208657 look sane, or would that need a different approach? (first time I looked at britney admittedly, some state keeping is rather confusing)
[09:41] <rbasak> sarnold: it seems reasonable, though I suppose we need an FFe now. Thank you for the review!
[09:46] <rbasak> teward: ^^ - let's chat about this when you're next online. Note that I'm away Mon-Wed next week.
[09:52] <ogra> doko, i see you added a new dep on libtasn1-6, but  it seems there was no older dep dropped (see http://people.canonical.com/~ogra/touch-image-stats/20140228.changes) is that wanted ?
[10:01] <doko> ogra: libtasn1-3-dev is now built form libtasn1-6
[10:02] <doko> not sure why libtasn1-3 wasn't there before
[10:08] <ogra> doko, it still is there i was just expecting it to be traded for the new binary (there are no "dropped packages" in the list as there usually are in transitions)
[10:12] <Laney> oh, we got 1-6 in main, cool
[10:13] <cjwatson> pitti: I haven't reviewed it quite yet, planning to look today.  I don't want to give a knee-jerk opinion as I'll need to stare at the context for a while
[10:13] <Laney> there was something we had a delta on to keep it at 3. /me tries to remember what that was
[10:13] <cjwatson> pitti: Thanks in advance of review for diving into that though :)
[10:13] <pitti> cjwatson: ack; yes, no knee-jerk patches into britney :)
[10:13] <Laney> p11-kit
[10:13] <pitti> cjwatson: next week I'll look into fixing that "binary taken over by new source" bug (the gccgo-4.9 fun that we had)
[10:14] <pitti> cjwatson: but I wanted to start with something easier first
[10:27] <tkamppeter> mdeslaur, hi
[10:45] <xnox> cjwatson: if a package drops things into /etc/default/grub.d does it need to do anything special to trigger "update-grub" or do grub packages have file trigger for those? (looking quickly through triggers, i don't see one)
[10:45] <xnox> cjwatson: or should one just do "update-grub || true" in postinst? (given that grub might be installed, but not in use)
[10:59] <cjwatson> xnox: Just conditionally do update-grub like lupin-support.postinst does, I think
[10:59] <xnox> cjwatson: thanks for pointer.
[11:10] <pitti> hm, did anyone see this error with the new kernel already?
[11:10] <pitti> In file included from ../src/core/socket.c:32:0:
[11:10] <pitti> /usr/include/x86_64-linux-gnu/sys/xattr.h:31:3: error: expected identifier before numeric constant
[11:10] <pitti>    XATTR_CREATE = 1, /* set value, fail if attr already exists.  */
[12:17] <mdeslaur> soren: cool, thanks!
[12:17] <mdeslaur> tkamppeter: hi!
[12:21] <mdeslaur> tkamppeter: ah, got your email, thanks
[13:48] <xnox> plars: psivaa: server images should be back to green. By the way, why are floodlight jobs not triggered? the referenced bug was fixed, no?!
[13:50] <psivaa> xnox: thanks for the server image fix. floodlight was disabled as per server team request. let me see the exact convo
[13:52] <xnox> psivaa: if it's disabled, why is it (a) red, (b) published on jenkins.qa.ubuntu.com ?
[13:52] <psivaa> xnox: <jamespage>     psivaa, where do I find the utah smoke tests again? going to convert the floodlight test into a DEP-8 test instead
[13:52] <psivaa> psivaa, https://code.launchpad.net/~james-page/ubuntu-test-cases/server-drop-floodlight/+merge/196511
[13:52] <xnox> psivaa: maybe i'm looking at the wrong views?
[13:53] <xnox> psivaa: ah, sounds excellent! can it be cleaned up from jenkins.qa.ubuntu.com (trusty series at least)?
[13:53] <xnox> psivaa: or do a last green run ;-)
[13:53] <psivaa> xnox: http://ci.ubuntu.com/smokeng/trusty/server/amd64/20140228/6872/ is the right place. but i'll report a ticket to clean up floodlight
[13:54] <xnox> psivaa: ok, thanks! will bookmark those pages then.
[14:43] <Saviq> jibel, hey, I saw you were enabling some autopkgtests for uitk, I was wondering recently - we have a bunch of QML UI tests that we only run on CI on a real machine these days, I'd love to put that into autopkgtest, but they require OpenGL, is that something we could get with xvfb via gallium / llvm / whatever-its-called?
[14:47] <xnox> Saviq: ubuntu-emulator-runtime runs under xvfb with gallium on cloud instances / virtual machines, and it requires gl accelaration.
[14:47] <ogra> urgh
[14:48] <brendand> dholbach, hey - do you have any idea how to create a mailing list on lists.ubuntu.com?
[14:49] <xnox> Saviq: libgl1-mesa-glx, xvfb, xinit is all you need I believe.
[14:50] <Saviq> xnox, ok, I tried that locally recently, didn't seem to work - will try again :)
[14:50] <Saviq> xnox, thanks for the confirmation that it should
[14:50] <xnox> Saviq: best boot into ubuntu-desktop livecd in a VM. that should have all the gallium bits, et. al. and try running the tests there.
[14:50] <xnox> Saviq: distilling down from that should be easy.
[14:51] <xnox> Saviq: oh, for some tests we had to increase the default xvfb screenresolution and pixel depth.
[14:51] <Saviq> xnox, good to know
[15:00] <jibel> Saviq, as xnox said you need libgl1-mesa-glx and set screen to a minimum of 1024x768x24, by default xvfb uses 800x600x8 IIRC
[15:01] <xnox> jibel: should we just bump xvfb default, no a more reasonable default?! the world has moved on from 800x600x8....
[15:02] <jibel> xnox, it is even worst than that, the default is 640x480x8
[15:36] <jibel> bdmurray, any opinion about bug 1286161? it looks like a real issue but first time I see it from S to T
[15:40] <bdmurray> jibel: this looks suspcious Unpacking udev (204-5ubuntu11) over (204-0ubuntu19.1) ...^M
[15:40] <bdmurray> Preparing to unpack .../libblkid1_2.20.1-5.1ubuntu14_amd64.deb ...^M
[15:41] <bdmurray> jibel: whoops, sorry its still early
[15:43] <dholbach> brendand, https://wiki.ubuntu.com/MailingLists#Requesting_a_list
[15:52] <guest6019532> hello
[15:52] <guest6019532> i came here because of the following bug:
[15:52] <guest6019532> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/932834
[15:53] <guest6019532> is anyone here who could comment on this? is there any chance this bug could be fixed for trusty (14.04)?
[15:53] <guest6019532> some more info:
[15:53] <guest6019532> http://www.webupd8.org/2013/03/install-pulseaudio-with-built-in-system.html
[15:53] <guest6019532> https://sites.google.com/site/nevion/projects/qpaeq
[15:54] <guest6019532> http://ubuntuforums.org/showthread.php?t=1378087
[15:54] <guest6019532> it would be much appreciated
[15:55] <seb128> guest6019532, you can try to talk to TheMuso, but he's based in Australia and it's friday night there, so maybe better to try next week either earlier or later in the day
[15:59] <guest6019532> seb128: thx for your reply. i already approached TheMuso in #ubuntu-accessibility a few minutes ago. but he didn't reply.
[15:59] <seb128> guest6019532, it's 3am for him, he's probably sleeping
[16:00] <Laney> You could also email him
[16:01] <seb128> or that
[16:07] <guest6019532> seb128: ok, thx anyway
[16:07] <seb128> yw
[16:08] <guest6019532> Laney: to see email adresses on launchpad, one needs to log in first, as far as i can see. however, i am not registered on launchpad ;p
[16:08] <Laney> guest6019532: <username>@ubuntu.com works for ubuntu members
[16:09] <guest6019532> Laney: ok, thx
[17:01] <Saviq> xnox, jibel, so with xvfb-run I'm getting:
[17:01] <Saviq> libGL error: failed to load driver: swrast
[17:01] <Saviq> Could not initialize GLX
[17:01] <Saviq> and crash
[17:02] <Saviq> even though unity itself runs under gallium in the VM where I'm trying that
[17:02] <Saviq> ah
[17:03] <Saviq> xnox, jibel, unping, seems the resolution/colorspace change helps
[17:06] <jibel> Saviq, yes, without a depth of 24 it fails with Error: couldn't get an RGB, Double-buffered visual
[17:06] <Saviq> jibel, awesome, we're getting somewhere, thanks!
[17:19] <xnox> Saviq: start with trying to run "glxinfo" and nux_test utilities, to make sure they say it's all good.
[17:20] <Saviq> xnox, yup, that's what I did, even managed to get it to load gallium on my nvidia
[17:20] <xnox> Saviq: excellent.
[17:20] <Saviq> xnox, so all looks great, we'll be having some new autopkgtest soon :]
[18:59] <pranith__> Hi, can someone help me in packaging the latest GNU global package for Ubuntu 14.04? The package in debian is 6 years old and the maintainer is not interested in packaging the latest upstream because of some issues
[19:01] <Noskcaj> pranith__, link the bug you made
[19:01] <Laney> why do we want the issues in Ubuntu?
[19:02] <pranith__> upstream debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574947
[19:03] <pranith__> ubuntu bug: https://bugs.launchpad.net/debian/+source/global/+bug/1275029
[19:15] <pranith__> what is the front-end package which I need to use with bzr-fastimport?
[19:15] <pranith__> on 12.04 I get an error of no such package for front-end
[20:21] <ockham> hi, i'm trying to set up a sid pbuilder under saucy, but it fails with
[20:21] <ockham> Err file: saucy/ Packages
[20:21] <ockham>   File not found
[20:22] <ockham> ~/.pbuilderrc is at http://paste.ubuntu.com/7012360/
[20:22] <ockham> can anyone help?
[20:24] <sarnold> ockham: you can take raring out of your UBUNTU_SUITES -- it's EOL -- but that likely won't fix your problem, which I can't spot. good luck :)
[20:24] <ockham> sarnold: thx
[20:43] <ockham> i think i found it. i had to touch /var/cache/archive/sid/Packages and /var/cache/archive/sid/Sources
[23:55] <teward> sarnold, when yo uwake up, or are not busy, ping.
[23:55] <sarnold> hey teward :)
[23:56] <teward> sarnold, wrt nginx and the mir, would you want a separate source package, or an nginx-tiny added to the existing source to build an upstream-core-modules-only binary that would get into main?
[23:56] <sarnold> teward: existing source package would be great
[23:56] <teward> that makes my work considerably LESS evil
[23:57] <teward> it's easier to add to the current debian/ than it is to trim down the current debian/ and still make everything work xD
[23:57] <sarnold> teward: oh absolutely
[23:58] <sarnold> teward: I just need some clear demarcation for the users about which modules we can support and which modules we can't support. I certainly don't want to discard all the hard work you've put into the package over the years :)
[23:58] <teward> sarnold, debian put the effort into the package :p
[23:58] <teward> not me
[23:58]  * teward has only been on this for about a year with the PPAs
[23:58] <sarnold> teward: do you think debian upstream would be willing to accept these changes too? it'd also be nice to avoid an ubuntu delta here
[23:59] <teward> sarnold, if by "upstream" you mean "debian"
[23:59] <sarnold> teward: oh no, I know you've put work into it :P
[23:59] <teward> then ask Debian
[23:59] <teward> i have no say in what debian does/doesn't do
[23:59] <teward> i just yell things at them and they sometimes listen xD
[23:59] <sarnold> :)D