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

asac_fta: it is your call :)00:04
=== asac_ is now known as asac
mohbanadoes flash work?00:20
jdongno. we specifically put in some code to break it because it'd be funny to watch 30 million people install it and scratch their heads.00:21
mohbanaok bug dound00:24
samtb2hi there. ant in intrepid seems to depend on gcj even though i have openjdk installed. is this correct? am i supposed to ignore dependencies or something or just install gcj too?00:26
=== CarlFK1 is now known as CarlF1
jibelScottK: Hi, the bug with pycentral in bug 293208 is the way dist-upgrade of python-modules are handled by pycentral00:29
ubottuLaunchpad bug 293208 in python-central "package python-reportlab 2.1dfsg-2 failed to install/upgrade: " [High,Triaged] https://launchpad.net/bugs/29320800:29
jibelScottK: mvo and pitti have discussed about it in bug 29126200:29
ubottuLaunchpad bug 291262 in python-central "package python-psyco 1.6-1 failed to install/upgrade: pycentral pkginstall: not overwriting local files" [High,Triaged] https://launchpad.net/bugs/29126200:29
Keybukpitti: hmm, seem to be hitting a large number of archive 404s :-/00:33
Keybukelmo: around?00:39
elmoyeah00:41
* cjwatson starts to flush out syncs, at least as far as the autosyncer managed to get before falling over00:41
Keybukelmo: is there an internal archive casey should use instead of archive.u.c ?00:41
elmoKeybuk: what's wrong with archive.u.c ?00:42
Keybukelmo: it keeps 404ing00:42
elmochecking00:43
Keybukas if Packages is being updated but not pool00:44
elmonah, a couple of machines are out of sync00:44
elmodue to trigger hoarkage, I'm ficking it00:45
wgrantcjwatson: Are we expecting queue-builder to collapse again this time, meaning buildds sit idle for hours, or is that fixed?00:46
KeybukI'm sure whatever bug we hit last time is fixed00:46
cjwatsonwgrant: I have no idea and am not all that desperately worried00:46
cjwatsonwgrant: we'll find out00:46
Keybukand that we'll find all new bugs this time00:46
Keybuk;)00:46
wgrantHeh.00:47
ajmitchwgrant: have faith00:47
LordMetroidAlright, lets get on deving 9.0400:47
LordMetroidBut how do a newbie as me go about doing so?00:48
LordMetroidI mean newbie to Open Source development00:48
cjwatsonhttp://wiki.ubuntu.com/ContributeToUbuntu00:48
wgrantajmitch: Perhaps.00:49
elmoKeybuk: all in sync, and should be ok going forward00:49
Keybukthanks00:50
Keybuklooks like it ran this time00:50
LordMetroidcjwatson: thank you00:57
slangasektjaalton: have you seen bug #283015 by chance?  I see that you've done a lot of the xkb-data uploads00:58
ubottuLaunchpad bug 283015 in xkeyboard-config "Error in numeric keypad -> "." (dot) key  displays "," (comma) instead" [Undecided,Confirmed] https://launchpad.net/bugs/28301500:58
=== jt66 is now known as jtisme
ThayleHow do I get involved?01:09
directhexThayle, #ubuntu-motu is best for you01:09
ThayleAlright thanks.01:09
directhexremember that many people are busy with the election though01:09
slangasekwith the election, or with the election parties?01:10
TheMusoheh01:11
* ajmitch really should go & vote this weekend then01:12
slangasekso you can get your free coffee at Starbucks?01:13
ajmitchI doubt they'd do that here :)01:13
jdongslangasek: isn't that a felony?01:14
ajmitchwe have to endure a few more days of campaigning in NZ still01:15
slangasekjdong: getting free coffee?01:15
ajmitchdarn, hardy01:15
wgrantWhat has Hardy done now?01:15
ajmitchhardy's debootstrap won't let me create a jaunty pbuilder tarball01:15
wgrantHah.01:16
wgrantSymlinks win there.01:16
ajmitchhaven't upgraded the laptop to intrepid yet :)01:16
slangasekajmitch: pass the extra arg to tell it to use the intrepid or hardy script for building01:16
jdongslangasek: it's offering a monetary incentive to vote, is it not? :)01:18
ajmitchjdong: I believe they've stopped doing that01:19
jdongajmitch: really? is it for that reason?01:19
slangasekjdong: Starbucks actually already got slapped for trying to offer it as an incentive for voting, so they instead changed it to giving free coffee to everyone01:19
jdongslangasek: ah, gotcha :)01:19
jdongslangasek: sadly I don't have any starbucks around here01:19
ajmitchjdong: from what I heard, yes, a number of companies have changed to just giving free stuff/discounts to all01:19
jdongajmitch: haha interesting, I didn't think they'd take that radical reading of election laws so literally :)01:20
slangasekjdong: well you're not missing much, it's only brewed coffee that they're giving away :)01:20
slangasekalso, it's not that Starbucks took the reading literally, it's that the Washington sec of state smacked them01:20
jdongslangasek: with that money I can power my car for 0.5 seconds!01:20
* Keybuk tries to remember what the tomerge files are for01:21
KeybukDaD maybe?01:21
KeybukAdri2000: ?01:21
cjwatsonajmitch: I haven't backported that debootstrap yet01:22
cjwatsonajmitch: but yes, the jaunty script is just a symlink to gutsy, let alone hardy/intrepid01:22
ajmitchyes, I've just put in that symlink for now01:22
Keybukok, mom's brain wiped again *sigh*01:25
wgrantThat sounded very strange.01:25
jdongwgrant: better than last time we had that mom and dad merging discussion.01:30
jdongthat sounded much worse.01:30
wgrantjdong: Indeed, indeed.01:32
KeybukERROR:root:dpkg-genchanges for changes/ubuntu/d/dia/dia_0.96.1-7ubuntu1_source.changes failed01:34
Keybukkooky01:34
Keybukright01:54
Keybuklet's try a patch publish again01:54
Keybukok, http://patches.ubuntu.com/ now has correct data I think01:56
superm1hum what happened to mom?  did she die?01:58
Keybukshe suffered an aneurysm during her move01:58
superm1is she talking about moving in with dad again?02:00
StevenKKeybuk: MoM moved?02:00
cody-somervilleYour MoM is so fat... ugh, never mind. :(02:01
KeybukStevenK: casey likes to throw disks02:04
Keybukand when casey isn't throwing disks, mom is filling 'em02:04
Keybuklooks like there was more damage from the filled disk than I thought02:04
Adri2000Keybuk: yes that was for doing a DaD-like front-end to MoM. iirc I started doing something but nothing was actually finished and published02:05
Adri2000I guess you can keep them though, they might be useful for something else in the future02:05
Keybukmathiaz patched them to add more info, so he must be using them for something ;)02:05
Keybukcomments support:02:11
Keybukit would be nice to have that as plain cgi02:11
Keybuknot being resident in memory would make elmo happier02:11
Keybukright02:16
Keybuklet's spin this again and see whether we get merges with patches this time ;)02:16
KeybukValueError: process failed 17: dpkg-source -x abiword_2.6.4-4.dsc /srv/patches.ubuntu.com/unpacked/a/abiword/2.6.4-402:19
KeybukGnNNAARRGH02:19
ajmitchthat's not a useful error to work with02:19
NCommanderScottK, hola02:22
lifelessKeybuk: :13:57 < nhandler> Is MoM being updated? It only goes up to 'm' right now02:59
lifeless:02:59
lifelessfrom -motu02:59
Keybuksee above03:00
lifelessKeybuk: ah, I only recalled your saying patches should be ok earlier03:01
lifelessKeybuk: thanks03:01
NCommanderwgrant, ping03:47
wgrantNCommander: Hi.03:51
NCommanderwgrant, care to do some upload sponsoring?03:51
wgrantNCommander: Sorry, lots of homework.03:52
NCommandernp03:52
ScottKNCommander: Hello.04:24
NCommanderhey ScottK04:24
Keybukmom working on universe now05:20
Keybukpitti: http://merges.ubuntu.com/a/autogen/ now has both sets of patches ;05:20
Keybukoh, I mean multiverse05:23
=== Keybuk changed the topic of #ubuntu-devel to: Archive: Jaunty open, MoM running, go wild! | Ubuntu 8.10 released! | Development of Ubuntu (not support, not app development on Ubuntu) | #ubuntu for support and general discussion for dapper-intrepid | #ubuntu-motu for getting involved in development | http://wiki.ubuntu.com/UbuntuDevelopment | See #ubuntu-bugs for http://wiki.ubuntu.com/HelpingWithBugs
Keybuk...05:48
Keybuklooks like cjwatson did a sync05:48
pittiGood morning06:15
Hobbseehey pitti!06:15
pittiKeybuk: I noticed some packages which have both patches06:15
pittiKeybuk: archive 404> ah, that could be it; I occasionally get that on my box as well, but 5 seconds later it works again06:15
Keybuklooked like a combination of factors06:16
pittiyay jaunty06:17
Keybukof course, now it has to catch up with the sync06:18
StevenKHey pitti06:18
superm1cjwatson, it looks like that task bug won't actually be resolved until soyuz 2.1.11 on at least 2008-11-19.  at least until then would you anticipate any ramifications in switching it back over to calling upon the meta packages in livecd-rootfs?06:26
superm1if not, i'll do another upload of livecd-rootfs with that hack in place to do a first alpha, planning to remove it shortly after first alpha06:28
michael__MoM?06:41
brycemerge-o-matic06:44
bluefoxicydamnit06:44
bryceiz our lil' friend06:44
bluefoxicyI cannot sing Beautiful Dreamer, and I haven't been able to actually record on Ubuntu for like 6 releases06:44
michael__cool06:47
tjaaltonslangasek: aww that one.. yes it was mentioned on another bug that got fixed.. should be simple to fix07:25
slangasekok, cool :)07:25
=== tkamppeter_ is now known as tkamppeter
pittiArneGoetje: intrepid-proposed langpacks copied; however, since the jaunty sync wave is building, too, building the langpacks will take a while07:47
StevenKi386      1532 builds waiting in queue07:52
StevenKDaaaaaaaaaaaaaamn07:52
pittineed more buildds :)07:52
pittiunifying the ppa and ubuntu buildds would be great in times like that07:52
Hobbseewhee!07:53
Hobbseepitti: does that mean you'll fix your buildd.py script to work for rescores again?  :)07:53
wgrantpitti: There are bugs about that, filed by almighty people.07:53
pittiyeah, I talked about that with Adam07:53
liwpitti, if there was a way to run buildds easily under kvm, perhaps temporary buildds could be arranged for these times07:54
wgrantPooling buildds between the big three archs and PPA/primary would indeed be very nice.07:54
pittiand about 800 of those builds are langpacks, which are currently only built by i386 buildds07:55
wgrantHmm, pretty pathetic sync run. Was that incomplete, or are we seeing the effects of the Lenny freeze?07:55
liwwgrant, I'm pretty sure we are07:57
liwthough I can't be bothered to dig up statistics for how sid has changed in the past several months07:57
pittiogasawara: o_O07:58
pittiogasawara: I thought we settled for having just one bug for tracking 2.6.27.y patches, to ease bureaucracy?07:58
pittiogasawara: so from all those invalid bugs I take it that intrepid final already has 2.6.27.2?07:59
pittiogasawara: ah, yeah, that's what the changelog says anyway07:59
* soren makes a note to remember to upload a new vim with syntax highlighting for Jaunty+1 *before* Jaunty releases08:45
lasko*nod*08:46
Treenakssoren: current vim doesn't have syntax highlighting?08:46
laskocurrent vim should.08:47
Treenakslasko: *phew* :)08:47
sorenNot for "Jaunty" in changelogs.08:47
Keybukit does highlight jaunty08:47
Keybukin that oh-so-attractive yellow-on-OMG-red ;)08:47
sorenWell.. Yes. :)08:48
laskoThough... if I remember correctly it requires vim-full?08:48
sorenNo, it's in vim-runtime.08:49
sorenThe syntax definition, that is.08:49
laskoahh08:49
sorencjwatson: Are you doing vim already or should I grab it?08:51
KeybukI don't think he's up yet08:52
=== hunger is now known as Guest33852
pittisoren: just do it :)08:57
NCommanderhey soren08:57
sorenNCommander: ahoy.08:57
=== hunger_t is now known as hunger
sorenpitti: Will do :)08:57
pittirandom throught of the day: using vimplate helps a lot for creating debian bugs with ubuntu patches08:57
NCommandersoren, how goes it this $TIME_OF_DAY08:57
pittisoren: which remeinds me that I totally forgot to upload mutt as my first merge; damn08:58
pittioh, we are current, nevermind08:58
sorenNCommander: I'm not sure, really. I'm rather knackered. I didn't get to sleep much last night.09:00
sorenNCommander: Yourself?09:00
sebnerpitti: mighty pitti. mind moving audacious from proposed to updates? bug #29164309:01
ubottuLaunchpad bug 291643 in audacious "Audacious plays the last playlist instead of the double-clicked file" [Low,Confirmed] https://launchpad.net/bugs/29164309:01
pittisebner: hm, I already went through the list today, that wasn't on my radar09:01
pittisebner: nack; just 2 days old, needs 709:01
NCommandersoren, trying to sleep and failing miserably -/09:01
sebnerpitti: also though I have already 4-5 positive comments?09:02
sorenNCommander: 'tis easy. Just stop.09:02
pittisebner: it's current policy; we occasionally do exceptions for really grave bugs, where the severity outweighs the risk of regression09:03
sebnerpitti: Ok Í see. anyway, thx09:03
pittibut it needs explicit justification09:03
=== lamont` is now known as lamont
pitti\sh: heck, what *is* wrong in the picture? :-)09:09
StevenKpitti: You don't see it? :-P09:09
pittioh, now I do09:09
pittioops :)09:10
StevenKHaha09:10
Keybukthat's the australian mirror09:10
StevenKHaha09:10
pittiʎןʇɔɐxǝ09:10
NCommanderwow09:14
NCommanderMcCain got slaughter09:14
NCommanderer09:14
NCommanderwrong channel09:14
Keybukyay, MoM finished09:14
* Keybuk remembers to unlock her09:14
StevenKYou lock up MoM?09:15
Keybuksure09:15
* Keybuk decides that chewing on a permanent CD marker is not such a great idea09:16
* mvo uploads a jaunty update-manager (for the early birds)09:20
Hobbseeoh dear...09:22
Keybukpitti: you leave the Changed-By to be mom?09:22
pittiKeybuk: whoops; not usually, that was a brainfart09:22
pittiKeybuk: I usually merge by hand, but that asciidoc thing was so simple that I just took MoM's output09:23
StevenKpitti: Including "DESCRIBE CHANGES HERE" ?09:23
* sebner hugs mvo for that :P09:23
pittiStevenK: no, the changelog is fine :)09:23
pittibut apparently I used "vi", not "dch"09:24
KeybukI often wonder if I made MoM secretly add "THIS PACKAGE WAS MERGED BY AN INATTENTIVE PERSON" to the description, how many people would notice :p09:24
StevenKHahah09:24
* pitti sighs at the devscripts delta09:25
mvosoren: do you think we could make "-net nic,model=virtio" default in the kvm in jaunty?09:26
mvosoren: and maybe a bigger default than -m 128 ?09:27
pittimvo: oh, is that the magic incantation to actually get network in kvm?09:27
Keybukand -soundhw all09:27
Keybukand make it somehow magically work on my XPS09:27
mvopitti: for me "-net user -net nic,model=virtio" is the key to get fast networking09:27
pittimvo: well, at first I wanted to get networking *at all*09:27
mvoKeybuk: yeah, good point09:28
mvopitti: otherwise its stuck at ~300kb/sec even from a local cache09:28
mvopitti: oh? -net user did that for me, but that is the default AFAIK09:28
* Keybuk has the only Intel Core 2 Duo without Virtualization support09:28
pittimvo: inside it might work, but at the host I tried to configure pan0 appropriately, and it wouldn't work09:28
pittimvo: simply no ping; and that didn't even get to masquerading or so09:29
pittiI ended up kpartx-mounting the image for copying stuff into the vm09:29
NCommanderKeybuk, nope, I got one too09:30
NCommanderYay first generation hardware09:30
Keybukbut since it can run amd64, vmware works09:30
NCommanderKeybuk, wait, if it supports amd64, it should have VTx09:30
KeybukNCommander: tell that to Dell09:30
NCommanderTHe chip supports it09:30
NCommanderyou might need to cox the bios to enable it09:31
sorenmvo: No.09:31
KeybukNCommander: no vmx in /proc/cpuinfo09:31
sorenmvo: That would make anything but Hardy and Intrepid fail miserably.09:31
Keybukwhereas my Intel Core Duo has vmx in /proc/cpuinfo even when disabled in the BIOS09:31
NCommanderKeybuk, d'oh09:31
sorenmvo: (the nic model thing, that is)09:31
NCommanderKeybuk, what model Dell is it?09:32
KeybukNCommander: XPS m133009:32
NCommanderhrm09:32
NCommanderKeybuk, the m1330 is listed as supporting it09:33
NCommanderYou need a BIOS greater than A2 however09:33
mvosoren: oh, ok - that is a good arguement against it ;)09:34
NCommanderKeybuk, to get it to work on mine, I had to apply a hack to my BIOS :-)09:34
Keybuka hack?09:35
NCommanderSony locks out VTx on their chips09:35
NCommanderYOu have to mod the BIOS to enable it09:35
* NCommander LOVES playing find the offset09:35
NCommanderDell just seems to require a new enough BIOS09:36
* Keybuk has bios A0809:36
NCommanderAnd no VTx ENABLE in the POST menu?09:36
Keybuknope09:36
sorenKeybuk: vmx capabilities show up in cpuinfo even when disabled in the BIOS. That's expected.09:36
NCommandersoren, not always09:37
Keybukit's a T555009:37
NCommanderOuch09:37
NCommanderOk09:37
NCommanderYeah09:37
sorenNCommander: I've never seen it not happen.09:37
NCommanderI can't believe they actually shipped a core without VMX which the T5550 is09:37
* Keybuk has no understanding of Intel product names or numbers09:38
NCommandersoren, I know on this machine I always had it, it was just a matter of hacking the Phoenix BIOS this POS came with09:38
* NCommander notes that he got this machine at prices that are disturbing low09:39
NCommanderOnly reason I got a sony09:39
Keybukthis was the cheapest on-offer pick from the website09:39
Keybukit mostly runs iTunes and Lightroom ;)09:39
NCommanderKeybuk, it could be worse09:43
directhexwhen does jaunty go EOL?09:43
Keybukt'other half got the expensive, top-of-the-range 155009:43
sorenNCommander: Do you actually have examples of hardware that manages to hide vmx even from cpuinfo when disabled in the bios?09:44
Keybukdirecthex: two years last thursday09:44
directhexsoren, yes! this desktop pc does that!09:44
NCommanderdirecthex, its a little early for that ;-)09:44
NCommanderdirecthex, its a little early for that ;-)09:44
NCommanderer09:44
directhexNCommander, not when warning upstream of which versions of their apps will be shipped09:44
NCommanderNot offhand sommer09:44
NCommanderwow09:45
NCommanderI totally fail Keybuk09:45
NCommanderwait, no, that was soren09:45
sorendirecthex: Brand?09:45
NCommander-ENOSLEEP09:45
directhexsoren, HP09:45
sorendirecthex: Can I see your cpuinfo, please?09:45
directhexsoren, i had to actually flash on a replacement BIOS just to get the ability to turn it on09:45
NCommanderdirecthex, It has an AMD core, right?09:45
directhexNCommander, intel09:45
NCommanderO_o;09:45
NCommanderI've only seen AMD's do that09:45
sorenNCommander: AMD's don't have vmx.09:45
* Keybuk bestows the Tollef Award for Terseness on mvo09:45
Keybukupdate-manager (1:0.95) jaunty; urgency=low09:45
Keybuk  * updated for jaunty09:45
NCommanderI meant the equivelent of vmx for AMD09:46
Keybuk--09:46
MithrandirNCommander: svm, then09:46
* soren nods09:46
directhexsoren, i turned it on in the replacement "vpro" bios: flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr lahf_lm09:46
directhexsoren, the regular bios doesn't have the functionality, full stop09:46
sorendirecthex: So no chance of seeing the full cpuinfo with the regular bios?09:47
NCommandersoren, some processors only report abilities when they are actually active09:48
directhexsoren, not unless i boot XP and re-flash09:48
NCommandersoren, i.e., last time I checked, lm only shows up when my process is actually in long mode09:48
NCommanders/process/processor09:48
directhexsoren, an HP dc7700, if you care09:49
* mvo happily accepts the award from Keybuk and put it into his trophy glass cabinet09:50
Keybukspeech!09:50
NCommandersoren, you seem suprised that cpuinfo isn't always static09:51
directhexsoren, http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=3232108&prodTypeId=12454&prodSeriesId=3232029&swLang=13&taskId=135&swEnvOID=1093#12009:52
directhexsoren, the "HP Compaq Business Desktop System BIOS (786E1 BIOS)" download cannot do vmx09:52
directhex"HP Compaq dc7700p Business Desktop System BIOS for Intel vPro Technology (786E1 BIOS)" can09:52
sorenNCommander: Not really. I'm just puzzled that it's the case for vmx/svm. I never encountered a system where it wasn't reported in cpuinfo, if the CPU had the capabilities.09:53
NCommandersoren, well, I would think its a safety feature09:53
sorenHow so?09:53
Chipzzhrrrrm09:53
ChipzzError in /home/chipzz/.mutt/sidebar, line 5: sidebar_width: unknown variable09:53
NCommanderPrograms trying to use VTx are supposed to check with the BIOS to make sure it actually would be safe to do so09:54
Chipzzbut the changelog documents the sidebar patch as being applied?09:54
NCommanderVirtualization solutions like Xen run guest OSes in Ring 1, and only fault to -1 (VTx) when needed09:54
NCommanderI would guess that this behavior exists to make sure no instructions are not run in the wrong ring by accident09:55
Chipzzsoren: ^^09:55
Chipzzsince you did the last upload09:55
NCommandersoren, I have absolutely no idea if thats the truth, but its the only plausable explication I can think of (lm is the other mode that sometimes seems to disappear and reappear as well ...)09:55
sorenChipzz: Do you have mutt-patched installed?09:56
Chipzzjust mutt; but the mutt changelog documents the patch as being applied09:56
* soren is using the sidebar patch quite happily.09:56
sorenChipzz: Yes. To mutt-patched.09:56
Chipzzare mutt and mutt-patched build from the same source?09:56
sorenYes.09:56
Chipzzah, that would explain09:56
Chipzzquite misleading though09:57
sorenWhat is?09:57
directhexNCommander, it's true - kvm was what told me i had no vmx flag09:57
Chipzzthat the changelog of mutt documents a feature being applied in mutt-changed09:57
Chipzz(yes I know packages built from the same source have the same changelog;09:58
NCommanderdirecthex, wait, kvm told you?09:58
Chipzzhence my comment about "quite confusing")09:58
directhexNCommander, well, the init script09:58
NCommanderdirecthex, that error message usually means the BIOS isn't allowing access to ring -109:58
Chipzzanyway problem fixed09:58
directhexNCommander, the init script just looks for "vmx" or "svm" in cflags, and if you have neither, says "                log_failure_msg "Your system does not have the CPU extensions required to use KVM. Not doing anything.""09:59
directhexcpuflags, even09:59
NCommanderOh, I see09:59
* NCommander notes VTx is an amazing hack10:00
Chipzzsoren: maybe make a note in the changelog about mutt-patched?10:00
NCommanderdirecthex, you know how VTx works?10:01
directhexNCommander, black magic and voodoo? that's enough for me10:02
NCommanderlol10:02
sorenChipzz: I'm not going to change earlier changelog entries. I might add a reference to mutt-patched in mutt's long description, though.10:02
pittimvo: I just started upgrading my wife's computer to 8.10; u-n told me about the missing nvidia driver10:04
pittimvo: however, since version -96 now works again in intrepid-proposed, we should update u-m as well for that; is that already on your radar, or shall I open a tracking bug for this?10:04
pittimvo: (or a new task, rather)10:04
mvopitti: its on my radar, tseliot mentioned it yesterday10:06
* pitti hugs mvo10:06
mvopitti: I just need to add checks so that we ensure we never end up with the non-working version10:07
pittimvo: that's similar to the jockey update (bug 293107)10:08
ubottuLaunchpad bug 293107 in jockey "Offer nvidia driver version 96 again" [High,Fix committed] https://launchpad.net/bugs/29310710:08
Chipzzsoren: I wasn't suggesting that. but in the next changelog maybe?10:08
pittimvo: I think we can safely do it once the new driver is in intrepid-updates, right?10:08
pittimvo: btw, version 71 still seems to fail10:08
sorenChipzz: Like " * Oh, look! There's a package called mutt-patched, too!" ? :)10:09
mvopitti: oh, good to know10:10
Chipzzsoren: :) or just mentioning that the patch is only applied to mutt-patched next time updating the patch?10:10
Treenaks11:05 <@     _mike_> zo, alle newszilla dreaders zijn nu debian/lenny, met de  laatste diablo code, en een openvz 0-master10:11
Treenaks11:05 <@     _mike_> <phew>10:11
TreenaksOOPS10:11
Treenaks--------------------------------------------------------------------------------10:11
mvopitti: yeah, I think so too. when its in -updates we should be fine10:11
ChipzzTreenaks: where you from?10:12
Treenaksso.. on-topic, what about disabling middle-button emulation (left+right=middle) for jaunty?10:12
directhexTreenaks, it's disabled? :(10:13
Treenaksdirecthex: no, it's enabled10:13
directhexTreenaks, thank god10:13
Treenaksdirecthex: that's why I pasted something I didn't want to paste10:13
KeybukTreenaks: get a better IRC client?10:16
Keybukxchat requires you to press Enter after pasting10:16
directhexi wonder if smuxi does10:17
TreenaksKeybuk: so does irssi, but only if you paste more than 3 lines10:17
TreenaksKeybuk: but good idea, thanks.. I'll see if I can configure that10:17
KeybukTreenaks: the real problem there is using an IRC client that is blissfully unaware of the fact you're running in a GUI10:18
Keybukthere are plenty of real GUI clients available ;)10:18
TreenaksKeybuk: make a screen for X apps and I'll consider them ;)10:19
Keybukit's called vnc :P10:19
Treenakss/screen/gnu-screen like program/10:19
liwfor those who use irssi so that they can run it under screen, I note that bip seems to work very well with xchat: you can quit xchat whenever you like, and then re-connect to bip (an irc proxy) when you feel like being flooded again10:19
directhexreally?10:21
directhex-directhex- VERSION bip-0.7.210:21
Keybuksee, I just don't bother10:26
Hobbseeliw++10:26
Keybukand accept that people will talk about me when I'm not here10:26
KeybukI don't let it worry me10:26
ion_Middle button emulation for the win.10:27
liwKeybuk, I don't care if people talk about me, but I find it practical to know when they talk _to_ me, without my having to monitor irc constantly10:27
liwKeybuk, there is an unfortunate tendency amongst people to wait for people to get onto irc rather than e-mail them :(10:27
Keybukif you're eating dinner, or asleep, why does it matter if they're talking to you?10:28
Keybukyou can't do anything about it - so there's no real point to being online10:28
Keybukand the best bit is10:28
Keybukif you're not online10:28
Keybukthey stop trying10:28
liwthat's certainly a valid point of view, I don't disagree with that at all10:28
liwbut people have expressed annoyance if I*m not on irc throughout my entire work day10:29
Keybukwhy would you disconnect during your working day?10:32
liwto be able to concentrate for a while, without having xchat interrupt me10:32
sorenKeybuk: But you might miss out on people talking *about* you. :(10:33
Keybukliw: I just ignore it10:33
liwKeybuk, you're a better man than I am (but we knew that)10:33
Keybukthen again, I have very minimal notification10:33
Keybukit just places an icon in the notification area at the top10:33
cjwatsonsuperm1: it's fine to use the metapackages until then10:35
cjwatsonwgrant: it got stuck at libxcrypt; I fixed that by hand and am rerunning10:35
cjwatsonsoren: vim> go ahead if you haven't already10:36
sorencjwatson: Almost done. Got distracted. :)10:37
cjwatsonmvo: your debconf changelog is bizarre; the remaining changes allegedly include a backport from trunk, but those changes were in the Debian upload you merged10:43
cjwatsonmvo: could you commit your changes to bzr, too?10:45
cjwatsonwith a 'bzr merge' there10:45
mvocjwatson: my only change to debconf (that I can remember is): 1.5.23ubuntu2 - is that the one?10:48
mvoand that change is in bzr10:48
cjwatsonoh, it was Scott10:48
cjwatsonKeybuk: ^-10:48
Keybukcjwatson: ?10:49
cjwatsonKeybuk: you uploaded debconf, apparently10:49
Keybuka merge?10:49
cjwatsonyes10:49
Keybukright10:49
cjwatsonKeybuk: you didn't commit the changes to bzr, and the merge changelog entry was wrong10:49
KeybukI know10:50
cjwatsoncan you please fix that?10:50
KeybukI can't retroactively fix the changelog message10:50
cjwatsonMoM should have a warning for packages maintained in bzr10:50
Keybukpackages maintained in bzr are a pain in the arse10:51
Keybukit's impossible to ever get them right10:51
KeybukI won't touch it next time10:51
cjwatsonthey're trivial to get right if you use bzr ;-)10:51
stefanlsdKeybuk: i agree with cjwatson. We just need a process10:51
seb128the issue is that not everybody uses bzr10:51
Keybukyou have to apt-get the source10:51
Keybukthen you have to get the branch10:51
cjwatsonnot in this case10:51
Keybukthen you have to figure out what's in the branch that's not in the source10:51
Keybukand somehow overlay them over each other10:51
Keybukand then figure out where you got to10:52
Keybukand then probably do other things to make it build10:52
Keybukit's utterly stupid10:52
cjwatsonseb128: no, the issue is when people decide not to use bzr even when the package already does10:52
cjwatsonseb128: I don't mind (well, I do, but :-) ) that not everyone uses bzr right now; it's the clash that's awkward10:52
Keybukno10:52
seb128right10:52
Keybukthe issue is that bzr is fundamentally incompatible with the way we do source packages10:53
Keybukand we're trying to force people to use it10:53
Keybukand it doesn't work10:53
seb128but everybody doesn't want to spend half an hour rather than 5 minutes just to fight bzr10:53
cjwatsonKeybuk: in this case, the bzr branch is sufficient; I don't believe any overlaying is necessary10:53
pittiKeybuk: apt-get source warns, and you have debcheckout for convenience10:53
seb128I just stopped touching packages in bzr due to that10:53
cjwatsonKeybuk: I try to make that be the case for all my packages10:53
cjwatsonor at least have it be obvious when it isn't10:53
mvoKeybuk: I find bzr a huge help for my package maintainance in many ways10:54
cjwatsonKeybuk: so AFAICT you're complaining about something which is true for other packages but not this one10:54
wgrantI think much of the problem is that bzr usage is very inconsistent.10:54
cjwatsonwgrant: yes, I agree with that10:54
Keybukcjwatson: my compaint is the time it takes to figure out what package this one is10:54
Keybukwhether it's one that's easy, or hard10:54
Keybukand that you still have to assume it's hard to find out it's easy10:54
cjwatsonKeybuk: so leave it alone if you don't want to put in that effort10:54
Keybukand it's a waste of time10:54
seb128mvo: that's likely because you have complicated packages, it's just annoying when doing simple changes10:54
Keybukcjwatson: like I said, I'll leave it alone next time10:54
cjwatsondon't screw it up for other people10:54
pittiKeybuk: but I think a MoM warning if a package has Vcs-Bzr:.*launchpad* would be utterly helpful10:55
seb128mvo: but we already had this discussion ;-)10:55
Keybukpitti: I'd rather just have MoM ignore those packages10:55
mvoseb128: indeed :)10:55
Keybuksince it clearly will never be the right thing10:55
cjwatsonKeybuk: I use MoM as a to-do list even while ignoring its *output*10:55
pittiKeybuk: it can point out the need for merge, but not output anything, right10:55
cjwatsonKeybuk: so ... what pitti said10:55
pittiKeybuk: maybe its report should point out "debcheckout" or so10:55
Keybukcan't do that with the current design10:55
Keybukeither it generates a merge, or it doesn't10:55
cjwatsonmake it spanner the merge somehow10:56
Keybukwhy?10:56
Keybukwhatever it does will clearly be wrong10:56
Keybukjust like whatever anyone does that doesn't know the package will clearly be wrong10:56
Keybukthis is why I hate bzr packaging10:56
pittithe need for merging isn't wrong10:56
Keybukit, ironically, makes it impossible to maintain packages as a team10:57
pittis/impossible/different/10:57
pittiand that's what we need to improve10:57
Keybukyes, we can spend a lot of time working on the procedures10:58
Keybuktraining10:58
Keybukgetting everybody to do things the right way10:58
Keybukand we'll end up with something almost as good as what we had before10:58
Keybukonly a little extra work10:58
pitti(wasn't it you who wrote NoMoreSourcePackages? :-) )10:58
cjwatsonI think there should be a rule that every package that's in bzr should either be buildable straight from the branch, or should fail in an obvious way with directions as to what to generate (but preferably the former, and moving towards universally the former)10:58
cjwatsonthere are not enough packages in bzr right now to make that terribly hard to enforce10:59
pittiyeah, if debcheckout+debuild doesn't work, that's a bug10:59
mvodoes that mean we should keep it as it is and abandon the whole maintain-packages-in-bzr idea?10:59
Keybukpitti: the whole point of that document was my assertion that the *only* way do to bzr packaging was to *only* do bzr packaging10:59
pittiKeybuk: I fully agree :)10:59
Keybuktrying to package both ways simultaneously is just pain for pain's sake10:59
cjwatsonthe problem with that assertion is that it's false. I get by just fine otherwise10:59
pittiyes, I don't argue that10:59
Keybukbzr packaging fails the moment you have an .orig.tar.gz11:00
Keybukbecause you can't put that in bzr in a way that works11:00
pittino, that's not true11:00
pittiyou are just not using the tools we have for that11:00
Keybukthe tools we have are hacks11:00
Keybukthey get one bit from other there, and the other from other *there*11:00
Keybukand end up only slightly worse than apt-get source11:00
pittiwell, apt-get source fetches orig.tar.gz and diff.gz and applies that11:00
Keybukwhich is what I find ridiculous11:00
pittidebcheckout fetches orig.tar.gz and the branch and applies that11:00
pittiI don't see the fundamental difference11:00
pittiwell, I do appreciate that it could be cleaner11:01
pittibut it works as well as apt-get source, IMHO11:01
KeybukI disagree11:01
cjwatsonfixing this is one of the reasons James has put lots of effort into bzr-builddeb11:01
Keybukyou can't do a diff.gz with that11:01
seb128it's just extra steps, slower and a different workflow you need to learn11:01
Keybukand none of this actually gives us anything we didn't have before11:02
Keybukin fact, it's worse11:02
Keybukbecause in the brave new bzr world you can't use merge-o-matic anymore11:02
Keybukso merges become hard work again11:02
pittiseb128: if someone uploads jockey or apport without committing to bzr, it's much slower and extra steps for me to clean up after him...11:02
cjwatsonKeybuk: merge-o-matic gets things wrong when bzr merge doesn't11:02
Keybukunless you're lucky enough to be Colin and only focus on things which are native and in revision control upstream along with their packaging11:02
pittiKeybuk: merges are a snap of a finger with bzr11:02
seb128pitti: right, but you just discourage people to fix things on your packages then11:02
cjwatsonyour claim that it's worse is based on the theory that merge-o-matic is at least as good11:02
Keybukcjwatson: such as?11:02
pittiseb128: and doing serious upstreamish development work without revision control is insane11:02
Keybukyou've not filed any bugs11:03
seb128pitti: we don't discuss upstream work but packaging there11:03
pittiKeybuk: I don't use MoM  for merging cups or hal -- I just use "bzr merge", and that just works11:03
cjwatsonKeybuk: it has less context for changes; I don't see it as something MoM can fix11:03
Keybukcjwatson: it has the same context11:03
pittino, MoM doesn't have history11:03
Keybukyes it does11:03
Keybukit might not be quite as discreet as the commit logs11:03
Keybukdepending on whether the author releases often or bunches things up11:04
Keybukbut otherwise it's basically doing the same thing11:04
pittibut it can't tell that patch A has been applied as modified patch A' upstream and thus is merged11:04
Keybukin fact, MoM tries to be a bit smarter about the merge than bzr11:04
cjwatsonKeybuk: lucky enough? ignoring the native thing which I really don't think is as important as you make out, the reason I'm in this position is that I've put effort into it11:04
Keybukcjwatson: and that means you're the only person who can really make changes to those packages now11:05
Keybukbecause you're the only person who understands the way you've done it11:05
Keybukwhich is almost certainly different to the way pitti does it11:05
cjwatsonKeybuk: demonstrable bollocks11:05
Keybukand probably different to the way mvo does it11:05
cjwatsonyou can tell this from the fact that other people change them11:05
pittiI had no problem so far committing changes to d-i or update-notifier11:05
Keybukand get ranted at on IRC for fucking it up11:05
seb128right, because you put the required efforts to figure how to update those and you are used to bzr so it's likely something easy for you11:06
cjwatsonthe people who utterly ignore stuff that's in place will screw it up, sure; in other cases I haven't had many problems actually11:06
cjwatsonpeople generally get it right11:06
KeybukI didn't get it right11:06
Keybukand I don't think I'm incompetent11:06
pittiseb128: that may be true, yes11:06
cjwatsonyou ignored the vcs-bzr, which I think tools could have helped you with11:06
cjwatsonif you hadn't, I'm confident that you would have got it right11:07
Keybukto see the vcs-bzr, I had to get it from bzr11:07
mvoasac: could you please check #272314 ? I think you were a bit quick with making it "invalid" ;)11:07
Keybukit's a chicken and egg11:07
cjwatsonhuh?11:07
pittiKeybuk: no,apt-get source warns you11:07
cjwatsonthe vcs-bzr field is in the package as uploaded, and as pitti says ...11:07
Keybukat no point there, did I run apt-get source11:07
seb128pitti: I don't even know where to push my changes usually, I apt-get source which gaves me a bzr command, which I use and gives me a readonly checkout and there I'm stucked11:07
cjwatsonKeybuk: and, like I say, I think MoM should have warned somehow11:07
pittiKeybuk: right, you downloaded from MoM, which brings us back to the original problem of MoM not warning about it :)11:07
Keybukand as I've frequently filed bugs - apt-get source has never given me a bzr warning11:07
cjwatsonhence "I think tools could have helped you"11:07
Keybukcjwatson: patches welcome11:08
sorenKeybuk: You could put the info in REPORT and have grab-merge warn you.11:08
mvo(asac: and adding a update-manager taks for that matter)11:08
cjwatsonapt-get source often gives me bzr warnings11:08
cjwatsonso "WFM" is unfortunately the best I can say at the moment ...11:08
cjwatsonanyway, midwife visit11:08
pittiseb128: debcheckout :)11:08
Keybukquest tmp% apt-get source debconf11:08
Keybukdpkg-source: extracting debconf in debconf-1.5.23ubuntu211:08
Keybukdpkg-source: info: unpacking debconf_1.5.23ubuntu2.tar.gz11:08
seb128pitti: what is that?11:08
Keybuksee, no warning11:08
pittiseb128: convenience script to fetch orig, branch, and set it up correctly11:09
liwKeybuk, weird: NOTICE: 'debconf' packaging is maintained in the 'Bzr' version control system at:11:09
seb128pitti: should apt suggest than rather than bzr get on http locations?11:09
Keybukif bzr is the correct way to get a package11:10
Keybukthen apt-get source should *not* bitch at you11:10
pittiseb128: yes, very much so; in fact, it should use "lp:~/ubuntu-core-dev/debconf/ubuntu", which works for read-only as well as push11:10
Keybukapt-get source debconf should automatically use bzr to fetch it properly11:10
pittimvo: ^11:10
asacmvo: sure11:10
asaclet me look11:10
mvoKeybuk: I can add that (for bzr+lp branches)11:10
pittiKeybuk: that, or at least a stronger warning if DEBEMAIL =~ /ubuntu/ is a good idea11:10
pittimvo: and advocating http:// is really outdated now, I think11:11
Keybukpitti: warning is silly11:11
KeybukI really never read apt output11:11
pittimvo: but I guess it takes that straight from Vcs-Bzr11:11
Keybukit's all random crap about package lists and stuff11:11
Keybukwhich is why it's turned off11:11
pittiKeybuk: it could just fail11:11
Keybukpitti: that's not being helpful either11:11
mvopitti: yes11:11
Keybuk"do this" ... FAIL!11:11
Keybukif apt knows what you're supposed to have done instead, it should just do that11:12
mvoKeybuk is right, it should to it automatically, problem is how to ensure the diff gets sent back to lp when its finished?11:12
asacmvo: well. ia32libs wasnt updated for them11:12
liw"apt-get source" can work (local mirror) whereas bzr might fail (no Internet access)11:12
pittimvo: what about apt-get source just calling debcheckout if it sees Vcs-Bzr:.*launchpad ?11:12
Keybukliw: in which case, according to colin, you shouldn't be allowed to fetch the source package11:12
asacmvo: should be a lower depends bound ... true11:12
mvoasac: right, that clearly indicates that there is a versionized dependency missing, no?11:12
pittiKeybuk: fetching is fine, uploading is disallowed (which is why we are currently doing it that way)11:13
asacmvo: but still those folks claimed that multiverse got disabled ;)11:13
mvoasac: I asked for the upgrade log, in general, we keep multiverse, but of course there might be a bug (or corner case)11:13
pittibut yeah, it's a tricky problem11:13
mvoasac: yeah, that worries me a bit :/11:13
asacmvo: maybe update manager could do better to see that there are packages from a now-disabled component?11:13
pittimaybe we should just try to make apt-get source call debcheckout, and see who complains11:13
asacmvo: lets assume user disabled it ;) ... that could be the case for sure11:14
mvopitti: yes11:14
asacmvo: or maybe apturl :)11:14
pittiit coudl still download the package with --force, or so11:14
* Keybuk didn't know about debcheckout, btw11:14
Keybukwhere was that announced?11:14
asacmvo: but update-manager could also know that there are packages from multiverse and do something imo. otherwise the upgrade would fail too i guess11:14
mvoasac: well, what should it do in this case? I can not embed special knwledge into it for each package, if the dependencies are fine, u-m will install it11:14
pittiKeybuk: devscripts 2.10.8, Tue, 11 Sep 200711:15
asacmvo: how? if multiverse isnt enabled the upgrade will either fail (because the dep cannot be fulfilled) or removed?11:15
mvopitti: I think calling debcheckout if fine, but how do we ensure that the change in bzr are then sent back to LP? or does debcheckout do that?11:15
Keybukpitti: I can't see any ubuntu-devel posts introducing it?11:15
pittiKeybuk: but right, that's why apt-get source should point it out/JFDI11:15
mvoasac: or kept at the same version. but it does something sensible, even if that is removing the package11:15
Keybukwhich is an interesting point11:15
Keybukwe're getting an increasing number of DTRT tools11:15
Keybukyet you can only learn about them by osmosis, since we don't really document them anyway11:15
asacmvo: true. i think if package comes from a none-ubuntu archive it should be removed if it would cause problems to keep it at same version11:16
pittimvo: you mean teaching people how to use "bzr commit"?11:16
mvoasac: right, but how should u-m know? it can not have special knowledge for each package, if its not encoded in the dependencies, there is little I can do AFAICS11:16
asacmvo: but cant we do better if people have things from ubuntu archive ? maybe an index of package names mapped to archive section?11:16
mvopitti: yes11:16
asacmvo: hmm ... isnt the info to identify a package as being from multiverse in the cache?11:17
mvopitti: it sounds silly, but you did not have to do it with apt-get source / dput11:17
asacmvo: like in the Pool file name?11:17
Keybukpitti: it's a shame that Vcs-Bzr isn't in the changes file :-/11:17
asacbut yeah. lets keep this as a dependency bug11:18
mvoasac: it is, but why should it tread multiverse differently than say universe?11:18
mvoor restricted ?11:18
pittimvo: well, I don't think we can pretend to not use bzr11:18
asacmvo: no it should treat all that way11:18
pittimvo: if we'd do that, we wouldn't need it in the first place11:18
asacmvo: if you hav a package for which the section was disabled and that comes from ubuntu archives, we can consider to enable that pool for upgrade11:18
mvopitti: I agree - I think i just need to add a message explaining that bzr commit is required or something like this11:19
Keybukactually11:19
pittimvo: point to https://wiki.ubuntu.com/BzrMaintainerHowto ?11:19
Keybukthis is damned hard11:19
Keybukwe end up with three different Vcs-Bzr fields11:19
pitti(which should get an update...)11:19
Keybukone from BASE, one from LEFT and one from RIGHT11:19
mvoasac: that information is not recorded (yet) if the user commented out his repos11:19
Keybukwhich one do we believe?11:19
Keybukand how do we deal with them being different?11:19
mvoasac: but yeah, having this information "Installed-From" would be *really* useful11:19
pittithe one from ubuntu11:19
mvoasac: for liw and his system-cleaner for example11:20
asacmvo: which information? i can currently look at apt-cache show and see the poolname in the filename11:20
Keybukpitti: two of those may be ubuntu ;)11:20
Keybukin fact, three of them may be in some circumstances11:20
pittiKeybuk: well, RIGHT is Debian, and LEFT is what you are just generating, isn't it?11:20
Keybukno11:20
mvoasac: right, now try to comment out multiverse and do that apt-cache policy thing again11:20
asacmvo: Filename: pool/multiverse/f/flashplugin-nonfree/flashplugin-nonfree_10.0.12.36ubuntu1_amd64.deb11:20
pittiKeybuk: ah, no, LEFT is current ubuntu, RIGHT is current Debian11:20
mvoasac: or try it in a version that is no longer downloadable (because there is a new version in jaunty and the old one got removed from the archive)11:20
pittiKeybuk: so, "LEFT" is the right Vcs- field11:20
Keybukpitti: not so much11:21
asacmvo: ok ... i believe you ;)11:21
Keybukall three can come from the same distro11:21
Keybuk.e.g initramfs-tools11:21
pittiKeybuk: but as I said, it's not really necessary for MoM to do the merge; it is actively wrong to upload it11:21
KeybukBASE might have been in ubuntu first11:21
mvoasac: we should talk about this at uds, the "record where it comes from" idea is really good11:21
KeybukLEFT and RIGHT might also have been in ubuntu11:21
* mvo needs to run for lunch11:21
Keybukwell, normally not, but it's possible11:21
Keybukthe problem is that just about every debian/control we're talking about inherently has a conflict11:22
Hobbseewhen is the ETA for moving everything to bzr?11:22
Hobbsee(is there one?)11:22
Keybuksince the apparent change made to everything is to change the Vcs-Bzr to point to launchpad11:22
Keybukpitti: the problem is that MoM has to do the merge11:22
Keybuksince the information is in debian/control11:23
Keybukwhich it only has when doing the merge11:23
pittiKeybuk: it's also in the .dsc11:23
Keybukis it?11:23
pittiwell, it's in Sources.gz, so it has to11:23
pittiIt's VCS-Bzr:11:23
asacmvo: is that fixable in a SRU (for new upgraders) at all? will update-manager look at -updates for updates or do an intermediate step to "plain" first?11:24
Keybukinteresting11:24
Keybukhere's a thought11:25
asacmvo: or do we need a tweak as hardy SRU now?11:25
Keybukgrab-merge could branch the bzr repository into a temporary directory11:25
Keybukand move the .bzr into the directory the merge result is unpacked into11:25
pittiand auto-add the new files in debian/ ?11:26
Keybuknot auto-adding would make people manually check a bit more carefully11:26
Keybuklifeless: around?  I feel momentarily evil11:26
pittisure11:26
KeybukI wonder if I can fake a bzr conflict for the conflicted files :p11:26
pittiwell, I don't use grab-merge, but if many people do, that sounds helpful11:26
asacfake a conflict? for the not added files?11:27
pittifor the real conflicts in the files, I figure11:27
Keybukasac: for the ones with MoM conflict markers in them11:27
sorenKeybuk: .bzr/checkout/conflicts11:28
asacoh. so we still want to do our own merge logic and not bzr merge?11:28
pittiKeybuk: but that would still not record the merged revisions from trunk11:28
pittiKeybuk: so you'd break bzr merge11:28
Keybuksure11:28
pittiso if debian/trunk is in bzr, doing that would be wrong, too11:28
Keybukso which header field is that documented? :p11:28
pittiKeybuk: Debian's Vcs-*? :-)11:29
Keybukor does that require personal knowledge of the package11:29
pittiwe only need to consider Vcs-Bzr, I think11:29
Keybukpitti: there doesn't seem to be a standard for those11:29
pittiI do have bzr imports for vcs-svn, too11:29
KeybukI've seen people using both XS-Debian-Vcs-Bzr and XC-Original-Vcs-Bzr11:29
pittibut since svn doesn't really support branches and merges, it doesn't matter11:29
sorenKeybuk: The latter is certainly wrong.11:29
Keybuksee11:29
Keybukthis is the problem11:29
pittiKeybuk: no, scratch that11:29
pittilook at the debian .dsc11:29
sorenKeybuk: It needs to be XS- at the very least.11:29
Keybuksoren: I mean XS11:29
Keybukpitti: look at it for?11:30
KeybukVcs-Bzr ?11:30
sorenKeybuk: There was some discussion a long time ago about whether to use Debian or Original.11:30
pittiKeybuk: yes11:30
Keybukwhat do you do in that case?11:30
pittiKeybuk: I guess that only really affects d-i11:30
sorenKeybuk: I'm quite sure we agreed Debian was correct.11:30
pittiKeybuk: don't use MoM11:30
Keybukdebconf uses Original ;)11:30
Keybukpitti: so how do we document which packages to use MoM for and which not to?11:30
Keybukyou see my point here11:30
Keybukwe've ended up in the situation where no developer can touch anything for fear of getting it wrong11:30
pittiKeybuk: If Ubuntu has a Vcs-Bzr:, I would discourage MoM11:30
pittiotherwise use MoM11:31
pittiand if Debian has a Vcs-Bzr, too, MoM shouldn't output anything, since uploading it breaks bzr merge11:31
pittiadmittedly having just ubuntu in bzr, and not debian/trunk, is utter crack11:31
Keybukwhy would you discourage MoM in the former case?11:31
pittiand I doubt that many people use that actually11:32
pittisince it makes merges so much harder11:32
Keybukif you're just committing uploads to bzr, the MoM upload is worth committing11:32
KeybukI don't agree11:32
KeybukI think bzr is making the merges so much harder11:32
pittiKeybuk: well, discourage, or use your magic grab-merge approach11:32
sorenKeybuk: https://lists.ubuntu.com/archives/ubuntu-devel/2007-March/023379.html11:32
pittiKeybuk: just keeping ubuntu in bzr and not the debian side is, IMHO11:32
pittiI did it long enough, and it was a PITA11:32
pittinow I import debian's svn to bzr and merge from that11:32
pittiso much easlier11:32
Keybuksee, everyone's doing it differently ;)11:33
pittiwell, "just ubuntu in bzr" -> pain, discourage, not document11:33
ScottKpitti: I thought I'd gotten that Spamassassin SRU you just accepted rejected.  It's got two problems.11:33
pitti"import deiban into svn" -> love, and you don't need MoM11:33
ScottKpitti: 1.  I forgot to add the patch to 00list, so it doesn't get applied.11:33
sebnerpitti: will the "old" way once gets disabled so we are forced to use bzr?11:34
pittiScottK: whoops, that slipped my review (argh too many SRU reviews today); sorry11:34
ScottKpitti: 2.  I uploaded it to dapper-updates, not dapper-proposed (so it's just as well actually the patch wasn't applied).11:34
ScottKpitti:11:34
ScottKpitti: No problems.11:34
ScottKpitti: There's a fixed one I just uploaded.  I'd appreciate it if you'd accept it.11:34
pittiScottK: thanks, will do11:34
pittisebner: which old way?11:34
ScottKpitti: Great.  Thanks.11:34
sebnerpitti: the normal way we work on packages now ^^11:35
Keybukpitti: can you think of an unmerged package using bzr?11:35
pittiKeybuk: hal11:35
pittiKeybuk: but as I said, I have debian in bzr, too, so all I do is "bzr merge", and it's happy11:35
Keybukhttp://merges.ubuntu.com/h/hal/REPORT11:36
Keybukthat detected that you have ubuntu in bzr \o/11:36
pittisebner: maybe once we have everything in bzr, but notuntil that11:36
Keybukbut you're missing vcs-bzr for the debian version :p11:36
pittiKeybuk: that's because debian is in svn11:36
pittiVcs-Svn: svn://svn.debian.org/svn/pkg-utopia/packages/unstable/hal11:36
Keybukand you use bzr-svn?11:37
pittiyes11:37
Keybuksee11:37
sebnerpitti: how long will this take? I suppose you are already actively migrating?11:37
Keybukhow is another developer merging hal when you're away supposed to know this stuff?11:37
pittisebner: we have some prototypes, but don't hold your breath11:37
Keybukthe sheer amount of magic required to merge hal that's only in your brain is worrying to me11:38
HobbseeKeybuk: no one's else is insane enough to merge hal.11:38
pittiKeybuk: as long as he commits it to bzr, I don't mind11:38
pittiKeybuk: having debian in bzr is making things easier for *me*11:38
Keybukpitti: but you've said yourself, you'd rather they didn't because it'd be wrong11:38
pittiif someone else wants to do it the hard way, and doesn't ask me, *shrug*11:38
Keybukthe problem is, by making it easier for you, you're making it harder for everyone else11:39
pittiKeybuk: no, only if debian/trunk is in bzr, too11:39
pittiKeybuk: why? that I have debian hal in an svn-imported bzr is totally opaque to anyone else?11:39
pittiand that I have ubuntu hal in bzr is obvious due to vcs-bzr11:39
Keybukunless they're trying to merge11:39
pittiyou can just commit a manual merge11:40
pittithat's just bad if trunk/debian is a real bzr branch, since then you don't record the merged revisions11:40
Keybukor they can just upload it as normal, and you can sort it out later? :)11:40
pittibut for svn that doesn't matter anyway, because svn doesn't know11:40
pittiKeybuk: "normal" in the sense of committing the changes to bzr without worrying at all about the debian svn, yes11:41
KeybukI mean just dupload11:41
pittioften people just upload without committing, so I just prod them to send me the diff or commit afterwards11:41
mvoasac: that is fixable, update-manager will use the latest stuff in the archive11:41
sebnerpitti: kk11:42
cjwatsonI don't actually mind when people upload rather than committing, since I can just ask them to commit; it doesn't normally turn into an hour-long argument about life the universe and everything11:43
cjwatson(and I have committed stuff on other people's behalf before)11:44
cjwatsonpitti: is your Debian hal branch lp:~ubuntu-core-dev/hal/debian ?11:47
cjwatsoncode.launchpad.net/hal is where I would naturally look for this stuff11:47
pitticjwatson: yes, I push it there; updating now11:48
pittiit's just a bzr-svn alioth <-> lp gateway11:48
pittithis is a setup which I don't actually *like* and which should be much easier11:48
pittibut well, it's a package that I work on a lot, so doing that initial setup is worth it11:49
cjwatsonI agree, it ought to be lp:debian/hal11:49
cjwatsonand automatically imported11:49
pittisince you lose merge tracking if you do another svn import11:49
pittisince svn is just so <censored> <beep>11:50
cjwatsonpresumably, though, pulling the branch from LP, running 'bzr pull' with bzr-svn installed, and pushing is fine11:50
cjwatsonthat should probably be in the branch whiteboard11:50
Mithrandirpitti: uhm, svn does merge tracking now, you know that?11:50
pittiMithrandir: oh? since when?11:51
Mithrandir1.511:51
pittiwow, that brings it on par with cvs :)11:51
Mithrandirso intrepid + hardy-backports.11:51
Keybukhttp://pastebin.ubuntu.com/67874/11:51
Keybukthat turns out to be quite easy11:51
ograMithrandir, dont mix intrepid with hardy-backports :P11:51
Mithrandir*shrug*; unless bzr it doesn't change the on-disk format twice a week and then proceeds to whine at me.11:52
pittiKeybuk: I'd use Vcs.*launchpad11:52
Keybukpitti: that doesn't work for your packages11:52
Keybukthis will err on the false positive side11:52
pittiKeybuk: otherwise we'd catch all the alioth vcs-svn ones which we don't care about11:52
Keybukbut I think that's ok11:52
pittiKeybuk: my packages?11:52
Keybukie. hal11:52
Keybukit wouldn't show up the debian bit11:52
Keybukwhy would it have launchpad in it anyway?11:52
Keybukshouldn't it be Vcs-bzr: lp:~ubuntu-core-dev/hal/ubuntu ?11:53
pittiKeybuk: suppose package foo is in alioth svn, but not in bzr in ubuntu anywhere11:53
pittithen a standard non-VCS merge is the right thing11:53
Keybukpitti: then they'll get a warning11:53
Keybukand can figure out whether its safe to continue11:53
cjwatsonI haven't been using lp: so far, but maybe I should11:53
pittiKeybuk: yeah, if it's just a warning, that's in fact fine11:53
Keybukright, that goes at the bottom of grab-merge11:53
pitticjwatson: I don't use it in the Vcs-: fields, because I like them to be clickable11:54
cjwatsonthe thing about using lp: is that you can't c'n'p them into a web browser11:54
pittibut for bzr checkout/pull/push/get they work nicely11:54
cjwatsonso you have to have a separate vcs-browser field which is more fiddly11:54
pitticjwatson: but debcheckout is clever enough to translate them, I think11:54
Keybukcjwatson: the thing about not using lp is that it doesn't translate nicely into a writable or readonly url automatically11:54
cjwatsonKeybuk: yeah, I don't pretend to have a perfect answer there11:55
cjwatsonpitti: it is11:55
cjwatsonmaybe I should just bite the bullet and use vcs-browser11:56
cjwatsonI just don't want to be changing things round every five minutes since that's confusing too11:57
jernstbryce: ping?11:58
ograjernst, likely to early for him11:59
jernstI thought so too ;-), thanks11:59
pittibryce: do you want to do the inkscape merge? it's currently on my plate, since I tossed the recommends: around right before release, but you feel more attached to it :)12:05
pittisoren: ^ likewise, do you wnat to do virtinst?12:06
sorenpitti: I'll do virtinst, yes.12:07
pittisoren: thanks12:08
pittiargh, guys, pretty please forward patches to Debian12:13
=== thekorn_ is now known as thekorn
kwwiimvo: could you look at #293482 and confirm that it is not a compiz problem?12:16
asacTheMuso: your ppa is named here: https://wiki.ubuntu.com/MozillaTeam/Bugs/FlashAnswers :) ... anything else you would like to be asked on NEW sound bugs?12:19
ahasenackis there a way for apport to report the time of the crash?12:23
ahasenackI have a bug report saying that when a program called Me-TV was closed, apport reported a crash in landscape-sysinfo, which is clearly wrong12:23
ahasenackso I'm guessing apport is reporting an old crash12:23
pittiahasenack: yes, it's written into the report by default12:24
pittiahasenack: "Date:"12:24
ahasenackpitti: I must be blind then, I don't see it here: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/27195412:25
ubottuError: This bug is private12:25
pittiahasenack: oh, it's not copied to the LP bug report12:25
pittiahasenack: in fact it was doing it before, but I was asked to throw out redundant fields12:26
ahasenackpitti: only that field?12:26
ahasenackpitti: can you put it back please? :)12:26
pittiahasenack: how would it help you with that bug?12:27
pittiahasenack: yes, ignore the "me-tv" comment, it's clearly wrong12:27
pittiahasenack: you got one of those nice python segfault crashes12:27
ahasenackpitti: I would compare the date of the crash with the date of the bug12:27
pittiI'm regularly lost what to do with those, too12:27
pittiahasenack: it should be "5 minutes earlier" or so12:28
pittiahasenack: it apparently happened while a session was running12:28
ahasenackpitti: I was assuming that apport was reporting an old crash that was for some reason not reported when it actually happened12:28
pittiahasenack: apport pops up and reports straight after the crash happens12:28
pittiunless you don't have a running session, in which case it asks you when logging in12:28
pittibut that's not the case here, according to the description12:28
pittiahasenack: given that landscape-sysinfo is cron'ed every 10 minutes, I guess me-tv was just a coincidence12:29
ahasenackpitti: yes, that's what I'm thinking now12:29
ahasenackpitti: so, if the crash happened outside of a session and the user logged in only the next day into gnome, then we would get very different dates for the crash and the report, right?12:30
mvokwwii: "I get the same result with or without Compiz. As I already said, the12:30
mvofresh account experiences the same issue too." (last comment) so I doubt its a compiz issue12:30
pittiahasenack: yes12:31
kwwiimvo: yeah, in the meantime I am not sure if this guy is being honest in the report...thanks for checking12:32
ahasenackpitti: thanks12:33
mvokwwii: oh, ok - I double check here on my system12:33
mvoRiddell: for bug #291115 there is no "TEST CASE" in the description yet, is it sufficient to just use turkish locales to trigger the bug?12:39
ubottuLaunchpad bug 291115 in update-manager "[kde] Kubuntu Update Manager crash problem with Turkish language" [Undecided,Fix committed] https://launchpad.net/bugs/29111512:39
mvokwwii: works for me on a fresh system with and without compiz (just tested it on a freshly upgraded test system)12:48
Riddellmvo: yes12:54
mvoRiddell: thanks, I added a test case now, it would be cool if you could fill in the extact commands that are required (how to run adept to get the --proposed version of hte upgrader, how to switch default language with kde )13:05
mvodid we release note that evms was removed from the archive?13:12
sorenIt was?13:12
* soren lets out a sigh of relief13:13
mvormadison evms tells me its no longer in intrepid13:13
mvoit just is a pain for people upgrading with evms root13:13
mvoand update-manager will happily remove evms because its now obsolete13:13
KeybukI thought we kicked that out back in edgy or something13:15
Keybukah, universe in gutsy13:17
Keybukgone from intrepid13:17
mvobad for people with evms roots13:17
Keybuksync'd removal from Debian13:17
Keybukso we probably never noticed13:17
kwwiimvo: cool, thanks...I appreciate your help13:18
mvoaha, thanks13:18
Keybukcjwatson: removals.txt isn't updated anymore?13:18
mvoKeybuk:  I was wondering about that13:18
* mvo prepares a update-manager SRU for the two evms users13:18
Keybukmvo: one assumes if they had it installed, it wouldn't be removed?13:19
Keybukor does update-manager remove it?13:19
mvoKeybuk: update-manager removes everything that is obsolete unless its told otherwise13:19
mvo(obsolete == vanished from the archive)13:19
Keybukhow does it tell the difference between that and local packages?13:19
mvoKeybuk: it checks what is local before it updates the sources.list and then calcs the difference13:20
Keybukcunning13:20
Keybukmvo: who's the *other* evms user?13:20
mvoheh :)13:21
Keybukactually, I can think of two13:21
KeybukTollef and wasabi13:21
cjwatsonKeybuk: https://launchpad.net/ubuntu/+source/evms/2.5.5-26ubuntu2 logs the removal; bug 159585 is for the fact that removal data is spread over two places13:23
ubottuLaunchpad bug 159585 in soyuz "lp-remove-package.py does not log removals to our standard place" [Low,Confirmed] https://launchpad.net/bugs/15958513:23
* cjwatson nags that bug13:24
tseliotRiddell: do you know if there's something similar to the gnome-settings-daemon in KDE? For example something which loads the screen settings (resolution,etc.) on login?13:27
pittimvo: btw, no need to do a no-change upload of intrepid-proposed to jaunty; we can just copy-package it (which I usually do for SRUs if jaunty and intrepid versions are the same)13:36
pittimvo: also, you didn't build with -v, thus the bugs don't get autoclosed13:36
ogasawarapitti: yah, sorry for the extra noise with those 2.6.27.2 bugs that I had opened and closed.  It was an oversight on my part.13:49
pittiogasawara: no problem about the noise; I'm more worried about misunderstandings about the future SRU workflow13:50
ogasawarapitti:  I believe tim was under the impression people wanted an SRU bug report/patch13:50
pittiogasawara: hm, who? I'm fine with just one bug report, with a changelog13:50
pittiI want the kernel team to read the changelog and check for something fishy13:50
pittinot to create busywork for themselves and me to create tons of bug reports :)13:51
ogasawarapitti: agreed, that's why I had scripted opening the bugs for them.13:51
ogasawarapitti: let me talk with them, just a sec13:51
rtgpitti: while clumping all of the stable updates into one report makes SRU processing easier, it will make regressions a little more difficult to track.13:54
pittirtg: okay13:55
rtg'cause there is a pile of them. About 40 committed, another 57 in the pipeline,13:55
pittirtg: well, if you actually want to have one SRU bug per commit yourself, I'm fine; I was just under the impression that you didn't13:55
pittiI think I can easily counterattack ogasawara's script with a script to close SRU bugs when moving things to -updates :)13:56
ogasawaraheh13:56
rtgpitti: I was just trying to find a way to change policy so we could add stable updates. The mechanics don't matter to me.13:56
pittirtg: it seems easier to me to create bug reports about particular regressions when they are found, not in advance, but that might be just me13:57
rtgpitti: however, that being said, whoever is doing the work really needs to look at each patch.13:57
rtgpitti: that works for me as well.13:57
pittirtg: for a casual tester/reporter, it's not really feasible to find the commit that was responsible for the regresssion anyway13:57
rtgso, clump the stable updates into one SRU request, then create regression reports as they appear?13:58
mvoRiddell: is #241314 sru worthy?13:58
pittithat, or just use that one bug; I think it's a matter of common sense13:58
pittirtg: also, if we notice that we get like 5 regressions per stable pull, that's not a sign to change the bug reporting policy, but a sign that we shouldn't do it in the first place :)13:58
pittione regression is worse than 10 known bugs usually...13:59
rtgpitti: I guess experience will tell us if we're doing the right thing.13:59
pitti(unless they are of the data loss/security kind, of course)13:59
Riddellmvo: I wouldn't say so13:59
pittirtg: exactly13:59
mvoRiddell: ok, good14:01
tseliotRiddell: is there no equivalent?14:03
Riddelltseliot: oh sorry, no there's nothing which sets resolution as far as I know14:04
ogasawarartg: I'll open a master bug for 2.6.27.3 and 2.6.27.4 then and clean up those other bugs that got opened.14:04
tseliotRiddell: ok, thanks14:04
rtgogasawara: cool. I think that will constitute enough change that an upload is required.14:05
rtgpitti: in checking on https://edge.launchpad.net/ubuntu/+source/linux-backports-modules-2.6.27 I see that it needs building, but I can't find it in any of the Intrepid queues.14:07
rtgwhy are the buildd's so backed up anyway?14:07
pittirtg: the source is already accepted, so it's not in a particular queue (well, it's in "DONE")14:07
pittirtg: we have the initial jaunty sync wave, plus new langpacks14:07
rtgah, the DONE queue. 111K entries.14:08
rtghrmph. make that Jaunty stuff wait until _my_ builds are done.14:09
ScottKpitti: If you're still up for doing archiv'ish things, please have a look at intrepid backports for lintian, devscripts, and debootstrap.14:26
pittiScottK: seb128's archive day today :)14:27
ScottKpitti: OK.  Thanks.14:27
ScottKseb128: ^^^14:27
seb128oh right, I forgot about that14:27
seb128will have a look14:28
ScottKseb128: Thanks.14:28
seb128pitti: I got used to not touch the archive during the intrepid freeze ;-)14:28
tseliotRiddell: is it a bug the fact that Konsole doesn't remember its previous size when you launch it?14:32
Riddelltseliot: yes, fixed in trunk14:33
tseliotRiddell: ok, thanks god it's not a feature ;)14:33
danimohi14:45
danimoasac: ping?14:45
mvopitti: re bug #272199 - the reason this is not in intrepid already is that it breaks the string freeze (that was the reason why its not in gnome too). I can still do a upload if the regression is more imporant than the string freeze (I don't mind either way)14:50
ubottuLaunchpad bug 272199 in gnome-terminal "[intrepid REGRESSION] Missing option to disable "switch to tab" keyboard shortcuts" [Low,Confirmed] https://launchpad.net/bugs/27219914:50
pittimvo: not sure, but we did have that string until shortly before RC14:51
nxvlcjwatson: i'm not getting jaunty-changes's confirmation e-mail, is that list moderated?14:51
asacdanimo: ?14:51
cjwatsonnxvl: err, are you trying to mail it directly?14:51
mvopitti: well, we had it for about a week (added 2008-10-21 and removed 2008-10-3114:52
maxbBut the strings were in hardy, weren't they?14:53
tedgKeybuk: So, if MoM will do a merge automatically will it propose that as a merge in the packaging VCS?  How does that work?14:53
mvopitti: I have no strong opinion either way, I'm fine with doinga sru for it14:53
mvopitti: it would be nice if we could resurrect the strings from hardy somehow14:53
mvo(the translations I mean)14:53
pittimvo: there's a script which copies them over14:54
cjwatsonnxvl: mails to jaunty-changes are moderated, but subscription is open14:54
cjwatsonnxvl: the moderation queue is also empty14:54
Laneymvo: Please do it!14:55
mvopitti: oh? is that script in the bug somewhere (and I overlooked it?) - if so, I'm happy to do it right away14:55
Laney:)14:55
nxvlcjwatson: i mean the subscription14:55
cjwatsonnxvl: nothing to do with us ...14:55
nxvlcjwatson: mmm, i will check what's happening, thank you14:55
pittimvo: it's a Launchpad thingie; I don't know it either, I just know about its existance14:55
mvopitti: so it happens automatically?14:56
pittimvo: someone has to call it14:56
=== smurfix is now known as smurf
danimohi asac15:01
danimoasac: Riddell said you could help me with tracing down an issue with network manager15:01
danimoasac: my provider assigns me an ipv6 address, and I guess nm thinks it thus doesn't need to assign me an ipv4 address via dhcp15:02
danimoasac: but I need to prove it somehow15:02
ograARGH15:02
ogratkamppeter, my cups went on strike after printing once15:03
ograi get a "No %%Pages: comment in header" message15:03
ograit worked a second ago and now i cant even print a testpage15:03
ogranot even a reboot and resetting the printer helped15:05
asacdanimo: is that pppoe?15:07
Spadsogra: a friend of mine got that problem shortly after upgrading to intrepid.15:07
ograwell, i rinted several times on intrepid already15:08
ograand it woked a minute before this job15:08
* ogra goes mad ... why does such a thing only happen if i'm in massive time pressure 15:09
danimoasac: no, plain ethernet15:10
danimoasac: (student dorm)15:10
* ogra cries15:16
asacdanimo: then how does your provider assign you ipv6?15:18
danimoasac: the student dorm is my isp15:18
danimoasac: ipv4 and ipv6 via one ethernet line15:18
asacdanimo: open a bug, reproduce and attach the complete syslog so i get an initial idea ;)15:19
asacdont use IPv6 here :/15:20
danimoasac: I wanted to ask where to look15:20
danimoasac: the ipv6 address is assigned as the interface is brought up15:20
danimoasac: ipv6 doesn't require dhcp15:20
=== cody-somerville_ is now known as cody-somerville
superm1asac, is there any particular reason that libmbca depends on bluez-gnome?15:24
asacsuperm1: yes. i think the wizard itself support bluetooth somehow15:24
asacwe cannot use that in NM though for now15:24
superm1it's pulling in the entire bluetooth stack whenever you install network-manager gnome15:25
asachmm15:25
superm1because network-manager gnome is recommending libmbca015:25
asacsuperm1: could you file a bug about that? is that a big problem? i men in the end we want to support bluetooth by default i think15:25
asacs/men/mean/15:25
superm1asac, well it's not a problem for main distro, but for derivatives it is adding a lot of dependencies15:26
superm1asac, i'll file a bug though15:26
asacsuperm1: ok. but assume next release NM supports bluetooth ... fixing this bug wouldnt change much for derivates then i think15:27
asac(not really sure how NM will do that in the end ... so there might be less depends involved)15:27
superm1asac, right.  well i guess that also depends on the timeframe of that release15:28
superm1i guess the better question to pose is why it's asking bluez-gnome rather than libbluetooth3 or similar15:28
asacsuperm1: point that out in the bug. libmbca upstrewam has to give a comment then15:29
asacdanimo: ok. first stare at the log and see if it tells you something special about ipv615:30
asacdanimo: then go and look in code how the nm-setting-ip6-config.h things are used15:32
asacand if they prevent stage4 from getting the ip15:32
ograURGH !15:35
ograso as soon as a print job gets sent to /dev/usblp0 the device vanishes15:35
ograwhat a mess15:36
danimoasac: will  try, bbl15:36
ograpitti, ^^^^ any idea ?15:36
pittiogra: urgh? no, that's news to me; anything enlightening in dmesg?15:37
ogra[  847.544312] usb 7-3: USB disconnect, address 815:37
ogra[  850.168082] usb 7-3: new high speed USB device using ehci_hcd and address 915:37
ogra[  850.321234] usb 7-3: configuration #1 chosen from 1 choice15:37
ogra[  850.324979] usblp0: USB Bidirectional printer dev 9 if 0 alt 0 proto 2 vid 0x03F0 pid 0x411715:37
ogra[  852.301256] usblp0: removed15:37
ograthats all15:37
ograbetween 850.324979 and 852.301256 i clicked on "print"15:37
ograi can cncel the job, replug the printer and have the device back15:38
ograprinting again gets me the same result15:38
ograthe printer ui just shows "No %%Pages: comment in header"15:38
pittiogra: sounds like a kernel bug or hw problem15:39
pittiogra: device disconnect when you talk to it...15:39
pittiyou talked too loudly, it fell over15:40
ograwell, the device works/worked in hardy15:40
ograi'm cursing here15:40
seb128and it worked in intrepid you said15:40
seb128and just before breaking usually things work15:40
ograi should be on the autobahn since 30min, but cant print my badge for the conf i'm heading to15:40
ograseb128, it worked during the dev cycle15:41
ograi probably scared it by loud cursing :)15:41
ograand it constantly worked in hardy15:41
ograjust intrepid final seems not to15:41
seb128boot an hardy cd and print your badge?15:41
ograhrm15:42
seb128it'll be faster to boot a CD than to debug15:42
pittiRiddell: good news15:43
wasabiKeybuk: mvo: I no longer use evms15:43
wasabiSo, 1 left.15:43
wasabiBut, I no longer use it because it's in such a crappily maintained state, not because I think it sucks. I still think it's awesome. ;015:43
Riddellpitti: mmm?15:44
pittiRiddell: I found the msgctxt problem, and band-aided it15:44
Riddellpitti: ooh?15:44
pittiRiddell: next langpack build shoudl be good15:44
Riddellpitti: is it not a launchpad issue?15:44
pittiRiddell: unfortunately intrepid's gettext-po.h/glibc implementation is too stupid to know about msgctxt15:45
pittiso I disabled using that15:45
pittithat will make the packs considerably bigger (the English ones), but at least correct15:45
pittiand for -updates we don't care so much15:45
Riddellpitti: why much bigger?  the strings were always in the .po files15:46
pittiRiddell: it filters out msgid == msgstr ones15:46
Riddellah15:47
pittiRiddell: for those people who have fun earning easy karma by translating C into en_US and en_GB15:47
* liw ponders using Finnish for msgids15:50
sebnerwb nxvl15:53
Keybukcjwatson: yeah I saw that the removal records are now in soyuz, that's where I got the "removed from debian" bit from16:20
ograno way ...  and suddenly th same hapens with hardy as well, on all three printers in my house16:21
jdongis there a way with apt_preferences(5) to pin a glob of packages?16:21
* ogra doesnt get whats happening here 16:21
ograpitti,16:23
ograE [05/Nov/2008:17:13:56 +0100] [Job 36] No %%Pages: comment in header!16:23
ograE [05/Nov/2008:17:14:15 +0100] Pause-Printer: Unauthorized16:23
ograE [05/Nov/2008:17:14:19 +0100] PID 9919 (/usr/lib/cups/filter/pstopdf) stopped with status 1!16:23
ograE [05/Nov/2008:17:18:55 +0100] Resume-Printer: Unauthorized16:23
ograi see a lot of that in my cups log16:23
pittitkamppeter: ^ any idea?16:23
* ogra wonders where the pause and resume comes from16:24
=== apachelogger is now known as Oxyhydrogen
=== gouki_ is now known as gouki
ograsigh16:32
* ogra doesnt get it 16:33
rtgkees: is CVE-2008-3831 important enough to warrant another -security upload?16:35
mvoif there is anyone faimilar with evms, I would appreciate if you could help me with writing the sru test case for bug #292179 - I need a recipt how to add a evms parition to the system (for someone with no clue about evms like me)16:36
ubottuLaunchpad bug 292179 in update-manager "Intrepid upgrade removed EVMS but should not have allowed upgrade" [Medium,In progress] https://launchpad.net/bugs/29217916:36
Keybukevms --cause-pain --hurt --ow --ow --make-it-stop --please --illl-do-anything /dev/sda116:39
pittiKeybuk: didn't you forget --fsck-drives?16:41
=== seb128_ is now known as seb128
ion_The idea of evms sounds nice. I hope someone makes an equivalent UI for lvm, md etc.16:44
ograpitti, hmm, now i can print but get empty pages16:44
Keybukbtrfs!16:45
Keybukbtrfs!16:45
Keybukbtrfs!16:45
ograpitti, and the intresting part is:16:45
ograogra@osiris:~$ ls /dev/usblp016:45
ograls: Zugriff auf /dev/usblp0 nicht möglich: No such file or directory16:45
ograthough it prints  ...16:45
Keybukmy mouse just stopped working16:46
Keybukwtf16:46
ion_btwfs, huh. /me takes a look16:47
ion_r16:47
jdstrandrtg (and kees): unless there is more to it than the CVE description, I'd say it can wait til the next round16:48
rtgjdstrand: works for me. I'm about to upload 40 plus SRU/stable patches16:49
jdstrandrtg: is it included in there?16:50
rtgyep16:50
jdstrandyeah-- that sounds right to me16:50
jdstrand-updates, and wait on -security16:50
rtgbut this kernel will likely stay in -proposed for quite awhile16:50
Keybuksilly things to type #143: rmmod usbhid16:51
jdstrandwell, there are a lot of ways for a local DoS besides that ioctl, so IMO, it's low priority (so we'll wait until we have several of them or something bigger)16:51
rtgjdstrand: np16:51
KeybukHMM16:53
Keybukthings you cannot do without a mouse16:53
KeybukLOG OUT!16:53
mvoctrl-alt-backspace16:53
mvosee, it works!16:53
rtgKeypucnhing the power button doesn't bring up the dialog?16:54
cjwatsonalt-f1 right right up up enter (alt-tab if necessary) alt-l16:55
cjwatsonsee, obvious16:55
Keybukit's sad that I still blame Linux for problems like that16:58
Keybuk(the battery had run out)16:58
ion_:-)16:59
* ogra goes to install a windows pc 17:01
jernstbryce: ping17:03
keesrtg, jdstrand: I thought CVE-2008-3831 was fixed already?  (or was intrepid still vulnerable?)17:06
rtgkees: well, its in the stable series. Did I already get it? checking changelog....17:07
rtgits not in the Intrepid changelog17:08
brycejernst: rather than pinging people, it's better to just ask the question...17:11
keesrtg: ah, dang, we'll get it in the next round then.17:11
rtgkees: well, as I pointed out to jdstrand, this kernel is going to cook in -proposed for several week, perhaps longer.17:11
keesshould be fine.17:12
jernstbryce: sorry, was not sure that you were back. regarding https://bugs.launchpad.net/bugs/286924 could you please review your patch rejection reason in the light of my last comment ?17:12
ubottuLaunchpad bug 286924 in usb-creator ""Create a USB startup disk" menu entry should be named "USB startup disk creator"" [Low,Triaged]17:12
keesslangasek: why is "die" more correct than "done" for the PAM regression?17:14
brycejernst: sure17:17
tkamppeterogra, pitti, the failure of /usr/lib/cups/filter/pstopdf is bug 28975917:18
slangasekkees: I'm not sure that it is?17:18
ubottuLaunchpad bug 289759 in cups "cups kyocera" [Undecided,New] https://launchpad.net/bugs/28975917:18
tkamppeterogra, pitti, the unauthorized resume should not influence the job.17:19
slangasekkees: it's more correct than 'ok', because using 'ok' will fall through to the next module, which is probably pam_deny17:19
keesslangasek: right, "ok" clearly fails.  regardless, I'd like to get it SRU'd asap, since it's clearly a regression.17:20
brycejernst: the patch isn't rejected, only the intrepid task17:20
tkamppeterogra, pitti, bug 28975917:21
ubottuLaunchpad bug 289759 in cups ""/usr/lib/cups/filter/pstopdf failed" in error_log and only blank page printed" [Undecided,New] https://launchpad.net/bugs/28975917:21
jernstbryce: sure no problem however the reason (breaks translation) doesn't stand as no translations exists17:21
slangasekkees: yes, by all means.  I would suggest using '=done' then, and SRUing ASAP17:21
brycejernst: fair enough17:21
keesslangasek: will there be any conffile silliness?  (I assume you have just buck-passed the SRU to me)17:22
slangasekkees: nope, none at all; you should be able to just edit the unix profile and it should work17:23
slangasekyes, I'm passing it to you so that I can do the SRU approval :)17:23
ogratkamppeter, what i dont get that i printed yesterday and the whle morning stuff and it worked, it just suddenly stopped working17:23
keesslangasek: hah, perfect, I'll jump all over it.17:24
keesmurdok: hola!  :)17:27
murdokhola :Ð17:27
murdokit's about bug https://bugs.launchpad.net/ubuntu/+source/procps/+bug/21639817:27
ubottuLaunchpad bug 216398 in dosemu "default mmap_min_addr breaks dosemu" [Medium,Confirmed]17:27
keesyup, hopefully my comments have described the situation a bit.  have you looked at what wine did to solve this in intrepid?17:28
murdokYou said that is better to include in the package a /etc/sysctl.d/dosemu.conf file to fix it17:28
murdokyes i have17:28
murdokis it as simple as including this file or do i miss something? i would like to do it17:28
keesmurdok: well, according to the README in /etc/sysctl.d/, I'd recommend something very late in the process, so naming it 90-dosemu-low-memory.conf or so17:28
murdokokay17:29
keesmurdok: it should be trivial to add to the dosemu package.  (this is why there was a push for /etc/sysctl.d/, so we could support per-package configurations)17:29
murdokwine's config is named  wine.sysctl.conf17:29
murdokmaybe it should be also change to 90-*17:29
keesmurdok: yeah, it's an over-sight, since they created the file prior to there being a standard for sysctl.d.  but as it happens, they resolve last anyway, so it works.17:30
keesmurdok: the maintainer-script juggling to rename that file is non-trivial, but if one of the wine maintainters is up for it, I'd like that too.  :)17:30
ogratkamppeter, do you have anything about "No %%Pages: comment in header" ?17:31
ogratkamppeter, seems thats the issue it started with17:31
murdokisn't it as easy as cp wine.sysctl.conf 90-wine.sysctl.conf and if it doesn't exists create it?17:32
murdokoops mv*17:32
ograand apparently the printer doesnt work at all anymore on any of the laptops i try it on17:32
murdokwell but it works at the end17:32
murdoki'll try it with doesmu, should i assign the bug to me?17:32
keesmurdok: no, since it's possible the user has changed the conf file, so an md5 check is needed.17:33
keesmurdok: sure, yeah17:33
=== LucidFox_ is now known as LucidFox
murdokokay, let's see if I have it ready tonight17:33
murdoknow I must go17:33
murdokthanks :D17:33
keesKeybuk: is there more currect documentation on conffile removal/renaming than http://wiki.debian.org/DpkgConffileHandling ?17:34
murdokkees: oops i forgot, should i do the patch for jaunty and intrepid?17:47
murdokboth still have the same versions17:47
keesmurdok: if you want to pursue an SRU, do intrepid, but probably best to start with jaunty so you can test it17:49
murdokokkie17:50
ograok, at least windows worked :(17:51
* ogra cuses that he has to install windows to get a printout, especially since i wont get any sleep through that 17:51
Keybukkees: no idea17:54
keesKeybuk: okay.  I saw a whole bunch of extra magic added to the procps maintainer scripts when removing the tcp timestamp stuff.17:55
Keybukcolin did that ;)17:55
KeybukI think he took my functions and replaced sed with dpkg-query17:56
Keybukso his are probably the most current ;)17:56
keesI will use procps as the gold standard now.  :)17:56
=== robbiew is now known as robbiew-lunch
=== BenC1 is now known as BenC
Keybukpitti: pidgin18:12
pittiKeybuk: mutt18:12
Keybukerr, disregard18:13
KeybukI'm sure pidgin had an NM plugin18:13
pittiKeybuk: oh? then we should activate it18:23
pittior switch to empathy now, maybe18:23
Keybukthat's the thing18:25
KeybukI thought it was on18:25
Keybukbut I'm clearly hallcuinating18:26
keesslangasek: do you have docs on how the pam-configs stuff is processed?  I haven't found anything in the PAM debian/ tree yet.  I'm trying to figure out how -Initial differs from the entires without -Initial18:53
keesslangasek: and under which situations do I need to update the md5sums in local/pam-auth-update ?18:56
kees(oh, nm, that's just for templates?)18:57
=== Oxyhydrogen is now known as apachelogger
keesslangasek: okay, 291091 updated and ready for SRU evaluation.19:09
=== robbiew-lunch is now known as robbiew
slangasekkees: documentation is only in the wiki currently, at https://wiki.ubuntu.com/PAMConfigFrameworkSpec; and yes, the md5sums are just for the templates19:19
keesslangasek: ah! a pointer to that page would be Nice(tm) in the debian/ tree somewhere.  in the meantime, I will read that just to double-check my changes are sane.19:20
slangasekkees: you've installed this, just to confirm that it does update your configs files correctly? :)19:21
NCommanderhey kees19:22
keesslangasek: yea, it works for me19:23
keesNCommander: heya :)19:23
slangasekkees: ok, please upload19:23
keesslangasek: okay, done.19:25
slangasekthanks19:26
superm1slangasek, can you disable the cron job that would be creating jaunty mythbuntu alternates whenever dailies would be starting?  We've decided not to do alternates any more due to their enormously low take rate and the testing burden of testing both.  I'm working on porting over all the bits and pieces of our hacks in our live cd build script to other packages so that live cds can be built with livecd rootfs.  it'd be more ideal at that poin19:35
superm1t to have daily live disks generated in the alternate's place19:35
lifelessKeybuk: has it passed?19:57
vadi2I was told that my webcam driver is buggy, but how can I find out who to report the bug to in launchpad?20:06
=== ogra_ is now known as ogra
johanbrvadi2: file a bug against the kernel (package "linux")20:10
vadi2johanbr: alrighty, thank you20:10
psusican anyone remind me how you turn on KERN_DEBUG printks?20:12
vadi2johanbr: sorry, but I don't see an option to add an affected package: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/29414220:13
ubottuLaunchpad bug 294142 in cheese "[intrepid] Cheese chooses wrong resolution by default and fails to work" [Low,Triaged]20:13
johanbrvadi2: Should be another way to do it, but try https://bugs.launchpad.net/ubuntu/+source/linux/+bug/29414220:18
ubottuLaunchpad bug 294142 in cheese "[intrepid] Cheese chooses wrong resolution by default and fails to work" [Low,Triaged]20:18
vadi2johanbr: thank you20:19
slangaseksuperm1: ok, changed in bzr20:21
keesslangasek: uhm, is soyuz supposed to auto-submit things from intrepid-proposed into jaunty?  or did you trigger that?20:22
slangasekI did that20:23
kees(i.e. https://edge.launchpad.net/ubuntu/+source/pam  -- I was not expecting it to build in jaunty)20:23
keesokay, whew20:23
slangaseker, hrm20:23
slangasekdid it get built twice?  that would be a sign that I screwed up.20:23
keesslangasek: in that case, do you want me to push those changes into bzr?20:23
slangasekit should all go to bzr anyway, yes20:24
slangasekbut if it built in jaunty, then... oops.20:24
keesI yelled at me about a build failure, that's how I noticed20:24
ogrause earplugs :)20:25
lifelessKeybuk: (that was a pong)20:27
=== dfiloni is now known as devfil
keesslangasek: do you want it in bzr as 1.0.1-4ubuntu5.1 or as UNRELEASED with 1.0.1-4ubuntu6 ?20:29
slangasekkees: I'm already taking care of it in bzr20:29
slangasek(5.1, now 5.2 since I have to do a rebuild20:29
slangasek)20:29
keesd'oh, okay, nm20:30
RainCTanyone knows if it's possible to limit the bandwith pbuilder uses?20:31
=== dwatson is now known as davewatson
tkamppeterogra, pitti, I have dound a possible solution for the pstopdf problem in bug 289759. Please try. It should also fix several other bugs, should get SRU.20:49
ubottuLaunchpad bug 289759 in cups ""/usr/lib/cups/filter/pstopdf failed" in error_log and only blank page printed" [Undecided,Incomplete] https://launchpad.net/bugs/28975920:49
ogratkamppeter, i will do so if i caom back on sat. for now i had to print on windows to get the papers i need tomorrow morning20:50
=== Kmos_ is now known as Kmos
jdstrandslangasek: hi! so pitti sent apparmor to intrepid-proposed like 13 hours ago, however all archs show 'needs building'21:20
jdstrandhttps://launchpad.net/ubuntu/+source/apparmor/2.3+1289-0ubuntu4.121:21
jdstrandslangasek: is this cause for concern or just archive lag?21:21
infinityjdstrand: jaunty-release is scored higher than intrepid-proposed.21:24
infinityjdstrand: So, you get to wait until the autosync queue is done.21:24
infinityjdstrand: Or, if it's urgent and we need it built and tested ASAP, let me know, and I'll score it up.21:24
jdonginfinity: is that a bug or a feature?21:24
infinityjdong: Feature.21:25
jdstrandinfinity: no, not that urgent-- I made a comment in the bug. we should be good. thanks!21:25
infinityjdong: With rare exceptions, -proposed is never meant to be "urgent", while bugfixes in the devel release may well be.21:25
jdonginfinity: gotcha21:26
=== RAOF_ is now known as RAOF
seb128kees: there?22:05
keesseb128: yea, but on a conf call22:08
seb128kees: ok, did you upload a system-tools-backends new version? there is some new bugs about postinst errors22:09
seb128whoever did the upload might want to have a look to those22:10
james_wseb128: intrepid or jaunty?22:11
keesseb128: back.  bug #?22:11
seb128james_w: intrepid22:11
james_wodd22:12
seb128kees: bug #29429122:12
ubottuLaunchpad bug 294291 in system-tools-backends "package system-tools-backends 2.6.0-1ubuntu1.1 failed to install/upgrade: il sottoprocesso post-installation script ha restituito un codice di errore 1" [Undecided,New] https://launchpad.net/bugs/29429122:12
keesseb128: looks like a problem due to being in the middle of an upgrade?22:13
seb128ok, I didn't look into details I was just reading my mails before going to bed and there was 2 upgrade errors for the new version so I figured I would let you now to maybe keep an eye on coming bugs there22:14
seb128bug #29438922:14
ubottuLaunchpad bug 294389 in system-tools-backends "package system-tools-backends 2.6.0-1ubuntu1.1 failed to install/upgrade: subprocess post-installation script returned error exit status 1" [Undecided,New] https://launchpad.net/bugs/29438922:14
keesgeh, I will try to reproduce, but I didn't have any problems with it yesterday22:15
seb128that's the other one22:15
keesjames_w: any idea how to reproduce this?22:17
seb128the issue doesn't seem due to the changes22:17
james_wkees: no clue22:18
seb128and there was already a similar bug opened before intrepid22:18
james_wkees: the second one may be that it is already started22:18
seb128so that's likely not due to the update and just a coincidence22:18
james_wkees: in the second log it apparently starts fine once, and then it tries to start it again later and fails22:18
seb128kees: sorry for the noise22:19
keesseb128: well, it's clearly related to people getting the security update, but I'm not sure in what way they're set up that it's breaking22:19
seb128kees: right but it doesn't seem specific to security changes, the postinst has just corner cases where it can break apparently22:20
* kees nods22:20
=== fta_ is now known as fta
seb128mvo is right, all those postinst are not robust enough22:21
NCommanderkees, so I have a PIE-built chroot (I need to hand it to Gentoo; when you want to do something completely insane, it works well)22:21
keesNCommander: kewl22:21
NCommanderkees, do we want to add anything like PaX, or are we just going to stay w/ AppArmour22:21
seb128anyway enough work for today22:22
seb128'night everybody22:22
NCommandernight seb12822:22
keesNCommander: most of PaX is already in mainline.  beyond that, AppArmor works well enough for a MAC system.22:23
NCommanderkees, MAC?22:23
NCommanderMacs didn't have AppArmour until jaunty22:24
keesNCommander: heh.  Mandatory Access Control.  (AppArmor, SELinux, SMACK, etc)22:24
NCommanderah22:25
NCommanderCool22:25
NCommanderGentoo has already done quite a bit of the hardwork needed to make this fly, and based with my previous attempt, I think I can successfully get an amd64 PIE built chroot off the ground22:25
jordiTheMuso: I uploaded alsa-lib & alsa-driver to unstable, with some changes re: what was in svn22:55
TheMusojordi: Right I got those already./22:55
jordiTheMuso: next will be -utils,tools and plugins22:55
TheMusojordi: Right.22:56
jordiTheMuso: -plugins includes a biarch patch that you could somehow ask for testing :)22:56
=== robbiew is now known as robbiew_
TheMusojordi: Awesome!22:56
jordiTheMuso: ie, it will generate lib64asound2-plugins and so on22:56
* TheMuso nods.22:56
RAOFjordi: Oh?  That biarch patch I put up there some time ago has finally hit a package? :)22:56
jordiTheMuso: still not committed, I'm trying to finish improving the package descriptions22:56
RAOFYay!22:56
jordiRAOF: so it's you22:57
RAOFYup.  That was me.22:57
jordiRAOF: it's taken a while22:57
jordibut it's the beginning of both Ubuntu and Debian cycles22:57
jordiso I decided to apply it, look somewhere else and let TheM^WUbuntu fix it if something goes wrong ;)22:58
RAOFYeah.  I was too late for pushing that for Intrepid, or for lenny for that matter.22:58
jordiTheMuso: it's also a perfect time to bring our diffs close to 0. Go ahead and discuss whatever you want (specially alsa-lib I guess) in the list22:58
jordior commit whatever is clear we want in both distros22:59
jordiRAOF: yep22:59
jordiand the patch is scary :)22:59
jordi  [ Christopher James Halse Rogers ]22:59
jordi  * debian/control, debian/rules: import the multi-arch magic from22:59
jordi    alsa-lib to build a lib32asound2-plugins package wherever22:59
jordi    lib32asound2 is built, and similarly for lib64asound2 (closes: #436201).22:59
jordithis is the uncommitted changelog23:00
jordimany thanks, RAOF!23:00
vadi2intrepid-security isn't enabled by default for a clean install, but intrepid-updates is. Is there any rationale behind this or is it a bug? https://bugs.launchpad.net/bugs/28919723:00
ubottuLaunchpad bug 289197 in update-manager "[Intrepid] security updates aren't enabled by default" [Undecided,Incomplete]23:00
TheMusojordi: Ok.23:05
rulusHello, can someone enlighten me on bug 293127? (I'm the reporter) Are there plans to update these images, or am I doing something wrong? :)23:06
ubottuLaunchpad bug 293127 in debian-installer "Update Intrepid hd-media images to final release" [Undecided,New] https://launchpad.net/bugs/29312723:06
=== robbiew_ is now known as robbiew
bdmurrayTheMuso: Are you familiar with ubuntustudio-menu at all? bug 276503 was brought to my attention23:13
ubottuLaunchpad bug 276503 in ubuntustudio-menu "package ubuntustudio-menu 0.10 failed to install/upgrade: there is no script in the new version of the package - giving up" [High,Triaged] https://launchpad.net/bugs/27650323:13
TheMusobdmurray: I have touched the package on several occasions, and the studio team is well aware of that bug. Since nobody else has seemed to do anything about it yet, I'll likely take a peak at some point in my own time.23:14
bdmurrayTheMuso: Great, I'll pass it on.23:17
NCommanderhey TheMuso ]23:23
jordiRAOF: ooh23:25
jordi+       # We don't necessarily have pulse, dbus, or jack biarch libraries23:25
jordi+       # and even if we do, we don't have the .so symlink for them23:25
jordi+       # since ia32-libs-dev doesn't exist.23:25
jordi+       # SO: we need to detect these libs when they exist, provide .so23:25
jordi+       # symlinks, and copy the pkg-config files.23:25
jordiRAOF: I think I didn't like this too much23:25
jordiwhy can't we have biarch libs for these?23:25
* slangasek shoots biarch in the forehead23:26
jordila la23:26
jordithere it goes.23:27
jordinow debian/rules is as ugly as it can get23:27
jordislangasek: enjoy23:28
jordihttp://svn.debian.org/wsvn/pkg-alsa?op=comp&compare%5B%5D=%2Ftrunk%2Falsa-plugins@2126&compare%5B%5D=%2Ftrunk%2Falsa-plugins@214023:29
slangasekI assume that involves biarch and will therefore pretend it doesn't exist23:29
jordiyou can't escape biarch23:30
slangasekI can replace it with multiarch23:30
jordiRAOF: I guess this will create duplicate files with ia32-libs or so23:30
jordislangasek: that would be quite cool :)23:31
jordiRAOF: here?23:53
RAOFjordi: Briefly.23:53
jordiRAOF: ia64-libs doesnt exist, but was added to Build-Depnds23:53
jordiany clue?23:54
RAOFUm, was it?23:54
TheMusoia64-libs sounds... weird.23:54
RAOFI presumably had some reason to think that ia64-libs existed.23:54
jordiamd64-libs?23:54
RAOFAaah.23:55
RAOFBrain transcription error :)23:55
jordiyep ;)23:55
RAOFI sometimes like to forget IA64 is an ISA distinct from x86-64.23:55
NCommanderYou can run x86 binaries on ia64 however23:57
TheMusoAt what performance penalty?23:58
stgrabernot only on part of them ? (I thought the first ones didn't have the x86 compatibility thing)23:58
lifelessTheMuso: no penalty23:58
lifelessTheMuso: the penalty is in the fact that the chip is HUGE23:58
lifelessTheMuso: and its clock rate doesn't scale as high, so its x86 work/sec is less than current x86-64 dedicated chips23:59
RAOFjordi: The crazy "create symlinks and pkg-config files" madness was there for some reason.  Possibly because ia32-lib-dev exists only on ia64, and that's an uninteresting arch for me.23:59

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