=== tkamppeter__ is now known as tkamppeter
ScottKRAOF: Which browser?01:04
RAOFScottK: Chromium is what's set up, and if it's running then the URL goes to the right place.01:05
ScottKOK.  I was curious since I haven't seen that.  I may just not have been looking.01:05
cjwatsonSarvatt,RAOF: hm, so if mesa no longer provides the mesa-utils binary package, what are things like gnome-shell supposed to do which use glxinfo?  there are a couple of other reverse dependencies listed in http://people.canonical.com/~ubuntu-archive/NBS/mesa-utils02:04
cjwatsonogasawara: could we have an upload of linux-meta-mvl-dove to match the 410 ABI?02:04
RAOFcjwatson: Yeah, I just got reminded about that with bug #648401.02:04
ubottuLaunchpad bug 648401 in mesa (Ubuntu Maverick) "mesa-utils still referenced by packages" [High,Confirmed] https://launchpad.net/bugs/64840102:04
cjwatsonRAOF: ah, doko beat me to it - thanks02:05
cjwatson(I don't agree with his "option for maverick-updates", though - the archive needs to be consistent for release)02:05
RAOFmesa-demos got split out of the main mesa source tree and put into a separate repository.  I knew about this a couple of months ago, and just plain forgot when the 7.9 FFe came through :/02:06
RAOFI'm not sure whether re-munging the mesa-demos tarball into our mesa tarball is the way to go, or whether to go with the separate packaging I've got lying around.02:07
cjwatsonI don't think it matters too much from the archive point of view (FWIW)02:08
RAOFIt's probably easier from a review standpoint to re-munge the tarballs.02:09
RAOFThat does seem a bit like cheating, though.02:09
cjwatsonRAOF: sounds like a pain to compare either way actually02:10
cjwatsonso go with what makes most sense to you02:10
RAOFSeparate packging it is, then.02:11
RAOFGood morning :)02:32
=== hunger is now known as Guest13487
TheMusoHey RAOF.02:38
RAOFHowdie TheMuso.  How's Sydney's springtime treating you?02:39
TheMusoRAOF: Not too bad, unseasonally warm unfortunately, but cooler weather is on its way, at least temporarily.02:40
* RAOF wouldn't mind just a *little* bit of unseasonable warmth :)02:41
RAOFIt's decided to be really really windy, instead.02:41
RAOFI'm not yet sure what sounds from the roof to be alarmed at, either.02:42
=== nigelbabu is now known as nigelb
=== almaisan-away is now known as al-maisan
=== fabbione_vac is now known as fabbione
=== al-maisan is now known as almaisan-away
=== almaisan-away is now known as al-maisan
=== al-maisan is now known as almaisan-away
=== almaisan-away is now known as al-maisan
ogasawaracjwatson: just uploaded linux-meta-mvl-dove
amitkogasawara: why are you up at this hour?07:33
ogasawaraamitk: am actually just going to go to bed now.07:33
amitkogasawara: good night, take care :)07:34
pittiGood morning08:19
micahggood morning pitti08:22
micahgpitti: would it be possible to accept gjs into lucid-proposed08:25
\shpitti: stupid question who is responsible for the partner archive of C.?08:31
pittimicahg: I'll have a round of SRUs next08:57
micahgpitti: awesome thank you08:57
pittimicahg: Brian Thomason (iamfuzz)08:58
micahgpitti: ?08:58
StevenKpitti: \sh asked that :_)08:58
pittioops, sorry ;)08:58
ograRAOF, hey09:00
\shpitti: thx :)09:02
=== spike_ is now known as spikeWRK
\shand btw...cdbs is broken, eventually doing some black magic to DEB_MAKE_INVOKE settting -C without setting $(DEB_BUILDDIR_$(cdbs_curpkg)) that's why libapache-mod-fastcgi is FTBSing in maverick...I wonder how to fix cdbs for that...09:03
\shwithout declaring DEB_MAKE_INVOKE = $(MAKE) inside the package rules file, there is no other way to fix it...and I'm not a cdbs specialist...09:05
\shI think makefile-vars.mk:DEB_MAKE_INVOKE = $(DEB_MAKE_ENVVARS) $(MAKE) $(if $(DEB_MAKE_MAKEFILE), -f $(DEB_MAKE_MAKEFILE),) -C $(DEB_BUILDDIR) $(DEB_MAKE_EXTRA_ARGS) is the bugger in makefile-vars.mk09:06
\shhttp://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596950 <- debian bug report09:09
ubottuDebian bug 596950 in cdbs "makefile-vars.mk need $(cdbs_make_curbuilddir) from makefile.mk" [Serious,Fixed]09:10
RAOFogra: Howdie.09:16
ograRAOF, i have a weird X input problem with a weird setup i run here09:16
RAOFGood, good.  Do go on :)09:16
ograi run an ubuntu chroot on top of an android kernel on unsupported HW and cant get keyboard input to work under X09:17
ogra(i cant tell if it would work in console though since the kernel has no framebuffer console builtin)09:17
RAOFDoes the android kernel provide evdev devices?09:18
ograi see garbage if i cat /dev/input/event0 and type on the keyboard09:18
ograi'm not sure09:18
RAOFThat looks quite likely to be an evdev device.09:18
ograi also cant run udev on the system since i cant start upstart09:18
RAOFOk.  Well, that will certainly freak X's input autodetection out.09:19
ograso i have to live with xorg.conf for input devices ... for the touchpad that works fine09:19
ograand i see the kbd being detected too in the log09:19
ograbut ...09:19
ograthere are queue overrun errors all the time09:19
ograi was wondering if you have any idea if there is a achnce to make it work09:20
RAOFThat would be queue overruns in dmesg?09:20
ogra(note thats only my private toy project, not work related or something ...)09:20
ograno, in Xorg.0.log09:20
RAOFEQ overflows?09:20
ogralet me get the device (i dont have it near me ...) gimme 10min09:21
RAOFI'm not confident that I'll be particularly helpful, but sure :)09:22
=== tkamppeter_ is now known as tkamppeter
=== asac_ is now known as asac
ograRAOF, [ 18128.824] Generic KBD: dropping event due to full queue!09:28
ograthats the error i see09:28
RAOFHm.  And you've set up your keyboard to be driven by evdev, or kbd?09:28
ograsince we dont have kbd in maverick09:29
ogrado we have a package of the old kbd driver anywhere =09:29
ograi'd happily recompile it for arm and try if that fixes it09:29
RAOFYou could probably grab one from Debian; they still need it, because it's useful on !linux09:30
ograyes, it apparantly is :) (/me considers android to be !linux) :)09:31
RAOFI'm not _sure_ whether “ubuntu chroot on android kernel” is sufficiently not-linux to qualify :)09:31
ograwell, there runs a minimal android so ubuntu is effectively run as a chroot in a java VM :)09:32
ograits more than the kernel09:32
ogra(as i said, really odd setup)09:32
directhexi'd say android is !linux if one defines linux as "os with linux kernel and gnu userland". chroots are getting into a grey area09:40
ogradirecthex, well, the java vm runs partitally inside the kernel09:43
directhexdalvik is a monstrous creation09:43
ograthere is a lot of GNU userland still09:43
ogralike busybox :)09:44
kklimondaa lot?09:44
pittiRAOF: ugh, that mesa upload looks scary at this point10:03
cjwatsonogasawara: thanks10:07
\shpitti: there are two more ftbfs fixes mgltools-{support,volume}, can you approve them?10:11
pitti\sh: currently looking at the queue, yes10:12
\shpitti: thx :) I'll try to push more ftbfs fixes today...working down the list from lucas10:12
pitti\sh: many thanks!10:12
pittiso, I processed the queue, all except mesa10:12
* pitti re-reads the diff again; there seems to be a lot of noise due to the renaming of a backend10:13
pittiRAOF: the solution for bug 633406 isn't clear yet according to the bug trail, and that mesa upload changes a lot of other things; has this verrsion been tested at a larger scale?10:15
ubottuLaunchpad bug 633406 in mesa (Ubuntu Maverick) "Display freeze when changing kwin effects settings if effects are active" [High,Confirmed] https://launchpad.net/bugs/63340610:15
\shhmm..what happend to pkg sablotron in maverick?10:15
pittismb: how do you feel about the current lucid-proposed kernel?10:16
smbpitti, Another day another try. What do you think of the current Lucid proposed? Beside the no-op ALSA updates that failed verification there are now some more successful verifications and it has been in proposed for more than three weeks now without people screaming. Beside it has some very nice to have IO performance enhancements.10:16
smbpitti, Hehe10:16
smbI was just thinking on that10:16
pittismb: right, that was my impression, too10:16
smbpitti, Cool. Yeah, I think it should be good to move10:17
pittismb: good, will do; thanks10:17
smbpitti, \o/ Thanks you :)10:17
pittiI'll reopen the failed bugs then10:17
\shmicahg: sablotron is deleted, regarding LP you requested this...(LP #636333)10:17
ubottuLaunchpad bug 636333 in sablotron (Ubuntu) "Please remove sablotron from archive" [Wishlist,Fix released] https://launchpad.net/bugs/63633310:17
\shmicahg: what about caudium, which needs libsablot0*, should we remove it before release as well?10:18
happyaronpitti: ping10:18
pittismb: hm, there's only the main kernell, no -ec2 and armel friends; what happened to them?10:18
micahg\sh: yes, oh..let's see10:18
pittihappyaron: pong10:18
happyaronpitti: excuse me, have you read my email about language packs in kubuntu/xbuntu live cd?10:19
pittihappyaron: I got it, yes; I didn't have time yet to respond10:19
happyaronpitti: thanks10:19
smbpitti, Pending in transfer. I am currently transferring stable things over to Steve and Brad and they got delayed for re-upload for various reasons10:19
micahg\sh: yes, it's been removed from Debian10:20
smbpitti, We upload them soon and then could go over to updates as well10:20
micahg\sh: do you want me to file the bug?10:20
\shmicahg: yes please10:21
micahg\sh: k, thanks for catching that10:21
\shmicahg: np...just working down lucas ftbfs list10:21
micahg\sh: fabrice_sp already beat us to it10:21
\shah yes :)10:22
lifelesscjwatson: hi; https://bugs.edge.launchpad.net/ubuntu/+source/grub2/+bug/648638 may be of interest (or may not)10:23
ubottuLaunchpad bug 648638 in grub2 (Ubuntu) "grub_xputs not found after answering question as recommended during upgrade to maverick" [Undecided,New]10:23
smbcjwatson, Hi Colin, it seems sconklin has only be given upload rights for the Maverick package set but would need the same for Dapper, Hardy, Jaunty, Karmic and Lucid10:26
pittijibel: do you know if anyone tested fglrx on jaunty? I didn't see feedback there10:27
pittijibel: I'm inclined to just push it, since it's rather urgent, and the same patch worked everywhere else10:27
jibelpitti, no. I can give it a try.10:28
lifelessanyone else with an x201s had a jumpy cursor, edge scrolling not working, that sort of thing?10:28
pittinot on my x201 (non-s)10:28
pittilifeless: sounds like the touchpad is picked up by the wrong x input driver?10:29
lifelessI'd assume so10:29
pittithere has been some bugs in the utouchification10:29
pittilifeless: is that with the touchpad?10:29
pittiI'm usually running this machine docked (with usb mouse)10:29
lifelessI'm half way through an ubuntu-bug ginput-device-settings report for this10:29
lifelesspitti: yeah trackpad10:29
lifelesspitti: the nipple is fine10:29
pittilifeless: nope, touchpad works fine here10:31
lifelesspitti: its finding it as SynPS/2 Synaptics TouchPad10:31
lifelesswhich sounds right10:31
pitti[    16.085] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event10)10:31
pitti[    16.085] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"10:31
pitti[    16.085] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"10:32
* pitti redirects you to RAOF then10:32
lifelesshah, details...10:32
lifeless(II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)10:32
lifeless(**) SynPS/2 Synaptics TouchPad: always reports core events10:32
lifeless(**) SynPS/2 Synaptics TouchPad: Device: "/dev/input/mouse0"10:32
lifeless(EE) ioctl EVIOCGNAME failed: Inappropriate ioctl for device10:32
lifeless(II) UnloadModule: "evdev"10:32
lifeless(EE) PreInit returned NULL for "SynPS/2 Synaptics TouchPad"10:32
pittilifeless: oh, interesting10:33
pitti[    16.583] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse1)10:33
pitti[    16.583] (II) No input driver/identifier specified (ignoring)10:33
pittilifeless: so on mine it tries to pick up both, but mouse1 is blacklisted somewhre10:33
pittilifeless: do you have a synaptics stanza for the corresponding evdev device, too?10:34
lifelessmouse1 in the nipple for me; I have no input devices in xorg.conf10:34
cjwatsonlifeless: your boot loader is incorrectly installed10:35
cjwatsonlifeless: (I haven't looked at the bug yet but that's what that error basically means.  see my blog for details)10:35
lifelesscjwatson: I'll look at your blog; the concerning thing for me was that following the advice resulted in both no-error and no-boot.10:36
cjwatsonlifeless: as far as I can see you read the help text precisely backwards10:36
cjwatson Note: It is possible to install GRUB to partition boot records as well, and10:36
cjwatson some appropriate partitions are offered here.  However, this forces GRUB to10:36
cjwatson use the blocklist mechanism, which makes it less reliable, and therefore is10:36
cjwatson not recommended.10:36
pittismb: oh argh, l-b-m is still in the unapproved queue, with the fix to make the gobi_loader rules ABI specific10:36
cjwatsonand yet you interpreted this as saying that installing to sda was a bad idea?10:36
pittismb: would you mind reuploading this with just the top changelog, and we'll try to push that to -updates fast?10:37
cjwatsonwhat it actually says is that installing to sda1 may be a bad idea ...10:37
lifelesscjwatson: *blink*10:37
lifelesscjwatson: Perhaps it would be clearer to provide the good-idea bad-idea hint in the list - either as two lists [recommended] and [not recommended], or as a marker in the list ?10:38
smbpitti, I could, but compared to what is in updates for that package all the changes in the log are in. So why only the last one?10:38
cjwatsoncan't provide two lists, debconf doesn't support it10:38
lifelesscjwatson: (yes, clearly I did read it backwards, for which I have no excuse)10:38
cjwatsonI'll transform your bug into a recommendation to put a marker in the list10:38
pittismb: http://launchpadlibrarian.net/56311364/linux-backports-modules-2.6.32_2.6.32-25.24_source.changes -> 25.23 is in -updates now10:39
pittismb: so now it's just -25.24 which is new10:39
smbpitti, Ah ok, got it10:39
pittismb: (rejected the current upload)10:39
smbpitti, Ok, will do a quick repackaging. Just a second10:39
pittismb: sorry, we probably should have accepted and tested this one first, and then moved to -updates10:39
pittibut as long as we don't get a new ABI, it should be fine10:40
pittioh, and the new ABI will have the custom path anyway10:40
cjwatsonlifeless: interesting that you saw the dialog at all; I suspect you previously had removable devices plugged in and perhaps had asked for grub to be installed to one of them (maybe without noticing)?10:40
smbpitti, Probably would have been more convenient for the gobi_loader users. But the update from that won't clash and the abi doesn't change as well. So maybe its not that bad after all10:41
lifelesscjwatson: I don't think so; this is my x201s (last machine to be upgraded)10:41
cjwatsonlifeless: do you need repair assistance?10:41
lifelesscjwatson: it was a fresh install 6 months ago10:41
smbpitti, Just the current update may require people to remove the old package...10:41
pittismb: right, it shouldn't cause problems, but I'd still like to have this change in, just in case10:42
lifelesscjwatson: no, I'm good now; live-cd;chroot;reconfigure grub-pc and select both options on the theory that it was probably user error of some sort.10:42
lifelesspitti: appears that update-manager didn't update the evdev package correctly.10:42
cjwatsonlifeless: you can/should just select sda10:43
cjwatson(selecting sda1 as well is technically harmless but may cause confusion later)10:43
lifelessok, I'll reconfigure again next time I'm about to reboot10:43
cjwatsonthe partition options are there for the minority (but not negligible minority) who have some other custom boot loader in the MBR10:44
lifelesscjwatson: yeah, I can certainly understand the need and tradeoffs10:44
lifelessI did a good job of foot-shooting10:44
directhexcjwatson: tri-booting my imac also needed a partition install of grub10:45
cjwatsonright, weird hardware another reason :)10:46
smbpitti, lucid-lbm re-uploaded (will probably take one or two more minutes to show up in lp)10:47
pittismb: cheers10:48
\shhmmm...I'm stucked ...10:48
\shlibmed-dev : Depends: libmed1 (= 2.3.6-2) but it is not going to be installed10:48
\sh libmedc-dev : Depends: libmedc1 (= 2.3.6-2) but it is not going to be installed10:48
\shbut apt-get install those files on a standard maverick, works as expected, only sbuild chroots means "no this doesn't work"10:48
lifelesspitti: appears the xorg stack is mid transition or something; xserver-xorg-input-7 conflits with xserver-xorg-core ><10:49
\shoh wow...ecs is broken10:51
jibeltkamppeter, mvo, another package blocking the upgrade because of the change to foomatic-db-compressed-ppds: bug 64746010:57
ubottuLaunchpad bug 647460 in update-manager (Ubuntu) "Upgrade from 10.04 to 10.10: printconf is blocking the upgrade." [High,Triaged] https://launchpad.net/bugs/64746010:57
mvojibel: thanks10:59
cjwatsonsmb: sconklin> fixed11:07
pitticjwatson: I want to do some no-change rebuilds for NBS cleanup; do you prefer to review them, or can I just accept them myself?11:08
cjwatsonno-change rebuilds should be fine as long as they aren't packages with giant buildd times11:11
cjwatson(I meant to type "build" but that's good enough ...)11:11
cjwatsonpitti: which packages?11:11
pitticjwatson: I didn't start yet11:12
cjwatsonnote that libopensync-plugin-gnokii needs a non-trivial source change11:12
cjwatsonI'm not sure if anyone is looking at the opensync cluster11:12
lifelessI ran screaming11:15
cjwatsonit wasn't obvious to me that there were huge numbers of no-change uploads available from NBS any more (doko has been cleaning a lot of stuff up), but absolutely go ahead if you find some11:15
cjwatsonmy suspicion is that most of the rest require source work11:15
lifelessI think my name is still on part of it simply because it hasn't been uploaded outside of experimental, or some such.11:15
pittiI'll see how far I'll get11:15
lifelessnight all11:15
pitticjwatson: but I guess stuff like libavutil49, libindicator0, libvala0 should be triviall11:16
pittiI'll just start from the top11:16
=== diwic is now known as diwic_afk
cjwatsonlibvala0 is just libvala-dev and those are all build-deps11:16
cjwatsonlibindicator0 is just ubiquity which is already in progress11:16
cjwatsonlibavutil49 not sure, it's different between architectures so will require some analysis11:16
pittilibvala-dev is NBS itself; I'll check the rdepends for having alternatives to libvala-0.10-dev11:17
cjwatsonpitti: BTW, I rewrote checkrdepends over the weekend - it has a slightly different argument syntax now11:18
pittiI noticed11:18
cjwatsonthough that wasn't the point, the point was to get cron.NBS runtime down to a minute11:18
pittiit's using launchpadlib now?11:19
hemanthImportError: No module named nautilus, even after installing python-nautilus, any suggestions?11:19
pittiperhaps we should add this to ubuntu-archive-tools bzr11:19
cjwatsonit's still analysing Packages/Sources directly, but it's a lot faster to do that inline in python rather than repeatedly calling grep-dctrl11:19
cjwatsonsure, if you like, though we don't have that checked out anywhere on cocoplum right now11:20
cjwatsonfaster> well, at least if you're asking about large numbers of packages at once11:20
cjwatsonalso, I just made it look at main/installer-*/current/images/udeb.list, so it can now spot when d-i is still using a given kernel ABI and create an artificial dependency11:21
cjwatsonwhich should save us from future accidents11:21
pittiah, right, we use /srv/archive-scripts/bin bzr right now11:22
pittihm, it would be easier if libvala0.10-dev would Provides: libvala-dev..11:23
pittididrocks: ^ WDYT?11:23
didrockspitti: I think it's safe to do that, right11:24
didrocksI don't see any reason that people want to build with previous buggy vala version11:24
pittididrocks: I mean it's easier than adding alternative build-deps to http://people.canonical.com/~ubuntu-archive/NBS/libvala-dev11:24
didrockspitti: yeah, I agree, do you want to do the change? I'll report it to debian then.11:25
pittididrocks: would be nice; thanks!11:26
didrockspitti: thank to you :)11:26
pittididrocks: actually, no11:26
pittididrocks: Debian didn't rename them that way11:26
pittithey just use unversioned packages11:26
pittiI'm not quite sure why we went through the hassle of versioning them11:27
cjwatsoncould somebody look at bug 648469 and check what the right fix is?  then we can remove python-gnome2-desktop and python-gnomeprint11:27
ubottuLaunchpad bug 648469 in labyrinth (Ubuntu Maverick) "depends on NBS python-gnome2-desktop" [High,New] https://launchpad.net/bugs/64846911:27
pittiI'll just add the provides:, and NBS libvala{0,-dev}11:27
pitticjwatson: for powerpc specific FTBFSes which block NBS removal, I guess we'll just remove them anyway and say "*shrug*"?11:28
cjwatsonif they're leaf packages we can do that11:28
didrockspitti: debian did it in 0.9.5-1 IIRC11:28
cjwatsonis dpm on holiday or something?11:29
pittididrocks: no, see http://packages.qa.debian.org/v/vala.html11:29
cjwatsonpitti: one thing only you can do, since dpm doesn't seem to be around; there are several uninstallable language packs11:29
pitticjwatson: will look at those11:30
pittivala uploaded with the new provides:; it's not a no-change upload, so I'll let someone else review it11:31
pittididrocks: ^11:31
didrockspitti: I think I don't understand :) I didn't do the merge (was in vacation) but it seems nevertheless, they have a libvala-0.10-dev package shown in http://packages.debian.org/source/experimental/vala or is there something I'm missing?11:32
pittididrocks: ah, in experimental only; I see11:33
pittididrocks: ok, thanks for forwarding11:33
* didrocks is not crazy (yet!) :p11:33
pitticjwatson: did dpm happen to talk to you about the final maverick langpack set?11:36
\shpitti: could you approve ecs pls, thx :)11:36
cjwatsonpitti: no11:37
cjwatson(I don't think so)11:37
pitticjwatson: ok, thanks; we'll need a fresh -base rebuild and thus a full export11:38
pittiit's too late to squeeze it into the RC for Thursday, but I'll request one now and build them locally, so that we can upload them right after RC11:38
pitticjwatson: ^ sounds okay to you?11:38
pitticurrent langpacks cause an extra 7 MB on the alternates, and make them overflow, but we can just drop a langpack there for the RC11:39
cjwatsonOK for after RC, yes11:40
Riddellpitti: the LanguagePackTranslationDeadline is Sep 30th11:40
cjwatsonwhat about the current uninstallables?  do those need that fresh rebuild?11:40
pittithat, too11:40
cjwatsonthey're causing some livefs build failures11:40
cjwatsonso we'll need to work around that11:41
pittithe -kde variant for those is newer than the main one11:41
cjwatsonat least edubuntu-dvd11:41
pittiwe could drop the strict dependency from -kde-base to -base11:41
pittiin fact, I think I can make this change in the langpack-o-matic templaltes11:41
pittibut that will only get effective at the next upload, of course11:41
cjwatsonor we could exclude those language packs from the build11:43
cjwatsonI think that's preferable for RC11:43
pittifor RC, yes11:43
pittiand after that it'll fix itself11:43
cjwatsonright, we won't need the langpack-o-matic hack11:43
cjwatson\sh: accepted11:45
pittididrocks: so you'll do the yelp update for bug 605577? I'll manually fix the -gnome-en langpack now, then11:46
ubottuLaunchpad bug 605577 in language-pack-gnome-en-base (Ubuntu Maverick) "Help contents title bar shows cubes with numbers instead of a proper title" [High,In progress] https://launchpad.net/bugs/60557711:46
didrockspitti: oh, as you wish. I've assigned to me before you told you wanted to handle it, but if you want to do both, please do :)11:47
pittididrocks: ok, I'll have a look11:47
didrockspitti: thanks :)11:48
\shcjwatson: thx11:48
pittiseb128: why do we carry a manual patch 07_rosetta_translations_update.patch in yelp?12:02
pittiseb128: especially because this patch isn't in the series?12:05
didrockspitti: the patch isn't in the series during unstable update IIRC to avoid having to refresh it at each new ustream version. It should be added back in final upload12:09
didrocks(just using my memory, not 100% sure about it but that should be that :))12:09
pittididrocks: ok; I fixed the patch, but I won't upload it right now, since it's not currently cuasing trouble12:09
pittibug updated as well; so we just need to accept the new -gnome-en-base, and everything is well again12:10
=== diwic_afk is now known as diwic
cjwatsonpitti: accepted12:21
jibellatest python-virtkey is broken in maverick. bug 64869512:23
ubottuLaunchpad bug 648695 in virtkey (Ubuntu) "package python-virtkey (not installed) failed to install/upgrade: file does not exist: /usr/lib/python2.6/dist-packages/python_virtkey-0.60.0.egg-info" [Critical,Triaged] https://launchpad.net/bugs/64869512:23
seb128pitti, sorry I was at lunch12:27
seb128pitti, what didrocks say on the serie12:27
pittiseb128: ok, thank you12:27
seb128pitti, we carry the patch because translated xml are generated on build12:27
seb128so they don't work with langpacks12:27
pittiah, I see12:27
=== doko__ is now known as doko
RAOFpitti: Re: mesa - it's been tested by me, Sarvatt, ScottK, and mvo thus far, and is now actually from the 7.9 release branch.12:34
dokoRAOF: btw, what is the replacement for the dropped mesa-utils?12:44
RAOFdoko: The split-out mesa-demos on revu http://revu.ubuntuwire.com/p/mesa-demos12:45
RAOFUpstream dropped the code we shipped in mesa-utils from the main mesa tree between 7.8 & 7.912:46
RAOFmesa-demos is exactly that code, now released as a separate project.12:47
dokoRAOF: somebody reviewing this currently?12:47
dokook, looking at it12:48
\shdoko: could you push sun-java6 6.21dlj to c. partner repo? you could use the package from https://edge.launchpad.net/~sun-java-community-team/+archive/sun-java612:51
\shfor maverick that is...dunno if someone else can do this12:51
doko\sh: I'll have a look12:51
\shdoko: thx a lot :)12:51
=== MacSlow is now known as MacSlow|lunch
dokoRAOF: is the complete 11MB source really needed?12:58
RAOFdoko: I could repack the tarball and strip everything we don't ship out, for Maverick.12:59
RAOFFor Natty I want to ship *all* the demos in a separate package, as they're useful for users to pinpoint problems in mesa.13:00
dokook, then it makes sense13:01
dokoRAOF: uploaded, waiting in NEW13:06
RAOFdoko: Awesome, thanks.13:06
dokoRAOF: needed for http://people.canonical.com/~ubuntu-archive/NBS/mesa-utils (openened a bug for mesa, although bryce2 did tag it as ppc, don't know why)13:07
RAOFThat'd be an arsenal script, probably grabbing from the powerpc in the text of the bug.13:08
RAOFI closed that mesa bug in the changelog, right?13:09
RAOFYes, there it is.  Good :).13:09
RAOFI'm off to bed now.  If you want to discuss mesa with someone pitti I'll point you at Sarvatt for the next 10 hours or so :).13:29
pittiRAOF: ok, thanks13:30
=== diwic is now known as diwic_afk
jibelpitti, fglrx-installer verified in jaunty too.13:48
pittijibel: nice, thanks13:48
* pitti moves to -updats13:48
\shhmm...can someone translate this buildlog for me? It says, FTBFS but everything is ok it seams14:00
\shseems even: http://launchpadlibrarian.net/56574998/buildlog_ubuntu-maverick-amd64.emerald_0.7.2-0ubuntu5_FAILEDTOBUILD.txt.gz14:00
wgrant\sh: Look at the end of the log.14:01
wgrantThe implicit pointer conversion thing.14:01
\shwgrant: yeah I saw it, but the reason seems to be a bit misleading..the package builds perfectly, eventually LP needs to be trained to give another reason for arch problems14:02
=== bilalakhtar_ is now known as bilalakhtar
cjwatson\sh: it's a recognised hack14:03
\shcjwatson: I mean the subject of the mail , that was irritating me :)14:04
cjwatsonsure, like I say, it's not a particularly clean hack and everyone involved in creating it knew this :-)14:05
corecodethe last gnome-terminal update on lucid changes some useful defaults14:08
=== MacSlow|lunch is now known as MacSlow
jibelpitti, I've added a bugpattern for the current virtkey issue but it's not pushed to http://people.canonical.com/~pitti/bugpatterns/ . Are commits to the lp branch still rolled out every 15mn ?14:14
pittijibel: they should, yes14:19
pitti*/15 * * * * env LC_ALL=C bzr pull -q -d ~/public_html/bugpatterns >/dev/null14:19
pittishould have happened 4 mins ago, let me check14:19
pittijibel: it's at r147 for bug 64251814:19
ubottuLaunchpad bug 642518 in fglrx-installer (Ubuntu Karmic) "[MASTER] package fglrx 2:8.723.1-0ubuntu4 failed to install/upgrade: Kernel fix for CVE-2010-3081 breaks fglrx" [High,Fix released] https://launchpad.net/bugs/64251814:19
pittijibel: a manual pull doesn't bring anything new; did you push?14:20
=== bilalakhtar_ is now known as bilalakhtar
jibelpitti, yes I've pushed it, but can't find it anywhere and I'm still at r147 :/ probably another pebkac, retrying. sorry14:31
=== ara_ is now known as ara
=== dendro-afk is now known as dendrobates
pittijibel: worked now15:21
=== ivoks-afk is now known as ivoks-zombie
jibelpitti, yes, thank you. I really don't know where my previous push is gone.15:23
tkamppeterpitti, hi15:24
pittijibel: to the place whe all the lost socks and pens go?15:24
pittihey tkamppeter15:24
jibelpitti, very likely :)15:24
=== bjf[afk] is now known as bjf
tkamppeterpitti, last week I got a patch from Japan for the pdftopdf filter so that it builds with Poppler 0.15.x without loosing compatibility with older Poppler versions. I have applied it only to the upstream CUPS add-on package but not (yet) to the BZR at Debian.15:26
tkamppeterpitti, now I want to ask whether I can already apply it to the BZR (withoutbeing packaged for Maverick) or whether I should wait for Maverick being released.15:27
pittitkamppeter: is that important for maverick? we already have the new poppler, after all?15:27
pittitkamppeter: oh, please push it; it's the Debian unstable development tree, after all15:27
pittitkamppeter: if we need another maverick change, we'll branch it15:27
tkamppeterpitti, thanks, I wll push it.15:34
tkamppeterpitti, done.15:44
=== deryck is now known as deryck[lunch]
pittiRiddell: does the dbus you just uploaded differ in any way to the one from 2 hours ago?16:14
tkamppeterpitti, can you have a look at bug 647369? It is probably a problem caused by the upstartification of CUPS?16:16
ubottuLaunchpad bug 647369 in gutenprint (Ubuntu) "gutenprint: postinst: lpstat: no such file or directory" [Undecided,Incomplete] https://launchpad.net/bugs/64736916:16
pittitkamppeter: very unlikely -- it seems it can't find /usr/bin/lpstat, but I wouldn't know why16:17
pittiit's in cups-client, which is installed16:17
\shttx: will you give libspring-2.5-java a new punch to actually build on maverick? ;)16:17
tkamppeterpitti, the "lpstat: no such file or directory" is caused by lpstat being called to quickly after CUPS being started. In that moment CUPS has not yet created the socket file /var/run/cups/cups.sock16:18
tkamppeterpitti, if lpstat is not found, one would get "Command not found".16:18
ttx\sh: *sigh*16:18
tkamppeterpitti, simply try "sudo stop cups; sudo start cups; ls -l /var/run/cups/cups.sock"16:19
\shttx: there are some packages which are in need of it ;)16:19
pittiright, that'd start in the background16:19
Riddellpitti: fixed .symbols file16:20
pittiRiddell: ah, so I'll reject the previous upload16:20
pittiRiddell: (done)16:20
tkamppeterpitti, formerly, the "invoke-rc.d cups force-reload" exited only after CUPS was ready and so the next line in the script could already use CUPS.16:20
* ttx punches16:21
\shttx: rocking :)16:22
tkamppeterpitti, so the backward compatibility commands, like "invoke-rc.d", "service", "/etc/initd.*" should wait for the service getting ready before exiting.16:22
pittiyes, indeed16:22
tkamppeterpitti, should I move the bug to upstart and target it for Maverick?16:23
pittiso this would require a rather ugly while status cups | grep -q start/running loop16:23
tkamppeterpitti, in the gutenprint postinst script works adding16:23
tkamppeter for i in 1 2 3 4 5; do if [ -r /var/run/cups/cups.sock ]; then break; fi; sleep 1; echo -n "."; done; echo;16:23
pittiah, I see; but 5 seconds wasn't enough there?16:24
tkamppeterbut this fixes only the reported problem with Gutenprint, there are probably many more.16:24
pittiKeybuk: ^ would it be realistic to have invoke-rc.d (on an upstart job) wait until the servie is "start/running"?16:24
tkamppeterpitti, the loop breaks as soon as the file appears, for me always after one second, but there can be slower systems.16:25
pittithat might break tasks, though?16:25
Keybukpitti: a better question would be to ask why invoke-rc.d doesn't wait for that right now16:25
tkamppeterpitti, "start/running" is perhaps not even enough, as I get16:26
tkamppetertill@till:~/ubuntu/gutenprint$ sudo stop cups; sudo start cups; ll /var/run/cups/cups.sock16:26
tkamppetercups stop/waiting16:26
tkamppetercups start/running, process 2335616:26
tkamppeterls: cannot access /var/run/cups/cups.sock: No such file or directory16:26
tkamppeterpitti, so a start/running is reported but the file is still not there.16:26
pittitkamppeter: hm, but that's something that the original init script didn't do either16:26
Keybukpitti: blocking is the default behaviour for "start"16:27
Keybukto *avoid* start blocking until its start/running, you'd need --no-wait16:27
pittiKeybuk: ah, thanks; so it's probably unrelated (see above, we need to wait on the socket to appear)16:28
Keybukyou can use a post-start script for that16:28
Keybukpost-start script16:28
Keybuk   while [ ! -e /var/run/cups/cups.sock ]16:28
pitticups has one already for the coldplugging16:28
Keybuk  do16:28
Keybuk    :16:28
Keybuk  done16:28
Keybukend script16:28
pitti(perhaps a sleep .5)16:29
Keybukwell, yes, a sleep in there would be less "my cpu! mine!"16:29
pittiKeybuk: and actually giving the CPU to cupsd to start :)16:29
tkamppeterpitti, with16:29
tkamppetersudo killall cupsd; sudo /usr/sbin/cupsd; ll /var/run/cups/cups.sock16:29
pittitkamppeter: this indeed seems conceptually unrelated to the upstartification, but the different timing behaviour might have made it more probable16:30
pittitkamppeter: so, I'm fine with cups' upstart script waiting until the daemon is ready16:30
tkamppeterone never gets "no such file or directory". And this is what the old init script did.16:30
pittiah, right; previously we had cupsd take care of the forking16:30
pittinow we call it with -f and have upstart do the fork16:31
cjwatson\sh,ttx: libspring-2.5-java needs a manual build; we have a sysadmin ticket open for it and they will do it this week16:31
tkamppeter"cupsd -f" should only be used for debugging not for regular use.16:31
ttxcjwatson: arh, ok16:32
ttxcjwatson: looked like a transient error16:32
pittitkamppeter: hang on16:32
Riddellsladen: how's that font package doing?16:39
pittitkamppeter: pushed to r90616:43
pittitkamppeter: I'll create a maverick branch (which we will also use for SRUs) and cherrypick it there16:43
pittitkamppeter: lp:~ubuntu-printing/cups/maverick16:45
sladenRiddell: sabdfl is working on licencing at the moment, or was until robbiew filed a higher-priority interupt16:46
tkamppeterpitti, thanks.16:46
sladenRiddell: so whenever that's finalised plus some number of hours to implement16:47
Riddellsladen: are you doing the implementing?16:50
pittitkamppeter: uploaded; needs someone else to review now16:50
tkamppetersudo stop cups; sudo start cups; ll /var/run/cups/cups.sock16:54
tkamppeterworks for me now, but16:54
pittitkamppeter: I ran that in a loop for about 10 minutes16:54
tkamppetersudo /var/lib/dpkg/info/cups-driver-gutenprint.postinst  configure16:55
tkamppeterstill does not work.16:55
=== deryck[lunch] is now known as deryck
pittitkamppeter: I just get a complaint about invoke-rc.d being out of date, and16:57
pittilpstat: No destinations added.16:57
pittitkamppeter: what do you see?16:57
tkamppeterpitti, I get the originally reported16:57
tkamppeterlpstat: No such file or directory16:58
pitti# while true; do stop cups; sleep 0.5; start cups; lpstat -p; done16:58
pittithat's what I'm running16:58
* pitti refines to # while true; do stop cups; start cups; lpstat -p 2>&1|grep -q "No destinations" || exit 1; done16:59
pittitkamppeter: you are using my updated upstart script now?16:59
tkamppeterpitti, can it be that this post-install script does a "reload" of CUPS instead of stopping and starting it?17:00
tkamppeterpitti, in which way does upstart this "reload" of CUPS?17:00
pittiperhaps; I'm not sure what reload does, hang on17:00
pittiso, above loop works fine for me17:00
cjwatson'man reload' tells you what upstart's reload does17:01
sladenRiddell: yes17:02
pittitkamppeter: ah, right, it SIGHUPs the daemon17:02
Riddellsladen: ok let me know when you're starting that.  and robbiew stop distracting Mark :)17:02
tkamppeterpitti, try it with "reload cups" instead of "stop cups; sleep 0.5; start cups;".17:02
pittitkamppeter: right, I can reproduce it there17:02
tkamppeterpitti, the "reload" does not stop and start CUPS it simply HUPs at it.17:03
pittitkamppeter: but that's what the init.d script did as well17:03
pittitkamppeter: so in this regard the upstartification should make no differernce17:03
pittiRiddell: erm, upgrading dbus from 1.2 to 1.4 at this time? this is an awfully big diff for a such a critical service17:05
Riddellpitti: yes, I realise it's a long shot17:05
Riddellbut it does stop random crashes happening in threaded apps which use dbus17:05
tkamppeterpitti, so you have fixed an independent problem which also had to get fixed and I should add a wait loop to the postinstall script of Gutenprint?17:05
pittican't we backport the race condition fix?17:05
pittitkamppeter: yes, I think so; can you please add back a gutenprint task then?17:06
Riddellpitti: I'm told we can't, the patch isn't reliable in the 1.2 version17:06
pittiI remember that we discussed that earlier on around beta time, and back then we thought it was too intrusive17:08
Riddellpitti: well at least I can tell upstream I tried :)17:09
pittibjf: you uploaded linux-mvl-dove to maverick-proposed instead of final, was that intended?17:09
=== dendrobates is now known as dendro-afk
bjfpitti, no17:10
pittibjf: ok, I guess I should reject it then, and you'll reupload to maverick?17:10
bjfpitti, yes, please reject it17:10
=== al-maisan is now known as almaisan-away
tkamppeterpitti, new gutenprint package uploaded.17:23
pittitkamppeter: thanks, will review in a bit17:23
=== bilalakhtar_ is now known as bilalakhtar
=== ivoks-zombie is now known as ivoks
=== hunger is now known as Guest84224
smbpitti, That upload of mvl-dove should have been made by Tim. But please reject the fsl-imx51 in Karmic17:35
=== dendro-afk is now known as dendrobates
pittismb: done17:36
=== dendrobates is now known as dendro-afk
=== beuno is now known as beuno-lunch
=== dendro-afk is now known as dendrobates
sladenRiddell: realistically, tomorrow at the earliest17:50
Riddellsladen: we'll be frozen for RC by then17:51
Riddellit'll need to wait until Thursday17:52
macocjwatson: these quality status emails keep making me go "must buy cjwatson a $beverage"17:52
* cjwatson wonders how he's managing that; perhaps sync processing17:59
=== beuno-lunch is now known as beuno
=== hanska is now known as dapal
bdrung_doko_: why did you close bug #640732?19:24
ubottuLaunchpad bug 640732 in audacious-plugins (Ubuntu) "audacious2 crashed with SIGSEGV in std::ios_base::Init::~Init()" [High,Invalid] https://launchpad.net/bugs/64073219:24
doko_bdrung_: glibc patch not accepted upstream?19:26
bdrung_doko_: according to audacious upstream it's fixed in gcc-4.5, but not in gcc-4.419:29
doko_bdrung_: and why do thy send a pointer to a glibc patch? and what needed fixing in gcc?19:31
bdrung_doko_: quote: "This is a duplicate of AUDPLUG-241. It was ruled to be a bug in the STL shipped by GCC 4.4, which has been fixed by GCC 4.5."19:33
=== doko_ is now known as doko
dokobdrung_: sorry, do *you* understand the reasons for "It was ruled to be a bug" ?19:34
dapaldoko: (OT: care to reply to DBTS #573745 ?)19:35
bdrung_doko: i don't understand the bug.19:36
bdrung_doko: let's make the test if it works with gcc-4.519:36
=== dendrobates is now known as dendro-afk
=== dendro-afk is now known as dendrobates
didrocksurgh, seems amd64 builders have some issues, known?20:01
bdrung_doko: it works if i am using CXX=g++-4.5, but it fails if g++-4.4 is used20:01
didrocksseems there are really an issue, second fail: https://launchpad.net/ubuntu/+source/unity-place-files/0.5.30-0ubuntu1/+build/1977028/+files/buildlog_ubuntu-maverick-amd64.unity-place-files_0.5.30-0ubuntu1_FAILEDTOBUILD.txt.gz20:16
seb128didrocks, those are an arch all,any mistmatch issue20:18
seb128libunity-dev : Depends: libunity0 (= 0.2.44-0ubuntu1)20:18
seb128didrocks, it seems you just need to have unity published on amd64 and retry20:18
didrocksseb128: urgh, I stopped too early, just stucked at sh: gcc: not found20:19
didrockssorry, yeah20:19
didrockswell, new unity release upladed soon…20:20
dokochrisccoulson_: please use dh_python2 for future python packaging (instead of python-central)20:21
dapaldoko: re-ping?20:21
dokodapal: ?20:24
dapal[20:35:47] <dapal> doko: (OT: care to reply to DBTS #573745 ?)20:25
dokohow does the affect ubuntu?20:26
dapaldoko: I prefixed that with OT, and I see you're active here, and never replied to any mail directly sent to you20:26
dapaldoko: so I just caught the chance to ping you here. I could've also done that privately.20:27
dokonot today, sorry20:28
dapaldoko: can I have an ETA?20:28
dapaldoko: also, that bug is open since March, I would expect much more consideration from a fellow DD20:31
lifelessis there a blessed way to check if a process is running ?21:05
ogra_acpgrep ?21:06
lifelessmmm, api wise I meant - its in python21:11
ogra_acoh, k21:12
sorenlifeless: os.kill(pid, 0)21:26
sorenlifeless: I suppose.21:26
sorenlifeless: Whether it's the process you're expecting it to be... That's a different story.21:26
sorenlifeless: ..but kill(2) with a signal 0 checks if there's such a process.21:27
lifelessthere is some dodgy code in lp's test runner21:27
lifelessto delete it entirely is the long term goal, but its going to be an iterative thing; gotta get it into a nicer layout, then build on that to get better isolation, then the old cruft can go21:27
sorenlifeless: If you start the process yourself, you can keep track of its cmdline and check /proc/blah/cmdline (assuming the process doesn't alter that).21:27
ebroderIf it's a child process you could wait4() on it with WNOHANG21:33
lifelessit wouldn't be, but thanks21:34
=== hanska is now known as dapal
=== yofel_ is now known as yofel
=== dendrobates is now known as dendro-afk
=== dendro-afk is now known as dendrobates
marmy ubuntu clock freezed at 00:01. What do I do? :)23:28
ogra_acwind it up23:29
marin ubuntu even clock doesn't work right :/23:30
=== dendrobates is now known as dendro-afk
sladenmar: please take a screenshot23:42
sladenmar: please file it at  http://launchpad.net/ubuntu/+source/gnome-panel/+filebug23:43
sladenmar: including information about your timezone23:43
micahgmar: actually, running 'ubuntu-bug gnome-panel' will probably be better23:45
mari changed settings a little and seems that it's running now23:47
marit happened a lot to me for a few days so i'll try to catch it later23:48

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