/srv/irclogs.ubuntu.com/2010/02/24/#ubuntu-devel.txt

superm1and cjwatson had a commit for the fix to bug 524169  on the tree ready to go too00:05
ubottuLaunchpad bug 524169 in ubiquity "Ubiquity installer partitioner crashed, main installer enters endless loop" [High,Fix committed] https://launchpad.net/bugs/52416900:05
slangaseksuperm1: ok, that sounds like a set worth uploading then00:07
slangaseksuperm1: please go ahead00:07
superm1alrighty, thanks00:07
Sarvattso something is sending a quit signal to x's controlling tty when some people press enter after first boot ( http://paste.ubuntu.com/382615/ shows it coming from the tty layer) when plymouth is used. suse seems to be getting around it with http://suse-moblin.com/obs-status/Moblin:Factory/aaa_base/aaa_base-bootsplash.patch anyone familiar enough with plymouth to dig into it more? i noticed one place where it could be resetting the ISIG flag o00:10
Sarvattn plymouths tty (in src/libplybootsplash/ply-terminal.c) so the enter key (0x1c) becomes Control-\ (0x1c) if the same VT is used for X but its a bit over my head.00:10
slangasekpitti, bryceh: what's the status of hal removal now?  I see it included on daily desktop ISOs, which seems to put the lie to what was written in the A2 tech overview :)00:23
brycehslangasek, afaik we no longer use it for anything00:23
brycehslangasek, so if you spot something X-ish which does, let me know as it's a bug00:24
slangasekit's in main because of libvirt-bin, but that doesn't explain it being on the CD; will dig00:24
slangasekah, it's pitivi00:25
ccheneylol00:25
brycehheh00:25
slangasekseb128, robert_ancell: does pitivi need this Recommends: hal?00:25
robert_ancellslangasek, not sure, seb128 do you know?00:26
robert_ancellslangasek, thanks for your help with plymouth+upstart.  It's driving me insane :)00:26
seb128slangasek, yes00:26
slangasekseb128: waah - why? :)00:26
seb128slangasek, it needs to be ported to python-gudev00:26
slangasekrobert_ancell: is it /still/ driving you insane? :/00:26
seb128slangasek, because it uses it...00:27
robert_ancellslangasek, yeah.  I already knew about the /proc issue (I've tried mounting it before running plymouthd and modifying plymouthd to not require it)00:27
slangasekseb128: is that likely to happen in lucid?  I guess the daemon is no longer started by default so it's not a huge problem, right?00:27
robert_ancellslangasek, the problem I find is it's really hard to tell why it doesn't boot up00:27
seb128slangasek, https://bugzilla.gnome.org/show_bug.cgi?id=60592000:27
ubottuGnome bug 605920 in general "Switch to (g)udev for device detection/support (deprecation of HAL)" [Normal,New]00:27
slangasekrobert_ancell: even after fixing plymouthd to not mind if /proc is missing?00:28
seb128slangasek, would be nice for lucid, and correct for the start00:28
robert_ancellslangasek, yeah, did that ages ago.00:28
robert_ancellseb128, is gudev an official GNOME dependency?00:28
slangasekrobert_ancell: mmk; is there some way I can get my hands on a running environment of what you're working on, to poke at directly?00:28
seb128robert_ancell, yes, there was no python bindings though00:28
slangasek(not that I'll have time until Friday, but)00:28
seb128robert_ancell, pitti get that solved now00:29
robert_ancellseb128, that's what I was going to ask pitti - is the halsectomy an ubuntu goal and/or a GNOME goal?00:29
seb128both I guess00:29
seb128not an official GNOME goal that I know00:30
seb128but they work toward deprecating it too00:30
slangasekbryceh: is this note about not having wacom support obsolete in a3?  I see xserver-xorg-input-wacom is in now00:30
brycehslangasek, that's correct, wacom is good to go00:30
slangasek\o/00:30
Sarvattwell usb wacom support at least, serial digitizers still need an xserver change thats in git00:33
Kai_why is there a distribution upgrade available? I'm running lucid alpha 2.00:34
persiaKai_: Probably as part of the testing for the upcoming Alpha-3: you might get a more detailed answer in #ubuntu+100:35
Sarvattnext xserver upload will have it, most tablet pc's need that00:35
Kai_okay, thanks00:35
=== nhandler_ is now known as nhandler
ccheneyis there a known issue with lucid that when you do autologin it doesn't seem to change to the X server00:52
ccheneyi see the xcursor but not the rest of X00:53
ccheney16.5s boot from upgraded lucid (not clean install by any stretch) not bad at all :)00:54
ccheneyit just doesn't show X properly for some reason :-\00:54
=== bladernr_ is now known as bladernr|away
ccheneyhmm it worked after trying again01:04
ccheneyseems to not be completely stable for me for some reason01:04
slangasekmdeslaur, zul: where did /etc/network/if-up.d/samba go in samba 2:3.4.5~dfsg-2ubuntu1 ?  this should have been kept until the conversion to upstart could be done (bug #526659)01:09
ubottuLaunchpad bug 526659 in samba "nmbd fails to start at boot time" [Undecided,New] https://launchpad.net/bugs/52665901:09
slangasekccheney: bug #521175; would love it if you could figure out *why* autologin is different01:09
ubottuLaunchpad bug 521175 in plymouth "Plymouth AND Automatic Login enabled system freezes" [Undecided,Incomplete] https://launchpad.net/bugs/52117501:09
mdeslaurslangasek: looking now01:09
slangasekmdeslaur: if it's broken anyway, I'm inclined to just upload for bug #523868, I'm just surprised to see this regression01:11
ubottuLaunchpad bug 523868 in samba "FFe request: samba upstartification" [Low,New] https://launchpad.net/bugs/52386801:11
ccheneyslangasek: it didn't actually freeze for me, some of the times the xcursor showed up but not the rest of the desktop, other times it came up all the way but then x would crash after a short time, but would respawn ok01:11
ccheneyon intel x450001:11
slangasekccheney: all the same thing.  Does gdm come up ok when *not* using autologin?01:12
ccheneyslangasek: yea01:12
ccheneyslangasek: and even when x didn't come up all the way i could still switch vt's01:13
slangasekccheney: yep.  So somewhere in the gdm logic to interface with plymouth, there's a bug when autologin is used; but I couldn't find it when I tried to trace the gdm code01:13
smosercan someone accept nomination for lucid for https://bugs.launchpad.net/ubuntu/+source/euca2ools/+bug/52669701:13
ccheneyoh ok01:13
ubottuLaunchpad bug 526697 in euca2ools "euca-describe-images has incorrect order of ramdisk and kernel" [High,Confirmed]01:13
ccheneyon the times i booted up and xcursor was all that showed it played the login music with just the black screen, one time i switched vt's and the desktop showed up, iirc it crashed soon afterward though01:14
ccheneyso maybe some kind of bug with the vt switching in plymouth/gdm, but not really sure01:14
Sarvattevery time that's happened to me ureadahead was reprofiling, could just be a coincidence though.01:19
slangasekthere very definitely seems to be something different in gdm's interaction with plymouth when using autologin01:20
slangasekif someone can figure out what, that's probably the bug01:21
slangasek(and knowing what it is might help me fix other plymouth bugs, fwiw)01:21
mdeslaurslangasek: looks like the samba in lucid never got the if-up.d file added to debian/samba.files01:26
mdeslaurzul: ^01:26
slangasekmdeslaur: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/462169/comments/6401:27
ubottuLaunchpad bug 462169 in samba "nmbd dies on startup when network interfaces are not up yet" [High,Fix released]01:27
zulmdeslaur: i remember putting it in lucid its in lucid-updates as well01:28
mdeslaurzul: you forgot to add it to debian/samba.files01:28
mdeslaurzul: http://launchpadlibrarian.net/38098612/samba_2%3A3.4.3-2ubuntu1_2%3A3.4.3-2ubuntu2.diff.gz01:28
zulfrig...01:28
zulmy bad01:28
slangasekhuh, ok :)01:29
* mdeslaur votes for the upstart job :)01:29
zulas do i :)01:29
=== nhandler_ is now known as nhandler
homebrewcideranybody use dvbcut? i get an error message saying "the chosen file *** contaqins no video"    anybody come across the before?01:45
micahg!support | homebrewcider01:46
ubottuhomebrewcider: The official ubuntu support channel is #ubuntu. Please be aware that this channel is for development only.01:46
homebrewcideroops sorry01:47
homebrewciderclicked the wrong room01:47
persiahappens to everyone once :)01:47
=== nhandler_ is now known as nhandler
=== Kai_ is now known as Kaj_
ScottKSome much more frequently than that.02:55
=== Kaj_ is now known as Kai_
mohaao/03:40
mohaa  /usr/lib/claws-mail/plugins/notification_plugin.so: undefined symbol: menu_create_items03:40
mohaai'm having issues with 2 plugins in claws-mail03:40
mohaanotification and att_remover03:41
mohaais that here that i should adress  or to maintainer ?03:41
jdongmohaa: best to file a bug on launchpa03:53
jdongd03:53
jdongubuntu-bug claws-mail03:53
mohaadoing it03:54
mohaalikely, it's too complicated :D03:54
jdongawesome, thank you.03:54
* mohaa mad at maintainers not using their builds :P03:54
jdongwe're not being mean and trying to send you to the proverbial RT, just the bug tracker is the best way of getting the attention of those who care, so to speak.03:55
mohaaactually in this case CLAWS-MAIL has been upgraded  and not the plugins   -_-03:55
mohaaso we have fresh client  and plugins compiled for an older version of claws :-\03:56
jdongis this on karmic or lucid?03:56
mohaa:o03:56
mohaa9.0403:56
jdonggroan... yikes.03:56
mohaai don't use this system much so....03:57
jdongugh *rant mode* plugin packagers should properly depend on the version of the parent program they need....03:57
mohaa:D03:57
jdong*end rant* :)03:57
ScottKIIRC the one Ubuntu dev I know of that uses claws mail wasn't that active during Jaunty development.03:57
ScottKjdong: It probably just needs a rebuild.03:57
mohaai see it03:57
jdongwhy am I getting a deja vu moment.03:57
mohaait's still on 3.6 series  :-\03:57
* ScottK used to need to care about claws when it has clamav plugin.03:58
mohaaScottK_san it still has it  ;)03:58
nigelbmohaa: you probably could check this ppa https://launchpad.net/~claws-mail/+archive/ppa03:59
mohaanigelb  thx :)03:59
mohaai'm using a quite old buntu so...04:00
syn-ackhey, didnt Alpha 3 drop today?04:02
brycehThursday04:03
syn-ackI could have sworn the timeline said today04:03
brycehFebruary 25th04:04
syn-ackMust have confused it with the rebuild test04:04
jdongI think a 3-day pushback.04:04
syn-ackOk, so I'm NOT nuts04:04
jdongjust got the freeze announcement this morning04:04
jdongwhich mentioned a schedule delay :)04:04
jdongso no, you probably correctly marked your calendar04:05
mohaajdong: https://bugs.launchpad.net/ubuntu/+source/claws-mail/+bug/526831   ;)04:08
ubottuLaunchpad bug 526831 in claws-mail "Claws-mail : plugins built against different parent program" [Undecided,New]04:08
ScottKjdong: Milestone releases are always on Thursdays.04:15
jdongah, gotcha04:15
ScottKFreeze on Tuesday and release on Thursdays for Alphas.04:16
nasserashhello everyone: I'm trying to compile with gcc a program and I need the -lsocket library, I installed "happycoders-libsocket-dev" but I still get an error that says "/usr/bin/ld: cannot find -lsocket" any ideas ?04:59
mohaabye you guys04:59
mohaao/04:59
detIs it known if Lucid will ship with Mono 2.6 ?05:24
detIt is currently using 2.4, and 2.6 was released in December and contains many bug fixes05:25
micahgdet: it will probably be 2.4 as that's an LTS05:27
micahgdet: 2.6 will most likely be in lucid +105:28
detThat is very unfortunate, but thanks for the info05:28
micahgdet: it would be more unfortunate to have an unsupported version of mono in an LTS :)05:29
detWhat do you mean by unspported ?05:29
micahgdet: mono only supports branches for certain amounts of time, so if we ship a short support branch in a long term release, then we'll have a period of time w/out upstream fixes/patches05:30
detDo you happen to know that Mono 2.4 is a long term support branch, while 2.6 not?05:31
micahgdet: http://www.mono-project.com/Roadmap05:31
detI understand now, thanks.05:32
micahgdet: np :), LTS's aren't the place for latest and greatest anyways..people want stability more than features in tehm05:33
detPerhaps some of the bug fixes I am interested in from 2.6 are backported into the 2.4.3 release05:33
micahgdet: maybe and if they're not, maybe it can be requested05:33
detI will test out the Lucid alpha-205:34
micahgdet: alpha 3 is coming thursday05:34
detWell, I am interested in testing mono 2.4.3, which I think alpha-2 has05:35
detI tried 2.6 from a suse live cd, and it solved some problems in an application05:36
pittiGood morning06:52
StevenKHi pitti!06:52
pittibryceh, slangasek: so the two remaining use cases of hal in lucid are: (1) pitivi, and (2) gnome-power-manager uses hal to change the backlight on devices which don't have XBACKLIGHT support (which is still the majority)06:54
pittislangasek, bryceh: hal was switched to d-bus activation, i. e. it does not start up on systems with xbacklight support on boot06:54
pittislangasek: I'm afraid we are stuck with that in lucid06:54
StevenKpitti: I guess pitivi uses hal for hardware notifications?06:55
pittiyes06:55
pittifinding cameras, etc.06:55
StevenKBleh06:55
brycehpitti, is the xbacklight issue already known upstream?06:55
StevenKHowever, g-p-m is the much harder one to kill :-/06:55
pittibryceh: yes, for a long time06:56
brycehbrb, gotta help put kiddo to bed06:56
pittibryceh: it's a matter of getting driver support for it06:56
pittiargh! a dist-upgrade here wants to install chromium now, WTH?06:57
StevenKWow, what's pulling that in ...06:59
brycehpitti, any work arounds?  Can whatever hal does be extracted into something more standalone?06:59
pittiargh, nevermind06:59
StevenKpitti: False alarm?07:00
pittibryceh: in theory yes, but in practice it'd be better to add xrandr support to drivers; otherwise you keep having two things which are responsible for the backlight control07:00
brycehpitti, hmm, well waiting for stuff to get added to drivers (X drivers at least) can take a while...07:03
pittiright07:03
pittibut I think there's no way we can make even a workaround happen in lucid07:03
dholbachgood morning07:07
slangasekpitti: ok, makes sense07:11
Mamarokis something wrong with the repo main server? it is extremely slow07:40
nigel_nbMamarok: yep.  same here07:50
mtx_initto much tv07:54
pittiaah, I tracked down the reason for the major udisks boot time increase \o/08:30
ogrageez, our armel images exploded in size ... darn openoffice08:30
pittiogra: when? which version of rhythmbox-ubuntuone-music-store do you have?08:31
ograpitti, did we inherit the new langs from you guys ?08:31
pittiogra: today's netbook images exploded by 40 MB, due to a wrong dependency in above08:31
ograpitti, the image from 22 is 540 vs 690 today :)08:31
* ogra check RB08:31
pittiogra: we dropped most languages from our seeds08:31
ogra*checks even08:32
ogra+rhythmbox-ubuntuone-music-store 0.0.2-0ubuntu208:32
pittithat's it08:32
ograhttp://paste.ubuntu.com/382809/ is the manifest diff08:32
pittiogra: you can substract 40 MB once  0.0.2-0ubuntu308:32
pittiis published08:32
ograah, cool08:32
ograstill bloated :)08:33
ogra540MB was so convenient :)08:33
pitti+default-jre 1.6-3408:33
pittithere you go08:33
pittidon't do that08:33
ograi think that came in with oo.o08:33
ograwe didnt change our seeds at all, we only use what you guys use for netbook now08:33
pittiogra: don't seed oo.o-base08:33
persiaIt's the *same* seed.08:34
ograit will go again once the online office spec is fully implemented08:34
ograuntil then we'll live with oo.o i guess ... its not oversized yet08:34
pittihm08:34
pitti-base is not seeded08:34
ograand 40MB less gets us back to 650 at least08:35
pittiso some wrong dependency pulls it back in08:35
pittiit's not on the i386/amd64 ones08:35
ograstrange08:35
ograthe seeds are identical, as persia stated abov08:35
ograe08:35
pittiogra: we recently had that problem on i386/amd64 as well08:36
ograwhat was the issue ?08:36
pittisome oo.o translation package depended on language-support-writing-en | openoffice.org08:36
pittisomething like that08:36
pittibut that got fixed during the sprint08:36
ograweird, there shouldnt be any armel specific deps08:36
pittiit's definitively not a seed problem08:36
pitti+openoffice.org-report-builder-bin 1:3.2.0~rc4-1ubuntu108:37
pittinobody ever seeded stuff like that08:37
ograReverse Depends:08:37
ogra  openoffice.org-report-builder08:37
ogra  openoffice.org08:37
ograhmm, the same on x8608:38
pittiogra: perhaps some package is out of date on armel?08:40
=== yofel_ is now known as yofel
lifelesspitti: in my laptops dmesg09:19
lifelesspitti: actually, I lie09:19
lifelessI was sshed into a linode ;P ignore that09:20
pittihm, I'm pretty sure we disabled it in karmic09:20
pittiheh09:20
lifelessI do see udev spam on boot09:20
lifelessprobably stale rules or something09:20
pittilifeless: I see them from calibre09:20
pittibut I'm sure there's plenty of other broken/obsolete rules in packages out there :/09:20
* pitti will fix calibre soono09:21
pittis/o$//09:21
lifelesscalibre? free californians?09:21
pittiheh09:21
pittilifeless: e-book organizer/converter/creator09:21
lifelessnice09:22
lifelessI was trolling :>09:22
* pitti remembers to stop taking you seriously from now on :)09:23
pittilifeless: how's your Klingon these days?09:23
lifelesspitti: you should, when I'm not serious09:23
lifelesspitti: terrible, I don't know it09:23
lifelesspitti: I only set it up for you guys :>09:23
lifelesspitti: however, FF has a klingon pack too, now.09:30
=== tkamppeter_ is now known as tkamppeter
tseliotcjwatson: any ideas as to why "DEB_SHLIBDEPS_INCLUDE_$(PKG_driver) := debian/$(PKG_driver)/$(DRIDIR)/fglrx/:/$(DRIDIR)/" doesn't work with cdbs in this case? http://pastebin.ubuntu.com/382879/10:50
cjwatsonI don't really know cdbs ...?10:50
tseliotoh10:51
cjwatsonmaybe try 'export DH_VERBOSE=1' and run the relevant commands by hand to dig into it?10:51
tseliotcjwatson: ok, but you know debhelper. Basically what's happening here is that a binary depends on a library shipped by the same package10:52
tseliotok10:52
tseliotby hand?10:52
persiatseliot: Since debian/control is not supposed to change at build-time, can't you just hardcode the dependency for that library into debian/control?10:53
cjwatsonat a shell prompt10:53
tseliotpersia: the binary and the library it depends on are in the same package10:54
persiatseliot: The same source package or the same binary package?10:55
tseliotpersia: both things10:55
persiatseliot: Then why do you care about shlib:Depends there?  You know it's provided.  Just ship a symbols file for things that build against it.10:56
persiatseliot: If you're working around debug packages, you may want to request debhelper >= 6.0.3, but as long as you have debhlper >= 6.0.0 you shouldn't need -l anyway (which is what DEB_SHLIBDEPS_INCLUDE sets)11:02
Noisihi there! i try to cross compile with arm-linux-gcc a sqlclient to arm720t and i need lib mysqlclient. Must i compile it from soucre? How?  it would give me great pleasure for some tip.11:03
tseliotpersia: it's a proprietary library and it can get even messier. I've found out that my cdbs option works if I create a link (libfglrx_gamma.so.1) to libfglrx_gamma.so.1.0 (the actual library)11:03
tseliotpersia: as the error was dpkg-shlibdeps: error: couldn't find library libfglrx_gamma.so.111:04
persiatseliot: Ugh.  That's just messy.11:04
tseliotpersia: welcome to the world of fglrx ;)11:04
persiaNoisi: #ubuntu-arm might be a better forum.  There are precompiled binaries that might or might not work properly in a primarily cross-compiled environment.11:05
Noisipersia: Thanks :-)11:06
tseliotpersia: with that link I don't even need DEB_SHLIBDEPS_INCLUDE_11:07
persiatseliot: So, you're operating with binary blobs?  I suspect a gap between filenames and information presented from introspection (nm might let you confirm).  Drop the -l, add the symlink, and generate a symbols file just to verify stuff.11:07
persiatseliot: Well, if you use debhelper 5 you'd still need it :)  The fix is with debhelper 6.  What's debian/compat?11:07
tseliotpersia: 711:08
persiaYeah, then you very much don't need DEB_SHLIBDEPS_INCLUDE11:08
tseliotcjwatson, persia: ok, thanks for your help11:09
qenseIf we would like to get bug #506125 fixed we'd have to sync Nautilus Actions, because the fix is in 2.29.4. Otherwise I'd remove nautilus-actions since it now just doesn't work. Will nautilus-actions be synced to 2.30 in time for the Lucid release?11:14
ubottuLaunchpad bug 506125 in nautilus-actions "nautilus-actions-config-tool assert failure: NA-nact:ERROR:nact-ibackground-tab.c:381:get_folders_treeview: assertion failed: (GTK_IS_TREE_VIEW( treeview ))" [Medium,Triaged] https://launchpad.net/bugs/50612511:14
cjwatsonNoisi: you might also like to look into dpkg-cross11:16
cjwatson(requires some setup)11:16
sorenKeybuk: Mind if I bother you for a sec? In VMBuilder, I routinely mkfs some devmapper devices. Immediately afterwards, I use blkid to extract the uuid. Occasionally, blkid fails (exit code 2).11:18
sorenKeybuk: I tried adding a "udevadm settle" in between the two, but it still happens every once in a while.11:18
sorenIt's rare, so I thought the "udevadm settle" fixed it, but it just happened again, so now I'm back to square 1.11:18
Keybuksoren: the mkfs will cause udev to run blkid itself, and rearrange symlinks11:18
Keybukwhich way do you run blkid?11:19
Keybukwith -p or without?11:19
Keybukif you run without, it's possible the cache is out of date11:19
sorenwithout.11:19
sorenRight.11:19
Keybukright, run with -p11:19
sorenHm. I thought that was frowned upon.11:19
Keybukyou shouldn't need the settle11:19
Keybuk-p is a physical probe of the block device11:19
sorenI thought the idea was that only udev would need to do that.11:19
sorenI understand.11:19
Keybukwithout means "whatever was in the cache"11:19
Keybukyeah11:19
Keybukbut you need to wait for udev to do that11:19
Keybukyou can steal the wait-for-root code out of initramfs-tools if you like11:20
Keybukthat has the logic to wait properly11:20
Keybukif you use that, you can just call blkid11:20
* soren looks at that11:21
sorenCan you explain why -p is needed? I thought that when mkfs let go of the device node, it would trigger an inotify event upon which udev would react, and that "udevadm settle" wouldn't return until udev was done processing this event (and thus, calling blkid -p and updating the blkid cache).11:22
sorenWhich part is mistaken?11:22
sorenKeybuk: ^11:24
Keybukthat "udevadm settle" knows what you meant to wait for11:26
sorenKeybuk: Could it be that my "udevadm settle" occurs before udev even sees the inotify event and thus does not think there are any unprocessed events?11:26
Keybukudevadm settle simply waits for udev to be idle11:26
Keybukevents could be still somewhere en-route to udev11:27
Keybukwhen we initially added the inotify stuff, it was true that udevd would force the inotify queue to be drained on settle11:27
Keybukon the assumption that any file close instantly resulted in the entry being added to the inotify queue11:27
Keybukbut inotify has been entirely rewritten since then (replaced in-kernel with fsnotify)11:28
Keybukso that may no longer be true11:28
Keybukit might be possible for there to be a gap between the mkfs call, and the inotify event being queued for udev to receive11:28
sorenRight, ok.11:29
Keybukit would be worth reading some kernel code to find out whether or not that's changed11:29
sorenKeybuk: You said "when we initially added the inotify stuff, it was true that udevd would force the inotify queue to be drained on settle"... Does it not attempt to drain this queue anymore? (Yes, I understand that the event might not be in the queue at all yet, this is just a side-question)11:30
Keybuksoren: udevd does, yes11:30
sorenOk.11:30
Keybuk*inotify*, in the kernel, has been completely rewritten11:31
Keybukso it's possible that the act of mkfs closing the device node does queuey things in the kernel11:31
Keybukthat no longer guarantees that udevd's inotify socket polls for reading *by the time close() returns*11:31
Keybukif that bit has gone async in the kernel, you'd have a race where after mkfs exits, udevd may not yet have received the inotify event for the block device11:31
soren*nod*11:32
Keybukthat'd be worth some investigation11:33
sorenKeybuk: udev still uses the inotify /interface/, right?11:39
Keybukyes11:40
sorenalright11:40
cjwatsonKeybuk: so yesterday I started converting console-setup to upstart in order to fix its interaction with plymouth, which is a little bit involved due to how it glues into the installer.  Am I duplicating work you've already done and should I stop? :-)11:42
cjwatson(I didn't get very far as it was at the end of the day - just wrote initial job sketches)11:42
ChipzzKeybuk: ugh, too much *notify's and fa*'s ;P11:44
Chipzzstarting to get really confusing :)11:44
Keybukcjwatson: no, you're doing work I felt was far too scary for me ;P11:44
KeybukI couldn't work out when we'd actually run console-setup11:44
Keybuksince plymouth is *always* running from startup through to power off11:44
KeybukI thought we might need to use ConsoleKit to run console-setup when switching away from X11:44
Chipzzinotify, dnotify, fanotify, fam...11:44
Chipzzwhich ones am I forgetting? :P11:44
Chipzzfsnotify11:45
KeybukChipzz: fam is not a kernel interface11:45
KeybukChipzz: and all those you mentioned are the same in-kernel code11:45
Keybukjust different user-space interfaces for the underlying fanotify code11:45
Keybukor is it fsnotify11:45
ChipzzKeybuk: I know, but all these technologies fall into the same "realm"11:45
KeybukChipzz: they're all the same technology from the kernel POV11:45
Chipzzjust different iterations :P11:45
Keybukthe difference between inotify, dnotify and fanotify is the difference between open(), creat() and socket()11:45
Keybukno, not even iterations11:46
Keybuk*the same code*11:46
cjwatsonKeybuk: I was thinking of running it 'on starting plymouth-splash'11:46
cjwatsonroughly11:46
Chipzzwasn't dnotify replaced by inotify?11:46
Chipzzs/replaced/obsoleted/11:46
sorenChipzz: Yes.11:47
KeybukChipzz: dnotify was implemented using inotify11:47
sorenChipzz: And then inotify was replaced by fsnotify.11:47
Keybukcjwatson: right, that's about the only point we can do it11:47
Keybukthe problem then is racing gdm11:47
Keybukyou could be doing console-setup and hold up plymouth --show-splash11:47
Keybukmeanwhile gdm starrs11:47
Keybukand starts X11:47
cjwatsonthis would suck less if the kernel sucked less11:48
cjwatsonit's ridiculous that we need an active text-mode console in order to set the console font11:48
Keybukagree11:49
Keybukit would suck less if upstart sucked less too11:49
cjwatsonusing consolekit would sort of work, but wouldn't be effective on server-type installations11:50
cjwatsonsince ttx filed the bug in question ... :-)11:50
cjwatson(well, one instance of it)11:50
Keybukwell, on server plymouth does exit at the end of rc211:50
Keybukso that's one obvious place to run console-setup11:50
cjwatsonyeah, true11:50
cjwatsonwe used to do that for usplash11:51
cjwatsoncould shove it in plymouth's stop script11:51
Keybukit's desktop that's tricky, because getting to a console is really only by C-A-F111:51
Keybukcjwatson: on stopping plymouth plz :p11:51
cjwatsonfair enough :)11:51
Keybukshoving other things into upstart scripts is not the upstart way ;)11:51
cjwatsonok, so I'm happy to make this my problem if I'm not stepping on your toes and you don't mind occasional requests for criticism11:52
Keybuksure11:52
KeybukI'm happy for it to be your problem11:52
Keybukgives me more time for plymouth itself to be my problem <g>11:52
cjwatsonmaybe I should just fix the damn kernel11:52
KeybukJim Leib tried that11:52
Keybukhe died11:52
* cjwatson is not Jim Lieb11:53
cjwatson:-)11:53
* ogra grins11:53
Keybukno, indeed; you're unlikely to have to learn ANSI C just to read the kernel source11:53
* sebner has faith in our mighty cjwatson :D12:01
cjwatsonwell, this is something that's defeated me in the past, so we'll see12:02
cjwatsonthe basic problem (AFAICR) is that vgacon stores the font only in video memory12:02
Keybukwe're not using vgacon anymore though, right?12:10
Keybukwe're always using fbcon12:10
cjwatsonKeybuk: for a kernel bug report, I'd want to cover all possibilities12:13
cjwatson*kernel patch12:13
cjwatsonKeybuk: and that's the basic reason why there's a != KD_TEXT guard in console-impl-independent code12:14
Keybukyeah, I recall12:14
Keybukdidn't we find a different ioctl() that didn't have that guard?12:14
Keybukmy memory on this is hazy12:14
Keybukthough that may be the fact I just downed 8 different tablets ... whee drugs :p12:15
=== MacSlow is now known as MacSlow|lunch
cjwatsonKeybuk: I don't remember that, though that's not to say it didn't happen - I'd rather fix it so it doesn't need the guard though :)12:40
Keybukright12:42
seb128"ubi-partman failed with exit code 141"12:57
seb128I guess it's not today I will manage to reinstall that mini12:57
seb128"Device /dev/sda1 not found is os-prober"12:58
seb128"Device /dev/sda1 not found is os-prober output"12:58
seb128rather12:58
seb128what component should be bugged about that?12:59
cjwatsondevice not found> irrelevant message12:59
cjwatsonbug on nubiquity12:59
cjwatson*ubiquity12:59
cjwatsonplease reproduce with debug-ubiquity on the kernel command line before filing the bug, and use ubuntu-bug from within the live session to file it13:00
seb128cjwatson, ok will do13:03
pitticjwatson: gnome-user-share does not have any uploaders in edit_acl at all; can you please fix this?13:14
lamontsome of the ppa buildds are undergoing a little maintenance atm.  Just fyi13:20
dholbachbryceh: could it be that your script went beserk on bug 520796? :)13:21
ubottuLaunchpad bug 520796 in x11proto-dri2 "Sync x11proto-dri2 2.2-1 (main) from Debian unstable (main)" [Undecided,Incomplete] https://launchpad.net/bugs/52079613:21
=== dholbach_ is now known as dholbach
uelapeppahi13:27
=== funkyfox is now known as balboa
balboahi13:31
balboai've tried to make an ubuntu lucid remix folowing this how-to :https://help.ubuntu.com/community/LiveCDCustomizationFromScratch but when i try to install it i get "AssertionError: Missing filesystem.size." from ubiquity13:34
seb128cjwatson, bug #52705713:35
ubottuLaunchpad bug 527057 in ubiquity "ubi-partman failed error on partitions change" [Undecided,New] https://launchpad.net/bugs/52705713:35
seb128seems similar to bug #52508113:35
ubottuLaunchpad bug 525081 in ubiquity "ubi-partman failed with exit code 141" [Undecided,Incomplete] https://launchpad.net/bugs/52508113:35
seb128"PartmanOptionError: partman/choose_partition should have finish (None) option"13:36
seb128cjwatson, I get the issue every time on the mini so let me know if you need any detail13:37
evbalboa: you need /casper/filesystem.size on your CD.13:40
balboaev: and how can i create it?13:41
evwell, if you haven't changed the squashfs at all, you can simply reuse the existing one.  If you have changed the squashfs, then:   printf $(du -sx --block-size=1 /path/to/the/mounted/squashfs | cut -f1) > filesystem.size13:42
balboaev: i made the iso from scratch so for "/path/to/the/mounted/squashfs" can i use the path of my chroot?13:45
ev(updating that wiki page now with this)13:45
evyes13:45
balboaev: thank you =) i'll try it13:46
evbalboa: sure thing13:46
evgood luck! :)13:46
pittiev: oh, nice! the keymap guesser is in ubiquity now13:49
balboaev: i get some errors from du : it can't read some directories13:50
evbalboa: stick a sudo in front of it13:50
evprintf $(sudo du...13:50
evpitti: yup :)13:50
cjwatsonpitti: gnome-user-share> done13:51
pitticjwatson: cheers13:51
pittichrisccoulson: ^ FYI13:51
chrisccoulsonpitti / cjwatson - thanks13:51
balboaev: i'm stupid -.- i've put sudo in front of printf13:51
chrisccoulsonpitti - is that part of the packageset i can upload?13:52
pittichrisccoulson: edit_acl says ubuntu-desktop, yes13:52
chrisccoulsoncool, thanks:)13:52
pittichrisccoulson: when will you apply for core-dev?13:53
chrisccoulsonpitti - soon hopefully13:53
* pitti holds up his fanboy cardboard sign13:53
chrisccoulsonheh :)13:54
=== MacSlow|lunch is now known as MacSlow
seb128chrisccoulson++13:58
ograKeybuk, i see "ureadahed-main terminated" messages on boot of armel live images, do i need to worry ? (i dont see that on installed systems, ureadahread seems to work fine there)14:00
ogra(do we actually use it in live images)14:01
Keybukogra: what exit code?14:01
=== bladernr|away is now known as bladernr_
ograi have to reboot for that, gimme a bit14:04
cjwatsonseb128: investigating14:05
seb128cjwatson, thanks14:05
ograKeybuk, it says status 414:05
ograwow, JamieBennett is a hero, the live image on armel boots really really fast !14:06
Keybukogra: that's ok, that's just ureadahead saying "I don't have anything to read for this mount point"14:06
ogra1:48 ... vs ~4min in karmic14:06
ograKeybuk, perfect, thanks14:07
cjwatsonseb128: ah.  bug occurs when there is a partition that partman doesn't know how to resize14:07
seb128cjwatson, it shouldn't need to resize anything in my case though?14:07
seb128cjwatson, I delete one partiton and use the space to create a new one + a swap14:08
cjwatsonseb128: sure, but it still scans14:08
seb128ok14:08
cjwatsonit's the cache-building bit that falls over14:08
seb128let me know if you want me to test a fix or something14:08
cjwatsonare you in a position to edit a file before ubiquity starts?14:08
seb128cjwatson, yes, I'm back to livecd desktop14:08
seb128I can edit and run ubiquity again14:09
cjwatsonseb128: you'd probably better restart in "try ubuntu" mode, I don't want to deal with possible wreckage in the live session14:09
seb128ok, doing that14:09
seb128it's an usb key so it's quick to boot ;-)14:09
cjwatsonseb128: could you apply http://paste.ubuntu.com/382990/ to /usr/lib/ubiquity/plugins/ubi-partman.py, please?14:10
zuljames_w: thanks for the samba branch14:11
james_wzul: it's a little out of date at the moment due to dpkg-dev weirdness, looking in to it right now14:12
seb128cjwatson, ok, trying that14:12
zuljames_w: cool14:12
seb128cjwatson, that seems to work, at least I can get to the next screen without error now14:18
seb128cjwatson, continuing the install, I will let you know how it works14:18
seb128bah14:19
seb128ubiquity segfault now14:19
seb128is apport running on the livecd?14:19
seb128pitti, ^14:20
pittiseb128: yes, it is14:20
cjwatsonsegfault?  it's python14:20
cjwatsoniz gtk bug?14:20
seb128cjwatson, http://paste.ubuntu.com/38299514:21
seb128cjwatson, iz glib bog? ;-)14:21
seb128I don't get a .crash though14:21
james_wzul: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=55848514:21
ubottuDebian bug 558485 in patch "patch creates backup files with 000 perms for newly created files" [Normal,Fixed]14:21
james_wzul: that's not fixed in hardy where it matters for this, so I will have to implement a workaround.14:22
cjwatsonseb128: committed the fix for 527057 anyway, thanks14:22
seb128cjwatson, thanks!14:22
zuljames_w: sounds good to me14:22
cjwatsonseb128: mm, a few people have reported that kind of thing, I'd tentatively put it down to image errors but if you're seeing it maybe you can figure out what's causing it?14:22
seb128cjwatson, I will try, shame that apport is not working14:22
seb128bah, it works if I kill -11 gedit14:23
Laneyis archive.u.c sick?14:26
james_wyes14:26
seb128cjwatson, any idea what process I should use gdb on?14:27
seb128cjwatson, ubiquity exit with code 037714:27
seb128I've gdb --args python /usr/bin/ubiquity14:27
cjwatsonthat'll miss privilege elevation14:28
seb128ok14:28
cjwatsonerr14:28
seb128let me start again14:28
seb128and sudo gdb -p it14:28
cjwatsonyou probably want:14:28
cjwatsonsudo -E devkit-disks --inhibit -- gdb --args /usr/bin/python /usr/lib/ubiquity/bin/ubiquity14:28
cjwatsonor something like that14:28
cjwatsonthough yes, attaching to the running process would probably be easier14:29
didrockscjwatson: thanks for the netbook seed fix :)14:29
cjwatsonno problem, hope it works ;-)14:29
=== al-maisan_ is now known as al-maisan
seb128cjwatson, http://paste.ubuntu.com/383006/ not really useful ...14:39
* seb128 tries valgrind14:40
cjwatsonpublic service announcement: please can everyone STOP trying to find an existing ubiquity bug report that describes their problem and attaching logs to it14:40
cjwatsonjust file new bugs14:40
cjwatsonsuggests that a main loop source got trashed?14:41
cjwatson          prepare = source->source_funcs->prepare;14:42
seb128could be yes14:42
geserbryceh: do you really need the xorg.log and the output from lspci for a bug about a insufficient dependency (bug 507618)?14:42
ubottuLaunchpad bug 507618 in xserver-xorg-video-ati "xserver-xorg-video-radeon has insufficient (even missing) dependency on libdrm-radeon1 " [Undecided,Incomplete] https://launchpad.net/bugs/50761814:42
cjwatsonseb128: do you think I should go ahead with a ubiquity upload for a3 anyway, to get rid of the partitioning bug, or do you think this is likely to need a change in ubiquity?14:43
seb128cjwatson, I've no real clue about this crasher atm, I would guess it's an ubiquity issue though since we didn't get similar bugs otherwise14:44
cjwatsonI don't understand how python code could cause a segfault unless the python binding libraries are broken14:45
seb128cjwatson, still I'm not sure the crash bug will be fixed quickly and since it doesn't happen to everybody I would fix the partioning issue to start14:45
cjwatsonubiquity used to have some python bindings of its own, but we got rid of those a while back14:45
seb128cjwatson, well you could be doing something wrong, like using gtk after exiting the mainloop14:46
cjwatsonok, I'll upload .27 then14:46
seb128cjwatson, pygtk tends to not handle always such cases in a pythonish way, ie raise exceptions14:46
seb128it rather crashes14:46
seb128same if you try using gtk without a display set14:47
cjwatsonhmm, I suppose that's possible14:47
cjwatsonwe do some funny things with the main loop14:47
cjwatsoncould I get a separate bug for this with debug logs?14:47
seb128cjwatson, yes, let me try to valgrind first :-)14:47
* cjwatson nods14:48
seb128$ unset DISPLAY; alacarte14:48
seb128Erreur de segmentation (core dumped)14:48
seb128just as an example of pygtk is not friendly with errors ;-)14:48
cjwatsonmain loop's a bit more likely, DISPLAY isn't going to get magically unset :-)14:49
seb128right14:49
seb128bah, installing valgrind on the livecd = fail14:49
seb128enospace14:49
cjwatsonmine more memory14:50
kirklandpitti: re: https://bugs.launchpad.net/bugs/503180, could you nudge that karmic-proposed eucalyptus to karmic-updates?  I have another SRU pending for upload to -proposed ;-)14:50
ubottuLaunchpad bug 503180 in eucalyptus "[SRU] eucalyptus-cloud doesn't reply to requests (eucalyptus doesn't work after reboot or services restart issues due to upstart networking behavior)" [High,Fix committed]14:50
cjwatsonor --no-install-recommends, it might not really need libc6-dbg too badly14:50
cjwatsonoh, that's a depends, ignore me14:50
pittikirkland: ah, it's just 7 days old today, fine; moving14:52
kirklandpitti: cheers, thanks ;-)  i've been keeping my eye on it ;-)14:52
=== maco2_ is now known as maco2
pittididrocks: ah, so you broke the armel netbook images ;)14:57
didrockspitti: me? sure? :-)14:58
pittididrocks: please don't seed language-support-${Languages} for anything else but -en14:58
pittilanguage-support-* is huge, and it also pulls in the entire openoffice.org including java14:58
pittiogra: ^ FYI14:58
didrockspitti: oh, so we need to add [!armel] to the language pack?14:59
didrocks(there was -en and -es before my change, FYI)14:59
ogradidrocks, oh, pleasse dont :)14:59
ograwe want the translations on armel as well14:59
pitti--- live2010-02-22 16:00:21 +000014:59
pitti+++ live2010-02-24 14:59:02 +000014:59
pitti- * language-support-${Languages}14:59
pittiogra, didrocks: r1448 in netbook.lucid seed15:00
ogradidrocks, the prob is that -support pulls in *everything*, you only want the stuff thats actually needed on a live image for space reasons15:00
didrockspitti: ogra: but it was there before (see in r1441.1.3), only with -es15:01
ogradidrocks, there should be -en but no other langs15:01
didrockspitti: ogra: I just add aditionnal language, is there an exception of -es so?15:01
pittididrocks: no, l-support-es shouldn't be there either15:02
ograno, -en is the only language we fully install15:02
pittibut -es doesn't have a hyphenation package15:02
pittididrocks: language-pack-* is okay; language-support-* is a no-go for shipping15:02
seb128cjwatson, while looking around I found an another issue, you call devkit-disks in ubiquity15:03
seb128cjwatson, there is no such command now, it's "udisk"15:03
didrockspitti: so, it was an error on the previous version of the seed, right? The issue was just not triggered because -es has no hypenation package?15:04
seb128cjwatson, do you want a bug about that? or just fix it now?15:04
pittiargh, sorry about that15:04
pittiit's "udisks", not "udisk"15:04
seb128ups15:04
pittiI checked through the reverse depends, but since it's not a dependency that slipped my attention15:04
cjwatsonseb128: ah, I can fix that now, no need for a bug15:04
seb128cjwatson, thanks15:05
seb128cjwatson, it's udisks (plurial as pitti pointed before)15:05
seb128I guess you will get it right but just pointing in case ;-)15:05
pitticjwatson: it's a pure rename of the command, CLI syntax stayed the same15:06
cjwatsonyep - committed15:08
=== gnomefreak76 is now known as gnomefreak
imranhello15:27
rbrunhuberhi, is there a list of feature freeze exceptions for lucid and more important does it contain php5.3?15:45
zulrbrunhuber: im in the process of doing it15:54
rbrunhuberzul : The list or the ffe for php5.3?15:55
zulrbrunhuber: working on the ffe for php5.315:55
rbrunhuberzul: How likely do you think is it that the ffe is getting approved?15:59
zulrbrunhuber: no idea16:00
qensePython 2.5 was removed from Lucid?16:01
nigelbqense: yes16:02
qensenigelb: ok, thanks16:02
rbrunhuberzul : Is there anything I can do to help you with the ffe?16:04
zulrbrunhuber: nope you just have to be patient16:04
rbrunhuberzul : Ok, thanks.16:04
didrocksjono: around? I heard you plan to do a new lernid release today? (so that I can push it into universe)16:15
jibelmvo, hi, I pushed a fix for the xapian search in synaptic. Could you please review it when you have a minute ?16:16
jibelmvo, it fixes relevancy of the results, large performance improvement and add boolean operators.16:18
mvojibel: yes, I merged it locally already, looks fine, but I did not have time for a proper review16:18
mvojibel: the relevance set is now gone, right? I'm not sure of how much practial value it really is/was, but it was meant to improve things when debtags is around16:19
jibelmvo, it's still there but user configurable.16:20
cjwatsonRiddell: did you mean to close bug 526534 in your ubiquity upload?  you used a syntax in the changelog that does not close the bug16:20
ubottuLaunchpad bug 526534 in ubiquity "kubuntu ubiquity crashes after first page" [Undecided,New] https://launchpad.net/bugs/52653416:20
jibelmvo, I mainly dropped the expansion stuff since it's done by xapian.16:21
Riddellcjwatson: no, hiding the progress bar is a workaround, I'd like to find the cause after the alpha16:21
mvojibel: aha, ok. I need to have a proper look :) thanks a lot for working on it16:21
jibelmvo,  and limit the resultset based on the estimate returned by the search engine.16:21
cjwatsonRiddell: ok.  and should bug 526456 still be alpha-3?16:22
ubottuLaunchpad bug 526456 in ubiquity "shutdown does not work" [Undecided,New] https://launchpad.net/bugs/52645616:22
cjwatsonRiddell: I'll move 526534 to beta-1, then16:23
Riddell526456 can be moved to beta-1 as well16:24
cjwatsonok16:24
cjwatsondone16:25
jonodidrocks, hey, on a call, but yep, planning on a release :)16:26
jonodidrocks, will ping you in a bit16:26
mbuddejono: I'd like a have a talk with you too :)16:26
didrocksjono: cool :)16:26
jonombudde, yeah, sorry for the delay on Lernid - I was traveling last week16:26
jonombudde, I think just a little more visibility on the tweet button and we are good to go16:27
didrocksmbudde: do you have a FFe under the hand? do you need some help? :)16:27
mbuddedidrocks: sorry, haven't started on it yet.16:28
pittiseb128: is bug 527098  what you got as well?16:31
ubottuLaunchpad bug 527098 in ubiquity "ubiquity crash segfault error 4 in libglib-2.0.so.0.2304.0" [Undecided,New] https://launchpad.net/bugs/52709816:31
pitti(just spotted from the iso tracker)16:31
seb128pitti, yes16:32
pittiseb128: is that a dupe then? or did you just debug it on IRC?16:32
seb128pitti, I didn't open the bug yet, I've been fighting to get details but the bt is useless16:33
seb128and valgrind doesn't work16:33
seb128I can't go pass the partitionning stage when running valgrind16:33
pittiok, fine; well, then that is "the" bug report16:33
seb128pitti, not quite, I will open one with ubuntu-bug debug infos16:34
cjwatsonwell, "a" bug report16:34
cjwatsonone with ubuntu-bug will likely be a bit more useful :)16:34
seb128I'm just redoing my key and upgrading to .2716:34
pittiabsolutely16:34
seb128I did too many hacking changes to get valgrind running16:34
pittiseb128: good luck!16:34
seb128like unpack in tmp and ln in usr16:34
loolcjwatson: endianess issue > not sure, the initrd was built on real hardware (buildd) and the kernel as well, so I'm not sure why these would suddenly be wrong; did you have a particular explanation in mind?16:35
cjwatsonjust a vague memory that cpio endianness is funny16:35
cjwatsonI've written assembler code to byte-swap it16:35
cjwatsonI thought the kernel dealt with that though16:35
=== Guest5903 is now known as NCommander
james_w"Unable to read [...] FileExists (2: No such file or directory)" <- nicely done16:47
Keybukpitti: did you do any investigation into this rsyslog bug?16:57
pittiKeybuk: I sketched what the daemon would need to do, but no C implementation16:58
Keybukpitti: but it does that already16:58
pittii. e. seteuid(rsyslog), read()16:58
Keybukit has this whole klogWillRun() thing16:58
pittiEPERM -> seteuid(0), keep it16:58
pittiworks -> setuid(rsyslog) to drop permanently16:58
Keybukso if it gets EPERM, it should just disable klog16:58
Keybuknot spin16:58
pittiI didn't look at that16:59
cjwatsonwhen it happened to me, rsyslog itself didn't seem to be spinning, but the entire rest of the system slowed to a crawl, load average went through the roof, and I had to reboot17:01
cjwatsonI can't prove it was rsyslog, but it was right after the rsyslog package was upgraded17:01
cjwatsonI wasn't really in a position to debug it accurately, but I speculated that everything else was getting stuck on full buffers or something17:01
Keybukbut this is only klog, the thing that picks up dmesg17:02
* ogra thought that was a missing kernel feature or was that a different bug ?17:02
ograi definately saw rsyslogd eating 100% CPU when it hit me on armel17:02
pittiogra: it's fixed in current lucid kernel and in linux trunk17:02
seb128today is ubiquity bug day17:03
pittibut not during upgrade, etc.17:03
ograpitti, right and in the imx51 .31 kernel17:03
ograwhere we only saw it last week17:03
pittiKeybuk: isn't it all just one process in rsyslog?17:03
Keybukpitti: no, rsyslog seems very modulised17:03
pittiI only have a single rsyslogd -c4 process here17:04
pittiwhich has fds to /proc/kmsg as well as /var/log/*.log17:04
Keybuksure, but internally it's doing everything through a linked list of structs, etc.17:04
Keybukif it can't open the klog thing, afaict, it will be just missing that module17:05
Keybukwhich is odd for "CONSUMES 100% CPU ARGH!"17:05
Keybuk:p17:05
pittiKeybuk: it can certainly open it17:05
Keybukoh, the open() doesn't fail, the read() does?17:05
pittiKeybuk: rsyslogd starts as root, opens files, keeps fds, and then drops prifs17:05
pittiprivs, even17:05
pittiand then read() fails with EPERM17:05
pitti(see bug description)17:05
Keybukpitti: not entirely sure that's true17:05
KeybukrunInputModules() happens *after* the de-rooting17:05
Keybukpitti: the bug description isn't very helpful17:06
pittibut if it would drop privs before opening /proc/kmsg it wouldn't work on current lucid at all17:06
KeybukFeb 18 05:04:22 ubuntu kernel: last message repeated 1327321 times17:06
Keybukis about as much detail as it gives :p17:06
Keybukpitti: I don't follow?17:07
Keybukah, no, I see17:07
Keybukthe fact this works is an accidental side-effect of testing to see whether it works :p17:07
* Keybuk is guessing deroot.patch is yours?17:07
pittiKeybuk: right now it seems to open() as root and read() as rsyslog17:07
pittiKeybuk: no, I never touched rsyslog17:08
Keybukhmm, the deroot.patch is ubuntu-specific17:08
* pitti rtfs17:08
Keybukah, it's mterry's17:08
Keybukpitti: yeah that'd fit17:08
Keybukcurrent lucid - you need to open as root?17:08
pittiright17:08
pitti-r-------- 1 root root 0 2010-02-24 07:42 /proc/kmsg17:09
* seb128 files bug #527199 now17:09
ubottuLaunchpad bug 527199 in ubiquity "ubiquity returned an error after the langpacks installation" [Undecided,New] https://launchpad.net/bugs/52719917:09
pittiKeybuk: in previuos kernels, the bug was that not only the open(), but also the read() needed root privs17:09
pittiKeybuk: which is why we needed that dd process to shovel it to a fifo17:09
Keybukok17:09
Keybukso I don't see at all what you thought might work17:09
pittinow it behaves as usual, open() obeys file perms, and read() just needs an fd, without checking capabilities17:09
pittiKeybuk: so on an older kernel, read() will -EPERM17:10
Keybukok17:10
pittiso one possibility would be to just stop the klog module on that17:10
Keybukyeah, that seems the only possibility here17:10
pittithe other would be to temporarily drop privs with seteuid(rsyslog), do the first read() (or peek()), check for -EPERM, and then re-raise or permanently drop privs17:10
Keybukthere is no peek()17:11
pittiwhich would work on older kernels as well17:11
Keybukthat read() could cause rsyslog to block forever17:11
pittibut is more tricky to implement17:11
Keybukif there was no kernel log pending, or the level was set high, then the read() would forever block waiting for data17:11
pittiKeybuk: right, it'd require some fcntl with O_NONBLOCK, etc.17:11
Keybukif you read non-blocking, it'd return EAGAIN not EPERM17:11
pittithat's where the "more tricky to implement" bit comes in :)17:11
Keybukthen suddenly when there was data, EPERM and go back to 100% CPU17:11
pittiKeybuk: "EAGAIN not EPERM" > are you sure?17:12
Keybukpitti: yes17:12
Keybukreasonably17:12
pittithe kernel capability check was pretty early17:12
Keybukit's certainly *permitted* to return EAGAIN without a cap check17:12
Keybukand we wouldn't want to rely on kernel behaviour here17:12
pittiKeybuk: and in the python snippet on bug 515623  I had read() block as well (when running as root)17:13
ubottuLaunchpad bug 515623 in linux-fsl-imx51 "Do not require CAP_SYS_ADMIN for reading from /proc/kmsg" [Medium,Fix released] https://launchpad.net/bugs/51562317:13
pittibut immediately -EPERMing as non-root17:13
pittiit didn't block17:13
pittiKeybuk: but even if it does, certainly rsyslog currently has blocking calls as well?17:13
pittithe blocking shouldn't really matter17:13
pittiit just needs a little state machine to remember whether it's the first read17:13
KeybukI don't think we can unload modules looking at this17:14
Keybukonce the module is loaded, it looks like it's impossible to unload it17:14
Keybuktoo many unprotected linked lists17:14
Keybukit'd turn 100% CPU into SIGSEGV17:14
pittiok, let's not do that then17:14
KeybukI wonder what read(0) would do here17:15
Keybuk>>> import os17:16
Keybuk>>> fd = os.open("/proc/kmsg", os.O_RDONLY)17:16
Keybuk>>> os.read(fd, 0)17:16
Keybuk''17:16
Keybuk>>> os.seteuid(1000)17:16
Keybuk>>> os.read(fd, 0)17:16
KeybukTraceback (most recent call last):17:16
Keybuk  File "<stdin>", line 1, in <module>17:17
KeybukOSError: [Errno 1] Operation not permitted17:17
Keybuk--17:17
Keybukthat seems to work17:17
Keybukwhereas17:17
Keybuk>>> os.seteuid(0)17:17
Keybuk>>> os.read(fd, 0)17:17
Keybuk''17:17
Keybuk>>> os.read(fd, 1)17:17
Keybuk(still blocking)17:17
pitti"If  count is zero, read() returns zero and has no other results. "17:17
pittibut if it -EPERMs, that's great17:17
Keybuksure, but it should at least go through the cap check ;)17:17
pittimakes it much easier to imiplement17:17
pittibah, tpying is hrad17:18
Keybukok, so that's the trick then17:18
Keybukdo a zero-byte read after opening17:18
Keybukif we get EPERM, then decline17:18
pittis/decline/not drop privs/?17:18
Keybukno, don't think we can do that17:19
Keybukdrop privs is WWWWAAAYYY above this code17:19
Keybukjust decline to do kernel logging17:19
Keybukthis is inside an alternate backend code, inside a module, inside a configurable part of the build tree, etc.17:19
Keybukand for the upgrade case, rsyslog has already dropped privs, it can't undecide ;)17:20
pittifair enough17:20
pittiKeybuk: no, we restart rsyslogd on upgrade (that's where the problem comes from in the first place)17:21
Keybukah ok17:21
pittiKeybuk: we could _not_ restart rsyslogd on upgrades with an older kernel running17:21
pittiif we want to retain kern.log for upgrade bug reports, or anythign like that17:21
Keybukthe point still stands though that it's already decided whether or not to drop privs before it loads modules17:21
Keybukextending the rsyslog module interface just to let modules say "hey, I can't!" seems like a massive patch17:22
pittiright, which makes it hard to work with older kernels17:22
Keybukadding a read(0) to the "will the klog module work" function seems much easier17:22
pittiso let's not do that17:22
pittithat> turn the implementation upside down, I mean17:22
pittiKeybuk: oh, it just occurs to me that most apport bugs use dmesg anyway instead of attachign kern.log17:23
pittiso that should be fine17:23
Keybukyeah, I just don't see a way of doing what you suggest17:24
Keybukrsyslog just isn't engineered that way17:24
pittiKeybuk: at the time when it opens /proc/kmsg, can it reach its option dictionary? it coudl do the read() test there, and unset the "drop privileges" option?17:27
pittibut oh well, not having klog when running older kernels doesn't seem like a big issue17:28
Keybukpitti: no, it can't17:29
cjohnstonmbudde: ping17:29
mbuddecjohnston: pong17:29
Keybuk/proc/kmsg is opened in the "is this module supported on this system?" function17:29
Keybukit doesn't have config or anything yet17:29
Keybukmodules only get that in other functions fwictr17:29
Keybukbut again, it doesn't change the fact that main() is already in a different if() statement because it's decided to be de-rooted17:30
cjohnstonHey dude.. We had a couple ideas for Lernid if you have a few.. based on some things with ClassBot17:30
mathiazcjohnston: hi - does grub2 support booting from devices part of a raid1 array?17:30
cjohnstonI dunno17:30
mathiazcjwatson: hi - does grub2 support booting from devices part of a raid1 array?17:30
mathiazcjohnston: sorry - wrong nickname17:30
cjohnstonI figured.. ;-)17:30
cjwatsonmathiaz: in general I think so, but there are some known bugs, like it doesn't support the latest mdadm metadata format17:31
mathiazcjwatson: hm - would this be the reason why grub-install would fail?17:32
mathiazcjwatson: http://paste.ubuntu.com/383141/17:32
cjwatsonerr buggadifino17:32
cjwatsongrub-install --debug might be a bit more informative17:33
cjwatsonactually, that's weird17:35
cjwatsonI think you should just install to /dev/md017:35
mathiazcjwatson: that's from d-i17:35
cjwatsondid something pick /dev/vda /dev/vdb /dev/vdc for you, or did you enter that yourself?17:35
mathiazcjwatson: let me pull up the preseed17:35
Keybukpitti: http://people.canonical.com/~scott/deroot.patchpatch17:37
mathiazcjwatson: http://people.canonical.com/~mathiaz/raid5.preseed17:37
Keybukpitti: does that smell/look right to you?17:37
cjwatsonmathiaz: ok, bug on grub-installer I guess, then17:38
cjwatsonall a bit odd, no idea where it gets /dev/vd[a-c] from there17:40
cjwatsona syslog with DEBCONF_DEBUG=developer might help17:40
mathiazcjwatson: ok - I'll retry an installation17:41
mathiazcjwatson: DEBCONF_DEBUG=developer should be set on the command line?17:41
mathiazcjwatson: the *kernel* command line?17:41
cjwatsonyes17:41
mathiazcjwatson: ok - I'll respun an install a file a bug against grub-installer17:42
Keybukpitti: actually, that won't work :-/17:44
brycehgeser, I use scripts to work on bugs in LP.  The scripts parse and use info from the .log and lspci.  So you don't have to provide that info, but it makes it less likely your bug will get attention.17:44
cjwatsonmathiaz: thanks!17:45
Keybukpitti: I guess seteuid(<arbitrary number>) would upset you?17:46
pittiKeybuk: re17:54
Keybukpitti: so there's no way for the klog module to know the uid that syslogd is going to use17:54
pittiKeybuk: it shouldn't matter which uid it is, though17:55
Keybukright17:55
pitti"nobody" (65534) shoudl be fine17:55
Keybukso is there any random uid I can use that won't upset you? :p17:55
Keybukok17:55
seb128re17:55
pittiread() shouldn't check user at all17:55
* seb128 shakes fist at plymouth which got installed back17:55
pittiKeybuk: so the patchpatch code runs under setuid()? or as root?17:55
Keybukpitti: as root17:55
seb128and keeps crashing my box on user switch17:55
pittiKeybuk: ah, then wrapping into seteuid(65534)/read()/seteuid(0) ought to work17:56
pittiKeybuk: 1 is a static uid "daemon", that also seems appropriate17:56
* pitti checks LSB17:56
seb128slangasek, Keybuk: I still get the "user switching lead to a cursor over a text vt taking over my xorg"17:57
Keybukpitti: updated patch17:57
seb128slangasek, Keybuk: if you need debug infos or something feel free to ping me17:58
* seb128 uninstall plymouth17:58
pittiKeybuk: right, "daemon" is required, but it doesn't prescribe uid 1; but it shouldn't matter17:58
Keybukyeah, will just use 6553417:58
pittiKeybuk: looks okay to me (why don't you just use saved_errno in the LogIntMsg()?)17:59
Keybukpitti: in case there are other reasons it gets used later I guess17:59
Keybuklike what that ksyslog() call does17:59
pittiah, it's not a libc function, I see17:59
pittilooks fine to me; many thanks!17:59
Keybukright18:04
Keybuknow to make quilt update the patch18:04
Keybukquit --please --please --please --ill --do --whatever --you --ask --just --do --what --i --want18:04
pittiquilt push foo.patch18:04
pittipatch < patchpatch18:05
pittiquilt refresh18:05
pittiquilt pop -a18:05
pittishoudl work18:05
pittiKeybuk: oh, please don't call "quit"! we still need you!18:05
Keybukpitti: doesn't want to work18:06
Keybukquilt refresh didn't do anything18:06
Laneyquilt import?18:06
slangasekseb128: I'm in a holding pattern on plymouth; Keybuk tells me much of this should be getting fixed upstream18:06
Laneyor quilt push blah; quilt shell; hack; exit; quilt refresh18:06
pitti"quilt shell"? that's news to me18:06
KeybukLaney: so, the state I am currently in:18:07
KeybukI have applied the quilt patches18:07
slangasekseb128: that particular bug may fall out from some of the other fixes for the boot-time problems everyone is seeing, so I'm not going to dig into it right now18:07
KeybukI have modified the working tree18:07
pittiKeybuk: did "quilt push foo.patch" work?18:07
Keybuknow how do I get the working tree changes *back into the patch* ?18:07
Laneyyou have to quilt add the files you changed18:07
Laneythen quilt refresh18:07
pitti"quilt refresh" ought to do that18:07
Laney(I think)18:07
pittiLaney: its' not adding new files18:07
Keybukpitti: No patches in series18:07
slangasekLaney: if you've already modified them, it's too late to do a 'quilt add'18:07
Laneyoh...18:07
Keybukquest rsyslog-4.2.0% quilt refresh18:07
KeybukPatch deroot.patch is unchanged18:07
seb128slangasek, ok, fair enough18:07
KeybukFWIW, I did the "quilt add" in advance18:08
Keybukit said18:08
Keybukquest rsyslog-4.2.0% quilt add plugins/imklog/linux.c18:08
KeybukFile plugins/imklog/linux.c is already in patch deroot.patch18:08
pittiright, if you change an already patched file, you don't need to add it again18:08
pittiit's differently complicated than git :)18:08
* ogra is happy to see that even Keybuk struggles with that user-unfriendlyness 18:08
Laneyuse quilt edit or quilt shell to be safe18:08
ograi get beaten up all the time if i complain about it18:08
Laneyit's knobbly and annoying18:09
cjwatsonI don't beat people up for complaining about it - I just find all the alternatives worse in different ways :)18:09
pittiwhat is really (un)funny is to generate 99autoreconf with quilt18:09
seb128or not so18:09
Laneypitti: that's where you want quilt shell18:09
ogracjwatson, so why dont we have quilt-edit-patch that does all the ugly stuff for me ?18:09
pittiindeed, I didn't know about quilt shell, that's handy18:09
Keybukso18:09
Keybukany ideas?18:09
pittiLaney: thanks18:09
cjwatsonnowadays what I do is to work in bzr (doing a temporary bzr init .; bzr add if necessary) and then punt necessary stuff into quilt afterwards18:09
cjwatsonogra: mvo has been working on an edit-patch wrapper18:10
Keybukstuff in working tree, patch on top18:10
Keybukhow do I make quilt update the patch?18:10
ogracjwatson, oh, you just made my day !18:10
pittiKeybuk: quilt push deroot.patch; quilt shell; patch < patchpatch; exit 0 <- perhaps?18:10
cjwatsonquilt shell does appear to be The Right Thing18:10
cjwatsonit's basically what people complain about not having18:10
slangasekKeybuk: if you did the 'quilt add', then 'quilt refresh' should DTRT; it's not?18:10
Keybukpitti: quilt push says "No patches in series"18:11
pittipush/refresh has usually worked for me as well, but perhaps there's some differnet assumption here which I'm not aware of18:11
pittiKeybuk: oh, hang on18:11
Keybukslangasek: quilt add says "File plugins/imklog/linux.c is already in patch deroot.patch"18:11
pittiKeybuk: export QUILT_PATCHES=debian/patches18:11
pittido you have that?18:11
cjwatsonlp:~mvo/+junk/edit-patch18:11
pittiit defaults to ./patches18:11
Keybukpitti: no?18:11
pittiI just set that in my .bashrc18:11
cjwatsonmay be worth using that - it includes all of the tips listed in this channel so far18:11
pittiKeybuk: check if it created a ./patches/deroot.patch; you might need to clean that up18:12
Keybukpitti: it didn't create that18:12
Keybukbut setting that makes it work18:12
cjwatsonhttp://paste.ubuntu.com/383162/ is the quilt bit of it18:12
Keybuk\o/18:12
cjwatsonor was, he's updated it a little since I last looked18:12
pittiKeybuk: I have that in my .bashrc, since I only ever use it for debian/patches; everything upstreamish is bzr/git anyway18:13
cjwatsonI picked up http://paste.ubuntu.com/383163/ in ~/.quiltrc from somewhere, and it generally DTRT18:13
slangasek"from somewhere" - that's in /usr/share/doc/quilt/README.source18:14
slangasek(which is hardly an obvious place for it)18:14
cjwatsonseems plausible18:14
Keybukcjwatson: ooh, handy thanks18:14
cjwatsonfor true horror, try slang218:15
Keybukslangasek: do you want this in the queue/archive?18:15
cjwatsondpkg-source v3 *and* dbs18:15
slangasekKeybuk: "this"?18:15
pittiboggle18:15
Keybukslangasek: rsyslog18:15
pitticjwatson: tar-in-tar?18:15
cjwatsonyep18:16
Keybuk"I can put it anywhere"18:16
slangasekKeybuk: sorry, my current context was truncated somewhere in the midst of quilt discussions :-)  yes, please upload rsyslog to the archive18:16
Keybukcjwatson: YADA18:16
cjwatsonand the change was together with a new upstream release, so there isn't even the excuse of not wanting to rev the .orig.tar.gz18:16
slangasekheh18:16
slangasekKeybuk: yada.m418:19
seb128slangasek, can I upload a libgnome-keyring fix?18:20
seb128slangasek, http://git.gnome.org/browse/libgnome-keyring/commit/?id=5e37e8cc09712fd8cab60e42636f260f23bacd7e18:20
Keybukrsyslog is a bit crazy18:20
seb128slangasek, basically right now gnome-keyring doesn't ask the "do you want to create a keyring" if there is none18:20
Keybukit's like someone looked at syslogd and thought "what this *really* needs is a plugin architecture"18:21
seb128slangasek, which makes desktopcouch crash because it can't use gnome-keyring18:21
seb128slangasek, and probably cause some other issues on new installs18:21
ograseb128, oh, wait18:23
slangasekseb128: you can upload, but I'm not thinking this should be cause for a respin18:23
seb128ogra: it's in libgnome-keyring, not gnome-keyring, ie not what ftbfs for you18:23
ograbug 527179 should have a gnome-keyring debdiff too18:23
ubottuLaunchpad bug 527179 in gnome-keyring "FTBFS fix for armel" [Undecided,New] https://launchpad.net/bugs/52717918:23
slangasekseb128: once the user upgrades libgnome-keyring after install, they should get correct behavior, yes?18:23
seb128slangasek, yes18:23
ograseb128, hmm, i thought they FTBFS both18:24
seb128slangasek, I don't think it's worth an alpha respin18:24
slangasekseb128: yep - so we should push to the archive but not respin18:24
seb128ogra: I will look at this too18:24
ograseb128, thanks18:24
seb128slangasek, thanks, I was just checking if upload was ok or would create issues with current respins18:24
seb128ogra: np18:24
ogra:)18:24
slangasekogra: why hasn't anyone from your team uploaded the gnome-keyring change before now, when the fix has been known for > 24h?18:26
ograslangasek, look when the bug was filed, NCommander has connection issues after he wrote the fix18:26
ogra*had18:26
ccheneymvo: ping18:27
ccheneymvo: are echo's from install scripts somehow supressed in the DpkgTerminalLog.txt?18:28
slangasekogra: bug, yes; but the fix was discussed in #ubuntu-release 24h ago as I said, it's not clear to me why this should have waited for NCommander to file a bug report again18:29
ograslangasek, he said he would provide me a debdiff so i was waiting ... then he vanished from the sufrface of the earth until some hours ago, because i didnt expect that we still could upload and pitti was in the last rounds of respins already i asked him to file the bug so the fix doesnt get lost18:30
mvoccheney: they shouldn't be - do you have a example where it does not work?18:31
ograslacker_nl, i'll do the upload after the freeze unless seb128 has picked it up by then18:31
ograerr18:31
ograslangasek, ^^18:31
slangasektseliot: linking bug #526892 to foundations-lucid-boot-experience in place of the corresponding whiteboard item, as long as people are filing bugs we might as well use them :)18:31
ccheneymvo: i'm not sure if it is working for openoffice.org-emailmerge.preinst18:31
ubottuLaunchpad bug 526892 in plymouth "Plymouth uses fallback blue ASCII progress bar; no splash" [Medium,Triaged] https://launchpad.net/bugs/52689218:31
ccheneymvo: i am still getting weird errors from users like http://launchpadlibrarian.net/39732587/DpkgTerminalLog.txt18:32
mvoccheney: ok, let me have a look18:32
mvoccheney: what is the bug accociated with it?18:33
ccheneybug 52716818:33
mvoccheney: hm, emailmerge - that rings another bell (a history of maintainer script problems :(18:33
ubottuLaunchpad bug 527168 in openoffice.org "package openoffice.org-emailmerge 1:3.1.1-5ubuntu1 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 (dup-of: 450569)" [Undecided,New] https://launchpad.net/bugs/52716818:33
ubottuLaunchpad bug 450569 in update-manager "package openoffice.org-emailmerge 1:3.0.1-9ubuntu3.1 failed to install/upgrade: " [Undecided,Confirmed] https://launchpad.net/bugs/45056918:33
tseliotslangasek: right ;)18:33
ccheneymvo: yea i backported the current preinst fixes and it still does the same type error18:34
slangasekogra: ubiquity was a 2h17 build, gnome-keyring is ~30min; had this been uploaded in parallel at any point, you would have the up-to-date gnome-keyring on the next ISO. <shrug>18:35
ograwell ...18:35
mvoccheney: from looking at the current preinst exit 1 is also done after the debconf prompt, no prompting then (in current lucid)18:35
mvoccheney: you will see nothing in the terminal when users use gnome debconf (the default in u-m)18:35
ccheneyubuntu-mobile?18:36
mvoccheney: update-manager, sorry18:36
ccheneyoh ok :)18:36
ccheneyso we do display debconf messages?18:36
mvoccheney: is there a way to make OOo exit (and save work)? then you could make the default debconf action to send graceful-kill18:37
mvoccheney: yes, via the gnome frontend by default18:37
ccheneyoh ok18:37
mvounless people upgrade explicitely with non-interactive18:37
mvo(which is not default and not something we encourage)18:37
ccheneyyea in non-interactive case it should be logging though, so i think they are just ignoring the message and filing a bug :-\18:38
mvosomething like "You are running OOo, we can close it for you"18:38
mvoright18:38
mvothe default action should therefore (if that is possible) to kill OOo and make it write a recover file. and if people do not like it they can select a different debconf option18:38
ccheneymvo: not sure if there is a way to cause it to shutdown18:38
mvo(and complain)18:38
mvokill -9 :P18:38
mvo(not really)18:38
ccheneywell if we kill it leaves the lockfile which i think it might be using to do the recover bit18:39
mvoyou could of course simply add a "echo user closed, but OOo still running" and create a bug pattern that auto-closes these reports18:40
ccheneyyea18:40
ccheneyi think i will add that18:41
mvoI personally think the default for any debconf question during a upgrade should be "continue in some sensible way"18:41
mvoand not "fail"18:41
mvobut I know that its not always possible (especially for server packages)18:41
jmlis there a schedule for lucid+1 somewhere?18:41
ccheneyyea :-\18:41
jmlwe're looking at shifting Twisted to releasing every three months and we want to be in sync w/ Ubuntu18:41
jml(we missed the feature freeze for lucid, unfortunately)18:42
ccheneyjml: well the release date is very likely to be Oct 28, but it doesn't seem to have a release schedule yet18:42
jmlccheney, feature freeze is what I care about the most, I guess.18:45
jmlccheney, maybe I can make a guess based on karmic's schedule18:45
ccheneyjml: yea probably will be about the same as jaunty/karmic18:45
ccheneyhmm did the wiki go down?18:47
ccheneymy ff is just sitting waiting for response18:47
ccheneyworking now, hmm18:48
ccheneyjml: guesstimate would be final freeze on aug 2618:49
jmlccheney, ok, thanks.18:51
tkamppeterpitti, hi18:52
=== yofel_ is now known as yofel
mpt_asac, are you able to answer Joanmarie's question in <http://launchpad.net/bugs/433104>: "what is the cut-off point for Ubuntu including a newer release of WebKitGtk?"19:01
ubottuLaunchpad bug 433104 in software-center "Ubuntu Software Center "Get Software" screen contents not read in Orca" [High,Incomplete]19:01
=== nick_ is now known as Guest35451
asacmpt_: the cut off point was FF ... everything on top needs careful review and approval19:19
asacis there anything upstream yet for that?19:20
asacanswered in bug19:21
mpt_asac, ok, thanks for the answer19:23
asacnp19:23
alex-weejis there some reason rpm/alien is now a dependency of my karmic install? or is it some dodgy package upgrade i have?19:24
slangasekalex-weej: rpm is a dependency of lsb-core, so if you have any of the lsb support installed that would do it19:26
alex-weejmy karmic install is many months old -- why is it being brought in now?19:26
slangasekdunno, would have to see an upgrade log to tell you19:27
=== mpt_ is now known as mpt
mptasac, incidentally, it's kind of weird that <https://launchpad.net/webkit> (a) talks about WebKit being an "attempt" and (b) has, as its latest download, a Firefox variant19:29
asacmpt: i am hopefully not the owner of the webkit launchpad project ;) ... am i?19:31
mptasac, true, but it also shows up on https://launchpad.net/ubuntu/+source/webkit19:33
cjwatsonjml: yes, add a year to karmic's schedule and you'll be within a week or two of m's19:39
alex-weejquestion: i'm very interested in doing some system testing, especially regression testing between releases. is there a formal team that i can join?19:44
alex-weejideally i want to make sure a wide range of macs are included in testing19:44
alex-weejas many of my friends are quite upset with regressions etc.19:45
ionDunno if this idea is insane, but anyhoo, bug #527292. :-)19:46
ubottuLaunchpad bug 527292 in ubuntu-meta "Recommend lsb-invalid-mta to satisfy other packages’ MTA recommendation by default" [Undecided,New] https://launchpad.net/bugs/52729219:46
jcoleis it possible to have the "guest" session start in an xnest by default?20:18
slangasekalex-weej: I think that's in scope for https://wiki.ubuntu.com/Testing20:19
alex-weejis there an official set of test hardware that canonical uses btw?20:19
slangasekion: I'm kinda leaning toward 'insane', yes; sendmail is specified in the LSB with the expectation that *it can be used to send mail*, if it should be made optional then that should be done in the LSB instead of bodging it in the distro20:20
* jcole pokes at files in gdm-guest-session20:22
ionslangasek: True. But on that basis, shouldn’t the package itself have never been added to Ubuntu in the first place?20:23
slangasekion: ugh, that's an Ubuntu-specific add-on?20:24
slangasekpitti: you seem to have sponsored this; why do you think this is reasonable?20:25
ionslangasek: It seems to be, judging from the package’s changelog.20:25
ionFWIW, i’m happy a package like it appeared in Ubuntu. Things no longer want me to install a MTA to my desktop boxes. :-P20:26
slangasekion: install ssmtp instead of a full MTA?20:27
ionslangasek: It expects me to have constant access to a certain forwarder. Doesn’t really work for my laptop. I rather just have no sendmail or a have sendmail binary that just fails.20:30
slangasekpackages depend on an mta when they rely on being able to use /usr/sbin/sendmail to deliver messages to the system admin.  I care not one whit if that gets delivered to a local mailbox, or sent over SMTP, or delivered over *twitter* if that's what you want, but deliberately dropping them on the floor is wrong20:31
ionI didn’t mean packages that depend on an MTA, but packages that recommend one. I want my apt-listchanges just to show the changes, not mail them. I wouldn’t need mdadm’s email functionality on a hypothetical desktop box with RAID.20:34
lamalexDoes anyone know how to debug debootstrap/cowbuilder/pbuilder?20:45
lamalexit's dying with a very generic error20:45
lamalexhttp://paste2.org/p/68724120:46
jcolelamalex: are you running it with sudo20:50
lamalexjcole: no, but I don't need to when I do cowbuilder-dist <ubuntu release> create20:51
lamalexit works fine then20:51
lamalexbut I'm trying to set up cowbuilder to work off of a different distro20:52
gesercowbuilder-dist might call cowbuilder with sudo (check the source)20:56
geserand you need to "sudo cowbuilder" if you don't use "cowbuilder-dist"20:57
lamalexgeser: it does20:58
lamalexi should have said that,sorry :P20:58
lamalexi think the problem is an incomplete mirror20:58
qenseI'm working on giving Guake AppIndicator support and I would like to include something like C's preprocessors in the code to allow people to not use AppIndicator. Does anyone know how to do such a thing? The project is using a makefile and not something like python-distutils.22:19
=== micahg1 is now known as micahg
seb128qense, the code is python?22:21
qenseseb128: yes, so preprocessors won't do the trick22:21
seb128qense, well at runtime should work then22:22
seb128look at jockey22:22
seb128just try: the import22:22
seb128no?22:22
qenseseb128: thank you! I'll have a look at jockey.22:22
=== jelmer__ is now known as jelmer
=== jelmer is now known as Guest75587
=== Guest75587 is now known as ctrlsoft
CaesarWhat package provides the system status info in /etc/motd on Ubuntu Server?22:49
jpdsCaesar: update-motd?22:50
Caesarjpds: thanks22:50
ccheneyupdate-motd claims that libpam-modules does it now22:50
=== robbiew is now known as robbiew_
jcoleis there an irc room for the ubiquity ubuntu installer23:07
lifelesshere usually, I think23:07
stgraberjcole: ubuntu-installer23:07
jcoleperfect, thanks23:08
=== Kai___ is now known as Kai_

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