[00:11] <stilia-johny_> hi
[00:11] <stilia-johny_>  in synaptic we can see a screenshot of package! how can i add a screenshot IN my source???
[00:11] <stilia-johny_>  and when i upload it on ppa and go to synaptic search my app view the screenshot!
[00:11] <stilia-johny_> * stilia-johny_ ?
[00:11]  * stilia-johny_ ?
[00:17]  * stilia-johny_ any?
[00:21] <RAOF> stilia-johny_: IIUC those screenshots come from screenshot.debian.org
[00:21] <ulysses> stilia-johny_: AFAIK those screenshots come from Debian, see http://screenshots.debian.net/
[00:22] <ulysses> ^^
[00:23] <stilia-johny_> and how can i add my screenshot for my app?
[00:24] <stilia-johny_> and how can i add my application there??
[00:27]  * stilia-johny_ ?
[06:01] <cdbs> bdrung: I was just added to pkg-miltimedia
[06:02] <cdbs> I know what to do from now onwards. Thanks!
[06:10] <cdbs> bdrung: BTW, what packages come under 'audacious packages'? I think only audacious and audacious-plugins
[06:12] <fabrice_sp> micahg, fyi, I commented on dolphin-emu package
[06:12] <fabrice_sp> (in REVU)
[06:14] <micahg> fabrice_sp: cool, thanks
[06:15] <fabrice_sp> yw ;-) I was going to have a look at packaging it myself, so better have a look at an existing one :-)
[06:16]  * micahg needs to become an Admin on REVU
[06:16] <fabrice_sp> Admin?!
[06:16]  * fabrice_sp is just a reviewer :-)
[06:24] <micahg> fabrice_sp: I thought you didn't need .install and .dirs if there was only one binary package
[06:28] <fabrice_sp> micahg, in this case, he is doing cp in the rules file
[06:29] <fabrice_sp> and also a mkdir, so better to use dirs and .install files IMHO
[06:30] <micahg> fabrice_sp: and just add debian/tmp/*?
[06:31] <fabrice_sp> if that would have been the case, you would have been right, but xpm in the not installed by upstream and manually copied
[06:31] <micahg> fabrice_sp: why not just patch the upstream code to install it?
[06:32] <fabrice_sp> less intrusive?
[06:32] <fabrice_sp> it's also a posiblity
[06:32] <fabrice_sp> anyway, desktop file is not upstream
[06:32] <fabrice_sp> so it has to be installed manually
[06:33] <micahg> fabrice_sp: well, depending on how many lines you need to add to .install, it might be easier, also, there's no dh helper for .desktop files?
[06:33] <fabrice_sp> not anymore
[06:33] <fabrice_sp> dh_desktop got deprecated some versions ago
[06:34] <fabrice_sp> anyway, you're free to comment and disagree with me in REVU :-)
[06:34] <micahg> fabrice_sp: not at all, just trying to learn :)
[06:35]  * micahg hasn't made anything from scratch yet
[06:35] <fabrice_sp> you already know a lot! :-)
[06:35] <fabrice_sp> ohh: it's harder than you think
[06:35] <fabrice_sp> espcially if copyright is crazy
[06:36] <fabrice_sp> (here, it seems to be a nightmare, with a lot of 'external' software)
[06:39] <micahg> fabrice_sp: doesn't external software have to be packaged separately?
[06:42] <fabrice_sp> yep
[06:43] <fabrice_sp> and in this case, a lot is already in Ubuntu
[06:43] <fabrice_sp> so my guess is that it will take time to have dolphin in Ubuntu
[06:43] <fabrice_sp> (package required software and then desactivate the bulding of those modules in Dolphin)
[06:44] <cdbs> Hello there fabrice_sp !
[06:45] <fabrice_sp> cdbs?
[06:45] <cdbs> fabrice_sp: I am bilal akhtar
[06:45] <fabrice_sp> ohhhh
[06:45] <fabrice_sp> for a moment, I thought you would argue about me recommending dh7 in revu :-)
[06:46] <fabrice_sp> you will have a lot of false highlights!
[06:46] <cdbs> no, I myself prefer dh7
[06:46] <cdbs> fabrice_sp: I know, many of the in #ubuntu-devel when someone asks : Do you use cdbs for package foo?
[06:47] <cdbs> I had the hilight installed since before I changed my nick, just for a test
[06:47] <fabrice_sp> :-)
[06:47] <cdbs> *highlight
[06:47] <cdbs> g2g
[06:49] <fabrice_sp> breakfast time :-)
[07:55] <dholbach> good morning!
[08:53] <cdbs> bdrung: came back?
[09:35] <bdrung> now i am here
[09:43] <tumbleweed> bdrung: landed pbuilder-dist changes, I'm happy with them.
[09:52] <bdrung> tumbleweed: great, i will look at it tonight
[10:04] <shadeslayer> how do you deal with old packages with new names?
[10:04] <shadeslayer> do you retain the changelog ? ...
[10:05]  * shadeslayer looks at Debian Wiki
[10:14] <soren> shadeslayer: That's what I'd do, yes.
[10:15] <geser> shadeslayer: the renamed packages that I looked at till now kept the changelog entries for the old source package name (it's also part of the history of this package and it makes it easier to see when a source package got renamed)
[10:16] <shadeslayer> geser: so 1) make a dummy package for natty with all the history , 2) keep previous history for new package
[10:16] <shadeslayer> debian wiki doesnt say anything about changelog histories tho...
[10:17] <geser> shadeslayer: why dummy package?
[10:17] <geser> what exactly do you want to rename?
[10:18] <shadeslayer> because debian wiki says i need to create a dummy package to transition from the old on
[10:18] <shadeslayer> http://wiki.debian.org/Renaming_a_Package
[10:18] <geser> ah, that's for transitioning binary package renames
[10:18] <shadeslayer> Kubuntu-konqueror-shortcuts -> kubuntu-web-shortcuts
[10:18] <shadeslayer> so i just replace and conflict the old package?
[10:20] <geser> yes, I'm not sure if Breaks is needed too, not up-to-date on this part of policy
[10:21] <geser> shadeslayer: for renaming the source package: just replace all occurances of the old name with the new name and add a new changelog entry for the new source package name too the existing debian/changelog (perhaps also mentioning the rename in the changelog entry)
[10:23] <shadeslayer> ok :)
[12:02] <kklimonda1> dholbach: hmm, what's wrong with gtkmm?
[12:03] <kklimonda1> dholbach: the update is to 2.22.0 and not to 2.20.3
[12:03] <dholbach> kklimonda1, oops
[12:03] <dholbach> kklimonda1, I'll have a look at it when I'm back from lunch
[12:03] <kklimonda1> sure, no problem
[12:03] <dholbach> kklimonda1, can you mark it as 'needs review' again?
[12:04] <kklimonda1> dholbach: just so you know it won't build right now - I've requested this mege for Sebastien to keep track of it because he has to sponsor atkmm1.6 upload first.
[12:04] <kklimonda1> dholbach: will do
[12:04] <dholbach> if seb didn't get to it before I do, I'll have a look at atkmm too
[12:05] <dholbach> to repent for my sin of rejecting your merge proposal
[12:05] <dholbach> see you later :)
[12:13] <KNRO> Hello, quick question: can you build Lucid packages using pbuilder while I'm using Maverick?
[12:13] <popey> KNRO: yes
[12:14] <KNRO> popey: pbuilder will figure this out itself from the changefile or I have to manually rebuild the base package?
[12:14] <popey> hmm, I do pbuilder-dist and specify the release
[12:15] <popey> pbuilder-dist lucid create
[12:15] <popey> pbuilder-dist lucid build foo.dsc
[12:18] <KNRO> don't have pbuilder-dist , can I use pbuilder --distrbution lucid instead?
[12:18] <popey> pass
[12:18] <KNRO> ok downloading now ubuntu-dev-tools
[12:19] <popey> sorry, I'm not a motu, just a pretender
[12:37] <directhex> KNRO: pbuilder-dist makes it easy... i basically emulate pbuilder-dist using environment variables
[13:39] <dholbach> kklimonda1, do you have a url for the atkmm one?
[13:45] <kklimonda1> dholbach: bug 672817
[13:46] <kklimonda1> dholbach: there is a revu bug in the link
[13:47] <kklimonda1> dholbach: there is still one bug in atkmm packaging -- I was sick for few days and haven't uploaded the right package to revu apparently.. I though I did.
[14:29] <dholbach> kklimonda, but you're better again now?
[14:29] <dholbach> kklimonda, my only hesitation about atkmm packaging would be the new debhelper version - if you don't use it for a specific reason (I didn't find out), I'd probably use a lower version, so you can still do backports
[14:30] <kklimonda> dholbach: well, I'm well enough to use computer :)
[14:30] <kklimonda> dholbach: downgrade it to 7 then?
[14:30] <dholbach> that's at least something :)
[14:31] <dholbach> if you don't need debhelper8 for something specific I think that'd be reasonable
[14:32] <kklimonda> no, I don't think I use anything specific to 8
[14:38] <dholbach> kklimonda, gtkmm misses a build-depends on libatkmm-1.6-dev
[14:39] <dholbach> and gtkmm ftbfs
[14:39] <kklimonda> dholbach: it doesn't miss a dependency.. no wait, it does.. wth?
[14:40] <kklimonda> i have it right here..
[14:40] <dholbach> kklimonda, BUILD-depends
[14:40] <dholbach> I just commented on the merge proposal
[14:40] <kklimonda> dholbach: yes, I see.. but it's here.. I have two branches - one for packaging only and another for the whole package :/
[14:42] <dholbach> hang on
[14:42] <dholbach> http://bazaar.launchpad.net/~kklimonda/gtkmm/packaging/annotate/head%3A/debian/control.in
[14:42] <dholbach> search for 'libatkmm-1.6-dev'
[14:42] <dholbach> kklimonda, ^
[14:42] <kklimonda> dholbach: yes, I can see it
[14:43] <dholbach> am I blind?
[14:43] <dholbach> :)
[14:43] <nigelb> heh
[14:43] <dholbach> I still can't see it there
[14:43] <kklimonda> dholbach: no, I see it in my local branch :)
[14:43] <dholbach> ahhhhhhhhhhhhhhhhhhhhhhh
[14:43] <dholbach> well
[14:43] <kklimonda> and I can see that it's missing from the branch that I pushed
[14:43] <dholbach> if I could see it in your local branch you'd have a problem :)
[14:43]  * dholbach hugs kklimonda
[14:44] <dholbach> and gtkmm ftbfs for me, I added the log snippet to the merge proposal
[14:45] <kklimonda> yes, I can see that.. that's weird
[14:46] <dholbach> maybe seb128 has an idea?
[14:48] <kklimonda> I'll ask him and see if I can make it fail here. I did build it, you know? ;)
[14:49] <kklimonda> I did it a week ago, maybe something changed in natty since then?
[14:50] <dholbach> kklimonda, I believe you - don't worry :)
[14:50] <dholbach> yeah, things are pretty much in flux right now
[14:52] <kklimonda> I don't really worry, I'm just a bit surprised :)
[15:00] <kklimonda> dholbach: hmm, it doesn't fail in my pbuilder..
[15:00] <kklimonda> dholbach: I login into pbuilder chroot, install all build-deps, atkmm debs and run debuild
[15:01] <kklimonda> I've pushed it to PPA and see if I can reproduce failure there
[15:02] <dholbach> kklimonda, thanks!
[15:16] <jetienne> offtopic: when upgrading from one release to the next, this is downloading in 5min here. but then i got 2h of disk+cpu before it is completed. can someone explain to me how come this is so long ?
[15:26] <directhex> probably more of apt's fsync() stuff slowing it down
[15:31] <jetienne> i was thinking that all is install in sequence... this is likely quite suboptimal too
[16:14] <AJenbo> Hi, i made a ppa, and build a package on my local machine, but after uploading about a week ago the package still dosn't appear in my ppa
[16:14] <AJenbo> What might i be doing wrong?
[16:16] <ari-tczew> AJenbo: did you receive a confirmation e-mail?
[16:16] <AJenbo> dput ppa:ajenbo/id-game-ports ../ioquake3_1.36_i386.changes
[16:16] <AJenbo> ari-tczew, no
[16:17] <AJenbo> it uploades the compressed source and changes, but after that nothing happens
[16:17] <ari-tczew> AJenbo: you should receive an e-mail about accept or reject
[16:17] <AJenbo> hmm
[16:17] <ari-tczew> AJenbo: did you try to upload again?
[16:18] <AJenbo> yes, i also uploaeded from my 64bit machine
[16:19] <AJenbo> If i try again i get
[16:19] <AJenbo> ppa:ajenbo/id-game-ports
[16:19] <AJenbo> Package has already been uploaded to ppa on ppa.launchpad.net
[16:19] <AJenbo> Nothing more to do for ../ioquake_1.36_i386.changes
[16:20] <AJenbo> https://launchpad.net/~ajenbo/+archive/id-game-ports
[16:22] <ari-tczew> AJenbo: delete file *upload
[16:24] <AJenbo> http://ubuntu.pastebin.com/exYnbyWK
[16:26] <SpamapS> AJenbo: is the GPG key you used to sign the package attached to your launchpad account?
[16:26] <AJenbo> yes
[16:26] <SpamapS> AJenbo: also you can only upload source packages
[16:26] <SpamapS> AJenbo: you should have gotten a rejection email telling you that
[16:30] <AJenbo> SpamapS, isn't what i have a source package?
[16:30] <AJenbo> it contains all the source code
[16:31] <ari-tczew> AJenbo: you should receive a confirmation email. please go on #launchpad and ask there.
[16:31] <AJenbo> I did not get any mails from the system
[16:31] <AJenbo> ari-tczew, ok thanks
[16:31] <jetienne> if i kill metacity, is it relaunch automatically ?
[16:32] <jetienne> arg bad channel sorry
[16:53] <SpamapS> Aj
[16:54] <SpamapS> sorry
[16:54] <SpamapS> AJenbo: that also included the binary package though
[16:54] <SpamapS> AJenbo: use 'debuild -S' to produce a source-only changes file
[17:05] <AJenbo> SpamapS, thanks
[22:06] <bdrung> tumbleweed: around?
[22:18] <bdrung> tumbleweed: i searched for remaining bugs for pbuilder-dist and found bug #371221