[00:02] <carstenh> doctormo: edit-patch looks fine if you want to change an existing package, for new ones I would suggest a different approach. dpkg has two (non-native) source format versions: "1.0" and "3.0 (quilt)". if you use the former you have to take care of all the patching yourself with the help of your favorite tool, if you use 3.0 (quilt) you just change the source and build the package, dpkg takes care of creating the patch, placing it under ...
[00:02] <carstenh> ... debian/pachtes/patchname and adds the patchname to the file debian/patches/series
[00:02] <Quintasan> shadeslayer: I think apachelogger might know something
[00:02] <shadeslayer> hmm
[00:02] <simar> I successfully created my the first debdiff..
[00:02] <simar> All credit to shadeslayer and geser ..
[00:02] <shadeslayer> simar: hand it over to Quintasan or geser :P
[00:02] <shadeslayer> simar: all credit goes to you!
[00:03] <carstenh> doctormo: you could also just copy a patch file to debian/pachtes and add the name to debian/patches/series by hand
[00:03] <shadeslayer> brrr.. huge build log
[00:03] <simar> shadeslayer: thanks . :))
[00:03] <Quintasan> simar: yeah, give it to me, maybe I'll learn sponsoring once for all
[00:03] <shadeslayer> i think ill break pastebin.com
[00:03] <shadeslayer> Quintasan: http://pastebin.com/7S65Vtwe
[00:04] <doctormo> carstenh: So quilt would do allt he work without much effort? Because I've edited source code before and it just errors out.
[00:04] <carstenh> doctormo: if you prefer 1.0 you need to change the simple rule file from "... dh $@" to "... dh $@ --with quilt"
[00:04] <shadeslayer> Quintasan: line 6816 onwards
[00:04] <carstenh> doctormo: the only difference is that now the patching is done whilst building instead of whilst unpacking
[00:04] <shadeslayer> :P
[00:05] <Quintasan> wut?
[00:05] <Quintasan> well, not that long
[00:05] <shadeslayer> Quintasan: thats the build log of digikam,the missing hook lists the missing files...
[00:05] <Quintasan> shadeslayer: Qt build was 25k+ lines
[00:05] <shadeslayer> so,tell me if i need to adjust those .mo files
[00:05] <carstenh> doctormo: yes, quilt does everything you need. you dont even need the quilt command if you know where to place the patches and don't forget to add the name to the series file
[00:05] <shadeslayer> Quintasan: :D
[00:06] <shadeslayer> i dont think we need to install those
[00:06] <shadeslayer> im about 75 pc sure that those files are not to be installed
[00:06] <Quintasan> shadeslayer: why don't youc check  with current package?
[00:06] <cjwatson> doctormo: if I were you I would simply document the 3.0 (quilt) format.  there's docs on the debian wiki which I would link to were I not typing on my phone.
[00:06] <shadeslayer> Quintasan: that is the current packaging with just a rules modification
[00:07] <simar> Quintasan: How to send you the file :)
[00:07] <Quintasan> and ir results with tons of *.mo files?
[00:07] <Quintasan> it*
[00:07] <shadeslayer> Quintasan: aye
[00:07] <cjwatson> doctormo: it's the direction things are going, and it means you don't have to mess around with applying and unapplying patches at build time.
[00:08] <shadeslayer> Quintasan: i havent changed anything except add a condition to copy one file,which was causing a FTBFS"
[00:08] <doctormo> cjwatson: Sounds like what I should be doing, is 3.0 tied in already to dh_make?
[00:08] <cjwatson> doctormo: you just leave the patches in the applied state when building the package.
[00:08] <shadeslayer> s/anything/a thing
[00:08] <carstenh> doctormo: you need to know which patches are applied in which case. if you unpack a 1.0 source all patches are unapplied. if you change an unapplied source tree and save the result as patch it would not apply correctly to the patched source. this could be the problem you had.
[00:08] <cjwatson> I don't know.  see comment about phone
[00:08] <Quintasan> shadeslayer: well, digikam in lucid has no *.mo files
[00:08] <cjwatson> check whether it creates debian/source/format and if so what it says.  read dpkg-source(1).
[00:09] <shadeslayer> Quintasan: packaging has no mo files or no mo files generated?
[00:09] <Quintasan> shadeslayer: packaging
[00:09] <shadeslayer> Quintasan: well.. dont need them then
[00:10] <Quintasan> simar: send it over to quintasan@kubuntu.org
[00:10] <shadeslayer> Quintasan: No primary archive build -> not cleaning l10n content. << apachelogger's magic :D
[00:10] <Quintasan> hey
[00:10] <Quintasan> digikam is in main
[00:10]  * Quintasan is only a MOTU
[00:10] <shadeslayer> \o/
[00:11] <shadeslayer> Quintasan: ok.. dont worry :P
[00:11] <Quintasan> though give me the debdiff
[00:11] <shadeslayer> Quintasan: sure :D
[00:12] <carstenh> doctormo: concentrating on the 3.0 (quilt) and adding a pointer to the man page would probably really be the simplest way for your documentation. mentioning edit-patch if one needs to change existing patches would also a good thing.
[00:12] <shadeslayer> omg..
[00:12] <simar> Quintasan: thanks, I'm mailing you debdiff.
[00:12] <shadeslayer> my mod doesnt come up in debdiff :S
[00:12] <carstenh> doctormo: when using 3.0 (quilt) people also don't need to know the details, it should just work
[00:13] <shadeslayer> Quintasan: http://pastebin.com/MX87AgzF
[00:13] <shadeslayer> which is totally wrong
[00:15] <carstenh> doctormo: dh_make creates 3.0 (quilt) per default since IIRC about last fall
[00:15] <Quintasan> god damn, that stupid kadu patch won't apply
[00:15] <Quintasan> what the hell I'm doung wrong
[00:15] <shadeslayer> Quintasan: pastebin patch
[00:16] <cjwatson> 3.0 (quilt) is at about 25% adoption in unstable at the moment, still rising fairly linearly
[00:16] <shadeslayer> Quintasan: how about i make a packaging frontend :D
[00:16] <shadeslayer> Quintasan: with Qt
[00:16] <Quintasan> shadeslayer: let me figure it out by myselt :P
[00:16] <shadeslayer> Quintasan: hehe :D
[00:17] <Quintasan> #ubuntu.pl
[00:17] <Quintasan> grr
[00:17] <cjwatson> http://upsilon.cc/~zack/stuff/dpkg-v3/
[00:18] <shadeslayer> btw any idea when harvest will be up again?
[00:22] <shadeslayer> Quintasan: ScottK digikam debdiff http://pastebin.com/BHrXeiZF
[00:28] <shadeslayer> ScottK: would be better if you can wget from http://people.ubuntu.com/~rohangarg/Patches/digikam.debdiff
[00:30] <Quintasan> shadeslayer: wait, members get space at people.ubuntu? :DD
[00:30] <shadeslayer> Quintasan: yeah...
[00:30] <shadeslayer> Quintasan: didnt you know?
[00:30] <Quintasan> nope :O
[00:30] <shadeslayer> Quintasan: they do :D
[00:31] <shadeslayer> Quintasan: what did you think?
[00:31] <shadeslayer> heh.. i cant open that link :P
[00:31] <Quintasan> nothing, I didn't know about that :P
[00:32] <shadeslayer> lawl
[00:32] <shadeslayer> Quintasan: https://wiki.ubuntu.com/PeopleUbuntuCom
[00:32] <Quintasan> well
[00:32] <Quintasan> Kadu deb diff is broken
[00:35] <shadeslayer> Quintasan: http://people.ubuntu.com/~rohangarg/Patches/digikam.debdiff
[00:35] <shadeslayer> can you access that?
[00:35] <meoblast001> hi, not sure if this is the right place to ask.... but it seems appropriate.... does the Bullet Physics library have anything that Ubuntu considers nonfree, as I had trouble finding it in repositories
[00:36] <Quintasan> shadeslayer: yes
[00:36] <shadeslayer> kool
[00:36] <Quintasan> well I'm off
[00:36] <Quintasan> good night
[00:37] <shadeslayer> Quintasan: wait
[00:37] <shadeslayer> Quintasan: explain http://pastebin.com/gGenHDss
[00:37] <shadeslayer> before you go
[00:37] <shadeslayer> seems he is gone :P
[00:38] <shadeslayer> im off to sleep too ... :D
[00:39] <micahg> siretart: do you mind if I merge gxine?
[01:33] <MTecknology> so... I've been having fun with packaging lately but a lot of files that get installed keep changing nd moving around. How can I deal with files that need to be removed/added/changed from the package?
[01:34] <MTecknology> actually I think I'm done aside from screwing up once - it'd just be niceto learn about for the future
[01:35] <micahg> MTecknology: http://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces ?
[01:36] <MTecknology> micahg: I'm not trying to overwrite other files - just trying to cleanly update files this package installs - or is it the same?
[01:37] <micahg> MTecknology: oh, do you have a .install?
[01:37] <MTecknology> micahg: ya
[01:38] <micahg> MTecknology: well, that's the list of files to be installed, right?
[01:38] <MTecknology> ya, one is an entire directory
[01:43] <MTecknology> micahg: how can I control what files need to be added/removed/changed?
[01:44] <micahg> MTecknology: well, is there only 1 binary?
[01:44] <MTecknology> ya
[01:44] <MTecknology> err - I guess it produces a -dbg too
[01:44] <micahg> MTecknology: then I don't think you even need a .install file if make install puts everything in the right place
[01:44] <MTecknology> it doesn't
[01:45] <micahg> MTecknology: oh, that's an issue then
[01:45] <micahg> MTecknology: is there a problem modifying the .install?
[01:45] <MTecknology> no - I just don't know what to put in there to make it do what I want
[01:45] <MTecknology> lemme paste my .install
[01:46] <micahg> MTecknology: is this for the archvie?
[01:47] <MTecknology> no- I'll wind up writing a blog post about my changes to the package but I fear if people blindly grabbed it they'd get very confused
[01:47] <micahg> MTecknology: I was just going to suggest moving to -packaging then
[01:48] <MTecknology> micahg: should I move there? I forgot that channel existed
[01:48] <micahg> MTecknology: yeah, that's for PPA/non-archive packaging help
[01:51] <siretart> micahg: not at all, please go ahead!
[01:51] <micahg> siretart: great, thanks, since it's a xul rdepend I requested it be added to my package set
[02:25] <doctormo> Very early alpha of this debian packaging guide: http://divajutta.com/doctormo/foo/debian-packaging.tar.gz your humble review would be most welcome.
[04:09] <siretart> do sftp uploads need to be gpg signed as well?
[04:14] <james_w> siretart: yes
[04:17] <EzraR> persia: are you around?
[04:28] <siretart> hm. then I wonder what's the advantage of using sftp over ftp?
[04:28] <micahg> siretart: FW issues?
[04:29] <micahg> siretart: sorry, firewall
[04:29] <james_w> there's not a great deal for most people. sftp can be more reliable, and for some people want it for private archives.
[04:31] <siretart> oh, I see
[04:54] <EzraR> what should I do about header files that are autogenerated concerning copyright?
[06:04] <EzraR> anyone willing to review a package of mine on REVU? The package is mangler, a ventrillo client for linux. It would make a great addition for gamers in Ubuntu. It has one advocate already and should be in good shape!http://revu.ubuntuwire.com/p/mangler
[07:39] <dholbach> good morning
[08:14] <geser> good morning
[08:15] <geser> shadeslayer: re "[-e": there is a space missing between the [ and the -e
[09:26] <dupondje> https://bugs.launchpad.net/ubuntu/+source/aegir-provision/+bug/543662
[09:26] <dupondje> can somebody upload it in lucid ? don't have permissions for it
[09:42] <geser> dupondje: 3 minor corrections: version 0.3-2ubuntu0.1 for the SRU, target: lucid-proposed, urgency=low (Ubuntu doesn't use it, so no benefit for setting it to something other)
[09:42] <geser> and 4th: LP: #bugnumber instead of Closes: ; the former is for Ubuntu/LP and the later only for Debian BTS
[09:45] <dupondje> posted (http://launchpadlibrarian.net/52022432/lucid.debdiff)
[09:47] <geser> looks good now
[09:48] <geser> dupondje: just noticed that you forgot to call "update-maintainer" (no need to update the debdiff just for that, but remember it for the next time)
[09:49] <dupondje> and remove the non-maintainer upload change in changelog also ? :p
[09:49] <geser> yes, already did that
[09:50] <geser> I don't mind doing small corrections when sponsoring but I still notify the sponsoree about it for the next time
[09:50] <dupondje> yea ofc :) learning every day :)
[09:50] <dupondje> why naming it ubuntu0.1 btw ?
[09:50] <dupondje> default sru naming?
[09:51] <geser> yes
[09:52] <geser> that way the version is smaller than the one in the development series even if it only has "ubuntu1"
[09:52] <Quintasan> argh, damn you dput
[09:53] <geser> ?
[09:54] <Quintasan> nothing, almost tried uploading to lucid
[09:55] <geser> it would get rejected
[09:55] <geser> I managed to upload through ppa.launchpad.com into the main archive :/
[09:55] <Quintasan> geser: :O
[09:56] <Quintasan> shadeslayer: well, open-invaders changelog still points to lucid, and I get some files that are not installed but they are in install files, beats me why, they install fine though
[09:58] <geser> dupondje: sponsored
[09:58] <Quintasan> shadeslayer: besides, shouldn't this header be added as a patch to source, not modified manually?
[10:02] <dupondje> geser: thx !
[10:03] <Quintasan> geser: did ari-tczew ask you to review kadu merge?
[10:03] <geser> no
[10:04] <Quintasan> mhm, okay
[11:43] <shadeslayer> Quintasan: what where who?
[11:43] <shadeslayer> i dont get you :S
[12:14] <jibel> porthose, Hi, could you please check your patch for bug 578137 . It introduces a regression in -proposed. Thanks.
[12:34] <apachelogger> shadeslayer: about mo files....
[12:34] <shadeslayer> ah
[12:34] <shadeslayer> right
[12:34] <apachelogger> shadeslayer: generally stuff in main must provide pot&po for import into launchpad from where the l10n content will then be exported to the ubuntu langpacks
[12:35] <apachelogger> in cosequence the langpacks ought to be the only packages to provide .mo files
[12:35] <shadeslayer> apachelogger: ok,but what are mo files?
[12:35] <apachelogger> which is not always the case, but in general
[12:35] <apachelogger> shadeslayer: compiled po files
[12:35] <apachelogger> the actual translations
[12:35] <shadeslayer> ok
[12:35] <apachelogger> should a package still try to install mo files they ought to be generally stripped automatically (unless overriden that is)
[12:36] <shadeslayer> k
[12:36] <shadeslayer> so do not install .mo files ( in general )
[12:36] <apachelogger> universe packages must generally ship mo files themselfs (universe does not get imported into launchpad, although at last UDS it was discussed to have that optional, for e.g. xubuntu which lives in universe AFAIK)
[12:37] <apachelogger> shadeslayer: you do not have to worry
[12:37] <apachelogger> for digikam they still get installed, but ubuntu package building magic will strip them from the package
[12:37] <shadeslayer> ok
[12:37] <apachelogger> shadeslayer: digikam debdiff looks fine btw ... I hope you tested it ;)
[12:37]  * apachelogger leaves again for lunch
[12:38] <shadeslayer> apachelogger: also,remember when i told you that akonadi takes up alot of bandwidth? its just caching stuff
[12:38] <shadeslayer> apachelogger: did you upload?
[12:38] <shadeslayer> apachelogger: and yes i tested it
[12:50] <apachelogger> shadeslayer: the caching takes up the badnwith? Oo
[12:50] <shadeslayer> apachelogger: yeah,it caches stuff from you imap/twitter/identi.ca account
[12:51] <shadeslayer> apachelogger: thats what i was told :P
[12:51] <apachelogger> yes, I know that
[12:51] <apachelogger> but where is the problem with that?
[12:51] <porthose> jibel, damn, ok will look at it this afternoon :(
[12:52] <shadeslayer> apachelogger: the problem was i didnt know ;)
[12:53] <apachelogger> oh
[12:53] <apachelogger> shadeslayer: well what did you expect it to do considering it is a PIM data *storage* service :P
[12:53] <shadeslayer> apachelogger: btw in kubuntu,the default browser is still konqueror under Settings > Default apps
[12:53] <apachelogger> in a new install?
[12:54] <shadeslayer> yes
[12:54] <shadeslayer> latest ISO
[12:54] <jibel> porthose, thanks
[12:54] <shadeslayer> apachelogger: i poked kubuntu-default-settings,but couldnt find anything there
[12:54] <shadeslayer> apachelogger: so effectively when you click on a link,it still loads up konqueror
[12:55] <apachelogger> yes it is not configured in kds
[12:55] <apachelogger> feel free too fix
[12:55]  * apachelogger will feel free to revert to konqueror if rekonq doesnt stop crashing :P
[12:55] <shadeslayer> apachelogger: ok
[12:55] <shadeslayer> :P
[12:57] <apachelogger> oh dear oh dear, the ui of TOra is sort of horrible
[13:01] <shadeslayer> apachelogger: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/430013
[13:01] <shadeslayer> :P
[13:01] <shadeslayer> also.. wrong use of opinion
[13:01] <ScottK> shadeslayer: There is no right use of opinion.
[13:01] <shadeslayer> haha
[13:02] <apachelogger> lol
[13:02] <apachelogger> well
[13:02] <apachelogger> actually it is the right use of opinion anyway
[13:03] <apachelogger> I closed the bug because it was not packaged and because molecule is inferior to qtcurve
[13:03] <ScottK> apachelogger: No.  There is no right use of opinion.
[13:03] <apachelogger> ScottK: there is of the bug tag :P
[13:03] <apachelogger> right use == what the author intent it to be used for
[13:03] <ScottK> apachelogger: I think it's not useful and we shouldn't use it.
[13:04] <apachelogger> since the packaging aspect of making molecule default is sort of resolved that leaves the closing reason of inferior implementation standing
[13:04] <apachelogger> and whether that is a good reaosn or not might very well be discussed :P
[13:05] <apachelogger> which does not change the fact that I *won't fix* it but in any case looks nicer
[13:05] <ScottK> Yes, but we have a process for deciding Kubuntu defaults that doesn't involve the bug tracker.
[13:06] <shadeslayer> i should probably apply to bug control...
[13:06]  * shadeslayer goes to frame application...
[13:07] <apachelogger> ScottK: opinion is just like invalid or wont fix to not piss off the reporter
[13:07] <shadeslayer> hehe
[13:07] <shadeslayer> its a bug which the community wants fixed but is a Wont Fix bug
[13:07] <ScottK> apachelogger: No.  Opinion is just like invalid or wontfix except it invites people to still fill my inbox with noise.
[13:07] <shadeslayer> ScottK: ++
[13:08] <apachelogger> as if they will not do it anyway?
[13:08] <apachelogger> "WHY IS THIS INVALID -> reopen"
[13:08] <ScottK> apachelogger: I predict encouragement won't reduce it.
[13:08] <apachelogger> jonny comes along -> closes again
[13:08] <apachelogger> "YOU ARE A BUTTERFLY => open"
[13:08] <apachelogger> ...
[13:08] <ScottK> The real solution is locking bug status.
[13:08] <apachelogger> ack
[13:09] <apachelogger> shadeslayer: would you mind committing your digikam rules fix?
[13:09]  * ScottK will stop now before he gets to the point where someone needs to give him a CoC warning relative to LP development priorities.
[13:09] <shadeslayer> apachelogger: in bzr?
[13:09] <apachelogger> aye
[13:09] <apachelogger> ~kubuntu-members/digikam/ubuntu/
[13:10] <shadeslayer> ok.. im just setting up bzr..
[13:10] <shadeslayer> ( brand new install )
[13:10] <ScottK> apachelogger: I was going to tell him he needed to deliver it scribbled on a napkin to Riddell in Prague.
[13:10] <apachelogger> lol
[13:11] <shadeslayer> whats Riddell doing in Prague? :D
[13:14] <ScottK> Canonical distro team development sprint.
[13:16] <toabctl> how can i restart a daemon automatically after a package update? i tried "initctl restart myupstartjobname" but that does not work. any ideas?
[13:23] <shadeslayer> ScottK: btw where does the setting for default browser live in kds?
[13:25] <apachelogger> shadeslayer: it does not
[13:25] <apachelogger> konqueror == KDE default => no override necessary in kds
[13:25] <shadeslayer> apachelogger: 0_o
[13:25] <shadeslayer> ohh
[13:25] <shadeslayer> apachelogger: then how do we set rekonq to default?
[13:26] <apachelogger> via the config :P
[13:26] <shadeslayer> apachelogger: :P
[13:26] <shadeslayer> apachelogger: i meant in the live CD
[13:26] <apachelogger> via the config :P
[13:27] <apachelogger> a) look at the code where the appropriate config value would be set and what it would be called
[13:27] <apachelogger> or b) set the setting in systemsettings and check where it changed/added a value in ~/.kde/share/config
[13:27] <apachelogger> latter is mostly easier
[13:31] <shadeslayer> apachelogger: digikam in bzr
[13:31] <shadeslayer> ill check it out later ..
[13:34] <apachelogger> shadeslayer: thx
[13:49] <dupondje> somebody here had a broken maverick ? :p
[13:49] <dupondje> aka not loading x
[14:56] <EzraR> anyone willing to review a package of mine on REVU? The package is mangler, a ventrillo client for linux. It would make a great addition for gamers in Ubuntu. It has one advocate already and should be in good shape!http://revu.ubuntuwire.com/p/mangler
[16:27] <dholbach> Last day of https://wiki.ubuntu.com/UbuntuDeveloperWeek starting in 33 minutes in #ubuntu-classroom
[16:50] <geser> dupondje: when did you update the last time?
[16:50] <dupondje> update what ? :)
[16:52] <geser> dupondje: your maverick
[16:52] <dupondje> 1hour ago :) anyway the x issue is fixed now
[16:53] <geser> dupondje: there was an grub update recently that switched a default which might cause your problem (at least it did for me)
[16:53] <geser> ok
[16:53] <geser> than it was a different issue
[16:53] <dupondje> libdrm fixed it for me it seems
[17:08] <dupondje> geser: what change was it in grub ?
[17:25] <AnAnt> Hello, why does Ubuntu build nspluginwrapper for i386 arch ?
[18:04] <Rhonda> Why not?
[18:04] <Rhonda> It also gets built for amd64 arch, btw.
[18:30] <AnAnt> Rhonda: I understand that nspluginwrapper is to get 32-bit plugins working under 64-bit linux
[18:31] <Rhonda> No, that's not the case.
[18:32] <Rhonda> Oh, wait. ndispluginwrapper? Thought you meant ndiswrapper itself :)
[18:33] <Rhonda> Though I don't find a package with that name, neither source nor binary?
[18:33] <AnAnt> nspluginwrapper
[18:34] <Rhonda> Right …
[18:34] <Rhonda> In Debian it's only built for amd64.
[18:35] <ari-tczew> \o/ yes! Outstanding Merges in universe are smaller than in main!
[18:42] <ari-tczew> bdrung: could you review bug 595499 because patch still since  2010-06-17
[18:59] <bdrung> ari-tczew: waiting for an update diff ;)
[19:10] <ari-tczew> are there any statistics about MoM status? like "X outstanding merges and Y updated merges at start FeatureFreeze" or "... on final release" ?
[19:18] <shadeslayer> MoM needs cleanup imo
[19:18] <shadeslayer> everything that has been fixed/uploaded needs to be removed
[19:19] <ScottK> That's generally automatic.
[19:33] <shadeslayer> ScottK: uh.. when the package gets uploaded?
[19:34] <ScottK> Yes.  More precisely the MoM update after the package gets uploaded.
[19:34] <ari-tczew> ScottK: not every package is removed from MoM after update.
[19:34] <ari-tczew> e.g. fakesyncs
[19:35] <ScottK> They should once they have a higher version.
[22:54] <Rhonda> What do I need in a dh 7 style rules file to create a dbg package?
[23:06] <james_w> Rhonda: nothing I believe, just the control entry with a -dbg package with the same root name as your other package
[23:07] <james_w> Rhonda: if you want a single -dbg for multiple binary packages then I think it is some more work, involving override_dh_strip: