[00:02] so is pycentral horked or what ? [00:05] quite. [00:07] anyone fixing it, or should I break out pdb? [00:08] I started looking at it but was distracted by PulseAudio. So, the latter. [00:53] slangasek, when would be a good time to look over the changes to cdimage that I had proposed? cjwatson had asked me to ask you to look into merging them in [01:01] superm1: mmm, today is archive duty day and tomorrow I'm off, so I guess Wednesday? [01:01] slangasek, okay sounds good to me. [01:03] slangasek, while you are archive duty'ing, you can nuke the first upload of libnet-upnp-perl to save yourself catching the error in it (there are two in NEW). it was uploaded as arch any rather than all (the second one is fine) [01:04] superm1: thanks, kicking it out so I don't get confused later [01:04] ok thanks [01:10] johanbr: still having issues with bz headset and PA? [01:11] crimsun_: Yes, I'm afraid so. Even getting it to work without PA has been challenging. [01:12] Sadly, it seems like the bluez developers are not very interested in the issue. I've had more luck with headsetd than with the bluez audio service. [01:27] Is there any reason why thunar-svn-plugin hasn't been accepted yet? It did make it before the FF, right? [01:31] <_MMA_> Still sitting in the queue. https://launchpad.net/ubuntu/hardy/+queue Might take a bit to clear. [01:31] <_MMA_> And only been 4 days. (it looks like) [01:42] slangasek: is that in the standard gconf? I just did a quick google for gconf ldap and only found references to some evolution specific stuff? [01:42] Chipzz: I didn't look too closely at how gconf was using ldap [01:42] lifeless: ping [01:44] pong [01:45] lifeless: so, people asked me to upload opensync-0.22 for hardy, as it's pretty clear 0.40 won't be ready in time [01:45] think 0.22 is an unambiguous improvement ? :) [01:45] if so then yeah, JFDI [01:46] of course, there's still the issue that the plugin configuration and the database changed etc., [01:46] but what about a 1-line patch telling it to use ~/.opensync-0.22 rather? [01:46] yeah, I like that [01:46] if time permits, I/somebody else could try to port the plugin configuration converter from 0.3x that dgollub committed last week [01:46] (for 0.22->0.3x) [01:47] now, should I upload that to Debian unstable first and get somebody to sync? [01:47] opensync appears to be in main [01:47] yeah [01:47] upload and sync is easiest [01:47] I think hardy is frozen now anyhow [01:48] only the lib [01:48] right, it'd need an exception [01:48] I have to admit that while evo2<->file works, I had no luck trying to sync my mobile via bluetooth or irda === tiborio_ is now known as tiborio [01:48] connection refused, something which at least works slightly better with 0.3x [01:49] lifeless: do you remember why you changed the test suite (create_case->CREATE_CASE, which is a macro) [01:50] because that got rejected during update [01:50] crimsun_: With the bluez audio service I can get simple things working, like playing a wav file. But ekiga segfaults and Twinkle fails to open the device. [01:51] azeem: blink, debian changelog [01:52] lifeless: AFAICT it was in from the beginning, so "Intial upload" would be the entry... [01:53] hrm, or not [01:53] I'm pretty sure someone gave me a patch for that; might be in the bzr changelog, one sec [01:53] isn't that codehelp's patch? [01:54] oh indeed [01:54] lifeless: oops, sorry [01:55] slangasek: apparently it only does this for certain (evolution-specific) settings: http://svn.gnome.org/viewvc/gconf/trunk/backends/README.evoldap?revision=1966&view=markup [01:55] Chipzz: to be honest, I don't really care about the gconf backend at all, my only concern is that it not get misbuilt and become a source of bug reports :-) [01:56] ok :) [01:56] I actually was kind of interested ;) [01:58] http://lists.debian.org/debian-project/2008/02/msg00048.html -> *sigh* :) [01:59] *yawn* [01:59] Wordpress! YAY! [01:59] Oh, that mail. [01:59] I wish they'd hurry up and remove it from the archives so that we can too... [01:59] haha [02:08] lifeless, azeem I know for a fact I need to use 0.22 to sync with my mobile, so 0.22 would be welcome. [02:09] I know I need > 0.22, so I'd like > 0.22 please ;) [02:09] slangasek: I can live without, I just build locally, but nevertheless. [02:10] TheMuso: what mobile? I think we really ought to be moving opensync forward, and getting fixes for any plugins that aren't ported yet [02:10] slangasek: Nokia 5700 Xpress Music. [02:12] TheMuso: which plugin does that use in 0.22? [02:12] slangasek: problem is, 0.22 is sort of a dead end [02:12] the few developers who hack on opensync concentrate on 0.3x [02:13] problem is, opensync has never had a stable release that they actually stand by [02:13] yeah [02:13] and I see mentionings of "let's get 0.40 out before I switch jobs and go MIA, maybe somebody else will pick up" [02:13] they've routinely broken disk compatibility and api compatibility, and while thats ok if you provide migration - they aren't. [02:13] lifeless: there's now a migration tool from 0.22 to 0.3x [02:14] they actually say it's a requirement this time [02:14] azeem: hmm? I'm aware 0.22 is a dead end, this contributes to me wanting something newer... [02:14] slangasek: ah, ok [02:14] since the plugin that supports my phone is 0.3x-only [02:14] slangasek: Syncml. [02:14] unfortunately, there's no nice GUI for 0.3x yet either [02:14] 3-4 half-finished ones [02:16] Probably expalins why opensync in Debian has stayed where it is for so long. :) [02:20] TheMuso: I think that's explained by "upstream keeps screwing around with build systems" [02:20] heh right [02:21] they're really happy with cmake now that they reimplemented pkg-config and libtool in it [02:25] azeem: isn't pkg-config written in C? :) [02:46] slangasek: What plugin do you need to use with your phone? [02:47] TheMuso: moto-sync, which has no working 0.22 version AFAIK [02:48] No, I don't remember seeing that plugin for 0.22 === kitterma is now known as ScottK2 [03:21] did the x86 retracer die? [03:31] if i wanted to find which applications ubuntu packages that use Xinput, would "apt-cache showpkg libxi6" be appropriate? [03:33] pwnguin: rdepends [03:56] how can I tell libtool to use libopensync.0d as soname? [03:57] (after re-reading Debian #429798) [03:57] Debian bug 429798 in libopensync0 "opensync: please use library versioning" [Wishlist,Open] http://bugs.debian.org/429798 [03:58] Dear tarfile, please become 200% faster. No love, Steve [04:00] oh wait, nm [04:02] is this the right place to be for help with building source? [04:12] lifeless: This isn't Linda, this is moblin-image-creator. [04:13] StevenK: ah; creating tars ? [04:13] StevenK: are you using python's gzip support ? [04:14] lifeless: It is using python's bz2 support. [04:14] are you setting a compression level ? [04:15] * StevenK paws through the code [04:15] tar_file = tarfile.open(tar_filename, "w:bz2") [04:15] I doubt it. [04:15] write, thats your problem [04:15] TheMuso: well, moto-sync is a separate upstream, and I think the current, working version only builds against opensync 0.3x [04:16] lifeless: Hm? Don't write? :-) [04:16] try: [04:18] ah, I was going to suggest something like TarFile.bz2open(tar_filename, mode='w', compresslevel=5), but checking my docs bzip2 doesn't scale like gzip [04:19] python's GZipfile uses -9 by default, not -6 which gzip does; so pythons gzip wrappers are insanely slow by default [04:19] StevenK: run lsprof over it [04:20] StevenK: if you need glue code to do that and get a kcachegrind file look at bzrlib.lsprof [04:21] you can trivially get a cachegrind file from there :) [04:22] I don't think I care that much. :-) [04:44] alt-installer, is a python stack dump an error, or is this allowable? http://dpaste.com/35856/ [04:45] the installer aborted, but much later and I think for an unrelated problem [04:46] that's a different bug [04:46] someone broke python central today [04:46] a lot of hardy is broke because of it [04:47] no lube on that upload [04:48] superm1: so no need to file report - just wait ? [04:48] CarlFK, there's an open bug already if you want to subscribe to it [04:48] let me grab it [04:48] many open reports :) [04:48] hrm, that's the sort of bug that should be milestoned for the alpha that's due in, oh, 3 days [04:49] but 192992 [04:49] this is what caused the installer to abort http://dpaste.com/35857/ [04:49] bug 192992 [04:49] Launchpad bug 192992 in python-central "[hardy] pycentral crashed with ValueError in parse_versions()" [Medium,Confirmed] https://launchpad.net/bugs/192992 [04:49] thanks [04:50] "This bug has 16 duplicates" [04:51] I feel so behind :) [04:51] i'm surprised its only 16 [04:53] but is it confirmed? :) [05:14] superm1: Did you know you set the pycentral bug back to Medium at the same time slangasek set it to High? [05:14] * ScottK2 thinks you might put it back. [05:14] ScottK2, I didn't change it? [05:15] i only changed the milestone [05:15] rather, you targetted it to a release [05:15] well i did that by accident looking for the milestone, and then i changed the milestone :) [05:16] ah - so yes, I had done that just before you :) [05:16] superm1: Activity log says different (it's a refresh issue). [05:17] yeah suppose so [05:18] Just thought I'd mention it so it'd end up set where it was wanted to be. [05:18] Ouch. The latest live CD appears to still be using an old version of casper. [05:21] Yeah, latest live CD has casper 1.115. [05:21] And 1.118 is in the archive. [05:23] Same with a lot of packages I think, including artwork. [05:23] So much for my a11y testing this afternoon. :) === cjwatson_ is now known as cjwatson [05:47] TheMuso: check http://people.ubuntu.com/~ubuntu-archive/livefs-build-logs/ [05:47] TheMuso: this is usually because later livefs builds failed and somebody needs to focus on getting them back into shape [05:48] It may be related to the python-central breakage ... [05:48] I win, it is. [05:49] I have a theory on the python-central breakage, but no good way to test it and I'm about to go to bed. Anyone interested in hearing a shot in the dark? [05:50] ScottK2: No chroot you can upgrade? [05:50] StevenK: I've got a machine, just it's almost 1am and I've got an early meeting. [05:51] cjwatson: Ah right, it took me a bit to work that out, but looks like they are failing. Latest is from the 18th, for i386 at least. Ppc and ia64 have builds from the 19th. [05:51] ScottK I have a box I czan test on [05:51] StevenK: My shot in the dark is to revert the changes in python/sourcelist.cc in the last python-apt upload. The pyversions.py file the python-central keeps dieing on is unchanged from the last to the current versions.. [05:52] er... I take that back. I have a gutsy box... [05:53] You could do it in a Hardy chroot. [05:53] http://pastebin.com/m63ba51ca is the change that I'm guessing needs reverted. [05:53] But it's just a guess. Doing that may eat you children. [05:53] Good night all. [06:02] yea that bug is a bit annoying [06:42] Good morning [06:42] cjwatson: language-support split> that happened last Thursday [06:42] Good evening. [06:42] cjwatson: it's all done [06:45] cjwatson, asac: BTW, I wonder whether I should continue to test the n-m 0.7 packages? will we get it for hardy, or shall I go back to dogfooding the 0.6 ones? [06:46] good morning [06:49] Good evening [06:49] * pitti hugs dholbach [06:49] * dholbach hugs pitti back [06:55] good morning [06:56] argh argh, seems that the new python-central is on a 'break postinsts' rampage [06:57] yes, yes it is [07:01] on the master bug there seems to be at least a workaround - no idea if it's "the real fix" [07:01] bug 192992 comment 32 [07:01] Launchpad bug 192992 in python-central "[hardy] pycentral crashed with ValueError in parse_versions()" [High,Confirmed] https://launchpad.net/bugs/192992 === hunger_t_ is now known as hunger [07:19] apport bugpattern for bug above bug added [07:19] no more dups from now on [07:40] hm, current hardy's bzrtools is 1.0, which is incompatible with 1.1~rc1 [07:40] but when I sync from Debian, I get bzrtools 1.2 [07:40] because Debian already has bzr 1.2 [07:40] Drag in both bzr{,tools} 1.2? [07:40] slangasek: ^ Since bzr gets so exceptionally well self-tested, WDYT about syncing 1.2 for both? [07:40] Ah [07:42] (a lot of people will want 1.2 anyway) [07:43] pitti: we probably ought to take 1.2 for hardy, yes [07:43] ok, then I'll flush my syncs, thanks [08:07] Hi all! [08:08] * pitti hugs warp10, his favourite MOTU aspirant [08:10] * warp10 hugs back pitti, his favourite mentor and UDW speaker :D [08:24] mvo: is you or doko looking at bug #192992? [08:24] Launchpad bug 192992 in python-central "[hardy] pycentral crashed with ValueError in parse_versions()" [High,Confirmed] https://launchpad.net/bugs/192992 [08:28] seb128: possible, I don't know [08:29] mvo: I asked you or doko, I'll take it as you are not ;-) [08:29] where is doko? broke hardy and ran away? ;-) [08:29] seb128: I can check it out now if he is not around [08:30] mvo: there is already 30 duplicates so would be nice if somebody could look at it, upgrades are broken for everybody [08:31] bug 192992 comment 32 has a workaround (maybe even a solution) for it [08:31] Launchpad bug 192992 in python-central "[hardy] pycentral crashed with ValueError in parse_versions()" [High,Confirmed] https://launchpad.net/bugs/192992 [08:31] mvo: there is a comment pointing a preinst change, not sure if it's correct though [08:31] seb128: doko is at some OOo meeting [08:32] ok, so we better don't wait on him to fix the issue [08:35] seb128: I added an apport pattern for it now, BTW [08:35] thanks [08:36] seb128: looking at it now [08:36] * seb128 hugs pitti [08:36] * seb128 hugs mvo [08:37] pitti: good idea, I almost forgot about bug patterns ;-) [08:37] we don't use those often [08:37] for cases like these they are really handy [08:37] I recently sent an announcement about putting them in bzr [08:37] so more people can use them [08:39] right, I read this one [08:46] Amaranth: stop reassigning all the compiz bugs to libwnck ;-) [08:46] heh [08:46] I'm pondering making a compiz sucks bug there and duplicating everything === fabbione is now known as thegodfather [08:47] seb128: the one that i think i moved over a couple times is libwnck not paying attention to window extents [08:47] then there are the usual "libwnck doesn't handle viewports correctly" bugs [08:47] well, if they have the same cause and you know which one that would be nice to comment to say that and duplicate those [08:48] right, i planned to go through them afterward, had like 50 compiz bugs open in tabs at the time [08:49] ok, thanks [08:49] that'll probably be a few hours though, gotta sleep soon :) [08:49] but i'll take care of it, libwnck probably has a bunch of compiz-related dupes hanging around [08:49] btw, the broken move to workspace n, are you sure it's due to libwnck? [08:49] upsteam says yes [08:49] bah [08:50] I know one of the problems was not taking window decorations into account when figuring out how far to move [08:50] the window extents i mentioned [08:56] seb128: ooh, bug 184998 looks easy to fix [08:56] Launchpad bug 184998 in libwnck ""Move To Another Workspace:" moves to Desk 3 in Desk 2 when selectin Desk 1 in Compiz" [Unknown,Confirmed] https://launchpad.net/bugs/184998 [08:57] it seems to just move the wrong way, the reporting just happened to get lucky enough to have so little viewports it wrapped around [08:57] probably a + needs to be a - somewhere, i'll look later [08:57] Amaranth: thanks [09:03] pitti: looks like we will stay at 0.6 in hardy [09:03] asac: :-( [09:03] asac: so upstream doesn't have a release schedule yet? [09:03] Hi all. I am not sure if this the place to discuss this but is anyone working on getting latest bluez-gnome in Ubuntu? I think the recent releases also have file transfer support using obex-data-server and libopenobex-glib (none of them present in Ubuntu). [09:04] tjaalton: more or less yes. [09:04] otoh, NM 0.6.6 is planned for end of this month ;) [09:05] bah, 0.7 has all the goodies ;) [09:06] slytherin: obex-data-server is in NEW [09:06] seb128: Damn. I always forget to make sure before I ask [09:06] slytherin: I think there is a sponsor request about the new bluez-gnome but the other one needs to be accepted first [09:06] slytherin: dunno about libopenobex-glib [09:07] seb128: Thanks for info. I will try to explore what all is possible with obex-data-server. [09:07] you are welcome [09:18] asac: oh, then I better downgrade [09:18] seb128: I'll NEW obex-data-server, since I was the one who rejected it last time. [09:18] seb128: I uploaded a fix that is hopefully correct [09:18] asac: too many regressions? [09:20] pitti: too much uncertainty [09:21] y s tat [09:21] ur 4rm [09:21] on https://launchpad.net/ubuntu/hardy/+source/linux/2.6.24-9.15 under builds it says 'failed to upload' what does that mean? will there be afix before the next alpha? [09:22] good morning [09:22] pitti: we don't know _when_ upstream will release ... and if we release a random snapshot we might end up with a code base in a LTS release that upstream has no clue about (e.g. sec patches might not apply et al) [09:22] asac: ah, I see [09:22] pitti: we discussed that in -platform meeting and came to this conclusion [09:22] gud morning [09:22] Mithrandir: thanks! [09:22] I wasn't aware of the release status of 0.7 [09:23] * seb128 hugs mvo [09:23] seb128: accepted now. [09:23] mvo: thanks for the quick fix [09:23] I should probably do a MIR for it [09:23] Mithrandir: rock on ;-) [09:23] * pitti hugs mvo [09:23] that would be nice [09:24] wat would be nice [09:24] mvo: I have another question about python-apt if you are not too busy. [09:24] ya sure [09:24] anyone from xorg team ? [09:25] ssam: something went wrong with the upload of the debs build by the buildd. the uploader should got a mail with the errror message, others can currently only guess about the reason. [09:25] i dont know [09:25] slytherin: sure, fire [09:25] slytherin: I may be a bit slow answering, but will do my best :) [09:26] geser, thanks [09:26] y thanx [09:26] saispo: #ubuntu-x [09:26] mvo: I see in the examples installed in package python-apt, apt_pkg.Architecture is used to retrieve architecture. But when I try to use it I get some error, something that sound like api is not present (probably removed). Is this a bug or problem in examples? [09:27] seb128: thanks [09:29] slytherin: that sounds like a bug, I wouldn't mind a bugreport. use "apt_pkg.Config.Find("APT::Architecture") [09:30] mvo: I had tried Config.Get instead of Config.Find. :-D [09:32] mvo: Ok, .Find works. I will log a bug for the examples [09:32] slytherin: thanks [09:33] pitti: ah, ok, thanks, I checked but must have missed it somehow [09:34] cjwatson: well, the split of language-support-* into fonts/writing aids etc. is done; not the per-country split of language-pack-zh [09:36] right, that I knew [09:36] I think I just misread apt-cache show (since it also showed my installed package) [09:39] mvo, what would you think about a note that is displayed if users run apt-get dist-upgrade, pointing them to update-manager(-core) ? i guess we'd avoid a lot of breakage with a tiny change [09:39] like: "if you want to use this command to upgrade to a new distribution release, please rather use update-manager" [09:39] pitti: I have *THE BEST* apport bug [09:40] Keybuk: apport crash on apport crash on apport crash? [09:40] no, even better [09:41] ogra: It probably should also mention do-release-upgrade (it’s the same thing with a text UI, isn’t it?) [09:41] ion_, i thought that was -core [09:41] ogra: Ah, right :-) [09:41] pitti: http://people.ubuntu.com/~scott/apport-doh.png [09:41] in any case we shouold give users being used to dist-upgrade a hint imho [09:42] lol [09:42] ogra: yeah, I think that makes sense [09:42] keybuk: :-D [09:43] ogra: something more clever would be even better that can see if a actual release upgrade is performed or "just" some random upgrading [09:43] Keybuk, are you sure we're not violating a M$ patent here ? [09:43] Keybuk: "upgrade to a known-broken version! now!" :) [09:43] pitti: that's exactly what failed ;) [09:43] mvo, that would be the second iteration :) [09:43] the report is the failure to upgrade python-central [09:43] which it can't file, because I need to upgrade python-central [09:43] but I can't upgrade python-central, because it fails [09:44] generating a problem report which I can't file, because I nee*BOOM* [09:44] Keybuk: interesting self-referential case :) I think we shuold disable that check if ProblemType == Package and Package == obsolete Package [09:45] and I got a problem report because I ^\'d an app [09:45] but I think I'll ignore that ;) [09:46] awn crashed with SIGQUIT [09:46] what was it again, SIGSTOP or SIGQUIT? [09:46] ah [09:46] worth a bug report, though [09:47] a but that apport reports it? [09:47] yes [09:48] it's a valid report for most things I would have said [09:48] *shrug* [09:48] did you know, btw, that apport is actually an English word? :) [09:48] it's actually supposed to ignore SIGQUIT [09:48] Keybuk: yes, it's a German word, too [09:48] "apportieren" -> a dog fetches somethign you throw [09:48] it's a property of pets in nethack ;-) [09:48] heh [09:49] (meaning pretty much exactly that) [09:49] that's why I chose it as a name, it fitted well [09:49] in English, it means "to transfer something by mysterious means" [09:49] * Fujitsu finds apport mysterious enough. [09:49] sounds about right :) [09:49] heh [09:49] Keybuk: so, anyway, I expliticly have "if signum == str(signal.SIGQUIT): sys.exit(0)" and even test cases for it [09:49] good name :-) [09:50] pitti: hmm, maybe I did something very strange that confused it [09:50] I'm good at that [09:50] Keybuk: that's why I wonder why you still got a report; can you mail me your /var/log/apport.log? [09:52] asac: is there a bug against FF that if I have both GNOME & KDE installed, FF uses external applications randomly choosing either a KDE or GNOME equivalent depending on the phase of the moon :) [09:53] strike the moon stuff, it wouldn't be random then ;) [09:57] pitti: sure, it's my home machine [09:58] tjaalton: not that i know of [09:59] Keybuk: toghether with an explanation which application you ^\ed [09:59] asac: it can offer file-roller five times in a row, then the same for ark .. [09:59] it was avant [09:59] it was annoying me [09:59] asac: when trying the same archive, for instance [09:59] Keybuk: just tried it here, I don't get a report for ^\ [10:00] pitti: I'm wondering whether it didn't respond fast enough, and I did something else :p [10:00] tjaalton: if you have a minute, please file a bug about this [10:00] asac: sure [10:00] thanks [10:03] pitti: in fact, arguably any upgrade failure should be filed whether or not there are obsolete packages? [10:03] Keybuk: true that [10:03] . o O { if only Launchpad tracked versions } [10:04] oh [10:04] Keybuk: in fact the obsolescence check already applies *only* to ProblemType: Crash [10:04] Keybuk: apparently your report wasn't a package install/upgrade one, but a crash report [10:04] so python-central crashed while it was upgrading itself? [10:04] right [10:04] does python-central's postinst run python-central? [10:05] spethial [10:05] and I don't generally want to disable the obsolescence check, since we very deliberatly introduced it [10:06] Keybuk: yes, so it seems [10:06] if /var/lib/pycentral/delayed-pkgs exists [10:09] Keybuk: I uploaded a fix for the python-central issue some minutes ago [10:11] ArneGoetje: hm; I was just told that openoffice.org-hyphenation is the *old* way of doing things, and that it was split into several sources for easier maintenance; so we shuold migrate the language-support packs away from it [10:17] The locale generation bug yesterday doesn't happen if I give the virtual machine a GB of RAM. [10:20] yeah that bug is weird [10:20] it has killed my machine before :( [10:21] mvo, that didnt fix it completely it seems [10:21] mvo, http://paste.ubuntu-nl.org/56598/ [10:22] (i just grabbed your upload from LP) [10:23] confirmed ^^ [10:29] ogra: thanks! doko took care of it and uploaded a new (better) fix [10:29] pitti: please give-back: libept. I got hit by graphviz being uninstallable. Thanks [10:31] ogra: could you please grab that latest version https://edge.launchpad.net/ubuntu/+source/python-central/0.5.50ubuntu3 and check if that helps? [10:31] geser: done [10:34] ogra: you need to rebuild with this version [10:35] pitti: please also give-back: xen-3.2. Got also hit by graphviz. Thanks. [10:35] doko, you mean i need to rebuild python-apt ?? [10:35] ogra: yes [10:35] oh [10:35] ok [10:36] doko, mvo, ogra: just installing the new python-central (ubuntu3) made installation work for me [10:36] dholbach, well, stgraber sees it as well [10:36] ogra: ubuntu3? [10:36] the first error was gone for me after ubuntu3 [10:36] hm, weird [10:36] but introduced the byte_compile error [10:36] dholbach: yes, for python-apt it does work [10:36] err [10:37] ubuntu2 [10:38] ogra: could you please check ubuntu3? if that is ok we are good, otherwise we need to look at it again [10:39] well, that takes some more effort ... let me see to get python-central ubuntu3 into my pbuilder somehow [10:40] ogra: pbuilder login --save-after-login and install it there [10:40] yeah [10:40] thats what i'm doing :) [10:40] ogra: rebuilt package: http://people.ubuntu.com/~doko/tmp/python-apt_0.7.4ubuntu5_i386.deb [10:40] oh, wow, thats even better :D [10:40] geser: done [10:41] doko, mvo, http://paste.ubuntu-nl.org/56603/ [10:42] :/ [10:42] ogra: http://people.ubuntu.com/~doko/tmp/python-central_0.5.50ubuntu3_all.deb [10:43] ogra@ceron:~/Desktop$ dpkg -l python-central|grep ii [10:43] ii python-central 0.5.50ubuntu3 register and build utility for Python packages [10:43] ogra@ceron:~/Desktop$ [10:43] but i'll try your package [10:44] same thing [10:44] File "/usr/bin/pycentral", line 624, in byte_compile [10:44]