=== asac_ is now known as asac === fta_ is now known as fta [00:36] bug 402175 [00:36] Launchpad bug 402175 in gnumeric "gtk_tree_view_column_get_cell_renderers implicitly converted to pointer" [High,Triaged] https://launchpad.net/bugs/402175 === blueyed_ is now known as blueyed [02:37] doko: are you here? === mnabil_ is now known as mnabil === tkamppeter_ is now known as tkamppeter === hunger_t is now known as hunger === yofel_ is now known as yofel === Quintasan_ is now known as Quintasan === durt_ is now known as durt [13:15] cjwatson: debhelper 7.3.5 introduced support to build Python modules and extensions for every supported Python version, do you see room to merge current 7.3.8 in Karmic? It changed a lot, though (implementation of buildsystems, primarily). === cprov is now known as cprov-afk [16:21] Hello, can someone look at LP 404561 [16:21] Launchpad bug 404561 in debhelper "Candidate revision debhelper_7.3.8ubuntu1" [Undecided,New] https://launchpad.net/bugs/404561 === joaopinto is now known as joaopinto_brb === joaopinto_brb is now known as joaopinto === korn_ is now known as c_korn [18:12] howdy! is there a generic "package" name against which users could report an upgrade problem (other than caused by update-manager, in which case they would report against update-manager)? [18:13] e.g. for a generic "upgrade from intrepid to jaunty failed for me" type of reports [18:13] we don't really have an equivalent to Ubuntu pseudopackages, unfortunately [18:13] err, to pseudopackages in the Debian BTS [18:14] if you don't want to treat update-manager as a pseudopackage for upgrade problems, I think the only available option is to report the bug without a source package name [18:16] cjwatson: I'm trying to write an apport wrapper for 'upgrade-system' to avoid getting generic upgrade reports against the package, [18:16] because many people report against that package when they really mean to report a generic upgrade issue, whether performed using update-manager or APT or aptitude. [18:17] check with mvo to see if he minds general upgrade reports going against update-manager? [18:18] apparently, many people use synaptic or LP's search option and end up randomly picking 'upgrade-system' the package because it matches a search for the keyword "upgrade" when they mean to report a failure against update-manager or, in many cases, because a specific package pulled by update-manager failed to upgrade. [18:19] right. I'm hesitant with systematically redirecting every report to update-manager, though. [18:20] my main strategy would have been to write an apport hook that would cancel the report if it's done against 'upgrade-system' and yet that package isn't installed. [18:20] as to which ubuntu package should get that hook is anyone's guess :) [18:21] obviously, adding the hook to 'upgrade-system' won't work... [18:26] cjwatson: any other suggestion for managing such bug reports? :) [18:40] what is up with all of these warnings in dpkg-shlibdeps for the past week or so? [18:40] dpkg-shlibdeps: warning: debian/xserver-xorg-video-openchrome/usr/lib/xorg/modules/drivers/openchrome_drv.so contains an unresolvable reference to symbol DRIDestroyInfoRec: it's probably a plugin. [18:40] dpkg-shlibdeps: warning: 183 other similar warnings have been skipped (use -v to see them all). === dwatson is now known as davewatson === robbiew1 is now known as robbiew === Shane_Fagan is now known as fagan [19:25] dtchen, recently I've had a problem develop on karmic where when I switch songs or streams then there is a 3-10 second or more delay before the song will start to play. [19:26] dtchen, installing pulseaudio and telling my media player to use pulse solves the issue [19:27] dtchen, so I assume its some sort of regression with ALSA or something as I tried an older kernel that I knew to work and a version of the media player from jaunty and the issue still manifested when using the alsasink. === DktrKranz2 is now known as DktrKranz === |Baby| is now known as Baby === highvolt1ge is now known as highvoltage [21:50] Any chance of getting btrfs-tools updated in karmic soonish? [22:11] Debian/unstable has that already. [22:13] hunger: you are free to file a sync request [22:17] sebner: How so? [22:19] http://wiki.ubuntu.com/SyncRequestProcess [22:19] Thanks! [22:19] maxb: ah thx for the link [22:19] hunger: don't worry. I already did that for you [22:19] sebner: Thanks! [22:26] sebner: ola [22:27] i need you! [22:27] * sebner hides [22:27] like tester for http://backtrack.it/~emgent/hackstuff/Gerix-Wifi-Cracker-NG/index-en.html [22:27] ember: omg. rofl. xD [22:28] what rofl ? [22:28] r0x. :-) [22:28] test it and let me know [22:28] ember: bah qt and even q3! [22:28] *qt3 [22:28] ember: b0rken by design :P [22:29] lol [22:31] emgent: why /opt/ ? [22:35] emgent: I don't see any product but gerix site has nice graphics ^^ [22:49] sebner: it`s backtrack native. [22:50] emgent: I can't really test because I have no network to crack ^^, maybe tomorrow [22:53] I've got a problem with Ubuntu 9.04 (Jaunty) as live cd/dvd system with persistent home. I did not manage to use an usb stick as persistent home although I've formatted it with ext2 and labeled it "home-rw" as requred by casper. It seems if there are not any usb devices available when casper searches for the persistent home partition. Any hints? [22:53] Sorry, good eavening everybody. [22:56] Sh***, I'm on the developer channel... sorry for disturbance. [23:08] anyone around that can make bug 306627 be retraced? [23:08] Bug 306627 on http://launchpad.net/bugs/306627 is private [23:08] it seems to never have gotten processed [23:09] i'm not even sure how i can see it atm [23:10] ah all ubuntu dev is part of the crash team === Znova_ is now known as Snova_ === vorian is now known as OldSchool [23:40] Alpha 3 released and still got big issues with intel drivers. At least my graphic card.