=== ember_ is now known as ember [02:04] debian native packages in revu should have a version such as 0.1.2ubuntu1 right? [02:05] debian native packages should not in revu [02:06] you can subscribe it to ubuntu-universe-sponsor directly [02:06] lidaobing: it would be unusual, but I don't see why it doesn't need a review [02:06] with the status confirmed and no one assigned. [02:06] lidaobing: debian native != unmodified from debian [02:06] lifeless, sorry, i mis-understanding it [02:07] lifeless, i thought it as a synrequest [02:07] savvas: I don't think there is a sensible version number, but that would make sense to me [02:07] lidaobing: I know; its ok :) [02:08] I meant the debian native versioning, sorry for misleading hehe [02:09] savvas: you didn't ;) [02:10] I also wonder if I should recommend to a friend of mine, http://revu.ubuntuwire.com/p/pdfshuffler to go to Debian directly [02:10] there's an ITP bug open but the person didn't reply or make any progress as far as I know [02:16] oh and one more thing, do you think I should ask him to remove the debian/ folder from the original source, to stop being debian native? seems more appropriate [02:26] savvas: that has nothing to do with being debian native [02:26] failing to have an orig tarball and using a native version number do that [02:27] if its not something that is intrinsic to debian, it shouldn't be a native package [02:27] just put -1 in the changelog [02:27] hi [02:27] and give it a package_version.orig.tar.gz [02:28] what do i put as the version number in the name of the tarball when what I am packaging just comes as a script with no version numbers, just a release history with dates? [02:29] lifeless: ok thanks, I'll talk with him later :) [02:29] i.e. foo_20071208.orig.tar.gz [02:30] looks fine [02:30] nothing stops a date being a version number [02:31] just rember that you will need an epoc if they switch to "normal" version numbers in the future [02:31] or you could do 0~2007... [02:31] true, that would be my choice "just in case" [02:32] k0p, thanks [02:32] btw, hiya lifeless :) [02:33] another thing? [02:34] i can log into revu but see no link where I can upload packages [02:34] I have my gpg key uploaded to launchpad [02:34] ode: you dont upload via the web interface, you use dput ( like the archive and ppa's ) [02:35] ode: https://wiki.ubuntu.com/MOTU/Packages/REVU [02:36] thanks [02:37] * imbrandon ran across a "python for dummies" book on his shelf he has never read [02:37] heck , i dont even rember buying it [02:38] the videos from this years pycon are now on bliptv [03:05] james_w: I am not sure that I understood your comment to my REVU upload - scantailor [03:06] there is a stock README.Source about using simple-patch-sys [03:06] *is there? [03:06] I can't seems to find one bundled in cdbs [03:09] can someone point me to some documentation regarding install time package detection with dpkg/apt? [03:35] artfwo: See https://wiki.ubuntu.com/README.sourceHowTo (it's not official, but maybe better than nothing?) [03:36] jmarsden: yes, that is exactly what I was looking for, thanks! [03:36] No problem. [03:58] dpkg-checkbuilddeps: error: syntax error in debian/control at line 16: first block lacks a source field [04:04] Does the first line of your debian/control file start: Source: [04:04] with a source package name after that ... [04:23] ScottK: ? [04:23] qiyong: Can you pastebing your debian/control file? [04:24] Package: fvmm [04:24] ScottK: ^ [04:24] From the Ubuntu archives? [04:24] !pastebin [04:24] pastebin is a service to post multiple-lined texts so you don't flood the channel. The Ubuntu pastebin is at http://paste.ubuntu.com (make sure you give us the URL for your paste - see also the channel topic) [04:24] ScottK: local pkg [04:25] OK. If you pastebin the debian/control I can probably tell you what's causing that error [04:25] ScottK: can i /msg you? [04:25] OK [06:03] Is there a guide anywhere for breaking a package up into sub-packages? There's one that has a three-part setup (graphical client, cli server, cli robot), and I'd like to be able to install the server/robot portions without the graphical dependencies. [06:04] tonyyarusso> Add more packages to debian/control. In debian/rules, install first to debian/tmp, then use dh_install and debian/[packagename].install files to move the files to debian/[packagename] directories. [06:04] Or if using CDBS, this would already be done for you. [06:05] Look at any existing source package with multiple binary packages for an example. [06:06] Do you have a particularly good example to recommend? [06:07] (Preferably a relatively simple one too) [06:08] debhelper or CDBS? [06:11] debhelper [06:15] look at geanygdb which just entered karmic. [06:15] that uses debhelper [06:15] or man dh [06:16] no wait, geanygdb is a single binary package [06:16] hmmm [06:28] tonyyarusso: its pretty stock; you add packages to control [and install/doc/dirs files to match], thats it usually. [06:33] tonyyarusso> You could look at avidemux for debhelper << 7, or gtkpod for debhelper 7 [06:34] avidemux was a single package up to version 2.3 - since 2.4, it's split into avidemux, avidemux-common, avidemux-cli, avidemux-gtk and avidemux-qt [06:35] wait, no avidemux-gtk [06:38] Gosh, Launchpad really is the new Facebook. https://edge.launchpad.net/~ubuntu-photographers [06:39] LucidFox: -cyclists too [06:40] what is the debian/files format? [06:46] qiyong> It's generated by the build tools, so you don't have to worry about it :) [06:46] http://www.debian.org/doc/debian-policy/ch-source.html#s-debianfiles [06:54] good morning [06:54] * LucidFox waves at dholbach [06:55] hiya LucidFox! === TheMuso_ is now known as TheMuso [07:29] Damnit, quassel, stop crashing on hiding buffers. [07:44] That's apparently a tough one for them as the backtraces they've gotten on it don't point to any code in Quassel. [07:54] I wonder if it would make sense to maintain a version of Quassel with pure Qt, built without kdelibs [07:54] that's just asking for packaging trouble, though [07:56] And would it make sense to merge it from Debian? [07:58] Since I used it with KDE, I'd think not. I've vaguely considered trying to build both KDE and Qt versions from the same source package. [07:59] If you figure out how to do that sanely (I haven't really looked into it), I'm open to it. [07:59] I did that with kde4-style-qtcurve by doing a double build, but it had only one binary package. [08:01] You'd end up throwing away the 2nd quasselcore build as it would be the same either way. [08:03] * LucidFox nods [08:03] So it would add quassel-nokde and quassel-client-nokde to the existing quassel, quassel-client, quassel-core and quassel-data [08:08] I'd call them -qt4, but yes. [08:18] gnight all [08:21] * nixternal hugs dholbach [08:22] * dholbach hugs nixternal back [08:32] good moaning [08:48] ScottK> That's going to be some unwieldy debian/rules. http://paste.ubuntu.com/169357/ [09:00] LucidFox, you call that unwieldy? o_o [09:04] directhex> Compared to the current CDBS-based debian/rules, ye [09:07] try http://svn.debian.org/viewsvn/pkg-cli-apps/packages/ikvm/trunk/debian/rules?revision=4424&view=markup for an extra-special rules which i claim all appropriate blame for [09:19] directhex> heh, even dh 7 wouldn't shorten it that much [09:19] LucidFox, there's so much voodoo in it i don't know what adding dh7 medieval black magic would do - probably nothing healthy [09:19] hahaha [09:21] LucidFox, that was weeks and weeks of work though, including round-trip discussions with upstream [09:21] Wow. [09:21] and even HE recommends people just use the binaries, because building is a pig [09:22] he helped me pin down how to create my own bootstrap binaries, which i need to provably do for them to be bootstrap binaries (and not just generic evil bundled closed-source things). the trick is grabbing half-build objects from halfway through the build process [09:41] directhex> Why doesn't upstream just create a sane build system? === dpm_ is now known as dpm [09:42] LucidFox, i think he finds it easier to split out the "external" parts (modified openjdk and classpath sources) from his own stuff [10:01] is the info on http://retro.apebox.org/keysign.pdf combined with my passport sufficient for keysignage at UDS? [10:06] popey: when you remove spam - do you just "remove wiki page" or do you have permissions to "remove spam"? [10:06] depends how it was spammed [10:06] I meant the regular 2768246kjl24nhzl42ljh426hj spam :) [10:06] there have been a lot of pages recently created called MoinMoin/SomeRandomName, the spammers attach text files to those pages [10:06] or is there another form of regular spam? [10:07] some is just links on pages, some is in attachments [10:07] Hey, I apologize if this is off-topic, but it's a quick question: Do I need special permission to create a personal wiki on wiki.ubuntu.com? I've read that it's a step in the Ubuntu membership process. [10:07] evanrmurphy: no, just go for it :) [10:07] evanrmurphy: no just go ahead and create a page at http://wiki.ubuntu.com/YourName [10:08] dholbach, popey: Thanks! [10:08] dholbach: did I understand your question correctly? [10:08] popey: yes, thanks :) [10:08] https://wiki.ubuntu.com/HelpOnInstalling/ZicuaDihulav is an example [10:08] just looking at cash-advance-loans :) [10:08] you can spot them a mile away, if you go to https://wiki.ubuntu.com/RecentChanges and search for txt [10:09] they kinda stand out [10:09] dholbach: Yes you understood perfectly. P.S. your tutorials and packaging sessions on Ubuntu development are excellent. [10:09] evanrmurphy: thanks a lot for the flowers :) [10:10] :) [10:10] dholbach: Scratch that first sentence, I misread popey's "dholbach: did I understand your question correctly?". Enjoy the flowers. :) [10:11] dholbach: have you noticed that the person _just_ spammed the wiki [10:11] note the user ~David, doesnt exist [10:12] popey: agy just told me that a fix for that will hopefully be rolled out today [10:12] nice [10:12] thanks [10:26] ScottK> Why is quassel built with nostrip? [10:34] dholbach, so how would a new MOTU go about getting an @ubuntu.com address he can stick on the end of his GPG key? [10:35] directhex: https://wiki.ubuntu.com/Membership has a link to it [10:35] https://wiki.ubuntu.com/UbuntuEmail [10:36] ooh, automagic AND functional! [10:40] directhex> Ooh, an interview already. [10:40] * LucidFox reads [10:41] LucidFox, prepared it weeks ago, back when the evil ubuntu conspiracy had already decided i was going to be a MOTU ;) [10:41] Haha [10:41] "Age: 25, if Evolution’s calendaring is to be believed." [10:41] LucidFox: I'm sure directhex practised giving interviews in front of his mirror months ago [10:42] ^_^ [10:44] dholbach, in a manner almost identical to http://xkcd.com/578/ as it happens [10:52] james_w, nixternal, thanks for reviewing and advocating scantailor! [10:53] now if anyone could take some time to review http://revu.ubuntuwire.com/p/supercollider that would be much appreciated :) [10:54] Every time I use dput, I'm worried of automatically typing "ubuntu" instead of "revu" or "ppa" [10:54] oh, remind me to kill my default target [10:58] How does the Behind MOTU process work? [10:58] artfwo: no problem, it was a good job [10:58] LucidFox: dholbach mails each new MOTU with a questionaire [10:58] oh [10:59] LucidFox, directhex: see the end of https://wiki.ubuntu.com/DeveloperGuide/Uploading [11:00] Thanks [11:02] <\sh> moins [11:04] <\sh> thekorn: ScottK : Thx (just readnig your queries :)) === cherva_ is now known as cherva === azeem_ is now known as azeem [12:26] Why are my packages still being signed with the old key :S [12:27] Where do I choose which key debuild uses? [12:27] ~/.devscripts.cf [12:27] or something like that [12:27] DEBSIGN_KEYID in there [12:27] if not specified then it's matched by GPG [12:30] thanks, it worked [12:30] ogra: A new Gobby with undo hit Karmic (source package gobby-infinote, binary gobby-infinote/gobby-0.5); test server available on gobby.0x539.de. [12:30] cute ! [12:32] ogra: Not protocol-compatible to the old, sadly, and not entirely finished, but you can try it out. (It works, it was pretty stable, but it is not yet feature-complete for 0.5 and there could still be slight protocol changes.) [12:36] LucidFox: you could always delete your old key. [12:36] and back it up somewhere [12:37] Nah, I'll leave it until the expiry date [12:37] expiry eh.. [12:37] my keys have no expiry [12:43] Hi guys, if someone's got a little time can they check I'm not going completely mad? ;) It seems libdkim-dev is missing from hardy/universe yet the package source is set to build that package, and if I build it myself I do get the libdkim-dev built along with libdkim0... [12:46] * Hobbsee looks [12:47] that's weird [12:47] Hobbsee: Yeah, I think I found the .deb in the right place but it was just absent from Packages(.gz) iirc [12:48] cprov: any idea why that's not there? [12:52] Just digging around some more... the package history seems to show it being superseded by dkim-milter 2.0.2.dfsg-1ubuntu1, but then that version was deleted... [13:03] Looking through the Planet Ubuntu /heads directory, it kind of bugs me that some people apparently intentionally chose the *worst* photos they could find :) [13:06] LucidFox: Hey, some people don't even use photos! *nudge* *nudge* :) [13:06] soren> Heh. [13:06] I have a reason not to. *wink* [13:07] Secret agent, eh? Fair enough. === rgreening_ is now known as rgreening [13:23] my chikkin.png > a photo [13:39] ajmitch: should treecc be removed from Ubuntu too? [13:40] which treecc? aren't there two? [13:40] precisely [13:40] rename one "bushcc". it's the only way. [13:55] I'm tempted to start a quote database for Ubuntu channels [13:57] LucidFox, make a fortunes file, for inclusion in email signatures! [14:07] james_w: hi. you commented on bug 373512 that it needs to be a fake-sync. can you point me to some documentation on this? [14:07] Launchpad bug 373512 in ffmpeg-php "Sync ffmpeg-php 0.6.0-1 (universe) from Debian unstable (main)." [Wishlist,Confirmed] https://launchpad.net/bugs/373512 [14:07] Ampelbein: you need a motu to do that for you [14:08] I subscribed the sponsors again, someone should act on it [14:08] james_w: ok, thanks. [14:08] or someone here could do it for you now, it doesn't take long at all [14:09] i could do it. what am i doing? are there likely to be pirates? [14:10] .orig differ in debian and ubuntu, but we want to sync [14:10] so grab the debian package, and the ubuntu tarball [14:10] check the tarballs don't differ in contents [14:11] then upload a build1 based on the debian package, but built against the ubuntu changelog [14:11] if that makes sense [14:11] do i need to build1 it? i thought fakesyncs usually kept the debian versioning [14:11] actually it's ubuntu1 isn't it? [14:11] we don't want the autosync to fall over it I guess [14:12] ubuntu1 would be just a merge, not a fakesync? [14:16] I thought fakesyncs were ubuntu1 [14:17] Hello, is onkarshinde here ? [14:18] slytherin [14:18] AnAnt> He's slytherin here, so no [14:18] If the package already has a ubuntu* version, you bump it, otherwise add build1 [14:18] judging by the user list [14:18] mok0> Isn't this for rebuilds? [14:18] yes [14:18] isn't that the issue? [14:19] are quilt-based source packages supported yet ? [14:21] if a package that I maintain was using quilt patch system, but all patches got removed (since they were applied upstream), do I have to remove quilt from Build-Deps ? [14:21] nixternal: thanks for uploading django-openid-auth :) [14:21] wth? http://packages.qa.debian.org/b/bash-completion-lib.html [14:21] Any more opinions on the gtkpod-aac issue? [14:22] james_w: ? [14:22] just a really odd package [14:23] oh [14:23] forking an old version of a package in order to take it somewhere that the new maintainers of the package want to go anyway [14:23] hehe === asac_ is now known as asac [14:27] Gawd, sourceforge is slow [14:34] james_w: depends on bash3 [14:35] erm, nevermind [14:35] the new version is 4 not 3 [14:37] james_w: would you mind pushing bug 373845 again? Sorry for my mistake, I've built this package so many times that I forgot to actually build the updated one. This time I've tested it. ;) [14:37] Launchpad bug 373845 in python-django-tagging "Sync python-django-tagging 0.2.1+svn154-2 (universe) from Debian unstable (main)." [Wishlist,New] https://launchpad.net/bugs/373845 [14:38] kklimonda: quilt has been synced now? [14:38] james_w: yes [14:39] ok [14:39] I've just built it on karmic pbuilder. [14:39] I don't have time now I'm afraid [14:39] sure [14:39] It isn't that important - I just wanted to remind you. :) [14:39] np [14:39] put a note in the bug report [14:40] then other people would consider it [14:40] and it will mail me [15:11] Heya gang [15:14] I'd like to ask any Vim experts how would I handle a bug like bug 310213 [15:14] Launchpad bug 310213 in vimoutliner "README.debian does not explain how to activate vimoutliner addon" [Undecided,Confirmed] https://launchpad.net/bugs/310213 === awe is now known as awe-afk [15:16] I have a package, which includes README.Debian with explanations about vim-addon-manager, but since it's useless without vim-addon-manager will it really hurt, to Depend on vim-manager instead of recommending it? [15:19] artfwo: I think the current situation is fine, but you could explain that if they don't have the vim-addon-manager command they should install that package [15:19] I am thinking of that as well, will an OK-only debconf dialog be sufficient? [15:20] for what? [15:20] for explaining this to the user [15:20] nope [15:20] README.Debian then? [15:20] that's fine [15:21] using debconf for this isn't a good idea === awe-afk is now known as awe [15:21] that's what I have already done [15:21] most people won't see it [15:21] for those that will see it it will stop the installation, just to tell them something they might already know [15:22] but I've just have a discussion with an upstream author, who wants a hard dependency on vim-addon-manager at least, because his system does not install recommended as dependencies [15:22] siretart> Now there's my concern. If libmp4v2 isn't even in recommends (and ScottK says that it shouldn't be), then with the death of proper gtkpod-aac there will be no obvious way for multiverse users to actually get gtkpod with m4a support. [15:23] james_w: doing a hard dependency will break the vim policy, and I don't want that as well [15:23] Since "apt-get install gtkpod-aac" will not install libmp4v2. [15:23] LucidFox: I think we can safely assume that multiverse users have 'ubuntu-restricted-extras' installed [15:23] LucidFox: or kubuntu-restricted-extras [15:23] * LucidFox doesn't... [15:24] well, that is the documented and advertised method to get "that multimedia stuff" working [15:24] even so, it doesn't depend on libmp4v2 [15:24] well, change it then :-) [15:27] It's a highly specific library, and the recommends for ubuntu-restricted-extras are all generic [15:27] why are they recommends rather than depends in the first place, by the way? [15:27] "they"? [15:27] ubuntu-restricted-extras has no depends, only recommends [15:27] Recommends: gstreamer0.10-plugins-ugly, gstreamer0.10-plugins-ugly-multiverse, ttf-mscorefonts-installer, adobe-flashplugin | flashplugin-nonfree, unrar, gstreamer0.10-plugins-bad, gstreamer0.10-plugins-bad-multiverse, gstreamer0.10-ffmpeg, libavcodec-unstripped-52, gstreamer0.10-pitfdll [15:28] not sure, ask mvo. I assume thats common practice with meta-packages these days [15:29] I assume it's so you can opt out of individual ones without having to remove the overall metapackage [15:29] ah [15:30] I rather think it has to do with being able to install package that conflict with one or more packages from the list without resulting in having to deinstall the other packages [15:31] coffee.now [15:33] And why "adobe-flashplugin | flashplugin-nonfree"? adobe-flashplugin isn't in the archive, and flashplugin-nonfree is transitional to flashplugin-installer [15:34] is it for some kind of backward compatibility? [15:34] LucidFox: a-f is in partner [15:35] ah [15:35] iirc [15:35] but flashplugin-nonfree can be changed to flashplugin-installer? [15:35] looks like it [15:39] directhex: http://behindmotu.wordpress.com/2009/05/11/jo-shields-directhex/#comment-624 [15:47] Since I'm going to modify ubuntu-restricted-extras, can I add all ffmpeg unstripped libraries as suggested in bug #373963? [15:47] Launchpad bug 373963 in ubuntu-restricted-extras "ubuntu-restricted-extras should depend on libavformat-unstripped-52 libpostproc-unstripped-51 libswscale-unstripped-0 or conflicts with stripped versions of these packages" [Undecided,New] https://launchpad.net/bugs/373963 [15:48] right now all [kx]?ubuntu-restricted-extras have libavcodec-unstripped-52, but not the other libraries [15:50] LucidFox: yes, please fix it as you see fit === bluesmoke_ is now known as Amaranth === awe is now known as awe-afk === awe-afk is now known as awe [16:06] LucidFox: yes please. I'm surprised that this hasn't happened yet. [16:06] siretart> uploaded [16:06] thanks [16:06] added libmp4v2-0 to ubuntu-* and xubuntu-* too [16:07] did you add just libavcodec-unstripped-52 or also the other ones? [16:08] libavcodec-unstripped-52 was there already, I added the other ones [16:12] arg, sorry, I misread [16:13] the others are actually not necessary. until now nobody has raised any concerns about libavformat, so I don't strip that library (but in theory I could implement that) [16:13] for the other ones, I cannot imagine serious concerns, so the unstripped variant has functionally identically libraries [16:14] we do built them for convenience of the users: avformat depends on avcodec, and that on in turn pulls in postproc, avutil and avfilter [16:15] but anyway, it doesn't matter much [16:21] Apparently quite a few people have doubts about notify-osd... [16:29] does update-manager support upgrade from 7.10 to 8.04? 7.10 was moved to old-releases.u.c and I don't know if the update-manager that was shipped with it handles such a situation.. [16:30] 7.10->8.04 ought to be fine [16:32] what was the version of update-manager in 7.10? [16:32] (i'm actually going to check out if it supports this upgrade as this question is popping over and over again) [16:35] directhex: doesn't look like u-m from gutsy supports it.. at least grepping source for "old-releases" returns nothing.. [16:42] http://www.schwimmbadspiel.de/?refId=99828434 [16:42] http://www.schwimmbadspiel.de/?refId=99828434 [16:42] http://www.schwimmbadspiel.de/?refId=99828434 [16:42] http://www.schwimmbadspiel.de/?refId=99828434 [16:42] http://www.schwimmbadspiel.de/?refId=99828434 [16:42] http://www.schwimmbadspiel.de/?refId=99828434 [16:42] http://www.schwimmbadspiel.de/?refId=99828434 [16:42] http://www.schwimmbadspiel.de/?refId=99828434 [16:42] http://www.schwimmbadspiel.de/?refId=99828434 [16:42] http://www.schwimmbadspiel.de/?refId=99828434 [16:42] http://www.schwimmbadspiel.de/?refId=99828434 [16:42] http://www.schwimmbadspiel.de/?refId=99828434 [16:42] http://www.schwimmbadspiel.de/?refId=99828434 [16:42] http://www.schwimmbadspiel.de/?refId=99828434 [16:42] http://www.schwimmbadspiel.de/?refId=99828434 [16:44] super spam [16:52] what is option 'X-Ubuntu-Gettext-Domain' in .desktop files used for? [16:57] kklimonda: For packages in main we strip the translations out of the .desktop files and gnome-menus has a patch to load a translation from the .mo file [16:57] kklimonda: it uses that key to figure out where to get the translation [16:58] Amaranth: it doesn't apply to packages from universe? [16:58] kklimonda: it won't strip the translation but it'll still prefer the .mo file version if that key is set [16:59] i see.. thanks :) === dpm is now known as dpm-afk [17:17] dholbach: no problem on django-openid upload :) === mterry is now known as mterry_lunch [17:24] :-) [17:33] hmm.. there isn't anything like requestmerge tool - can you point me to some "perfect" merge request so I can copy it? :) [17:34] kklimonda> "Please merge packagename version from Debian unstable ({main|contrib|...})" [17:35] Add debian/changelog entries since the last Ubuntu version, attach your debdiff, and subscribe u-m-s or u-u-s [17:35] kklimonda: If you look at the requestsync output and change sync/merge and attach a debdiff from the Debian version you should be good. [17:36] ok, thanks :) [17:38] should I create debdiff from both previous ubuntu release and debian release? [17:39] kklimonda: Just the Debian one. Some people do the previous Ubuntu one, but I have no idea why. [17:39] ScottK: it is mentioned on merge wiki page [17:39] OK. Then that's a good reason to include it. [17:40] Honestly I've never looked at one when I was sponsoring. [17:40] I've diffed the debian dirs, but the upstream changes really aren't generally of interest. [17:41] DktrKranz: are you around ? [17:43] ScottK: that's why I'm asking - it sounds overzealous to me especially when a debdiff is over 12 megabytes ;) [17:44] I'd leave it out and explain why. [17:48] ScottK> Jonathan Thomas says in bug #374802 that quassel packages can be stripped now - is this correct? [17:48] Launchpad bug 374802 in quassel "Consider building versions of quassel and quassel-client without KDE dependencies" [Wishlist,Confirmed] https://launchpad.net/bugs/374802 [17:48] I specifically added force nostrip to the new debian/rules because it was in the old one === Igorot is now known as Knightlust [17:49] LucidFox: I think so. We generally use CDBS for KDE packages because of special rules for KDE in kde4.mk. [17:49] I'm kind of reluctant to abandon that. [17:49] Ah [17:49] A double build would be much more difficult to do with CDBS, though, if not outright impossible [17:50] * JontheEchidna seems to remember seeing another KDE package that did a double build... [17:50] kdiff3 I think [17:51] Yeah, it does a double build with CDBS, albeit not with kde4.mk [17:51] o_O [17:51] * LucidFox downloads [17:52] (this is new in the latest version in karmic synced from unstable, mind) [17:52] s/synced/merged [17:54] JontheEchidna: What's the one we're switching to in Karmic? [17:54] LucidFox: There's a newer helper in pkg-kde-tools that we'll want for Karmic in any case. [17:54] Specifically for double builds? [17:54] ah, wait [17:55] replacing kde4.mk [17:55] /usr/share/pkg-kde-tools/qt-kde-team/1/debian-qt-kde.mk is the drop-in replacement for kde4.mk [17:55] bug 375000 - how does it look? Damn, nice bug number ;) [17:55] actually, that needs pkg-kde-tools as a build-depend [17:55] Launchpad bug 375000 in transmission "Please merge transmission 1.60-2 from Debian unstable (main)" [Undecided,New] https://launchpad.net/bugs/375000 [17:55] It just includes kde4.mk, actually [17:56] The one in Karmic doesn't do that [17:56] ah [17:56] It probably did that for sync purposes in Jaunty [17:56] and come to think of it, it would make backporting easier too [17:57] JontheEchidna: That's exactly why i did it (sync/backporting). You do need to make sure you don't use any of the symbol file magic in Jaunty though as we don't support that. [17:58] Yeah, though I was pleasently surprised when strigi from Unstable built fine in Karmic :) [17:58] symbol files and all [17:58] Hmm.. Why is transmission's maintaner set to Ubuntu Core Developers when package is in universe? [17:59] IIRC it used to be in Main. [17:59] There's no automatic process for changing that when packages move between components. [17:59] should i change maintainer to MOTU or leave it be? [18:00] I'd change it. [18:00] Upon looking at the karmic debian-qt-kde.mk, none of that seems relevant to quassel. [18:01] Could be. No guarantee it would remain that way in the future. [18:02] I'd prefer to stick with it, but if it's not possible, then I think it's not essential. [18:05] cjwatson: looks like someone beat to me the punch for the aap sync bug; so moving on to console-common, it also looks like it's just a sync; do you mind if i go ahead report the bug? [18:06] s/go ahead report/go ahead and report/ [18:08] awe: no, I believe that Debian only just merged my keymap.sh patch [18:08] awe: check that el.po is either not empty any more or has been removed [18:09] awe: (see 0.7.80ubuntu1 changelog) [18:09] awe: I have zero interest in console-common any more since we no longer use it by default :) [18:10] cjwatson: OK [18:10] I'll get the hang of this one of these days. Sigh... [18:13] hi there [18:14] cjwatson: how come the old ubuntu patch file doesn't show that the empty po file was removed? I just see the changelog entry that say it was... [18:15] I'd like to know why I can make a deb with debuild, but not with pbuilder... the dependencies are not recognized by pbuilder [18:16] if a package is in Dependency wait status, when will it tried again to build? [18:17] https://launchpad.net/ubuntu/+source/mpg123/1.7.2-3ubuntu1/+build/985773 [18:17] https://edge.launchpad.net/ubuntu/+source/treecc What the heck? === mterry_lunch is now known as mterry [18:17] http://packages.qa.debian.org/t/treecc.html [18:18] heh [18:18] nice [18:18] cjwatson: also it looks like el.po is no longer empty in the new debian version, so looks like a sync request is correct [18:21]