[00:00] <RainCT> i4x: you can also find some examples here: http://code.launchpad.net/~ubuntu-dev/ubuntu-dev-docs/packaging-jam
[00:00] <Kopfgeldjaeger> i4x: https://wiki.ubuntu.com/PackagingGuide/Basic#head-e04be34f77d138d433da4235a59a3cc82d2219be
[00:02] <i4x> LaserJock: I want to create folders, install files there, run some instructions and finally remove the temporary files!!
[00:03] <norsetto> night all
[00:04] <RainCT> i4x: the easiest way to do this is calling dh_install in debian/rules and create a debian/install file where you list each file you want to install in one line (syntax is: <original file> <destination directory, ie. usr/bin, usr/share/application, etc>)
[00:06] <LaserJock> RainCT: I'm not sure that'll work if he wants to remove them later
[00:08] <i4x> RainCT: won't it work if I only paste the files under debian/ folder ? (eg: debian/var/www/index.php)
[00:09] <RainCT> LaserJock: with cdbs he can remove them from within install:: (just rm debian/<app>/path/to/file), not sure where he has to put the code without cdbs but it must be possible, too
[00:09] <LaserJock> RainCT: but it sounds like he wants to do it at install time, not build time
[00:09] <RainCT> i4x: when you build the package, the files that are inside debian/<binary package name> are installed in the .deb
[00:09] <RainCT> ahh
[00:10] <RainCT> i4x: so.. do you want this at build time (debian/rules) or install time (debian/preinst, debian/postinst?)
[00:11] <i4x> yes!.. RainCT, I just need to use postinst to change permissions and remove some temporary files!
[00:11] <RainCT> ah ok
[00:11] <RainCT> well, what's the problem then?
[00:11] <i4x> but I see that 'rules' has some isntructions from 'ed-0.9'!..
[00:12] <i4x> what files do I really need to do something so easy?
[00:12] <RainCT> debian/rules is only used to build the .deb - it isn't included in the binary package
[00:13] <RainCT> and then there are debian/preinst, which is included in the .deb and is executed (with root permissions) when the user start sto install the package, debian/postinst after he installed the package,
[00:14] <RainCT> debian/prerm when he removes the package (but before removing it) and debian/postrm after it has been removed
[00:17] <RainCT> and if you say that you want to change permissions and remove files in postinst (although I can't think of any use case for this) then get a postinst template (I'm not sure how they look like) and just use chmod and rm -f there
[00:18] <RainCT> well, I'm off
[00:18] <RainCT> see you
[00:18] <i4x> thx!!
[00:18] <i4x> i'm in the phone!!
[00:18] <RainCT> you're welcome :)
[00:42] <sistpoty> argh... who did add all that maintainer field task. cleaning that out seems like a never ending story :/
[00:43] <sistpoty> (bug 230350 fyi)
[00:46] <LaserJock> sistpoty: DrkTranz I believe
[00:46] <sistpoty> LaserJock: hm... he filed the initial bug, but I doubt he added all that tasks (there used to be much less tasks earlier on) ;)
[00:47] <sistpoty> I guess, I'll add a "if you add any more tasks, I will personally take care that someone with a very poky stick will come after you" comment *g*
[00:47] <LaserJock> I would honestly close all the bugs and use a wiki page or something
[00:48] <LaserJock> besides the fact that it's actually a pretty unnecessary task
[00:48] <sistpoty> hm... I'm through to kio-sword atm, and there are maybe 3 bugs that I didn't close or mark won't fix so far
[00:48] <sistpoty> s/bugs/tasks
[00:50] <sistpoty> oh, and I totally agree with unnecessary :)
[00:52] <wgrant> sistpoty: But some Debian people don't.
[00:52] <bimberi> "You received this bug notification because you are subscribed to gnucash
[00:52] <bimberi> in ubuntu."
[00:53] <bimberi> Adding a comment to it is a good way to communicate with a large proportion of the Ubuntu community ;|
[00:54] <LaserJock> wgrant: the policy was to do it as-needed though
[00:54] <LaserJock> wgrant: if Debian has a problem with that they should talk to the TB
[00:54] <wgrant> LaserJock: Well, it has been 2 years...
[01:00] <LaserJock> wgrant: and?
[01:01] <wgrant> We're being slower than even Debian's release process.
[01:02] <sistpoty> wgrant: the sponsors queue is huge, merges are huge... *that* are things to care about imo, fixing a maintainer field is whishlist for me
[01:04] <wgrant> sistpoty: Right, and it seems Debian is being fairly quiet about it, so I guess it should be low.
[01:04]  * wgrant does some merges.
[01:05] <sistpoty> wgrant: yep... and finally, I guess after I've done my triage there will be only 5-10 tasks remaining :)
[01:05] <wgrant> sistpoty: Oh, good.
[01:06] <sistpoty> (most are ubuntu only, or have a maintainer field already or need to be merged anyways)
[01:32] <m0u5e> anyone know why glob2 is outdated? :(
[01:32] <luisbg> no clue
[01:32] <m0u5e> its such a great game, its sad that its oudated in the repos :(
[01:32]  * luisbg waves at LaserJock "long time no see"
[01:33] <LaserJock> hi luisbg
[01:33] <luisbg> LaserJock: how is life and your research?
[01:34] <LaserJock> they're going
[01:34] <LaserJock> better now that I don't have to worry about *buntu stuff
[01:35] <luisbg> :S
[01:35] <luisbg> thats sad :P
[01:35] <luisbg> when are you coming back?
[01:36] <luisbg> let me rephrase that...
[01:36] <luisbg> when are you finishing your research?
[01:38] <LaserJock> sometime this fall
[01:41] <luisbg> oh cool
[01:41] <luisbg> well... should go to bed
[01:41] <luisbg> cath you some other time :)
[01:47] <luisbg> s/cath/catch
[01:48] <LaserJock> luisbg: cya
[01:56] <m0u5e> eom cannot play annimated gifs, could i move to replace eom with gthumb as the default picture viewer? :)
[02:00] <leleobhz> a package manpage must to stay in . or in debian dir?
[02:04] <sistpoty> leleobhz: package manpage? do you mean a normal manpage for a program?
[02:04] <leleobhz> yep
[02:04] <leleobhz> appp.1
[02:06] <sistpoty> leleobhz: it should be installed at /usr/share/man/<section>, localized version in /usr/share/man/<locale>/<section>
[02:06] <sistpoty> iirc
[02:06] <leleobhz> err
[02:06] <leleobhz> sistpoty: in source package
[02:06] <leleobhz> using dh_manpage
[02:07] <sistpoty> leleobhz: in the source package, just put it in the debian folder
[02:08] <sistpoty> leleobhz: and make sure to reference it in <package>.manpages in the debian folder, if you use dh_installman
[02:12] <leleobhz> trying again
[02:12] <leleobhz> sistpoty: thanks!
[02:12] <sistpoty> np
[02:29]  * sistpoty goes to bed now... gn8 everyone
[02:33] <leleobhz> well, no progress
[02:33] <leleobhz> dh_installman -phandbrake
[02:33] <leleobhz> HandBrakeCLI.1: No such file or directory at /usr/bin/dh_installman line 123.
[02:33] <leleobhz> make: *** [binary-install/handbrake] Error 2
[02:34] <slangasek> you have to list the filename as debian/HandBrakeCLI.1
[02:35] <leleobhz> on handbrake.manpages?
[02:36] <leleobhz> well, i think it worked
[02:50] <leleobhz> OWWWWWWWWWWWWWWWWWWWWWWWWWWWWWOOOOOOOOOOOOOOOOOOOOOOWWWWWWWW! Done!
[02:50] <leleobhz> just run dput revu handbrake_0.9.2-0ubuntu2_source.changes
[03:27] <Hobbsee> ScottK: it was supposed to be fixed last release too, and got partially fixed.
[04:01] <ryanakca> How would I package a python app that doesn't ship a setup.py, with CDBS?
[04:02] <leleobhz> ship another installer?
[04:05] <ryanakca> leleobhz: no installer whatsoever...
[04:05] <leleobhz> hmm
[04:05] <ryanakca> leleobhz: They just say "cd into this directory and run ./foobar"
[04:06] <leleobhz> i think if you want to use cdbs
[04:06] <leleobhz> well
[04:06] <ryanakca> well, "run 'python foobar.py'"
[04:06] <leleobhz> this foobar is a python app?
[04:06] <leleobhz> aaaaaaaaaaaaaaaaaaaaaaaaa
[04:06] <leleobhz> ryanakca: well, hard to say, but maybe cdbs inadequate for this case
[04:06] <leleobhz> anyway, if you want to use cdbs
[04:07] <ryanakca> Did you want to see what I have so far? I'm manually installing it to /usr/share and /usr/bin... but it still wants to run setup.py :) ...
[04:07] <leleobhz> i think you may need create a patch, creating a setup.py
[04:07] <leleobhz> ryanakca: so why cdbs? ;]
[04:08] <ryanakca> leleobhz: no clue ;)
[04:10] <leleobhz> ryanakca: i think you have 2 choices.
[04:10] <ryanakca> leleobhz: yep, thanks :)
[04:10] <leleobhz> or you make a very sample package or you patch it
[04:10] <leleobhz> ryanakca: :]
[04:12] <LaserJock> I think you should be able to just install the file
[04:12] <LaserJock> does it also install other modules?
[04:13] <leleobhz> LaserJock: havent even a setup.py ;]
[04:13] <leleobhz> may some dependencies...
[04:13] <LaserJock> yeah, but the question is what all needs installing
[04:14] <LaserJock> it could be simple enough that a setup.py is unnecessary work
[04:14] <ryanakca> LaserJock: *uploads the dsc* ...
[04:16] <ryanakca> LaserJock: dget http://mentors.debian.net/debian/pool/main/s/slingshot/slingshot_0.8.1p-1.dsc
[04:28] <LaserJock> yeah, so it has all those modules that it also installs
[04:29] <LaserJock> you could do it without a setup.py but maybe it's just as well to do it
[07:40] <\sh> moins
[08:54] <geser> Guten Morgen \sh
[08:54] <\sh> hey geser
[08:55] <\sh> never ever start something like a software project...really it gives you #trouble
[09:50] <elmargol> I did create new packages for Gnunet (GNUnet is a peer-to-peer framework which focuses on providing security.) https://launchpad.net/~teamgnunet/+archive | I would love to get some feedbrack from hardy users
[09:53] <Zic> !deowner
[09:54] <Zic> !deop
[09:55] <jussi01> Zic: can I help you at all?
[09:55] <Zic> Désolé erreur d'amsg multiserveur / Error of /amsg command on multiserver, sorry
[09:56] <jussi01> Zic: ahh :)
[10:35] <i4x> hugs 4 every1!!
[10:59] <sebner> DktrKranz: aloha \o/ time now for the fakesync?
[10:59] <DktrKranz> sebner, yep
[11:00] <sebner> =)
[11:00] <sebner> DktrKranz: bug #236312
[11:01] <DktrKranz> I'll finish wordpress update on my site and I'll test build ;)
[11:02] <sebner> kk
[11:02] <DktrKranz> you can call it "paranoia"
[11:02] <sebner> DktrKranz: ^^ , I'm curious. What do you do with the debdiff (except testbuilding of course)
[11:03] <DktrKranz> I'll download current intrepid version and apply it
[11:03] <sebner> but you don't examine the whole debdiff? ^^
[11:03] <DktrKranz> just to be sure, I'll download debian version and check if the only difference is in the changelog
[11:04] <sebner> well, there are many differences like always when we package it at our own
[11:04] <sebner> and sync then
[11:06] <DktrKranz> well, if it is a fakesync, we suppose package should be the same
[11:06] <sebner> hmm ^^
[11:06] <sebner> You'll examine and tell me then
[11:08] <rgl> hi
[11:08] <rgl> how do I install sun-java6-jre in hardy?    here its failing with dependency problems prevent configuration of sun-java6-jre :-(
[11:09] <bimberi> rgl: please put the errors on a pastebin
[11:10] <rgl> bimberi, http://dpaste.com/56677/
[11:10] <rgl> the first command I've used to install the jre was: apt-get install sun-java6-jre
[11:11] <rgl> I guess I'll have to somehow try to run the postinst script by hand to try to figure out the problem?
[11:11] <DktrKranz> rgl, IIRC, there's a candidate update in hardy-proposed
[11:11] <rgl> what is hardy-proposed?
[11:12] <rgl> a repo?
[11:12] <DktrKranz> yes
[11:12] <bimberi> yes
[11:19] <rgl> is there a way to see the packages inside that archive?
[11:19] <rgl> (as in, packages.ubuntu.com
[11:20] <DktrKranz> just add hardy-proposed line to your sources.list
[11:20] <DktrKranz> or enable it in synaptic (there's an option somewhere)
[11:22] <rgl> deb http://archive.ubuntu.com/ubuntu hardy-proposed main universe multiverse ?
[11:23] <rgl> How do I just import the sun-java6-jre updates?  (I'm don't want the other updates that are in that archive)
[11:25] <rgl> oh scrap that, there is no update in the -proposed archive.
[11:29] <rgl> OMG... not even java5 install, how could this happen? :(
[12:08] <DktrKranz> sebner, soundkonverter has some changes which should be analyzed more deeply, so I'm subscribing u-u-s
[12:26] <sebner> DktrKranz: kk, thx
[12:58] <sistpoty> hi folks
[12:58] <emgent> hi sistpoty :)
[12:58] <sistpoty> hi emgent
[12:59] <sistpoty> asac: mind to take a look at bug #232402?
[12:59] <sistpoty> asac: as there is xulrunner linking fun involved
[13:01] <\sh> hmm..does anyone know if the $HOME/.config location is somewhere defined in the environment ? like XDG_LOCAL_CONFIG or whatever?
[13:03] <asac> sistpoty: commented
[13:03] <\sh> found it
[13:03] <sistpoty> asac: thanks
[13:11]  * juliux hugs siretart for the gnucash-hbci package
[13:12] <sistpoty> saivann: ^^ read the comments?
[13:19] <siretart> juliux: I currently consider uploading it to intrepid as is. this way it becomes a candidate for hardy-backports
[13:20] <juliux> siretart: cool
[13:24] <\sh> siretart: why wasn't it in the default package of gnucash in debian? ;)
[13:25] <siretart> \sh: is this a serious question?
[13:26] <siretart> the package juliux is testing is a rebuild of a very experimental preprelease package from alioth
[13:26] <\sh> siretart: regarding the foo I read about that...I still it's a bar question ;) so no :)
[13:26] <sistpoty> hi siretart: maybe you could sponsor bug #240034 for me? (bryce told me he'd appreciate help with X merges)
[13:28] <siretart> sistpoty: I'm on it
[13:28] <sistpoty> thanks siretart :)
[13:30] <siretart> sistpoty: any particular reason why you don't keep old changelog entries?
[13:31] <sistpoty> siretart: I've done this always like this, rebasing instead of merging. Imho it's cleaner like this
[13:32] <sistpoty> (and doing it by hand means that I really need to check each bit of ubuntu delta, and if it's still necessary *g*)
[13:33] <siretart> sistpoty: it's not really usual, you should perhaps discuss this on the mailing list first
[13:33] <siretart> because you basically drop the work history of previous people working on the package
[13:34] <sistpoty> siretart: imho old changelog entries are not necessary, as long as every important bit is preserved (i.e. also who did a change and for what reason)
[13:37] <sistpoty> siretart: if you want, I can write a mail to ubuntu-devel though
[13:37] <siretart> sistpoty: I think this is pretty controversial. you remove attribution from previous developer who have worked on the package
[13:38] <siretart> but we do that on syncs as well. that's why I don't say that's unacceptable behaviour.
[13:38] <sistpoty> siretart: actually I don't remove attribution. that's one of the things that I always put in the last changelog entry (who did what change)
[13:40] <siretart> well, you could as well just leave the previous changelog entry
[13:40] <siretart> this way timestamps, contact address and all are preserved
[13:40] <siretart> (which is the point of the changelog, no?)
[13:41] <sistpoty> hm... I don't think timestamps are too important information personally
[13:41] <sistpoty> also, it's really that I'm rebasing instead of merging, i.e. I'll redo every ubuntu specific change (which guarantees reproducibility), instead of well, merging *g*
[13:42] <sistpoty> so it wouldn't really fit to have old changelog entries in there imho (because it's really me redoing the stuff instead of just merging it in)
[13:44] <Hobbsee> sistpoty: it's usefulto know what's happened previously with the package.
[13:44] <Hobbsee> sistpoty: re when transitions happened, etc.
[13:45] <sistpoty> Hobbsee: you mean the date is useful? can you give me an example?
[13:45] <siretart> sistpoty: you become unresponsive and need to talk to the previous uploader
[13:45] <Hobbsee> sistpoty: yes - well, at least the release name.  transitions, and LTS releases.
[13:45] <Hobbsee> is the immediate one I think of
[13:45] <siretart> you can dig this information out of launchpad of course, but thats tedious
[13:46] <Hobbsee> also figuring out when a change was made, so how many stable releases it effects.
[13:46] <sistpoty> siretart: that's why I put in there who did what change
[13:46] <Hobbsee> yes, but that's launchpad.  and it's nto there indefinetly, because the info may be hidden at any time, if the LP guys decide to change the UI.
[13:49] <Hobbsee> (which means it's a Very Bad Idea to have launchpad as your only easy source of this information)
[13:50] <sistpoty> hm... I'm still wondering about the "how many stable releases it effects" bit, but still can't see a concrete example
[13:50] <Hobbsee> sistpoty: okay
[13:51] <Hobbsee> sistpoty: so, if we've had a regression, due to debian packaging, say, openssh, it's useful to check what version and release the bad change is in.
[13:51] <Hobbsee> also, if we want to check when the port number has changed for a particular irc client, to check the DCC exploit.
[13:52] <Hobbsee> (and how long we need to keep that document for)
[13:52] <Hobbsee> also, if a person wrongly removes changes, and it gets uploaded (i've seen worse - eg, packages that get their default languages changed by accident!), there's no history to figure out what revision to look at, to get that change back again.
[13:53] <sistpoty> hm... ok, that does make some sense now.. thanks Hobbsee for the examples :)
[13:54] <Hobbsee> obviously, once you find the particular version you want, you can use rmadision to check what release is in each ubuntu version - but you still have to trawl through launchpad, assuming it's still there, to find it
[13:54] <Hobbsee> sistpoty: y/w.
[13:54] <sistpoty> siretart: I'll respin the debdiff and add the old changelog entry ;)
[14:00] <siretart> and moreover, we don't have any guarantees how long launchpad will keep old versions of the package
[14:06] <Hobbsee> siretart++
[14:09]  * siretart increments
[14:09] <Hobbsee> so there are 2 siretarts now?
[14:11] <sistpoty> I guess that would be fork :P
[14:11] <Hobbsee> aww
[14:12] <sistpoty> ok, new debdiff attached. I even close the merge bug now :)
[14:12] <Hobbsee> \o/
[14:13] <siretart> hey Baby
[14:13] <Hobbsee> Baby!
[14:15] <Baby> hi!!! :)
[14:19] <Kopfgeldjaeger> If there's a bug report in LP with a "wrong" title (like I want my new foo version!!11) and it should be like "Please sync blabla", should I open a new bug or just comment to the bug and subsribe e.g. u-u-s?
[14:19] <Laney> Kopfgeldjaeger: you can retitle bugs
[14:20] <Kopfgeldjaeger> aah, I see :)
[14:44] <Kopfgeldjaeger> If a package has no Debian changes (foo 1.2.3), what should be the ubuntu version?
[14:45] <Hobbsee> Kopfgeldjaeger: -0ubuntu1
[14:45] <Hobbsee> ie, 1.2.3-0ubuntu1
[14:45] <Kopfgeldjaeger> ok, thx
[14:45] <Hobbsee> Kopfgeldjaeger: ie, it isn't in debian
[14:45] <Kopfgeldjaeger> well, it's in Debian but has no extra Debian changes (only *.dsc and *.orig.tar.gz, no *.diff.gz)
[14:46] <Kopfgeldjaeger> eer
[14:46] <Kopfgeldjaeger> no *orig*, only *.tar.gz
[14:46] <Hobbsee> Kopfgeldjaeger: that means it's native.
[14:46] <Kopfgeldjaeger> yeah.
[14:46] <Hobbsee> which usually means it's specific to debian
[14:46] <Hobbsee> so, ie, has a lot of debian changes.
[14:47] <Hobbsee> you want to use something that will be overwritten if we sync from debian on a later vesrion - including if they do a point release
[14:50] <Hobbsee> Kopfgeldjaeger: 1.2.3ubuntu1 is the usual naming.
[14:50] <Kopfgeldjaeger> OK, thank you.
[14:50] <Hobbsee> (i htink)
[14:53] <Kopfgeldjaeger> Just to be sure: mcpp is in universe, but still has a main-Maintainer field, right?
[14:54] <Hobbsee> if it's in universe, it should have a universe maintainer field.
[14:54] <Hobbsee> looks like it dropped out of main in hardy.
[15:12] <sistpoty> thanks siretart
[15:26] <Kopfgeldjaeger> Hobbsee: Hm. dch renamed my working directory to mcpp-2.7.1ubuntu1 and dpkg-buildpackage again built a native package. So there is no *.diff.gz against the Debian version.
[15:27] <siretart> Kopfgeldjaeger: have you considered converting it to a non-native package? we are doing that for fai
[15:27] <siretart> and works quite will for me
[15:27] <Hobbsee> Kopfgeldjaeger: yes, you'll need to version 2.7.1-0ubuntu1 and to rename the tarball
[15:27] <Hobbsee> if you want it non-native
[15:29] <Kopfgeldjaeger> Oohkay. Thanks
[15:30] <afflux> I just noticed that HardyReleaseSchedule lists May 29th as "bug nomination deadline". Does that mean that I can't get a fix for a bug to 8.04.1 now?
[15:31] <Hobbsee> afflux: ask slangasek
[15:34] <LucidFox> Riddell, are you going to package qtjambi 4.4.0?
[15:36]  * sistpoty is off again... cya
[15:46] <leleobhz> ping to RainCT or superm1
[15:52] <RainCT> leleobhz: pong
[15:52] <leleobhz> RainCT: we can discuss this now? http://revu.ubuntuwire.com/details.py?package=handbrake
[15:52] <leleobhz> i have some questions i cant handle
[15:53] <RainCT> leleobhz: yeh, just ask
[15:53] <leleobhz> RainCT: well, some topics is in my comment
[15:54] <leleobhz> 1) Maintainer should be Ubuntu-MOTU or at least a MOTU team that will be touching this.  <-- this is a thing i dont understand
[15:54] <leleobhz> it on debian/copyright?
[15:54] <RainCT> leleobhz: Ah, I see.  For point 10 see file:///usr/share/doc/debian-policy/policy.html/ch-archive.html#s-priorities
[15:56] <leleobhz> RainCT: im in doubt for the package sign
[15:56] <RainCT> leleobhz: about 13, no. the manpage is to document how to use the command. if there's only one or two authors it can be nice to write them there too, but for 10+ that's pointless
[15:56] <RainCT> (brb)
[15:56] <leleobhz> RainCT: well, il mantain only the main developer
[15:57] <leleobhz> RainCT: but the author requested me dont insert a help in manpage
[15:58] <leleobhz> well, changing to standard so
[16:00] <leleobhz> RainCT: the main problem is the developer wants to kick-off all programming standards
[16:02] <leleobhz> and i dont know how to handle with it
[16:06] <RainCT> (back)
[16:07] <leleobhz> ^
[16:09] <leleobhz> RainCT: ill need to get out and back in 30 min +-
[16:09] <leleobhz> RainCT: please see what ive writed

