[12:46] <tsmithe> crimsun_, are you here?
[01:52] (sistpoty/#ubuntu-motu) enyc: not quite sure actually... maybe the debian new maintainers guide gives some points or the ubuntu packaging guide could have some infos
[01:52] <sistpoty> no idea somerville32
[01:52] <Fujitsu> somerville32, you mean federation.imbrandon.com?
[01:52] <somerville32> Yup
[01:52] <enyc> sistpoty: ok... erm... now there is a broken qpsmtpd package in dapper and edgy... probably broke in fiesty too now... what do I do about these different versions etc.?
[01:53] <enyc> sistpoty: create separate diffs for all of them?
[01:53] <sistpoty> enyc: first get the fix into feisty ;)
[01:53] <enyc> sistpoty: errr hrrm ive never done this before etc.
[01:53] <sistpoty> enyc: then you'd might want to fix edgy then dapper via a sru (see https://wiki.ubuntu.com/MOTU/SRU for details=
[01:54] <sistpoty> enyc: I guess we can help ;)
[01:54] <sistpoty> enyc: are you on feisty already?
[01:55] <enyc> sistpoty: no
[01:55] <enyc> sistpoty: have acces to dapper and edgy machines
[01:55] <somerville32> Don't you guys just love it when you try to ssh into a box when it's ip address has changed? haha
[01:55] <somerville32> "IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!"
[01:56] <Fujitsu> Heheh.
[01:56] <sistpoty> enyc: hm... being on feisty helps a little bit... but otherwise you can get the sourcepackage from packages.ubuntu.com/src:<packagename>
[01:56] <sistpoty> enyc: just use dget on the .dsc
[01:56] <sistpoty> (link)
[01:56] <enyc> sistpoty: I can download the 3 files for the feisty source...
[01:56] <enyc> ?dget?
[01:57] <sistpoty> enyc: same as wget, but it will fetch the three files if you stuff it with a link to a .dsc file
[01:57] <somerville32> Ugh oh. :/
[01:57] <sistpoty> enyc: package devscripts has it
[01:57] <Hobbsee> sistpoty: which breaks on LP, incidently
[01:58] <somerville32> imbrandon, ping
[01:58] <enyc> sistpoty: hrrm how do i install dget on edgy?
[01:58] <sistpoty> Hobbsee: yes, librarians fault
[01:58] <Hobbsee> somerville32: what were you wanting?
[01:58] <sistpoty> enyc: apt-get install devscripts
[01:58] <somerville32> Hobbsee, I can't login :(
[01:58] <sistpoty> maybe someone is doing something nasty? :P
[01:59] <Hobbsee> somerville32: what syntax are you using to log in, and did you fix the ip changed address?
[01:59] <somerville32> Hobbsee, I removed the offending key on line 13! :D
[01:59] <somerville32> And the syntax is:
[01:59] <somerville32> ssh federation.imbrandon.com
[01:59] <Hobbsee> of .ssh/known_hosts presumably
[02:00] <Hobbsee> you need to use ssh<EMAIL_ADDRESS>[02:00] <somerville32> My username is the same as local, I think
[02:00] <Hobbsee> as your username on your home system is often different to the username on his machine
[02:00] <Hobbsee> just try it, anyway
[02:00] <somerville32> Well.. then I don't know what my username is, haha
[02:00] <somerville32> Hobbsee, can you find me and see?
[02:00] <somerville32> *finger
[02:00] <Hobbsee> trying
[02:00] <Hobbsee> imbrandon: ping?
[02:01] <Hobbsee> oh, he's changed the passwords with the new machine
[02:01] <somerville32> Oh :/
[02:01] <Hobbsee> and it's always random each time, so i couldnt guess what it is
[02:02] <somerville32> I guess I'll just have to do things locally
[02:03] <enyc> sistpoty: right I have the fiesty source 3-files
[02:03] <Hobbsee> somerville32: where are you?
[02:04] <enyc> sistpoty: that has _not_ extracted them like "apt-get source" does....
[02:04] <Hobbsee> Lathiat: was offering shells on his machine - you may want to ask him for one.  he's in perth
[02:04] <sistpoty> enyc: now run dpkg-source -x *dsc, which will unpack the source package
[02:04] <somerville32> Hobbsee, Canada.
[02:04] <Hobbsee> hrm
[02:05] <enyc> sistpoty: this has been done
[02:05] <enyc> sistpoty: interestingly it mumbeles about signatute (using edgy machine)
[02:05] <sistpoty> strange...
[02:06] <Hobbsee> because you dont have the public key of whoever uploaded it?
[02:06] <sistpoty> shouldn't be signed at all actually
[02:06] <Hobbsee> well, it is when uploading
[02:06] <sistpoty> enyc: now change into the dir, and add a new changelog entry. you can use "dch -i" for it
[02:07] <enyc> sistpoty: well thats why it mumbles... because its not signed
[02:07] <sistpoty> enyc: well, ignore that ;)
[02:07] <geser> sistpoty: the .dsc is signed
[02:08] <sistpoty> geser: nice, indeed
[02:08] <somerville32> Hobbsee, Do you do mentorships?
[02:08] <Hobbsee> somerville32: mentorships?
[02:08] <somerville32> Hobbsee, Oui.
[02:09] <Hobbsee> somerville32: i dont understand what they are - as in, mentoring for packaging or something?
[02:09] <Fujitsu> Hobbsee, which email addresses?
[02:09] <enyc>   * Create /var/run/qpsmtpd in init script
[02:09] <enyc>     (Ubuntu bug 72602)
[02:09] <somerville32> Hobbsee, Yeah and sponsoring and stuff
[02:09] <somerville32> Hobbsee, I want to fast-track to becoming a dev :)
[02:09] <Hobbsee> Fujitsu: the @ubuntu.com and @kubuntu.org
[02:10] <sistpoty> enyc: also see if the distribution is still unstable, and if so change it to feisty
[02:10] <Hobbsee> somerville32: sort of.  people here will answer most questions
[02:10] <Fujitsu> Hobbsee, I believe you change your primary LP email, and wait for it to be synced.
[02:10] <Hobbsee> somerville32: and ubuntu-universe-sponsors is good to subscribe for uploading it
[02:10] <Hobbsee> Fujitsu: ahh, okay
[02:10] <Fujitsu> (or request that it be synced)
[02:10] <somerville32> Hobbsee, Yeah, but I want someone I can bug regularly ;p
[02:11] <Hobbsee> somerville32: the people here are regular
[02:12] <sistpoty> enyc: also the version should have an -XubuntuY suffix, so you should change it to 0.32-4ubuntu1
[02:12] <enyc> sistpoty: debian/qpsmtpd.init seemingly I need to change....
[02:12] <sistpoty> enyc: I was still with the changelog ;)
[02:12] <enyc> qpsmtpd (0.32-4ubuntu0) feisty; urgency=low
[02:12] <enyc>  ?
[02:12] <enyc> yes sorry
[02:12] <enyc> nano debian/changelog now
[02:13] <sistpoty> enyc: great!
[02:13] <enyc> sistpoty: but you suggested -ubuntu1 I wanted -ubuntu0 ;-) erm.. does it matter ?
[02:13] <enyc> sistpoty: also should there be o - there
[02:13] <sistpoty> enyc: ubuntu1 is better ;)
[02:14] <enyc> ??
[02:14] <enyc> hrrm well this looks okay to me!
[02:14] <sistpoty> enyc: 0.32-4ubuntu1
[02:14] <Fujitsu> 0.32-4ubuntu1 is the correct versioning scheme.
[02:14] <Hobbsee> enyc: you wont get it through the reviewers
[02:14] <enyc> ok i see
[02:15] <sistpoty> enyc: 0.32-4 is the old debian version, now we append ubuntu (because it's for ubuntu) and an ubuntu version starting with 1
[02:15] <enyc> eree
[02:15] <enyc> error
[02:15] <sistpoty> enyc: so if a newer debian version comes in, that would be 0.32-5 and be higher than the ubuntu version
[02:15] <sistpoty> hehe
[02:16] <enyc> sistpoty: yes I understand... used to seeing these things
[02:16] <sistpoty> good
[02:16] <enyc> I see that dch debdiff dget are all part of "devscripts"
[02:16] <somerville32> Should I use my @ubuntu.com e-mail address now that I have one?
[02:16] <Hobbsee> somerville32: yeah
[02:16] <sistpoty> enyc: yes... developers are lazy ;)
[02:16] <Hobbsee> somerville32: a) makes you look official, and b) gets filtered less
[02:17] <somerville32> Hobbsee: That'll mean I have to setup a gpg sig and everything though, haha
[02:17] <somerville32> :D
[02:17] <somerville32> sistpoty: Indeed.
[02:17] <Hobbsee> somerville32: you need to anyway, for packaging
[02:17] <somerville32> I have one for my gmail account
[02:17] <sistpoty> btw.: Hobbsee: cool revu trick, if you look at one detail page and are not logged in: just open a new tab and login there, and then reload the old tab
[02:18] <Hobbsee> yep :)
[02:18] <Hobbsee> i've been using that :)
[02:18] <sistpoty> so am I ;)
[02:18] <Fujitsu> I would use my ubuntu.com one, but the script creating them is buggy, so I use my ubuntu.{org,com}.au instead :)
[02:18] <Hobbsee> sistpoty: it'd be more helpful if i could just login on the same page.  or if it would actually keep my login, if the IP is the same
[02:18] <somerville32> Whats a good gui front-end for gpg?
[02:18] <Fujitsu> somerville32, seahorse, but don't use a GUI.
[02:19] <somerville32> lol
[02:19] <sistpoty> Hobbsee: it would indeed, and revu2 can do that (but it can do pretty much only do login and not much else)
[02:19] <sistpoty> Hobbsee: I'm just tooooo lazy ;)
[02:20] <Hobbsee> sistpoty: ahh, fair enough.  get coding then :P
[02:20] <sistpoty> hehe
[02:20] <ajmitch> Hobbsee!
[02:20] <Hobbsee> hey ajmitch!
[02:21] <enyc> sistpoty: anyway im just reading the init script carefully....
[02:21] <somerville32> Should I have my irc nick in the comment field?
[02:22] <somerville32> ie. Cody A.W. Somerville (somerville32<EMAIL_ADDRESS>[02:23] <enyc> sistpoty: so far as I can tell I only need an entry in qpsmtpd_start() ... im not sure what i the best most "neat" mway to do this... I definitely want to do the mkdir whatnot  afeter any "bail-out"
[02:24] <enyc> sistpoty: I can use a if ! -d    whatnot to only do the mkdir if the dir does not exist...
[02:24] <Hobbsee> somerville32: if you like.  i did
[02:24] <enyc> sistpoty: also there is not environment variable for the /var/run location... not that there neend to be...
[02:24] <Hobbsee> somerville32: just because i dont tend to use my real name her
[02:24] <Hobbsee> e
[02:25] <sistpoty> enyc: ok, it gets a little bit more tricky first, since the package uses a patch system (dpatch)
[02:25] <sistpoty> enyc: so before you certainly want to create a nice patch
[02:25] <sistpoty> enyc: please install dpatch
[02:26] <enyc> sistpoty: err... ok installing dpatch
[02:27] <enyc> edgy/main dpatch 2.0.20 installed
[02:27] <Fujitsu> somerville32, don't you already have a key!?
[02:27] <sistpoty> enyc: and then in the top source dir, use dpatch-edit-patch <patchname> (where patchname should be s.th. to match what you are modifying, e.g. fix-init-script)
[02:27] <somerville32> Fujitsu, Making one for my new e-mail
[02:27] <somerville32> Am I... not suppose to do that?
[02:27] <sistpoty> enyc: it should go along the names you can find in debian/patches directory
[02:28] <Fujitsu> somerville32, silly you... Just create a new ID on the existing one :)
[02:28] <somerville32> Doh!
[02:28] <somerville32> Fujitsu, syntax?
[02:28] <enyc> sistpoty: I see .. doing it this way means the patch will likely be applyable to other versions....
[02:29] <enyc> sistpoty: rather than just creating a debdiff which only applies to the fiesty version by changing it directly
[02:29] <enyc> sistpoty: ?
[02:29] <Fujitsu> somerville32, gpg --edit-key [your key ID here]
[02:29] <Fujitsu> Then adduid
[02:29] <sistpoty> enyc: kind of... you'll end up with a separate patch in debian/patches, that could be applied to different versions
[02:30] <sistpoty> enyc: but that patch will then end up in the debdiff
[02:30] <enyc> sistpoty: hrrm what is a "s.th."?
[02:30] <somerville32> Fujitsu, So I should now have:
[02:30] <somerville32> [ultimate]  (1)  Cody A.W. Somerville (somerville32<EMAIL_ADDRESS>[02:30] <somerville32> [ unknown]  (2). Cody A.W. Somerville<EMAIL_ADDRESS>[02:30] <somerville32> right?
[02:30] <somerville32> :D
[02:31] <sistpoty> enyc: s.th=something, where did I write this?
[02:31] <Fujitsu> enyc, that confused me originally. `Something', I believe.
[02:31] <Fujitsu> somerville32, correct.
[02:31] <somerville32> Fujitsu, Do I need to re upload to lp?
[02:31] <enyc> "dpatch-edit-patch init-creates-var-run-qpsmtpd"
[02:31] <sistpoty> enyc: sounds sane
[02:32] <Fujitsu> somerville32, gpg --keyserver keyserver.ubuntu.com --send-keys [your key id]  will do it, yes.
[02:32] <enyc> sistpoty: above -- [...] "<patchname> (where patchname should be s.th. to match what"[...]
[02:32] <sistpoty> enyc: well, I'm tired and no native speaker ;)
[02:32] <Fujitsu> You don't need to tell LP about they key again though, just upload it to the server.
[02:33] <sistpoty> enyc: I'd add the mkdir command directly above the start-stop-daemon call in start to the init-script
[02:34] <enyc> sistpoty: indeeed...
[02:34] <sistpoty> enyc: and I guess you'll want mkdir -p <directory>
[02:34] <enyc> sistpoty: now I either use a if -d  stanza  whatnot or  mkdir -p method...
[02:34] <sistpoty> enyc: mkdir -p is shorter ;)
[02:34] <sistpoty> <- lazy as hell
[02:35] <theCore> Hobbsee: ping
[02:37] <enyc> sistpoty: ok.. reading some other init scripts... some check with   if ! -d   ... some mkdir -p  lol
[02:38] <enyc> sistpoty: theres 3 commands actually to create the same permissions as the package installs
[02:39] <sistpoty> enyc: many ways lead to rom ;)
[02:39] <sistpoty> +e
[02:39] <enyc> sistpoty: debian/patches/init-creates-var-run-qpsmtpd.dpatch created
[02:40] <sistpoty> enyc: good, add this one to debian/patches/00list
[02:40] <enyc> sistpoty: however
[02:40] <enyc> sistpoty: I may have done somethin silly...
[02:40] <sistpoty> enyc: 00list just determines the order in which the patches are applied
[02:41] <sistpoty> enyc: if these don't overlap, you can use any order
[02:41] <enyc> sistpoty: I have done "chown qpsmtpd:qpsmtpd" on the dir... but there is a RUNAS user mentiond
[02:41] <enyc> sistpoty: maybe I sohuld be chown $RUNAS:$RUNAS incase somebody changes the $RUNAS ?
[02:42] <sistpoty> enyc: sounds sane... you can use dpatch-edit-patch <patchname> again to reedit the present patch
[02:42] <sistpoty> how many times did the word patch appear in my last msg? *g*
[02:44] <somerville32> Question: If I don't compile my python code, can I just manually set a python dependency or do I have to use dh-py* scripts and the {python:Depends} thinger?
[02:44] <enyc>         chown $RUNAS:$RUNAS /var/run/qpsmtpd
[02:44] <enyc>  hrrm
[02:44] <enyc> i wonder if is safe to assume a group exists in the same name as the RUNAS user?
[02:45] <enyc> the debian package installs /var/run/qpsmtpd  user qpsmtpd group qpsmtpd mode 2755
[02:45] <joejaxx> merges go under wishlist importance?
[02:46] <enyc> hrrm setgid dir!
[02:46] <enyc> wonder why they make it setgid
[02:46] <enyc> ... is not writable by group anyway!
[02:47] <Hobbsee> theCore: heya!
[02:47] <somerville32> Hobbsee: If I don't compile my python code, can I just manually set a python dependency or do I have to use dh-py* scripts and the {python:Depends} thinger?
[02:48] <zul> Hobbsee needs a good poke of the pointy stick of doom
[02:48] <joejaxx> its Hobbsee! :D
[02:48] <zul> heh
[02:48] <joejaxx> haha
[02:48] <Hobbsee> somerville32: better to follow python policy, ie the latter
[02:48] <enyc> sistpoty: see above ;-).. im a little puzziled
[02:48] <joejaxx> that funniest part is the trademarked trademark
[02:48] <somerville32> Hobbsee, I can't get it to work though :(
[02:48] <somerville32> Hobbsee, I'll try again and then I'll get your help
[02:49] <enyc> sistpoty: i hae no idea why the debian package makes /var/run/qpsmtpd setgid but not group-writable
[02:49] <sistpoty> enyc: I guess it's setgid in case new subdirs are created
[02:49] <sistpoty> enyc: but no real idea atm.
[02:49] <enyc> sistpoty: in combination with the problem that if somebody then changes RUNAS for some reasen... the script now relies on there being a group in the same name as that user
[02:50] <bddebian> Heya gang
[02:50] <sistpoty> hi bddebian
[02:50] <Hobbsee> somerville32: okay
[02:50] <bddebian> Heya sistpoty
[02:50] <somerville32> Hobbsee, Can you think of a python package that doesn't compile that I can use as an example?
[02:50] <Fujitsu> Morning, bddebian.
[02:51] <bddebian> Heya Fujitsu
[02:51] <Hobbsee> somerville32: supybot maybe?  anything written in python
[02:51] <joejaxx> hello bddebian
[02:51] <theCore> Hobbsee: I got supertux!
[02:51] <bddebian> Heya joejaxx
[02:51] <sistpoty> enyc: init-scripts aren't meant to work as is. if s.o. edits the script one can assume that he/she knows what to do
[02:51] <Hobbsee> python doesnt compile as such, does it?  like, pre-runtime
[02:51] <joejaxx> bddebian: :)
[02:51] <Hobbsee> theCore: yay!  how stable is it?
[02:51] <enyc> sistpoty: in any case I now have ok
[02:51] <enyc> sistpoty: ok
[02:51] <joejaxx> bddebian: my merge bug/debdiff status was changed :D
[02:51] <theCore> Hobbsee: it's pretty stable
[02:52] <enyc> sistpoty: in any case I now have the patch I want ... looking into the 00list thing
[02:52] <somerville32> Hobbsee, It can be compiled into .pyc
[02:52] <Fujitsu> somerville32, or .pyo
[02:52] <somerville32> Right
[02:52] <bddebian> joejaxx: To what?
[02:52] <theCore> Hobbsee: at least, it didn't crash
[02:52] <sistpoty> enyc: 00list is pretty much self-explanatory ;)
[02:52] <Hobbsee> theCore: yay :)
[02:52] <theCore> Hobbsee: would you like to review the package?
[02:52] <Hobbsee> theCore: sure :)
[02:52] <joejaxx> bddebian: status: fix commited :)
[02:53] <theCore> Hobbsee: http://revu.tauware.de/details.py?upid=3849
[02:53] <bddebian> joejaxx: Ah, nice
[02:53] <enyc> sistpoty: yes... niterseting how some files atre .patch  -- some files are .dpatch -- some files are .patch.dpatch
[02:53] <joejaxx> bddebian: i should do more
[02:53] <enyc> sistpoty: anyway added mine to bottom of list
[02:54] <bddebian> sistpoty: So, we doing merges or more reviews? ;-)
[02:54] <Hobbsee> bddebian: how do i use diffstat?
[02:54] <Hobbsee> bddebian: or is it zcat?  i've forgotten
[02:54] <enyc> sistpoty: now I have to use debdiff ?
[02:54] <Hobbsee> (to check if the orig tarballs are different)
[02:54] <somerville32> Hobbsee, Should I make a man page for my package if it doesn't have one?
[02:54] <sistpoty> bddebian: I'm too tired to think straight right now *g*
[02:54] <bddebian> Hobbsee: Ohh, hmmm  I'm not sure I remember
[02:54] <bddebian> Give me a sec
[02:55] <Hobbsee> somerville32: yes
[02:55] <sistpoty> enyc: first you'll need to create a source package... please recheck your debian/changelog (if you create a patch, it doesn't hurt to mention the patch name in the changelog)
[02:55] <Hobbsee> somerville32: you should keep going until you get no warnings from lintian/linda, apart from the bad version and distribution, which are debian-specific
[02:55] <sistpoty> enyc: then do a dpkg-buildpackage -rfakeroot -S -sa -us -uc
[02:55] <enyc> sistpoty: to make tneh source pkg.. i see
[02:56] <sistpoty> right
[02:56] <bddebian> Hobbsee: diff -urN foo-old foo-new | diffstat > diffstat.txt
[02:56] <Hobbsee> bddebian: neat
[02:57] <Hobbsee> bddebian: presumably i need to convert both to .tar.gz first?
[02:57] <enyc> sistpoty: iirc this sort of thing needs "build-essential fakeroot"
[02:58] <sistpoty> enyc: then install it ;)
[02:59] <bddebian> Hobbsee: I would assume so, or maybe you could just view the contents with tar, not sure about that one
[02:59] <enyc> sistpoty: already have those...    dpkg-buildpackage is complicated!
[02:59] <enyc> sistpoty: debian packaging is very powerful....
[02:59] <Hobbsee> bddebian: right
[02:59] <bddebian> to merge or review.. That is the question
[02:59] <sistpoty> enyc: now you should have to .dsc-files, one being the original you downloaded, right?
[03:00] <sistpoty> (and two .diff.gz's)
[03:01] <enyc> sistpoty: qpsmtpd_0.32-4ubuntu1.diff.gz
[03:01] <enyc> sistpoty: its created a .changes file too
[03:01] <enyc> sistpoty: as well as new .dsc
[03:01] <enyc> sistpoty: bit leaves the same orig.tar.gv  which makes sense ;-)
[03:01] <sistpoty> enyc: yes. the .changes file is useful for uploading, so you won't need that for a debdiff
[03:02] <sistpoty> enyc: so fire off debdiff ;)
[03:02] <enyc> sistpoty: with both .dsc files as arguments?
[03:02] <sistpoty> enyc: sure, debdiff will always compare two packages, so it needs to .dsc files
[03:02] <sistpoty> two
[03:03] <Hobbsee> theCore: reviewed :)  we may as well update that, i'm not sure how long debian will take
[03:03] <enyc> sistpoty: I see. now I just need to  > thso to a file and upload to the bug ?
[03:03] <sistpoty> enyc: yes... :)
[03:04] <theCore> Hobbsee: thanks
[03:04] <Hobbsee> theCore: :)
[03:04] <enyc> sistpoty: is there a naming scheme for .debdiff files?
[03:05] <theCore> What debian/compat is for? debhelper version?
[03:05] <bddebian> Yes
[03:05] <sistpoty> enyc: it's nice to have the package name in it, and to know from and to which version it is... but there isn't a standard really
[03:06] <Hobbsee> bddebian: i get
[03:06] <Hobbsee> supertux_0.3.0.tar.gz |binary
[03:06] <Hobbsee>  1 file changed
[03:06] <Hobbsee> theCore: yep
[03:06] <theCore> ok, thanks bddebian, Hobbsee
[03:06] <Hobbsee> bddebian: that presumably means...?
[03:07] <enyc> sistpoty: hrrm ok
[03:07] <bddebian> Hobbsee: What's in the tarball?
[03:07] <somerville32> Hobbsee, If I make a few modifications to disable compiling the python code in the Makefile.in provided by upstream, should I just make the mods or is the change (ie. commenting out a few lines) big enough to warrant the use of some sort of patch system?
[03:08] <Hobbsee> bddebian: sorry?  supertux*.orig.tar.gz, both changed from bz2
[03:08] <enyc> sistpoty: should i be doing a dpkg-buildpackage -b  and testing my fixed version?  i do not have a fielst machine but im reasonably happy it will likely work on edgy anyway
[03:08] <Hobbsee> somerville32: anything changing the upstream tarball is.
[03:08] <Hobbsee> somerville32: so, yes
[03:09] <sistpoty> enyc: you can use pbuilder to testbuild your package... the bot should know about it
[03:09] <sistpoty> !pbuilder howto
[03:09] <ubotu> pbuilder: personal package builder for Debian packages. In component main, is extra. Version 0.155ubuntu3 (edgy), package size 77 kB, installed size 436 kB
[03:09] <somerville32> !search pbuilder
[03:09] <ubotu> Found: pbuilder
[03:09] <sistpoty> ubotu: pbuilder howto, not the package description
[03:09] <sistpoty> ubotu: please?
[03:09] <ubotu> Sorry, I don't know anything about please? - try searching on http://bots.ubuntulinux.nl/factoids.cgi
[03:09] <somerville32> !pbuilder
[03:09] <ubotu> pbuilder is a system to easily build packages in a clean chroot environment. To get started with PBuilder, see http://wiki.ubuntu.com/PbuilderHowto
[03:10] <somerville32> !pbuilder howto is <alias> pbuilder
[03:10] <ubotu> I'll remember that, somerville32
[03:10] <bddebian> Hobbsee: What files/dirs are inside once you extract it?  Maybe it's just another tarball inside the tarball so only 1 file changed?
[03:11] <theCore> Hobbsee: should I drop all the version dependencies?
[03:11] <sistpoty> thx somerville32 and ubotu
[03:11] <somerville32> !botsnack
[03:11] <ubotu> Yum!
[03:12] <bddebian> heh
[03:13] <bddebian> Any of you Python experts?
[03:13] <Hobbsee> theCore: which ones were in ubuntu before?
[03:14] <somerville32> bddebian: I've been struggling with this python package the last week or so (my first package) - so I might be able to provide some insight.
[03:14] <theCore> Hobbsee: I was trying to find it out
[03:14] <Hobbsee> theCore: debdiff will help
[03:15] <enyc> sistpoty: hrrm my edgy pbuilder does not know howto create a fiesty enviorment
[03:15] <Fujitsu> enyc, you need to install debootstrap from Feisty.
[03:15] <Hobbsee> theCore: leave the maintainer field and all that as it is
[03:15] <theCore> Hobbsee: ok
[03:17] <chillywilly> hi
[03:18] <Hobbsee> theCore: why the -       dh_installchangelogs ChangeLog?
[03:18] <bddebian> Heya chillywilly
[03:18] <Hobbsee> oh, is it not there anymore
[03:18] <theCore> Hobbsee: uh?
[03:18] <Hobbsee> theCore: you took       dh_installchangelogs ChangeLog out of debian/rules - any reason why?
[03:19] <theCore> Hobbsee: there isn't a ChangeLog anymore
[03:19] <Hobbsee> gotcha
[03:19] <Hobbsee> my debdiff appears not to show that :P
[03:19] <bddebian> somerville32: Nevermind, thanks, apparently the mighty geser already fixed it :)
[03:20] <enyc> Fujitsu: coo thatnks... that seem to be working
[03:21] <Fujitsu> engla, np
[03:21] <somerville32> tsmithe, ping
[03:25] <Hobbsee> bddebian: foudn the trick
[03:25] <Hobbsee> bddebian: untar both tarballs, then do the folders
[03:27] <bddebian> Ah, yes thx
[03:28] <bddebian> Damn it's hard to tell what's already been requested to be synced, etc.. :-(
[03:29] <sistpoty> gn8 everyone
[03:30] <Hobbsee> bddebian: yep
[03:31] <theCore> Hobbsee: when should I put versioned dependencies?
[03:33] <theCore> Hobbsee: and it's correct to just copy the description from Supertux's homepage?
[03:33] <Fujitsu> theCore, why are you repackaging it?
[03:33] <Hobbsee> theCore: you need to for debhelper.  if it doesnt build/work with the lower dependancies.  there's nothing technically *wrong* with them, unless you try to backport it
[03:34] <Hobbsee> Fujitsu: major upstream version change, whcih means a lot of the info is out of date/wrong now
[03:34] <Hobbsee> Fujitsu: like description, build system, etc
[03:34] <Fujitsu> Ah, that'd do it.
[03:34] <Hobbsee> Fujitsu: upstream changed to jam, instead of make
[03:34] <Fujitsu> Ew.
[03:34] <Hobbsee> so it'll be painful to merge, i expect, but we'll cope
[03:34] <Hobbsee> hehe.  i've not seen jam in action
[03:35] <Fujitsu> Why not wait for Debian?
[03:35] <Hobbsee> Fujitsu: selfish reasons
[03:35] <Fujitsu> Hahah.
[03:35] <Hobbsee> like, "we've got devs who want to play this"
[03:36] <Hobbsee> Fujitsu: :P  :D
[03:36] <Fujitsu> Frozen-Bubble I can understand, but I've not played SuperTux.
[03:36] <somerville32> Are patch and unpatch rules called automatically or do I need to add calls in build and clean?
[03:36] <Hobbsee> somerville32: you need to add it, unless it's using cdbs
[03:36] <bddebian> FreeLords!!  Of course I need my libparagui first :-(
[03:36] <Hobbsee> assuming your using patch, of course
[03:36] <Hobbsee> bddebian: hrm?
[03:36] <Hobbsee> bddebian: what's freelords?
[03:37] <Hobbsee> !info freelords feist
[03:37] <Hobbsee> !info freelords feisty
[03:37] <ubotu> Package freelords does not exist in edgy
[03:37] <ubotu> Package freelords does not exist in feisty
[03:37] <Hobbsee> bah
[03:37] <bddebian> Not there yet :)  it's a WarLords clone
[03:37] <rmjb|away> !info iriverter feisty
[03:37] <ubotu> Package iriverter does not exist in feisty
[03:37] <rmjb|away> :(
[03:37] <Hobbsee> bddebian: ahh, whatever that is
[03:37] <Hobbsee> i didnt think it would be
[03:40] <bddebian> Hobbsee: Think cheesy WarCraft ;-)
[03:40] <Hobbsee> fair enough
[03:42] <Fujitsu> gnome-sudoku should be removed, shouldn't it?
[03:43] <Hobbsee> yes, ksudoku is much better.
[03:43] <Hobbsee> in fact, perhaps we should just remove all of gnome, as kde is much better.
[03:43] <Hobbsee> :P
[03:43] <Fujitsu> @lart Hobbsee
[03:46] <bddebian> hehe
[03:48] <theCore> Hobbsee: would it be correct to drop some of the old version dependencies?
[03:48] <somerville32> Gah
[03:48] <somerville32> This driving me crazy :/
[03:48] <theCore> Hobbsee: like libsdl1.2-dev (>= 1.2.7+1.2.8cvs20041007-5.2)
[03:49] <theCore> Hobbsee: I am sure this one isn't correct anymore
[03:50] <Hobbsee> theCore: yeah
[03:50] <Hobbsee> just keep the deps there
[03:50] <Hobbsee> theCore: it's especially troublesome if they decide to backport
[03:51] <theCore> Hobbsee: should I explain why I dropped it in the changelog?
[03:51] <somerville32> What does this mean?:
[03:51] <somerville32> /bin/sh: Syntax error: end of file unexpected
[03:51] <somerville32> make: *** [unpatch]  Error 2
[03:52] <theCore> somerville32: a shell script failed ...
[03:52] <Hobbsee> theCore: um...probably dont need to.  say which build deps you added, adn dropped
[03:52] <Hobbsee> but i dont think you need to talk about the versions
[03:52] <theCore> Hobbsee: ok
[04:08] <somerville32> imbrandon: Please e-mail me my new password.
[04:09] <somerville32> Welp... I'm going to go for a walk, do some housework, go for another walk, and then get something to eat and then hopefully this build will be done. :)
[04:19] <theCore> Hobbsee: I'm done (I think)
[04:19] <Hobbsee> theCore: yay :)
[04:20] <theCore> Hobbsee: I will upload, as soon it finishes building
[04:20] <Hobbsee> okay :)
[04:27] <theCore> Hobbsee: perfect!
[04:27] <Hobbsee> theCore: yay!
[04:28] <Hobbsee> theCore: now stop playing, and upload it to REVU dammit :P
[04:28] <theCore> hehe
[04:29] <theCore> it works fine on Edgy
[04:30] <Hobbsee> what'd you build it on?
[04:30] <Fujitsu> Which version is it?
[04:31] <Hobbsee> 0.3.0
[04:31] <theCore> % dput revu supertux_0.3.0-0ubuntu1_source.changes
[04:31] <theCore> done!
[04:32] <Hobbsee> :)
[04:49] <theCore> Hobbsee: http://revu.tauware.de/diff.py?upid1=3849&upid2=3852
[05:03] <Hobbsee> theCore: looks good
[05:04] <theCore> Hobbsee: I reincluded the Uploader field in another upload
[05:05] <Hobbsee> theCore: yep, i saw :)
[05:05] <bddebian> Heya Yagisan, long time no "see" :-)
[05:06] <Yagisan> G'day bddebian
[05:06] <Yagisan> bddebian, real life eating all my time
[05:06] <bddebian> I hear that
[05:07] <Hobbsee> hey Yagisan
[05:08] <Yagisan> G'day Hobbsee
[05:08] <Yagisan> spent yesterday in the Hospitial
[05:08] <Yagisan> looks like my wife will get reconstructive surgery next year
[05:09] <Yagisan> and for christmass my landlord has broken the lease and served me with a 60 day notice to vacate the property
[05:09] <Yagisan> at about the same time my wife is expoected to go in for surgery
[05:09] <Hobbsee> somerville32: stop twiddling :P
[05:10] <Yagisan> if you see even less of me, you'll know why
[05:10] <somerville32> Hobbsee: Buy me a new computer then :P
[05:10] <theCore> somerville32: hehe
[05:10] <Hobbsee> somerville32: ouch.  make imbrandon come back, or ask Lathiat for a shell there
[05:10] <somerville32> Oh goodie!
[05:10] <theCore> I had a Pentium 233 for years
[05:10] <somerville32> It built :D
[05:12] <bddebian> Yagisan: :-(
[05:12] <Yagisan> bddebian, that about sums it up
[05:12] <somerville32> Hobbsee, It isn't calculating the python dependencies
[05:13] <Hobbsee> somerville32: argh.  find someone who knows python and ask them :P
[05:13] <somerville32> Hobbsee: Is it possible that since I'm not compiling that I need to set the dependency on Python manually?
[05:14] <bddebian> heh
[05:14] <bddebian> Are there any merges left? :)
[05:15] <Hobbsee> somerville32: i've got no idea
[05:15] <Hobbsee> Fujitsu: what's so wrong with that?
[05:15] <somerville32> Hobbsee: If I upload, will thou advocate?
[05:15] <Fujitsu> Hobbsee, she mandated that I ask her over.
[05:16] <Hobbsee> somerville32: i'll probably look at it :P  i'm not good with python stuff
[05:16] <Hobbsee> theCore: supertux built
[05:16] <somerville32> Hobbsee, This is my first package and it has caused me so much grief :(
[05:16] <theCore> \o.
[05:16] <Hobbsee> :(
[05:16] <theCore> \o/
[05:16] <Fujitsu> theCore, who cut off your left arm? Was it Hobbsee?
[05:17] <theCore> Fujitsu: hehe
[05:17] <bddebian> haha
[05:17] <Hobbsee> wasnt me...
[05:17] <Fujitsu> Guilty!
[05:17] <somerville32> !revu | somerville32
[05:17] <ubotu> somerville32: REVU is a web-based tool to give people who have worked on Ubuntu packages a chance to "put their packages out there" for other people to look at and comment on in a structured manner. See https://wiki.ubuntu.com/MOTU/Packages/REVU
[05:17] <somerville32> Hmm..
[05:17] <somerville32> Whats the link for revu?
[05:18] <Hobbsee> revu.tauware.de
[05:18] <Hobbsee> dput revu *.changes
[05:18] <somerville32> I have revu set as my default
[05:18] <theCore> somerville32: don't to include the full source
[05:19] <somerville32> theCore: :S
[05:19] <theCore> debuild -S -sa
[05:19] <somerville32> I've uploaded this package 13 times :P
[05:19] <Hobbsee> -sa *will* include the full source
[05:19] <somerville32> I got it down pat :D
[05:19] <Hobbsee> :)
[05:19] <bddebian> Stop putting crap on REVU, there's already too much!! :-)
[05:19] <Hobbsee> haha
[05:19] <Hobbsee> bddebian: i'm about to archive an upload.  and you can review somerville32's package
[05:20] <theCore> Hobbsee: so, supertux is okay?
[05:20] <Hobbsee> theCore: yep
[05:20] <Hobbsee> Uploading via ftp supertux_0.3.0-0ubuntu1.dsc: done.
[05:20] <Hobbsee> Uploading via ftp supertux_0.3.0.orig.tar.gz:
[05:20] <Hobbsee> theCore: ^
[05:21] <theCore> my first package in the archives
[05:22] <Fujitsu> theCore, you need to wait for it to pass NEW, though :P
[05:22] <somerville32> http://revu.tauware.de/details.py?upid=3855
[05:22] <somerville32> :D
[05:24] <somerville32> Hobbsee, Are you going to look? :)
[05:24] <Hobbsee> somerville32: i'll let bddebian first
[05:24] <Hobbsee> the machine that i tend to look on is uploading
[05:24] <bddebian> Oh sure, like I'm such a "great" reviewer :-(
[05:25] <TheMuso> supertux is already there in feisty
[05:26] <Fujitsu> TheMuso, this is a new one.
[05:26] <TheMuso> oh ok
[05:26] <TheMuso> Why would that have to go through new then?
[05:27] <Hobbsee> Fujitsu: sorry, what has to wait for NEW?
 my first package in the archives
 theCore, you need to wait for it to pass NEW, though :P
[05:27] <Fujitsu> Hobbsee, yes, I failed to notice it was just an updated version.
[05:27] <Fujitsu> So, my NEW comment was invalid.
[05:28] <Hobbsee> Fujitsu: yeah, it's just an updated version.
[05:28] <somerville32> So, who is currently reviewing my package?
[05:29] <bddebian> I'm building bouml atm so I will when it's done
[05:29] <Fujitsu> somerville32, I am... Isn't there a significantly cleaner way of doing patches than the way you've done it?
[05:29] <somerville32> What do you mean?
[05:29] <somerville32> It is very clean
[05:29] <Hobbsee> Fujitsu: than with patch?
[05:29] <Fujitsu> Cleaner than all manually like that.
[05:30] <somerville32> It is recommended by the packaging guide
[05:30] <somerville32> And the one patch is super small
[05:30] <Fujitsu> The packaging guide is wildly mislead, then.
[05:31] <Hobbsee> well, just dumping one section in clean rule, instead of unpatch
[05:33] <somerville32> Fujitsu: Don't let that prevent you from advocating :P
[05:37] <theCore> Fujitsu: how patches should be done?
[05:37] <theCore> with dpatch?
[05:38] <Fujitsu> Yes, there's a much cleaner way to do it with dpatch, I'm sure.
[05:39] <Fujitsu> I think you should just need to include /usr/share/dpatch/dpatch.make, and that will handle the patch/unpatch targets.
[05:39] <Fujitsu> (you also need a debian/patches/00list)
[05:39] <somerville32> The current patch system is sufficient
[05:40] <somerville32> Infact, I wouldn't even see a problem just having the changes in the package diff since they are so small
[05:40] <Fujitsu> The current patch system is messy and took more work, though.
[05:40] <theCore> Fujitsu: hmm... I heard dpatch wasn't recommended for Ubuntu to keep the patch lists cleaner for Debian
[05:40] <somerville32> Fujitsu: Not really... just copy and paste :P
[05:40] <Hobbsee> Fujitsu: it's a standard way of doing things, it's not frowned upon
[05:40] <Hobbsee> Fujitsu: of course, for patching, cdbs rocks more
[05:41] <Fujitsu> Hobbsee, of course.
[05:41] <Fujitsu> 4 pings in a row, I must be wrong.
[05:41] <Hobbsee> (dpatch often doesnt let you merge with no conflicts)
[05:41] <Fujitsu> OK, the mess may stay :P
[05:41] <bddebian> heh
[05:41] <somerville32> Huzzah
[05:41] <Fujitsu> However, the dh_make `Add X here' comments want to be removed.
[05:41] <somerville32> Where? :P
[05:42] <Fujitsu> In debian/rules, there are a million of them.
[05:42] <somerville32> inline comments are important :P
[05:42] <Fujitsu> Of course.
[05:43] <somerville32> Ok, I removed the two that existeD :P
[05:43] <Hobbsee> somerville32: yes, people are picky :P
[05:43] <somerville32> Sorry, 3
[05:43] <somerville32> :]
[05:43] <somerville32> Do you think I can get this package uploaded tonight?
[05:44] <Fujitsu> I'm impressed, pyNeighborhood upstream actually put the required license headers in.
[05:44] <rmjb_> g'night guys
[05:44] <theCore> ok, I am off for tonight
[05:44] <rmjb_> g'day to Hobbsee
[05:44] <Hobbsee> hey rmjb_
[05:44] <rmjb_> and Fujitsu
[05:45] <Hobbsee> if i can remember what the password is...
[05:45] <theCore> see ya everyone
[05:45] <Fujitsu> Bye rmjb_.
[05:45] <Fujitsu> Bye theCore.
[05:45] <somerville32> This is so frustrating.
[05:45] <somerville32> Remind me never to package a python package ever again :P
[05:46] <somerville32> Fujitsu, Do you want me to upload new or do you have more comments?
[05:46] <Hobbsee> or not, as the password appears to have changed.
[05:52] <somerville32> Hobbsee, Code us a bot to review packages on revu all day long :]
[05:53] <bddebian> No shix
[05:54] <somerville32> http://revu.tauware.de/details.py?upid=3856
[05:55] <somerville32> bddebian, Hobbsee, Fujitsu: I uploaded new version. http://revu.tauware.de/details.py?upid=3856
[06:00] <somerville32> Are you guys actually reviewing my package or just giving me lip service?  :P
[06:01] <somerville32> And because I'm cool.
[06:01] <somerville32> : )
[06:02] <bddebian> E: pyneighborhood; No manual page for binary pyNeighborhood.
[06:02] <bddebian> W: pyneighborhood; The command /usr/bin/gksudo /usr/bin/pyneighborhood listed in a menu file does not exist.
[06:02] <bddebian> W: pyneighborhood; The menu file has subsection net, which is unknown.
[06:02] <bddebian> W: pyneighborhood; File /usr/share/doc/pyneighborhood/COPYING is considered to be an extra license file.
[06:02] <bddebian> W: pyneighborhood; File /usr/lib/pyenighborhood/config.py contained in /usr/lib of Architecture: all package.
[06:02] <somerville32> Where did you get that?
[06:03] <bddebian> Running linda/lintian on the resulting deb
[06:04] <somerville32> Whats with the last warning?
[06:05] <Fujitsu> somerville32, /usr/lib is architecture specific.
[06:05] <Fujitsu> /usr/share should be used otherwise.
[06:05] <bddebian> Aye
[06:06] <somerville32> ...
[06:06] <somerville32> Ok, so I'll have to patch the Makefile
[06:07] <somerville32> Whats with the second to last warning?
[06:07] <bddebian> I have to extract the package, give me a sec
[06:07] <Fujitsu> somerville32, COPYING should be a subset of what is in debian/copyright, so isn't necessary.
[06:07] <Hobbsee> bah, i knew i shouldnt have gone and gotten the bill
[06:07] <somerville32> So no need to install it?
[06:08] <Fujitsu> somerville32, correct.
[06:08] <Hobbsee> s/bill/mail
[06:08] <somerville32> Third to last warning?
[06:08] <Hobbsee> somerville32: sorry?
[06:08] <Fujitsu> somerville32, self explanatory, no?
[06:08] <somerville32> Yes.
[06:08] <somerville32> But... net doesn't exist?
[06:08] <bddebian> debian/menu: section="Apps/net"\
[06:09] <somerville32> Oh!
[06:09] <somerville32> capitalize n
[06:10] <somerville32> What about the first warning?
[06:10] <somerville32> Just don't provide full path?
[06:10] <bddebian> Dunno on that one :_(
[06:11] <bddebian> BTW, you should probably make your python depends >= 2.4
[06:11] <bddebian> build-deps that is.  You shouldn't need a python depends
[06:11] <bddebian>  {python:Depends} should do that for you
[06:11] <somerville32> But it doesn't
[06:11] <bddebian> Then something else is broken
[06:12] <somerville32> And that would be?
[06:14] <bddebian> Maybe you need to build-dep python-all-dev instead of python?
[06:14] <bddebian> Why are you using python-support instead of python-central btw?
[06:15] <somerville32> Ok
[06:15] <somerville32> changed to pycentral
[06:16] <bddebian> Shouldn't matter
[06:16] <bddebian> You call dh_pysupport but not dh_python?
[06:16] <somerville32> You don't call dh_python anymore
[06:16] <bddebian> Since when?
[06:16] <bddebian> http://www.debian.org/doc/packaging-manuals/python-policy/ap-packaging_tools.html#s-pysupport
[06:17] <somerville32> There is new python policy
[06:17] <somerville32> I read it there
[06:17] <somerville32> The man page says it
[06:17] <somerville32> and when you build it, it tells you
[06:17] <bddebian> Hmm, news to me so I'll shut up and go to bed now :-)
[06:18] <somerville32> This is my first package remember :P
[06:18] <Fujitsu> I thought dh_python was still valid...
[06:18] <bddebian> As could I.  I'm wrong alot it seems :-)
[06:18] <Fujitsu> (and correct)
[06:19] <somerville32> I'm going to bed too
[06:19] <somerville32> Maybe I should try an easier package first
[06:19] <bddebian> You're close man
[06:20] <somerville32> It is frustrating because it seems like no one can give me the answer
[06:20] <Fujitsu> Yeah, you're very nearly done.
[06:20] <somerville32> Yea! :)
[06:20] <somerville32> Maybe I need to ditch py_support
[06:20] <somerville32> and just use dh_python
[06:21] <bddebian> somerville32: Some of us aren't packaging "masters" either :-(
[06:21] <somerville32> hehe
[06:22] <somerville32> Hobbsee, You're the Kubuntu Community Manager?
[06:22] <TheMuso> somerville32: Afaik the python policy requires that you use either python-support or python-central
[06:22] <somerville32> Why aren't they working?
[06:23] <somerville32> It doesn't replace the {python:Depends}
[06:23] <bddebian> I think because you aren't build-depping python-dev?
[06:24] <somerville32> Hmm... I'll try it tomorrow
[06:24] <Hobbsee> somerville32: yes, why?
[06:24] <somerville32> Hobbsee, Do you work with Jono?
[06:24] <bddebian> Another note: if there is a debian/pycompat file, you must launch dh_python after dh_pysupport, but the recommended way is to remove that file.
[06:24] <Fujitsu> bddebian, isn't python-dev used for building binaries against python?
[06:25] <Hobbsee> somerville32: some, yes
[06:25] <bddebian> Fujitsu: I haven't looked that closely at what he is actually building :-)
[06:25] <bddebian> somerville32: Have you seen this page?  http://wiki.debian.org/DebianPython/NewPolicy
[06:25] <somerville32> Yup.
[06:25] <bddebian> Another note: if there is a debian/pycompat file, you must launch dh_python after dh_pysupport, but the recommended way is to remove that file.
[06:26] <bddebian> So you were correct
[06:26] <bddebian> This one too: http://wiki.debian.org/DebianPythonFAQ ?
[06:27] <somerville32> Not sure
[06:34] <bddebian> OK, my old arse has to get to bed.  Gnight gang
[06:34] <bddebian> Good luck somerville32
[06:34] <bddebian> Sorry I'm not more help :-(
[08:40] <enyc> bah...
[08:40] <enyc> the pbuilder-create rather screwed things up by setting the keyboard layout and cenfiguring an arkward screenfont!
[09:31] <dholbach> good morning
[09:34] <Hobbsee> hey dholbach!
[09:34] <dholbach> heya Hobbsee!
[09:34] <Hobbsee> dholbach: do you know if Riddell is on holidays, by chance?
[09:34] <dholbach> yes he is
[09:34] <Hobbsee> darn
[09:36] <dholbach> anything urgent you need of him?
[09:39] <Hobbsee> was just going to ask about the @kubuntu.org email addresses, and how to move them
[09:39] <Hobbsee> seeing as that's not done in the same way @ubuntu.com ones are, it seems
[09:40] <dholbach> oh right
[09:40] <dholbach> well you could ask in #launchpad if there are any plans to make it like in ubuntu
[09:41] <Hobbsee> they didnt know
[09:41] <Hobbsee> hte kubuntu.org addresses are pretty rare - so i wouldnt be surprised if riddell himself has set them up
[09:41] <dholbach> right :/
[09:42] <dholbach> but it'd be good, if launchpad could do that
[10:22] <\sh> moins
[10:22] <tsmithe> howdy
[11:20] <xerxas> Hi all
[11:20] <xerxas> dholbach,  ?
[11:20] <dholbach> hi xerxas
[11:20] <xerxas> Hi dholbach
[11:20] <xerxas> how are you ?
[11:22] <dholbach> fine fine - how are you?
[11:23] <xerxas> fine !
[11:23] <xerxas> dholbach,  what is the status with telepathy ?
[11:23] <xerxas> is there still a need for landell / tapioca-sharp ?
[11:23] <dholbach> xerxas: what do you want to know?
[11:23] <dholbach> yeah sure
[11:23] <xerxas> ok
[11:23] <dholbach> it'd be great to have it
[11:23] <dholbach> the guys from #tapioca-voip are doing great work
[11:24] <dholbach> i just don't want to dive into mono packaging and leave it somebody else
[11:26] <xerxas> ok
[11:31] <zorglu_> ultra naive question: i would like to explicitly state that a package depends on another, is that in the control file ?
[11:31] <zorglu_> like adding my package name in the Depends: field ?
[11:32] <Hobbsee> yes.  better to build depend on hte -dev version of your package, though
[11:32] <zorglu_> Hobbsee: why -dev is better ?
[11:34] <Hobbsee> zorglu_: so that it gets included when ./configuring, the libraries tend to change names, etc
[11:34] <Hobbsee> depends on the package
[11:34] <zorglu_> ok thanks
[11:48] <gpocentek> is it OK if I archive old uploads on REVU
[11:48] <gpocentek> ?
[11:48] <gpocentek> a lot of packages are commented, and no new package has been uploaded since september/october
[11:49] <gpocentek> s/a lot of/some
[12:30] <zorglu_> q. what is the policy when installing a daemon with a /etc/init.d script ? should i start it on install and stop it on deinstall ?
[12:30] <zorglu_> maybe a suggestion on a package known to be doing the good thing, which i could copy :)
[12:32] <geser> zorglu_: grep for invoke-rc.d in /var/lib/dpkg/info
[12:34] <zorglu_> geser: thanks :)
[12:40] <\sh> sombody interested into reviewing? a nice package for ubuntu servers...sitar - http://revu.tauware.de/details.py?upid=3857
[12:41] <Hobbsee> \sh:
[12:41] <Hobbsee> \sh: it being you who made it, it should be fine...
[12:42] <\sh> Hobbsee: I have to follow the rules :)
[12:42] <Hobbsee> \sh: true.  and you're missing a versioned dep on debhelper - lintian/linda are complaining
[12:44] <\sh> you see ;)
[12:45] <Hobbsee> \sh: er, you've missed a lot...
[12:45] <\sh> hmmm...jepp it was the stupid wrong package I've uploaded
[12:46] <Hobbsee> \sh: there you go.
[12:46] <Hobbsee> what, you intended to upload something else?
[12:47] <\sh> no...I have a package with descriptions etc. I uploaded from the wrong place :(
[12:47] <Hobbsee> ah
[12:48] <Hobbsee> hehe
[12:48] <Hobbsee> i thought the lack of descriptions was good
[12:48] <Hobbsee> you're in what, core?
[12:48] <dholbach> hum, wasn't there a package in ubuntu/debian already called sitar? \sh: what is sitar?
[12:49] <\sh> system information at runtime
[12:49] <\sh> a retrival package...I didn't find it on p.d.o
[12:50] <\sh> http://sitar.berlios.de
[12:51] <dholbach> ok
[12:52] <\sh> hmm..can I just overwrite 0ubuntu1 version with a new src upload on revu?
[12:52] <\sh> or do I need to increase the version number?
[12:54] <Hobbsee> \sh: i think you can overwrite it
[12:54] <Hobbsee> in fact, i'm sur eyou can
[12:56] <\sh> lets see
[01:04] <\sh> Hobbsee:5 mins and you can check again ;)
[01:05] <\sh> food
[01:05] <Hobbsee> :)
[01:15] <zorglu_> q. im makeing a package which include a nss library, so /etc/nssswitch.conf has to be modified, any advice on how to do that ?
[01:15] <zorglu_> an horribly ugly script can add and remove the line, but it will be ugly and error prone...
[01:16] <zorglu_> i looked at libnss-mdns package and i dont see how it add itself in /etc/nssswitch.conf
[01:16] <zorglu_> and im wondering if the /etc/nsswitch.conf doesnt come with mdns in it by default :0
[01:17] <zorglu_> hint ? :)
[01:21] <lionel> zorglu_: for the libnss- packages I use, you have to edti manualy /etc/nsswitch.conf
[01:22] <zorglu_> lionel: hmm uncool :)
[01:22] <lionel> not sure it is a good idea to add them automatically (think if the libnss is not well configured)
[01:22] <lionel> libnss-ldap displays a debconf warning saying to manually edit /etc/nsswitch.conf
[01:23] <zorglu_> ok 2 things: 1. it makes it much harder to install 2. mdns doesnt requires to manually edit /etc/nsswitch.conf
[01:23] <zorglu_> imagine a plain user doing it, not a geek, this is a very hard stuff
[01:24] <lionel> mdns does not have any configuration I think (never used in fact). It is based on Windows broadcast I think
[01:24] <lionel> zorglu_: I agree, I just tell you how it is on other packages :)
[01:24] <zorglu_> :)
[01:25] <zorglu_> well if i have the choise between automatic installation (even ugly) or manual installation, i clearly go on manual installation
[01:26] <zorglu_> after that how to provide a automatic installation which is the least ugly
[01:26] <zorglu_> maybe i should do a script which is automodify the /etc/nsswitch.conf automatically and then see when to call it
[01:27] <zorglu_> pffffffff my brain is off
[01:27] <zorglu_> lionel: thanks for your help :)
[01:28] <lionel> :)
[01:29] <StevenK> zorglu_: You can't modify /etc/nsswiitch.conf automatically.
[01:30] <zorglu_> StevenK: why not ?
[01:30] <StevenK> zorglu_: It's owned by base-files, and Thou Shalt Not Play With Another Packages Conffiles.
[01:30] <zorglu_> ?
[01:31] <zorglu_> StevenK: this file is modifiable by the user
[01:31] <zorglu_> StevenK: what is the difference ?
[01:31] <StevenK> Because then the user knows it has been done.
[01:31] <StevenK> And you can only play with it if you're base-files.
[01:32] <zorglu_> StevenK: sorry i dont understand
[01:32] <StevenK> zorglu_: That's okay, I'm probably not explaining it very well.
[01:32] <zorglu_> StevenK: 1. the user can freely modify the file, so it is modifiable
[01:32] <StevenK> There is a distinction made between the user modifying a file, and a package doing the same thing.
[01:32] <zorglu_> 2. if the point is making sure that the user know about the modification of nsswitch.conf, i have no trouble about this :)
[01:33] <zorglu_> i can put the biggest banner you have ever seen :)
[01:33] <zorglu_> StevenK: definitly a huge disctinction. one is very hard for the user, the other is very easy :)
[01:33] <StevenK> Secondly, it is a Debian Policy voilation (which we still have to respect in Ubuntu) to modify a conffile belonging to another package.
[01:34] <zorglu_> StevenK: i dont understand
[01:34] <zorglu_> the file is modifiable by the user
[01:34] <azeem> zorglu_: if "the user" == "root", every file is modifiable
[01:34] <StevenK> Which is entirely seperate to what I'm discussing.
[01:34] <zorglu_> providing a script to help the user modifying this file is easier for the users
[01:34] <azeem> it doesn't mean your random mp3 player should modify libc.so.6 for better performance
[01:35] <zorglu_> azeem: ok lets keep on topic :)
[01:35] <zorglu_> i want to make it easy for the user to install the stuff <- MY GOAL
[01:35] <azeem> zorglu_: if you ship a script the admin can execute at their own descretion, that would be fine I guess
[01:35] <zorglu_> to screw up the system <- NOT MY GOAL :)
[01:35] <azeem> but not if that script is automatically run by another package
[01:36] <zorglu_> azeem: ahhhhhhh ok :)
[01:36] <azeem> which could be deduced from your statement above (but I didn't read scrollback thouroughly)
[01:36] <zorglu_> azeem: now i understand :) the point is you dont want the script to be launch in the postinst or something
[01:36] <azeem> yes
[01:37] <azeem> I don't even know what the underlying problem is, but even putting up a note in the face of the admin saying "run this to get foo modified" would be bad, probably debconf abuse
[01:37] <azeem> having it in README.Debian (or maybe NEWS.Debian) would be fine
[01:37] <azeem> well, that's my opinion, anyway
[01:38] <zorglu_> ok i think i got the idea :)
[01:39] <zorglu_> 1. it is not advized to modify other files package during the install of a package
[01:39] <azeem> s/not advized/verboten/
[01:39] <zorglu_> 2. the user has to know about the modification
[01:40] <StevenK> \sh: Can I ste^Wborrow the clanlib merge off you?
[01:40] <zorglu_> 3. it is ok to provide something to ease the modification if the user explictly say yes
[01:41] <zorglu_> now i have to find out if i modified /etc/nsswitch.conf myself for libnss-mdns :)
[01:41] <zorglu_> thanks all :)
[02:20] <\sh> back
[02:21] <Hobbsee> :)
[02:23] <\sh> the lintian errors I  can forget...newer standards version etc.
[02:23] <Hobbsee> true
[02:40] <giskard> hello *
[02:42] <cypher1> geser, are you there ?
[02:43] <\sh> my fellow motu...I wish you all a merry christmas and a happy new year...:)
[02:44] <geser> cypher1: yes
[02:44] <cypher1> geser, thanks for catching the doc++ bug
[02:45] <cypher1> geser, can i convert the same bug to a sync request ?
[02:45] <cypher1> geser, bug 76479
[02:45] <Ubugtu> Malone bug 76479 in doc++ "Merge doc++ 3.4.10-3.4 from Debian" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76479
[02:45] <geser> sure
[02:46] <geser> just retitle the bug and add the missing info for a sync request
[02:46] <cypher1> geser, that had been my first work in motu :(
[02:55] <cypher1> geser, done :)
[02:56] <zorglu_> q. is there a cmdline command to get the default web browser of the user? once again, i take any hint/pointer etc... to get an answer :)
[02:58] <geser> cypher1: see https://wiki.ubuntu.com/DeveloperResources for how sync request should look like
[02:58] <geser> cypher1: you should mention that it should be synced from "Debian unstable (main)"
[02:59] <geser> and copy of the new debian/changelog entries since the last ubuntu version
[03:16] <cypher1> geser, thanks.. i have changed.. can you please have a look at it before i subscribe ubuntu-archive to it
[03:19] <geser> cypher1: I've ACKed it and subscribed ubuntu-archive
[03:19] <geser> DeleoperResources is missing that you need an ACK from a MOTU (if you aren't a MOTU)
[03:20] <geser> you usually subscribe ubuntu-universe-sponsors for a sync request
[03:20] <geser> a MOTU ACKs it and subscribes ubuntu-archive
[03:20] <cypher1> geser, thanks a lot.. do i have to unsubscribe "ubuntu universe sponsors" ?
[03:20] <cypher1> geser, sorry did not see your message
[03:22] <geser> cypher1: leave u-u-s subscribed
[03:38] <bddebian> Heya gang
[03:40] <cypher1> are we in UpstreamVersionFreeze ?
[03:40] <ivoks> i doubt that :)
[03:41] <lionel> cypher1: https://wiki.ubuntu.com/FeistyReleaseSchedule
[03:41] <lionel> UVF is on the 8th of February
[03:53] <cypher1> lionel, thanks
[03:56] <xerxas> how can I tell in a debian/rules with /usr/share/cdbs/1/class/autotools.mk to not run ./configure but rather autotools.sh ?
[03:56] <xerxas> (I'm using cdbs)
[03:56] <xerxas> there's seems to be a NOCONFIGURE=1 variable that I can set, but don't know where
[03:56] <xerxas> and how
[03:57] <azeem> https://perso.duckcorp.org/duck/cdbs-doc/cdbs-doc.xhtml
[03:57] <azeem> should be explained there I think
[03:58] <azeem> xerxas: do you want to run autogen.sh first, or can you not run configure after autogen.sh?
[03:58] <xerxas> I want to run autogen.sh first
[03:58] <xerxas> it creates a configure
[03:59] <azeem> then probably makebuilddir/foo:: is the right target
[03:59] <azeem> dunno
[03:59] <xerxas> ok
[03:59] <xerxas>  what is /foo ?
[03:59] <xerxas> the name of the binary package ?
[04:00] <azeem> yes
[04:00] <xerxas> it's the target to run ./autogen.sh or to set NOCONFIGURE=1 ?
[04:00] <azeem> the former
[04:00] <xerxas> ok
[04:00] <xerxas> the former, is the 1st one ? so autogen.sh ?
[04:01] <azeem> yes
[04:01] <azeem> alternatively, you can run autogen.sh before and put the changes it makes as a patch into debian/patches
[04:03] <xerxas> ahh , yes, someone already told me that
[04:03] <xerxas> ./configure is supposed to generate the same on all systems
[04:03] <xerxas> because it's a distribution
[04:03] <xerxas> but I need to satisfy my dependencies
[04:06] <zul> effing sweet..
[04:06] <zul> chuck@chucktest:~$ uname -a
[04:06] <zul> Linux chucktest 2.6.19-xen #1 SMP Fri Dec 22 09:59:43 EST 2006 i686 GNU/Linux
[04:06] <xerxas> azeem,  thanks you very much
[04:06] <xerxas> I'm sticking to run NOCONFIGURE=1 ./autogen.sh in makebuilddir/foo
[04:07] <azeem> xerxas: does autogen.sh run configure itself?
[04:08] <xerxas> don't think so
[04:08] <xerxas> it generates it
[04:08] <xerxas> maybe my target should be 2 lines ?
[04:08] <xerxas> humm
[04:08] <xerxas> seems it runs it
[04:08] <xerxas> sorry
[04:18] <neutrinomass> When a package needs rebuilding to resolve the deps, what can I do as a non-MOTU? (add an entry to the changelog and attach a debdiff? )
[04:19] <zul> yes
[04:20] <neutrinomass> say, for example, bug 60801 :-)
[04:20] <Ubugtu> Malone bug 60801 in testdisk "Testdisk depends upon libntfs8 but it isn't present. (AMD64)" [Medium,Confirmed]  http://launchpad.net/bugs/60801
[04:20] <dholbach> siretart: want me to approve your mail to ubuntu-motu@?
[04:21] <siretart> dholbach: oh, it needs approval? I've seen that we should mail things we upload to ubuntu-motu during the revu days
[04:21] <siretart> dholbach: is the mail ok at all?
[04:22] <dholbach> I'll auto-accept mails from<EMAIL_ADDRESS>now
[04:22] <dholbach> maybe you sent from @tauware.de most of the other time
[04:22] <sistpoty> hi folks
[04:23] <siretart> dholbach: right. thanks
[04:23] <siretart> huhu sistpoty
[04:23] <sistpoty> hi siretart
[04:23] <dholbach> heya sistpoty
[04:23] <sistpoty> hi dholbach
[04:23] <sistpoty> woohooo! great!
[04:23] <sistpoty> siretart: just saw your comments about bug #76861
[04:23] <Ubugtu> Malone bug 76861 in spampd "[SRU]  spampd 2.30" [Undecided,In progress]  http://launchpad.net/bugs/76861
[04:23] <siretart> sistpoty: for the future, it is 'just' creating a symlink in /usr/local/bin, and issuing 'pbuilder-feisty create'
[04:24] <sistpoty> cool
[04:24] <siretart> yes, since bash is essential, we don't need an explicit dependency
[04:24] <sistpoty> siretart: actually I told marc to add the dep on bash (I'm mentoring him)
[04:24] <siretart> oh
[04:24] <siretart> :)
[04:24] <siretart> I don't see the necessity. bash is essential, we need it in any case
[04:25] <sistpoty> siretart: debian policy 3.5 says otherwise... only essential deps can be omitted
[04:25] <siretart> bash IS essential
[04:25] <sistpoty> it is?
[04:25] <siretart> look at 'apt-cache show bash'
[04:26] <sistpoty> nice... didn't see this :)
[04:28] <bddebian> Heya sistpoty, siretart, dholbach
[04:29] <sistpoty> hi bddebian
[04:29] <siretart> huhu bddebian!!
[04:30] <siretart> sistpoty: oh, I see that I need to copy a new apt.config as well. hmm
[04:31] <neutrinomass> is kdesu in kdebase or kdebase-bin ?
[04:33] <dholbach> hiya bddebian
[04:49] <siretart> hm. has anyone seen raphink lately?
[04:50] <sistpoty> not really...
[04:52] <siretart> ah, found it. let's test revu-build
[04:53] <sistpoty> lucas: may I grab osgcal merge from you?
[04:57] <siretart> lucas: congrats to dam approval, btw :)
[04:57] <lucas> :-)
[04:57] <lucas> siretart: yes, go ahead
[04:57] <lucas> sistpoty:
[04:57] <sistpoty> lucas: ok, thx. (I'm out of merges *g*)
[04:58] <siretart> okay. revu-build works again now!
[04:58] <siretart> builds in a pbuilder-feisty
[04:58] <geser> sistpoty: wasn't the last osgcal uploaded by lfittl?
[04:59] <siretart> need to go to supermarket for the holydays now, bbl - have fun!
[04:59] <sistpoty> geser: damn, righto... I'm mixing up nicks again *g*
[04:59] <sistpoty> lfittl: may I merge osgcal?
[05:01] <Adri2000> anyone knows why this package https://launchpad.net/distros/ubuntu/+source/gnutls12 has been removed from feisty?
[05:02] <geser> I assume everyone should use libgnutls13
[05:03] <Adri2000> yep, that's it
[05:03] <Adri2000> gnutls12 is also not anymore in debian
[05:08] <sistpoty> why, just why do ppl. do huge commits directly before they go into christmas holidays? aaargh!
[05:08] <Adri2000> when uploading a package for a rebuild, the version should be -Xbuild1 or -Xubuntu1?
[05:08] <sistpoty> Adri2000: -Xbuild1 in case it doesn't have a ubuntu suffix yet
[05:09] <Adri2000> ok
[05:09] <Adri2000> so that it will be automatically synced for the next release I believe
[05:09] <sistpoty> Adri2000: that's the plan ;)
[05:14] <geser> Adri2000: on which package are working currently?
[05:15] <ScottK> I have an update to pyspf (the version in both Debian and Ubuntu is two years behind upstream) update that I got some good comments on earlier in the week (thanks Adri2000 and whoever<EMAIL_ADDRESS>is).  This is my first Debian package and I was hoping someone could take a look at the revised package and see what else I need to do to get it in shape.  Thanks.  http://revu.tauware.de/details.py?upid=3838
[05:15] <Adri2000> geser: I only added a comment at bug #76882
[05:15] <Ubugtu> Malone bug 76882 in wput "[UNMETDEPS]  Failed deps, feisty" [Medium,Confirmed]  http://launchpad.net/bugs/76882
[05:16] <sistpoty> ScottK: will do. btw<EMAIL_ADDRESS>[05:16] <geser> Adri2000: already uploaded with -1build1
[05:18] <ScottK> Ah.  Thanks.  I appreciate your comments earlier in the week (now that I know who to thank).
[05:18] <Adri2000> geser: ok, you are going to close the bug?
[05:19] <geser> yes
[05:19] <Adri2000> cool
[05:20] <xerxas> dholbach,  can you have a look at that :
[05:20] <xerxas> https://bugs.launchpad.net/people/telepathy/+branch/tapioca-sharp/ubuntu
[05:21] <xerxas> I think I'm not too far from it being packaged
[05:21] <dholbach> xerxas: you'd better ask ajmitch, bhale or slomo
[05:21] <xerxas> ok
[05:21] <dholbach> xerxas: I'm no mono packaging pro
[05:21] <xerxas> anyway it doesn't work for now
[05:21] <xerxas> it want to compile dbus-sharp I think so
[05:28] <sistpoty> ScottK: python-spf is still not quite right: type99.py doesn't have a shebang line and the shebang line of spf-query is missing a "!"
[05:28] <sistpoty> ScottK: maybe you should just install the resulting package and see if you can execute each script that's somewhere in path as is?
[05:28] <ScottK> Urgh.
[05:29] <ScottK> OK.
[05:29] <ScottK> Give me a minute and I'll try again.
[05:29] <ScottK> Is there anything else.  There are a few Lintian warnings, but I don't know enough to know if they are significant.
[05:31] <sistpoty> ScottK: nothing really serious... maybe you could add the version to the python-support build dependency
[05:31] <sistpoty> (>= 0.3)
[05:31] <sistpoty> ScottK: apart from that, I didn't see other biggies
[05:32] <ScottK> I'll add that too.
[05:32] <ScottK> THanks.
[05:32] <sistpoty> np
[05:32] <ScottK> Some days it seems copy/paste is to hard for me.
[05:33] <sistpoty> hehe
[05:37] <Toadstool> hi everybody
[05:38] <geser> is someone working on merging sword?
[05:39] <joejaxx> /usr/bin/ld: cannot find -lXp
[05:39] <joejaxx> anyone recognize that?
[05:39] <joejaxx> geser: sword?
[05:39] <azeem> joejaxx: check for -lXp in /usr/lib/*.la, I'd say
[05:41] <joejaxx> libXp is there
[05:43] <joejaxx> ahh
[05:43] <joejaxx> silly me
[05:47] <joejaxx> azeem: thanks :)
[05:51] <siretart> is<EMAIL_ADDRESS>around?
[06:06] <ScottK> For sistpoty or anyone else who knows about packaging Python scripts...  I put the shebang back into type99.py and spf-query.py as above.  They are both executable (I installed the resulting package as suggested).  The problem is that now I get a Lintian error (same error for both files): E: python-spf: python-script-but-no-python-dep ./usr/bin/type99.py.  If that were really true, I don't think calling the scripts direct
[06:06] <ScottK> Do I need to worry about it?  Suggestions on how I should fix it?
[06:11] <sistpoty> ScottK: http://www.debian.org/doc/packaging-manuals/python-policy/ should give some hints
[06:11] <sistpoty> ScottK: I'm just taking a look at iit
[06:11] <sistpoty> -i
[06:11] <siretart> are sync requests processed lately?
[06:12] <sistpoty> siretart: usually done in batches, but the last batch was some time ago iirc
[06:13] <siretart> okay
[06:14] <siretart> wow: https://bugs.launchpad.net/people/ubuntu-archive/+subscribedbugs shows 97 bugs
[06:15] <ScottK> sistpoty - I am looking there, but have not found anything yet
[06:23] <ScottK> FIgured it out.  It appears the way I was depending on Python in the control file was wrong.
[06:37] <ScottK> sistpoty - Thanks again for the look.  Revised package uploaded. http://revu.tauware.de/details.py?upid=3862 I'd appreciate another look.
[06:40] <Toadstool> hmm... quick question, does it matter if there are unsupported archs (like kfreebsd-i386) in the Arch: field of a package I want to merge?
[06:41] <sistpoty> Toadstool: no, doesn't matter... just think from the buildd POV: if myarch then do something else ignore
[06:42] <Toadstool> oh right... I feel stupid now :)
[06:42] <Toadstool> thanks sistpoty
[06:42] <sistpoty> np
[06:44] <nemo79> hello sistpoty
[06:44] <sistpoty> hi nemo79
[06:44] <nemo79> thanks for all infos.
[06:44] <sistpoty> you're welcome
[06:45] <nemo79> I corrected my package to include the modifs asked by you and siretart
[06:47] <sistpoty> nemo79: yay, cool. thx
[06:48] <nemo79> sistpoty: So I have now to wait for a 3th ack, right ?
[06:49] <sistpoty> nemo79: right
[06:49] <cypher1> what is the use of "Step Seven" mentioned at https://wiki.ubuntu.com/MOTU/School/Merging-and-Syncing
[06:50] <siretart> sistpoty: didn't we lower the requirements to 2 acks?
[06:50] <sistpoty> siretart: did we do that?
[06:50] <siretart> oh. hm.
[06:50] <siretart> if in doubt, then not ;)
[06:51] <siretart> I thought so :)
[06:51] <sistpoty> siretart: can't remember... at least the wiki page would be outdated then ;)
[06:51] <sistpoty> ScottK: you shouldn't hardcode a dependency to python, but rather use ${python:Depends} for this
[06:52] <ScottK> OK.  That's what I had before and was getting the error.
[06:52] <sistpoty> ScottK: however I had some trouble to get it to work myself, I'll look exactly what I changed so that it spit out python, k?
[06:52] <ScottK> Yes.  Please.
[06:57] <ScottK> Looking at http://www.debian.org/doc/packaging-manuals/python-policy/ch-module_packages.html#s-dependencies gave me the idea I should hard code it to python.
[07:00] <sistpoty> ScottK: I guess it would result in the same thing... but actually python-central/python-support are there to make this easier... *g*
[07:02] <ScottK> This is my first try at this.  I'd hate to see harder.
[07:02] <ScottK> sistpoty - Any suggestions on where to go from here?
[07:03] <sistpoty> ScottK: this is strange... I cannot make dh_pysupport *not* create the python-dependency any longer *g*
[07:04] <sistpoty> ScottK: from you latest revu upload, I only remove python from the depends and added ${python:Depends}
[07:06] <sistpoty> ScottK: but if I get it correctly, you shouldn't build-depend on python-all-dev but rather on python, since there doesn't get anything compiled during the build process
[07:14] <cypher1> UbuntuStats ?? new bot ?
[07:14] <jdong> oh bow
[07:14] <zorglu_> NOTE: Bash, as packaged for Debian, does not support using the /dev/tcp and /dev/udp files <- from bash man page. and it does not work on ubuntu either, any idea as of why ?
[07:14] <jdong> boy*
[07:15] <jdong> zorglu_<EMAIL_ADDRESS>[07:15] <jdong> > > This has been discussed several times [1] [2] , and the outcome was every time
[07:15] <jdong> > > that this should not be a feature of the shell, but of more specialized
[07:15] <jdong> > > tools like nc. Use those or recompile your bash.
[07:16] <zorglu_> thanks :)
[07:16] <gouki> cypher1: Yes. It will collect logs and parse them to HTML, to create statistics
[07:16] <jdong> I won't say I agree with the reasoning though :)
[07:16] <zorglu_> their argument is valid about 'it should not be in bash'. unfortunatly it assume that 'there are other tools' :)
[07:16] <zorglu_> and nc is not exactly known to work :)
[07:20] <tsmithe> howdy
[07:22] <tsmithe> is packaging libraries any different to normal applications?
[07:23] <zorglu_> i dunno myself but i know the http://wiki.ubuntu.com/MOTU/Documentation contains a link dedicated to packaging library
[07:23] <tsmithe> cool
[07:23] <zorglu_> http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html
[07:23] <zorglu_> this one to be more precise :)
[07:26] <tsmithe> danke schoen
[07:26] <cypher1> Can anyone please review bug 76897 ?
[07:26] <Ubugtu> Malone bug 76897 in firestarter "[Merge Request]  Merge firestarter 1.0.3-1.3 from Debian" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76897
[07:28] <ScottK> sistpoty - Thanks.  I'll have a look at those changes and try again.
[07:28] <sistpoty> cypher1: please list all remaining ubuntu changes in the topmost changelog entry
[07:29] <giskard> keescook, your upload failed! (aolserver)
[07:29] <keescook> giskard: yeah... typo.  :(
[07:29] <cypher1> sistpoty, remaining ubuntu changes == ubuntu changes on top of the new Debian version ?
[07:29] <sistpoty> cypher1: yes
[07:29] <sistpoty> cypher1: am I wrong, or is this package merged already?
[07:30] <sistpoty> cypher1: I am wrong ;)
[07:30] <cypher1> sistpoty, :)
[07:31] <sistpoty> all those funny numbers ;)
[07:31] <tsmithe> and also...
[07:31] <tsmithe> seeing as "IT'S THE REVU DAYS"
[07:32] <luisbg> tsmithe... can I pm you?
[07:32] <tsmithe> could someone revu asoundconf-gtk
[07:32] <tsmithe> sure thing luisbg
[07:32] <cypher1> sistpoty, done.. can you please look at it ? is that ok ?
[07:32] <sistpoty> cypher1: will take a look
[07:34] <sistpoty> Czessi: for klear: it won't hit the -changes list, unless it's through new FWIW. however it's strange that you didn't get an "this package is new..." mail
[07:34] <sistpoty> Czessi: but there it is: https://launchpad.net/distros/ubuntu/feisty/+queue?queue_state=0&queue_text=klear ;)
[07:35] <sistpoty> cypher1: what did you do now actually?
[07:36] <cypher1> sistpoty, copied the changes retained from the changelog
[07:37] <cypher1> sistpoty, copied the changes retained in ubuntu from the changelog
[07:37] <sistpoty> cypher1: you'll need to list these in your changelog entry, not in the bug report ;)
[07:37] <sistpoty> cypher1: also please don't copy/paste the entries as is, but rather look what has been done
[07:38] <cypher1> sistpoty, sorry then i did not understood what you had requested by "please list all remaining ubuntu changes in the topmost changelog entry"
[07:38] <sistpoty> hehe
[07:39] <cypher1> sistpoty, sorry now i understood
[07:39] <cypher1> sistpoty, you want me to change debian/changelog right :)
[07:39] <sistpoty> cypher1: debian/changelog contains the changes that have been changed in the package. change it :)
[07:40] <cypher1> sistpoty, on it
[07:46] <gandalfn> hello, I had a problem, I lost my WIFI connection on upload which break package. I tried to make a dcut but I saw that this one afterwards doesnsupported by NOT RE-EXAMINED. There is to you it another means to purge and push back?
[07:46] <gandalfn> oups sorry ! hello, I had a problem, I lost my WIFI connection on upload which break package. I tried to make a dcut but I saw that this one afterwards doesn't supported by REVU. There is to you it another means to purge and push back?
[07:47] <sistpoty> gandalfn: revu doesn't support dcut...
[07:47] <sistpoty> gandalfn: however if you tell me which package it was, I'll remove that
[07:48] <gandalfn> i know now , sorry :/ thanks
[07:48] <gandalfn> it's compiz
[07:49] <sistpoty> gandalfn: it's gone
[07:49] <gandalfn> thanks very much
[07:49] <sistpoty> np
[07:51] <sistpoty> later folks
[07:51] <bddebian> Later sistpoty
[07:53] <cypher1> sistpoty has left
[07:54] <cypher1> he was reviewing bug 76897
[07:54] <Ubugtu> Malone bug 76897 in firestarter "[Merge Request]  Merge firestarter 1.0.3-1.3 from Debian" [Undecided,Unconfirmed]  http://launchpad.net/bugs/76897
[07:54] <cypher1> will it be possible for anyone else to review and tell me whether i have done properly ?
[08:07] <enyc> hrrm
[08:07] <enyc> thats odd
[08:08] <enyc> edgy version of qpsmtpd creates /var/run/qpsmtpd user qpsmtpd group adm
[08:08] <enyc> wonder why that is
[08:16] <geser> cypher1: not all former merger mentioned the remaining changes in their changelog entry
[08:18] <cypher1> geser, but those were either rebuilds or another merge, do i have to mention those ?
[08:18] <geser> not the merges but the other changes
[08:19] <cypher1> geser, i did mention the changes done through 1.0.3-1.2ubuntu2, am i missing any other
[08:20] <geser> yes the changes in 1.0.3-1.2ubuntu1 which aren't fortunately mentioned
[08:21] <geser> e.g the addtional patches (11_desktop_file 12_firestarter_transparent_icon 13_browser_nonroot)
[08:21] <geser> or * gksu -> gksudo from 1.0.1-1ubuntu1
[08:22] <geser> simply go through the debdiff and identify the changelog entries for each remaining change in the debdiff and add it to your changelog entry
[08:22] <cypher1> geser, but that is not mentioned in the 1.0.3-1.2ubuntu1 merge either
[08:23] <geser> yes, it was forgotten by the merger
[08:23] <cypher1> geser, ok i will make the changes..
[08:23] <cypher1> geser, hold on
[08:23] <geser> this makes it easier for the next merge
[08:28] <geser> that way the next merges has only to look at your changelog entry instead of the whole changelog
[08:34] <cypher1> geser, thanks.. i have modified changelog.. can you please look at it ?
[08:39] <geser> cypher1: much better now
[08:39] <geser> cypher1: "Rebuild without libhowl0" was a no change rebuild -> doesn't need to be mentioned in your changelog
[08:40] <geser> and the gksu -> gksudo change was undone later, so doesn't need to be added to the changelog
[08:40] <cypher1> geser, i thought they removed some Makefile or maybe code to rebuild without libhowl0
[08:41] <geser> often rebuilds don't have any changes, the new libs are picked up automatically
[08:41] <cypher1> geser, ok will do the changes now...
[08:42] <geser> and you only need to mention those changes that are still there
[08:42] <geser> it happens that some of the ubuntu changes are picked up by debian
[08:49] <cypher1> geser, changed.. can you please look at it now ?
[08:49] <cypher1> geser, i do not see any ubuntu changes being picked by debian from the descriptions in changelog..
[08:51] <geser> this was more generic and may not apply in this case
[08:52] <cypher1> geser, ok :)
[08:53] <geser> looks ok now
[08:53] <cypher1> geser, thanks
[08:54] <cypher1> geser, what should be my next step now ?
[08:54] <geser> I will clean up that gksu->gksudo->gksu patching and upload it
[08:55] <cypher1> geser, cleanup in the code ?
[08:57] <geser> a little bit: 01_use_gksu.dpatch is changed to use gksudo instead of gksu and 11_desktop_file.dpatch changes it back again from gksudo to gksu
[08:58] <zorglu_> outof the blue, there is kdesu and gksudo... the naming is not very consistent..
[08:59] <zorglu_> kdesu/gtksu or kdesudo/gtksudo would seems more consistent. out of the blue stuff
[09:30] <geser> cypher1: firestarter uploaded
[09:31] <cypher1> geser, thanks!! :)
[09:35] <cypher1> geser, how can i see it ? (packages.ubuntu.com does not show it, merges.ubuntu.com still says it is outstanding and i am on edgy )
[09:36] <geser> it should appear soon on https://launchpad.net/distros/ubuntu/+source/firestarter/
[09:37] <geser> it takes some hours till it is on the archive
[09:37] <geser> and merges.u.c is updated only daily(?)
[09:37] <geser> cypher1: you can also check the feisty-changes ML
[09:37] <geser> https://lists.ubuntu.com/archives/feisty-changes/2006-December/002784.html
[09:39] <cypher1> geser, thank you!
[09:39] <cypher1> geser, got to go 2:10 am.. catch you later
[09:55] <EvanCarroll> I just had an idea, and I'm willing to do all the work if I can get a thumbs up
[09:56] <EvanCarroll> I'm wanting to package all of the Abandon ware into multiverse, prefixing every game with abandon- , and having a big mega package abandon-games. or the like
[09:56] <EvanCarroll> abandonware games*
[10:04] <dholbach> merry christmas everybody
[10:04] <dholbach> and a happy new year!
[10:05] <azeem> guten Rutsch!
[10:05] <dholbach> Dir auch! :-)
[10:06] <tsmithe> frohe Weihnachten
[10:06] <tsmithe> ;)
[10:06] <dholbach> tsmithe: Dir auch! :-)
[10:06] <tsmithe> danke!
[10:08] <siretart> Frohes Fest! :)
[10:08] <siretart> ah, too late ;)
[10:10] <tsmithe> ;)
[10:10] <sinisterguy> for the Depends line of a package in the control file, what does ${shlibs:Depends} and ${misc:Depends} mean?
[10:15] <ScottK> I've taken another shot at my pyspf package update.  REVU would be gratly appreciated: http://revu.tauware.de/details.py?upid=3867
[10:16] <siretart> ScottK: is this a NEW package, or just an update?
[10:17] <siretart> ScottK: I think the package description could be a bit more verbose
[10:21] <tsmithe> could someone review my asoundconf-gtk package?http://revu.tauware.de/details.py?upid=3725 please
[10:30] <tsmithe> yay!
[10:32] <ScottK> siretart - pyspf is an update to an existing package Ubuntu takes straight from Debian.  I'm not the Debian maintainer, but the package is very old and the current pyspf has added several files, so the package got more complex.
[10:34] <siretart> tsmithe: after reading http://revu.tauware.de/revu1-incoming/asoundconf-gtk-0612101210/asoundconf-gtk-1.5/README-debian.rules, I wonder why you use CDBS at all
[10:34] <tsmithe> ok... explain
[10:35] <tsmithe> i chose cdbs as it was easy for my first ever package, and it wasn't too hard to have those extra lines to override the default behaviour
[10:36] <sinisterguy> ok, i've figured out most of it, but i'm getting a wierd error. i'm using this control file: http://pastebin.ca/289113 but when i do debuild -us -uc i get this error http://pastebin.ca/289119
[10:36] <sinisterguy> any suggestions?
[10:36] <siretart> ScottK: did you talk to gustavo?
[10:37] <siretart> tsmithe: for that reason, I wouldn't recomment using cdbs for the first package
[10:37] <tsmithe> siretart, oh - why? it's done now :(
[10:37] <tsmithe> sinisterguy, line 5 spills over to line 6 it looks like
[10:37] <ScottK> No.  My theory was to get the update correct here and then point him at Ubuntu.
[10:38] <siretart> tsmithe: because I see the trouble you have now
[10:38] <tsmithe> it's no trouble is it?
[10:38] <tsmithe> i mean, it all works fine
[10:38] <sinisterguy> tsmithe: thanks
[10:38] <siretart> well, okay
[10:38] <siretart> I'm not a friend of cdbs nor of pysupport
[10:38] <Toadstool> cdbs is evil! I love it :)
[10:38] <tsmithe> i didn't use cdbs for my next two packages, though
[10:39] <tsmithe> but i don't want those to be uploaded any time soon (licence issues)
[10:39] <siretart> no problem. I still have a package which still uses cdbs (londonlaw)
[10:39] <tsmithe> (well, i want it to be soon, but not in the current state)
[10:44] <siretart> tsmithe: advocated
[10:45] <tsmithe> thanks siretart :)
[10:45] <siretart> ScottK: hm. I'm basically okay with the package, but I really think you should talk to gustavo. I'm sure he'll appreciate help
[10:50] <sinisterguy> do you guys here handle backported packages as well as regular packages?
[10:50] <siretart> ScottK: ok, advocated for now
[10:59] <ScottK> siretart - Thanks.
[11:00] <bddebian> Later gang
[11:40] <siretart> yay! I can reboot my machine now without having to resort to an ps/2 keyboard :)
[11:42] <tsmithe> yay!
[11:51] <agent> why reboot when you can pull the plug? ;P
[12:04] <jdong> agent: because we yet to have a fully atomic filesystem to date? ;-)
[12:04] <jdong> oh yeah, there's that one made by that one wife murderer... what was his name again?
[12:04] <jdong> :)
[12:04] <agent> :D
[12:04] <realist> hrmmm
[12:04] <agent> i used that fs before years back
[12:05] <agent> never had problems
[12:05] <realist> guilty until proven otherwise?
[12:05] <jdong> agent: I said fully atomic :)
[12:05] <jdong> agent: that up and coming one that nobody wants in mainline ;-)
[12:05] <jdong> realist: certainly...
[12:05] <agent> jdong: sure sure.... ;)
[12:05] <jdong> actually, I did use that one last year for a while
[12:06] <jdong> it was great until I merged a buggy mm patchset....
[12:06] <agent> :D
[12:06] <jdong> I definitely hope it goes somewhere nice in the future
[12:06] <jdong> we need a fully atomic filesystem... heck Vista has one now :(
[12:06] <agent> have gentoo people beta test.... they like that kind of stuff
[12:07] <jdong> user*
[12:07] <agent> me too
[12:07] <jdong> switched in Warty Preview days
[12:07] <agent> i switched in hoary beta
[12:07] <agent> was going to switch to debian but decided to try that goofy new distro with a 6mo release cycle :D
[12:07] <realist> I'm a relative newbie to ubuntu (dapper)
[12:08] <agent> i have not done a clean install since hoary beta
[12:08] <agent> fear!
[12:08] <agent> ;P
[12:08] <realist> Been using debian since, forever...
[12:08] <agent> debian is nice....
[12:09] <agent> but i must say, ubuntu community has changed big time since dapper.... forums are chock full of ex-windows users like nowhere else
[12:10] <Fujitsu> I switched back to Debian for a month, ending a couple of weeks ago. My first non-Ubuntu since Hoary.
[12:10] <agent> Fujitsu: did you fresh install or just dist-upgraded (and then downgraded back?)
[12:11] <agent> jdong: what script is used to quickly convert debian debs to ubuntu?
[12:11] <agent> jdong: its not your prevu is it?
[12:11] <Fujitsu> Firstly, going to Sid isn't an upgrade in many cases. Secondly, downgrading is very very risky and likely to get you killed.
[12:11] <Fujitsu> So no, I installed clean.
[12:11] <Fujitsu> agent, prevu should do it fine.
[12:12] <agent> ok
[12:12] <Fujitsu> (although Debian ones may install OK anyway)
[12:12] <agent> yeah i know
[12:12] <agent> :)
[12:13] <realist> agent: the ex-windows users is partly why I'm hesitant about the ubuntu community (especially the forums)
[12:13] <realist> The developers on IRC seem fairly clueful though, thankfully :-)