[00:10] I hope this isn't a terrible place for a packaging question, but I've put ubuntu-mono icons into my package, but it's not regenerating the icon cache after installing, so they're not showing up. I've googled and found dh_icons, but I'm not sure how to invoke it [00:11] I've looked at other applications that include mono icons, and they don't seem to use it either, and I can't find any examples online. So, I'm wondering what do I need to add to my source package for this to work [00:14] zachtib: From memory that should be automatically handled by a file trigger. That memory might be faulty, though, if you find that it doesn't work :) [00:15] zachtib: why not depends on the ubuntu-mono package? [00:15] RAOF, no, I'm having to run update-icon-caches manually [00:20] I suppose I could add a postinst script to run update-icon-caches, no? [00:22] zachtib: if you're using icons from the package, you should just depend on the package (and thus getting the cache updating for free I believe) [00:22] micahg, I'm not, I'm adding a mono panel icon for my application [00:23] ah, ok [00:25] zachtib: You'd want to just call dh_icons to grab the automatic update-icon-caches fragment. [00:25] RAOF in my postinst script, then? [00:26] No, in debian/rules. It'll add the appropriate maintainerscript fragments itself [00:26] RAOF, when I added it there, I got an error (though I have an odd rules file, it's using pycontrol) === medberry is now known as med_out [05:20] tumbleweed: poke [05:20] tumbleweed: Brian just made a preliminary list with a script :) [05:21] I'm confirming that there are no false positives. [05:21] (this is for the ftbfts) [05:21] *ftbfs [07:01] good morning [08:28] nigelb: cool [08:29] tumbleweed: ah, I have one doubt. Hang on getting the log [08:31] tumbleweed: Is this a linking failure? https://launchpadlibrarian.net/72378541/buildlog_ubuntu-oneiric-i386.4store_1.1.3-1_FAILEDTOBUILD.txt.gz [08:33] nigelb: yes [08:33] The script needs tweaking :) [08:34] nigelb: both .a files in that linker call need to be moved before -lz -lraptor2 as they use symbols from those libs [08:35] at least lib4storage.a uses them [08:35] I can fix that when I get home :) [08:40] I submitted a patch to fix build failure linking change in redis, upstream tells me they have no problem building it. HOw do I reply to it? [08:42] http://code.google.com/p/redis/issues/detail?id=562 [08:42] Suggestions on a response welcome :) [08:45] nigelb: I'd explain that Ubuntu's linker is becoming more strict (point them to the wiki page / doko's e-mails), and tell them they can verify it by trying to build it on an Ubuntu Oneiric alpha [08:46] tumbleweed: Thanks, I'll do that :) [08:48] you can also point them to the old build log (the one with the FTBFS) [08:49] ah, yes [08:49] tumbleweed: is there a better link than https://lists.ubuntu.com/archives/ubuntu-devel/2011-March/032632.html [08:50] sladen: yes, that was the reversion of the changes, the original announcing e-mail or http://wiki.debian.org/ToolChain/DSOLinking [08:52] okay, so this is what I'm going with http://dpaste.com/553984/. Did I miss anything? [08:53] lgtm [08:56] geser, tumbleweed: Done thanks :) [08:57] sladen: Thank you for the extra comment :-) [10:57] Can I dput with dput from Debian to a ppa, or is that a Ubuntu specific patch? [11:00] Nevermind, added the four lines to my ~/.dput.cf [11:01] What version shall I choose for a ppa upload? The current version is 1.14.0~beta1-1 [11:02] it's generally sensable to append ~ppa1 [11:02] Would that be 1.14.0~beta1-1ppa1 then? [11:02] Then the help files are outdated. :) [11:02] https://help.launchpad.net/Packaging/PPA/BuildingASourcePackage [11:03] # [11:03] Ubuntu package myapp_1.0-1ubuntu3 → PPA package myapp_1.0-1ubuntu3ppa1 [11:03] I guess common sense just applies. Does one want to preced or supercede [11:03] You're right of course. [11:06] Rhonda, depends on where you want to place it - i.e. how it should supercede or be superceded by a distro package. and also depends on which version is the "base" version you're working from [11:06] Rhonda, i.e. if 1.14.0~beta1-1 is current, use ~ppa1 or +ppa1 depending on whether you want higher or lower [11:07] Now I wonder what to put into the changelog. Upload target would be oneiric, right? [11:14] yes, if you want to build it for oneiric [11:15] That's the idea, thanks. :) [11:16] How long would it take until it appears in my PPA? [11:17] And … I am a bit puzzled by the ppa dput config snippet. When one creates a PPA they give it a name, multiple PPAs can get created. [11:18] Though, there is no PPA name part in the upload path, only e.g. ~rhonda/ubuntu. [11:18] Now I wonder how that gets moved in the proper named PPAs from there? [11:19] "ubuntu" is the ppa name in that case afaik, or is this in your .cfg? [11:19] It's in the .cfg [11:19] Then I guess I should switch that. [11:20] ~arand/redeclipse/ubuntu is what i use e.g. [11:20] middle bit being the ppa name [11:20] doesn't the default dput.cfg contain a generic ppa snippet in Debian (or was it only patched in Ubuntu?)? [11:21] hah, that was it :) [11:21] you should get a e-mail soon (the uploads gets processed every 5min) [11:21] geser: Not in squeeze. [11:21] It does, but you need to change it to fit, ubutnu has a patch which allows passing your ppa name to dput as an argument, but that hasn't been upstreamed [11:21] Upload Warnings: [11:21] No copyright file found. [11:21] That's a false warning. [11:21] geser: the ppa: snippet can't be used on Debian until it supports SFTP (afaik) [11:22] There is debian/pgadmin3-data.copyright in the source. [11:23] This is what works for me with dput: http://paste.debian.net/119784/ [11:23] There is a build queue and a guesstimate of time if you check the "package details" and "all builds", I think it's called [11:23] "currently building" \o/ [11:25] Oh, so the /ubuntu at the end is superfluos, I didn't know that :) [11:26] Maybe not, it's still building :) [11:26] arand: IIRC you can do /ubuntu/$release [11:26] Right, hmm, that overrides what's defined in the changelog then? [11:27] yes, and is IIRC discouraged [11:27] Right, because it would encourage same versions [11:28] and would easily lead to confusion [11:33] Though there is an easy "copy packages" option for that [11:37] \o/ [11:37] https://launchpad.net/~rhonda/+archive/pgadmin3/+packages [11:37] arand: Wouldn't that add a changelog entry? [11:38] It does not seem to do no. [11:40] hi [11:40] Rhonda: why should "copy packages" add a changelog entry? it's still the same .debs that are just published in an other release too [11:41] geser: I would have hoped that it change the version accordingly, and for that adds a required changelog entry? [11:42] Otherwise a copy across the distributions somehow doesn't make sense to me. [11:44] Rhonda: it copies the packages as is; this works best for packages copied forward which don't need a rebuild (the same way untouched packages get carried over from one Ubuntu release to the next) [11:44] Ah, forward makes sense, yes. [11:45] on the other hand, this might still leave to unresolveable dependencies because of removed libraries and stuff [11:46] and in those cases you need to reupload a new version [11:46] but there are plenty of cases where that isn't so [11:47] I think I just go the path of uploading the source with different versions :) [12:03] hmm. successful builds are linked, failed builds not? [12:03] Now to I find out why/where it failed? [12:10] Rhonda: which build failed? in your pgadmin3 PPA I only see the "backports" in depwait: "Missing build dependencies: postgresql-server-dev-all (>= 117~)" [12:10] Rhonda: firstly, you should get an e-mail, second, expand the line on the +packages page to see the detaiuls. Or dig into "View all builds" [12:10] geser: Yep, that Build-Depends is the issue, I seem to have to pull it in from pitti's PPA or such, not sure. [12:11] you could make your PPA "depend" on pitti's PPA [12:11] or your add pitt's PPA as a dependency [12:11] If I would understand affairs better I would cancle the remaining pending builds. [12:11] you can't cancel [12:11] A building one not, but neither a pending one? [12:12] you can supercede it, that's about it [12:12] So how can I make the PPA depend on pitti's? And would that reschedule the builds? [12:12] (or poke a launchpad admin, if it's a massive build and will fail after 20 hours" [12:12] Ah, think I found it :) [12:12] you can't reschedule, but you can retry the failed builds [12:15] I'll check later. [12:22] Get:20 http://ppa.launchpad.net/pitti/postgresql/ubuntu/ lucid/main postgresql-server-dev-all 117~lucid [5482B] [12:22] Now that looks much much better. :D [12:23] geser, tumbleweed, thanks for the hint in the right direction. :) [12:49] I'm trying to update the libtorrent package, 0.12.6 to 0.12.8, but I get this weird error all the time [12:49] chmod: cannot access `/tmp/buildd/libtorrent-0.12.8/build-tree/libtorrent-0.12.8/configure': No such file or directory [12:49] make: *** [debian/stamp-autotools] Error 1 [12:49] when trying to pbuild the sourcepackage (.dsc) [12:50] I apt-get source libtorrent [12:50] wget the new source and extract it [12:50] then I copy the old debian dir to the new source dir [12:50] and dch -i [12:50] then debuild -S -sa [12:50] I must be missing something here [12:50] any pointers? [12:51] is the mentioned file there? [12:52] geser, nope, the tmp dir is just there during the build I guess [12:52] however, there's a configure file in the source dir [12:53] is that from pbuilder? you can add a hook to drop you into a shell when the build fails [12:53] geser, yes it is [12:53] oh really, how? how's that going to help me? =) [12:54] so I can checkout files and stuff? [12:54] pbuilder destroys the chroot when it exits, when you get dropped into a shell you can investigate why it failed before everything gets removed [12:54] ah [12:54] the thing is I don't know what to look for anyway === Quintasan_ is now known as Quintasan === makl is now known as ximion === makl is now known as ximion === med_out is now known as medberry === ximion1 is now known as ximion === Tonio_ is now known as Tonio_aw [15:30] is there a release manager around who can approve the series tasks for bug #675108 please? it's a natty regression with a proposed patch that I've worked into a bzr branch and tested... going to forward port it to oneiric next, but the SRU will need the natty task. [15:30] Launchpad bug 675108 in gnome-power-manager (Ubuntu) "gnome-power-manager adds battery to indicator twice when battery hot-unplugged and plugged back in" [Medium,In progress] https://launchpad.net/bugs/675108 === zul_ is now known as zul [16:26] psusi: someone from #ubuntu-desktop should be able to accept the nominations too === Tonio_aw is now known as Tonio_ === hannesw_ is now known as hannesw === lionel__ is now known as lionel === Tonio_ is now known as Tonio_aw [17:48] cjwatson: libdkim on had half of your patch applied, do you want me to reupload the other half or wait until Debian does it? [17:48] *only [17:52] micahg: I reopened the Debian bug [17:53] I think we can probably just leave it until then TBH - I was only in a rush because it was on the OpenSSL transition list [17:53] * micahg thought you already rebuilt it for the transition [18:03] I want to become a motu. Specifically I want to fix the packages I maintain or use that are broken in oneiric === Tonio_aw is now known as Tonio_ [18:07] sinzui: awesome, so, the best way to start is to propose fixes for your packages for sponsoring [18:08] michag. I need to ensure the bug in reported against the package in oneiric and subscribe the sponsor team? [18:15] sinzui: no need to target the bug, yeah, just add a patch and subscribe ubuntu-sponsors or propose a branch for merge into lp:ubuntu/foo [18:51] micahg: the fix was after my rebuild attempt [18:52] micahg: and since it's now been transitioned, I'm not in a desperate hurry to fix the reappearing failure [18:52] happy to wait for Debian + autosync [18:58] cjwatson: ah, ok, thanks === Tonio_ is now known as Tonio_aw === Tonio_aw is now known as Tonio_ === medberry is now known as med_out === Tonio_ is now known as Tonio_aw === Tonio_aw is now known as Tonio_ === yofel_ is now known as yofel === Tonio_ is now known as Tonio_aw === med_out is now known as medberry === Tonio_aw is now known as Tonio_ === Quintasan_ is now known as Quintasan