[02:49] does anyone have any opinions about the k3b + normalize-audio issue raised on kubuntu-devel? [03:35] k3b continues to have a coding 'error' with regard to the recognition of the installed package normalize-audio. Bug reports that go back four years still exist, and current reports still complain about the problem. See https://bugs.launchpad.net/ubuntu/+source/k3b/+bug/45026 and comment #32 by [03:35] Vanessa Ezekowits who posted a simple shell script to overcome the programming 'error' in k3b, and which identifies the underlying problem. Any k3b maintainers care to take this on? [03:35] Ubuntu bug 45026 in k3b (Ubuntu) "K3b dont find emovix-2 and normalize" [Undecided,Confirmed] [03:45] Snowhog: well, we don't have k3b maintainers per se [03:46] not to mention I just asked that question about an hour ago ;) [03:46] dtchen: Understand, I think, but someone/somebodies must be maintaining k3b, yes? [03:48] Snowhog: as a practical matter, probably only in a passing manner [03:51] dtchen: I did attempt to send and email with the details to kubu-devel@lists.ubuntu.com but got a reply that the list isn't open to non-members. Then claydoh replied and I provided him with what I tried to send. The work-around is to run a shell script that addresses the internal program error in k3b, but it would be nice if k3b it self was fixed/patched to fix this rather simple problem. [03:52] Snowhog: yes, I've been looking at it. I'm surprised that upstream k3b maintainers haven't fixed it. [03:52] simple, but more of a hack, right? [03:53] it's a terribly hack IMO [03:53] hai Snowhog my fine snowy friend :) [03:53] terrible hack* [03:54] dtchen: Maybe so, but it does work. But yes, it would be much better if k3b were itself patched/fixed. [03:54] what I haven't investigated tonight is whether Debian is carrying a specific customisation for normalize-audio such that we would need to do something ourselves, i.e., it becomes our problem and not upstream k3b's [03:55] dtchen: From what I gather, it's simply that k3b is version testing for normalize-audio instead of just checking for it's existance. I have no idea whether a specific version is required, but I'd think not, since this has been an issue for over four years now. [03:56] hey claydoh. Yeah, decided to raise the topic here. Be careful what you suggest! :) [03:59] * claydoh goes to bed [04:03] huh. In Oneiric that script seems to do the wrong thing. [04:03] dtchen: http://machine-cycle.blogspot.com/2011/04/fixing-normalize-audio-feature-in-k3b.html contains the documentation/script I'm using to fix the k3b issue. Still a hack, but... [04:03] dtchen: I'm using the above script in Natty 64-bit. [04:04] i.e., [04:04] 127|crimsun@errno:~$ normalize --version | sed -e 's/normalize /normalize-audio/g' [04:04] No command 'normalize' found, did you mean: Command 'vnormalize' from package 'lipsia' (universe) [04:04] normalize: command not found [04:04] Quintasan: also, "grok" [04:04] which isn't surprising, since the normalize-audio package doesn't ship a normalize executable [04:05] I guess the package's original normalize-audio is renamed to normalize? [04:05] oops, scroll error [04:05] dtchen: That's what I read in one of the bug comments. [04:09] ok, well, I just answered my own question above. It looks like the upstream normalize is actually normalize-audio in Debian, and as a result, rgreening applied a patch way back in Sept '09 to use that executable name [04:14] eek, Vcs entries are outdated [04:15] dtchen: When I installed normalize-audio in Kubuntu 11.04, k3b reported it, but without a path, so was showing as 'not found'. When I created/ran the script in http://machine-cycle.blogspot.com/2011/04/fixing-normalize-audio-feature-in-k3b.html, k3b then properly reported it with it's path. [04:18] bzr branch lp:~kubuntu-packagers/kubuntu-packaging/k3b [04:19] ...and it looks like we?someone? needs to check in jr's latest changes [04:26] crimsun@errno:~/Code/Kubuntu-packagers/k3b$ bzr push [04:26] Using saved push location: bzr+ssh://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/k3b/ [04:26] Pushed up to revision 28. [04:26] ok, now to look at this normalize-audio mess... [04:47] ok, so the problem is, of course, the binary being 'normalize-audio', but the version string being 'normalize 0.7.7' [04:48] dtchen: Yes, that is correct. [04:49] it's rather daft that externalBinManager()->foundBin() assumes the string will always match the executable name [05:00] dtchen: Looking at normalize-audio with apt-cache show indicates that normalize-audio replaces normalize. So the problem, as you indicate, is that the coding that originally worked for the 'normalize' package, doesn't for the replaced package normalize-audio. [05:02] Snowhog: right, and the gist of the issue is that externalBinManager() needs to grow to accept an actual executable name, not just assume the executable name is identical to the "program name" string preceding the version string [05:03] the more I look at it, the more it seems it will be a Debian- /Ubuntu-specific delta. :-( [05:03] dtchen: So, is this a 'fixable' issue? It's been way to long - four+ years - that the problem has existed without resolution. [05:03] Snowhog: well, it's able to be worked around [05:03] "fixed" is rather imprecise, I'm afraid [05:03] dtchen: That is true, but 'normal' users won't figure it out. [05:04] AFAIK upstream k3b would likely be concerned, this is a Debian- /Ubuntu-specific corner case [05:04] dtchen: And getting that group to address it is doable?? [05:05] Snowhog: you're in that group's midst [05:05] and however (un)fortunate it may seem, I don't know if anyone else is going to take up the mantle [05:05] dtchen: hehe [05:11] dtchen: From a July 2010 reply to the bug: Downloading the normalize code, and making the fix to src/normalize.c fixes the issue. [05:12] dtchen: That is, if you want to fix the source and recompile. Again, normal users should not have to do that. [05:13] Snowhog: yeah, but we also don't know who else is relying on that precise string [05:14] dtchen: Isn't the basic problem that the comparison criteria is to strict? Can the check be made looser? [05:14] if we change the source to print out argv[0] (which arguably is the right thing to do), we might break some other user [05:14] IMO the check isn't too strict, it's plain inflexible [05:14] dtchen: hehehe [05:15] dtchen: Am I correct in assuming/believing, that k3b is a mainstream KDE application, and as such, should be coded to be complient with any KDE Linux distro? [05:20] Snowhog: I don't think that's particularly revelant in this context [05:20] relevant* [05:20] sheesh, 1 AM and everything goes to shot [05:22] dtchen: Well, I'm happy at least, that someone 'in the know' (you) has looked at it and seen where the problem lies. One can hope that a viable solution can be arrived at and included in a future release of k3b. As said, four+ years of this issue is a bit 'long in the tooth'. [05:32] dtchen: Thank you for looking at this, and the discourse. I'm off for the evening, but I'll check back in tomorrow. === yofel_ is now known as yofel [07:05] apachelogger: <3 :) [07:37] morning [07:52] Hi Kubuntu devs. A KDE translator asked me why he couldn't see the latest KDE translations in Launchpad, and it turns out that there hasn't been an upload of the kde-l10n-* packages for a while. When you've got a minute, may I ask you to upload these packages for Oneiric? [07:57] apachelogger: ^ === Quintasan is now known as Quintasan_ === Quintasan_ is now known as Quintasan === Quintasan is now known as Quintasan_ === Quintasan_ is now known as Quintasan === Quintasan is now known as Quintasan_ === Quintasan_ is now known as Quintasan [09:01] * apachelogger waves fist because of work [09:29] \o [09:36] apachelogger: ping [09:36] hmm [09:36] more like DarkwingDuck [09:38] * apachelogger waves fist more and more === Squt is now known as Sput [10:38] yofel: ping [10:58] yofel: i have no idea, it built fine here, twice [10:58] apachelogger: want to review my pkg-kde-tools l10n changes before I upload? https://bazaar.launchpad.net/~kubuntu-packagers/pkg-kde-tools/pkg-kde-tools/revision/322 [10:59] yofel: i'm a bit busy this week, will be back to work on monday [11:00] Oo [11:00] I just got a comment on the most original neon post [11:00] wtf [11:00] what [11:00] debfx: why merge findfiles from stable? [11:02] apachelogger: that is what's used once the development version is branched [11:03] oh [11:03] rules also grabs stable [11:03] well [11:03] fair enough [11:03] debfx: looks good to me, I think we shoudl do something about the wget though [11:04] plz report a bug and assign it to me and add it to the packaging blueprint [11:05] how do you want to change that? [11:05] (without cloning the whole repository) [11:07] shallow clone [11:07] or perhaps I get a better idea [11:25] we have quite some QA issues regarding patches [11:26] I've just removed 3 patches from kde-workspace that were either refreshed wrongly or upstream reverted the commit [11:40] debfx: who uploaded it? [11:44] apachelogger: I haven't tracked down when those patches were refreshed [11:45] debfx: probably bambee did not revert all changes or someone uploaded the wrong workspace [11:45] I know that the first proposed workspace merge was bogus WRT patches [11:46] apachelogger: I've reverted all patches [11:47] I have just refreshed the broken ones [11:48] debfx: what was the problem? [11:49] apachelogger: they were broken even before this cycle [11:49] all kaput [11:49] win win win [11:50] bambee: nothing with your changes, just our patches being broken in general [11:50] oh :) [12:21] * apachelogger is overengineering the l10n rules [12:21] \o/ [12:22] your time would be better spent reviewing patches ;) [12:24] * apachelogger should be doing phonon things [12:33] [kde-l10n-common] Harald Sitter * apachelogger@ubuntu.com-20110713123336-tnpv7b2ek3cji489 * debian/ (README.source build-l10n.sh changelog control rules) (log message trimmed) [12:33] * Introduce new targets: - get-l10n: called by the build script and - [12:33] get-desktop: prerequisites all targets to get desktop file translations - [12:41] http://blog.linuxmint.com/?p=1791 [12:41] LOLOLOLOLOLOL [12:43] >http://blog.linuxmint.com/?p=1791 [12:43] bleh [12:43] >The lack of performance and the amount of resources needed by the Kubuntu base were identified as an issue [12:44] so they will be switching to Debian KDE packages [12:44] lol [13:24] Quintasan: lol [13:25] good luck having a rolling release with Debian ^_^ [13:26] I'm running Ubuntu Oneiric. Have all the KDE 4.6.90 packages landed? Is it okay to install and test kubuntu-desktop right now or should I wait more? [13:27] cdbs: please see the topic\ [13:28] *ahem* okay [13:28] * cdbs decides to wait [13:29] everything you get with kubuntu-desktop should be uploaded [13:30] you might want to test it in a VM first though :) [13:31] thanks [13:32] shadeslayer: more like, how can our packages really differ performance-wise from Debian's? [13:32] We are using the same base and we don't build some stuff [13:32] well that too [13:33] Unless we are doing something horribly wrong performace-wise they should be the same [13:33] but Debian more or less focusses on stability [13:33] the blog post mentions use of resources [13:33] ( thats the impression i get anyways ) [13:33] That's very ambiguous term [13:33] Whatever [13:34] ^^ [13:34] * Quintasan goes for a beer [13:34] Is Debian also moving to 4.7? [13:34] The last time I checked, they were on 4.4 [13:34] They will someday [13:35] Quintasan: do you know which packages are missing in the package set? [13:35] at least libkexiv2 and libkipi [13:37] debfx: kdegraphics-thumbnailers [13:38] marble [13:38] parley [13:38] rocs [13:38] ksnapshot [13:39] debfx: nothing else comes to mind nor is not returned by grep [13:43] ok, thanks [13:58] o/ [13:58] apachelogger: pong? [13:59] ScottK: do you know what happened to the live images? [13:59] They've been failing recently, I think due to /run stuff, but I'm not sure. [14:01] cdbs: Debian has 4.6 in unstable, not sure how much of 4.7 they did yet. I only know they did some of the language bindings [14:02] too bad, would be interesting to know if everything is installable [14:04] yofel: how is the blog post? [14:04] debfx: I'll do a check in a chroot, but I believe there was something that didn't work yet [14:04] apachelogger: [] [14:05] ah good, kross is in [14:07] debfx: in fact now, kubuntu-desktop has no dependency issues in O [14:08] my google exploded [14:08] again o.O? [14:09] yofel: ah good, there are still a some upgrade issues [14:09] hopefully the kdegraphics-libs-data transitional package will fix that [14:10] I'll install the packages as a test [14:11] went fine, so I believe the only breakage in oneiric should be the /run business [14:12] hm, wasn't gwenview in the default install? [14:12] (which isn't uploaded yet thanks to broken licensing) [14:12] I'll file a bug about that [14:13] oh how I love file overwrite errors [14:13] (thanks to missing epochs) [14:14] I found the overwrite errors that come from 4.6.4/5 -> 4.6.90 uprades thans to << 4:4.6.3-1ubuntu1 replaces more fun [14:16] yofel: what is with gwenview licensing? [14:16] just fix it already [14:16] apachelogger: the docs have the license comment out, thus no license [14:16] *commented [14:17] oh yeah [14:17] I told agateau already [14:18] well, not fixed [14:18] someone simply fix it :P [14:18] * yofel thinks apachelogger would be the ideal person to do that [14:18] bug 794513 is going to get beatin for removing quanta [14:18] Launchpad bug 794513 in kdewebdev-kde3 (Ubuntu) "Please remove kdelibs and kdewebdev-kde3 from the archive" [Low,Confirmed] https://launchpad.net/bugs/794513 [14:18] yofel: no time [14:18] ... [14:18] I got you commit access [14:19] so use it :P [14:19] I don't mind adding license copies, but I'll try to get some gwenview dev first before changing the licensing [14:19] yofel: apachelogger can you refresh my memory regarding this issue? [14:20] agateau: you comment out the FDL license markup in your documentation as to work around missing FDL copy problems [14:20] which in turn is a problem as now your documentation is not licensed at all [14:20] which makes it non-free content [14:21] ScottK: I've put 2 packages into NEW for you [14:21] apachelogger: what would be the best solution in your opinion? license it as GPL or FDL? [14:22] every other package uses FDL, so I would say keep that [14:22] you've got the FDL statement already in there, just commented out [14:22] IMHO the question should be FDL or CC, GPL is a terribly unsuitable license for documentation IMHO [14:23] agateau: I'd go with FDL, all other KDE documentation is [14:23] + a full copy of the GFDL-1.2 is missing as COPYING.DOC [14:26] apachelogger: sounds good, but I need to contact the doc authors before doing this change [14:27] sure [14:27] so, I think our new l10n rules are ready [14:28] [kde-l10n-common] Harald Sitter * apachelogger@ubuntu.com-20110713142833-pr4xwf6rk0781duj * debian/config add config, all should be good now [14:45] debfx: Looking [14:50] yofel or debfx: Did patches/step_needs_-lcln.diff go upstream? [14:51] step accepted. [14:53] yofel: apachelogger: just sent a mail to ask doc authors their agreement on licensing Gwenview doc under FDL [15:01] debfx, dpm: we have a good chance at breaking all of KDE l10n this cycle [15:01] preparing packages right now [15:02] apachelogger, oh, why's that? [15:02] agateau: thanks [15:03] ScottK: looking at it again [15:03] dpm: all sorts of upstream changes [15:04] naming, architectural etc. [15:04] ScottK: no, it's an undocumented patch from Debian [15:04] we really need some better implementation for all this [15:04] too much possibility of failure [15:04] s/of/for/g [15:04] apachelogger meant: "too much possibility for failure" [15:05] debfx: Looks like something ~straightforward to go upstream. [15:05] ScottK: actually, I believe we can drop that [15:05] from cmake: [15:05] -- qalculate found and cln is:-lcln [15:06] It's not worth having more diff from Debian over. [15:06] apachelogger, ok, let me ask you more about this tomorrow (finishing off my UDW talk right now) [15:06] See if they'll drop it. [15:08] svuorela added that in 4.6.96 "* Add patch to also build with -lcln when building step with qalculate" [15:08] step seems to build prefectly fine without that though [15:09] errr... 4.2.96 [15:10] step binaries accepted. [15:11] I'll drop it from bzr, it builds with -lcln even without the patch [15:12] Talk to Debian too. [15:19] yofel: is rc2 wip already? [15:20] apachelogger: not yet, although I wanted to start with kdelibs in the evening [15:20] we were still fixing broken packages [15:20] could we please finish rc1 before that? [15:21] debfx: define finish [15:21] well, I would like to get gwenview, cantor and kate in at least before doing RC2 [15:21] forget the other bindings [15:22] why is that? [15:22] I'll take a look at ksaneplugin [15:22] +gwenview is postponed anyway [15:22] upload kate, kdegraphics-strigi-analyzer, mobipocket and svgpart [15:22] well, kate is currently unfunctional in oneiric, cantor should be fine to upload, rc2 won't be different, and ok, forget gwenview [15:22] yofel: blog post? [15:23] apachelogger: do you want me fixing packages or spending hours on wondering what to write about our work? [15:23] and make sure upgrades work [15:23] yofel: I think I answered that question at least once [15:23] you did indeed -.- [15:23] well [15:24] * apachelogger starts writing a post then, if yofel doesnt have itme [15:25] [lp:~kubuntu-packagers/kubuntu-packaging/step] Philip Muškovac * 4 * debian/ (4 files in 2 dirs) drop step_needs_-lcln.diff since it's not needed anymore [15:26] I need to write a kubuntu.org post about RC1 (kde and kdepim) or users are going to kill us for not communicating. [15:27] is there a generic kde project on launchpad? we need one to link the packages to [15:28] https://launchpad.net/kde ? [15:29] yofel: I've tried that but it doesn't work [15:29] apparently you can't link them to project groups [15:30] :/ [15:33] I'll just use the old projects like kdebindings [15:33] [lp:~kubuntu-packagers/kubuntu-packaging/ksaneplugin] Philip Muškovac * 7 * debian/copyright That's LGPL, not GPL [15:35] "we need one to link the packages to" why? [15:35] [lp:~kubuntu-packagers/kubuntu-packaging/ksaneplugin] Philip Muškovac * 8 * debian/copyright use the version of the BSD-3-clause license that's shipped with the package [15:35] apachelogger: upstream bug report links I believe [15:35] we do not track upstream reports [15:35] *shrug* then [15:36] Upstream branches (which we also don't care about) [15:36] Translation links (I don't think we care) [15:36] most of those are under project-neon/ anyway [15:36] UDD branches (I don't think we care anyway) [15:36] we certainly don't [15:40] ksaneplugin should be fine to upload [15:44] I think it's useful to be able to add upstream bugs [15:44] [lp:~kubuntu-packagers/kubuntu-packaging/svgpart] Philip Muškovac * 9 * debian/control Fix Vcs links and control file layout [15:45] debfx: you can use any random kde project for that [15:45] for that reason it is a bug that the kde project cannot be used for that [15:46] [lp:~kubuntu-packagers/kubuntu-packaging/svgpart] Philip Muškovac * 10 * debian/ (control copyright libsvgpart.install) wrap-and-sort cleanups [15:46] apachelogger: right, file a bug against launchpad then [15:47] svgpart should be ready too [15:50] debfx: how's your build status page progressing btw.? [15:59] yofel: haven't worked on it any further [15:59] k === mgraesslin_ is now known as mgraesslin [16:10] shadeslayer: *are* you going to fix kate soon? If not I'll do it [16:11] blargh [16:11] yofel: If you are looking for someone to upload then ping me [16:12] I will be reading a book [16:12] Quintasan: see wiki [16:12] yofel: cantor? [16:12] not in damn packageset [16:12] well, it's not up AT ALL [16:13] * Quintasan looks at it and uploads [16:13] ksaneplugin and svgpart aren't either. Recheck those though before upload [16:13] Why is r stuff commented out? [16:13] universe [16:14] and kalgebra is not in tarball? [16:14] If cantor won't hit new I can upload it. [16:14] no, cmake detection broken upstream [16:14] :/ [16:15] ScottK: Can you upload cantor? I don't really feel like uploading this and then getting to know it's rejected [16:17] shadeslayer: WRAP-AND-SORT FFS [16:17] ffs? [16:17] for !@#@#% sake [16:17] which package? [16:17] ksaneplugin [16:17] Quintasan: Sure. [16:17] cantor too [16:18] cantor would be me, and I didn't know about w-a-s back then [16:18] ScottK: Thanks. [16:18] I did run wrap-and-sort on svgpart though [16:18] yofel: I see, but shadeslayer knew about that [16:18] not when he did ksaneplugin I believe ^^ [16:19] Quintasan: I don't see it got uploaded before. Isn't it New source? [16:19] That'll need me to acceptit. [16:19] ScottK: It is [16:19] It is which? [16:20] It is entirely new package [16:21] Which you can't upload because you aren't MOTU? [16:21] debfx: Can you upload cantor so I can New it ^^^ [16:21] oh wait [16:21] ... [16:21] * Quintasan uploads [16:21] debfx: Nevermind [16:22] * Quintasan turn on his brain [16:27] grrrrr [16:27] shadeslayer: ping ping ping [16:28] ScottK: Please disregard ksaneplugin for now [16:33] shadeslayer: Fix ksaneplugin tarball and changelog [16:34] since they both suck [16:34] ScottK: cantor uploaded [16:42] Quintasan: what's wrong with the tarball? I can redo the changelog [16:45] yofel: let shadeslayer do [16:45] it [16:51] Quintasan: if he seriously wants to get back to work on monday then I'll rather fix it [16:51] lol [16:51] k [16:51] the changelog doesnt mention the repack [16:53] hm, then only the changelog should need fixing, what's wrong with the tar? [16:58] cantor source accepted. [16:58] or not. lp fails [16:59] Second try worked [16:59] [lp:~kubuntu-packagers/kubuntu-packaging/ksaneplugin] Philip Muškovac * 10 * debian/control fix hadling of versions in breaks/replaces [16:59] Quintasan: Should I reject ksaneplugin? [16:59] ScottK: Please do [16:59] ScottK: yes please [16:59] [lp:~kubuntu-packagers/kubuntu-packaging/ksaneplugin] Philip Muškovac * 11 * debian/copyright remove trailing spaces [17:00] Done [17:01] oh, akonadi 1.6.0 is out [17:02] I'll do that later [17:07] [lp:~kubuntu-packagers/kubuntu-packaging/ksaneplugin] Philip Muškovac * 12 * debian/ (changelog control) Add a proper changelog entry and description [17:07] yofel: tarball unpacks to ./ [17:07] not ./ksaneplugin-4.6.90 [17:07] well, description is still lacking, but I can't find anything more [17:07] didn't here... [17:08] Didn't? [17:08] oh wait, you're right... [17:08] :/ [17:08] dpkg-source unpacked it in ksaneplugin-4.6.90+repack/, but the tar indeed has ./ [17:09] repack1 is in order... [17:10] [lp:~kubuntu-packagers/kubuntu-packaging/ksaneplugin] Philip Muškovac * 13 * debian/changelog repack again [17:12] Quintasan: new tar uploaded to ninjas [17:21] yofel: Thanks [17:24] [kde-l10n-common] Harald Sitter * apachelogger@ubuntu.com-20110713172406-seaeazgdrgpeb3q7 * debian/ (build-l10n.sh changelog) releasing version 4:4.6.90-0ubuntu1 [17:25] [lp:~kubuntu-packagers/kubuntu-packaging/akonadi] Philip Muškovac * 31 * debian/changelog New upstream release [17:47] cool, kstars has missing license copies again [17:47] * yofel fixes [18:41] [lp:~kubuntu-packagers/kubuntu-packaging/kstars] Philip Muškovac * 2 * debian/ (not-installed changelog control copyright) fix up packaging [18:42] ok, this should be right now except that libindi in the archive is too old (but it's optional) [18:52] yofel: Thanks for fixing ksaneplugin, uploading [19:00] ScottK: Are seriously considering moving to alioth or it's just a suggestion? [19:01] ScottK: Also, ksaneplugin uploaded, this time it is working [19:03] Quintasan: I think it's worth discussing. [19:03] For our packaging branches it doesn't matter if they are in LP or not. [19:04] It certainly doesn't [19:04] I can do git-buildpackage -S as well [19:04] Are there any benefits? [19:05] uh, you'll have a sane VCS? [19:05] Is bzr THAT insane? [19:05] bzr is fine. [19:05] well, not really, but it would make working with debian easier [19:07] That's a benefit. [19:10] bah, cantor failed on armel :/ [19:15] yay, rosetta spam again... [19:21] ScottK: do you get what's wrong on https://launchpadlibrarian.net/75126316/buildlog_ubuntu-oneiric-armel.cantor_4%3A4.6.90%2Brepack1-0ubuntu1_FAILEDTOBUILD.txt.gz ? [19:22] according to launchpad libspectre was built on armel... [19:23] Looking [19:23] hi, i don't know where to ask my question. please just say if i am wrong here. i want to make a small patch to kmail in the experimental ppa. I installed the build-deps and the source from the ppa. Fine so far. dpkg-buildpackage takes some time (some hours to be exact on my rather slow laptop) is there something like a build service? or how do you test patches for such a big package? any help/hint/link appreciated. [19:25] ovidius: If you have an LP account you can have your own PPA for this [19:26] yofel: What happens if you try to install libspectre1 on your armel box in a oneiric chroot? [19:26] ScottK: checking [19:28] ksaneplugin source accepted. [19:34] this totally doesn't make sense: http://paste.kde.org/95779 === yofel_ is now known as yofel === mgraesslin_ is now known as mgraesslin [19:42] ScottK: aptitude: libgs9: Depends: libgs9-common (= 9.02~dfsg-2ubuntu1) but it is not going to be installed. [19:42] archive inconsistency I guess [19:46] * yofel makes an attempt of building kdelibs 4.6.95 on armel.. [19:48] yofel: https://felix.fobos.de/kubuntu/kubuntu-buildstatus.htm [19:49] ping me if a package is missing [19:50] kubotu: order cookies for debfx [19:50] * kubotu slides a whole bunch of world's finest cookies down the bar to debfx. [19:50] debfx++ [19:51] yofel: https://launchpad.net/ubuntu/+source/ghostscript/9.02~dfsg-3ubuntu1/+build/2623476 is the reason [19:51] :/ [20:06] debfx: kde4libs is missing on your page. kdelibs is kde3 [20:07] * debfx blames the wiki [20:09] ksaneplugins binaries accepted. [20:19] [lp:~kubuntu-packagers/kubuntu-packaging/kdelibs] Philip Muškovac * 363 * debian/ (14 files) those symbols aren't i386 specific === ximion1 is now known as ximion === ximion is now known as ximion1 [21:23]