/srv/irclogs.ubuntu.com/2008/09/29/#ubuntu-devel.txt

=== ScottK-vacation is now known as ScottK
retro89hellow02:01
dholbachgood morning04:07
StevenKdholbach: It's what, 5am?04:08
dholbachStevenK: I didn't sleep very well, so I thought "why not get up and do some work?" - YAWN04:08
Hobbseemorning dholbach!04:09
dholbachhi Hobbsee04:09
Hobbseewow.  since when does hppa only have 8 pending builds for intrepid?04:11
StevenKHobbsee: Since the other 5,000 failed04:11
HobbseeStevenK: ahh.  that'd do it.04:11
TheMusooheh. If one sees an FTBFS mail, one can almost be 100% sure that it is hppa that has failed.04:18
ajmitchdo you have spam filters to throw them away?04:19
dholbachjames_w: congratulations!04:25
* Darklock is still up, celebrating the fall of the CSU in bavaria :->04:26
=== bddebian2 is now known as bddebian
* Hobbsee beats dholbach with a herring04:50
Hobbseedholbach: yes, 6 mails later, I understand that james_w is a MOTU!  :P04:50
DarklockMaster Of The Universe?05:04
Darklockit is......05:04
pittiGood morning06:38
wgrantHi pitti.06:38
Hobbseepitti!06:41
* Hobbsee waves the "we love pitti" flag around, and drapes it over pitti's shoulders06:41
Hobbsee(thanks to the we love pitti fanclub for the flag, which got borrowed)06:43
* pitti blushes06:43
pittiBenC: I sub'ed you to bug 271956, I'd like to get your "still works" ack before uploading this; thanks in advance!06:44
ubottuLaunchpad bug 271956 in makedumpfile "Upgrade to new upstream version 1.2.9" [Undecided,New] https://launchpad.net/bugs/27195606:45
nxvlheh06:47
nxvli will bring a "we love pitti" flag to UDS06:47
nxvl:D06:47
=== macd_ is now known as macd
StevenKpitti: So, wgrant and I found two things that aren't in NBS, and should be. lib{32,64}ffi406:49
wgrantStevenK: Ah, thanks - I'd forgot about those!06:51
pittiStevenK: oh? libffi4 was NBS, and removed a while ago06:51
StevenKpitti: lib32ffi4 is still listed on amd6406:52
StevenKFilename: pool/universe/g/gcc-4.2/lib32ffi4_4.2.3-2ubuntu7_amd64.deb06:52
pitti$ asrc gcc-4.2|grep Binary.*ffi06:52
pitti$06:52
wgrantlib{32,64}ffi4 are very arch-specific, definitely NBS, but not in NBS.06:52
pittisorry, asrc = apt-cache show-src06:52
wgrantRight.06:53
wgrantThey're not built any more.06:53
wgrantTheir source is long gone.06:53
wgrantThey're still published.06:53
wgrantBut they're not in the generated NBS lists.06:53
StevenKBuilt from gcc-4.2, which is currently 4.2.4-3ubuntu206:53
wgranthttp://launchpad.net/ubuntu/intrepid/amd64/lib32ffi406:54
wgrantIt could be because they're arch-specific, or because their source is published in another distroseries, or blah blah blah...06:55
persiaI've seen this previously, which arch-specific stuff.  Is there maybe a way to tweak the NBS finder to find things like this?  The last I found was some leftover linux-meta stuff.06:55
persias/which/with/06:56
pittiI'm not entirely sure how the NBS finder works06:56
wgrantDo we have the source?06:56
pittiwgrant: for the reverse depends checker yes, but the list of stale packages is created by a soyuz script, which isn't too useful without the corresponding database, etc.06:59
wgrantpitti: Ahh, so it is a Soyuz bug after all.07:00
=== fargiola` is now known as fargiolas|afk
seb128to whoever build retried gnome-python-extras that didn't work because pygtk is out of sync between arch all and any pacakges due to xvfb being broken08:37
pittiseb128: oh, indeed, I was going to ask you about pygtk08:39
pittiseb128: I sponsored that trivial fix for the example hashbang, and it FTBFSed all over the place08:39
pittiseb128: oh, first: bonjour!08:39
pittiseb128: some failed due to xvfb, amd64 failed due to "extension "RANDR" missing on display ":99.0""08:40
RAOFThat's an awesome FTBFS error in so many ways :)08:41
seb128pitti: guten tag ;-)08:41
pittiseb128: so I could maybe try the workaround with the mesa build dep, too?08:41
seb128pitti: we could, would be nice if the xorg guys were fixing xvfb though08:41
* directhex hands pitti cake08:41
persiaI don't see a bug on that.  Does it need one?08:48
pittipersia: well, not really; we need to get the damn thing building; if that's tricky to do, we could use a bug as discussion place, of course08:54
pittiI'll set up an intrepid chroot somewhere; it locally built fine08:54
persiapitti: Makes sense.  I was thinking one against xvfb, as I was also looking at pygtk today.08:55
pittioh, xvfb, indeed08:55
seb128pitti: just do the workaround for pygtk I would say08:56
pittiseb128: will that also help for the xrandr thing?08:56
pittiseb128: I can do a test build on i386, but I currently don't have an amd64 pbuilder at hand08:57
seb128pitti: that seems to be a random xvfb error, dunno about it but it might08:57
slangaseklool: ping08:57
loolslangasek: pong08:57
seb128pitti: other option is to comment the xvfb-run call in debian/rules, it's just to call the testsuite08:57
loolWhat did I break /again/08:57
lool:-P08:58
seb128pitti: or try the xvfb workaround on your ppa quickly?08:58
pittiseb128: hm, test suite iz good08:58
pittiseb128: oh, ppa, right!08:58
seb128pitti: ppa are great ;-)08:58
loolpitti: I'm not the RANDR stuff is a failure08:58
slangaseklool: :-)  I see that elisa-plugins-good recommends: gtreamer0.10-ffmpeg and gstreamer0.10-plugins-ugly, both of which are in universe; I think those need to be demoted to Suggests?08:59
=== dholbach_ is now known as dholbach
loolslangasek: Good point; I'll demote them for Ubuntu08:59
slangaseklool: (I'm trying to track down why ffmpeg stuff is being wrongly pulled onto the livefs; elisa itself isn't to blame for this, but I might as well mention it :)08:59
pittiseb128: uploaded to my ppa, crossing fingers09:00
loolslangasek: Hmm which verison of elisa-plugins-good are you looking at?09:01
slangaseklool: 0.3.5-2; is that not current?09:01
seb128no, currents didn't build09:01
loolNo, the current one doesn't build because a package needs promotion to main and the MIR is pending since 10 days09:01
slangasekah09:01
slangasekoh, well then09:01
slangasek:)09:01
loolI have in my TODO "* Find out who's processing MIR and ping them"09:02
StevenKlool: ubuntu-mir ; pitti and doko09:02
loolBut also "* write a MIR for python-cssutil"09:02
loolOf course the latter before the former  :-P09:02
seb128pitti: bah, the pygtk builds failed in your ppa too09:26
pittiah, same problem09:26
slangasekpitti: dunno if you saw, I followed up to the console-kit-daemon crasher bug; the log certainly doesn't tell me anything, and the crashes are still happening09:32
pittislangasek: ah, I hoped it would have a truncated log, or at least tell me at which precise point it crashes (when writing a session open or close log, or so)09:33
=== mdz_ is now known as mdz
loolI reproduce the pygtk FTBFS in pbuilder09:36
slangasekpitti: did there end up being any problems with langpack generation (bug #273489)? You suggested during the meeting to follow up on #-devel, not sure whether that's happened yet09:36
ubottuLaunchpad bug 273489 in rosetta "Remaining Intrepid template approvals" [Critical,Fix committed] https://launchpad.net/bugs/27348909:36
slytherinseb128: sorry to bug you again, but do you plan to update gst-plugins-base to latest prerelease? This is regarding DVD playback blocked with resindvd plugin.09:36
pittislangasek: I did followup with jtv; apparently the rosetta export crashes for ominous reasons, he is investigating09:37
slangasekok09:37
seb128slytherin: not likely before beta now, no09:38
loolpitti: Re: python-dateutil MIR; there's an embedded storm copy in elisa which is the code which relies on python-dateutil09:38
seb128ups09:38
loolI don't know how easy it would be for storm to move to python-tz; I'll try to ask them, but it's unlikely that it happens in time for intrepid09:38
seb128somewhat I manage to close xchat-gnome tabs while switching workspaces sometimes09:38
slytherinseb128: Ok. So should I try backporting the fix form upstream cvs? I will do that sometime tonight.09:39
seb128slytherin: if you want to, I'll try to update the version after beta09:39
loolOk, I think xvfb-run exits because it tries to kill Xvfb which already exited09:39
lool(the program is set -e and the kill clearly fails)09:40
* slytherin looks through intrepid schedule09:40
pittilool: so eliza actually uses the time zone db in python-dateutil?09:50
pittilool: I guess it's much easier in the end to make p-dateutil use the system tzdata than trying to convert storm09:50
loolpitti: elisa uses storm which uses dateutil for db dates I guess09:50
loolpitti: Got the same comment on #storm that it'd be simpler to fix python-dateutil09:51
shingarathere are no way to get list of all package with name of /package/version upstream/ubuntu version/ ?09:54
shingaraapt-cache send me the full version, no separate upstream version and ubuntu version09:55
* lool tries a pygtk build with -s -noreset09:55
loolCool, pygtk actually liked that09:59
loolslangasek, pitti: could you please look at pygtk 2.13.0-0ubuntu5 waiting for approval?  It fixes a FTBFS similar as the one on the buildds for me (in pbuilder here though)10:01
lool(Well it wasn't processed yet I guess)10:01
loolseb128: I think I pushed a fixed pygtk10:03
loolseb128: Are other packages likely affected?10:03
seb128lool: the change you mentionned was one of the workaround listed on #ubuntu-x the other day10:03
loolToo bad I had to search for it then10:04
loolseb128: How come it wasn't applied?10:04
seb128lool: well, gnome-python-extras, I opted for the libgl1-mesa-dri build-depends which was supposed to workaround that too, let's see if it builds after pygtk10:04
loolIt's not the same failure10:04
seb128ok so ignore my comment ;-)10:04
mvoshingara: there is a debian project for getting the upstream version based on debian/watch files10:04
shingarawhat project ?10:05
broonieddpo10:05
seb128lool: thanks for fixing it, there is still a xvfb bug though?10:06
wgrantshingara: Everything before the last - in a version should be the upstream version, or close to it.10:08
shingaraxserver-xorg-driver-all_1:7.3+10ubuntu1010:09
shingaraand this package is the exception?10:09
wgrantThere's no upstream version for that.10:09
wgrantIt's a native metapackage.10:09
loolseb128: Well it's a Xvfb design issue10:09
shingaraah10:09
loolRather xvfb-run10:09
loolseb128: xvfb-run <cmd> seems to assume only one client will connect, it seems10:10
seb128lool: which is not the case there?10:10
seb128lool: the issue you tracker was a different one indeed, the other one was a loop due to swrast_dri.so not being available10:11
loolseb128: I think I had to add bdeps to pygtk already to fix this IIRC10:11
lool  * Build-dep on xauth and xfonts-base as xvfb-run needs these and also bdep10:11
lool    on libgl1-mesa-dri for now until Xvfb can start without AIGLX support or10:11
lool    this dep is added to the package.10:11
loolpygtk 2.13.0-0ubuntu110:11
seb128ah right10:12
loolseb128: I think what happens is that "make check" starts multiple individual commands (one per test) and each test connects and disconnects from the DISPLAY10:12
seb128that one is a xvfb bug then ;-)10:12
loolWell, it's made to run a "client" not a command starting multiple clients10:12
loolAnd the flag to not close after the first client is the one I added10:13
loolIt might be that we were trying to run multiple tests but in fact were only running one!10:13
seb128lool: ok, so that was not what we discussed the other day, thanks for fixing this one ;-)10:13
loolI'm not too happy with xvfb-run in general, but here I think it's ok that we have to pass this special fla10:13
loolflag10:14
seb128right, it's just weird that things were working without that before10:14
loolWell TBH I'm not sure how they did10:14
loolPerhaps make check was completing really quickly because of the closed Xorg connection and kill had still something to kill10:15
loolNo idea  :-/10:15
seb128lool: did you upload the fixed version to intrepid?10:15
loolYes10:16
seb128thanks10:16
loolI pinged slangasek and pitti to unblock it10:16
loolI should have pushed to my ppa to make sure10:17
seb128the bug fix explanation makes sense and if you verified in pbuilder that should be good enough ;-)10:18
pittilool: rock, thank you10:22
loolpitti: I think we should act on the python-dateutil situation one way or the other; it seems the only doable solution is to fix python-dateutil to use tzdata; I don't want to keep elisa non-buildable and non-installable further, so could you either demote elisa to universe or promote python-dateutil to main until we sort it out?10:26
=== Ng_ is now known as Ng
loolI have no idea of the time budget to fix python-dateutil, but I have an idea of my time availability and I fear that nobody will step up before the intrepid release to fix it, so I prefer that we get at least some elisa testing, even if it's universe, or live with the tzdata copy in main10:27
Adri2000can I upload a main package directly to -proposed or should I wait for the ubuntu-sru ack?10:29
cjwatsonit's held in -proposed until the bug is approved anyway ...10:29
Adri2000ok, I guess I can upload then10:30
looljames_w: Congrats10:32
james_wthanks lool10:32
loolseb128, pitti: pygtk failed ot build in ppa and ubuntu; it's a new error again10:33
seb128gra10:33
pittibah, and all that just to fix an example script :/10:34
loolNow it's "Xvfb failed to start"; it does start with the same command-line in my pbuilder though10:35
loolxvfb-run -s -noreset /usr/bin/make -C build-2.5 check10:35
loolmake[1]: Entering directory `/tmp/buildd/pygtk-2.13.0/build-2.5'10:35
lool...10:35
loolxvfb-run -s -no-reset /usr/bin/make -C build-2.5 check10:35
loolXvfb failed to start10:35
loolmake: *** [build-2.5/build-stamp] Error 110:35
looldpkg-buildpackage: failure: debian/rules build gave error exit status 210:35
lool(first is my pbuilder, second it buildd)10:36
loolNow it might need some love from someone using sbuild10:36
slangaseklool: so the pygtk in the queue shouldn't be accepted?10:38
loolslangasek: No use to, it will ftbfs10:38
slangasek:/10:38
loolHmm I suspect XVFBARGS might get overwritten with -s10:38
loolNot sure how this affects Xvfb10:39
loolAnyone could do a test build in sbuild?  Or should I throw at my ppa?10:39
loolI'd like to change '-s -no-reset' to '-s "-no-reset -screen 0 640x480x8"'10:39
seb128lool: ppa will be faster to try10:40
jcristaulool: i'd be surprised if that was the problem10:40
looljcristau: Any idea what it could be?10:40
loolGRAH10:41
loolI typoed the one I uploaded10:41
loolto my ppa10:41
jcristaulool: i'm tempted to change the default ERRORFILE in xvfb-run...10:41
seb128oh, yeah, there is an extra "-"10:42
loolyeah10:42
pittilool: accepted pygtk, let's cross fingers10:42
looljcristau: Wow this would certainly help debugging indeed!10:43
pittilool: looking into -dateutil now10:48
loolStatus: Successfully built10:58
loolwoohoo10:58
loolSo the typo in my ppa upload was the only issue, sorry for the confusion10:58
looljcristau: And sorry for bothering :)10:58
loolThe second ppa upload with the proper flag name built fine10:59
pittilool: I think I fixed -dateutil10:59
loolpitti: woah10:59
loolpitti: Well thanks10:59
loolpitti: So I do owe you some beverage11:00
pittilool: at least I broke the test suite after removing the tarball, and it runs fine again with my fix11:00
xyzcould someone have a look at bug 23140711:01
ubottuLaunchpad bug 231407 in pulseaudio "pulseaudio causes restart- volume-restore.table file not found" [Undecided,Confirmed] https://launchpad.net/bugs/23140711:01
xyzit's still present in intrepid beta11:01
xyzno sound for VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller11:01
=== xyz is now known as xyz_
looljcristau: I kind of wonder whether this kill isn't racy in all cases: here we have multiple commands, so it's obvious why it might fail, but even for a single client, it's not impossible that Xvfb shuts down before the kill is reached11:02
=== xyz_ is now known as xxyz
jcristaulool: why would Xvfb exit?11:02
looljcristau: When X client disconnects11:03
jcristauonly if you pass -terminate11:03
looljcristau: I thought this was the default; I'm puzzled as to why -noreset helps if -terminate isn't the default11:04
looljcristau: Aha, the default is -reset11:05
jcristauthe default is to regen (shut down clients and screens, and re-init everything)11:06
looljcristau: I suspect the server restarts between commands11:06
loolHmm is this a good default11:06
looljcristau: Heh the xprint backend has dispatchExceptionAtReset = 011:07
loolSince 2006; don't know how to check earlier history11:08
looljcristau: https://bugs.freedesktop.org/show_bug.cgi?id=764 seems to be related to Xprt11:11
ubottuFreedesktop bug 764 in Server: Config: startup scripts "Xprt permanently resets itself after each client disconnect" [Critical,Resolved: fixed]11:11
looldd831c7a5c1b0c540a78350aadaeb34a8aa67395 in changelog11:11
loolThe rationale for xprint is slowness, and the fact that resources need to be configured again11:12
* jcristau pretends Xprt doesn't exist11:13
loolXpfrt!11:14
looljcristau: I can't come up with an use case of xvfb-run where one wants to reset the server for multiple clients though: the script inherently suggests you're running a single command to do some stuff11:16
loolSo even if the Xvfb default has some rationale behind it, xvfb-run could pass -noreset by default I think11:16
pittimvo: oh, you dropped the "remove landscape-client stub" update-manager code? IMHO this should still be present, we only install landscape-common by default11:36
pittimvo: maybe you can drop that change from 1:0.93.18 and reupload (same version number is ok)? I'll accept it afterwards, so that we'll get hte xorg driver transition in time for beta11:36
mvopitti: thanks, I can fix this after lunch11:37
mvosorry, there seems to have been some confusion about the right handling of this11:37
pittimvo: right, there was; this is the current approach now (isntall -common by default, but not -client)11:37
pittimvo: I rejected the current upload; please ping me after you uploaded the new version, for immediate processing; thanks! *hug*11:37
StevenKpitti: Can you have a look at linux-lpia?11:38
StevenKpitti: It is mainly so we can switch back to aufs11:38
pittiStevenK: accepted, doesn't really affect ubuntu desktops11:39
StevenKpitti: Thanks11:41
* persia tries harder to make the lpia alternate CD work for installing ubuntu desktops11:46
persials11:47
ogra /11:47
whykinghi12:07
whykinga package wants to install a dependency which has been renamed (libgsl0 became libgsl0ldbl), how could I fix that in the best way?12:15
whykingcreate an alias for that package?12:16
Mithrandirrebuild the package with the old dependenc.12:16
Mithrandir+y12:16
whykingMithrandir, how can I rebuild that package?12:17
whykingand where should I get the old dependency?12:17
whykingor maybe, is there a way to ignore that dependency? because it is already installed12:17
persiawhyking: You don't need the old dependency: rebuilding should pull the new dependency.12:17
Mithrandirhmm?  You have package foo that depends on libgsl0.  So you download the source, rebuild it using dpkg-buildpackage and install using dpkg.12:18
whykingcan't I just tell apt-get to ignore the broken dep?12:20
whykingsth like --ignore-missing12:20
Mithrandirbecause you don't have it installed?12:20
whykingMithrandir, I have12:21
whykingeverything is in place.. but he wants to install the old dependency.. the new one is installed12:21
Mithrandirno, you don't.  libgsl0ldbl and libgsl0 are two distinct libraries.12:21
whykingMithrandir, are they? so why was libgsl0 deleted?12:22
Mithrandirbecause it was superseded by libgsl0ldbl12:22
Mithrandirbut they are not completely compatible.12:22
Mithrandirso you need to rebuild any applications depending on libgsl012:22
whykingok, but it should work nonetheless then12:22
whykingmhh12:22
whykingI'd rather not :-/ its a huge source12:23
whykingno other way?12:23
persiawhyking: Rebuild anything depending on libgsl0ldbl with libgsl0, but that's the reverse of what everyone else will be doing.12:24
whykingpersia, alright.. I guess I'll have to wait for upstream to fix it then12:24
whykingthanks12:24
slangasekapachelogger: why is libksquirrel marked i386-only?12:38
geserslangasek: should packages in main have a -dbg or -dbgsym package or is it only nice to have?12:47
slangasekgeser: -dbgsym packages are autogenerated; -dbg packages get in the way of this more than anything, so I wouldn't call them nice to have at all12:48
siretartslangasek: they 'get in the way'?12:48
geserslangasek: libselinux has neither, and I wonder if it's important or only a wishlist bug12:48
slangaseksiretart: some packages are known to do things in the creation of their -dbg packages which breaks the -dbgsym extraction12:49
persiaslangasek: What about cases where -dbgsym autogeneration fails?12:49
sorenslangasek: From http://revu.ubuntuwire.com/details.py?package=libksquirrel: - Only build on i386 for now, have to talk to upstream about fixing amd64 build.12:49
cjwatson-dbg is only useful if the package needs a second pass to build useful debugging12:49
cjwatsonif it doesn't, then a request for -dbg is neither important not wishlist, it's invalid12:49
cjwatson(or wontfix I suppose)12:49
cjwatsons/not/nor/12:49
cjwatsonif -dbgsym autogeneration fails, it should probably be fixed :-) ask pitti12:49
* siretart wonders if he should make ffmpeg and xine stop building -dbg package in ubuntu12:50
cjwatsonthere's no need to introduce diffs to stop building -dbg packages12:50
slangasekmake them stop building -dbg packages in Debian :P12:50
cjwatsoncontrariwise, there's no need to put any effort into building them either12:50
geserthe problem is libselinux doesn't use debhelper so dh_strip isn't used and the trigger to build the -dbgsym doesn't get called12:50
slangasekgeser: ah, yes, heh12:50
cjwatsonexceptions are things like python modules which need a second pass12:50
cjwatsonit would be straightforward to call the dbgsym extractor, wouldn't it?12:51
siretartslangasek: I could, but I've found them rather useful. espc. for non-maintstream architectures.12:51
siretart'mainstream', even.12:51
geserit should be possible, if such change is deemed worth it12:51
cjwatsonit should be no harder than creating a separate -dbg package, and produces better results12:52
siretartslangasek: are there guidelines in debian when and when not to provide -dbg packages?12:52
slangaseksiretart: no, unfortunately12:52
siretart:(12:53
slangasekso we have awesomeness like -dbg packages for firewall tools12:53
slangaseksoren: hmm, and the revu page doesn't show the reason for the build failure... but ok, thanks12:53
pittire13:06
pittiwhat's up wrt. -dbgsym breakage?13:07
pittiseb128: looking into the camera bug now13:07
seb128pitti: thanks13:07
seb128pitti: what dbgsym breakage?13:08
pittidiscussed half an hour ago here, between slangasek, siretart, and cjwatson13:08
geserpitti: not a breakage, but only a question how important it is if a package in main has no -dbgsym (or -dbg) package13:08
geserpitti: see bug 27508213:08
ubottuLaunchpad bug 275082 in libselinux "no debug symbols package in intrepid" [Undecided,Confirmed] https://launchpad.net/bugs/27508213:08
pittigeser: oh; well, if it's a package which gets a lot of crash reports, we should fix it; otherwise I wouldn't waste too much time on it13:08
cjwatsonpitti: turns out it's a package that doesn't use debhelper. I guess it's fairly easy to call the helper by hand too13:09
slangasekseb128: hi, do you have any idea about the gstreamer0.10 build failure?13:09
siretartpitti: does ffmpeg/xine-lib break the apport retracer by providing -dbg packages? both are using debhelper13:09
seb128slangasek: oh, no, I wanted to ask lool or slomo about those13:09
pittiyes, it is: pkg_create_dbgsym debian/foo13:10
pittisiretart: ATM the retracer doesn't consider -dbg packages13:10
pittilool, seb128: yay, pygtk built everywhere13:11
siretartpitti: that didn't answer my question ;)13:11
pittisiretart: ok, then; to literally answer your question: "no" :)13:12
siretartexcellent :)13:12
siretartseb128: did you hear any news from the TB regarding my inquiry about ffmpeg?13:13
pittisiretart: "break" in the sense of "non-symbolic result if no -dbgsym is available": yes, "-dbg are merely available/present" -> no13:13
seb128siretart: no13:13
siretartseb128: FYI, an updated ffmpeg package is currently in debian NEW13:13
siretartpitti: okay, that means users have to retrace themselves. okay13:13
slangaseklool, slomo: ping?  Do you know what's up with the gstreamer.10 ftbfs?: http://launchpadlibrarian.net/17880819/buildlog_ubuntu-intrepid-i386.gstreamer0.10_0.10.20.2-1_FAILEDTOBUILD.txt.gz13:15
geserpitti: have you some time to help me on the fdi file for some smart card readers?13:24
pittigeser: oh, sure; what's the issue?13:25
slangasekpitti: do you think that the fdi file in 267682 is a right solution, and ready fo upload?13:25
pittislangasek: I think it's a reasonable workaround for intrepid, yes; it's not a long-term correct solution (we should clean up that entire mess in jaunty)13:26
pittislangasek: it was tested by a couple of thinkpad users now AFAICS13:27
slangasekpitti: ok.  Can you prepare the upload to add the fdi file to wherever is the appropriate place, or should I ask someone else about this?13:27
pittislangasek: I think the most correct place would be the -evdev driver, wrt. correct behaviour of backported packages (i. e. we should not ship it in hal)13:28
geserinspired by kirkland's work I started to write a similar file to grant access to smart card readers. I got it nearly working. I'm currently stuck at the point that it only works if I hardcode the device file name into the fdi file.13:28
pittislangasek: yes, I can prepare the upload13:28
slangasekpitti: ok, thanks13:28
gesersee http://paste.ubuntu.com/50012/ for my current fdi and policy file and the lshal output for the smart card reader13:28
pittigeser: you mean access to the raw device?13:28
pittigeser: do you know that a while ago StevenK already prepared this for all removable block devices?13:29
geserpitti: to e.g. /dev/bus/usb/001/00213:29
geserpitti: it's to finally close bug 57755 which got stuck as it used a new group (scard) for it in the udev rules13:30
ubottuLaunchpad bug 57755 in gnupg "Udev Rules for SmartCard Support" [Wishlist,Confirmed] https://launchpad.net/bugs/5775513:30
pittigeser: oh, right, I misunderstood what you meant with smartcards, nevermind13:31
geserpitti: does it matter that the smart card reader appears as a character device and not as a block device?13:31
pittigeser: yes, it does; I mixed it up with "SD card"13:32
geserI mean those to read a OpenGPG card13:33
pittigeser: right, I know now13:33
pittigeser: so, the tricky bit is to find out that a particular device is in fact an sd card reader13:34
geserwould it be possible to use the product id and vendor id? like in the proposed udev rules from that bug13:35
mdzasac: one-liner patch for you in ~mdz/network-manager/ubuntu.0.7/13:35
pittigeser: yes, that's always a possibility, if there's a reasonably small list13:37
pittigeser: some devices have a particular device or interface class, but if that's not the case, there's no other way than to use vendor/product ID lists13:37
mvopitti: update-manager uploaded13:37
pittigeser: btw, hal supports int_outof="0x001;0x002;0x003", that makes the rules shorter to write13:39
geserpitti: currently it's only a small list, 2 or 3 devices from SCM which gpg supports natively13:39
geserso the user needs access to the device file13:40
pittimvo: and accepted, thanks13:40
pittigeser: if the list gets longer, the fdi should probably be autogenerated during build, but for now, a static one seems ok to me13:40
pittigeser: allow_inactive should be false, though, otherwise several user sessions race for grabbing the device13:41
seb128Hobbsee: bouh13:41
pittigeser: otherwise your paste looks quite good to me13:42
Hobbseeseb128: i'm sorry?13:42
Hobbseeseb128: (oh, and re: the last ping, i figured it out, thanks)13:42
seb128Hobbsee: nice to mail about not testing uploads to upload an anjuta which can't built13:42
Hobbseeseb128: yeah, well.13:42
geserpitti: do you have an idea why it only works if I hardcode the device file into the fdi?13:43
seb128Hobbsee: we need the new anjuta version, huat is working on it13:43
geserif I use the copy-property line I get no acl for it13:43
Hobbseeseb128: at least i found about it pretty quickly.  And i'm not sure why no one in debian's reported the same problem yet.13:43
Hobbseeseb128: yes, so he said.13:43
seb128Hobbsee: anjuta 2.24 has been uploaded to debian13:44
Hobbseeseb128: yes, it has, and there's a grave bug about it.13:44
Hobbseeseb128: however, it's not passed to unstable yet, and i'm surprised that the unstable version hasn't been rebuilt at all - given that it should be uninstallable by now?13:45
Riddellmvo: could the upgrader be set to purge kdm-kde4 ?13:45
pittigeser: why do you copy it from the device's parent, and not from the device itself?13:45
seb128Hobbsee: I can't parse that13:45
pittigeser: the device you pasted already has linux.device_file, which seems to be the correct one?13:45
geserpitti: good question, I tried looking at how the other files do it13:46
pittigeser: drop the @info.parent:13:46
seb128Hobbsee: I'll fix anjuta, I'm talking regularly to huat about it for some days now13:46
geserpitti: still no acls (I've restarted hal and also issued a ck-launch-session)13:47
Hobbseeseb128: cool.  I've seen some action on the bug.13:48
Hobbseeoh, interesting.  according to debian packages, libgdl-gnome-1-0 still exists - but an old version.13:48
slangasekit's uninstallable and NBS13:49
* slangasek sharpens the axe while he waits for python-gnome2-extras to build13:49
seb128Hobbsee: right, nbs is not cleaned if there is still some packages depending on the binaries13:50
geserpitti: is /usr/share/hal/fdi/policy/10osvendor/ the correct location for my fdi file?13:50
Hobbseeseb128: in debian, it appears.  It's gone in ubuntu, apparently.13:50
seb128slangasek: I kicked the builds after pygtk built, now you might want to ask pitti to score higher those13:51
pittiprio bumped to 500013:51
seb128pitti: danke13:51
* Hobbsee want's pitti's version of buildd.py.13:51
pittigeser: yes, looks good13:51
asacmdz: committed (rev2902) thx13:52
pittiHobbsee: hm, you are right; it doesn't actually *work*13:52
Hobbseepitti: good.  so i'm not going mad!13:52
* Hobbsee sighs at seb. I get build failure mails for a reason.13:54
HobbseeInstall failures, however....13:54
Hobbseeah well.13:54
mdzpitti: I was looking at network-manager crashes, and noticed there were several which have been retraced but are still marked private.  is it a manual process to make them public after retracing?13:59
pittimdz: yes, it is; until someone inspected them, we cannot guarantee that there are no sensitive information in the stack trace; also, we just generally keep them private, in order to not clutter the bug mail recipients so much14:00
pittislangasek: I applied it in hal in the end; rationale in bug updated, and uploaded14:00
slangasekpitti: great, thanks14:01
pittislangasek: want to review, or shall I ack myself?14:01
mvoRiddell: sure, purge, not remove? I put that into bzr14:02
slangasekpitti: having already tested the fdi file and trusting that you know better than I where it needs to go in the package, I'm ok with you acking yourself if you don't think you need another pair of eyes14:03
pittislangasek: I'm reasonably sure, but best would be to test it again with the actual .deb from the repos14:03
pitti(I don't have a thinkpad here)14:03
* slangasek nods14:04
james_whey ema14:05
emahey james_w14:06
emajames_w: congrats for becoming a MOTU :)14:06
james_wthanks ema. How are you?14:06
emaI'm fine, but very busy with work any uni unfortunately14:07
geserpitti: found the problem: it's "copy_property" and not "copy-property" and I had to use @info.parent:linux.device_file14:07
geserpitti: it works now :)14:08
pittigeser: still curious, since the hal device you pasted had both the vendor/product IDs and the device file; but if it's conceptually correct to use the parent's, sure14:08
geserpitti: the next question would be, which is the best package to include the fdi (and policy) file as both gnupg and gnupg2 can use it (perhaps also libccid)14:09
pittigeser: is there a smartcard library which both use/14:10
pitti?14:10
geserpitti: no, both gnupg and gnupg2 support it natively, they don't need any special lib for it14:11
pittigeser: I guess then we should put it in hal; it has become the dumping ground for all sorts of stuff already, but *shrug*14:11
pittigeser: it should be integrated into the existing device access fdi/policy then, maybe upstream will even tak eit14:12
pittitake it14:12
geserpitti: I'll prepare then a debdiff and let you know for review14:13
pittigeser: cool, thanks (NB that I just uploaded a hal, thus bzr is newer than apt-get source)14:14
seb128re14:15
seb128lool: so gnome-python-extras fails the same way than pygtk now14:15
pittiwb seb12814:15
sonecahelo folks, i am working on Pidgin. There is an issue on Blocked users. Even when the contact is blocked, he also can send messages to user, and vice-versa. So, i want to help the team, making a patch to this issue, in libpurple and pidgin. Anyone else is working with this?14:27
stefanlsdsoneca: is it an ubuntu specific problem, or rather a problem with pidgin?14:29
TheMusocjwatson: I had a look at the Ubuntustudio seeds today, following the steps for tasksel that you outlined last Friday, and got no errors at all. This was on intrepid, with intrepid's version of bzr.14:29
sonecait's a pidgin problem. Sorry post in this channel14:29
sonecaI've posted on pidgin channel now14:30
stefanlsdsoneca: your best bet will be to work with upstream.  Try #pidgin  :)14:30
sonecathanks, it's an control-V issue. Copied from other channel and pasted in the wrong place ;)14:31
loolseb128: Hmm ok, we don't have the xvfb-run call in pkg-gnome so I didn't find it14:38
seb128lool: right, we didn't sync this one for a while14:38
loolseb128: Would have been nice to send that part to Debian14:38
loolIt's there since sep 200714:38
Riddellmvo: actually I'm not sure about that purge, it shares file with kdm in intrepid which we don't want removed14:40
looldpatch...14:40
seb128lool: yes, we didn't sync this cycle because the package has been splitted in debian and has dbg variants in ubuntu and the sync is not trivial and I've been too busy to do it and nobody else picked on the job14:42
loolI pushed a similar fix (adding -noreset Xvfb flag) for gnome-python-extra to my ppa and intrepid14:43
seb128lool: thanks!14:43
pittitedg1: good morning14:44
ograseb128, do you know if there is a way to preseed timed-login from d-i for gdm ? (i know there is for autologin, but that doesnt help if a user logs out)14:45
seb128no clue14:45
pittiseb128: so, do you agree about the "do nothing" approach for bug 274146? I don't see any correct approach to that14:45
ubottuLaunchpad bug 274146 in gnome-session "Has not yet replaced the existing log out applet" [High,New] https://launchpad.net/bugs/27414614:45
seb128pitti: I'm not happy about that but I prefer to not do anything than to do something broken14:46
pittiseb128: me too14:46
tedg1Morning pitti14:47
pittiseb128: ok, then AFAICS desktop team is down to bug 274140 (tedg1), bug 258083 (me), and bug 274085 (unassigned); do you see anything else critical for beta?14:47
ubottuLaunchpad bug 274140 in fast-user-switch-applet "Visability of Suspend and Hibernate doesn't match gnome-session's dialogs" [High,In progress] https://launchpad.net/bugs/27414014:47
ubottuLaunchpad bug 258083 in f-spot "F-Spot - Error connecting to camera.  "Could not lock the device"" [Medium,Confirmed] https://launchpad.net/bugs/25808314:47
ubottuLaunchpad bug 274085 in ekiga "Please update Ekiga to 3.00" [Wishlist,Triaged] https://launchpad.net/bugs/27408514:47
seb128pitti: Scott opened the bug, let's stay on the "do nothing" for now and wait for him to comment if he disagrees14:47
pittitedg1: how is that going, btw? (fusa suspend/resume), need any help?14:48
pittitedg1: we need to get the fixes in today in order to get the release out in time14:48
seb128Hobbsee: replying here to you gdl question, that's an upstream change14:48
seb128Hobbsee: and why I synced the new version, because that's a GNOME 2.24 tarball14:49
seb128Hobbsee: what is still using it in intrepid?14:49
mterrysuperm1, persia: I attached a debdiff to bug 269540 to fix the issue with the BT wizard in bluez-gnome 0.2814:49
ubottuLaunchpad bug 269540 in bluez-gnome "Add bluetooth wizard" [Undecided,New] https://launchpad.net/bugs/26954014:49
tedg1pitti: In testing.  Is there a particular time you need them?14:50
persiamterry: Does it work with keyboards on intrepid?14:50
pittitedg1: ah, good to hear; no, just "today" would be good14:50
mvoRiddell: hm, ok. let me know when you have decided what to do with it14:50
mterrypersia: I don't have a keyboard to test.  But what I remember you saying is that they were broken in 0.25 anyway?  This wouldn't fix that14:51
Hobbseeseb128: it *was* anjuta, but that became uninstallable, as the binary was pulled.14:51
persiamterry: Oh well.  Thanks for that.  If we don't move to 4.x, it's probably worth applying.14:51
seb128Hobbsee: yes, anjuta has to be uploaded to 2.24 too, but to update anjuta we had to upload gdl first because anjuta 2.24 depends on the new gdl14:51
Hobbseeseb128: i can understand that the new version got synced, but i would have expected the old version of the obsolete binary to stay, and not automatically vanish, but show up on the NBS lists?14:51
tedg1pitti: Okay, I'll finish catching up on e-mail from the weekend then :)14:51
seb128Hobbsee: the lib didn't vanish, it's just not installable because it doesn't match the libgdl-1-common current version14:53
Hobbseeseb128: ah.  I must have misread it, in the general churn of trying to make things installable again.  My error.14:53
seb128no problem, sorry about the installability issue late in the cycle14:54
Hobbseeseb128: hopefully it'll be fixed soon :)14:54
seb128today for sure14:54
cjwatsonTheMuso: did you use the current revision, or the one before I worked around the problem?14:54
loolseb128: gpe successfully built, can you accept?15:01
lool(in my ppa)15:01
loolhttps://edge.launchpad.net/~lool/+archive/+build/72604515:01
seb128pitti: can you?15:01
seb128pitti: gnome-python-extras in intrepid fixes the build correctly thanks to lool15:01
pittiseb128: can what?15:02
seb128lool: is you accent circonflexe broken too in intrepid?15:02
seb128pitti: accept -g-p-e15:02
pittiI already accepted g-p-e from unapproved15:02
seb128ah ok15:02
seb128thanks15:02
loolseb128: Rebooting to make sure, but it worked in xterm15:03
loolpitti: ty15:03
Riddellmvo: if it's going to remove files even though they now belong to kdm then it shouldn't br purged15:04
amikropCan I tell distutils not to place my data_files in /usr/foo but in /etc/foo? The docs do not refer anything about it.15:18
pittiamikrop: just set the destination dir to an absolute path15:19
amikroppitti: Alright, thank you. :-)15:19
pittiamikrop: 'share/foo' will land in prefix, '/etc/foo' will be absolute15:20
amikropthanks ;)15:20
Hobbseeamikrop: any *particular* reason you stuck that in 2 channels, simultaneously?15:21
loolseb128: Yeah, ê is broken in gtk+15:28
loolnot in xterm though15:28
* ogra ands lool a ö ... just cut out the right side, make a connection between the dots and it *nearly* looks the same 15:34
* Hobbsee hands ogra an h15:34
ograheh15:34
Hobbsee:)15:34
ograHobbsee, i'm speaking to french people ... the h is builtin :P15:35
* ogra hides15:35
Hobbseeogra: riiiiight...15:35
apacheloggerslangasek: FTBFS on anything but i386 IIRC15:41
persiaapachelogger: even lpia?15:43
apacheloggerpersia: can't remember TBH, it isn't of much use without ksquirrel anyway15:45
loologra: Hans hat ein hohes Haus im Hamburger Haffen15:45
loolThe h is for Germans15:45
ograHa Ha :)15:45
loolWe have oi ou oï15:45
mvolool: alter! du kennst hans :) ?15:45
apacheloggerOo15:46
apachelogger...germans...15:46
Koonmvo: aptitude recommends libparse-debianchangelog-perl (which results now in a set of extra packages being included in standard seed). As far as I can tell it doesn't use it at all... am I missing something obvious ?15:46
mvoKoon: let me check15:47
persiaapachelogger: OK.  I think I nearly have the alternate CDs working for lpia, and suspect that as more of the shiny little toys come out, it may be an interesting target for your stuff, although this is probably not a sane target for intrepid at this point.15:47
mvoKoon: it will use it for its internal changelog display widget to make version numbers more pretty, but it should work just fine without it15:48
Koonmvo: hm. then I missed where in the code it calls it :)15:49
mvoKoon: let me re-check, maybe it got removed again15:49
Koon mvo: got it15:50
Koonmvo: calls "parsechangelog" without calling any perl. Sorry for thenoise15:51
mvoKoon: no problem15:51
Koonwas fooled into thinking libparse-debianchangelog-perl would only contain perl modules :)15:51
mvoKoon: it should work without it afaics15:51
mvoKoon: :)15:52
loolmvo: Nah klar kenn ich him, und auch Fischer Fritz and seine frische Fische  :-P15:52
mvolol15:52
loolseb128: So what's that ê regression ?  gtk+ with latin1 layouts again?15:53
jcristaulool: s/him/ihn/?15:53
loolgeez15:53
seb128lool: no idea, it's not a multiple layout thing I've only an french one configured15:53
loolI just spoke to my german grandmother and I kept mixing english and german15:53
loolis hardz15:53
loolseb128: Me too15:54
loolseb128: But that's the closest thing which came to my mind15:54
mrooneyis there a guide for making patches in the Ubuntu kosher way? I tried diff -crB but it isn't giving me something comparable to the original patch I was working with15:55
apacheloggerpersia: yes, since KDE is doing a lot of work towards MIDs, this might be a good target for jaunty(+1)15:55
persiaapachelogger: I suspect you'll be able to get Kubuntu/lpia working for jaunty.  Whether you can get a kubuntu-mobile or kubuntu-mid flavour by then probably depends a lot more on upstream.15:56
ogracjwatson, can i assume that if i simply add "buildlive ubuntu-mobile ;for-project ubuntu-mobile build-image-set" to the crontab on antimony it will just DTRT ? (assuming there is a recent livecd-rootfs that knows abotu ubuntu-mobile)15:56
persiaGiven device availability, I'd recommend chasing kubuntu-mobile before kubuntu-mid.15:56
apacheloggerpersia: I think all the core KDE packages already build on lpia, NCommander did quite some work in this direction.15:57
persiaapachelogger: In that case, you might try to see if a kubuntu-lpia image works.  I'd recommend waiting for ubiquity 0.10.1, but I think that's the last piece you need.15:59
ogracjwatson, oh, i see build-image-set nedds to be taught about it15:59
apacheloggerpersia: ok, thanks :)15:59
cjwatsonogra: check with StevenK, as he's been working on fixing that stuff up16:03
geserpitti: can you review and sponsor the hal debdiff in bug 57755?16:03
ubottuLaunchpad bug 57755 in hal "Udev Rules for SmartCard Support" [Wishlist,Confirmed] https://launchpad.net/bugs/5775516:03
pittigeser: not before the beta release (unless you get slangasek's permission); can you please assign it to me?16:03
ogracjwatson, well, i try to wrap my head around it first16:03
ogra(beyond the fact thats 1am for him)16:04
StevenKogra: Nope, it won't16:04
StevenKcjwatson: There's a bug to remove multiseat -- it contains a udeb, is there anything I need worry about wrt d-i that uses it?16:05
geserpitti: assigned, it's not that important that it can't wait after beta release16:05
ograStevenK, yeah, i see buildlive is the first thing needing to learn about ubuntu-mobile ... then build-image-set, then build-mobile and in the end build-mobile-img, did i miss something ?16:05
geserpitti: and thanks for your help with it16:05
pittigeser: thanks16:06
StevenKogra: publish-mobile16:06
ograyeah and purge ...16:06
ograi wanted to get something building forst before publishng or purging :)16:06
ogra*first even16:07
cjwatsonStevenK: multiseat> no16:09
bdmurray\sh: It looks like some stuff is still missing for bug 271550.16:29
ubottuLaunchpad bug 271550 in ia32-libs "ia32-libs missing libQtDBus, others?" [Critical,Fix released] https://launchpad.net/bugs/27155016:29
bdmurray\sh: I think they are libqtgui4, libqtcore4 and libqt4-xml16:30
=== superm1 is now known as superm1|away
sistpoty|workpitti: Hobbsee already rejected gnome-iconedit ;) (and yes, it was deleted on the very same day where I later fixed it... .not some months ago ;)16:48
Keybuk?! Sorry, the program "bzr" closed unexpectedly16:48
Keybukdamned right it was unexpected, I wasn't _running_ bzr!16:49
YokoZarI uploaded wine-gecko a while ago, and I forgot to mention that it needs to go into multiverse and not universe16:49
pittiKeybuk: but you should!16:50
pittisistpoty|work: ah, ok16:50
Keybukpitti: I don't normally run it while reading e-mail ;)16:51
NafalloKeybuk: you don't have your mails in bzr? :-O16:52
Keybukno16:52
=== asac_ is now known as asac
ScottKKeybuk: Last week while I was offline you said something to me about changing a 3 year old bug from fix released to incomplete.  I've looked back over my bugmail and can't find anything that looks relevant.  If you still recall the issue and can point me at the bug, I'll be glad to have a look and clarify the situation.16:55
KeybukI commented on it, maybe you hadn't subscribed?16:56
KeybukI don't have the bug# to hand16:56
ScottKPerhaps.  I don't recall doing that, but I was totally offline for a week, so my brain pretty well purged that kind of stuff.  If you figure it out, let me know.16:57
=== robbiew is now known as robbiew-away
Keybuknp16:58
ion_!away17:00
ubottuYou should avoid noisy away messages in a busy channel like #ubuntu, or other Ubuntu channels; it causes excessive scrolling which is unfair to new users. Use the command "/away <reason>" to set your client away silently.  See also «/msg ubottu Guidelines»17:00
=== superm1|away is now known as superm1
cjwatsoncody-somerville: FYI I'm working on fixing up the Xubuntu powerpc CD building problem17:07
cjwatsonbetter get it sorted before beta17:07
cody-somervillecjwatson, thank you17:11
=== davmor2 is now known as davmor2_away
keesdoko, Keybuk: when doing an install of glibc from apt, I an error (this didn't happen when I installed it locally with dpkg)17:23
keesinit:io.c:724: Assertion failed in nih_io_message_send: message != NULL17:23
=== njpatel is now known as njpatel_away
Keybukkees: it doesn't fail though, right?17:25
keesKeybuk: doesn't seem to, no.  and init is running afterwards... is this some "hey, reload" msg being sent to upstart?17:26
Keybukyeah17:26
Keybukwhich obviously has no reply, since upstart drops the connection to telinit ;)17:26
keesheh17:26
keesI can reproduce it every time with   sudo apt-get --reinstall install libc617:27
Keybukyou can reproduce it with just "telinit u"17:27
keesyes17:27
keesah, this is a recent change to upstart.  whew.  I couldn't even begin to imagine how my glibc patch would have caused it17:27
Keybukwell17:27
Keybukit's a bug in glibc's postinst that after a security upgrade, it never restarted upstart17:28
* kees nods17:28
Keybukso upstart would still have the old libc open on the root filesystem17:28
Keybukso you couldn't remount that ro17:28
kees"u" is reload?  (not in the manpage)17:28
Keybukso I monkey-patched "init u" support in the quickest way I could to paper over that17:28
keesKeybuk: so upstart had been ignoring "u" before now?17:33
Keybukkees: err, well, it wasn't implemented17:33
Keybukit would have replied "unknown runlevel" or something17:34
=== robbiew-away is now known as robbiew
keesah-ha found it17:36
keeslibc.postinst:(init u ; sleep 1)17:36
keessleep 1.  very exacting.  ;)17:36
Keybukheh17:37
KeybukI like the way it's done in a sub-shell17:37
keesso, why didn't the "unknown runlevel" stderr show up prior to now?17:38
Keybukno idea17:38
Keybukactually, I may have been silently ignoring u17:39
keesyeah, looking at your patch, it seems so17:39
Keybuki silently ignore anything I vaguely saw in a manpage but couldn't be bothered to implement at the time ;)17:39
keesheh17:39
keesso the fix is to exit(0) instead of break ?17:39
Keybukyeah17:39
Keybuk"But that's a critical feature, you can't remove that!"17:40
Keybuk"How long have you been using Ubuntu?"17:40
Keybuk"Every release since warty!"17:40
Keybuk"So you haven't had that critical feature for the last two years, and you haven't noticed until I tell you? :p"17:40
keesheheh17:41
sabdflapachelogger: yowser, good stuff on the 5-a-day front17:41
keesKeybuk: oooh, I'll bet this not-ro-/ bug is what kept corrupting my XFS root partitions so many moons ago17:43
kees(well, really that's an XFS bug, but this was triggering it)17:43
Keybukno, that was just XFS17:43
keesheh17:43
KeybukXFS likes to trash filesystems every now and then17:43
sebnersabdfl: but afaik he got rejected as core-dev O_o17:44
Keybukit's like a dog weeing on the carpet17:44
Keybukit's just letting you know it's still there17:44
keesKeybuk: btw, the "u" crash was filed as 27595817:44
sebnerKeybuk: no we know how jaunty will boot faster ^^17:45
Keybuksebner: I'm going to comment out the entire boot sequence17:45
Keybukand only uncomment bits people complain about it17:45
keesKeybuk: okay, so you're uploading a fixed upstart for beta?17:45
sebnerKeybuk: hrhr. bad boy :D17:45
Keybukkees: it's not really beta freeze critical?17:46
sabdflsebner: i'm sure just deferred, not denied :-)17:46
Keybukit's a scary warning17:46
sabdflcrimsun: also, amazing work there17:46
keesKeybuk: I guess not, but it sure is alarming17:46
Keybukkees: I could replace it with a less scary warning17:46
Keybuk"GLIBC DETECTED!"17:46
sebnersabdfl: hopefully. he just ROCKS :D17:46
keesKeybuk: "YOUR MACHINE HAS BEEN ERASED!  just kidding"17:47
Keybukkees: I still want to write something that detects glibc, and outputs "*** glibc detected ***" to let you know17:47
keeshahaha17:48
keesmake sure it writes it to /dev/tty instead of stderr so you have to dig through the source to figure out how to redirect it.17:48
Keybuk:)17:48
=== davmor2_away is now known as davmor2
ion_Hehe17:50
bddebianlamont: ping? (about palo)18:21
lamontwhich freedom-hating aspect thereof?18:22
pittitedg1: need to leave for Taekwondo; can you please ask one of the US folks for sponsoring the fusa fix?18:27
pittitedg1: (seems seb128 is already out as well)18:27
bddebianlamont: Heh, just curious if you were going to fix it in Debian?  It appears you fixed in in Ubuntu? (BTS #464262)18:28
tedg1pitti: Yes.18:28
apacheloggersabdfl: hehe, doing my best ;-)18:28
lamontbddebian: I think someone fixed it in ubuntu18:29
lamontI've been ignoring it18:29
lamontthe assertion was that it was broken glibc headers somewhere18:29
bddebianOh, slangasek uploaded the fix in Ubuntu18:29
sebnerapachelogger: hehe \o/18:30
lamontlast time I mentioned it in the parisc channel, there were other ideas about fixing it, so I left it in their hands.18:30
lamontOTOH, dunno18:30
apacheloggersebner: btw, when do you apply for MOTU?18:33
sebnerapachelogger: not in this month and not in the next one. why?18:34
apacheloggersebner: just wanted to know, I am currently at 698 unread mails, and KDE 4.1.2 packaging is still gonna take a while, so I will probably have one month of lag in reading mails ;-)18:36
sebnerapachelogger: oh. didn't know that you really consider to comment. otherwise I'd let you know when I send the mail18:37
apacheloggersebner: commenting might be time consuming, but for you I consider taking the effort :P18:38
* sebner feeds apachelogger with cookies :P18:39
apachelogger(:18:39
sebnerapachelogger: so it only make sense if it's a postive comment :P18:39
apacheloggersebner: will be a short commen then :P18:39
apachelogger+t18:39
geserapachelogger: you're cheap :)18:40
sebnerapachelogger: perfect. you save time and I have a postive comment :P18:40
apacheloggergeser: :P18:40
sebnergeser: I still have a secret weapon :D18:41
* sebner gives apachelogger a captain :D18:41
apacheloggerhm18:42
apacheloggersebner: KDE release packaging > captain18:42
sebnerapachelogger: gnome > kde :P18:43
sebnerapachelogger: and think of your poor padawans. R.I.P :P18:43
apacheloggersebner: mac > gnome :P18:43
sebnerapachelogger: gnu > mac :P18:43
* apachelogger mentions darwin and hides18:44
* sebner slaps apachelogger with hurd :P18:44
jdongapachelogger: lol I've seen someone running more or less Darwin with GNU CLI stuff onboard18:47
jdongapachelogger: I guess just taking "think different" a step or 10 too far.18:48
apacheloggerhehe18:48
jdongoh the things people go through to look cool.18:48
ahasenackdoes anybody know what causes this? http://pastebin.ubuntu.com/52169/18:53
ahasenacksome post calling debconf again?18:53
ahasenackthat's on intrepid, btw18:54
ahasenack(if it matters)18:54
mvoahasenack: is that on your system?18:57
mvoahasenack: or in a VM?18:57
ahasenackmvo: no, it was reported by somone in launchpad18:57
ahasenackmvo: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/27561518:58
ubottuLaunchpad bug 275615 in landscape-client "package landscape-common 1.0.21.1-0ubuntu1 failed to install/upgrade: subprocess post-installation script returned error exit status 1" [Undecided,New]18:58
mvoahasenack: aha, ok. I have seen reports with that as well, but I haven't had anything conclusive yet, it might be cause by someone running dpkg-reconfigure something (ee.g. console-setup) in another window18:59
ahasenackmvo: ok, I see18:59
ahasenackmvo: thanks!19:00
infinitymvo: Doesn't dpkg-reconfigure check the dpkg lockfile?19:01
infinitymvo: You'd think it would...19:01
infinitymvo: s/check/check, touch, and remove/19:01
mvoinfinity: indeed, but it seems like it does not, dpkg-reconfigure console-setup (and leaving it) and then dpkg -i /tmp/foo.deb does work, just debconf does not19:02
mvoinfinity: I guess that would be the bug then :)19:03
infinitymvo: Yeah, given that dpkg-reconfigure is executing maintainer scripts, it's effectively a dpkg-like process, so should definitely lock.19:06
infinitymvo: Of course, as soon as you change it to lock, you'll discover some (utterly broken, IMO) package that uses dpkg-reconfigure in it's own maintainer scripts. :P19:07
infinitymvo: (Hypothetical, but I'll give good odds that SOMEONE's done it)19:07
mvoinfinity: heh :) let them burn!19:07
cjwatsoninfinity: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=46935419:08
ubottuDebian bug 469354 in debconf "debconf: dpkg-reconfigure should acquire dpkg lock" [Normal,Open]19:08
stgraberAm I the only one with passwd behaving strangely ?19:10
stgraberWhen changing my password and not entering the same password twice, it tells me:19:11
stgraberSorry, passwords do not match19:11
stgraberpasswd: password updated successfully19:11
stgraberand returns 019:11
slangasekstgraber: there's a bug on pam about that19:12
slangasekI need to look at it for intrepid, but not before beta19:13
stgraberok19:13
james_wbug 27223219:14
ubottuLaunchpad bug 272232 in pam "passwd - passwords do not match but updated successfully" [Undecided,Confirmed] https://launchpad.net/bugs/27223219:14
slytherinany archive admin around?19:29
=== DrKranz is now known as DktrKranz
infinityslytherin: Several.19:33
slytherincan anyone please fix the bug #272866? I am waiting for it to work on rdepends and reverse-build-depends19:34
ubottuLaunchpad bug 272866 in javassist "Please move package to universe" [Undecided,Confirmed] https://launchpad.net/bugs/27286619:34
=== smarter_ is now known as smarter
=== mterry is now known as mterry_afk
tedg1Can someone sponsor a couple of packages to main for me please?  In my PPA, gnome-power-manager_2.24.0-0ubuntu3 and fast-user-switch-applet_2.24.0-0ubuntu2.  http://launchpad.net/~ted-gould/+archive20:13
brycetedg1: have you gotten a beta-freeze exception?20:18
tedg1bryce: Well one is a beta-freeze milestone thingy.  Is that an exception?20:18
slytherintedg1: Why not add debdiff to the bugs that are fixed by these packages?20:19
tedg1slytherin: Because the person that would have to turn them into a package is me :)20:20
slytherintedg1: I don't understand. You are asking for sponsorship. Do you expect people to take package form your PPA and sponsor it?20:20
tedg1slytherin: I thought they could copy it?20:21
tedg1Isn't that one of the new LP features?20:21
slytherintedg1: Could or could not, that is not how it works.20:21
slytherintedg1: You have to add debdiff to the bug. Then subscribe ubuntu-main-sponsors to the bug. Someone will take that debdiff, verify and then sponsor.20:22
ograbryce, tjaalton, is there any way for me to not have to install the evtouch .fdi files into /etc/hal/fdi/policy ? if i put them into /usr/share/hal/fdi/policy/10osvendor they seem to be overwritten by mouse settings ... but it somehow feels wrong to put them into /etc20:27
=== fargiolas|afk is now known as fargiolas
slangasektedg1: as far as ppa copying is concerned, I didn't think that was going to (initially?) be available to anyone but archive admins20:30
brycetedg1: yeah if I were to sponsor a package from a ppa, I'd normally convert it into a debdiff20:32
bryceeven with ppa copying, i'd still want to see the debdiff for review purposes20:32
bryceogra, could it go into hal itself?  we've put a few fdi files into there so far20:33
cody-somervilleLaunchpad generates the diff automatically20:33
ograbryce, upstream nearly flamed me when i asked ...20:33
ogradanny kukawa doesnt want driver specific fdi'd in hal20:34
bryceogra, we've generally worked with pitti on these sorts of issues20:34
ogra*fdi's20:34
ograwell, you need the driver package installed anyway, so i dont think the attempt is to wrong20:34
ograthe only prob i have atm is the forced install location20:34
slangasekapachelogger: so I had to fix a cross-arch libksquirrel FTBFS, and along the way I've fixed the amd64 build failure too since that's what I have to hand as a dev env; I haven't changed the architecture: field, though20:34
superm1TheMuso, something I didn't see mentioned in that pulseaudio bug, check and see whether users were setting up automatic login and how that affects the pulseaudio daemon that gets spawned (since automatic login is easy to setup now in oem-config or ubiquity)20:35
ograi'm not sure why they get ignored in /usr/share either20:35
slangaseklool, slomo_: gar, this gstreamer0.10 build failure is evil, it never fails if I run the command by hand :(20:35
bryceslangasek: friday seb128 mentioned an xvfb fbs issue, that I offered to look into today, yet I can't find a mention of it in launchpad.  Do you know more about what the issue is and where I could find an error log or bug report?20:36
bryce(I've been hoping seb128 would pop online but I guess he's done for the day)20:36
bryceI'm assuming it's something that gets triggered during a 'make test' kind of a thing in some package(s)20:37
slangasekbryce: last-but-one builds of pygtk or gnome-python-extras show the error; it has to do with xvfb -noreset or something, it was discussed extensively in scrollback here this morning (around 4am or so, IIRC)20:37
slangasekI don't know if it's still regarded as an Xvfb bug; the package builds are fixed20:38
slangasektedg1: oh, bug #274681 fixed, awesome20:40
ubottuLaunchpad bug 274681 in gnome-power-manager "g-p-m is reporting 2 separate voltage/power levels" [High,Fix committed] https://launchpad.net/bugs/27468120:40
tedg1slangasek: Yes, except that the reason it was broken was entirely my fault :)20:41
slangaseksure, it's still awesome that it's fixed before I had a chance to report it :-)20:41
bryceslangasek: hrm, wonder if I should spend time investigating or not20:41
slangasekbryce: I vote "no" for now :)20:41
brycewish someone had filed a bug on it so it'd be easier to tell20:42
slangasekbryce: the immediate issue was the build failure, which I understand has been fixed without having to drop the test suite out20:43
bryceslangasek: ok, looks like look did this to fix the build failure:20:47
brycepygtk (2.13.0-0ubuntu5) intrepid; urgency=low20:47
bryce  * Pass no -s -no-reset to xvfb-run to prevent Xfvb from exiting when the20:47
bryce    last client disconnects and hence allow xvfb-run to kill it.20:47
bryce -- Loic Minier <lool@dooz.org>  Mon, 29 Sep 2008 10:53:49 +020020:47
Edulixhi20:53
EdulixI've noticed that NEtworkManager leaks memory in 8.04, is that fixed in 8.10 ?20:53
bryceslangasek: ok you're right.  It looks like the issue was that xvfb by design assumes a single client, and exits after that client exits.  According to lool's analysis, the pygtk testsuite was attempting to use a single xvfb instance with multiple clients (individual tests), which was causing the breakage.  Having to include the -no-reset flag appears to be a correct fix and not just a workaround20:57
=== fargiola` is now known as fargiolas
=== mterry_afk is now known as mterry
slangasekcalc: gstreamer0.10-plugins-good (+base, which it depends on) gives you all the codecs and formats that are supported by everything in main21:11
slangasekcalc: if OOo users need something outside that set, well, there are Larger Reasons why we don't install them by default :/21:11
=== fargiolas is now known as fargiolas|afk
slangasek(and no, it's not just theora/vorbis - at least flac, qtdemux, speex are there)21:13
slangasektedg1: fwiw, fusa can't do a source build after a binary build, it leaves generated .png files around21:14
slangasek(clean target should be fixed)21:14
tedg1slangasek: The uudecoded ones?21:15
slangasekyes21:15
slangasekthey should be removed in clean21:15
* tedg1 is a little curious what make is going to do with that. Since they're a data tag, I'm curious if they'll be built to be deleted....21:19
slangasekif you mean automake 'DATA', it shouldn't21:22
tedg1Yeah, it doesn't cool.21:23
keesslangasek: should I upload a fix for 273761 before beta?21:38
slangasekkees: sorry, I'm on my way out the door so can't look that up right now; but it doesn't hurt to upload and have it sit in the queue, regardless21:40
slangasek(unless it hurts you to do the work, I guess :)21:41
keesslangasek: no, the fix is trivial. when discussing it with Keybuk earlier, it seemed like it wasn't important to fix (amd64 handles it more gracefully).  but it seems that i386 segv's triggering apport.  (38 dups in 6 days)21:42
sbeattiekees: you verified it addresses the issue for i386?21:42
keessbeattie: waiting for the compile to finish, but it fixes it for amd64.  a few more moments...21:42
keessbeattie: confirmed to fix it on i386.21:43
keesI have no idea where Keybuk keeps the actual _code_ for upstart's ubuntu branch, his bzr tree is packaging only and I can't commit to it.21:44
sbeattiekees: okay. So long as we're sure it won't get lost in a future upstart update.21:48
keessbeattie: I don't think so.21:49
keesdoko: I don't know why, but PPC glibc isn't building (it's failing in tests, and I'm pretty sure my change isn't the cause).  any idea?21:51
dokokees: which test?21:54
keesdoko: I just retry'd the build.  none of the other archs fail.21:55
keesdoko: http://launchpadlibrarian.net/18052012/buildlog_ubuntu-intrepid-powerpc.glibc_2.8~20080505-0ubuntu7_FAILEDTOBUILD.txt.gz21:56
keesGCONV_PATH=/build/buildd/glibc-2.8~20080505/build-tree/powerpc-libc/iconvdata LC_ALL=C   /build/buildd/glibc-2.8~20080505/build-tree/powerpc-libc/elf/ld.so.1 --library-path /build/buildd/glibc-2.8~20080505/build-tree/powerpc-libc:/build/buildd/glibc-2.8~20080505/build-tree/powerpc-libc/math:/build/buildd/glibc-2.8~20080505/build-tree/powerpc-libc/elf:/build/buildd/glibc-2.8~20080505/build-tree/powerpc-libc/dlfcn:/build/buildd/glibc-2.8~20080505/bu21:56
kees/bin/sh: Syntax error: Bad fd number21:56
dokoI'll retry on the other buildd21:56
keesmake[3]: *** [/build/buildd/glibc-2.8~20080505/build-tree/powerpc-libc/nptl/tst-cleanup0.out] Error 221:56
keesieee21:56
keessorry, that was a much longer paste21:56
keesthan I was expecting.  :)21:57
keesdoko: how do you push it to another buildd?21:57
dokosetting the other to manual21:57
keesheh21:57
infinityThey both use the same chroot...21:57
infinityI see no way that something like FD breakage would change from one host to another.21:57
dokobut today is Monday21:58
keesI'd seen this error the very first time I built glibc locally the ("Bad fd number") stuff, and suspected maybe I was running out of disk space.  I cleaned up, and it went away.21:58
dokohmm21:58
infinityWhich host was the failure on?21:58
keesBuilder:   ross (powerpc)21:58
=== jussi01_ is now known as jussi01
calcslangasek: oh i don't disagree that it shouldn't be pulled in by default (i had forgotten about the recommends bit) just that only installing the good set won't be of too much use for cross platform office document viewing22:01
ogracjwatson, i still end up with epiphany in the mobile build :/22:04
ograso adding the task didnt really solve it it seems, unless my preseeding is wrong22:05
sbeattiekees: whoops, sorry for the bug editing collisions.22:08
cjwatsonogra: point me to the build logs?22:08
ogranot sure they are mirrored already22:09
ogralog/ubuntu-mobile/intrepid/daily-20080929.7.log22:10
* ogra looks at people.u.c22:10
cjwatsonI meant the livefs log22:10
ograoh22:10
ograindeed22:10
cjwatsonhttp://people.ubuntu.com/~ubuntu-archive/livefs-build-logs/intrepid/ubuntu-mobile/latest/livecd-20080929.1-i386.out?22:10
ograargh, my FF is broken22:11
ogralikely -222:11
ograif there is one22:11
keessbeattie: no problemo :)22:13
cjwatsonogra: wouldn't you need http://paste.ubuntu.com/52238/ in order to actually use the task?22:14
ograasac, http://people.ubuntu.com/~ogra/FF_no_button_text.png22:14
ogracjwatson, oh, sigh, indeed, i forgot about that one22:14
ogranot for mid though, they dont want a task i was told22:15
ogralool, ^^^22:15
cjwatsonogra: actually, make that http://paste.ubuntu.com/52239/22:15
ograyeah22:16
ograthe preseed already has mobile-mobile22:16
ogracjwatson, sorry for wasting your time :(22:17
norsettoasac: just uploaded new versions for gnome-mplayer/gecko-mediaplayer to mentors if you want to sponsor ...22:17
cjwatsonogra: it's ok22:18
cjwatsonit took almost no time since I suspected that was the problem from the start :)22:18
cjwatsonogra: do you want that ubuntu-mobile crontab entry added to the live crontab?22:18
slavikany chance of evolution 2.26 in ibex?22:19
ogracjwatson, i already added it, i suppose someone needs to activate it ?22:19
cjwatsonhence "live crontab"22:19
cjwatsondone22:20
ogracjwatson, oh, well, the cdimage entry calls "buildlive ubuntu-mobile; for-project ubuntu-mobile build-image-set"22:20
ograso i should drop the "buildlive ubuntu-mobile;" i suppose ?22:21
cjwatsonogra: what? not that sort of live22:21
ograoh, k22:21
cjwatsonogra: editing the crontab requires running the crontab command to update it22:21
ograah22:21
cjwatsonogra: I've done it now22:21
ogralive as in actual :)22:21
ograheh22:21
asacogra: not properly restarted after upgrade?22:21
ograi totally misunderstood ... we actually meant the same ... live confused me22:21
ograasac, rebooted22:21
asacogra: LANG? en-us?22:22
ograde_DE22:22
ograde_DE.UTF-8 actually22:22
ograhumm, cjwatson can you let the livecd-rootfs package through ? (and probably as well xf86-input-evtouch)22:28
asacogra: maybe language changes something?22:30
ograasac, let me try22:30
ograasac, hmm, gone now22:32
ogracant reproduce it22:32
asacogra: yeah .. you didint properly restart :-P22:32
=== beuno_ is now known as beuno
ograwell, i'd expect a reboot to be a proper restart :)22:33
ograbut well22:33
ograall fine now22:33
cjwatsonogra: both done22:33
ogragracias22:33
ograi wonder if it makes it until 2:45UTC ...22:34
asacogra: i agree ... if you see it again, let me know.22:34
ograwill do22:34
seb128slangasek: I've sponsored a gnome-build upload which fixes the previous screwed update we synced on debian, could you consider accepting before beta? only anjuta uses it and it's not installable right now due to the gdl changes, once this gnome-build is built we can sync anjuta 2.24 which fixes the installability issue22:34
* ogra calls it a day22:35
asacogra: enjoy22:36
slavikis openchange going to be in ibex?22:50
asaccjwatson: slangasek: i have uploaded latest NM with the wizard. its network-manager, -applet, -pptp, -vpnc and -openvpn. thanks.22:52
slavikcjwatson: does it honor the /etc/network/interfaces settings?22:53
asacslavik: you probably ask me?22:54
slavikbah ...22:54
slavikyes22:54
loologra: Sorry, don't quite get why you say mid doesn't want the task?  You mean the mobile one?  Or is this about the task headers?22:54
asacslavik: it honours them if you append the ,ifupdown plugin to the nm-system-settings.conf22:55
slavikty22:55
slavikasac: will that be default?22:55
asacslavik: the fix for the /etc/network/interfaces bug will be fixed individually22:55
slavikthere's a bug associated with that?22:55
* slavik is not aware of anything22:56
slavikalso, any idea of the best place to track the e1000e regression in the kernel?22:56
asacslavik: well, there is bug 25605422:56
ubottuLaunchpad bug 256054 in network-manager "[intrepid] new 0.7 branch ignores /etc/network/interfaces" [Unknown,Confirmed] https://launchpad.net/bugs/25605422:56
asacslavik: look in the mailing list archives. i think there was mail that referred to a bug id22:58
slavikk22:58
slavikasac: any idea about the openchange mapi plugin for evolution?22:58
asacslavik: why do you have so many questions ;)22:58
slavikI know gnome 2.26 will have it ... but any chance 2.24 to have it?22:58
slavikasac: asking questions is what I do22:59
asacslavik: i am not the gnome maintainer ;)22:59
asacslavik: bug 26355522:59
slavikit's the best way to learn things (and to annoy people, too)22:59
ubottuLaunchpad bug 263555 in linux "[intrepid] 2.6.27 e1000e driver places Intel ICH8 and ICH9 gigE chipsets at risk" [Critical,In progress] https://launchpad.net/bugs/26355522:59
* norsetto calls it23:00
TheMusocjwatson: Oh right, I'll have another look today then.23:20
mathiazslangasek: openchange is already available in the intrepid archive.23:20
mathiazslangasek: hm - sorry - not for you23:20
superm1TheMuso, the bzr tree for alsa-lib is missing your last few uploads.  don't forget to merge them back in23:30
TheMusosuperm1: I am well aware of that.23:31
superm1TheMuso, okay wasn't sure, just a friendly reminder.  I was pushing a bzr branch out for merging and noticed i had more changelog entries than i should in my commit23:32
MaximLevitskyI suggest you add glipper to base install, bacause it is very awkward to deal with the disapperance of clipboard when you close an app23:43
MaximLevitskyOr at least something that does that23:44
=== superm1 is now known as superm1|away
seb128TheMuso: hi, could you look at http://bugzilla.gnome.org/show_bug.cgi?id=535827, basically at-spi has a schemas which is not installed in ubuntu23:55
ubottuGnome bug 535827 in gtk "Automatically load gail:atk-bridge if AT_SPI_IOR is set on root window" [Normal,Unconfirmed]23:55
TheMusoseb128: I've been made aware of it by the orca lead developer, will take a look once I've processed email for the morning.23:55
seb128TheMuso: ok, they subscribed me to the bug so I was just forwarding the information23:56

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