[16:09] <RainCT> leleobhz: well, on Ubuntu we don't want to change standards :)
[16:09] <leleobhz> [15/06-12:09:47] < RainCT> leleobhz: well, on Ubuntu we don't want to change standards :)
[16:10] <leleobhz> i know
[16:10] <leleobhz> this is why im getting trouble handling this
[16:10] <RainCT> leleobhz: and shiping the libs with the source package will probably be rejected
[16:10] <RainCT> and is anyway a bad idea
[16:10] <leleobhz> RainCT: err
[16:10] <leleobhz> it dont ship libraries
[16:10] <leleobhz> it make a static binary
[16:10] <RainCT> ah ok
[16:10] <leleobhz> with patched library
[16:10] <leleobhz> make sense
[16:11] <RainCT> right.. dunno, I'm not a C/C++ guy
[16:11] <leleobhz> ill backl
[16:27] <afflux> anyone for sponsoring bug 199600? thanks
[16:39] <siretart> someone with java packaging experience around?
[16:42] <geser> siretart: try in #ubuntu-java or try asking man-di
[16:43] <siretart> afflux: is that patch coordinated with Rafael ProenÃ§a?
[16:45] <afflux> siretart: this is the patch he included in his private package.
[16:47] <siretart> okay
[16:47] <siretart> afflux: I have it in my upload queue
[16:47] <afflux> thanks
[16:53] <LucidFox> Can FUSE modules be GPLv3+?
[16:53] <LucidFox> without GPLv2?
[17:02] <crimsun> LucidFox: yes, only the modules.
[17:33] <Kopfgeldjaeger> Could somebody look at my debdiff in the lynx bug #147058? It corrects the Maintainer field and the desktop file
[17:35] <sebner> Kopfgeldjaeger: chris cheney will look at it when he has time ;)
[17:35] <Kopfgeldjaeger> ok
[17:50] <SpookyET> hi
[18:00] <leleobhz> RainCT: back
[18:42] <superm1> leleobhz, if the author maintains patches to different source packages during install, the better soltuion is to determine what those patches are and why they've not been submitted upstream
[18:44]  * Kopfgeldjaeger2 is writing a dirty script that downloads an old version of a package from a Debian archive site and debdiffs it against the Ubuntu version
[18:46] <leleobhz> superm1: the problem is
[18:46] <leleobhz> superm1: it compliles all the library static
[18:47] <leleobhz> everything gets a unique binary
[18:47] <superm1> geez.
[18:47] <superm1> that's not a very nice packaging scheme and playing nicely with the rest of the community
[18:48] <leleobhz> agreed
[18:48] <leleobhz> superm1: since the build sites have no internet connection
[18:48] <leleobhz> can i create a patch to create the files or something like this
[18:48] <superm1> why hasn't the author submitted these other patches upstream though?
[18:48] <leleobhz> superm1: i dunno
[18:48] <leleobhz> superm1: it uses versions in our own site
[18:49] <superm1> well i think it'd be better to find that out before you go an attempt to develop a very large patch to include all of them
[18:49] <leleobhz> i really dont know what handbrake team do
[18:49] <superm1> as i expect that will be very complex
[18:49] <leleobhz> superm1: ill try
[18:49] <superm1> especially for maintenance purposes
[18:49] <leleobhz> superm1: im using dpatch... let see what happend
[18:50] <superm1> there are some projects that will nest say a ffmpeg variant in themselves (xine, mplayer, mythtv), which i'm still not keen on either - but there is a defensive reason for it
[18:51] <superm1> the ffmpeg in distros is unreliable to contain the exact patches needed for their solution
[18:51] <SpookyET> leleobhz: have you remembered?
[18:51] <superm1> and the exact build options needed
[18:51] <leleobhz> SpookyET: nop. sorry
[18:52] <leleobhz> arent into my files... may be something very old
[18:52] <superm1> so if a majority of the patches here are applicable to upstream projects that they pull during build, then i say it's better for them to fix that and play nicer before they're allowed in ubuntu
[18:52] <leleobhz> superm1: but handbrakes compiles everything into one binary
[18:52] <leleobhz> no libraries, notting
[18:53] <leleobhz> its a "hardcoded" binary :p
[18:53] <leleobhz> this is the build mode...
[18:53] <superm1> right.  i'm just saying get an answer from upstream as to "why" it has to be that way
[18:54] <superm1> why they're patches can't go into the projects.  why they can't use dynamic libraries instead etc
[18:54] <superm1> rather than immediately jumping to the conclusion that "it has to be that way"
[18:55] <leleobhz> superm1: well, ive asked, and the team said they want (and simply)
[18:55] <leleobhz> and if im not happy.... you know
[18:56] <superm1> ugh. hate working with people like that :)
[18:56] <leleobhz> superm1: :]
[18:57] <leleobhz> so im trying to best serve both teams... but is too hard
[18:58] <leleobhz> superm1: ill try to make the patch
[18:58] <superm1> well this is my recommendation then:
[18:58] <superm1> add a get-orig-source rule
[18:58] <superm1> that will grab all that stuff you need and repack the orig.tar.gz
[18:58] <leleobhz> hm
[18:58] <Lutin> how can one get ARG_MAX in intrepid ? is #include <linux/limits.h> the only solution ?
[18:58] <superm1> and in debian/copyright explain why it's repacked like that
[18:59] <leleobhz> superm1: hmmm.... but if i use uupdate in future, it may crash
[18:59] <leleobhz> will not?
[18:59] <superm1> have a dpatch that modifies their build system to not wget, but instead use the prepackaged source packages in the orig.tar.gz
[18:59] <SpookyET> leleobhz: how many debs do you have? how many use cdbs?
[18:59] <superm1> you wont have to use uue
[18:59] <leleobhz> superm1: the jam detect if the file exists
[18:59] <superm1> leleobhz, so before jam runs, you will unpack the orig.tar.gz
[18:59] <superm1> and place the files where they need to go
[18:59] <superm1> so jam can find them
[19:00] <superm1> you can do all that in debian/rules before you get to jam
[19:00] <leleobhz> superm1: im telling about in a upgrade case
[19:00] <superm1> the get-orig-source will be ran when/before you build the source package and upload it somewhere
[19:00] <superm1> please elaborate.  i'll brb
[19:00] <leleobhz> ?
[19:01] <leleobhz> ill se what can i do
[19:11] <superm1> leleobhz, for upgrade scenarios (new upstream version), the orig.tar.gz will just be rebuilt by a MOTU updating it
[19:11] <superm1> that will grab the new versions and repack the orig.tar.gz for the new upstream version
[19:14] <leleobhz> superm1: ill try to do
[19:14] <leleobhz> may need a patch to download everything... but its ok
[19:15] <superm1> leleobhz, just handle that in debian/rules if you can in that get-orig-source.  even if it comes down to a nasty huge wget loop that parses the jam file for URLs etc
[20:11] <Riddell> kubuntu tutorials day happening now in #kubuntu-devel
[20:11] <leleobhz> wow
[20:29] <Kopfgeldjaeger2> http://tinyurl.com/6399j6 - what do you think about this? I know it's really dirty ;) -- [ ] already exists [ ] who needs that? [ ] ok [ ] 424 script too ugly
[20:36] <cyberix> https://bugs.launchpad.net/ubuntu/+source/pq/+bug/237300 Why was this changed to invalid for wine?
[20:37] <cyberix> Oh. I go ask #launchpad
[20:37] <cyberix> might be a bug in platform
[21:36] <LinuxMonkey> hi guys
[21:38]  * gsdf http://www.metacafe.com/watch/1390137/amazing_trick_with_coins nice video o_0
[21:39] <jpds> right...
[21:41] <LinuxMonkey> I dont think ill be visiting that site ever
[21:45] <jpds> LinuxMonkey: yes, probably for the best
[21:49] <LinuxMonkey> ive been reading up on MOTU and the more and more I read up on it the more and more I want to contribute.lol
[22:09] <i4x> ppl, anyone knows how do I use postinst to prompt for a password while installing a .deb package in gui?
[22:09] <i4x> not with the terminal!!
[22:10] <pochu> i4x: use debconf
[22:11] <i4x> pochu: can u give me a quick explain..?
[22:12] <norsetto> yawwwnnn
[22:12] <norsetto> err, hello
[22:12] <i4x> hi!
[22:13] <LinuxMonkey> just woke up?
[22:16] <pochu> !debconf | i4x
[22:17] <LinuxMonkey> If i want to get involved in motu I need to install the Devlopment Release right?
[22:17] <pochu> not necessarily
[22:18] <pochu> but that would help
[22:20] <norsetto> LinuxMonkey: if you know how to make and use a chroot, that would be the better option
[22:20] <LinuxMonkey> norsetto: i can learn.lol
[22:21] <norsetto> LinuxMonkey: https://wiki.ubuntu.com/DebootstrapChroot
[22:22] <LinuxMonkey> norsetto: kinda funny i was just reading that
[22:23] <norsetto> LinuxMonkey: I actually have a separate partition with the development release, and just chroot to it when I need
[22:23] <LinuxMonkey> norsetto: nice
[22:24] <LinuxMonkey> i think i got a free partition i can use.
[22:26] <i4x> norsetto: can you help me with one little thing?
[22:28] <norsetto> i4x: just a moment
[22:32] <i4x> ok I'll wait.. but anyway: how do I prompt a question (like the one in this example: http://pastebin.com/m39cbfbbe ) without using the terminal? the package won't be installed from the terminal, so I'm trying to prompt the question within the gui!! (if you know what I mean!)
[22:32] <i4x> norsetto: ^^^
[22:42] <norsetto> i4x: I don't think you can
[22:42] <i4x> hmm..
[22:43] <i4x> so I'll have to open a terminal and make the question there, right?
[22:43] <LinuxMonkey> norsetto: i got a 40GB partition, i think thats big ennought, what do u think? and should i mount it as /var/chroot?
[22:44] <norsetto> LinuxMonkey: 4 GB would be quite allright already, you can use any mount point you want
[22:44] <sebner> huhu norsetto =)
[22:44] <norsetto> heya sebner
[22:45] <norsetto> i4x: not necessarily, the package manager will do that for you
[22:47] <i4x> norsetto: will it? if I use something like http://pastebin.com/m39cbfbbe it will be prompt for the user?
[22:49] <i4x> norsetto: I'm just trying to ask the user the password (for 'mysql -p < db.sql') that normally is asked if the installation is made from the terminal!!
[22:50] <i4x> if I run a script with ﻿'mysql -p < db.sql' it doesn't ask anything!
[22:50] <norsetto> i4x: check the wiki for debconf
[22:52] <i4x> norsetto: that's where I  found that example you saw!.. but I've tried some scripts with those examples, and no1 asked anything while running within the gui!!
[22:53] <i4x> only asked if running the script in terminal!!
[22:54] <norsetto> i4x: sorry, I only use apt, I wouldn't know what other package managers can or can't do
[22:56] <emgent> norsetto: o/
[22:56] <norsetto> emgent: o\
[22:57] <i4x> hmm..
[22:57] <LinuxMonkey> should i add it to my fstab norsetto or manually mount it when i need it?
[22:58] <norsetto> LinuxMonkey: I manually mount it when I need it, you can of course do as you prefer
[22:59] <i4x> norsetto: you use apt.. with terminal, right?
[22:59] <norsetto> i4x: yes
[23:00] <i4x> well then.. thx!!! I'll make it open a terminal and ask the password!
[23:03] <LinuxMonkey> norsetto: i like your way of thinking :) manual mount it is.
[23:09] <LinuxMonkey> im following the guide to get chroot's installed and all and in the guide it has user doko (im guessing im supposed to change that to my username?)
[23:15] <LinuxMonkey> norsetto, i4x  know the answer to the question above or do i just put it as its showing on system
[23:16] <norsetto> LinuxMonkey: ?
[23:16] <i4x> LinuxMonkey: did you call me?
[23:17] <LinuxMonkey> im at the part it says Then append this line in /etc/schroot/schroot.conf:
[23:17] <LinuxMonkey> on https://wiki.ubuntu.com/DebootstrapChroot
[23:30] <LinuxMonkey> anyone available to help me with my chroot config for a sec. Im following this page https://wiki.ubuntu.com/DebootstrapChroot and under the section Installing and configuring schroot
[23:31] <devfil> someone can review pidgin-msn-pecan package in revu? http://revu.ubuntuwire.com/details.py?package=pidgin-msn-pecan
[23:32] <i4x> LinuxMonkey: sorry if you asked me for help, but I can't help you!
[23:32] <LinuxMonkey> were it says Then append this line in /etc/schroot/schroot.conf:  ... i know i need to change the [hardy] to the release name, what im not sure is the users=doko im guessing i need to change that to my user name is that true
[23:34] <joaopinto> that name is just a lable, set to something that matches your schroot content
[23:34] <joaopinto> i mean, label
[23:36] <LinuxMonkey> joaopinto: i know the [hardy] is a label,  but bellow it has users=doko thats what im asking about
[23:37] <joaopinto> that is just an access list
[23:42] <LinuxMonkey> thanks joaopinto
[23:58] <lukehasnonam1> Bug 239072