/srv/irclogs.ubuntu.com/2010/12/15/#ubuntu-devel.txt

SpamapS@pilot out00:13
=== udevbot changed the topic of #ubuntu-devel to: Archive: Open | Development of Ubuntu (not support, not app development) | #ubuntu for support and general discussion for dapper -> maverick | #ubuntu-app-devel for application development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://wiki.ubuntu.com/HelpingWithBugs | Current Friendly Patch Pilots: smoser`
ari-tczewdoko: is python-django on your todo ftbfs fix?00:52
=== ubuntuish is now known as rmrfslash
jferHi. I am having trouble using bzr to get involved in unity01:20
jfercan someone please give me a hand?01:20
achiangjfer: what is your question?01:29
=== jjohansen is now known as jj-afk
=== TerminX_ is now known as TerminX
=== asac_ is now known as asac
keesjames_w: say, why is this 6 months behind? https://code.launchpad.net/~ubuntu-branches/ubuntu/natty/kde4libs/natty03:41
keesRiddell: do you know anyone from upstream KDE that will commit my patch in https://bugs.kde.org/show_bug.cgi?id=245529 ?03:43
ubottuKDE bug 245529 in general "drkonqi fails when PTRACE restrictions are active" [Normal,Unconfirmed]03:43
=== akshatj|bed is now known as akshatj
james_wkees, bug 65330104:32
ubottuLaunchpad bug 653301 in Ubuntu Distributed Development "Packages failing due to pristine-tar not being able to reconstruct their tarball" [High,Triaged] https://launchpad.net/bugs/65330104:32
james_wwhich could actually progress now04:32
* james_w leaves that for tomorrow04:32
=== sam---___---- is now known as sam-_-
mark_test05:46
keesjames_w: ah-ha, thanks05:46
mark_any progress on the memory leaking nm-applet?05:47
=== _LibertyZero is now known as LibertyZero
=== oubiwann-holiday is now known as oubiwann
=== oubiwann is now known as oubiwann-holiday
=== almaisan-away is now known as al-maisan
mark_any progress on the memory leaking nm-applet?07:11
pittiGood morning07:41
dholbachgood morning07:54
akshatjgood morning dholbach07:54
dholbachhi akshatj07:54
* ebroder wants Upstart managing his user session instead gnome-session08:08
=== smb` is now known as smb
=== evilvish is now known as \vish
=== \vish is now known as vish
=== leagris is now known as virtuald
seb128hey08:58
seb128@pilot in08:59
=== udevbot changed the topic of #ubuntu-devel to: Archive: Open | Development of Ubuntu (not support, not app development) | #ubuntu for support and general discussion for dapper -> maverick | #ubuntu-app-devel for application development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://wiki.ubuntu.com/HelpingWithBugs | Current Friendly Patch Pilots: smoser`, seb128
* dholbach hugs seb12809:00
* seb128 hugs dholbach09:00
mvoseb128: happy flying09:03
seb128mvo, thanks ;-)09:04
=== jj-afk is now known as jjohansen
=== doko__ is now known as doko
mok0mvo, I see you fixed the python-minimal problem, THANKS!10:49
pittimvo: oh, did you?10:51
mvonot really :/10:51
mvodoko just added workaround for now10:51
* mvo is off for lunch10:51
mok0pitti: there was an upgrade of python2.6-minimal, after which I could install python-minimal10:51
pittimok0: in natty? no, that was python2.7-minimal dropping the Breaks:10:52
dokoit would be a workaround if the fixed python-defaults arrives in -updates10:52
mok0pitti: That's what it seemed like when apt-get did its thing10:52
mok0yes in natty10:52
mok0anyway my natty sbuilder is now happily compiling again :-)10:53
ScottKkees: Riddell, apachelogger, and JontheEchidna all have commit rights in KDE svn, so one of them.12:02
ScottKOh, or agateau if you can catch him.12:02
pittiseb128: can you please reupload bug     68878112:09
ubottuLaunchpad bug 688781 in sqlite3 (Ubuntu Maverick) "Fix performance regression affecting Banshee" [Low,Fix committed] https://launchpad.net/bugs/68878112:09
pittiseb128: with a fixed LP# ref in the changelog?12:09
seb128pitti, urg, yeah sorry about that12:15
seb128pitti, done12:18
pittiseb128: merci12:18
seb128de rien, sorry for not being careful12:18
seb128the bug number was listed twice but not with the right format ;-)12:19
=== jjohansen is now known as jj-afk
=== bilalakhtar_ is now known as cdbs
ScottKNCommander: When you have a moment, I'd like to talk to you about sip4-qt3 (looking for help understanding it, not asking you to do work).13:05
=== drspeedo|away is now known as drspeedo
=== njpatel is now known as njpatel_
dokoseb128: who best to ask about vala? bug #61880913:29
ubottuLaunchpad bug 618809 in gtask (Ubuntu) "libvala-dev -> libvala-0.10-dev transition" [High,Confirmed] https://launchpad.net/bugs/61880913:29
seb128doko, do they fail to build or...?13:32
dokoseb128: yes, b-d on libvala-dev, now we seem to target vala 0.1213:33
seb128doko, did they fail to build if you rename the build-depends?13:34
dokoseb128: yes13:37
seb128kenvandine, ^ do you have time to try to see what's wrong with gtask?13:38
dokocyphermox and slomo are not online. will subscribe them13:39
seb128doko, or wait for kenvandine to reply13:40
dokook13:40
ari-tczewWięcej osób chce Cię poznać na Badoo!13:41
ari-tczewups, not this copy13:41
ari-tczewdoko: is python-django on your todo ftbfs fix?13:41
dokoari-tczew: no. what is wrong with it?13:41
ari-tczewdoko: no longer build with python. it's to sync, but it can be synced because it's ftbfs on natty chroot.13:42
dokoari-tczew: bug number?13:43
ari-tczewdoko: not reported, report it?13:43
dokoari-tczew: ftbfs is not that much info ...13:43
ari-tczewdoko: as sync request or rather ftbfs?13:43
dokoari-tczew: is it safe ti sync, do packages b-d on it, build? you have more information than me. please make it available. bug report seems to be fine13:54
kenvandineseb128, i can look at gtask13:56
ari-tczewdoko: hmmm, I can't attack buildlog ATM, so I'm sending pastebin: http://paste.ubuntu.com/544044/13:57
ari-tczewbug 69064613:57
ubottuLaunchpad bug 690646 in python-django (Ubuntu) "FTBFS with python" [Undecided,New] https://launchpad.net/bugs/69064613:57
Davieydoko: Have you been seeing, http://pb.daviey.com/cRcx/raw/ ?13:57
dokoari-tczew: does the package b-d on python-all*?13:58
dokoDaviey: dpkg -l python python-minimal ?13:58
ari-tczewdoko: nope13:59
Davieydoko: version 2.6.6-2ubuntu1, want a full paste?13:59
dokoari-tczew: but it tries to build for it.14:00
Davieydoko:  http://pb.daviey.com/ZJew/raw/14:00
dokoDaviey: see my last comment in https://bugs.edge.launchpad.net/ubuntu/+source/python2.7/+bug/68930614:00
ari-tczewdoko: Build-Depends: debhelper (>= 7.0.50), python-support, python (>= 2.5) | python-sqlite, language-pack-en-base Build-Depends-Indep: python-sphinx, libjs-jquery14:00
ubottuUbuntu bug 689306 in python2.7 (Ubuntu) "package python2.7-minimal 2.7.1-1ubuntu1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 3" [Medium,Confirmed]14:00
* Daviey reads14:01
apwjhunt, hey, you had a bug for initramfs-tools for the fixes for the new linhib0001 stuff, can you point me at it14:04
jhuntapw: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/68360514:05
ubottuUbuntu bug 683605 in util-linux (Ubuntu) "kernel hibernate signature has changed from S1SUSPEND to LINHIB0001" [Undecided,New]14:05
apwjhunt, how is that one going, i am starting to see duplicates of it14:05
Davieydoko: thanks!14:05
apwjhunt, oh yeah it was waiting for something to invalidate a pending linhib0001 image in swap when it was first installed ... else bad poop (tm) could occur14:06
NCommanderScottK: I'm here14:13
ScottKNCommander: Hello.14:13
NCommanderScottK: how are you doing this morning?14:13
ScottKNCommander: I looked at dh_sip and it seems simple enough.  The one big question I have is where does the API version come from?14:13
ScottKNCommander: Pretty good.  Pleanty to do.14:13
NCommanderScottK: ah, that's a new feature added by the co-maintainer. I would have to look14:14
ScottKNCommander: OK.  I thought you had been involved in it.14:14
NCommandergive me a sec, I'll grab the source14:14
ScottKThanks.14:14
jhuntapw: sorry, been busy on upstart. So the scenario is that if a user boots a kernel older than 2.6.37 (having hibernated in the 2.6.37 kernel), we need to invalidate the swap signature right?14:14
NCommanderScottK: I did some design discussions, but then I went to China and it got implemented without me14:14
ScottKI see.14:14
NCommanderScottK: looks like we're quizing dpkg for the python-sip version14:15
apwjhunt, no actually the issue is if we have natty and hibernate, reboot, hibernate is not detected and swap is lost.  we then fix the tools and reboot and it finds and resume from the image and the filesystem no longer matches the memory image and BLAMMO bad corruption of /14:15
NCommanderScottK: which is sane because we don't know if the sip ABI has changed (there's no promise by upstream that it will remain stable)14:15
apwjhunt, so if you install your fixes to the tools, we need to invalidate the swap marker as the contents are definatly BAD to use14:15
apwcjwatson, ^^14:16
NCommandercjwatson: did you get around to putting archdetect in userspace BTW? (per UDS)14:16
ScottKNCommander: Right, but dh_sip uses whatever API version the package provides.14:16
ScottKI'm trying to figure out where that comes from (see the provides in debian/control)14:17
NCommanderScottK: it would be the version of the source package then14:18
* NCommander looks a little more indepth14:18
cjwatsonNCommander: see recent debian-boot@14:19
ScottKThat doesn't match what's there currently.14:19
NCommandercjwatson: checking14:19
NCommanderScottK: what's there currently?14:20
=== zyga is now known as zyga-food
ScottKNCommander: Provides: ${python:Provides}, sip-api-7.0, sip-api-7.114:20
NCommandercjwatson: thread title?14:21
* NCommander is not seeing it in the archive list14:22
cjwatsonNCommander: http://lists.debian.org/debian-boot/2010/12/msg00481.html14:22
NCommandercjwatson: interesting. I'll be watching what develops in this thread (dpkg-subarchitecture or extending dpkg-architecture is an interesting idea TBH)14:23
cjwatsonNCommander: I can't say I approve myself - stuff that isn't maintained by the dpkg team shouldn't be in the dpkg-* namespace14:30
cjwatson(dpkg-reconfigure is a historical mistake that shouldn't be repeated)14:30
cjwatsonI followed up to the thread to say that14:30
ari-tczewdoko: so, are B-D fine or not?14:39
dokoari-tczew: is the package meant for all supported python versions, or just for the current one?14:40
ari-tczewdoko: dunno, really14:41
dokoari-tczew: where is the merged package?14:45
ari-tczewdoko: merged?14:45
dokoari-tczew: I thought you wanted to merge from unstable?14:46
ari-tczewdoko: it's ready to sync14:46
NCommandercjwatson: thanks for being on top of this14:46
ari-tczewdoko: but it's ftbfs - the same with current package and from unstable, so I'm getting in touch with you14:47
dokoari-tczew: $ cat debian/pyversions14:50
doko2.3-14:50
cjwatsondholbach: does http://merges.ubuntu.com/main.json (and restricted, universe, multiverse, and main-manual etc.) fit the form you need for harvest?14:51
ari-tczewdoko: I see. what does it mean for me?14:51
dholbachcjwatson, that should be fine - I might write a script that goes and merges them (as Harvest does packagesets/etc. on its own) - let me quickly try it out14:53
dokoso it wants to build for all python versions. uninstall python26-minimal and try again14:53
cjwatsondholbach: right, it's just easiest to spit them out that way14:53
dholbachcjwatson, don't worry - that's totally fine - should be easy to do :)14:53
cjwatsondholbach: I also just committed a grep-merges tool to ubuntu-dev-tools that uses that output14:53
dholbachawesome14:54
dholbachI'll report back in a few14:54
dholbachthanks in any case14:54
cjwatsonso should at least be valid json ;-)14:54
dokoari-tczew: and it will fail later ...14:54
ari-tczewdoko: could you fix it?14:56
ari-tczew(I can't)14:56
=== njpatel_ is now known as njpatel
dholbachcjwatson, looking good :)15:11
dholbach(locally)15:11
cjwatsonexcellent15:12
=== tkamppeter_ is now known as tkamppeter
apwcjwatson, where do the unity peeps hang out ?15:29
dholbach#ayatana probably15:30
cjwatsonyeah15:32
NCommanderScottK: are you still interested in updating your +1 on my core dev app15:37
ScottKNCommander: I don't think we've worked on anything together recently?15:37
hallyn_hm, debootstrapping a lucid image on natty is giving me troubles15:38
NCommanderScottK: I poked you on that earlier lsat month, and I thought you wanted to revise what you said; are   you still confortable +1ing me?15:39
=== dholbach_ is now known as dholbach
ScottKYou did?15:39
* ScottK lost those brain cells apparently.15:40
ScottKNCommander: Give me a link and I'll look.15:40
NCommanderScottK: I thought I did, or at elast said something at UDS. Granted, its been a long month15:40
NCommanderScottK: https://wiki.ubuntu.com/MichaelCasadevall/CoreDevApplication15:41
ari-tczewdoko: I prefer to not uninstall python2.6-minimal - it will remove 50% of important packages.15:41
ari-tczewdoko: I guess that you're talking about remove python2.6-minimal from B-D?15:41
dokoari-tczew: you should do development in a chroot where you can do stuff like this15:42
ScottKNCommander: I think it's still correct.15:42
ari-tczewdoko: I use pbuilder. python2.6-minimal doesn't exist in debian/control15:42
mok0How to deal with a package distributed by svn only, and where upstream does not provide a .tar.gz file?15:49
azeemmok0: do they tag releases?15:49
=== bjf[afk] is now known as bjf
mok0azeem: nope15:49
pittimok0: do they have version numbers at all?15:50
mok0pitti: yes, svn revision numbers15:50
pittiI  mean "eleases"15:50
azeemthen I'd just use 0.0.0~r<svn-revision> as version number15:50
mok0azeem: oh, they do have a version number yes15:50
pittimok0: right, use 0.r1234 as fake version numbers and use make dist15:50
mok0pitti: ok... just seems going a detour, when everything is in LP15:51
mok0:-)15:51
ionPerhaps 0~r1234. That should accommodate any kind of future version number. :-)15:52
pittimok0: well, you could use bzr-svn to import upstream's trunk, and create a branch with the packaging in it15:52
pittiion: mathematically that's a really fun number15:52
mok0pitti: right, but I still need a tar.gz file for the source package15:52
pittia non-negative number smaller than 015:53
ionhehe15:53
pittimok0: why?15:53
pittimok0: you can call autoreconf in debian/rules, if you are worried about that15:53
mok0pitti, errh that was what I thought you said: "make dist"15:53
pittimok0: right, you'd use that _if_ you want to create an orig.tar.gz15:53
pittiif you want to branch off trunk for a packaging branch, you don't have to15:54
pittibut your choice really15:54
mok0pitti: I see. I've never done packaging directly from a bzr before, so it's new territory for me.15:55
pittiit's not that different; you just need to ensure that you build the autoconfiscation15:55
pitti(if they use autotools)15:55
mok0pitti: they do15:56
mok0pitti, do you have a reference for a package I could study, that does not use an orig.tar.gz file?15:58
pittihm, not off-hand15:59
Keybukjdstrand: when somebody files four separate SEGV reports in the space of a minute, I'm afraid I begin to suspect something else wrong16:01
Keybukjdstrand: so could you run memcheck86 on your machine please16:01
jdstrandKeybuk: they aren't mine16:01
jdstrandKeybuk: they are old and private. I just noticed them since I had access16:01
Keybukare they not?  LP's make them sound like they are16:01
Keybukahh16:02
KeybukLP fail then16:02
jdstrandKeybuk: so I subscribed you and james since I thought someone might be interested in seeing them :)16:02
Keybukthanks16:02
Keybukjdstrand: in general, subscribe james from now on16:02
jdstrandsure16:02
Keybukhe's the ubuntu maintainer now16:02
jdstrandKeybuk: ok, I did both of you this time, but noted16:03
Keybukbut I never mind being subscribed16:03
KeybukI just mean avoid only subscribing me by accident, since I won't be here :p16:03
* jdstrand nods16:03
Keybukthanks :p16:04
Keybukwill take a quick look at these now16:04
jdstrandcool, thanks16:04
=== tremolux_ is now known as tremolux
dokokenvandine: gtask, thanks for the upload, but better re-upload as ubuntu1 instead of buildN16:14
kenvandinedoko, will do16:18
kenvandinedoko, done16:20
dholbachcjwatson, it's on there! http://harvest.ubuntu.com/opportunities/ :)16:22
cjwatsonneat!16:23
* dholbach hugs cjwatson16:24
dholbachgood work!16:24
=== beuno is now known as beuno-lunch
=== jj-afk is now known as jjohansen
lamontI wish that my system wouldn't randomly decide that a window should have the cursor grabbed when the window believes that it does not...  clearing that makes for some fun exploritory poking16:30
seb128cjwatson, could you review or merge https://code.launchpad.net/~smoser/ubuntu/natty/openssh/lp688574/+merge/43366 when you have some time?16:39
cjwatsonI really wish that ssh-import-id weren't in openssh.  it's such a bad idea for it to be integrated there16:47
cjwatsonit belongs in a separate package16:47
cjwatsonseb128: Dustin's assigned it to himself, he can do it16:48
cjwatson(the bug)16:48
kirklandcjwatson: ?16:49
cjwatsonkirkland: 16:39 <seb128> cjwatson, could you review or merge https://code.launchpad.net/~smoser/ubuntu/natty/openssh/lp688574/+merge/43366 when you have some time?16:49
cjwatsonyou assigned the bug to you so as far as I'm concerned you're taking care of that16:49
kirklandcjwatson: it was a separate package, we reviewed it in belgium, and i got the go ahead from you to drop it in openssh-server16:49
cjwatsonover my protests16:49
seb128ups sorry, I was reviewing from the queue and just read the merge request, not the bug16:49
cjwatsonI thought it was wrong but you wouldn't let up :(16:49
cjwatsonbug 690436 is a great demonstration of why it should be separate16:50
ubottuLaunchpad bug 690436 in openssh (Ubuntu) "ssh-import-id requires wget and ca-certificates to function properly" [Undecided,New] https://launchpad.net/bugs/69043616:50
kirklandcjwatson: ?  i'm sorry, i didn't under you protested it16:50
cjwatsonit's bizarre that we have this thing that upstream doesn't care about, that's maintained totally separately from openssh to all intents and purposes, and yet it's in the openssh-server package16:51
cjwatsonit's basically an Ubuntu server add-on16:51
kirklandcjwatson: are you asking for this in a separate source package, or a separate binary package under openssh ?16:53
cjwatsonnormally, source packages are divided along maintenance lines16:53
cjwatsonI really don't know what I'm asking for any more, though, I just want not to have to worry about ssh-import-id TBH16:54
kirklandcjwatson: okay; i'm in the process of getting it upstream16:54
cjwatsonyou seriously think upstream will take it?16:54
cjwatsonI am extremely doubtful16:55
kirklandcjwatson: to do that, smoser wanted to re-write it in the way that that merge request does16:55
kirklandcjwatson: i honestly have no idea;  i have never dealt with that upstream16:55
kirklandcjwatson: is ssh-copy-id upstream?16:55
cjwatsonI think you're onto a loser16:55
cjwatsonssh-copy-id is, yes16:55
cjwatsonbut from ages and ages back16:55
cjwatsonopenssh upstream are extremely conservative, and rarely include anything significant that they didn't write themselves16:56
cjwatsonmaybe I'm wrong, but it would astonish me if they took ssh-import-id16:56
kirklandcjwatson: i see it in a contrib/16:57
kirklandcjwatson: i see this as ssh-copy-id, from the other direction16:57
kirklandcjwatson: ssh-copy-id securely pushes a public key;  ssh-import-id securely pulls a public key16:57
kirklandcjwatson: i mean, i can make a new source/binary package;  but it's one shell script and one manpage16:57
cjwatsonyou may see it that way, but I think it's unlikely that upstream will16:57
cjwatsonpulling keys has much more interesting cryptographic properties16:57
kirklandcjwatson: right;  i don't know that upstream well enough to have any idea what they would say16:58
cjwatsonpulling keys over SSL even more sos16:58
cjwatson*so16:58
cjwatsonbecause that means SSL is now within their security boundary16:58
cjwatsonnot to mention the hardcoding of LP, etc.16:59
cjwatson(sure, that's fixable, although the hardcoding is a desirable part of the UI from Ubuntu server's point of view)16:59
kirklandcjwatson: it's configurable now17:00
kirklandcjwatson: the URL;  defaults to LP17:00
cjwatsonbear in mind that even of patches I think are a good idea, or even blindingly obvious, I only have a 50% success rate or so at getting them upstream17:00
cjwatsonwhen they do take them, they often rewrite them17:00
kirklandcjwatson: okay, well, i plan on dropping the script on that list out of courtesy17:00
kirklandcjwatson: if they have constructive criticism that I can address, I will17:01
cjwatsonI'm pretty confident we're stuck with it forever17:01
kirklandcjwatson: if they tell me to go f myself, fine;  i've done my duty17:01
cjwatsonbut that's an ongoing maintenance problem17:01
kirklandcjwatson: now, what I really want to know is how you want this script to be packaged in Ubuntu, in the mean time17:01
cjwatsonIMO the dependency issues are a good reason why at the very least it needs to be a separate binary package again17:02
kirklandcjwatson: it shouldn't be a maintenance problem;  it should just work; shouldn't need a lot of attention; it should do one thing and do it well17:02
smoserits very little on going maintenance, and a fairly high amount of "man that was easy"17:02
cjwatsonthere's a bunch of mail I have to ignore17:02
cjwatsonany bunch of mail I have to ignore is a problem :)17:02
cjwatsonlook, I can procmail out anything with ssh-import-id in the subject if you really want, but I'm not sure that's constructive.  What I want is for it not to show up as part of openssh maintenance, because really, it's being maintained separately17:03
kirklandcjwatson: i'm subscribed to all bugs in openssh17:03
cjwatsonI know, but so am I17:04
cjwatsonthings like this happen, where the patch pilot asks me about something and I honestly don't have a clue17:04
kirklandcjwatson: "don't have a clue" -- dude, you probably the smartest person I know ;-)17:05
kirklandcjwatson: but I understand, I don't want this to be your problem17:05
cjwatsonI don't have a clue about the correctness or otherwise of this merge request17:05
cjwatsonI view that as a problem, given that I maintain the package17:05
cjwatsonwhether it's my problem ... I'm not sure17:05
kirklandcjwatson: well, for the record, I would be happy for you to pass any and all ssh-import-id issues to me, and I'll deal with them at a high degree of urgency17:06
cjwatsonbut it seems to me that having these two disparately-maintained things in the same source tree is just creating extra work17:06
kirklandcjwatson: that said, i'll split this out to a separate package17:06
Riddellkees: I committed that patch to KDE thanks17:06
kirklandcjwatson: fine, i'll split it out;  can openssh-server recommend this package?17:07
cjwatsonsure17:07
* kirkland gets to work17:07
cjwatsonthank you, my mailbox will appreciate it17:07
jhuntcjwatson: I've tweaked busybox for bug 683605, but am getting quilt errors on the 'dpkg-buildpackage -S'17:09
ubottuLaunchpad bug 683605 in util-linux (Ubuntu) "kernel hibernate signature has changed from S1SUSPEND to LINHIB0001" [High,Confirmed] https://launchpad.net/bugs/68360517:09
cjwatsonjhunt: what's the text of the error?17:10
jhuntcjwatson: error is, "dpkg-source: error: can't build with source format '3.0 (quilt)': no orig.tar file found"17:10
cjwatsonah, ok, that's easy - cd to the parent directory, 'apt-get -d source busybox'17:10
cjwatsonjust so it has the upstream source available17:10
cjwatsonI take it you generated a quilt patch for your change?17:11
jhuntok - the parent dir does have the bzr upstream src, but clearly that ain't good enough :-)17:11
jhuntcjwatson: no - never used quilt.17:11
cjwatsonaha, well you need to :)17:11
cjwatsonback out your changes to start with17:12
cjwatsonquilt new name-of-your-change.patch # look in debian/patches/ for examples17:12
cjwatsonquilt edit util-linux/volume_id/linux_swap.c # or whatever17:12
cjwatsonmake your changes17:12
cjwatsonquilt refresh17:12
cjwatsonthen edit debian/patches/name-of-your-change.patch according to http://dep.debian.net/deps/dep3/ so that we know why it's there in future17:13
cjwatsonthen you can build17:13
cjwatsonthe main thing to watch out for is just that quilt needs to know about any file you change before you edit it, so that it has a pristine copy - 'quilt edit' is basically 'quilt add; $EDITOR'17:13
cjwatsonyou can use the 'what-patch' tool in ubuntu-dev-tools to find out whether a package uses a patch system before you start editing it17:14
keesRiddell: great! thanks. :)17:15
jhuntcjwatson: thx! Re the apt-get src, I'm running maverick, but this bug is in natty, so a wget or similar instead presumably?17:15
cjwatsonoh, yeah17:15
cjwatsondget http://archive.ubuntu.com/ubuntu/pool/main/b/busybox/busybox_1.17.1-7ubuntu4.dsc17:16
cjwatsonsorry, dget -d17:16
cjwatsonor I have http://paste.ubuntu.com/544096/ lying around in ~/bin/get-lp-package - 'get-lp-package ubuntu busybox 1:1.17.1-7ubuntu4'17:17
evjhunt: or just put the natty deb-src in your sources.list17:25
jhuntev: thx17:26
=== beuno-lunch is now known as beuno
seb128kirkland, did you guys agree to use a new source? should the sponsors be unsubscribed from this bug for now then?17:46
seb128kirkland, the openssh one17:46
kirklandseb128: sure, just assign the bug to me17:47
seb128ok thanks17:47
kirklandcjwatson: presumably you're subscribed to  openssh-unix-dev@mindrot.org?17:49
kirklandcjwatson: and presumably you won't want me to explicitly CC you on my note to them?17:49
cjwatsonkirkland: right17:55
cjwatson(well, I read it via a news gateway)017:55
jhuntcjwatson: I'm confused by the Forwarded quilt field. I'm fixing this bug in lp:ubuntu/busybox, so to generate the upstream git patch, do I use the bzr-git to patch "lp:busybox" and export a git patch, mail to the busyboxy mailing list and then ref. *that* patch in my lp:ubuntu/busybox quilt patch?18:04
cjwatsonjhunt: upstream will probably respond best if you just generate a patch using git format-patch for them18:04
cjwatsonbased on whatever their current tip of development is18:05
cjwatsonjhunt: so normally, TBH, I just copy the patch around between two trees :)18:05
juliankWho does not love git format-patch?18:05
cjwatsonthough I mean a patch is a patch is a patch, so if you generate it with bzr-git I shouldn't imagine it would go too badly wrong18:06
cjwatsonanyway, Forwarded just wants a URL so that you can show you've sent the patch somewhere18:06
juliankcjwatson: git patches can be applied directly and have a commit message; so it's a bit easier (just git am 0001-my-patch.patch)18:07
jelmercjwatson, jhunt: "bzr send --format=git" generates git-format-patch-like patch files18:07
juliankjelmer: Cool18:08
jhuntcjwatson: thx, so I *think* I fix the bug in lp:busybox, bzr send it upstream, then pull that into lp:ubuntu/busybox as a quilt patch, build it, upload to ppa and request sponsorship. This bug is turning into a four-act epic... :)18:09
jelmerThere's also "bzr diff --format=git". I'm not sure if anybody other than myself is using either at the moment though.18:09
cjwatsonjhunt: it gets quicker as you build up habits18:11
juliankjelmer: I get bzr: ERROR: Bad value "git" for option "format". - am I missing something?18:12
jhuntcjwatson: whoever said this isn't easy? :)18:12
* jhunt goes for a strong drink and a lie down...18:12
jelmerjuliank: do you have bzr-git installed?18:12
cjwatsonjhunt: I don't really think about it any more18:12
juliankjelmer: I thought I had it installed, but I didn't.18:13
cjwatsonyou get used to lobbing patches around into the right places18:13
=== al-maisan is now known as almaisan-away
bdrungebroder: around?18:18
smoserpedro_, hggdh has implicated you. suggesting that you may have been running some lp:qa-regression-testing on lucid-proposed kernel (2.6.32-311.23)18:31
* hggdh hides, fast18:32
pedro_smoser, yes, for this kernel cycle i've running test-kernel.py and test-kernel-root-ops.py18:33
smoserso do you have results ? i'm completely unaware of how long that takes or what it entails18:34
pedro_i do, one sec18:34
pedro_smoser, http://people.canonical.com/~pedro/kernel/18:35
pedro_smoser, in there you can find the results and as well from autotest and ltp for maverick, lucid and karmic proposed kernels18:35
smoserpedro_, so, that represents "PASS" ?18:36
pedro_yes18:36
smoserpedro_, so, based on that, i'm going to mark changelog mentioned bugs as "verification-done"18:39
ebroderbdrung: Here now; will be caught up on backlog momentarily18:39
smoserand i'll point at your results. do you have any issue with that?18:39
pedro_smoser, ok nice, i'm commenting on the tracking bugs right now18:39
smoseroh.18:39
smoserwell, then you can do the 'verification-done' also18:40
smoseror maybe just let that up to an SRU person, but in the past pitti told me that i could change the tag if i'd done it.18:40
pedro_smoser, the tests were done by Monday but we were waiting for HW cert team to provide their results first, just following the https://wiki.ubuntu.com/Kernel/StableReleaseCadence#Tracking%20Bug%20Procedure18:41
pedro_smoser, but just a few minutes ago marjo said it's ok to comment on it and that the procedure is going to be fixed18:41
marjopedro, smoser: according to sconklin, qa team can post results, but we shouldn't be changing any tags until both hw cert & qa team are done18:45
pedro_marjo, smoser ok our part is done (qa team) now we have to wait for hw cert18:45
pedro_for maverick, lucid and karmic kernels18:45
marjopedro: ack18:45
marjopedro: nice job!18:46
pedro_hggdh, ^ that goes for you too ;-)18:46
pedro_thanks a lot marjo18:46
hggdhpedro_: this is relative to kernel updates, right?18:46
pedro_hggdh, yes Señor18:47
hggdhpedro_: muchas gracias18:48
bdrungebroder: i reviewed your backportpackage branch and i have some requests18:50
smoserok, so someone from QA is going to mark the relavant bugs as "verification-done" ?18:50
dokoI didn't like cmake that much in the past, but looking at the alternatives like handcrafted build systems and cmake, ... I do like it better18:50
smoserand we're waiting on some hw cert tests, is that right ?18:50
pedro_smoser, yes18:51
smoserany idea on how long that is going to be ?18:51
smoser(not nagging, asking)18:51
pedro_cr3, ^ ?18:51
bdrungebroder: you probably have to unquote the dsc url from launchpad (to convert "%2b" -> "+")18:52
bdrungebroder: you should evaluate if the package build process failed18:53
ebroderKeybuk, jhunt: I forget - why did you guys decide to do /etc/init/foo.override instead of a separate directory? Separate directories seems to me like it would enable more things easily down the road (e.g. using /etc/init.user + ~/.init for user sessions)18:53
ebroderbdrung: What do you mean by evaluate if the build failed? Right now it throws an error, doesn't it?18:54
bdrungebroder: biulder.build(...) returns the return code of the build command (should be 0 on success)18:55
bdrungebroder: example package for unquoting: qemu-kvm and abraca18:55
ebroderbdrung: Sure, the unquoting is easy. What do you think it should do if the build fails?18:57
bdrungebroder: print an error and abort (if you don't like that, then change the default for the upload question to no)18:58
ebroderbdrung: Nope, I like bailing. It's nice and simple18:59
bdrungebroder: i don't like global variables. you could pass lp to the function that require it.19:00
ebroderbdrung: :(, but ok19:00
bdrungebroder: 4) instead of passing opts to the subfunction you could pass the needed opts.foo instead19:01
bdrungebroder: optional 1) allow specifying the workdir (and then don't purge it)19:02
bdrungebroder: optional 2) allow a dsc as input19:02
bdrungebroder: optional 3) i want the workdir in /tmp for sponsor-patch too19:03
bdrungebroder: 5) give examples in the man page of backportpackage19:03
bdrungcjwatson: should grep-merges be installed? then you have to add it to setup.py. and please add some examples to the man page of grep-merges19:04
ebroderbdrung: Ok, I can do all of those. Can I do the same thing - default to mkdtemp() and clean it up afterwards, unless you specify a working dir?19:05
bdrungebroder: yes19:05
ebroderbdrung: Great19:05
bdrungebroder: you can do the optional things in separate branches19:05
bdrung- i want to get your backportpackage branch merged19:06
ebroderbdrung: The optional things are generally easier than the non-optional ones, so I'll probably do them all at once :-P19:07
ScottKebroder: I finally took a look at your merge request.  I have a couple of comments.19:11
ScottK1.  -f tends to be kind of hard wired in people's brains as "force" (at least mine anyway).  Can we use something else?19:12
ScottKMaybe -s/--source -d/--destination?19:12
ScottK2. Could to/destination default to whatever release the target system is running.  I suspect that will be by far the common case.19:13
ebroderYeah, I described them like that at first, but I was worried that people would conflate --source and the source package name19:13
ebroderYes, that's a reasonable default. I'll put that on my TODO19:13
bdrungebroder: i like the -s/--source -d/--destination idea19:13
=== Sarvatt_ is now known as Sarvatt
ebroderOk. I have no objections to --source/--destination19:14
ScottKebroder: Also it'd be nice if there were a way to specify a standard destination in a config file so you didn't have to specify it each time.19:14
bdrungi suggest to have a environment variable for that19:15
bdrungsame for upload destination19:15
ScottKconfig file or environment variable are fine, but I think that might be a bit magical for non-experienced users.19:15
ScottK(where that == environment variable)19:16
ebroderScottK: We already use environment variables in things like sponsor-patch, so this would be consistent. Also in backportpackage for things like UBUNTUTOOLS_BUILDER19:16
ScottKebroder: Yes, but sponsor patch is aimed at a developer user and this targets a broader audience.19:16
ScottKWhichever you prefer though, I'm OK with it.19:17
bdrungScottK: we could use the devscripts config file for setting the environment variables19:17
bdrungthen we have both19:17
ScottKSounds reasonable as long as it's documented.19:18
ebroderWhatever I do will end up in the manpage19:18
bdrungScottK: bug #68169319:19
ubottuLaunchpad bug 681693 in ubuntu-dev-tools (Ubuntu) "[wishlist] u-d-t config file" [Wishlist,New] https://launchpad.net/bugs/68169319:19
ScottKOK.19:19
ebroderbdrung: I'm thinking of supporting both an UBUNTUTOOLS_UPLOAD and BACKPORTPACKAGE_UPLOAD, and would probably also add a SPONSOR_PATCH_UPLOAD. Personally, I have separate PPAs for backports vs. non-backport tests, since the archive dependencies are different, so I want to be able to set that default separately. Seem reasonable?19:24
bdrungebroder: yes19:24
bdrungebroder: go ahead :)19:25
ebroderbdrung: Awesome. I'll try to get an update to my branch ready for you in the next day or two19:25
bdrungebroder: ok19:26
bdrungebroder: i would like to get a current version of backportpackage merged and then merge improvement (like upload env variables, workdir chnange, ...) merged separately (= easier to review)19:31
bdrungs/merged//19:32
=== ameetp_ is now known as ameetp
bdrungebroder: do you have the time to do the "required" task now and the optional ones later?19:37
cr3pedro_: which bug do you speak of, with smoser?19:40
smoserthe current -proposed kernel update19:40
cr3smoser: I believe brendan updated the lucid one with something like in progress and it will be extended approprietaly when done, I believe19:41
=== dendro-afk is now known as dendrobates
smosercr3, so, i'm just wondering what the time frame is19:45
smoserbugs referenced are bug 613381, bug 628776, bug 643891, bug 668380, bug 681132, bug 68325719:45
ubottuLaunchpad bug 613381 in linux (Ubuntu) "S3 resume hang when PCI Express wakeups don't clear the PM1 PCI_WAKE_DISABLE bit" [Medium,Fix committed] https://launchpad.net/bugs/61338119:45
ubottuLaunchpad bug 628776 in linux (Ubuntu Lucid) "HP NC511i Driver (be2net and be2scsi) is missing in kernel module udebs" [Low,Fix committed] https://launchpad.net/bugs/62877619:45
ubottuLaunchpad bug 643891 in linux (Ubuntu) "[IDT 92HD71B7X] ALSA test tone not correctly played back" [Undecided,In progress] https://launchpad.net/bugs/64389119:45
ubottuLaunchpad bug 668380 in linux (Ubuntu Lucid) "Lucid update to 2.6.32.25 stable release" [Medium,Fix committed] https://launchpad.net/bugs/66838019:45
ubottuLaunchpad bug 681132 in linux (Ubuntu Lucid) "Lucid update to 2.6.32.26+drm33.11 stable release" [Medium,Fix committed] https://launchpad.net/bugs/68113219:45
cr3smoser: my understanding is that certification only tests that systems can still install and boot the new kernel, whereas qa tests for specific regressions19:46
smoserwell, yes. and they've run that test suite, so i'm just wondering when you would expect that the certification tests would be done19:47
cr3smoser: Friday19:47
cr3smoser: please be patient with us, we're training new folks so that we can reduce the timeframe over time19:48
smosercr3, i promise, i'm just asking19:49
cr3smoser: cool, just thought I'd take this opportunity to reassure you we'll be getting awesomer :)19:50
seb128@pilot out19:51
=== udevbot changed the topic of #ubuntu-devel to: Archive: Open | Development of Ubuntu (not support, not app development) | #ubuntu for support and general discussion for dapper -> maverick | #ubuntu-app-devel for application development on Ubuntu | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://wiki.ubuntu.com/HelpingWithBugs | Current Friendly Patch Pilots: smoser`
bdrunggreat work seb128 - we are down to 32 task waiting for sponsoring19:53
seb128bdrung, thanks19:53
bdrungseb128: now i can see the whole sponsoring table without scrolling :)19:54
seb128;-)19:54
ebroderbdrung: Probably not until this evening - I should probably at least pretend to do work while I'm at work :)20:00
bdrungebroder: you are doing work - work for ubuntu :P20:01
bdrungebroder: in which time zone do you live?20:01
ari-tczewbdrung: which resolution do you use?20:03
bdrungari-tczew: fullhd - 1920x108020:04
bdrungups - 1920x120020:04
ari-tczewbdrung: aaa, then you can use look on SQ without scrolling :P20:04
ari-tczewbdrung: btw. could you sponsor BlackZ's merges for main? some of them are lying so long20:04
bdrungari-tczew: which one?20:05
ari-tczewbdrung: bug 685860 and bug 68141820:05
ubottuLaunchpad bug 685860 in nfs-utils (Ubuntu) "Please merge nfs-utils 1:1.2.2-4 (main) from debian unstable (main)" [Wishlist,New] https://launchpad.net/bugs/68586020:06
ubottuLaunchpad bug 681418 in e2fsprogs (Ubuntu) "Please merge e2fsprogs 1.41.12-2 (main) from debian unstable (main)" [Wishlist,New] https://launchpad.net/bugs/68141820:06
ebroderbdrung: US/Pacific20:08
bdrungebroder: that explains a lot20:10
=== akshatj is now known as akshatj|bed
=== dendrobates is now known as dendro-afk
=== dendro-afk is now known as dendrobates
aantnbeuno: are you martin albisetti?20:36
beunoaantn, yes I am20:36
cjwatsonbdrung: I *did* add it to setup.py, didn't I?20:48
cjwatsonoh, blast, forgot to commit that bit20:49
cjwatsonbdrung: do you think it needs examples?  it's really simple :)20:49
bdrungcjwatson: no, you didn't. :P20:49
bdrungcjwatson: yes, what kind of regexp are commonly used?20:50
cjwatsonI had the diff locally, honest20:50
cjwatsonit's just a substring match20:50
cjwatsonanyway, have to go for dinner, I'll do that part later20:50
apwcjwatson, it feels like linux-headers package installs are taking a long time on natty again ... has something changed ?20:57
=== sconklin-lunch is now known as sconklin
=== Sarvatt_ is now known as Sarvatt
hallyn_hm.  'bzr: ERROR: Merge upstream in merge mode is not yet supported.21:42
hallyn_kirkland: ^  that's what i get when i do 'bzr merge-upstream' from the vmbuilder-packaging tree21:43
cjwatsonapw: dunno, but things are *going* to change again in dpkg so not worth debugging right now21:53
cjwatsonapw: you can put force-unsafe-io in /etc/dpkg/dpkg.cfg now to turn off fsyncs across the board (at your own risk)21:53
apwcjwatson, ok thanks, i'll just leave it be, and keep an eye on it21:54
cjwatsonwe did go back to fsync(2) because sync(2) caused other problems - but there's a dpkg 1.15.8.7 on its way soon21:54
cjwatsonwhich uses sync_file_range(2) at tytso's suggestion21:54
apwcjwatson, sounds interesting21:55
apwcjwatson, we ended up needing to do a quick upload for something else so that vt numbering change is in with it ... should be built by the morning21:56
cjwatsoncool, thanks21:57
cjwatsonbdrung: example added no21:57
cjwatsonnow21:57
barrycan someone with perms please retry this build: https://launchpad.net/ubuntu/+source/pymvpa/0.4.5~dev23-2build1/+build/207660522:31
barryi think the underlying bug that caused this has been fixed (iow, it wfm locally)22:32
ebroderbarry: Sure, just a sec22:33
barryebroder: thanks22:33
ebroderDone22:33
* barry watches and crosses his fingers22:35
=== dendrobates is now known as dendro-afk
kirklandany idea why right clicking is not working in Natty?22:47
crimsunlool: while cleaning BTS, I noticed #460197. Are you experiencing this in Ubuntu as well?22:49
geserI hope we don't optimize for mice with one button :)22:49
kirklandhttps://bugs.launchpad.net/ubuntu/+source/sudo/+bug/69087322:53
ubottuUbuntu bug 690873 in sudo (Ubuntu) "latest natty sudo upgrade removes admin from /etc/sudoers" [Critical,Triaged]22:54
kirklandbe very careful if you upgrade sudo right now in natty ....22:54
kirklandkees: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/69087322:58
ubottuUbuntu bug 690873 in sudo (Ubuntu) "latest natty sudo upgrade removes admin from /etc/sudoers" [Critical,Triaged]22:58
kirklandkees: looks like blackz did the merge earlier today22:58
micahgbdrung: ^^22:59
kirklandkees: debian has changed /etc/sudoers to be a conffile, and wants to use a /etc/sudoers.d dir22:59
keesyeah, looks like sudo made /etc/sudoers a conffile when it wasn't one before.22:59
keesI can't find what added %admin originally...22:59
StevenKd-i?22:59
keesStevenK: not sure, but we need to fix sudo quickly and hard!22:59
kirklandkees: possibly installer magic?23:00
StevenKDo we want to block the sudo update on the mirror?23:00
keesI don't see it in any maintainer scripts I have installed, so yeah, must be installer.23:00
wgrantHas someone told ubuntustatus on identi.ca and twitter?23:01
keesslangasek: do you know this area at all?23:01
ebroderkees: Any chance it's user-setup or something like that?23:01
Laneycan you still block updates after they have been mirrored?23:01
wgrantLaney: Sort of.23:01
keeskirkland: can you pastebin the resulting sudoers file from sudo?23:01
wgrantLaney: We can chmod -r23:01
kirklandkees: sure23:01
wgrantAnd then force a mirror push.23:01
Laneyyeah, like that23:02
kirklandkees: before or after?23:02
keeselmo: awake?23:02
keeskirkland: after23:02
kirklandkees: http://pastebin.com/g1ghJNaX23:02
kirklandkees: that's straight out of debian/sudoers in the current sudo source23:02
keesUgh. Yeah, it even removes the ticket defaults.23:02
kirklandStevenK: I think it would be a good idea23:03
wgrantWho has access to identi.ca/ubuntustatus?23:04
kirklandStevenK: the conffile conflict defaults to "N" (keep my local copy), which is "something";  but I still breezed over the diff without noticing the -%admin the first time23:04
wgrantIt is for precisely this purpose.23:04
kirklandwgrant: not sure ... rickspencer3 ?23:04
kirklandrobbiew: ?23:04
JackyAlcineEvening, guys.23:05
kirklandkees: http://pastebin.com/Sze9Yk3H23:06
kirklandkees: that's the unbroken one23:06
kirklandkees: as a quickie, we could put the contents of that into the sudo package's debian/sudoers file23:06
ebroderkees: Ticket defaults? I don't remember there ever being ticket defaults...23:06
kirklandkees: so at least there's no diff when upgrading23:06
ebroderkirkland: We probably shouldn't if we were adding it as part of the installer before. That'd be a change in behavior for...people who do screwy things not involving the installer23:07
kirklandkees: for those who haven't modified their /etc/sudoers23:07
ebroderkees, kirkland: The snippet is added by user-setup-apply in user-setup23:07
keesebroder: ah, good find.23:08
ebroderDon't know if there's separate code somewhere in ubiquity23:08
ebrodercjwatson or ev would have a better idea23:08
keeskirkland: everyone has modified their /etc/sudoers because it's going from non-conffile to conffile, iiuc.23:08
kirklandkees: yes, but the delta could be zero23:08
ebroderkees: Yeah, looks like there's a copy of the user-setup source package in d-i/source/user-setup in ubiquity23:09
kirklandkees: anyway, that would just be quick and dirty to keep this from breaking in the near term23:09
ebroderSo you'd need to be sure to update that as well23:09
StevenKebroder: There's a script in ubiquity that will sync new code from d-i into it23:09
keesso, it looks like this will only break people if they say "Y" to the prompt23:09
kirklandkees: correct23:09
ebroderHow hard would it be for sudo's postinst to take everything in /etc/sudoers that didn't ship there and throw it in /etc/sudoers.d/50-custom? (Conditionalized on dpkg --compare-versions "$2" -lt "whatever", or whatever)23:10
StevenKkirkland, kees: If DEBIAN_FRONTEND is noninteractive, the default is N, right?23:10
kirklandStevenK: yes23:10
keesStevenK: right23:11
keesso, I thought the defaults were Defaults!lecture,tty_tickets,!fqdn for sudoers?23:11
keesdid that go away?23:11
ebroderkees: I don't remember ever seeing that in any of my sudoers files23:11
kirklandkees: from where I was sitting, though, I knew that I hadn't modified my own local /etc/sudoers, so I figured, meh, whatever Ubuntu recommends is good 'nough for me23:11
keeshunh23:11
ebroderkees: Looks like we compile those defaults in23:12
ebroder  * Merge from debian unstable.  Remaining changes:23:12
ebroder   - debian/rules:23:12
keesebroder: yup, this is an oooold sudoers file :)23:12
ebroder     - compile with --without-lecture --with-tty-tickets (Ubuntu specific)23:12
kirklandkees: hmm, so what do you think we should do with this?23:19
StevenKkirkland: Do you think we should block the update and upload a revert?23:20
keeskirkland: get the foundations folks to look at it. it'll only get people into trouble if they answer "Y", so I don't think this exactly qualifies for an archive block.23:20
wgrantkees: I would Y, since I know I haven't modified it myself.23:21
keeswgrant: it'll _always_ prompt, though, since it wasn't a conffile before. it'll prompt _everyone_.23:21
StevenKSo perhaps an ubuntustatus and u-d-a mail warning?23:21
kirklandwgrant: right, that's more or less what I did23:21
keeswgrant: ah, I see what you mean now23:22
wgrant(I personally wouldn't, but I know lots of people who would)23:22
ebroderWe should definitely change user-setup to use sudoers.d. That seems like it should be uncontroversial and will at least unbreak new installs23:22
keesStevenK: what about an upload that doesn't ship the sudoers file for now?23:22
keesI really don't know the best way to approach this.23:23
kirklandkees: yeah, i basically have that here now23:23
StevenKI'm not sure either23:23
kirklandkees: it's just a couple of lines to comment out of debian/rules23:23
ebroderThe upgrade path is annoying because the change was made by a package that doesn't get installed on the real system23:23
micahgBTW, conffile change is debian 605130 FWIW23:24
ubottuDebian bug 605130 in sudo "sudo: unowned files after purge (policy 6.8)" [Important,Fixed] http://bugs.debian.org/60513023:24
StevenKlamont: If you're around, ^23:24
* kees ponders a preinst that detects %admin and writes a file into /etc/sudoers.d for it.23:25
keesgah, what a mess.23:25
wgrantBlock and revert the update for now, I think.23:25
StevenKGoing from no conffile to conffile is always going to suck. Rocks.23:26
wgrantThen a proper fix can be devised at our leisure.23:26
keeswgrant: yeah, probably true.23:26
kirklandkees: actually, the easiest solution would be to just put the necessary %admin bit in the new /etc/sudoers.d23:26
ebroderkees: What about detecting if sha1sum /etc/sudoers == "some known value" (or alternatively in [list, of, known, values]), and if it does (is), writes the %admin line to /etc/sudoers.d and resets /etc/sudoers?23:26
ebroderkirkland: I don't think the sudo package should unconditionally put the %admin line in. That's not what it's done previously23:27
kirklandkees: people who answer "N" will continue working as normal23:27
micahgebroder: that won't help if people add select sudo rights23:27
keesebroder: right, I think that'll likely be the solution, but gathering that list of known values, or the stuff around it is what'll take time to test right23:27
ebrodermicahg: Yes, but if they know they've modified the conffile, they'll look more closely23:27
kirklandkees: ah, i just saw your ponderance23:27
kirklandkees: yeah, that's fine23:27
slangasekkees: ugh; not deeply familiar, no23:30
keesslangasek: okay, no worries.23:31
ebroderkees: I don't know about older releases, but Maverick's sudo.postinst doesn't change /etc/sudoers on upgrades. If that's true going back, then there shouldn't be many cases to test for23:32
keesebroder: right, it should be finite, but I don't want to gather that list in a rush.23:33
ebroderkees: Yeah, that's reasonable23:33
Laneyeveryone is going to get a conffile prompt regardless, right?23:34
slangasekshouldn't, if it's fixed right23:34
ebroderLaney: Not if we reset /etc/sudoers to match the conffile in a preinst :)23:34
Laneywhat conffile? it wasn't one before23:34
ebroderOh, hmm. Maybe you just remove the old file?23:34
slangasekwhy wouldn't we just add the %admin line into the conffile as shipped?23:35
keesLaney: right, a well-written preinst will handle the existing /etc/sudoers and potentially remove it completely23:35
Laneyright23:35
slangasekinstead of trying to match what Debian is doing here23:35
keesslangasek: hunh, yeah, I guess that would be reasonable as a crisis-workaround.23:35
kirklandkees: they have a %sudo line in theres23:36
keesslangasek: the prompt needs to be fixed regardless, but that would stop people from having unsudoable systems23:36
Laneythat's a reasonable immediate fix23:36
slangasekkees: fwiw I think it might even be the correct long-term solution23:36
ebroderslangasek: I kind of figured someone made a deliberate choice to put the %admin line in user-setup instead of in sudo23:36
keesebroder: yeah, that was my thinking too23:36
slangasekkees: if it's done correctly to where the conffile now matches the default generated file, then the conffile prompt goes out anyway23:36
Laneyeven if this is becoming a conffile for the first time?23:37
Laneyif so, then +123:37
slangasekyes23:37
keesslangasek: it's different at least due to the change of uncommenting the "include" directive23:37
slangasekah23:37
slangasekin that case you'd have to do the preinst md5sum && rm trick23:37
Laneyseems like something that would be reasonable for dpkg-maintscript-helper23:38
keesyeah, there's a non-trivial number of possible contents for the default /etc/sudoers, depending on which release you first installed. :(23:38
slangasekbut still, I think it's simpler for the conffile to include everything we expect to be there on upgrade23:38
hallyn_all rightg whoever just uploaded sudo with cldeaned ut conffile is on mhy naughty list :)23:38
kirklandhallyn_: yup23:38
ebroderhallyn_: Read the scrollback. It never had the %admin line, so this is a non-obvious multi-package interaction23:38
kirklandhallyn_: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/69087323:38
ubottuUbuntu bug 690873 in sudo (Ubuntu) "latest natty sudo upgrade removes admin from /etc/sudoers" [Critical,Triaged]23:38
kirklandhallyn_: that's quite possibly the worst typo'd sentence I've ever seen from you :-)23:40
Laneydrunk with no-more-sudo rage23:40
keeshaha23:40
hallyn_:)23:40
hallyn_on n90023:41
kirkland:-)23:41
kirklandhallyn_: sudo locked you out of your system then?23:41
hallyn_yeah, but i was walking ojut the door23:41
kirklandhallyn_: boot a live cd, mount your root disk and:23:41
kirklandecho "%admin ALL=(ALL) ALL" >> /etc/sudoers23:42
kirklandwell, to /etc/sudoers on your root disk, of course23:42
hallyn_kirkland: no worries i have reswcue mode23:42
ebroderkirkland, hallyn_: If you put it in /etc/sudoers.d/admin instead, you won't run into this problem in the future23:42
ebroderSo it looks like user-setup has been adding the %admin line since more or less time immemorial. r1 of user-setup in UDD :)23:46
=== oubiwann-holiday is now known as oubiwann

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!