/srv/irclogs.ubuntu.com/2008/11/10/#ubuntu-devel.txt

=== cjwatson1 is now known as cjwatson
=== asac_ is now known as asac
NCommanderMan, Freenode been glitchy03:00
ScottKYou say that like it's news.03:01
NCommanderScottK, I remember freenode when it was steady as a rock03:05
ScottKNCommander: Do you have some time to try and verify a security patch for me (It's C, so I'm hopeless)?03:06
jdongNCommander: yeah yeah and you walked in 15 feet of snow uphill and downhill everyday to school in the next city....03:06
ScottKjdong: You got it wrong, "Up hill both ways".03:07
NCommanderjdong, no, I took a bus03:07
NCommanderScottK, define verify03:07
jdongNCommander: verify (v. trans. InfoSec): "Yeah, I think most of ~/ is still there AFAICT..."03:07
jdong*ducks*03:07
ScottKNCommander: Upstream produced a new upstream release that has both a working exploit test and a very invasive fix.03:07
NCommanderOk03:08
ScottKNCommander: Upstream gave a hint on how to shortcut avoiding the problem in a less invasive way03:08
ScottKNCommander: Debian maintainer has produced a patch that he thinks is good, but upstream doesn't have time to deal with confirming it works.03:08
ScottKI'm looking for some independent verification.03:09
NCommanderSo, why not install package, run verification test?03:09
ScottKYou've looked at the code before so I thought of you.03:09
ScottKI'd have to understand Perl to run the test.03:09
ScottKThat and I'm currently busy trying to understand why cmake seems broken in Jaunty.03:10
ScottKI guess that's a no then.03:18
ScottKTries again.03:18
ScottKI guess that's a no then.03:18
NCommanderScottK, sorry, my laptop froze03:20
NCommanderScottK, sure, I can be convinced to test it03:20
ScottKOK.  I'll email you some stuff.  You'll want libspf2 from Jaunty and Hardy.  What address.03:20
ScottKNCommander: ^^03:22
NCommandersonicmctails@gmail.com03:23
ScottKNCommander: Forwarded you the upstream hint and the proposed patch.03:24
NCommanderis the patch in jaunty or the new upstream?03:24
=== deejoe is now known as spudnoggin
ScottKThe patch is against 1.2.5 (in Dapper -> Hardy).03:25
ScottKThe new upstream is in Jaunty/Intrepid-security.03:25
=== spudnoggin is now known as deejoe
ScottKThe test is in the new upstream.03:25
* NCommander grabs the jaunty source package03:25
ScottKIf the package is vulnerable, the test will cause a segfault.03:26
ScottKNCommander: Be sure to grab the -security version.03:26
NCommanderScottK,   libspf2-2: Depends: glibc-private but it is not installable03:26
ScottKThat adds the patch that made it possible to get to this problem (fix one vulnerability and expose another latent one |o/)03:26
NCommander*ahem*03:26
ScottK?03:27
NCommanderTrying to install on jaunty03:27
NCommanderPackage is broken03:27
ScottKWeird.  Installs on Intrepid.03:28
ScottKSame package.03:28
NCommander:-P03:28
NCommanderYeah03:28
NCommanderits broken on jaunty03:28
ScottKOK.  Separate issue.  I'll look at that.03:28
NCommanderok, I figured out how to run the test suite against various versions of the package :-)03:29
ScottKGreat.03:29
NCommanderI'll test the jaunty package (assuming it compiles)03:29
ScottKTry the hardy-security version against it and see.03:29
NCommanderI need to have a known working negetive03:30
ScottKRight.03:30
NCommanderargh03:30
NCommanderdamn it03:30
NCommanderI actually have to install the library03:30
* NCommander breaks pbuilder out03:30
NCommanderargh03:31
NCommanderthe test suite needs a non-packaged perl module it seems03:31
ScottKUpstream runs Gentoo, so who knows.03:34
* NCommander whacks head03:34
NCommanderbah03:34
NCommanderGetting this test suite to run is a ****03:34
* NCommander upgrades perl base03:35
NCommanderok03:35
NCommanderconfirmed that the version in jaunty does not suffer the buffer overflow03:35
NCommanderargh03:38
NCommandert/11_overflows.......dubious03:40
NCommanderTest returned status 0 (wstat 11, 0xb)03:40
NCommanderDIED. FAILED tests 3-503:40
NCommanderFailed 3/5 tests, 40.00% okay03:40
NCommanderScottK, ^03:41
NCommander(that being said, the test suite might be a false postive, I had to kick it to actually compile )03:41
ScottKThat's Jaunty?03:41
NCommanderHardy security03:41
ScottKOK.  I'm fairly certain that one isn't vulnerable.  More than one person who knows the code verified that.03:42
ScottKAh.  Hardy Security.  Sorry03:42
NCommanderyeah03:42
NCommanderit segfaulted03:42
ScottKI'd expect Hardy Security to fail.03:43
ScottKThat's the indication it's vulnerable.03:43
NCommanderit got through 2/3 tests however03:43
ScottKThe patch in Hardy security I think is tested for in that same test.03:44
NCommanderroot@blacksteel:~/libspf2-1.2.5.dfsg/perl# perl t/11_overflows.t03:45
NCommander1..503:45
NCommanderok 1 - use Mail::SPF_XS;03:45
NCommanderok 2 - parse_cidr did not run off start of data03:45
NCommanderSegmentation fault03:45
ScottKI think that's right.  I suspect the one in hardy-release would fail 203:46
NCommanderso now what?03:48
NCommanderlibspf has two rdepends03:48
NCommanderIt might just be worth doing a backport03:48
ScottKSo the question is does the patch I emailed you fix it?03:50
NCommanderoh03:50
NCommanderI thought the patch was applied already03:50
ScottKNo.03:52
ScottKI emailed you patch #2 that hopefully finishes fixing it.03:52
NCommanderLets find out03:52
NCommandert/11_overflows.......ok03:53
NCommanderWOOOO!03:53
cody-somervilleNCommander, chillax :P03:53
NCommanderchillax?03:53
ScottKNCommander: So it works.  Would you view it as sane?03:55
NCommanderYes, expect it makes a blank patch file as well03:56
NCommander51_actually-keep-track-of-max_var_len.dpatch - empty03:56
NCommander52 - has the real patch03:56
ScottKexpect/except?03:57
NCommander*except :-P03:57
ScottKOK.03:58
ScottKNCommander: Thanks.  I'll work on -security debdiffs then.03:58
NCommander\o/03:58
ScottKNCommander: Any thoughts on where glibc-private in Jaunty comes from?03:58
NCommanderno idea03:59
NCommanderit might just need a binary rebuild03:59
ScottKTried that.  No luck.03:59
ScottKIt picks that up from somewhere.03:59
NCommanderapt-cache doesn't know what it is04:01
ScottKIt doesn't exist.04:01
NCommanderits in none of the shlibs files I have04:01
* NCommander pokes LP04:03
NCommanderScottK, I'm semi-stumped04:18
ScottKNCommander: I dunno the relevancy, but glibc in Intrepid defines a large number of symbols in GLIBC_PRIVATE that seem to be gone in Jaunty.04:18
NCommanderbug in glibc?04:18
* NCommander debates downgrading to intrepid04:19
ScottKNCommander: I was thinking more planned change we need to figure out how to work with.04:20
NCommander??04:20
ScottKLooking at debian/changelog this symbol thing was on purpose.04:21
ScottKNot sure if it's relevant to the problem at hand or not.04:21
NCommanderwhere is doko when you need him04:21
=== jamesh_ is now known as jamesh
glaksmonohello05:19
ScottKNCommander: Thanks.  -security debdiffs are done.05:38
NCommanderyay05:38
* ScottK goes and sleeps.05:38
\shmoins06:23
\shNCommander: welcome on board of the MOTU ship :)06:24
NCommander\sh, thanks :-)06:24
NCommander\sh, do you know who the resident grub guy is on Ubuntu?06:24
\shNCommander: nope...sorry...06:25
NCommandercjwatson, I'd like to talk to you on adding splash images for grub06:57
wgrantNCommander: Not by default, I hope.07:05
NCommanderwgrant, ?07:06
wgrantNCommander: It was, I believe, decided that yet another mode change wasn't necessary.07:07
pittiGood morning07:07
NCommanderwgrant, mode change?07:07
* NCommander notes our current grub does properly support splashimages, and those work just fine07:07
wgrantNCommander: Splash image == graphical mode == mode switch == flickering == baaad07:08
wgrantMorning pitti.07:08
NCommanderfair enough07:08
NCommandermorning Pici07:08
* NCommander hit head07:08
NCommanderpitti,07:08
wgrantFlickering and slowness and other stuff, probably.07:08
pittiwgrant: pong07:08
wgrantIt's not accidental that we lack a splash image, at any rate.07:08
wgrantpitti: See bug #293318/07:08
ubottuLaunchpad bug 293318 in gnome-settings-daemon "gnome-settings-daemon leaks memory" [High,In progress] https://launchpad.net/bugs/29331807:08
wgrantI think it's that one.07:08
wgrantYes it is.07:08
tjaaltonfedora removed their grub splash image07:09
NCommanderThey did?07:09
tjaaltonfor the same reason07:09
* NCommander notes Debian still has one07:09
pittiwgrant: I got the bug mail, yes07:09
NCommanderwgrant, I can find that leak07:09
wgrantNCommander: Huh?07:09
tjaaltonnow they don't even show the menu anymore, unless there's another boot option available (like windows)07:09
NCommanderthe memory leak07:09
wgranttjaalton: That's what we do, isn't it?07:09
tjaaltonwgrant: yes07:09
wgrantNCommander: I've even fixed it upstream...07:09
NCommanderoh07:09
NCommandernm07:10
* NCommander hadn't finished reading the bug :-)07:10
wgrantNCommander: Why do you want a GRUB splash?07:11
NCommanderBrainstorm #21, and my mom freaked when she saw it when I installed Ubuntu on her PC07:11
wgrantSurely it's no more scary than watching a POST.07:12
NCommanderAt least no computer I've owned in a few years shows a text based PoST07:12
NCommander... PSOT07:12
NCommander... POST!07:12
NCommanderon mine, I get Sony VIAO -> grub -> usplash07:12
tjaaltonjust get rid of windows and you're saved07:12
* NCommander gets the grub countdown07:13
tjaaltonno grub menu anymore07:13
NCommanderyes, I know07:13
TreenaksOn my eee I get grub (very short) -> usplash07:13
Treenaks\o/ bios quickboot07:13
tjaaltonNCommander: oh, yet another "idea" I can close?-)07:14
NCommandertjaalton, if you must ;-)07:15
tjaaltonah, fedora didn't actually remove the splash, but it's not shown unless the menu is07:19
* NCommander notes thats how itlled is on Ubuntu as well if a splash is insta07:21
pittiwgrant: did you sent the two g-s-d input patches upstream? There aren't any patch headers or gnome bz refs07:22
wgrantpitti: The upstream-relevant parts are upstream.07:22
pittiwgrant: ah, nice; thanks07:22
wgrantI didn't add patch headers because the patches were already there.07:22
pittiwgrant: I added the bug ref for 293318 to the changelog; does 08_extra_touchpad_options.patch correspond to a bug report, too?07:24
wgrantpitti: They're both for that bug, though 08_extra_touchpad_options.patch is more of an additional defense.07:25
pittiok, thanks!07:25
wgrantNo, thank you.07:26
wgranttjaalton: Are any other distros going to be sharing our pain in the immediate future?07:26
pittifedora isn't yet?07:26
pittiwgrant: I assume "pain" == "input hotplug"? :-)07:27
wgrantpitti: Input hotplug for everything, yes.07:27
dholbachgood morning07:30
tjaaltonwgrant: fedora is07:31
tjaaltonat least07:31
tjaaltonand when lenny is released I bet debian will follow07:31
wgranttjaalton: Hmm, I wonder how they dealt with g-s-d...07:31
wgrantFrom what I could see they hadn't.07:32
pittiwgrant: nothing on http://daniel.holba.ch/harvest/handler.py?pkg=gnome-settings-daemon ?07:32
tjaaltonwgrant: what in particular?07:33
wgrantpitti: No...07:34
wgranttjaalton: Mouse settings (most annoyingly right/left-handedness) don't persist when you hotplug devices.07:34
wgrantSome keyboard stuff doesn't work at all, but that's another less important story.07:34
tjaaltonwgrant: okei07:36
tjaaltonuh07:36
tjaalton"okay"07:36
pittislangasek: did you see the response in bug 236830? seems there is still a bug there?07:44
ubottuLaunchpad bug 236830 in samba "cifs does not support kerberos authentication" [Medium,Fix committed] https://launchpad.net/bugs/23683007:44
=== anil1 is now known as anilg
SYDN谁知道有64的JAVA 那里下载08:10
RAOFIndeed.08:11
SYDNwhere08:12
wgrantI agree with RAOF.08:13
RAOFAha.  Sorry.08:14
RAOFGoogle tells me that you want to download Java.08:14
RAOFSYDN: You want the "sun-java6-jre" package.08:15
SYDNoh08:16
iulianThere is a #ubuntu-cn channel though.08:17
* iulian wonders why he didn't join there.08:17
pittimvo: good morning08:42
pittimvo: I checked the hardy SRUs, and it seems that bug 220890 is the only one which holds up -updates propagation of 3 hardy-proposed uploads08:42
ubottuLaunchpad bug 220890 in python-apt "[hardy] software-properties-gtk doesn't recognize (nor know about) ports.ubuntu.com" [High,In progress] https://launchpad.net/bugs/22089008:42
pittimvo: anything we can do about it? or is it not a regression, and we can copy and keep the bug open?08:42
mvopitti: I look into it now, sorry that it got put on hold during intrepid08:45
NCommanderUgh, that one08:47
* NCommander puts that on the Ports todo tracker08:47
slangaseksuperm1: ok, changed in bzr, thanks08:50
slangasekpitti: 236830> the only issue I see at the end of the bug log was user error, which EtienneG addressed?08:51
pittislangasek: ahh, I read it as "that's what the package should ship"08:52
mvoNCommander: what is the url for this?08:52
pittislangasek: ok, so that's basically "didn't get any feedback" then08:52
NCommandermvo, right now, I'm just going to note it on the kernelportspage08:52
* NCommander kicks the spacebar08:52
slangasekpitti: ah, so it is; I guess we should kick people for testing :/08:53
NCommanderBut at least w.r.t. to powerpc, I've been working w/ a bunch of other people to make sure PowerPC is a top-notch port again08:53
emgentgood morning08:55
NCommandermvo, I think I can probably fix this bug in Jaunty08:57
NCommander(the ports one)08:57
mvoNCommander: I check it out now and let you know what I find, I thought I fixed it already :/08:59
NCommanderI thought it was broken on Intrepid09:00
NCommandermvo, are you a ports user?09:00
mvono, that i part of the problem09:00
NCommanderinstall lpia on something w/ a CD then09:00
NCommanderIts considered a port on LP09:01
mvoright, good idea09:02
NCommanderI have those occasionally :-)09:02
pittimvo: I'm ready to accept update-manager for intrepid-proposed, unless you have some more changes stacked up?09:03
mvopitti: is the other one in -updates now?09:05
pittimvo: yes, I copied it this morning09:05
mvoexcellent!09:06
mvonothing pending currently09:06
pittimvo: good; accepted then09:06
kirklandmvo: pitti: I have a debdiff coming shortly for update-notifier for Jaunty;  adds an update-motd hook such that update notifications are appended to the MOTD09:07
NCommanderpitti, what is binary NEWed?09:07
mvokirkland: nice, I will merge it when its ready09:09
sorenIs anyone else unfortunate enough to have to deal with the wl wifi driver?09:11
NCommandersoren, yes, I have09:12
sorenI find there's a huuuuge difference between the latency of my network connections when I use that and when I use ndiswrapper (which used to be my only option).09:12
NCommanderpitti, https://bugs.edge.launchpad.net/ubuntu/intrepid/+source/mtd-utils/+bug/29442809:13
* soren runs a simple benchmark09:13
ubottuLaunchpad bug 294428 in mtd-utils "mtd-utils build fail" [Undecided,Fix committed]09:13
sorenNCommander: Is it horribly laggy for you as well?09:14
pittiNCommander: a package which hasn't been built before must be checked by the archive admins, and is held in a queue for that before being published to the archive09:19
NCommandersoren, my current machine doesn't have wl, but in my experience, yes09:19
NCommanderpitti, ah, I see. I enabled proposed on my intrepid box, and checked it, so now what :-)?09:20
pittiNCommander: if it works, then it's good for copying to intrepid-updates, and closing the bug09:21
geserpitti: Hi. Please give-back vim on i386. Thanks.09:21
NCommanderIt works to the extent I can test it (I don't have anythign attached to this PC I can forgot jffs2, but the tools, and the help for the tools work)09:21
sorenNCommander: http://people.ubuntu.com/~soren/wlstats.txt <---- No fun at all09:22
pittigeser: it's built already09:22
geserpitti: https://launchpad.net/ubuntu/jaunty/+source/vim/+builds shows a FTBFS for i38609:23
pittigeser: indeed, seems my script is broken09:24
* pitti fixes it for s/intrepid/jaunty/09:25
pittigiven back09:25
* soren wonders why he didn't see the e-mail about that build failure... :/09:25
wgrantHow does one get posting privileges revoked from -devel-discuss?09:36
slangasekmail -devel-discuss-owner, I guess?09:37
cody-somervillewgrant, is there a particular reason you ask? :P09:37
wgrantThey're not doing a very good job of making developers want to read it.09:38
ograthat's why it's called -discuss :)09:42
ografor actual development there is ubuntu-devel09:42
wgrantI mean, I thought I directed some serious torrents of hate at Launchpad, but that just doesn't compare...09:43
Hobbseewgrant: hmm, I wonder who has powers over that list10:02
Hobbseeoh, wow.  It's getting even better.10:03
NCommanderWhat list?10:04
wgrant-devel-discuss10:04
HobbseeNCommander: https://lists.ubuntu.com/archives/ubuntu-devel-discuss/2008-November/006221.html and that general thread (and other useless wastes of bytes on that list)10:05
HobbseeNCommander: oh, and those sorts of posts are normal for that guy, too.10:05
NCommanderWTF is the difference between devel-discuss and -devel10:05
wgrantOne has ******** on it.10:05
HobbseeNCommander: devel == sane.  has developers on it, and is moderated so you don't get that kind of rubbish.10:05
liwNCommander, one is discussion about developement, one is discussion about discussion about development?10:05
NCommanderHobbsee, semi-moderated, developers are whitelisted10:06
HobbseeNCommander: -devel-discuss: users speaking to developers...Or, now, as the case may be, lots of hate mail, which most people ignore, and occasional developer discussions, which a few people follow.10:06
NCommanderwho do I get in contact if I want a mailing list10:06
HobbseeNCommander: well, yeah.  But the developers aren't expected to behave badly.10:06
HobbseeNCommander: depends.  What for?10:06
* NCommander would like an ubuntu-ports list <g>10:06
HobbseeNCommander: do you want to use listadmin on it?10:06
NCommanderlistadmin?10:06
* NCommander knows listsrv, but not listadmin10:07
HobbseeNCommander: http://debaday.debian.net/2007/09/12/listadmin-command-line-mailman-moderator-queue-manipulation/10:07
NCommanderProbably10:07
* NCommander would whitelist developers of course10:07
HobbseeNCommander: if you do, you can't use the launchpad lists, you'll need to get a list on lists.ubuntu.com (and I think you'll need to speak to jcastro about it)10:07
NCommanderjcastro, ^10:08
Heller_Bardewhat program is this volume OSD of ubuntu part of?10:08
liwit's probably night for jcastro10:08
wgrantHeller_Barde: gnome-settings-daemon, I believe.10:09
Heller_Bardeah. and where can i find out how the shortcut is bound to it?10:09
wgrantHeller_Barde: What do you mean?10:10
Heller_Bardeor does gnome-settings-daemon capture shortcuts itself?10:10
wgrantIt does.10:10
Heller_Bardeah10:10
Heller_Bardei don't use gnome and actually dont want to but nothing else is able to look appropriately aesthetic :(10:10
Heller_Bardeoh well10:11
hyperairbah the two-stage rsync mirroring script from ubuntu is useless on slow internet connections10:12
hyperairrsync the debs first, then the indexes. sounds like the perfect idea. but then it takes so goddamn long to rsync the debs that the indexes have updated by then =.=10:13
wgranthyperair: You're not meant to mirror the archive on dialup.10:13
hyperairwgrant: i'm not on dialup damnit10:13
hyperairwgrant: this is a university connection10:14
mvopitti: I looked into #220890 and AFAICT the remaining issue is that source code is not recognized as "offical" on powerpc but binary deb lines are. so it should be ok for -update (and I will push another one afterwards that fixes the source lines)10:18
pittimvo: ok, thank you10:31
sebnerpitti: is your list for coping stuff from -proposed to -updated already empty (for intrepid)?10:32
pittisebner: yes; see http://people.ubuntu.com/~ubuntu-archive/pending-sru.html10:32
sebnerpitti: intrepid has 2 packages with 7 days ;D10:33
pittisebner: but not verified one10:33
pittis10:33
sebnerpitti: what has to happen to make it verified?10:34
pittisebner: test that the package in -proposed still works as usual, and that it fixes the bug, and give written confirmation of that in the bug10:34
sebnerpitti: my package (audacious) has over 5 users can confirm that the update in -proposed fixes the issue ;)10:35
pittisebner: ah, then nobody from motu-sru set the verification-done tag apparently; please do so then10:35
sebnerpitti: done10:37
pittithanks10:37
sebnerpitti: np, thank you your copying then :D10:37
tkamppeterpitti, hi10:40
tkamppeterwhat is missing to get the CUPS SRU released?10:41
pittitkamppeter: testing and being 7 days in -proposed10:41
tkamppeterpitti, did not know that there is a "minimum 7 days" condition. All bugs related to pstopdf are answered and the answers suggest that the problems which I have addressed with pstopdf are really solved.10:49
pittitkamppeter: right, except for the 'prints garbage on samsung' for splix10:49
pittibut we can keep that open and still move to -updates10:49
* ogra grumbles at asac ... my mobile phone is suddenly not detected as USB HDD anymore ... grrr10:50
* mvo thinks that asac probably sneaked int ogra house just to play that trick on him10:51
* ogra tries to get the pictures off the camera with bluetooth instead10:51
ogramvo, he doesnt go that far south for playing tricks i bet :)10:52
liwogra, perhaps he has agents everywhere?10:52
ograhaha10:52
liwhe is, after all, a manager ;)10:52
mvoogra: you never know, he is on vac, maybe that is part of his vacationfun ;)10:53
* mvo stops being silly10:53
tkamppeterpitti, and the AppArmor thingy with the network protocols I can confirm. The problem appears (I have 6 network printers) on the machine where I did not update to -proposed and does not appear with the -proposed package.10:53
pittitkamppeter: can you please say so in the bug, for having a written track of testing?10:54
tkamppeterpitti, done.10:56
tkamppeterpitti, the garbarge printing which you observer with SpliX now is most probably a problem of SpliX itself. Therefore I need you to do tests with the LSB packages from OpenPrinting. The test on 2.0.0rc2 can reveal whether there is perhaps a bug in the Ubuntu packaging. The test of the 1.1.1 version can show whether the 2.x generation of SpliX introduced a new bug.11:02
pittitkamppeter: ah, ok; I'll do that11:02
tkamppeterpitti, I have modified the OpenPrinting packaging last week so that these drivers can coexist with the ones coming from the distros.11:03
tkamppeterSo you do not need to uninstall any package.11:03
wgrantmvo: Does do-release-upgrade do the xorg.conf inputdevice mangling too?11:20
ograwgrant, what mangling ?11:21
wgrantogra: We comment out inputdevices on upgrades to let input-hotplug work its magic.11:22
ograxorg will ignore keyboard and mose settings from the file if not forced11:22
wgrantNo it won't...11:22
ograthats inside xorg afaik11:22
wgrantReally new xservers will ignore kbd and mouse entries, as evdev needs to grab them.11:22
ograthere was a setting i dont remember you have to add to the xorg.conf to make it use these entries11:23
wgrantAutoAddDevices, yes.11:23
ograright11:23
wgrantBut that's not what I'm talking about here.11:23
ograelse it will use evdev by default11:23
ograand ignore the xorg.conf entries for keyboard and mouse11:23
wgrantI know, but this is somewhat separate.11:24
ografor other input devices it depends on the driever ...11:24
ograi.e. wacom will only use hal if yu copy the .fdi in place, else xorg.conf should be used11:25
wgrantAnd lots of them will break horribly, which is why we now comment them out on upgrades.11:25
ograreally?11:25
* ogra wasnt aware we touch xorg.conf at all11:25
wgrantAs of late Intrepid we do.11:25
ograhmm11:26
tkamppeterpitti, I have investigated bug 293883 now and it is an evince bug, so it does not block the SRU release of CUPS. pstopdf was not the culprit there.11:31
ubottuLaunchpad bug 293883 in evince "8.10 Printed PDF missing parts / corrupt" [Medium,Confirmed] https://launchpad.net/bugs/29388311:31
cjwatsonNCommander: we tried it before and it broke some people's hardware, so I'm not all that interested in trying it again TBH11:38
NCommanderWorks for me11:39
* NCommander deletes the idea from his brain11:39
mok0rm -rf /sys/brain/idea11:39
mvowgrant: yes11:39
NCommandermok0, file not found11:39
wgrantmvo: Hmm, OK, I have a report from somebody that it didn't.11:39
mok0hehe11:40
wgrantBut perhaps not fully trustworthy.11:40
mvowgrant: it writes out a log what its doing11:40
mvowgrant: please ask the reporter about the stuff in /var/log/dist-uprade/*11:40
mvowgrant: is there a LP bug for it?11:40
wgrantmvo: There isn't. I'll ask for logs.11:40
mvothanks11:40
hyperairlate intrepid touches xorg.conf?11:42
wgranthyperair: Since late in the Intrepid release cycle, the dist-upgrader touches xorg.conf.11:42
hyperairoh11:42
hyperairwhat does it do11:42
wgrantComments out inputdevices.11:43
pittislangasek: I ported your hal patch 99_new-kernel-rfkill-interface.patch as best as I could to new hal upstream; but since I don't get any observable lshal change when flipping the killswitch either with your old nor with my ported patch, I can't really test it; can you?12:00
slangasekpitti: I guess that's for jaunty?  I'm afraid I can't test that very easily; but the main point would be whether NM detects the status change, I guess?12:04
pittislangasek: yes, for jaunty12:05
pittislangasek: well, NM doesn't do anything if I change the killswitch12:05
slangasekhmm12:05
slangaseknot with either version?12:05
pittibut didn't do that in intrepid either12:05
pittithat's why I can't test the ported patch12:05
slangasekhrm12:05
StevenKslangasek: Bit early, isn't it?12:05
slangasekpitti: this is on a system with Intel wireless?12:05
slangasekStevenK: ?12:05
StevenKslangasek: It's 4am in LA12:06
pittislangasek: yes, iwl3945 with dell killswitch12:06
slangasekpitti: do you have /sys/class/net/$dev/device/rfkill?12:06
slangasekStevenK: yep, right in the middle of my Monday shift12:06
slangasekpitti: (you're running the Intrepid kernel, right?)12:07
pittislangasek: intrepid kernel> yes12:08
pittislangasek: /sys/class/net/wlan0/device/rfkill/rfkill0/state12:08
pittislangasek: I can put the new consolekit and hal into my intrepid PPA, if that would help you12:09
slangasekpitti: that would be better12:09
slangasekI'm still puzzled that it doesn't work for you, though12:09
slangasekfor me, the nm-applet icon reflects the state change within a few seconds12:09
pittiwell, the killswitch itself works12:10
pittiin the sense of that it blocks wifi12:10
pittibut NM doesn't react to that12:10
slangasekhmm12:11
slangasekthen I guess my patch is screwed up somehow, even though IWFM :/12:11
pittislangasek: someone else on the upstream bug confirmed that it works12:11
pittiseems hw specific12:11
slangasekyeah, I saw12:11
slangasekbut I don't understand /why/ i would be hw-specific12:12
pittislangasek: if you change the killswitch, do you see something in lshal flip state?12:14
pittislangasek: both uploaded and building now12:21
slangasekpitti: lshal changes> no; though apparently if I'm lucky, I can hard-lock my laptop in the process12:23
slangasekpitti: but I guess calling 'hal-ystem-killswitch-get-power' directly should show the output?12:24
slangasek+s12:24
pittiw$ sudo ./hal-system-killswitch-get-power12:25
pitti.: 10: hal-functions: not found12:25
pittibah12:25
slangasekdoh12:25
pittibut it's there... ?!?12:25
Nafalloanyone know if we have support for Intel 4500MHD?12:33
TreenaksNafallo: what is it?12:33
TreenaksNafallo: a CPU?12:33
NafalloTreenaks: some kind of new graphics thing.12:33
NafalloI think :-P12:34
NafalloIntel Graphics Media Accelerator 4500MHD DVMT (Dynamic Video Memory Technology)12:34
Nafalloyea. new GMA.12:34
asacogra: so you want to use your phone as HDD and not 3G device ;)?13:00
ograasac, well, it used to show up as HDD when i plugged it in with cable ...13:01
ograbut BT works fine for pulling off files13:01
ogramy phone has a 2G micro SD card i use as data storage from time to time13:02
asacogra: when did USB stopp working?13:02
ograno idea, i just pluged it in for the first time after an aeon13:02
ograi dont think i even tried it in intrepid at all before13:02
ograit used to show up as HDD in hardy iirc13:03
asacogok13:03
ograogok ?13:03
liwI wouldn't mind using my phone as a storage device, too, in order to move files to the memory card13:03
asacogra: do you have different modes?13:03
asac(on the phone)13:03
ograits in usb storage mode by default ...13:03
liw(but I'm happy to shuffle the memory card around for now)13:04
ograone sec, doorbell, brb13:04
asacogra: maybe it was the airprime driver?13:04
=== LucidFox_ is now known as LucidFox
asac(that one was dumbed in intrepid afaik)13:05
mvocjwatson: do you happen to know if we use the wget udeb still these days? it got added by fabio in the feisty days and I was wondering if we should keep this change around or not13:10
cjwatsonmvo: I think Fabio might have wanted it for system-integrity-check maybe? nothing in d-i itself uses it13:15
mvocjwatson: yes, that looks right13:17
mvothanks!13:17
cjwatsonmvo: that said, I don't see anything in system-integrity-check that relies on it13:17
cjwatsonoh, no, Depends: wget-udeb. WTF13:17
cjwatsonfabbione: why was busybox's wget not good enough?13:18
cjwatsonfabbione: it doesn't seem as if system-integrity-check uses any features not in busybox's wget13:18
* NCommander laughs evilly13:31
slangasekjordi: yuck, why is there a lib64asound2-plugins?  Is there really a use case for 64-bit alsa support on 32-bit installs?13:32
directhexNCommander, evil laughter? that can only mean added mono! ;)13:32
NCommanderslangasek, offhand, I'm going to guess for compiler biarch sanity13:33
slangasekhuh?13:33
* NCommander shakes head13:33
NCommanderWow, I'm loosing it13:33
NCommanderjust ignore me13:33
NCommanderdirecthex, actually, debhelper 7 was backported (thank you slangasek)13:34
NCommanderThat unblocks at least 10, maybe more backports13:34
directhexNCommander, version?13:34
NCommanderhardy-backports13:34
directhexi meant actual package ver13:35
NCommanderdirecthex, the one from intrepid, 7.0.13ubuntu113:37
=== Keybuk_ is now known as Keybuk
pittiStevenK: what's the rationale for your pilot-link patch 30_3_arg_open.dpatch? no patch headers, no bug refs, no rationale in changelog :(13:40
fabbionecjwatson: at the time, it was not good for https. We started doing all the stuff to https and the whole thing was stalled on lack of time13:41
cjwatsonoh, right13:41
pittiStevenK: oh, nevermind, got it13:41
cjwatsonmvo: ^- above is still the case13:42
fabbionecjwatson: not sure if wget in busybox does https now.. nor if ubuntu cares about s-i-c. I gave it to the server team a while ago.. no idea if they have done anything about it13:42
cjwatsonI don't think anyone cares very much about s-i-c any more, but wget doesn't do https and that seems like a valid use case13:43
cjwatsonbusybox wget that is13:43
fabbionecjwatson: ok. I personally don't think i care nor i have time to do s-i-c. Might worth discussing it again with the server team and free resources at the datacenter since there is a server side for it13:44
pittiStevenK: did you send it to an upstream ML? I don't find an upstream bug tracker13:44
fabbionecjwatson: the code is still in bzr somewhere public I believe. anyway the last releae in the archive had everything that was in bzr anyway13:44
mvocjwatson, fabbione: right, thanks13:52
fabbionemvo: no worries :)14:02
Keybukcjwatson: still trying to figure this udev bzr packaging case out14:04
Keybukhit another problem; the udev git repository doesn't contain (as you'd expect) configure, Makefile.in, etc.14:04
Keybukwhich means merging with "bzr pull" isn't going to produce something like the orig.tar.gz14:04
Keybukthe diff.gz will always end up with autoconf changes14:05
Mithrandirnot if you nuke them in the clean target14:06
Mithrandir(and build-depend on auto*)14:06
pittiKeybuk: what's wrong with having autogenerated autofoo stuff in the diff.gz?14:08
pittiit might not be nice, but well, it's just noise14:08
Keybukpitti: well, fwics, I have two options14:09
Keybukclean bzr packaging, based off a git import, with merges and changes done with bzr nicely - but messy resultant traditional source package14:09
Keybukor a clean source package, created by lots of by-hand heavy lifting with bzr/git14:09
Keybukalso wouldn't it break colin's "what you checkout from bzr must be buildable" requirement?14:10
pittijames_w: do you care about backuppc? You did the last merge, but it's currently on my plate since I did a last-minute dependency fix14:11
pittiKeybuk: can't speak for others, but for e. g. jockey I don't care about messy diff.gz if the ubuntu package is a direct branch of upstream trunk14:11
james_wpitti: I did the last merge as it was DIF and unmerged I believe.14:12
james_wpitti: I don't mind merging again if you want it off your plate14:12
Keybukpitti: but then debcheckout doesn't give you anything buildable?14:12
pittiKeybuk: since you aren't going to use patch systems or MoM for those, messy diff doesn't really hurt IMHO14:12
pittiKeybuk: it should be buildable, of course14:12
pittiKeybuk: debian/rules could just call autogen.sh?14:12
Keybukhow do you make it buildable?14:12
Keybukbut then the package has to depend on auto*14:12
pittilots of packages do14:13
Keybukplease nuke autogen.sh ;)14:13
pitti(yes, I repeatedly argued against it in the past, for packages which update autofoo on build)14:13
cjwatsonKeybuk: james_w may have technology to generate the tarball branch (i.e. git + configure/etc.) automatically14:13
pittiKeybuk: or autoreconf -v, or whatever :)14:13
james_wlies!14:13
cjwatsonautogen.sh> still useful when you're doing things that autoreconf doesn't do :P14:14
pittijames_w: ok, nevermind then; I just wondered if you were actually using it and could test it or so, but seems not :)14:14
james_wthough it might be possible thinking about it14:14
Keybukit'd have to be a Build-Depend-Indep on auto*, right?14:15
cjwatsonjames_w: the only hard bit is identifying the revision from which the tarball was produced; after that you just unpack and blat the changes into the archive14:15
Keybukor is it only build-depends?14:15
cjwatsonBuild-Depends is stronger than Build-Depends-Indep in practice14:15
cjwatsonpolicy is extremely confusing on this14:15
Keybukyeah, I've never really understood it14:15
Keybukat one point I thought -Indep was for "things needed to make the source package"14:16
Keybukbut it appears policy disagrees on that now14:16
cjwatsonbasically I only use Build-Depends-Indep if either (a) I have an explicit build-indep rule and the dependency is only used there and/or (b) it's only used in binary-indep14:16
cjwatsonI don't think policy ever said anything like that14:16
pittiKeybuk: the way I understood it, you don't need -indep when building with -B14:16
pittisuch as the !i386 buildds14:16
NCommanderI was under the impression that Build-Dep-Indep is anything the independent build-deps needed explicately14:16
Keybukcjwatson: it's entirely likely it didn't ;)14:16
cjwatsonoh, it might have had confusing language about clean at some point14:16
Keybukthought of the day: we should have an autoreconf meta package :p14:16
* pitti generally just ignores B-D-I, too confusing to think about14:17
cjwatsonyeah, that's usually the right answer14:17
cjwatsonthere are a small number of cases where it is important and/or useful14:18
pittithat the !i386 buildds use -B is really just an implementation detail packagers shouldn't really care about, FWIW14:18
pitticjwatson: oh? so there's more to it than just buildds?14:18
cjwatsonpitti: no, I didn't say that :)14:19
cjwatsonpitti: I just meant that it is usually reasonable to default to sticking everything in B-D, and only think about B-D-I if you find you need to14:19
pittiah, right14:19
siretarta common case is running doxygen to create an libfoo-doc package. doxygen can go to B-D-I then14:20
ScottKI'm looking at a package that has gone uninstallable in Jaunty because it believes it needs to depend on a non-existant package called glibc-private.  Rebuilding produces the same result.  Package builds and produces an installable binary on Intrepid.  Any suggestions about where to look?14:20
pittiScottK: sounds like a bad .shlibs file?14:21
siretartScottK: bad shlib.local file in the package?14:21
pittiScottK: if local build does the same, grep /var/lib/dpkg/info/*.shlibs for glibc-private?14:21
cjwatsonScottK: that means that the package is relying on private glibc symbols and it shouldn't be14:21
cjwatsonScottK: it's basically glibc arranging for the package to blow up14:21
pittioh, magic14:21
siretartsweet14:21
ScottKArgh.  OK.  Thanks for the hints.14:21
ScottKYes.  Does the same thing on local builds, so I'll look.14:22
cjwatsonhttp://bugs.debian.org/cgi-bin/bugreport.cgi?bug=46244414:22
ubottuDebian bug 462444 in glibc "glibc: Please add symbols files for libc6" [Wishlist,Closed]14:22
ScottKThanks.14:22
cjwatsonI think you can pass -xglibc-private to dpkg-shlibdeps to skip it if you know what you're doing14:23
cjwatsonbut it's probably worth investigating first14:23
ScottKOK.  I'm definitely in an area where "know what I'm doing" doesn't apply.14:24
ScottKWhich is, of course, half the fun.14:25
Keybukcjwatson: did you autosync contrib or non-free?14:28
* ogra wonders if MoM is broken 14:32
ograor probably she simply forgot i exist14:32
pittiogra: curious14:34
ograi only seem to have one package in universe14:34
pittiogra: you've got stuff on http://merges.ubuntu.com/universe.html, thoug14:34
mvoogra: generally it seems to be running quite happily14:34
* mvo just checked the logs 14:35
ograwhich additionally is better off to be merged by LaserJock14:35
cjwatsonKeybuk: not yet14:35
cjwatsonKeybuk: doing so now14:35
pwnguinHobbsee: looking at the record thus far, I don't think the recent post by Vincenzo is "normal" in tone or language. it also doesn't reflect my own interactions with him.14:36
siretartMithrandir: did you have the chance yet to look into the pkg-config issue slomo and I asked you about?14:40
Mithrandirsiretart: I didn't, no. :-/14:40
pwnguinIt does reflect somewhat my own frustration with the status quo, but I'm not about to write angry letters over it14:41
hyperairwhat pkg-config issue?14:41
Keybukogra: ;)14:42
ogra:)14:42
KeybukI suspect it's because you've got your "you touched it last" list down to almost zero14:42
ograseems like14:43
ograwhich is weird14:43
siretarthyperair: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=50422014:43
ograi thought i touched a good bunch14:43
ubottuDebian bug 504220 in libavcodec-dev, "Missing dependencies" [Grave,Open]14:43
Keybuknot really, you tend to touch things in universe more than main14:43
ograbut i'll pick up leftovers14:43
Keybukand universe has a high "fix after freeze" ratio14:44
hyperairhm ubottu handles debian bugs too?14:44
hyperairi never knew14:44
ograyeah, since i'm in mobile i touch a lot of universe14:44
Mithrandirsiretart: you need to depend on the -dev packages.14:46
siretartMithrandir: but isn't that insane? why do depending packages need to care about whether libavcodec-dev links against libtheora or not?14:47
Mithrandirsiretart: if it is in "Requires.private", then it not only links with it, but also needs the headers from it.14:48
Mithrandirlike gtk exposes glib types in its headers.14:48
siretartMithrandir: libavcodec does not TTBOMK expose any libtheora internals14:48
Mithrandirif it just links with it without exposing any of libtheora's types, using libs.private should be fine.14:48
siretartokay. is there any documentation or any document I could point upstream at to get that fixed?14:49
Mithrandironce I get around to writing it. :-/14:49
siretartmay I quote this irc conversation?14:49
Mithrandirsure.14:53
tkamppeterpitti, did you do the test for bug 292690, I have also added another possibility to test.15:02
ubottuLaunchpad bug 292690 in cups "Garbage bitmaps printed on left margin in ubuntu testpage on A4 on Samsung printers" [Undecided,Fix committed] https://launchpad.net/bugs/29269015:02
=== dholbach_ is now known as dholbach
ftadear archive admins, please, consider opening the ppa gates to jaunty.15:08
cjwatsonis it our decision?15:09
cjwatsonI thought that was an LP thing15:09
ftai asked there 1st => <cprov> fta: the decision belongs to the archive-admins at this point, so #ubuntu-devel might be a better place to discuss it.15:09
cjwatsoncprov: do it15:09
cjwatsonI don't think we have the lever; if we do then please tell me15:09
cprovcjwatson: okay, I will organise the opening15:10
cjwatsoncprov: I can't think of any reason why we wouldn't want to open a distroseries for PPAs at the same time as we open it for regular uploads. Do you know why it is done separately?15:10
cprovcjwatson: those decisions are still orthogonal in the DB. We open a new distroseries by change its status from frozen to development15:12
cprovcjwatson: PPA archs are enabled per distroarchseries base.15:12
cjwatsoncprov: OK, I'll edit our NewReleaseCycleProcess to say we need to notify you to enable PPAs15:13
cprovcjwatson: right, if you think it's appropriate, we could try to glue those decisions in a single form.15:14
cprovhttps://launchpad.net/ubuntu/jaunty/{i386, amd64, lpia}/+admin15:14
cjwatsoncprov: I don't mind as long as it gets done; a note in NewReleaseCycleProcess should be good enough15:14
cjwatsoncprov: yeah, I don't have access to that15:15
cjwatsonsee also: why can't distro drivers administer distroseries, eh?15:15
cprovcjwatson: me neither, I will ask kiko.15:15
ftacprov, cjwatson: wonderful, thanks guys :)15:16
jordislangasek: I assumed it is as useful as lib64asound215:21
cprovcjwatson: fta: jaunty PPAs are supported.15:25
ftagreat15:26
cjwatsonthanks!15:28
siretartcprov: when exactly did you enable jaunty PPAs?15:29
cprovsiretart: few minutes ago.15:30
siretartah, ok. I tried this morning and got my upload rejected15:30
hyperair...what happens when someone uploads a html file that redirects to a virus site to launchpad? =.=15:31
hyperairhttps://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/5969515:31
hyperairsee the last comment15:31
ubottuError: Could not parse data returned by Launchpad: The read operation timed out (https://launchpad.net/bugs/59695/+text)15:31
ScottKhyperair: You should take that up in #launchpad.15:35
hyperairlol15:35
tkamppeterpitti, ping15:37
ScottKhyperair: Why is that funnny?  They're the only ones that can do anything about it.15:40
hyperairyesy es15:41
hyperairwell, i'm the kind of person who laughs when yet another windows user gets struck by a virus15:41
hyperairi'm evil like that15:41
hyperairanyway i've alerted the guys at #launchpad15:42
pittitkamppeter: hi15:47
pittitkamppeter: btw, I can't configure the lsb splix2 packgage; s-c-p doesn't find it, and if I select the PPD manually, I just get an internal cups error15:48
directhexmono 2.0-1 very soon, apparently15:48
pittitkamppeter: oh, nevermind, it didn't get configured (lsb dependency isn't installed)15:51
=== ember_ is now known as ember
pittitkamppeter: yep, works now15:52
pittitkamppeter: new filter tested now, too16:07
evandAnyone have a 4GB USB disk, a recent Apple computer, and a free moment to test something for me?16:21
liwevand, I'm lacking all three, but just for clarification: do you need exactly 4 gigs or at least 4?16:23
evandat least16:23
evand(I have an image to dd to such a disk, so the other requirement would be a disk that you don't care about :)16:24
pittipedro_, sbeattie: any chance to give gparted in hardy-proposed a test, for bug 37768? I was the uploader, so I need a second tester16:27
ubottuLaunchpad bug 37768 in gparted "gnome-volume-manager mounting Partition, while working with GParted" [Medium,Fix committed] https://launchpad.net/bugs/3776816:28
mvokirkland: hello! how often is update-motd run ?16:31
=== deejoe is now known as everyone_else
kirklandmvo: every 10 minutes;  i'm putting a delayer in the script i'm working on to ensure that the update-notifier bit wouldn't run more frequently than once per hour16:31
=== everyone_else is now known as deejoe
mvokirkland: the update-notifier bit is to pick up notification from user.d/ ?16:32
kirklandmvo: actually, i meant: /usr/lib/update-notifier/apt-check16:33
kirklandmvo: i propose something like this: http://pastebin.ubuntu.com/70058/16:33
kirklandmvo: call it "notify-updates-available"16:33
mvokirkland: aha, ok - I'm adding support for new release upgrade notification into update-manager-core right now (just fyi) - and it should ideally be only once a day16:33
kirklandmvo: similar to "notify-reboot-required"16:34
kirklandmvo: cool, what i'd really like is just a number dumped into /var/run/updates-available16:34
kirklandmvo: also, i find it really, really odd that /usr/lib/update-notifier/apt-check puts the number of updates available on STDERR ... why's that?16:35
mvokirkland: would it make sense to have a /etc/update-motd.d{.daily/,.hourly, etc} ?16:35
kirklandmvo: yes, i'm working on that, as update-motd's upstream16:35
kirklandmvo: i intend to do that very soon16:35
mvokirkland: its a workaround because sometimes other stuff gets spit onto stdout16:35
kirklandmvo: oh16:35
kirklandmvo: it gave me a few fits :-)16:36
kirklandmvo: i got around it16:36
mvokirkland: would it make sense to just modify apt-check so that it has a "--for-update-motd" (or something like that) so that it prints out exactly what you need?16:36
mvokirkland: update-notifier has a lot of UI dependencies, so changes to update-notifier are required I assume?16:37
kirklandmvo: right, i'd need something in update-notifier-common16:37
kirklandmvo: can't really bring all those UI deps into ubuntu-server16:37
kirklandmvo: what cronjob currently drives apt-check?16:38
mvokirkland: indeed :) so if we need to do that anyway, I wonder if we should have a apt-check that is tailored to the needs of update-motd in the sense that it outputs the right kind of message (with i18n and everything)16:38
mvothen all that is needed is that it installs a symlink to update-motd and is done with it16:39
kirklandmvo: okay, so i have throw one more wrinkle into the mix ...16:39
mvokirkland: update-notifier itself drives apt-check, it has inotify rules to monitor apt/dpkg so that it known when it should (re)check for updates16:39
kirklandmvo: i think it's going to be landscape-sysinfo that's going to gather this info16:40
mvokirkland: hm16:40
kirklandmvo: so landscape-sysinfo could even use a python library to grab this from apt-check16:40
* mvo scratches his head and thinks about it a bit16:41
sbeattiepitti: I'll take a peek16:43
ddfirehi17:33
ddfirei need help making a deb package17:33
ddfireor backporting asterisk 1.4.21 from 8.10 to 8.0417:33
ddfireanyone have an idea?17:33
ddfirea pdf?17:34
ddfirea clue?17:34
Nafalloddfire: wrong channel. try #ubuntu-motu.17:34
ddfireNafallo: thanks17:34
ddfireNafallo: what is the objetive of this channel?17:36
Nafalloddfire: what the topic says ;-)17:36
EtienneGquick question ... will we get Mono 2.0 in Jaunty?  I suppose so, just wondering.17:38
ddfireok17:44
ddfirethanks17:44
maxbThe intrepid-backports devscripts has broken the "dch --distributor" option :-/17:47
* maxb wanders in the direction of launchpad17:48
pittimvo: is it really deliberate that apt-get build-dep installed packages get auto-removed?17:52
pittiit makes 'autoremove' pretty useless on a developer box17:52
ScottKMaybe we need apt-get autoremove-build-dep-yes-really17:57
maxb"apt-get build-dep" is an explicit user request to install packages, so shouldn't they count as manually installed?17:59
cjwatsonI could go either way17:59
cjwatsonoften build-dep is only very temporary for me18:00
cjwatsoninstall, build, remove18:00
cjwatsonanyway:18:00
cjwatson  * make "apt-get build-dep" installed packages marked automatic18:00
cjwatson    by default. This can be changed by setting the value of18:00
cjwatson    APT::Get::Build-Dep-Automatic to false (thanks to Aaron18:00
cjwatson    Haviland, closes: #44874, LP: #248268)18:00
cjwatsonso change that configuration option if you don't like it18:00
ion_Yeah, build-deps are typically temporary – if i want -dev packages that stay, i can make them manually installed.18:01
pitticjwatson: ah, thanks; so feature, not bug18:03
liwI tend to find that apt's (or aptitude's) heuristics of autoremovable packages meshes badly with what I want to keep, but I am probably excentr^Wodd18:06
ion_liw: You might want to try debfoster. I use that (and apt-mark-sync to sync its decisions to apt and aptitude).18:11
apacheloggerjames_w: we are going to discuss bzr for KDE packages at the next Kubuntu meeting, please select agreeable time slots at http://doodle.com/participation.html?pollId=tvt9bb3fvtbqda8v18:20
bryceslangasek: hey, SRU question for you18:26
bryceslangasek: wacom tablets are fairly broken right now in Intrepid.  There is a newer version of the linuxwacom driver in Jaunty (0.8.1-6 vs 0.8.1-4) with necessary fixes.  Would a sync of something like that be conceivably within the realm of possibility?18:28
jdongbryce: since it's the same upstream version can't we just call it a "SRU"? :)18:45
brycejdong: guess that's my question ;-)18:46
pwnguinbryce: isn't it really hard to test jaunty right now?18:46
brycepwnguin: indeed.  In this case, the users self-compiled the driver and tested it on intrepid.18:46
jdongI mean if wacom is "fairly broken" IMO it wouldn't hurt to do some ~proposed testing. If you have big enough a base, put it into a PPA I guess18:46
pwnguini mean, im all for better wacom; the status quo is terrible18:46
jdongs/base/bug subscriber base/18:46
pwnguini hope i dont have a big ppa base18:47
pwnguinanyways, i dont have the right hardware to test18:48
jdongme neither.18:48
jdongchristmas presents welcome ;-)18:48
pwnguinheh18:48
brycewell, I'm trying to determine how much time this is going to require.  If we can just sync it in, it should be a reasonable amount of time and I'll give it a shot.  If it's going to require patch cherry picking, ppa testing, and so on, I likely won't have sufficient time to see the whole thing through to completion, so ought to focus my efforts elsewhere.18:48
jdongbryce: well I assume the differences between debian revision 4 and 6 is just going to be a lot of debian/patches magic, right?18:49
bryceprobaby18:50
bryce+l18:50
jdongI'd just package all of those patches into a SRU-like version number (i.e. -4ubuntu0.1) and consider that a SRU candidate, get a couple users to tell you it works okay, then you're done :)18:50
jdong(QA FOLKS PLEASE LOOK AWAY)18:51
pwnguinheh18:51
pwnguinwhat's the worst that can happen?18:51
pwnguinwacom remains broke?18:51
jdongpwnguin: from the way it sounds, it can't get any worse.18:51
jdongs/any/much/18:51
pwnguini suppose it could crash X18:52
jdongI wouldn't expect that to happen with the kind of changes in a new debian revision though.18:52
pwnguinbut the recovery tools are supposed to be bulletproof now ;)18:52
jdongI'd be a lot more scared if it were an entire new upstream release and a huge diff18:53
mvopitti: it was a feature request to have it this way, -o apt::get::build-dep-automatic=false turns it off18:55
* ScottK notices the upload of sane-backends and waits for insane-backends .18:55
mvopitti: I don't mind either way, I can switch it to the reverse again18:55
sebnerScottK: I just subscriped MC, I'll recieve more and more questions so it's easier18:56
pwnguinbryce: fyi, wacom is apparently scheduling a new release next week ;)18:56
ScottKsebner: OK.  You know you didn't really answer all my questions in your reply.18:56
sebnerScottK: well, I didn't know. apachelogger told me. So maybe I'm missunderstanding you or my lack of english skills has the fault18:57
brycepwnguin: nice... wonder if they'll include the changes needed for hal18:57
pwnguini suspect not;18:58
pwnguinThe new hotplugging (Xorg 1.5.1 or later) will be supported with linuxwacom version 0.8.4 (0.8.3 will be its unstable release).  It is too late to add the support to the coming stable release (0.8.2), which is scheduled to be posted this week.18:58
pwnguin""18:58
ScottKsebner: I'll write a new mail.18:58
* ScottK waits for jdong to package insane-backends18:58
sebnerScottK: yeah! yet another mail. keep going. I have a bet running that I'll recieve more than 10 questions :D18:59
ScottKsebner: Sent.19:00
sebnerScottK: now I'm subscriped, Does also my pending question (for dholbach) get's posted?19:02
ScottKsebner: You mean you sent a reply to dholbach?  If so, I haven't seen it.19:03
sebnerScottK: besides .. would you mind explaining your question question  ^ ^  I don't know what you want. A specific example?19:03
sebnerScottK: well, I wasn't subscriped so it was pending19:03
sebneror still is19:04
ScottKYes.  An example of one you wish you had asked for and didn't and one you wish you hadn't asked for and why, what you learned, etc.19:04
sebnerScottK: I made mistakes (like syncs that were merges) but I don't have regrets about any sync that filed19:06
sebner+ I19:06
ScottKsebner: Then comment on that to the ML.19:06
sebnerScottK: ah, ok (though it seems that is not the answer you wanted to hear) :)19:07
sebnerScottK: ah ah ah. I lost your mail xD would you mind resending it to me?19:10
gesersebner: I've just moderated your mail to motu-council19:16
sebnergeser: thx, I'm now subscriped. sry for the trouble19:17
sebnergeser: but please don't vote yet. still more questions are in the pipelie ;D19:19
sebner*pipeline19:19
james_wapachelogger: done, thanks. Unfortunately I can't commit to any times this week, but I will do my best to attend if one of those times is picked19:22
apacheloggerjames_w: looks like it's gonna be sunday since you have time and we have a quorum for the membership application :)19:32
james_wI have time, but I may be asleep :-)19:32
ScottKjames_w: As long as you're awake enough to simulate agreement to do stuff, I think it'll be fine.19:36
ScottKBetter you're not awake enough to really process it anyway.19:37
james_wheh :-)19:38
ScottKapachelogger: He thinks I'm kidding.19:39
superm1kees, ping19:50
apacheloggerjames_w: no one really is awake at kubuntu meetings, at least I am not, I usually just drop off some lines and continue dozing ;-)19:51
keessuperm1: pong20:01
superm1kees, i'm thinking something in default build flags decided to wreck some havock20:01
superm1kees, would you mind taking a look, i think you saw this before: bug 29645320:01
ubottuLaunchpad bug 296453 in kbuild "upgrading cvs to 1:1.12.13-12 causes FTBFS on kbuild" [Undecided,New] https://launchpad.net/bugs/29645320:01
* kees goes to read20:01
keesheheh, that's a great build log20:02
keessuperm1: I thought cvs was fixed for hardening weirdness.  I will poke at it.20:03
superm1thanks20:04
keessuperm1: I can't reproduce the cvs crashes...20:36
slangasekjordi: right, so how useful is /that/? :)20:47
slangasekbryce: wacom tablets are broken in intrepid aside from the known, release-noted fdi issue?20:49
superm1kees, i'm assuming on jaunty up to date chroot?20:49
superm1i've got a local sbuild lvm snapshot that is fully updated with no delta otherwise ( both i386 and amd64) that reproduce it20:50
keessuperm1: might be a bit out of date, let me try it again, on sec20:51
cyberixIn some previous version of Ubuntu I double clickked on a gnumeric file and it suggested I should install gnumeric.21:03
cyberixWhy doesn't this work anymore?21:03
keessuperm1: here's the note I removed about cvs: https://wiki.ubuntu.com/CompilerFlags?action=diff&rev2=27&rev1=2621:18
keessuperm1: I still can't reproduce on either amd64 or i386, updated jaunty chroots21:19
superm1kees, how weird that you can't reproduce.  i can in sbuild, pbuilder, and on buildd's21:19
bryceslangasek: yeah, additional bugs21:19
superm1kees, so try to rebuild cvs with that env variable and see if things improve then?21:20
keessuperm1: are there any minimal commands that fail for you?21:20
slangasekbryce: what bugs are those?21:20
keessuperm1: yeah, that'll certainly force those checks off in cvs, but I'd like to have a better idea of what's going wrong.21:21
superm1kees, the most minimal command that fails is "cvs status"21:21
kees.... uhm21:22
keesit's failing for me now.21:22
keeswtf.21:22
NCommanderhey superm121:23
superm1hi NCommander21:23
NCommandersuperm1, how goes it?21:23
superm1NCommander, busy as usual :)21:23
bryceslangasek: like #291908, hangs device when any pressure is on it21:23
NCommandersuperm1, busy with what specifically; anything I can do to hep?21:24
superm1NCommander, with work related things, so not really so much.  but if you are looking for bugs to fix on stuff, i've got plenty i can point you at :)21:25
NCommanderheh, ScottK just got me on one :-)21:25
keessuperm1: ah-ha, cvs 1:1.12.13-11 happened on Jan 27, 2008.  Hardening was enabled on Jun 08, 2008.21:27
bryceslangasek: basically my question is whether a sync of the driver is feasible, or if the individual fix needs to be identified and SRU'd by itself21:27
keessuperm1: so, this is a problem now (I have no idea how it was ever noticed during intrepid... weird)21:27
superm1kees, ah so it never got rebuilt for hardening.  the fact that we synced is why it happens now21:28
keessuperm1: right.  I'm curious how the problem in the wiki was ever noted, but when I tested it had "gone away" since it wasn't rebuilt yet.  wheee21:28
superm1kees, well at least i'm catching this early You've got eon's to ponder on it now. :)21:28
* kees wonders why it doesn't freak out in fedora...21:29
jackrabbitI'm having a problem running autogen.sh on a svn build of network-manager-applet since upgrading to 8.1021:45
jackrabbitthe error I get is: libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and21:45
jackrabbitlibtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.21:46
jackrabbitlibtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.21:46
jackrabbitdoes anybody know what's causing this?21:46
cjwatsonjackrabbit: surely that is a warning, not an error; if you aren't the developer you can ignore it21:48
jackrabbitwell, it started after I upgraded and then I got some other errors as well21:48
cjwatsonthen you should investigate the things that are actually errors21:48
jackrabbitand . . . I ma developing21:48
jackrabbit:)21:48
cjwatsonthe output you quote from libtoolize is clear instructions to developers on changes in libtool macro handling21:49
jackrabbitwhich I believe are responsibles for the errors later on21:49
cjwatsonbut, as you can tell from the language used ("Consider ..."), they don't need to be fixed immediately21:49
cjwatsonjackrabbit: it seems unlikely, but it is impossible to tell without knowing what those errors are21:50
jackrabbitcc1: warnings being treated as errors21:50
jackrabbitutils.c: In function ‘utils_fill_connection_certs’:21:50
jackrabbitutils.c:231: error: implicit declaration of function ‘nm_setting_802_1x_set_ca_cert_from_file’21:50
jackrabbitutils.c:235: error: implicit declaration of function ‘nm_setting_802_1x_set_client_cert_from_file’21:50
cjwatsontotally and utterly unconnected to the libtoolize output21:51
cjwatsonwhat is the svn url?21:51
jackrabbitI think they're caused by the abcense of header files21:51
cjwatsonwhat would libtoolize have to do with header files?21:51
cjwatson(it operates on objects and has nothing to do with headers)21:51
jackrabbitsvn://svn.gnome.org/svn/network-manager-applet/trunk21:51
jackrabbitcjwatson: I'm not that familiar with libtool/autotools etc21:52
cjwatsonjackrabbit: the network-manager-applet version you're compiling requires a newer NetworkManager than what's packaged in Ubuntu 8.1021:56
cjwatsonjackrabbit: the nm_setting_802_1x_set_ca_cert_from_file and nm_setting_802_1x_set_client_cert_from_file functions were added in revision 4239 of NetworkManager, which was committed on the day 8.10 was released21:57
jackrabbitthat's svn too21:57
jackrabbitok, I'll re-install and see if that helps21:57
cjwatsonthat suggests that you are not successfully using the headers from the NetworkManager you built, but are instead using the system headers, then21:58
jackrabbitcjwatson: mind if I ask how you figured that out?21:59
cjwatsonhow I figured which bit out?21:59
jackrabbitthat the symbols were from a newer version than 8.1022:00
cjwatsonjackrabbit: I checked out NetworkManager, grepped for that function, used 'svn blame' to find out when the lines in the header file in question were last changed, and used 'svn diff' to confirm that the revision in question was the one that initially introduced those symbols22:00
cjwatsonand then 'svn log' told me the commit date which was later than the time 8.10 was released so I didn't need to look any further than that22:01
jackrabbitok22:02
jackrabbitthanks, now I'll be able to check that out next time :)22:02
directhexhm, /me spots a minor bug22:08
directhexlooks like a gtk label doesn't have pango markup enabled on it22:08
keesholy cow.  cvs implements its own kind of asprintf.22:44
keesand manually constructs %n-using vsprintfs22:44
keessuperm1: well that was fun to track down.  I've uploaded a fixed cvs now.23:07
NCommanderhey kees23:09
keeshola NCommander23:09
NCommanderSo here's my research23:09
NCommanderIf you have a prebuilt PIE GCC and glibc, you can install it into an existing system23:09
NCommanderBut I need doko's help to actually get a usable patch, mine breaks the C++ compiler from compiling :-/23:10
keeswhy do gcc and glibc need to be PIE before I can built other PIE stuff?23:10
keeser, can build23:10
NCommanderno, if you want glibc/gcc to be pie23:10
NCommander:-)23:10
NCommanderYou can have PIE binaries without them23:10
keesI'm happy to move one step at a time23:11
NCommanderkees, if your going to be at UDS, we could work on this there (aka, get the spec fully hammered out and such)23:11
* kees nods23:11
keesyup, I'll be there.  :)23:11
NCommanderThat way, we can also pin doko and extract the secrets of GCC from his brain23:12
elmowoo, security vs. toolchain!23:14
elmoit wouldn't be a UDS without it!23:14
kees:)23:14
elmo\o/23:15
wgrantToolchain always wins.23:15
elmowgrant: this time, kees brought reinforcements23:15
elmoTAG TEAM CAGE MATCH23:15
keesthough, I think I still lost since I ended up joining the toolchain group.  :P23:15
NCommanderWe should have a four way fight, toolchain v. server v. kernel v. security!23:16
* NCommander runs23:16
wgrantelmo: But now you've warned doko of the evil reinforcement plan.23:16
NCommanderelmo, got a moment?23:16
wgrantDo the archive admins know that Jaunty PPAs are waiting on them now, or are we in a deadlock like we were with Intrepid translations?23:17
elmoNCommander: not really, but what's up?23:17
NCommanderelmo, its yet another PPA question. I have a pending request to see if the kernel team can get a non-virtualized PPA for the linux-ports kernel. Obviously building the -ports kernel on x86/amd64 is of *ahem* limited value :-)23:18
NCommanderer23:18
NCommanderTHat wasn't meant to be a PM23:19
NCommanderhttps://answers.edge.launchpad.net/soyuz/+question/48531 - the distro team asked me to bring to the PPA admins23:19
wgrantNCommander: You mean the other way around?23:19
NCommanderwgrant, what the otherway around?23:20
wgrantThe PPA people seem to be asking you to ask the distro team, not vice-versa.23:20
NCommanderthe distro team sent me back :-P23:20
wgrantAh.23:20
NCommanderEINFINITELOOP23:20
elmowell23:24
NCommanderPorts is somewhat unique, since even just finding some of the hardware *cough*hppa*/cough* is a down right pain23:25
=== lacqui_ is now known as lacqui
keesogra: can you handle the moodle merge? the security fixes I added are all in the Debian package now.23:50
DoYouKnowhow do I get the latest development kernel on ubuntu?23:59

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