[00:00] i'll remove the snapshots and re-test [00:01] plars: Is it possible to get as far as a working-ish session? [00:02] cjwatson: I'm trying the various options at the moment, running in low graphics mode doesn't seem to work [00:03] stgraber, https://bugs.launchpad.net/gcc/+bug/1123588 [00:03] Ubuntu bug 1123588 in upstart (Ubuntu) " [4.7 Regression] wrong code with the fix for PR53844" [Undecided,New] [00:03] cjwatson: neither does reconfiguring [00:03] cjwatson: so no it seems [00:04] plars: OK, so this sounds to me as though we shouldn't bother respinning everything for this because it won't be a worthwhile improvement === wedgwood is now known as wedgwood_away [00:05] cjwatson: it is at one point trying to LoadModule: "vboxvideo" in the xorg log and failing to find it it seems [00:05] Ah, for details you'll need to talk to X people :) [00:05] Of which I am not one [00:05] cjwatson: ok, was the libpciaccess fix the only thing different in this image? [00:06] cjwatson: I can update the bug [00:06] plars: No, it was a general build against -proposed [00:06] slangasek: bug 1123594 [00:06] It should have been the only relevant thing, though [00:06] bug 1123594 in memtest86+ (Ubuntu) "lvm snapshots cause memtest86+.post to become defunct" [Undecided,New] https://launchpad.net/bugs/1123594 === jackyalcine is now known as zz_jackyalcine [00:13] ogasawara: Do you think you could add specific directions to either https://wiki.ubuntu.com/PrecisePangolin/ReleaseNotes/UbuntuDesktop#LTS_Hardware_Enablement_Stack or https://wiki.ubuntu.com/Kernel/LTSEnablementStack (or possibly both) about how to opt into the kernel and X enablement stacks on upgrade? [00:14] I just noticed it says "the appropriate meta package" and the like but doesn't actually give commands or specific package names [00:24] that's interesting; first time I'd read about the HES; I guess that means that bugs found relatively late in Quantal kernel/X become more important because their about to find their way into LTS [00:26] penguin42: for 12.04.3 it'll be raring-based (3.8) [00:29] cjwatson: Yes; I'm just thinking that there has been a tendency to worry more about fixing something in an LTS because it's going to have to stay for the long run, but a bug in a non-LTS might not be SRUd for example [00:30] it might also make bug triage interesting to try and figure out which series people are actually running when they say it works/fails for them on precise === zz_jackyalcine is now known as jackyalcine === jackyalcine is now known as jackyalcine_ === jackyalcine_ is now known as zz_jackyalcine [01:31] jdstrand: qemu with spice build-dep has been dput'ed [02:05] hallyn: ack === Logan__ is now known as Logan_ === zz_jackyalcine is now known as jackyalcine [04:18] hi i need a help [04:18] i bzr branched a source of gnome-power-manager [04:19] but when im going to build it it gives error althoug i do it on original source (with out any change) [04:19] can anybody help me? [04:34] Dedunu: which error?, when compiling software you must ensure you have all the dependencies satisfied [04:41] debian/rules:6: /usr/share/gnome-pkg-tools/1/rules/uploaders.mk: No such file or directory [04:41] debian/rules:7: /usr/share/gnome-pkg-tools/1/rules/gnome-get-source.mk: No such file or directory [04:41] make: *** No rule to make target `/usr/share/gnome-pkg-tools/1/rules/gnome-get-source.mk'. Stop. [04:41] dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2 [04:41] debuild: fatal error at line 1350: [04:41] dpkg-buildpackage -rfakeroot -d -us -uc -S failed [04:41] bzr: ERROR: The build failed. [04:41] chilicui1: error is like this [04:41] i havent created a chroot enviroment is that the problem? [04:46] Dedunu: did you run $ apt-get build-dep before ? , how did you found that problem?, did you use $ dpkg-buildpackage -rfakeroot -us -uc #to compile it? [04:47] Dedunu: no, it should work in your system if you meet all the dependencies, the pkg you're trying to compile is the same version of the you current ubuntu setup?, I mean, it may be a little be harder to compile a pkg which is suppose to be installed in ubuntu raring from ubuntu precise [04:48] ah is that so [04:48] i used bzr builddeb [04:49] i installedpackaging-dev [04:49] packaging-dev [04:51] Dedunu: mm, it's ok, bzr builddeb runs dpkg-buildpackage, so now just be sure you installed the dependencies.., $ apt-get build-dep #also as you've already told.., you branched.., therefore the code you're trying to run should be run against a raring machine, please be sure to compile it in that environment, otherwise the deps may not be the versions you need [04:51] cjwatson: I updated both https://wiki.ubuntu.com/PrecisePangolin/ReleaseNotes/UbuntuDesktop and https://wiki.ubuntu.com/Kernel/LTSEnablementStack with instructions for how to opt into (ie manually install) the kernel and X enablement meta pkgs [04:52] chilicui1: ok thank you [04:52] ill try on raring environment [04:52] thanks a lot [04:52] Dedunu: have fun, good luck [04:56] Good morning [04:58] good morning === zequence_ is now known as zequence [07:56] good morning === smb` is now known as smb === shuduo is now known as shuduo_afk [08:04] dholbach: hi [08:05] all the day im struggling with a [08:05] papercut [08:05] i found the bug in that fixed it on code [08:05] but i can't build it yet [08:39] ogasawara: Great, thanks [08:48] chilicui1: stil problem is not solved i can builddeb [08:48] :( [09:04] infinity: any chances to get chromebook stuff from NEW? [09:05] ++ [09:31] please can anybody help me? [09:37] Dedunu, hi, if you don't state what help you are looking for, not likely [09:40] I got source with bzr [09:40] of gnome-power-manager [09:41] and found the place to edit also i edited it [09:41] when im going to build using bzr bd -- -S [09:41] it gives and error [09:41] dpkg-buildpackage: source package gnome-power-manager [09:41] dpkg-buildpackage: source version 3.6.0-1ubuntu1 [09:41] dpkg-buildpackage: source changed by Dedunu Dhananjaya [09:41] dpkg-source --before-build gnome-power-manager-3.6.0 [09:41] fakeroot debian/rules clean [09:41] debian/rules:6: /usr/share/gnome-pkg-tools/1/rules/uploaders.mk: No such file or directory [09:41] debian/rules:7: /usr/share/gnome-pkg-tools/1/rules/gnome-get-source.mk: No such file or directory [09:41] make: *** No rule to make target `/usr/share/gnome-pkg-tools/1/rules/gnome-get-source.mk'. Stop. [09:41] dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2 [09:41] debuild: fatal error at line 1350: [09:41] dpkg-buildpackage -rfakeroot -d -us -uc -S failed [09:41] bzr: ERROR: The build failed. [09:42] those are end parts [09:43] im using ubuntu 12.04 LTS and i also ran pbuilder-dist raring create before everything [09:43] this is my first fix [09:45] seb128: can you tell me what should i do? [09:45] Dedunu: Have you run ‘apt-get build-dep gnome-power-manager’? [09:45] nop [09:46] i want to build my code [09:46] i fixed a problem in it [09:46] what RAOF said [09:46] run that, it will install the packages needed to build gnome-power-manager [09:46] janimo, hey [09:46] than you ill try [09:48] janimo, https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1123930 [09:48] Ubuntu bug 1123930 in gnome-settings-daemon (Ubuntu) "memleak in plugins/orientation/gsd-orientation-manager.c" [High,New] [09:49] janimo, can you have a look? it's an important leak in your orientation patch ... also please go through review from now on rather than direct upload, reviews help to catch such errors before they hit users and have to go back through reports === jackyalcine is now known as zz_jackyalcine === zz_jackyalcine is now known as jackyalcine [10:02] seb128: RAOF: now error is change [10:02] d [10:03] sorry i would be much obliged to you if you could help me [10:03] dpkg-source: warning: Version number suggests Ubuntu changes, but Maintainer: does not have Ubuntu address [10:03] dpkg-source: warning: Version number suggests Ubuntu changes, but there is no XSBC-Original-Maintainer field [10:03] dpkg-source: info: using source format `3.0 (quilt)' [10:03] dpkg-source: info: building gnome-power-manager using existing ./gnome-power-manager_3.6.0.orig.tar.xz [10:03] dpkg-source: info: local changes detected, the modified files are: [10:03] gnome-power-manager-3.6.0/src/gpm-statistics.c [10:03] dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/gnome-power-manager_3.6.0-1ubuntu1.diff.dDUvhp [10:03] dpkg-source: info: you can integrate the local changes with dpkg-source --commit [10:03] dpkg-buildpackage: error: dpkg-source -b gnome-power-manager-3.6.0 gave error exit status 2 [10:03] debuild: fatal error at line 1350: [10:03] dpkg-buildpackage -rfakeroot -d -us -uc -S failed [10:03] bzr: ERROR: The build failed. [10:04] Dedunu: for applying changes to the upstream source, please see http://developer.ubuntu.com/packaging/html/patches-to-packages.html; you can't do that in-plce [10:04] "place" [10:04] Dedunu: You probably want to use a pastebin for such a lot of text. [10:04] Dedunu, please stop doing big pastes on the channel, use http://paste.ubuntu.com for that [10:05] sorry im new to irc [10:05] thank you === henrix_ is now known as henrix [10:37] seb128: RAOF: i patched it using quilt after that what should i do [10:37] im sorry [10:37] pitti: i did it after that what should i do [10:37] Dedunu, you should be able to run the command then [10:37] which command bzr bd -- -S [10:38] it is again failing [10:38] bzr revert your inline change if you put it in a quilt patch [10:38] bzr revert src/gpm-statistics.c [10:38] Dedunu, what issue are you working on btw, [10:38] ? === jackyalcine is now known as zz_jackyalcine [10:39] https://bugs.launchpad.net/hundredpapercuts/+bug/923292 [10:39] Ubuntu bug 923292 in One Hundred Paper Cuts "shortcut for closing power statistics app not working" [Low,Confirmed] [10:39] good ;-) [10:39] oh im sorry [10:40] omg [10:41] seb128: i reverted it [10:41] seb128: ubottu: is that uploaded to lp? [10:42] Dedunu, ubottu is a bot, it's not going to reply to questions ;-) [10:42] im realy new [10:42] Dedunu, you should be able to bzr bd if you reverted it [10:42] im very sorry if i annoy you [10:43] Dedunu, no, you don't, everybody has to start and has questions when starting, that's ok ;-) [10:43] Dedunu, I would just ignore IRC if I was annoyed ;-) [10:43] thanks [10:44] it hasn't revert things [10:44] how so? [10:44] my lines are there stil [10:45] can you copy the log to http://paste.ubuntu.com and give the url here? [10:45] lines i added are there [10:45] with a bzr diff and bzr status output as well [10:45] http://paste.ubuntu.com/1643366/ [10:45] bzr status is this [10:46] bzr diff gives nothing [10:46] shall i start from the begining? [10:46] first i init a repo [10:46] yeah, not sure what you did [10:46] wait [10:46] shall i explain you what i did? [10:46] yes please [10:46] basically you want to [10:47] bzr branch ubuntu:gnome-power-manager [10:47] export QUILT_PATCHES=debian/patches [10:47] yeah [10:47] bzr bd-do [10:48] quilt new 923292-fix.patch [10:48] quilt add src/gpm-statistics.c [10:48] edit src/gpm-statistics.c [10:48] quilt refresh [10:48] exit 0 [10:48] bzr add debian/patches/923292-fix.patch [10:48] bzr bd [10:48] dch -i "updated changelog for fix" [10:48] as well maybe [10:49] how can i test it i want to see whether i works [10:49] bzr bd will it give a output [10:49] ? [10:49] i mean a .deb [10:49] Dedunu, sorry, that's for slightly different bzr format ... ignore the bzr bd-do and exit0 lines [10:50] Dedunu, basically just follow http://developer.ubuntu.com/packaging/html/patches-to-packages.html and that should work [10:50] you should get a patch in debian/patches with your diff [10:50] Dedunu, yes, bzr bd will give you a .deb [10:50] hmm [10:51] then i cann install deb and see whether it works? [10:51] other wise build will fail [10:51] ? [10:51] you can install the deb and test it yes [10:52] Dedunu, build will fail? just try to start from scratch following http://developer.ubuntu.com/packaging/html/patches-to-packages.html and tell me if you hit an issue [10:55] ok [10:55] thank you [10:55] very much [10:56] you're welcome [11:00] bah [11:00] Laney, bah? [11:01] seems the qemu update broke launching VMs [11:01] * xnox notes to himself not to upgrade [11:02] Laney: who does THAT? [11:02] xnox: what does getfacl /dev/kvm show for you? [11:02] Laney: we can't cater for every edge case. [11:02] Daviey: No worries, I heard arch is better anyway. [11:03] Laney: http://paste.ubuntu.com/1643467/ [11:03] merci, same as me [11:03] (where tdlk is my user account, naturally) [11:03] Laney: although I may already have the new-new qemu stack [11:03] fn'ar, Laney - as xnox is pointing to.. ownership is a problem we have been seeing for a little while [11:03] something seems racey. [11:03] Laney, oh, that got updated, sorry I didn't see it in the middle of all those haskell uploads :p [11:03] Laney: do you use command line? then kvm needs -kvm option. === doko_ is now known as doko [11:04] xnox: virt-manager or virsh [11:04] lemme file le bug [11:04] Laney: ack. that should "just work always"(tm) [11:04] xnox: erm, it shouldn't.. it should use kvm by default, and gracefully fall back to non-accelerated [11:06] bug #1123998 [11:06] bug 1123998 in qemu (Ubuntu) "Can't launch VMs from virt-manager or virsh: Could not access KVM kernel module: Permission denied" [Undecided,New] https://launchpad.net/bugs/1123998 [11:10] seb128: i followed until bzr commit [11:10] after that i bzr bd [11:10] it got failed [11:11] before changing i tried to build it also got failed [11:12] Dedunu, can you pastebin the log with the fail? [11:13] seb128: http://paste.ubuntu.com/1643504/ yeah sure this is before change build fail [11:13] it is about failed debsign [11:13] what is it? [11:13] Dedunu, that didn't fail [11:13] Dedunu, you should have a deb in build-area/ [11:13] ok [11:13] ill [11:13] check [11:14] Dedunu, the message is confusing, it failed to sign the files, which is needed if you want to upload to Ubuntu (because we need to check who has upload rights, etc) [11:14] ok [11:14] Dedunu, but signing is not needed for local builds [11:14] thanks it is there [11:14] now i changed as on tutorial [11:14] and bzr commit also i ran [11:16] now how should i test my changes? [11:16] i got my old deb [11:16] where the patch now? [11:17] seb128: how to apply my changes on my system now? [11:18] Dedunu, install the deb (sudo dpkg -i build-area/gnome-power-manager*.deb) [11:19] is that include my changes? [11:20] if you did a build with your patch commited etc it should [11:20] Dedunu, what's the deb version? [11:20] 3.6.0-1 [11:20] the name of the deb [11:20] what is the current version in debian/changelog? [11:21] how to check it [11:21] Dedunu, editor debian/changelog [11:22] in the checkout of the source [11:22] the first line [11:22] there's nothing inside it [11:22] im sorry [11:22] i developed c/c++ things [11:22] never worked with those bzr [11:23] no worry, there is a learning curve ;-) [11:23] are you sure you are in the checkout dir? [11:23] there is a debian/changelog and it has content for sure in there [11:23] Is there a standard way for an upstart job's pre-script to log a message to the terminal when it fails? Writing to stdout or stderr redirects to /var/log/upstart/.log, which is fine, but isn't so helpful to a sysadmin starting a job by hand. Eg. bug 1121874. [11:23] bug 1121874 in mysql-5.5 (Ubuntu) "MySQL launch fails silently if < 4MB of disk space is available" [Medium,Triaged] https://launchpad.net/bugs/1121874 [11:24] seb128: 3.6.0-1ubuntu1 [11:24] i was in buildare [11:24] a [11:24] Dedunu, ok, so the deb you build should have this number [11:24] Dedunu, try running bzr bd again ? [11:24] 3.6.0-1 was the version you first built [11:25] or you maybe have the 2 debs in build-area if built both? [11:25] rbasak, there is a "console" option that can be set to print to plymouth [11:25] seb128: http://paste.ubuntu.com/1643532/ [11:25] this is build [11:25] i think its failed? [11:25] rbasak, http://upstart.ubuntu.com/cookbook/#console [11:25] ogra_: looking, thanks! [11:26] Dedunu, yeah, can you pastebin the output of both "bzr diff" and "bzr status"? [11:26] i think "console log" or "console output" [11:27] seb128: bzr status http://paste.ubuntu.com/1643539/ [11:27] bzr diff nothing [11:27] Dedunu, bzr add debian/patches/series and try bzr bd again [11:28] bzr add debian/patches .pc [11:28] (also quilt push, but one needs to setup the series file pointer...) [11:28] xnox, he followed http://developer.ubuntu.com/packaging/html/patches-to-packages.html [11:28] which recommends [11:28] bzr add debian/patches/name [11:29] bzr add .pc/* [11:29] that doesn't work for a package that had no patch before and the series not in the vcs... === zz_jackyalcine is now known as jackyalcine [11:29] seb128: http://paste.ubuntu.com/1643540/ [11:29] sounds about right, if there was a quilt push and/or commit (bzr bd does quilt push) [11:29] i took little bit of time [11:29] Dedunu, ok, great, it's failing in your patch on a code error [11:29] heh, true about first patch ever ;-) [11:30] ok than [11:30] thanks ill check it [11:30] Dedunu, sorry it was tedious, you should be set now [11:30] bzr commit the addition of the series file [11:31] Dedunu, you might just want to iterate builds by doing ./configure --prefix=/usr && make in your checkout and do "make" until you got the patch right [11:31] rather than going through a bzr bd every time [11:31] seb128: ok thanks [11:31] then do it properly once you are happy with the diff and get it to build [11:33] ogra_: that's making it go to /dev/console rather than the tty "sudo start mysql" is connected to === jackyalcine is now known as zz_jackyalcine [11:33] Is the answer just that jobs aren't supposed to talk to root's terminal for manual jobs? [11:34] rbasak: hm? in recent upstart all jobs stdout/stderr is redirected to /var/log/upstart/job.log [11:34] might be, ask jodh [11:34] rbasak: and stdin is /dev/null [11:35] xnox: yes, but that doesn't seem optimal [11:35] (in this case) [11:35] rbasak: it is for most things [11:35] xnox, jodh: in a pre-script, if it cannot continue, then it makes sense to tell root directly on his terminal if he called "start ", right? [11:35] rbasak: lets start from the beginning. What's your usecase / problem? and maybe upstart can help solving it in a different way =) [11:36] xnox, jodh: bug 1121874 [11:36] bug 1121874 in mysql-5.5 (Ubuntu) "MySQL launch fails silently if < 4MB of disk space is available" [Medium,Triaged] https://launchpad.net/bugs/1121874 [11:36] you might be able to add a TTY=$(tty) call and redirect explicitly to it ... not sure, depends if you have an environment thats handed to upstart in that case [11:36] I've amended it to echo to stderr, and that ends up in /var/log/upstart/mysql.log just fine. But I think it makes sense to do better and write to root's terminal too [11:36] rbasak: usually pre-start should issue stop command, and then the output from strart command will be: foo is stopped, rather than started. [11:37] Yes, but the reason for the failure isn't obvious. And /var/log/upstart/mysql.log isn't timestamped (though I can run date of course). === zz_jackyalcine is now known as zz_zz_jackyalcin === zz_zz_jackyalcin is now known as jackyalcine [11:38] rbasak: the problem is that it uses "exit" instead of "stop" which would correctly print the message that the job is not starting. [11:38] it will not, however print why it didn't start. But at least there will be some feedback. [11:39] With exit 1: $ sudo start mysql [11:39] start: Job failed to start [11:39] With stop: $ sudo start mysql [11:39] mysql stop/pre-start, process 18925 [11:39] I think the result of "exit 1" is clearer! [11:40] =) [11:42] rbasak: fair enough and it's more consistent with missing my.cfg & failing to load apparmor profile [11:42] which also do not print messages. === jackyalcine is now known as zz_jackyalcine === zz_jackyalcine is now known as jackyalcine [11:43] effectively this test should live inside mysqul imho and just log to syslog [11:43] ogra_: I'd rather not patch mysql for this if it can be done in a pre-start! [11:43] ogra_: no, because stuff that starts on starting mysql would have fired by then. [11:44] And I can still log to syslog from the pre-start with logger if I want to. [11:44] xnox, hmm ? if the upstart job failed nothing depending on it should start [11:44] rbasak: in the pre-start script you can do: echo "`date` Pre-start Sanity checks" [11:44] I think I understand the options now, thanks. So now the question becomes: what is the standard, or what should the standard be? [11:45] rbasak: and then you get timestamps and reasoning in the /var/log/upstart/mysql.log [11:45] xnox: yeah I guess that's the best option for now. Thanks! [11:46] ogra_: started - mysql started to run and didn't fail, starting - mysql is about to be launched [11:46] rbasak: possibly more messages for the other two fails (missing my.cnf & failing to load apparmor-profile) [11:47] xnox: ack [11:47] I'll fix it up === jackyalcine is now known as zz_jackyalcine === zz_jackyalcine is now known as jackyalcine [11:47] jodh: you might want to look at the mysql upstart job, it does some funny stuff in pre-start and post-start =) [11:49] rbasak: upstart cannot predict what is being tested in pre-start or script so the job itself should somehow hint to the user as to what it is doing. And since we log everything, stdout & stderr is your friend. [11:49] why ubuntu uses apparmor instead of selinux? [11:50] xnox: the post-start is pretty close to http://upstart.ubuntu.com/cookbook/#post-start, no? [11:50] maybe it's possible to (re)use selinux policies from redhat and thus share efforts, instead of developing new set of rules... [11:50] if one increases upstart logging $ initctl log-priority debug then you get detailed events emitted, but they go to like dmesg and not individual job logs. === _salem is now known as salem_ [11:51] mjt: selinux is harder for admins to get right, apparmor offers more flexibility/sanity. [11:51] mjt: although people on #ubuntu-hardened (security team) can answer that question better. [11:51] mjt: apparmor works really well. Witness all the sysadmins who end up disabling selinux because they don't understand it and it's blocking them [11:52] jdstrand: ^ mjt [11:54] mjt: why doesn't redhat use apparmor instead of selinux? Then we could share efforts, instead of developing a new set of rules... :-) [11:54] He didn't suggest switching but finding a way to share policies... [11:55] Good point. Sorry. [12:03] * mjt is back (was afk for a bit) === jackyalcine is now known as zz_jackyalcine === zz_jackyalcine is now known as jackyalcine [12:04] well. I ended up disabling selinux on a few redhat systems I manage exactly because it was constantly staying on the way [12:05] and it required quite some amount of time to get to actually fixing the problem [12:09] seb128, jibel added a proposed debdiff to the bug [12:09] I have just added one that is === jackyalcine is now known as zz_jackyalcine === zz_jackyalcine is now known as jackyalcine === jackyalcine is now known as zz_jackyalcine === zz_jackyalcine is now known as jackyalcine [12:34] * mjt wonders why, after typing `apparmor suse' in google the first suggestion it offers to complete the search term is `disable'... [12:34] janimo, thanks, I will review it in a bit [12:36] mjt: was the completion "disable apparmor" or "disable suse" ?! [12:36] * xnox =D [12:36] heh [12:39] in that context i remember a subject in qemu-devel@ recently -- "Discard improvements" by Paolo Bonzini... [12:39] that meant to be improvements for "discard" command (to a virtual disk), not to discard any improvements made so far... [12:40] yeah, I know. [12:40] hello o/ [12:41] I got an archive question :-) [12:41] a package seems to have gone AWOL... cjwatson? :-) [12:42] and when I say one, I mean two. [12:44] Nafallo: which src package names? [12:44] xnox: not sure, but binary package names would be open-vm-tools and open-vm-dkms === jackyalcine is now known as zz_jackyalcine === zz_jackyalcine is now known as jackyalcine [12:46] I would imagine the source being open-vm-tools [12:47] Nafallo: https://launchpad.net/ubuntu/+source/open-vm-tools/+publishinghistory it's published in multiverse [12:47] Nafallo: do you have multiverse enabled? [12:47] yeah, all of the four [12:47] * xnox is waiting for rmadison results.... [12:48] hrm [12:48] for some reason I don't have the package lists for multiverse... [12:49] *scratches head* [12:49] thanks for checking. seems I've got bigger issues. [12:49] Nafallo: it's on disk on mirrors, either you don't have multiverse enabled or the mirror you are using doesn't have multiverse. [12:50] yeah, I don't have the lists in /var/lib/apt/lists, so something isn't right on this server. thanks for confirming :-) [12:51] xnox: fixed by magic... I blame the squid proxy. === jackyalcine is now known as zz_jackyalcine === zz_jackyalcine is now known as jackyalcine === jackyalcine is now known as zz_jackyalcine === zz_jackyalcine is now known as jackyalcine [13:17] I wonder why the postgresql security update hasn't propagated to updates yet? I thought that usually happened almost immediately (to offload the security mirrors). [13:18] soren: hi! I think that was turned off in preparation for the precise point release [13:18] jdstrand: Hey :) [13:19] jdstrand: Why wouldn't we want security updates to be included in the point release? [13:19] soren: we would, but, aiui, the point release was more or less imminent [13:19] testing done, etc [13:19] Oh, I see. [13:20] Oh, well. As long as it's intentional, it's probably all good. [13:21] I think that may all get turned back on today [13:21] Cool beans. === jackyalcine is now known as zz_jackyalcine === zz_jackyalcine is now known as jackyalcine [13:27] soren: I turned it off because we were iterating on candidates and I wanted exact control over what changed in each one === jackyalcine is now known as zz_jackyalcine === zz_jackyalcine is now known as jackyalcine [13:33] mjt: xnox was right. apparmor is easier to use on many levels. selinux is available in Ubuntu as well. We do work with other distros to share apparmor policy, but sharing policy like this (apparmor or selinux) is difficult because of distro nuances [13:34] mjt: if you want some more info, I suggest taking a look at: https://wiki.ubuntu.com/AppArmor (which has a bunch of links for more info) [13:40] seb128: i fixed it and finally built it [13:40] seb128: thank you lot [13:40] Dedunu, great, you're welcome! === jackyalcine is now known as zz_jackyalcine === zz_jackyalcine is now known as jackyalcine [13:48] seb128: now i pushed my code to my lp [13:49] so i should ask for a sponsership nah? [13:50] Dedunu, did you submit a merge request for it? [13:52] seb128: nope [13:52] how to request a merge [13:52] ? [13:52] cjwatson: Ok, cool. I just wanted to make sure it wasn't an unknown problem. [13:52] seb128: ubuntu wiki makes me confuse im sorry for asking steps [13:53] by step [13:53] Dedunu, http://developer.ubuntu.com/packaging/html/udd-sponsorship.html [13:55]