[12:14] <gouki> irssistats does a couple more, and I'm interested in going further with it (expand monitoring capabilities), but if someone else is doing it, I should help out, instead of starting fresh (=
[12:15] <gouki> adding top 5 ubotu request, for example
[12:15] <gouki> *requests
[12:22] <ianm_> sistpoty: ok, I added them both, hopefully correctly
[12:23] <sistpoty> thx ianm_
[12:33] <theCore> nice... Mark Pilgrim is "recommending" checkinstall
[12:33] <theCore> I think I got a package to do tonight
[12:34] <LaserJock> theCore: where?
[12:34] <theCore> http://diveintomark.org/archives/2006/12/18/supertux-milestone-19
[12:36] <LaserJock> theCore: seems reasonable, although I think it would be good to just distribute a .deb
[12:37] <LaserJock> sistpoty: awesome, thanks for sending the email
[12:37] <sistpoty> LaserJock: np ;)
[12:38] <sistpoty> ;)
[12:40] <Burgwork> imbrandon: you delivering unto me ebox or do I need to intall it myself
[12:46] <theCore> LaserJock: do you still use planner-el?
[12:54] <LaserJock> theCore: not a bunch, I just haven't been using emacs a whole lot
[12:54] <theCore> LaserJock: ah, well
[12:54] <LaserJock> theCore: I might get back into it a little bit in the future
[12:55] <theCore> LaserJock: then you should check out this mode http://staff.science.uva.nl/~dominik/Tools/org/
[12:56] <geser> is it ok when a package sets the homedir of a system user to /var/run?
[12:57] <sistpoty> geser: seems like it, at least from looking at /etc/passwd
[12:58] <geser> in my /etc/passwd I have only those with a subdir in /var/run
[01:00] <geser> sistpoty: I'm not quite sure if the change to postinst in http://librarian.launchpad.net/5474087/pidentd_76127.diff is ok
[01:00] <sistpoty> geser: is it for a merge or a bug?
[01:01] <geser> sistpoty: it's for bug 74968
[01:01] <Ubugtu> Malone bug 74968 in pidentd "Unable to write pid file" [Undecided,Unconfirmed]  http://launchpad.net/bugs/74968
[01:01] <geser> pidentd is started through inetd and has no init script
[01:02] <sistpoty> geser: without testing it actually, the fix *looks* fine for me
[01:04] <geser> it looks fine to me also but I'm note quite sure with the homedir as /var/run is used by different programs
[01:06] <sistpoty> geser: /var/run is used by different programs. probably a cleaner fix would be to look through the source where the pid-file is stored and change this (or is it done via inetd?) 
[01:06] <geser> it is done via inetd
[01:07] <sistpoty> geser: the pid-thingy itself? or just started via inetd
[01:08] <mr_pouit> sistpoty: thanks for dopi and klavaro reviews :)
[01:09] <sistpoty> mr_pouit: thanks for your contributions ;)
[01:09] <mr_pouit> np :)
[01:09] <ajmitch> sarah! :)
[01:10] <Hobbsee> hey ajmitch :)
[01:10] <mr_pouit> sistpoty: I have one question about sru : how many acks are needed ? 3 or 5 or ... ?
[01:10] <sistpoty> mr_pouit: 3 (we are only 4 people ;)
[01:10] <sistpoty> hi Hobbsee
[01:10] <mr_pouit> ok
[01:10] <sistpoty> geser: probably that would be a better fix: src/pidentd.h:#define PATH_PIDFILE "/var/run/identd/identd.pid
[01:11] <sistpoty> geser: (that's where the pid-file path is defined in pidentd, as far as I've seen it now)
[01:11] <geser> yes, I wanted to also fix the remaining mentions of /var/run/identd
[01:12] <Hobbsee> hey sistpoty 
[01:12] <geser> pidentd itself gets started through inetd
[01:14] <geser> I only don't know if "adduser --quiet --system --home /var/run identd" is ok, especially the choice of the homedir
[01:17] <ajmitch> sistpoty: I thought there were 5 of you :)
[01:18] <sistpoty> geser: imo it shouldn't be a problem... maybe ajmitch can verfiy that ;)
[01:18] <sistpoty> ajmitch: member No. 5 is just the secret watching member ;)
[01:20] <ajmitch> sistpoty: oh I see :)
[01:21] <sistpoty> ajmitch: the simple question geser wants to know if a daemon can have its homedir in /var/run itself?
[01:21] <ajmitch> afaik it can
[01:21] <Lathiat> lathiat@dargo:~$ cat /etc/passwd|grep /var/run|wc -l
[01:21] <Lathiat> 6
[01:21] <sistpoty> hi Lathiat
[01:21] <Lathiat> howdy
[01:22] <sistpoty> (but as in directly /var/run, not in a subdir)
[01:22] <geser> Lathiat: those are subdirs of /var/run and not /var/run itself
[01:25] <geser> sistpoty: thanks. If nobody says don't do it I will use that patch to use /var/run instead of /var/run/identd
[01:25] <sistpoty> geser: do it ;)
[01:26] <Lathiat> ohh, /var/run itself
[01:27] <Lathiat> right, that seems a bit odd 
[01:28] <ajmitch> plenty of programs put stuff directly in /var/run
[01:31] <theCore> Hobbsee: ping
[01:31] <Hobbsee> theCore: heya
[01:32] <Lathiat> ajmitch: hrm, so they do
[01:32] <theCore> Hobbsee: I trying to package the new version of supertux
[01:33] <theCore> Hobbsee: but it seems to use Jam instead of Make
[01:33] <Lathiat> woo, supertux
[01:33] <ryanakca> how would I fix "W: solseek: package-name-doesnt-match-sonames solseek-panelapplet " ?
[01:33] <ryanakca> Hobbsee: Teg?
[01:33] <theCore> Hobbsee: What should I change in debian/rules to make it use Jam? $(MAKE)?
[01:35] <Hobbsee> ryanakca: risk clone
[01:35] <ryanakca> no, I was wondering if you wanted to have a game...
[01:35] <Hobbsee> theCore: i *dont* know - but there/s a new version?  COOL!
[01:35] <ryanakca> but tony's server is down :(
[01:36] <Hobbsee> ryanakca: usually yes, at the moment, no
[01:36] <theCore> Hobbsee: hehe
[01:36] <ryanakca> "Error while trying to connect to server 'yarusso.no-ip.org' at port 2000" "net_listen:: Connection refused"
[01:36] <theCore> ok, then I will go for the Q&D way
[01:39] <sistpoty> theCore: jam is a make replacement, just use jam instead of $(MAKE)
[01:40] <theCore> sistpoty: can I just do MAKE = jam?
[01:40] <theCore> or this is "illegal"
[01:40] <sistpoty> theCore: it's not illegal, but very very ugly to look at...
[01:40] <theCore> hehe
[01:41] <theCore> ok then
[01:41] <sistpoty> theCore: because it's not clear from the beginning, that it's not make that you call but jam instead ;)
[01:41] <theCore> s/$(MAKE)/jam/
[01:41] <sistpoty> better :)
[01:42] <sistpoty> ryanakca: for solseek: it puts shared objects to /usr/lib... but is no library.
[01:43] <sistpoty> ryanakca: if these shared objects are used only by solseek, they should reside in /usr/lib/solseek instead
[01:43] <ryanakca> sistpoty: ok... and I fix that by...
[01:43] <ryanakca> ah, so patch it or something?
[01:44] <ryanakca> or add "mkdir /usr/lib/solseek && mv /usr/lib/solseek_panelapple.so /usr/lib/solseek/" to rules/postinst?
[01:44] <sistpoty> ryanakca: but it looks a little bit like these should really belong to somewhere else (for what is this solseek_panelapplet.so good for?)
[01:44] <sistpoty> ryanakca: postinst would be completely wrong ;)
[01:44] <ryanakca> sistpoty: no clue... lemme check
[01:45] <sistpoty> ryanakca: and if move it only in rules, I guess the shared objects aren't found any longer
[01:45] <ryanakca> and then run ldconfig afterwards?
[01:46] <ryanakca> http://revu.tauware.de/details.py?upid=3824
[01:46] <sistpoty> ryanakca: I'd rather make configure do that for you... I'm quite sure it's one parameter e.g. --libdir or s.th,.
[01:46] <theCore>  -> Considering  jam (>= 2.5)
[01:46] <theCore> W: Unable to locate package jam
[01:46] <theCore> bizarre
[01:47] <sistpoty> theCore: pbuilder up to date?
[01:47] <theCore> % apt-cache show jam | grep Version
[01:47] <theCore> Version: 2.5rel-1
[01:47] <theCore> maybe ...
[01:48] <theCore> ahh, I only got the main component
[01:48] <Hobbsee> theCore: poke me if you dont get that uploaded, and i'll look into it
[01:48] <theCore> Hobbsee: ok
[01:56] <theCore> yay, it's building
[01:56] <Hobbsee> :)
[01:58] <theCore> error....
[01:58] <theCore> libvorbis missing
[01:58] <theCore> not too bad
[01:58] <Hobbsee> b-d on libvorbis-dev
[01:59] <theCore> try #2
[02:00] <theCore> I really need a way to find dependencies that build, check, update, build, check ...
[02:00] <theCore> s/that/than
[02:01] <theCore> there was a Perl hack somewhere in the maint-guide
[02:01] <theCore> but the dependencies created were awful
[02:02] <theCore> yay, it passed configure!
[02:05] <theCore> ok, almost
[02:07] <theCore> Hobbsee: do why debian/rules is copying the files manually (with cp) instead of using `make install'?
[02:09] <sebest> is there a way to remove empty dir from a package?
[02:12] <sistpoty> sebest: rmdir in debian/rules should do the trick
[02:13] <sebest> sistpoty: should i do this at the end of the install target?
[02:13] <sistpoty> sebest: after the directory is created, and before the debian package gets build... in short: yes
[02:15] <sebest> sistpoty: thx
[02:15] <sistpoty> np
[02:16] <Lathiat> sebest!
[02:17] <sebest> Lathiat ! :)
[02:17] <sebest> what's up?
[02:18] <Hobbsee> theCore: i'm not sure.  i believe it's deliberate though
[02:18] <theCore> ahh
[02:18] <theCore> I got it
[02:18] <theCore> (I hope)
[02:19] <Lathiat> sebest: nm, hows about you?
[02:19] <Lathiat> thanks for fixing that bug :>
[02:19] <agent> i created a python module deb that is supposed to work with with python > 1.5 and was tested with many different versions, including 2.2, by the mod author - yet it only works with 2.5 and not 2.4 on my system.. what can be wrong?
[02:19] <sebest> Lathiat: it was really annoying :)
[02:20] <Lathiat> yeh, was :)
[02:20] <sistpoty> agent: what does it do with 2.4? spit out a backtrace?
[02:20] <sebest> i read that avahi will be enabled by default, great
[02:20] <agent> sistpoty: i cannot import it
[02:20] <Lathiat> sebest: in feisty, yeh
[02:20] <Lathiat> woo hoo ;)
[02:20] <Lathiat> 0.6.16 is coming out shortlyish
[02:21] <agent> sistpoty: my guess its a path problem
[02:21] <sistpoty> agent: probably... or it was built only for 2.5 and not for 2.4
[02:22] <agent> sistpoty: but usr/lib/python2.4 and usr/lib/python2.5 both have the exact same files installed... the rest is in /usr/share/python-support/
[02:22] <agent> sistpoty: could it still be the case that it was built only for 2.5?
[02:22] <sistpoty> agent: hm... then it *should* really work imo... 
[02:22] <sistpoty> agent: are you build-depending on python-all-dev?
[02:22] <agent> sistpoty: yes
[02:23] <agent> sistpoty: should i try 2.4 only?
[02:23] <Hobbsee> theCore: gotten supertux done yet?
[02:23] <theCore> Hobbsee: I am finishing it
[02:23] <agent> sistpoty: then again, if i do 2.4 only it won't build the module for 2.5... hrm
[02:23] <sebest> Lathiat: do you know something about update-menus?
[02:23] <Lathiat> not a thing ;)
[02:24] <Hobbsee> theCore: yay :)
[02:24] <Lathiat> sorry
[02:24] <sistpoty> agent: python-all-dev will draw in 2.4 and 2.5, so that shouldn't be the problem
[02:24] <agent> sistpoty: yeah... i endedup installing 2.5 because of that :)
[02:25] <sistpoty> agent: and it does work wrt with 2.5? and not with 2.4 though the files are the same?
[02:25] <agent> sistpoty: i just don't get it... all the files that really count are version number agnostic in terms of directory structure since its all in /usr/share/python-support
[02:25] <agent> sistpoty: yes, that is correct
[02:26] <LaserJock> sistpoty!
[02:26] <sistpoty> LaserJock ?
[02:26] <LaserJock> you da man :-)
[02:26] <sistpoty> hehe
[02:26] <agent> sistpoty: well, looking at the dir structure more closely, usr/lib/python2.*/ are populated exactly the same, but they are empty of files - they just have dirs.. all python files are in usr/share/python-support/
[02:26] <sistpoty> agent: do you call dh_pythonsupport (or whatever that is called nowadays *g*) in debian/rules?
[02:27] <sebest> is it possible to comment on REVU even if i'm not a reviewer?
[02:28] <theCore> does Feisty will have Python 2.5 by default? 
[02:28] <sistpoty> sebest: just pm me your comment, I'll add it
[02:28] <agent> sistpoty: dh_pysupport and dh_python are called
[02:28] <sistpoty> theCore: seems like it
[02:28] <theCore> \o/
[02:28] <sebest> sistpoty: i wanted to comment on one of my upload
[02:28] <sistpoty> sebest: you can always do that ;)
[02:29] <sistpoty> (if you can get to your password)
[02:29] <sebest> sistpoty: that's what i'm missing :)
[02:29] <sistpoty> agent: have them in debian/rules?
[02:29] <sistpoty> sebest: does the recover password thingy work?
[02:29] <agent> sistpoty: yes... i think without that nothing would build :)
[02:30] <theCore> Hobbsee: done
[02:30] <sistpoty> agent: well, haven't made through the python-transition myself, so I cannot tell this ;)
[02:30] <sistpoty> agent: sorry, I have no more clues w.o. looking at the package. can you put it somewhere?
[02:31] <sebest> sistpoty: that's what i was looking for, but there is non on the homepage, does it only appear on failed login?
[02:31] <Hobbsee> theCore: yay :)
[02:31] <Hobbsee> does it work?
[02:31] <sistpoty> sebest: yep... just enter anything in the password field ;)
[02:31] <theCore> Hobbsee: I am testing it
[02:32] <Hobbsee> :)
[02:32] <agent> sistpoty: i think i know whats wrong actually... crazy python install scripts look in control file which itself looks for python version somehow (dunno how) and somewhere there is a communication mistake where only 2.5 is shown... although i still do not understand how 2.4 dirs are created :/
[02:33] <agent> sistpoty: it calls pyversion -r
[02:33] <agent> sistpoty: (the install script) to get python avail versions
[02:34] <sistpoty> agent: ah, I knew there was some magic with the pyhton-versions from control file involved, but as I said, I didn't dive too deep into it
[02:34] <agent> can someone run pyversions -r in their terminal and tell me if it works or errors with "error parsing Python-Version attribute"
[02:36] <sistpoty> same here
[02:37] <sistpoty> sebest: do you want an answer via mail or right here? (/me == daemon@poleboy.de=
[02:37] <sebest> ah ok
[02:37] <sebest> sistpoty: i rewrote the package with debhelper
[02:37] <sistpoty> nice
[02:38] <sebest> but about the licence , yes you can tell me here
[02:38] <sistpoty> sebest: you should put a link to the gentoo bug report in debian/copyright. that way it's clear that upstream *meant* it to be gpl/artistic and only wrote otherwise in his script
[02:39] <bddebian> Heya gang
[02:40] <sebest> sistpoty: oki, and about the "or perl artistic" ?
[02:40] <sistpoty> sebest: for the dual license, just write s.th. like: This software is dual licensed, either GPL or Artistic License, then the gpl snippet and some pointers to look at /usr/share/common-licenses/{GPL,Artistic}
[02:40] <sistpoty> sebest: it was artistic license, right?
[02:40] <sebest> yes right
[02:41] <sistpoty> ok, should be fine then
[02:41] <sistpoty> hi bddebian
[02:41] <bddebian> Heya sistpoty
[02:41] <bddebian> You're a REVU machine :)
[02:42] <sistpoty> I just try to catch up with you ;)
[02:42] <bddebian> Heh, yeah right :-)
[02:43] <agent> is there a shell command/script that will output to console what python versions are available?
[02:43] <agent> python -V just outputs current default version, not all versions installed
[02:44] <sistpoty> agent: pyversions -s or pyversions -i
[02:45] <agent> sistpoty: what is the difference? i don't want to create a package that works for me and then breaks when 2.6 or whatnot comes around
[02:46] <sistpoty> agent: it's supported vs. installed... so in theory pyversions -i would be the same to pyversions -s if you build-depend on python-all-dev
[02:46] <agent> sistpoty: okay, thank you... i will use -i for installed "just in case"
[02:46] <sistpoty> hehe
[02:53] <LaserJock> alright, I'm off
[02:53] <LaserJock> I should be back in a couple of days
[02:53] <sistpoty> cya LaserJock
[02:53] <LaserJock> if anybody needs something tell them to email
[02:53] <sistpoty> ok
[02:54] <sistpoty> ok, one last review, then I'm off to bed...
[02:54] <LaserJock> \o/
[02:54] <ajmitch> bye LaserJock 
[02:54] <sistpoty> anyone with a review request right now?
[02:54] <sebest> sistpoty: http://revu.tauware.de/details.py?upid=3841 :)
[02:55] <sistpoty> sebest: ok
[02:57] <theCore> oh the fun...
[02:57] <theCore> I installed supertux in /
[02:58] <agent> :D
[02:58] <agent> it could be worse, at least the rules file did not have a "rm -rf /" line in it :D
[02:59] <theCore> hehe
[02:59] <agent> err
[02:59] <agent> maybe i should not give people ideas
[02:59] <theCore> we got fakeroot for that :)
[03:00] <sistpoty> sebest: uploaded, thx
[03:00] <bhale> for now
[03:00] <Hobbsee> hehe
[03:00] <sebest> sistpoty: thanx!
[03:00] <sebest> sistpoty: i have 2 other package, one small, and one bigger :)
[03:00] <sebest> http://revu.tauware.de/details.py?upid=3809
[03:01] <sistpoty> sebest: the smaller one right now, the bigger one tommorrow, ok?
[03:01] <sebest> yes, the smaller is not yet on the revu page
[03:01] <sistpoty> argl... ok then I'll review the bigger one now, and the smaller one tomorrow ;)
[03:05] <sebest> sistpoty: the big one will also be reviewed by seb128, because it needs a specific configuration in smb.conf: enabling the "net usershare" functionnality
[03:05] <sistpoty> sebest: nautilus-share?
[03:06] <sebest> sistpoty: yes
[03:07] <sistpoty> sebest: the long description could be a little bit more verbose
[03:09] <sistpoty> sebest: are you upstream for it?
[03:09] <sebest> sistpoty: i am
[03:09] <sistpoty> ah,k
[03:09] <brainsik> does anyone know why the echo command behaves differently under dash than bash?
[03:09] <sistpoty> sebest: then debian/copyright makes sense ;)
[03:10] <sistpoty> brainsik: I guess it's a builtin in bash?
[03:10] <sebest> brainsik: maybe on is built-in ?
[03:10] <sistpoty> hehe
[03:11] <brainsik> sebest, sistpoty: that's true, but the docs for each say -e option does the same thing. :(
[03:12] <sebest> brainsik: i already notice a similar bug, the vmware scripts use bin/sh which is a link to dash on edgy, and the script fails on echo -e
[03:12] <brainsik> sebest: exactly. in my case, one of the module-source packages in main wouldn't compile
[03:13] <sebest> to solve my issue i changed !bin/sh to !bin/bash, but i don't know if you can do the same
[03:14] <sistpoty> sebest: there shouldn't be an shlibs file in the package, since it's not a library and also the generated postinst with the ldconfig call is useless
[03:14] <sebest> that's not a library?
[03:15] <sistpoty> sebest: you don't link programs against it, do you?
[03:15] <sebest> sistpoty: right, it's just a nautilus extension
[03:15] <sistpoty> see ;)
[03:15] <sebest> .so
[03:15] <freeflying|away> REVU day today?
[03:15] <brainsik> sebest: i'm tempted to remove the dash package. this is the second time it's caused a package to fail for me.
[03:15] <sistpoty> freeflying|away: yep
[03:15] <sistpoty> FeistyFawn: and tomorrow and the day after tomorrow as well
[03:16] <sistpoty> freeflying|away: ^^ even
[03:16] <freeflying|away> cool  :)
[03:17] <sebest> sistpoty: what should i fix about the shlibs issue?
[03:17] <sebest> sistpoty: i don't understand where the postint/preinst scripts come from :)
[03:17] <sistpoty> sebest: you shouldn't call dh_makeshlibs... but I don't know how you can do this with cdbs :)
[03:17] <sistpoty> sebest: postinst/preinst also comes from dh_makeshlibs
[03:18] <sebest> sistpoty: it's hidden deep in cdbs?
[03:18] <sistpoty> sebest: deep as in crypted, yes
[03:19] <sebest> sistpoty: i see some env var in /usr/share/cdbs/1/rules/debhelper.mk
[03:19] <sistpoty> sebest: I look at it right now, but I haven't found a way to disable it yet :(
[03:21] <sebest> sistpoty:  he :)
[03:21] <ScottK> I fixed up pyspf-2.0.1 from the latest set of REVU comments.  I believe it's ready for another look http://revu.tauware.de/details.py?upid=3843 - Thanks!
[03:21] <sebest> sistpoty: i don't know why i used that, it was some one year ago or so
[03:21] <sebest> sistpoty: the nice thing is that it's quite easy to use
[03:22] <sistpoty> sebest: unless the package is not common enough ;)
[03:23] <sistpoty> sebest: maybe this will give some hints: /usr/share/doc/cdbs/buildcore.png
[03:25] <sistpoty> anyway, it's much too late here, and I gotta get up early (for a lazy student that is) tomorrow
[03:26] <sistpoty> good night everyone
[03:26] <freeflying|away> I lost my passwd of revu,  :)
[03:27] <sebest> freeflying|away: just try to login and the magic "recover my pass" will appear :)
[03:27] <freeflying|away> sebest: thanks
[03:33] <theCore> should I upload it?
[03:35] <Lathiat> theCore: shoot me the packages ;)
[03:35] <theCore> Lathiat: :)
[03:36] <Lathiat> i want to play it :P
[03:36] <Lathiat> haha
[03:36] <theCore> Lathiat: source or binary?
[03:36] <Lathiat> been lookign forward to that
[03:36] <Lathiat> source is good
[03:36] <theCore> then, I need to build it
[03:36] <theCore> :/
[03:36] <Lathiat> build what?
[03:37] <theCore> the source package
[03:37] <Lathiat> right, thats not that hard is it?
[03:37] <theCore> no
[03:37] <agent> are there any changes to the defaults in terms of paths that must be made when using distutils to install python modules?
[03:37] <theCore> Lathiat: it should take only a few minutes
[03:38] <Lathiat> fwaah, might take a whiel to upload, 30M :P
[03:42] <theCore> Lathiat: done
[03:44] <theCore> Lathiat: I uploaded it to REVU
[03:45] <jdong> ok, I think that's quite enough of me revamping the iPodVideoEncoding article...
[03:45] <jdong> any more and they might dispatch the MPAA to my front door :D
[03:46] <theCore> Lathiat: how do I send it to you?
[03:47] <theCore> it's 40MB
[03:47] <Lathiat> i'll grab it off revu
[03:47] <theCore> ok
[03:47] <theCore> Lathiat: but you still need the original tarball
[03:48] <theCore> Lathiat: REVU only has the diff
[03:55] <_Enchained> Hi all
[04:01] <bddebian> Heya _Enchained
[04:02] <_Enchained> bddebian: question :
[04:02] <_Enchained> I have to package a soft who use a .sh script to install
[04:02] <_Enchained> and in the script
[04:02] <_Enchained> it use java -jar
[04:02] <_Enchained> so I must put sun-java5-jre in BuildDep ?...
[04:03] <_Enchained> or anything else ?...
[04:06] <bddebian> I don't do java, sorry :(
[04:06] <_Enchained> I'll ask tomorrow in classroom-fr ^^
[04:06] <_Enchained> go to sleep
[04:07] <_Enchained> @
[04:08] <bddebian> What's the best way to tell why a package is in Debian but not in Ubuntu?
[04:09] <_Enchained> bddebian: can you give me your opinion on http://most-enchained.com/ubuntu/medibuntu/ ?
[04:09] <_Enchained> I made the site tonight
[04:09] <_Enchained> (how are graphics etc...)
[04:10] <bddebian> Looks nice
[04:10] <_Enchained> somthing to correct ?...
[04:11] <bddebian> Not that I can see
[04:12] <_Enchained> ok thanks
[04:12] <_Enchained> I go
[04:12] <_Enchained> (to bed)
[04:12] <bddebian> Gnight
[04:15] <bddebian> Gah, why is there no year on REVU?
[04:17] <ajmitch> probably because we never expected things to get that stale
[04:24] <bddebian> ajmitch: Aye :-)
[04:24] <bddebian> Heya LaserJock
[04:30] <bddebian> What freakin' order are packages in on REVU?
[04:33] <theCore> I think I will participate to the Summer of Code this year. My project would certainly be writing a better REVU 
[04:33] <theCore> something like Guido's Mondrian would be cool
[04:35] <LaserJock> bddebian: I think they are by comments, and the perhaps time
[04:37] <Burgundavia> imbrandon: going to ebox myself
[04:39] <bhale> Burgundavia: koke ebox?
[04:39] <Burgundavia> http://ebox-platform.com/installation-guide
[04:39] <Burgundavia> hmm, not liking feisty, however
[04:41] <bddebian> Heya Burgundavia
[04:41] <Burgundavia> hey bddebian
[04:44] <theCore> siretart: could remove supertux from /incoming ?
[04:45] <theCore> I need to upload the original source 
[04:46] <theCore> ajmitch: ping
[04:47] <bddebian> Hmm, obviously REVU doesn't update itself WRT new packages either :-(
[04:54] <chillywilly> hi
[04:54] <bddebian> What do we do about updates to packages that were already brought into the archives?  Do we still need two acks?
[04:54] <bddebian> Heya chillywilly
[04:55] <ajmitch> theCore: yes?
[04:55] <chillywilly> hi
[06:35] <bddebian> Gnight gang
[06:36] <ajmitch> night bddebian 
[07:37] <dholbach> good morning
[07:39] <ajmitch> hi daniel
[07:40] <dholbach> hey Andrew
[07:45] <tepsipakki> hmm, checkinstall build failed on amd64
[07:45] <tepsipakki> installwatch.c: In function 'fopen64':
[07:45] <tepsipakki> installwatch.c:3267: warning: cast from pointer to integer of different size
[07:45] <tepsipakki> make[2] : *** [installwatch.o]  Error 1
[07:46] <tepsipakki> is that common?
[07:47] <Fujitsu> ... it is checkinstall, so it's cursed.
[07:49] <dholbach> tepsipakki: does it build with  -Wall ?
[07:51] <imbrandon> moins
[07:52] <imbrandon> FINALY got some form of linux on here
[07:52] <imbrandon> this thing is nice but a pita
[07:52] <imbrandon> gig nic isnt detected , no accelerated video :(
[07:52] <imbrandon> i hate new computers
[07:53] <chillywilly> :-/
[07:53] <imbrandon> no tv card workie'
[07:53] <imbrandon> man
[07:55] <tepsipakki> dholbach: no idea.. I have no amd64 machine to test
[07:55] <tepsipakki> or you mean in general
[07:56] <dholbach> in general - it's stopping the build after a warning only
[08:01] <tepsipakki> oh
[08:02] <tepsipakki> I'll try when I get to work
[08:13] <imbrandon> ok ajmitch and other gurus, i'm buying a vid card tonight ( PCI-e ) as cheap as possible, ATI or NV ?
[08:14] <Hobbsee> nv, duh?
[08:14] <imbrandon> hrm but the free ATI drivers do 3d :)
[08:15] <imbrandon> here is the one i was thinking about getting, http://www.newegg.com/Product/Product.asp?Item=N82E16814141035
[08:15] <imbrandon> i just need something better than this onboard video that only does 1024x768 even in windows
[08:15] <imbrandon> lol
[08:27] <imbrandon> wget http://voyager.imbrandon.com/misc/debootstrap/debootstrap-0.3.3.1ubuntu1-2.noarch.rpm
[08:27] <imbrandon> err
[08:27] <nixternal> haha
[08:28] <imbrandon> heya nixternal 
[08:28] <nixternal> i take it yakuake wasn't hilighted :)
[08:28] <nixternal> howdy
[08:28] <imbrandon> nice domain :)
[08:28] <nixternal> why thank you ;)
[08:28] <nixternal> $22 for the whole year
[08:28] <imbrandon> btw i offered you the same deal many many moons ago :) but no biggie 
[08:28] <imbrandon> hehe any dreamhost customer can do it
[08:28] <nixternal> ya, i finally said the hell with it and did it
[08:28] <imbrandon> hehe
[08:29] <nixternal> only cuz i had like $29 in my stale paypal account
[08:29] <imbrandon> yea i finaly moved most everyting off dreamhost anyhow onto my new box
[08:29] <imbrandon> except seveas.imbrandon.com is the only thing left on the dreamhost box
[08:29] <imbrandon> pay for a full year ?
[08:29] <nixternal> yup
[08:29] <imbrandon> nice
[08:30] <imbrandon> your on mtdew ?
[08:30] <nixternal> hehe ya
[08:30] <imbrandon> omg you have to give me a shell hahaha
[08:30] <nixternal> the only server i don't have an account on
[08:30] <nixternal> err..didn't have an account on
[08:30] <imbrandon> haha
[08:30] <nixternal> i have like nixternal-nixternal20 over there
[08:39] <tepsipakki> dholbach: about checkinstall.. it already uses -Wall
[08:40] <dholbach> tepsipakki: yes, that's why it fails to build
[08:40] <dholbach> (because of the warning)
[08:41] <imbrandon> heya dholbach 
[08:41] <dholbach> hey imbrandon
[08:43] <tepsipakki> hmm, seems that I didn't paste the error:
[08:43] <tepsipakki> installwatch.c: At top level:
[08:43] <tepsipakki> installwatch.c:2694: error: conflicting types for 'readlink'
[08:43] <tepsipakki> /usr/include/unistd.h:775: error: previous declaration of 'readlink' was here
[08:50] <dholbach> I hope you all have seen the universe manual merges too! :-)
[08:52] <imbrandon> dholbach, yup, i'm working on merges all day today 
[08:53] <dholbach> nice :)
[08:53] <ajmitch> imbrandon: you make me feel like a real slacker
[08:54] <imbrandon> hahah i've been slacking the last few days
[08:54] <imbrandon> so its time to make up
[08:54] <imbrandon> even if i have no useable x
[08:54] <imbrandon> hehe
[09:01] <tepsipakki> what does the "manual" mean, that there is no REPORT and stuff available?
[09:01] <tepsipakki> umm, no
[09:01] <tepsipakki> only tried pax-utils, which didn't
[09:05] <tepsipakki> ah, I got it, maybe... so the version in ubuntu is not based on any version in debian, right?
[09:06] <imbrandon> tepsipakki, basicly , yes
[09:07] <imbrandon> little more to it than that sometimes, but thats the jest of it
[09:07] <tepsipakki> ok, I can look at some of them
[09:07] <imbrandon> sometimes they are based on the same verions just packed diffrently ( that happens when its in ubuntu first etc at times )
[09:07] <imbrandon> etc
[09:08] <tepsipakki> but it's ok to keep the delta as low as possible?
[09:08] <tepsipakki> ie. base it on the debian-version
[09:08] <imbrandon> amarok is a good ( bad? ) example of that in ubuntu and debian, they are two totaly diffrent animals
[09:08] <imbrandon> but both 1.4.4
[09:08] <imbrandon> based
[09:08] <tepsipakki> heh
[09:09] <imbrandon> but yea, imho keep the delta as small as possible if any at all
[09:09] <imbrandon> i dunno if thats official, but thats the rule of thumb i try to follow
[09:10] <imbrandon> dholbach could probably give you the "official" answer
[09:10] <imbrandon> :)
[09:10] <tepsipakki> "manual" seems to also mean that grab-merge.sh doesn't work :)
[09:10] <imbrandon> possibly
[09:10] <dholbach> you have to merge manually
[09:11] <tepsipakki> I'll start at the bottom, xfce4-xmms-plugin first
[09:12] <tepsipakki> s/at/from/
[09:31] <tepsipakki> xfce4-xmms-plugin can be synced, filing a sync-request
[09:32] <tepsipakki> wonder why it was packaged for ubuntu in the first place, since there was a debian version available
[09:38] <shawarma> tepsipakki: Our version predates the Debian one by three weeks. :-)
[09:38] <shawarma> compare http://changelogs.ubuntu.com/changelogs/pool/universe/x/xfce4-xmms-plugin/xfce4-xmms-plugin_0.4.0-0ubuntu1/changelog  with http://packages.debian.org/changelogs/pool/main/x/xfce4-xmms-plugin/xfce4-xmms-plugin_0.4.0-2/changelog
[09:39] <tepsipakki> not true, 0.3.1-1 was packaged Mon 8 Aug 2005 :)
[09:39] <tepsipakki> why not base the newer version on that
[09:39] <tepsipakki> but anyway
[09:39] <shawarma> tepsipakki: Sure, but we don't always wait for Debian to package new upstream versions.
[09:40] <tepsipakki> of course not, but that wasn't the point :)
[09:40] <shawarma> tepsipakki: Ok. I've been awake for 26 hours (working the 25 of them) so I'm not thinking entirely straight right now.
[09:41] <shawarma> and all the while you guys have been having fun merging things for Ubuntu.. gah...
[09:41] <tepsipakki> shawarma: hehe, take it easy then :)
[09:42] <tepsipakki> and get some sleep :)
[09:49] <shawarma> tepsipakki: Not quite yet. Major deadline in 2 hours and 10 minutes. Work, work, work.
[09:49] <shawarma> 2 hours, 10 minutes and 32 seconds, actually.
[09:53] <tepsipakki> heh, pity you :)
[09:54] <tepsipakki> shawarma: do you mind if I look at rawstudio?
[09:56] <shawarma> tepsipakki: Not at all.
[09:56] <lfittl> anyone in here who will come to the 23rd Chaos Communication Congress next week?
[09:56] <shawarma> tepsipakki: I'm quite certain it's just a sync.
[09:57] <tepsipakki> we'll see
[09:57] <tepsipakki> maybe yes, tepache was a sync-candidate as well
[09:58] <tepsipakki> hrmh, I hate it when config.guess is in the diff
[10:04] <tepsipakki> shawarma: actually the ubuntu version has a patch from upstream, I'll keep that
[10:06] <Sp4rKy> hi 
[10:12] <shawarma> tepsipakki: Ah, yes, I suppose they haven't gotten round to releasing that. Good catch. :-)
[10:52] <\sh> moins
[10:59] <highvoltage> hey mr \sh. I thought you are on holiday :)
[11:06] <\sh> yepp last day at work ;)
[11:07] <\sh> dholbach: libgoffice...I can only see libgoffice-0-x in feisty...what about libgoffice-1-x? :)
[11:07] <dholbach> ask upstream
[11:07] <dholbach> they went from .so.1 to .so.0
[11:08] <\sh> argl...and gnome-chemistry-utils needs libgoffice-1-x *grmpf*
[11:08] <dholbach> then you need to do a one-character change in debian/control, no?
[11:08] <ajmitch> \sh: that's a well-known problem, there are people working on that
[11:08] <dholbach> ajmitch: who's working on what?
[11:08] <ajmitch> the science team
[11:09] <\sh> dholbach: some more changes went into the debian package
[11:09] <ajmitch> gnome-chemistry-utils
[11:09] <ajmitch> ask laserjock or fujitsu or azeem
[11:09] <dholbach> \sh: which changes in which package?
[11:09] <\sh> dholbach: gnome-chemistry-utils
[11:09] <dholbach> ah, well then it's a one-character change on top of those changes :)
[11:10] <\sh> libgchemutils became libgcu
[11:10] <\sh> and our changes we can drop completly...and adjusting the debian package...and merging the changelog
[11:12] <tepsipakki> rawstudio done
[11:13] <azeem> the problem with gnome-chemistry-utils is that it needs the stable libgoffice, while Ubuntu has been shiping unstable ones so far, AFAICT
[11:14] <azeem> but LaserJock had a deeper look at it than I, and is working on it together with upstream
[11:15] <dholbach> azeem: the API changes between the two are minor (goffice-1 and goffice-0)
[11:15] <azeem> dholbach: ok
[11:15] <\sh> let's have a look...
[11:15] <dholbach> new API has been added, but only very very few have changed
[11:15] <azeem> I'm not convinced that g-c-u should use goffice in the first place, but that's a different story
[11:58] <tepsipakki> om, omins done
[11:59] <tepsipakki> riddell: ping?
[12:12] <tepsipakki> riddell: nevermind, was going to ask about plotdrop but it is sync-able and a request filed
[12:41] <daya> raphink, hi 
[12:49] <tepsipakki> giskard: ping
[12:49] <tepsipakki> bah, not here
[01:10] <tepsipakki> zul: ping
[01:10] <tepsipakki> zul: gmail-notify seems to be a sync candidate
[01:11] <tepsipakki> debian has all the patches that we do
[01:14] <gnomefreak> anyone in here know french?
[01:15] <bhale> or dholbach!
[01:16] <dholbach> hahaha
[01:17] <fernando> moin
[01:17] <tepsipakki> hobbsee: kguitar seems as a sync candidate, do you agree?
[01:18] <Hobbsee_> tepsipakki: what are the versions of each?
[01:18] <Hobbsee_> tepsipakki: that's on manual, isnt it?
[01:18] <gpocentek> gnomefreak: yes
[01:18] <tepsipakki> yes
[01:19] <gnomefreak> gpocentek: i think i got it
[01:19] <gnomefreak> ty though gpocentek 
[01:19] <tepsipakki> hobbsee_: we have 0.5-0ubuntu4, debian has 0.5-2
[01:19] <gpocentek> np :)
[01:19] <Hobbsee_> tepsipakki: gotta wait till 0.6* to sync it
[01:19] <Hobbsee_> tepsipakki: just leave that
[01:19] <tepsipakki> ok
[01:19] <Hobbsee_> tepsipakki: differening base tarballs
[01:19] <Hobbsee_> -en
[01:20] <tepsipakki> oh
[01:20] <Hobbsee_> (which is why it's a manual merge)
[01:21] <StevenK> That can be fixed.
[01:21] <StevenK> Well. Worked around. :-)
[01:22] <tepsipakki> hmm, I've now done 11 merge/sync-requests from the manual-queue.. hope that it wasn't all wasted :)
[01:22] <Hobbsee> StevenK: i know it can, but i didnt see anything specifically worth grabbing from debian, during edgy development
[01:23] <\sh> Hobbsee: taking kdbg
[01:23] <StevenK> Which makes it easier to ignore.
[01:23] <Hobbsee> \sh: go for it
[01:23] <StevenK> Fair enough.
[01:23] <Hobbsee> \sh: there's something fishy @that, iirc - it may not build, or the base tarballs may differ as well
[01:26] <\sh> Hobbsee: new upstream version
[01:26] <\sh> Hobbsee: missing some build-deps (autoconf/automake)
[01:26] <Hobbsee> \sh: way cool, should be fine then
[01:28] <\sh> Hobbsee:jepp easy one ;)
[01:28] <Hobbsee> \sh: :)
[01:28] <Hobbsee> \sh: not a sync, presumably?
[01:28] <\sh> nope
[01:29] <\sh> dh_iconcache was your change...and now some build-deps are missing on ubuntu
[01:29] <Hobbsee> ah, and it's using debhelper, not cdbs
[01:29] <\sh> jep
[01:35] <Hobbsee> to update, or not to update....that is the question...
[01:36] <\sh> what?
[01:37] <Hobbsee> my feisty
[01:37] <Hobbsee> i thought i heard reports of it not booting
[01:39] <dholbach> Hobbsee: it works again for me now
[01:39] <\sh> Hobbsee: gnucash taken ;)
[01:40] <Hobbsee> \sh: go for it.  it's a gnome app
[01:40] <dholbach> I deliberately didn't merge jokosher.
[01:40] <Hobbsee> dholbach: right
[01:40] <dholbach> just fyi - it doesn't work with either the debian's gstreamer nor ours
[01:59] <tepsipakki> dholbach: whoops, didn't notice the change in gst-plugins-farsight.. glad it didn't yet get sync'ed
[02:01] <dholbach> no problem
[02:01] <dholbach> it's not terribly important, but it makes the snippet in debian/rules work
[02:02] <dholbach> in CDBS, you can use       <target>::
[02:02] <dholbach> or                <binarypackage>/<target>::
[02:02] <dholbach> they used              <sourcepackage>/<target>::
[02:02] <dholbach> which doesn't work
[02:03] <Fujitsu> tepsipakki, that plotdrop sync is invalid. The upstream tarballs differ.
[02:03] <dholbach> so the removal of the *.la files didn't work
[02:04] <tepsipakki> fujitsu: <sigh> why do they differ?
[02:04] <Fujitsu> 'cause that's the way the world works. Blame LaserJock :P
[02:04] <tepsipakki> ok, I'll have another look
[02:04] <dholbach> tepsipakki: sometimes it's because of generating a .tar.gz from a .tar.bz2 (if the timestamp differs, the md5sum differs)
[02:05] <dholbach> tepsipakki: sometimes it's because a maintainer thinks that certain files shouldn't be shipped (which mostly is indicated by -dfsg.orig.tar.gz to indicate license problems)
[02:05] <Fujitsu> tepsipakki, don't bother. There's no action that can be taken on plotdrop at this time, and upstream is dead.
[02:05] <dholbach> same for tarballs generated from svn/cvs/...
[02:06] <tepsipakki> hmm, I guess hugin is a similar case
[02:06] <tepsipakki> it had CVS-stuff in the ubuntu tarball
[02:09] <tepsipakki> Fujitsu: do you refer to debian or the real upstream being dead? there seems to be 0.51 available
[02:24] <tepsipakki> so if the tarballs differ, the package can't be synced?
[02:25] <tepsipakki> I guess syncing doesn't include copying the same orig.tar.gz again :)
[02:25] <tepsipakki> so I'll reject the requests
[02:27] <Hobbsee> tepsipakki: correct
[02:27] <tepsipakki> I'm slowly getting the hang of it
[02:32] <Hobbsee> :)
[02:55] <slavik> is there any chance for mono-1.2 package for dapper?
[03:03] <Sp4rKy> hi there
[03:03] <slavik> hi
[03:03] <slavik> is there any chance for mono-1.2 package for dapper?
[03:40] <bddebian> Heya gang
[03:43] <cypher1> bddebian: hi!
[03:44] <bddebian> Hello cypher1
[03:46] <MidMark> hi, if I want to sponsor a bug to be added in amule -> feisty which motu I've to add?
[03:47] <MidMark> I mean which motu I've to subscribe to the bug?
[03:47] <wbadger> hello people, can someone please tell me what ubuntu<number> means in package names?
[03:49] <MidMark> 1ubuntu2 means: 1 version taken from debian, 2 version specific to ubuntu, means-> 2nd patched version from original source v1
[03:51] <bddebian> MidMark: Just subscribe ubuntu-universe-sponsors
[03:52] <wbadger> so openoffice.org 2.0.4-0ubuntu4 for example would mean it's still openoffice v2.0.4-0 and had 4 paches applied to it by ubuntu guys?
[03:53] <MidMark> bddebian: thx
[03:53] <MidMark> wbadger: it's not taken from debian, is all from ubuntu, and there are 4 patches
[03:53] <MidMark> 1 patch can have multiple patches of course
[03:54] <wbadger> you mean 1 patch can have multiple fixes?
[03:54] <MidMark> substitute patch with updates.... 4 updates
[03:55] <MidMark> one updates can have multiple patches
[03:55] <wbadger> MidMark, ok thank you :)
[04:01] <slavik> will there be a mono-1.2 package for dapper?
[04:19] <sistpoty|uni> hi folks
[04:20] <gpocentek> hey sistpoty|uni 
[04:20] <bddebian> sistpoty|uni: !!!
[04:20] <sistpoty|uni> hi gpocentek and bddebian 
[04:27] <\sh> phew...
[04:27] <\sh> many syncs, many merges
[04:28] <bddebian> Aye :-(
[04:28] <\sh> I'm ready for glhwein ;)
[04:28] <bddebian> Heya \sh
[04:28] <\sh> hey bddebian
[04:31] <sistpoty|uni> hi \sh 
[04:36] <bddebian> Damn, who's requesting all the syncs? :)
[04:36] <tepsipakki> I am?
[04:36] <bddebian> tepsipakki: All the xfonts ones?
[04:36] <tepsipakki> oh.. no
[04:36] <tepsipakki> but from the manual-queue
[04:37] <tepsipakki> I've double-checked their validity
[04:37] <\sh> me
[04:37] <bddebian> Have you built them?  Alot of times the manual syncs are due to md5sum problems because our orig.tar.gz isn't the same as Debians
[04:37] <sistpoty|uni> more syncs == less merges in the future :)
[04:37] <bddebian> \sh: Ah :-)
[04:37] <bddebian> sistpoty|uni: No, it's good, I was just curious
[04:37] <tepsipakki> sync: xfce4-xmms-plugin, tepache, pax-utils, omins, keytouch-editor, gmorgan, gmail-notify, beaglefs
[04:38] <\sh> who else...coming on the last day of work ;)
[04:38] <tepsipakki> merge: rawstudio, om
[04:38] <bddebian> \sh: ;-)
[04:38] <tepsipakki> rejected for now: hugin, plotdrop
[04:38] <sistpoty|uni> damn... now \sh will spam mail spam the changes list again :P
[04:38] <\sh> my 4 core machine needs something to do ;)
[04:38] <sistpoty|uni> hehe
[04:40] <\sh> sistpoty|uni: a long time ago that was right...now the young ones have to work more then me ;)
[04:40] <tepsipakki> it's been quiet since yesterday ;)
[05:19] <\sh> ok..off from work and now it's pub time with my colleagues
[05:19] <\sh> bye
[05:23] <sistpoty|uni> have fun \sh_away 
[05:23] <bddebian> Later \sh_away
[05:25] <jdong> imbrandon: ping
[05:26] <jdong> imbrandon: your xchat-gnome -0ubuntu2 upload didn't fix the tab char, it's still present and puking pbuilder
[05:26] <jdong> :)
[05:53] <imbrandon> jdong, ok i'll fix it here in a few
[05:54] <imbrandon> ( or try to again ) 
[05:54] <imbrandon> i have a meeting in 20 minutes
[05:54] <imbrandon> i'll do it after that
[05:56] <zorglu_> q. i would like to generate a new version in the .../debian/changes file, is there any tools to do that ?
[05:57] <zorglu_> .../debian/changelog i meant
[05:57] <azeem> zorglu_: dch
[05:57] <zorglu_> thanks
[05:59] <zorglu_> azeem: dch is not installed on my box, apt-cache search doesnt seems to find it either, any suggestion on the package name containing dch ?
[05:59] <azeem> packages.ubuntu.com has a search facility for that, at the bottom
[06:00] <zorglu_> ok apparently it does a apt-cache search :)
[06:00] <zorglu_> i will google some more :)
[06:01] <zorglu_> ok the pacakge name was 'devscripts'
[06:02] <azeem> it works for me
[06:12] <Czessi> Hi, I need a 2nd advocate. Can someone take a look, please: http://revu.tauware.de/details.py?upid=3765
[06:22] <sistpoty|uni> Czessi: sorry, cannot do reviews while at uni, but I'll look at it once I'm back at home (probable in 2-3 hours)
[06:22] <sistpoty|uni> Czessi: could you ping me then again? (I might forget otherwise *g*)
[06:23] <bddebian> Czessi: I'll try to take a look in a couple of minutes as well
[06:23] <Czessi> sistpoty|uni: Thanks. I must go to work in 2,5h 
[06:23] <sistpoty|uni> Czessi: d'oh. the +1 is from me :(
[06:24] <Czessi> bddebian: great, thanks
[06:25] <zorglu_> q. i got several package all creating/using the same configuration directory with the main config file in it, i would like to copy a default configuration at installation to save the time to the user, how can i fix the conflict of several package creating the same dir and default config file ?
[06:26] <zorglu_> what is the usual behaviour to follow in this case
[06:27] <sistpoty|uni> zorglu_: hm... maybe make one package that contains the configuration, on which the other packages need to depend on (which don't have the configuration)
[06:27] <zorglu_> hmm is there another possibility ?:)
[06:28] <zorglu_> i mean i find that overkill, from my shallow experience in the packaging field :)
[06:28] <sistpoty|uni> zorglu_: well, there should be other possibilities as well... let me think
[06:29] <zorglu_> hmm what about copying the default conf if and only if the config file is not already there ?
[06:29] <zorglu_> is that ok ?
[06:30] <sistpoty|uni> zorglu_: sounds ok
[06:30] <zorglu_> ok cool :)
[06:30] <zorglu_> now i just have to find out how to do that :)
[06:30] <sistpoty|uni> zorglu_: but you could run in trouble, if you need to update the default configuration
[06:31] <zorglu_> hmm i see
[06:31] <sistpoty|uni> zorglu_: because you'd need to fiddle out, if an admin modified the config or not
[06:31] <sistpoty|uni> zorglu_: the resolution would be pretty trivial though: if modified then don't do anything ;)
[06:31] <zorglu_> hehe :)
[06:32] <sistpoty|uni> zorglu_: another possibility was to abuse the alternatives system for that: each package could ship the config in a location unique to the package, and the alternatives system could take over which one to use
[06:33] <sistpoty|uni> (but that's not really an improvement over a separate config-package imo)
[06:33] <zorglu_> i agree :)
[06:33] <zorglu_> ok thanks for the info :)
[06:33] <sistpoty|uni> np
[06:48] <bddebian> Czessi: OK, advocated, though I'm not sure what we do about klear in NEW
[06:50] <Czessi> bddebian: I think it already my package in NEW (see December 11 12:10 and December 12 09:47 at the revu page)
[06:50] <bddebian> Czessi: Aye, but we should upload the newer version :-)
[06:57] <Czessi> bddebian: hmm, can't you delete the klear in NEW or is it newer than my package?
[06:57] <bddebian> I can't delete it :)
[07:01] <Czessi> bddebian: who can do that? 
[07:01] <bddebian> Only archive admins I assume
[07:09] <theCore> ftp://revu.tauware.de/incoming has been wiped?
[07:10] <theCore> that's interesting
[07:23] <sistpoty|uni> cya later
[07:54] <hub> how do I version packages that are "beta" release?
[07:54] <crimsun_> use ~
[07:54] <crimsun_> 1.0~beta3-0ubuntu1
[07:56] <hub> ah ok
[07:56] <hub> thx
[07:56] <crimsun_> np
[07:57] <hub> I wonder if I should upload it to REVU or to the archive
[07:57] <hub> I'll check it out first
[07:57] <hub> (the previous version is in universe)
[07:58] <crimsun_> archive
[07:58] <hub> of course debian highly diverge from my original package
[07:58] <hub> *sigh*
[07:58] <crimsun_> fun
[07:58] <hub> it is debian
[08:06] <somerville32> If I was in the middle of packaging one version of an application and another gets released (and I'd like to package this new version instead), should I just ask a MOTU to archive the current on revu and upload the new?
[08:10] <mr_pouit> somerville32: you can reupload, it will replace the old version
[08:10] <somerville32> mr_puit: k
[08:12] <hub> crimsun_: my fear in uploading to the archive is that it might be less stable than 0.6.1
[08:27] <toma> how often is the new queue processed?
[08:28] <mr_pouit> for revu or the archive ?
[08:28] <toma> mr_pouit:  archive
[08:29] <mr_pouit> I don't know for the archive :/
[08:30] <toma> mr_pouit: ok, is this the right channel to ask?
[08:31] <mr_pouit> yes, maybe you can ask on #ubuntu-devel
[08:31] <mr_pouit> *also
[08:31] <zorglu_> q. im porting a init.d script from fedora and it uses 'chkconfig', is there an equivalent for ubuntu ? i looked at the existing scripts and none seems to use chkconfig
[08:33] <zorglu_> or maybe a place where i could learn how to write a init.d script suitable for ubuntu
[08:33] <mr_pouit> zorglu_: http://wiki.debian.org/chkconfig ?
[08:34] <zorglu_> ah ok, so chkconfig is fully supported under ubuntu ?
[08:34] <mr_pouit> zorglu_: no, it gives chkconfig/update-rc.d equivalences
[08:34] <zorglu_> mr_pouit: i dunno why but i was under the impression it was a fedora specific 
[08:34] <zorglu_> ah ok
[08:34] <mr_pouit> I think you're right, it is fedora specific ^^
[08:34] <zorglu_> reading then :)
[08:38] <ajmitch> morning
[08:38] <geser> hello ajmitch 
[08:38] <zul> afternoon
[08:40] <zorglu_> mr_pouit: there is a similar thing apparently. using the tag ### BEGIN INIT INFO. i will use /etc/init.d/skeleton as basis :)
[08:41] <mr_pouit> ok :)
[09:00] <tsmithe> howdy motus
[09:00] <tsmithe> it's the revu time i see
[09:01] <tsmithe> i'd like to ask for alsa-firmware and alsa-tools NOT to be uploaded
[09:01] <tsmithe> but i'd love for asoundconf-gtk to be done
[09:10] <somerville32> ;?
[09:14] <tsmithe> alsa-firmware has licence issuse atm
[09:14] <tsmithe> alsa-tools wants the new alsa-firmware for the alsa-firmware-loaders to work properly
[09:14] <tsmithe> it's only built to supply a warning if it finds old firmwares
[09:14] <tsmithe> people can ignore the warning
[09:14] <tsmithe> i'd prefer it if alsa-firmware was available
[09:15] <tsmithe> (as it's not in the archives now)
[09:55] <ash211> if anybody would like to try exaile, it needs syncing with debian.. (jono reviewed it at http://www.jonobacon.org/?p=846 )
[09:56] <ash211> bug 76793
[09:57] <ash211> bug 76793
[09:57] <ash211> maybe ubugtu will come alive later
[09:57] <ash211> oh well
[09:58] <Ubug2> Malone bug 76793 in Ubuntu "please sync exaile 0.2.6+debian-2 from Debian unstable (main)" [Undecided,Needs info]  http://launchpad.net/bugs/76793
[09:58] <joejaxx> looks like the ivman merge was not done
[09:58] <joejaxx> did anyone use my debdiff?
[09:59] <bddebian> exaile is already sitting in NEW afaik
[09:59] <ash211> i was triaging the bug, and though the place to come for that bug was here
[09:59] <ash211> how can I check what's coming into NEW ?
[10:02] <sistpoty> hi folks
[10:02] <bddebian> wb sistpoty
[10:02] <sistpoty> hi bddebian
[10:02] <sistpoty> common packaging mistake session in #ubuntu-classroom now ;)
[10:03] <bddebian> ash211: https://launchpad.net/distros/ubuntu/feisty/+queue
[10:03] <ash211> thanks
[10:03] <bddebian> sistpoty: Are you trying to tell me something? ;)
[10:04] <sistpoty> hehe
[10:04] <sistpoty> well, only that everyone can help out, just like yesterday ;)
[10:05] <bddebian> Hmm, I don't see exaile on there though ash211
[10:05] <ash211> yeah, I wasn't seeing it either
[10:05] <ash211> well, if you're looking for a bug to close, there's one!
[10:07] <geser> joejaxx: what the bug # for the ivman merge?
[10:07] <joejaxx> there is not a bug written for it
[10:08] <geser> joejaxx: file a bug, attach the debdiff, subscribe ubuntu-universe-sponsors
[10:55] <sistpoty> arg... the wiki hates me :(
[10:56] <bddebian> Doh :-(
[10:56] <ogra> hate it back
[10:56] <bddebian> heh
[10:56] <sistpoty> It says I cannot rename my wrongly placed page, because the target page exists already... but if I click on the target page, it says that it doesn't exit... *clueless*
[10:57] <Burgwork> sistpoty: if you just deleted a page, it take a bit for the page to actually be deleted from the db, it seems
[10:58] <sistpoty> Burgwork: nope, afaict I didn't delete a page (maybe I accidently didn't create a page as in create but no more action and create the wrong one instead)
[11:06] <sistpoty> Czessi_away: cjwatson just removed klear from the new queue... so we can upload the newer version
[11:06] <sistpoty> bddebian: do you want to upload, or shall I?
[11:07] <coyctecm_> rtorrent crashes everytime I try to open torrent
[11:07] <coyctecm_> ubuntu edgy
[11:07] <Adri2000> bug report
[11:07] <sistpoty> coyctecm_: then please file a bug at https://launchpad.net/distros/ubuntu/+source/rtorrent
[11:07] <coyctecm_> sure
[11:07] <sistpoty> coyctecm_: and state which version you are using ;)
[11:08] <coyctecm_> now I'm using newiest stable
[11:08] <coyctecm_> directly from rtorrent site
[11:08] <sistpoty> coyctecm_: so you didn't install it via apt-get?
[11:09] <sistpoty> coyctecm_: I guess you should file a bug in the rtorrent bug tracker then...
[11:09] <coyctecm_> first I did install with apt-get, that version crashes, then I compiled it my self
[11:10] <coyctecm_> I'll file a bug
[11:10] <sistpoty> coyctecm_: we can handle bugs for the version in the archive... but we cannot handle ones for self-compiled software (because we have too many bugs ourselves already :(()
[11:12] <coyctecm_> sure. version from ubuntu edgy universe repos is the version which crashes
[11:12] <coyctecm_> :)
[11:12] <coyctecm_> not the newer whch I compiled my self
[11:12] <coyctecm_> which
[11:12] <sistpoty> coyctecm_: ah :)
[11:13] <coyctecm_> i so tired that my english must be horrible :D
[11:13] <sistpoty> hehe, I guess mine isn't really better ;)
[11:19] <coyctecm_> now it's reported.  https://launchpad.net/distros/ubuntu/+source/rtorrent/+bug/76812
[11:19] <Ubugtu> Malone bug 76812 in rtorrent "rtorrent crashes when opening torrent..." [Undecided,Unconfirmed]  
[11:20] <coyctecm_> i'm going to sleep -->  
[11:22] <bddebian> sistpoty: Go for it, you're DA MAN :-)
[11:27] <pirast> how can i run two pbuilders; an edgy one and a feisty one and how can I select which one I want to use then?
[11:28] <pirast> and how can I get the edgy source of a program although i am running feisty?
[11:29] <rmjb> pirast: https://wiki.ubuntu.com/PbuilderHowto#head-1be378ab60d3bab23eefabce49cf7df927d46f81
[11:30] <pirast> rmjb, thanks.. what's about apt-get source of different releases?
[11:30] <rmjb> umm... I'm not sure, maybe a chroot? or editing sources.list?
[11:30] <fdoving> you can add more deb-src lines.
[11:31] <pirast> k thanks
[11:32] <jdong> rmjb: apt-get source doesn't take -t or /distro, unfortunately
[11:32] <jdong> rmjb: so you're probably gonna want to bookmark / searchmark packages.ubuntu.com
[11:32] <jdong> and use dget to fetch the .dsc links :(
[11:32] <fdoving> you can use apt-get source package=version
[11:32] <jdong> fdoving: that ain't exactly easy either :D
[11:32] <fdoving> it does take -t
[11:32] <fdoving> liar.
[11:32] <jdong> still involves having a madison-lite database of packages :)
[11:32] <jdong> it takes -t but doesn't work
[11:32] <fdoving> apt-get -t source bash
[11:33] <fdoving> works here.
[11:33] <jdong> no, as in
[11:33] <fdoving> your apt sucks then :)
[11:33] <jdong> apt-get source bash -t dapper
[11:33] <fdoving> you'll have to add the -t before 'source'
[11:33] <fdoving> apt-get -t dapper source bash
[11:33] <fdoving> works for me.
[11:33] <jdong> really?
[11:33] <fdoving> I do it this way.
[11:33] <fdoving> I have deb-src lines for dapper, edgy and feisty on one box.
[11:34] <rmjb> jdong: you have the additional entries in your sources.list?
[11:34] <rmjb> what fdoving saod
[11:34] <rmjb> said
[11:34] <jdong> back when I tried it, yes
[11:34] <jdong> I'm adding it back and attempting again
[11:35] <jdong> wow, it works now
[11:35] <jdong> I _SWEAR_ that back in Dapper when I tried this last, it didn't work!
[11:35] <jdong> else I wouldn't have my silly Sources.gz grokking scripts
[11:36] <fdoving> :)
[11:36] <jdong> :)
[11:36] <rmjb> question, need help actually, I have a simple package for which I was advised to split into a binary, library and lib-dev package
[11:37] <rmjb> before it was all just one binary with everything
[11:37] <rmjb> and I have that one installed and working now
[11:37] <fdoving> .. it works on dapper too.
[11:37] <jdong> fdoving: that might be true
[11:38] <jdong> the last time I used -t for real (mixing testing / unstable), install didn't care where the -t went
[11:38] <sistpoty> rmjb: what's your question?
[11:38] <jdong> I didn't know that -t had to go first
[11:38] <rmjb> in the bin-only package I'm seeing files that are not showing up when I have the split pacakge set up, i.e. with multiple binaries in control and multiple .install files
[11:38] <rmjb> why would files be generated in one instance but not the other?
[11:39] <sistpoty> rmjb: if the three .install files are the same as the one .install file for the binary-only package, it really *should* be identical
[11:39] <rmjb> sistpoty: this is the bin-only package that needs to be split: http://revu.tauware.de/details.py?upid=3446
[11:39] <rmjb> I didn't have an .install file with the bin-only package
[11:40] <rmjb> the files in question are under /usr/share/doc/<bin-pkg-name> though... are those special files?
[11:40] <sistpoty> rmjb: did you change the docs file?
[11:41] <rmjb> I removed it as recommended by dholbach
[11:41] <rmjb> in the REVU
[11:41] <theCore> does REVU is working?
[11:42] <sistpoty> rmjb: what new files are there now?
[11:42] <sistpoty> theCore: ?
[11:43] <rmjb> sistpoty: the only changes I've made to the package since dholbach's feedback are removing debian/docs adding two more binary pacakge entries to debian/control and creating 3 .install files
[11:43] <sistpoty> rmjb: but what files do you see now, which haven't been there before? 
[11:43] <sistpoty> rmjb: AUTHORS?
[11:44] <theCore> sistpoty: I uploaded my package about 5 or 6 hours ago, but my package doesn't seem to be processed yet 
[11:44] <theCore> sistpoty: ftp://revu.tauware.de/incoming/
[11:44] <sistpoty> theCore: I'll take a look
[11:45] <geser> are there any tools to extract debdiffs from bugreports?
[11:45] <theCore> sistpoty: it's the supertux package
[11:45] <sistpoty> geser: what do you mean with "extract debdiffs"?
[11:45] <rmjb> sistpoty: well, the source package is called pmplib, the bin-only package is easypmp, these are some files that exist in the bin-only package:
[11:45] <rmjb> /usr/share/doc/pmplib/COPYING.gz
[11:45] <rmjb> /usr/share/doc/pmplib/README.gz
[11:45] <rmjb> /usr/share/doc/pmplib/ChangeLog
[11:45] <rmjb> /usr/share/doc/pmplib/AUTHORS
[11:45] <rmjb> /usr/share/doc/pmplib/INSTALL.gz
[11:45] <geser> sistpoty: see bug 76716
[11:45] <rmjb> /usr/share/doc/easypmp
[11:45] <Ubugtu> Malone bug 76716 in om "Please sponsor om upload" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76716
[11:45] <rmjb> /usr/share/doc/easypmp/changelog.gz
[11:45] <rmjb> /usr/share/doc/easypmp/copyright
[11:45] <rmjb> /usr/share/doc/easypmp/README.gz
[11:45] <rmjb> /usr/share/doc/easypmp/changelog.Debian.gz
[11:46] <sistpoty> rmjb: some are special, yes ;)
[11:46] <rmjb> sistpoty: after the split /usr/share/doc/easypmp is not being created it seems
[11:47] <sistpoty> geser: you can append s.th. like /comment/<number> to display the comment as text, but I don't recall exactly what it has been
[11:48] <rmjb> sistpoty: should I copy the files from /usr/share/doc/pmplib to /usr/share/doc/easypmp then? and not worry about where those files went to?
[11:48] <sistpoty> rmjb: did you look through all packages? imho these should be in the first package listed in debian/control
[11:50] <rmjb> I really don't understand this build process... there's no debian/tmp/usr/share/doc/easypmp, but there's a debian/easypmp/usr/share/doc/easypmp
[11:50] <rmjb> I guess the files are already there and don't need to be listed in the easypmp.install file then
[11:50] <sistpoty> theCore: the with which you signed the upload is not in revu key database... have you registered it with your launchpad account and are in the group ubuntu-universe-contributors
[11:50] <sistpoty> ?
[11:51] <theCore> sistpoty: I was in ubuntu-universe-contributors, but left the team
[11:51] <theCore> I left*
[11:52] <ajmitch> theCore: why did you leave the team, if you still want to upload?
[11:52] <theCore> the reason is really silly...
[11:53] <sistpoty> rmjb: changelog.gz e.g. is handled via dh_installchangelogs... some are handled via dh_installdocs even if you don't list them in docs
[11:53] <sistpoty> rmjb: so the question is, how is dh_installdocs called?
[11:54] <rmjb> sistpoty: I'm using cdbs
[11:54] <theCore> I just found Ubuntu Universe Contributors ugly on my lp home page
[11:54] <rmjb> from the output it seems to be called as dh_installdocs -p<package name> for all 3 packages
[11:54] <sistpoty> rmjb: but cdbs is using debhelper underneath
[11:54] <bddebian> Later gang
[11:54] <rmjb> yes
[11:54] <rmjb> later bddebian
[11:54] <sistpoty> later bddebian
[11:55] <theCore> sistpoty: so, I would need to join again?
[11:55] <sistpoty> theCore: yes, please... otherwise I cannot import your key to revu ;)
[11:56] <theCore> sistpoty: ok, I am a member of the team again
[11:57] <sistpoty> rmjb: maybe it's some help if you put export DH_VERBOSE=1 into debian rules (at the beginning). that should give you some insights what the debhelper scripts (called from cdbs) are actually doing
[11:57] <sistpoty> theCore: ok, I'll resync the keyring and put your package from rejected back to incoming
[11:57] <rmjb> sistpoty: THAT is what I need, thank you very much
[11:58] <theCore> sistpoty: thanks
[11:58] <sistpoty> np rmjb, theCore ;)
[12:02] <rmjb> sistpoty: things are looking up, another question about the usr/share/doc
[12:02] <rmjb> sistpoty: should it just be the binary package name? and not the source?
[12:03] <rmjb> binary package name: libpmp, source package name pmplib
[12:04] <sistpoty> rmjb: binary package name, though I'd highly advise you not to copy stuff in there yourself, but using docs (dh_installdocs) or examples (dh_installexamples) instead
[12:04] <sistpoty> rmjb: that way, you needn't change anything if e.g. the library package name changes due to a different soname
[12:04] <sistpoty> (library binary package name even)
[12:05] <rmjb> sistpoty: yeah, I'm not copying in myself, but I had usr/share/doc/<source package name> in the <lib binary package>.install file
[12:05] <rmjb> so I'm removing it
[12:08] <sistpoty> theCore: your package should show up on revu when the next */10 cron runs
[12:08] <sistpoty> (minutes)
[12:08] <theCore> sistpoty: thanks again
[12:08] <sistpoty> np
[12:09] <rmjb> does the INSTALL file usually get put into a package, or is it left out?
[12:10] <sistpoty> rmjb: unless you list it in docs, it gets left out iirc. 
[12:10] <rmjb> sistpoty: I'll leave it out then... ? I hope that's okay
[12:11] <sistpoty> rmjb: usually it only contains info necessary to compile the package. and that's not really useful for a binary package (and for the source package, you have it there in the first place)
[12:11] <rmjb> cool, it's okay
[12:11] <sistpoty> rmjb: if it contains info useful for the *binary* package though (happens sometimes as well), please include it
[12:12] <rmjb> nah, it's a standard cut-and-paste INSTALL file