[12:46] <LaserJock> ah, nifty
[12:46] <LaserJock> I added a source package search engine to opera
[12:46] <LaserJock> that's nice
[02:34] <ryanakca> can someone look at this http://revu.tauware.de/details.py?upid=2933 please?
[02:39] <crimsun> looks fine initially
[02:39] <crimsun> I can do a more thorough review in several hours.
[02:40] <ryanakca> kk, ty
[02:44] <LaserJock> pheww, I finally got one complete IRC log from the MOTU School session on the wiki
[02:45] <LaserJock> heh, I saved it before I said that, just in case ;-)
[02:51] <ryanakca> drats
[02:51] <ryanakca> lol
[02:54] <ryanakca> anybody else want to review eqonomize?
[03:03] <LaserJock> hi bddebian
[03:04] <bddebian> Heya LaserJock
[03:04] <bddebian> Heya gang
[03:04] <LaserJock> bye bddebian :-)
[03:05] <LaserJock> bbl
[03:05] <bddebian> Doh, bye
[03:10] <welshbyte> ello bddebian
[03:13] <welshbyte> bddebian: i'm mentioning you in a blog.. got a site/blog i could link to?
[03:16] <bddebian> What, are you doing a morons of Ubuntu page? :-)
[03:17] <welshbyte> nah, just rambling about my first experiences of ubuntu packaging, man page writing and stuff ;)
[03:18] <bddebian> :-)
[03:21] <welshbyte> oh, and when you have a spare minute.. http://revu.tauware.de/details.py?upid=2927
[03:23] <crimsun> (hah, these motu celebrities!)
[03:25] <bddebian> welshbyte: Aye, I'm working on some reviews now, so I'll take a look
[03:25] <bddebian> crimsun: But none of us can touch you :-)
[03:25] <welshbyte> bddebian: thanks :)
[03:25] <ajmitch> crimsun: why, back in our day there were no celebrities..
[03:25] <crimsun> bddebian: hah, I'm no celebrity.
[03:25] <crimsun> ajmitch: :)
[03:26] <tseng> the only celeb here is dholbach
[03:26] <bddebian> Heya tseng
[03:26] <tseng> great, the entire muslim community just switched away from ubuntu
[03:26] <crimsun> I'm pretty sure someone will proclaim you a blasphemer since BdDebianIsAGod is already in Google's cache
[03:27] <bddebian> Heh
[03:28] <bddebian> Well you will probably all be happy to know that I might be disappearing again for a while
[03:30] <bddebian> vas is los? W: libgrapple-1.0-0; The library libgrapple is not in a shlibs file.
[03:31] <ajmitch> bddebian: why are you leaving us?
[03:31] <bddebian> ajmitch: Because I bug you all?
[03:32] <ajmitch> oh right
[03:32] <bddebian>  :-)  j/k.  I'm not sure yet but work is going to pick up significantly until about November
[03:32] <crimsun> understandable.
[03:33] <ajmitch> right
[03:33] <bddebian> So like everything else, I know little about libraries.  What does that linda error mean?
[03:33] <bddebian> ajmitch: Nice
[03:34] <ajmitch> you must have the shlibs file in the final package
[03:34] <bddebian> What does that mean?
[03:34] <ajmitch> see the library packaging guide
[03:34] <bddebian> Gah
[03:35] <bddebian> OK
[03:35] <welshbyte> shouldn't add to your celebrity much, i expect the only person who reads my blog is my mother ;)
[03:35] <bddebian> Is there a library packaging guide as part of LaserJocks stuff?
[03:36] <bddebian> welshbyte: Believe me, I'm no celebrity
[03:36] <welshbyte> i know i know
[03:36] <ajmitch> bddebian: no, just the debian library packaging guide
[03:36] <ajmitch> first google hit
[03:36] <welshbyte> more of a deity
[03:36] <bddebian> welshbyte: Oh man, not you too
[03:36] <welshbyte> hehe
[03:40] <bddebian> Hmm, dh_makshlibs should cover it?
[03:40] <bddebian> Err makeshlibs
[03:41] <ryanakca> bddebian: ummm.... when you get a chance, can you review http://revu.tauware.de/details.py?upid=2933 please?
[03:41] <bddebian> Oh, no, he has that.  Hmm
[03:42] <bddebian> Is it maybe running for the wrong package?  I.E., should it be dh_makeshlibs -pfoo ?
[03:42] <ajmitch> possibly
[03:42] <ajmitch> or with the wrong options
[03:43] <ajmitch> or it could be done with debian/libfoo.shlibs
[03:43] <bddebian> OK, thx
[03:45] <bddebian> ryanakca: I'll take a look
[03:45] <ryanakca> bddebian: thanks :)
[03:53] <bddebian> So if I'm such a "God", why can't I figure out this pygobject crap? :'-(
[03:55] <slomo> bddebian: what's wrong with it?
[03:56] <welshbyte> it's a theological anomaly
[03:58] <bddebian> haha
[03:58] <bddebian> slomo: I'm not even sure it's it yet but bug #57182
[03:58] <Ubugtu> Malone bug 57182 in pygobject "Problem importing codegen from desextras" [Untriaged,Unconfirmed]  http://launchpad.net/bugs/57182
[04:02] <bddebian> welshbyte: Couple of things but overall looks good
[04:03] <welshbyte> bddebian: cool, cheers
[04:06] <bddebian> ryanakca: Gonna go have a cigarette, then you're next :-)
[04:06] <ryanakca> bddebian: kk
[04:14] <hub> ryanakca: dance more
[04:14] <ryanakca> lol, yes
[04:15] <bddebian> In Python whats the difference between sys.path.insert and sys.path.append?
[04:16] <ajmitch> where it gets placed in the sys.path list
[04:16] <ajmitch> which is checked in order
[04:16] <bddebian> insert at beginning, append at end?
[04:18] <ajmitch> insert takes a position to place the item
[04:18] <ryanakca> brb, log in log out... see if kde works again...
[04:21] <bddebian> ajmitch: Thx.  How does it get the path?  In this case it is doing sys.path.append(0, 'codegen').  How does it know where codegen is?
[04:22] <ajmitch> append or insert?
[04:22] <bddebian> Should changelog entry on initial packaging include any patches added?
[04:22] <bddebian> ajmitch: Sorry, insert
[04:22] <ajmitch> bddebian: so 'codegen' gets stuck as the first entry
[04:22] <ajmitch> changelog should
[04:23] <bddebian> ajmitch: I got that part but how does it "find" codegen?
[04:23] <ryanakca> bddebian: g'night... It's late and I'm going to bed, See you some time tommorow and I'll look at the revu page for comments
[04:23] <ajmitch> bddebian: codegen will be a directory, it'll look there
[04:24] <bddebian> ryanakca: OK, gnight
[04:25] <bddebian> ajmitch: So it shouldn't be a full path instead? Like sys.path.insert(0, '/usr/share/pygtk/2.0/codegen') ?
[04:31] <bddebian> Uh oh, I've overblown my question quota again, huh? :)
[04:34] <welshbyte> at least you're reading python and not this silly m4 stuff ;)
[04:34] <Quinn_Storm> ugh...m4...why in the world did they choose m4 for autotools?
[04:35] <welshbyte> hello Quinn_Storm
[04:35] <Quinn_Storm> greetings
[04:36] <bddebian> Hello Quinn_Storm
[04:36] <bddebian> welshbyte: Hey, I have a great one for you next.. ;-P
[04:36] <welshbyte> i swear autotools was created to give me headaches
[04:36] <welshbyte> bddebian: bring it on :P
[04:37] <bddebian> welshbyte: http://www.typo3.org  Needs the latest packaged ;-P
[04:38] <welshbyte> bddebian: would it be bad if i ignored that libdir warning from linda? it seems the 2.1.8 package ignored it
[04:39] <welshbyte> oh no, not a web app! :/
[04:43] <bddebian> welshbyte: Yeah and an ugly package at that. :-)
[04:43] <bddebian> welshbyte: If it's valid you can probably do a lintian-override for it but you might want some other input.  There is a lot I don't know :-(
[04:47] <welshbyte> well it seems valid, the file says /lib but it's in /usr/lib although i don't know how it works or what uses it
[04:47] <bddebian> Heya Hobbsee
[04:48] <welshbyte> ello Hobbsee
[04:49] <Hobbsee> hi bddebian
[04:49] <Hobbsee> hey welshbyte
[04:49] <Hobbsee> what's new?
[04:49] <bddebian> Hobbsee: Struggling through a python thing.  You?
[04:49] <Hobbsee> bddebian: having trouble typing in the root password :P  i just got up
[04:50] <Hobbsee> well, user password, ie sudo
[04:51] <Hobbsee> bddebian: what kind of python thing?
[04:51] <bddebian> Is getting the path to codegen by doing foo = getoutput('pkg-config --variable codegendir pygtk-2.0') considered "OK"?
[04:51] <bddebian> welshbyte: What, are you nuts? :-)
[04:52] <welshbyte>  /nick brazil_pecan_cashew
[04:52] <Hobbsee> holy cow.  74 new emails overnight.
[04:52] <Hobbsee> ryanakca: must have been busy, it looks like!
[04:53] <welshbyte> ouch
[04:53] <Hobbsee> and none of them are spam either :P
[05:00] <welshbyte> awesome, looks like i can ignore linda :)
[05:00] <welshbyte> i like learning new things
[05:01] <Quinn_Storm> hmm, looks like compiz is about ready ^-^, no more shlibdeps, proper revisions, no more goofy custom gconf stuff...broken out into compiz-core, compiz-plugins...build-deps and deps should be good
[05:02] <welshbyte> Quinn_Storm: awesome :)
[05:02] <Hobbsee> welshbyte: usually not a good idea to ignore linda, depending on what it is
[05:02] <bluefoxicy> linda needs to be updated on revu
[05:03] <Hobbsee> bluefoxicy: true that.  StevenK's working on it.  in fact, i thought he sent a copy
[05:03] <Hobbsee> bluefoxicy: oh, that's right.  StevenK was having trouble getting the latest version to install on breezy.
[05:04] <welshbyte> "W: gnu-smalltalk; The .la file /usr/lib/gnu-smalltalk/libc.la contains a libdir which is different to its path."  but libc.la says that libc.so.6 is in /lib and lo and behold, it is
[05:04] <bluefoxicy> can't he down revu for 6 hours to image it into a virtual machine
[05:04] <bluefoxicy> and then attempt to upgrade to dapper
[05:04] <Hobbsee> bluefoxicy: ask siretart that, he's the one who controls it (i think)
[05:04] <Hobbsee> welshbyte: do we ship .la files anyway now?  i think not.
[05:05] <bluefoxicy> (notice the CRITICAL part of this suggestion involving still retaining the old working copy-- in case you fuck it up)
[05:05] <Hobbsee> bah.  who needs revu anyway :P
[05:05] <Hobbsee> hey LaserJock
[05:05] <bddebian> Heya LaserJock
[05:05] <Hobbsee> hehe
[05:05] <welshbyte> Hobbsee: oh... you know something i don't
[05:06] <Hobbsee> welshbyte: i think they're gone, yeah
[05:06] <welshbyte> great, so i can just remove it in debian/rules
[05:11] <LaserJock> hi Hobbsee and bddebian
[05:25] <crimsun> bddebian: btw, unless you preface the sentence with my nick followed by either a comma or a colon, irssi doesn't highlight.
[05:26] <bddebian> Doh
[05:26] <crimsun> welshbyte: no, libtool archives are not supposed to be shipped.
[05:26] <LaserJock> hmm, you need some better highlighting then crimsun ;-)
[05:27] <crimsun> LaserJock: I consider it sanity-checking, else I'd never get any work done
[05:27] <welshbyte> crimsun: thanks... how about .a files?
[05:27] <bddebian> crimsun: Oh and here I thought you were just good at ignoring me ;-P
[05:27] <crimsun> welshbyte: yes, those are definitely shipped in -dev
[05:28] <crimsun> not doing so would break just about everything that passes -lfoo ;)
[05:28] <welshbyte> hm, gnu-smalltalk ships a /usr/lib/libgst.la and a /usr/lib/libgst.a at the moment
[05:29] <crimsun> remove the former prior to building the deb
[05:30] <welshbyte> will do
[05:30] <bddebian> crimsun: I don't suppose you have time to help me with this pygobject thing?
[05:31] <crimsun> I'd love to, but that requires significant resources, and honestly I'm about to nod off
[05:31] <bddebian> OK, thx anyway
[05:35] <bddebian> Heya carthik
[05:36] <carthik> Hi bddebian
[05:44] <bddebian> Should this just work or am I missing something?
[05:44] <bddebian> >>> import os
[05:44] <bddebian> >>> import sys
[05:44] <bddebian> >>> sys.path.insert(0, 'codegen')
[05:44] <bddebian> >>> from codegen import register_types
[05:44] <bddebian> Traceback (most recent call last):
[05:44] <bddebian>   File "<stdin>", line 1, in ?
[05:44] <bddebian> ImportError: No module named codegen
[05:47] <welshbyte> bddebian: where is the 'codegen' directory that you're inserting into the path?
[05:48] <lifeless> bddebian: changing the python path is usually not needed
[05:48] <bddebian> welshbyte: Dunno, that's what I'm trying to figure out
[05:48] <lifeless> bddebian: its ugly, error prone etc.
[05:48] <lifeless> bddebian: what are you trying to do ?
[05:48] <bddebian> This is what dsextras.py from pyobjects does
[05:48] <welshbyte> weird
[05:49] <lifeless> does it have a subdir 'codegen' with a subdir 'codegen' with a file '__init__.py' ?
[05:49] <bddebian> I don't see one
[05:49] <lifeless> then it wont work
[05:49] <bddebian> It doesn't ;-P
[05:50] <lifeless> is there a codegen subdir
[05:50] <lifeless> ?
[05:51] <bddebian> Where?
[05:51] <bddebian> From where dsextras.py is?
[05:51] <lifeless> I guess, though knowningcwd is probably more important
[05:51] <bddebian> Now this does work:
[05:51] <bddebian> >>> sys.path.insert(0, '/usr/share/pygtk/2.0/codegen')
[05:51] <bddebian> >>> from codegen import register_types
[05:51] <bddebian> >>>
[05:53] <lifeless> seriously wrong
[05:53] <welshbyte> i expect you only really need /usr/share/pygtk/2.0 to be in the path to import codegen from it
[05:54] <lifeless> welshbyte: nah, bet you uit has a subdir
[05:54] <welshbyte> heh, that would be typical
[05:54] <bddebian> Well here is the comment from dsextras.py from pyobjects:
[05:54] <bddebian>         # We must insert it first, otherwise python will try '.' first,
[05:54] <bddebian>         # in which it exist a "bogus" codegen (the third import line
[05:54] <bddebian>         # here will fail)
[05:54] <bddebian>         sys.path.insert(0, '/usr/share/pygtk/2.0/codegen')
[05:54] <bddebian> But I don't see an "extra" codegen dir anywhere
[05:54] <lifeless> this is either bogus code, or a bogus developer, or something
[05:55] <lifeless> crufty as
[05:56] <bddebian> I don't think so, it's seb128.  But I don't think he agrees with me
[06:06] <welshbyte> right lets see if this thing builds with tcl8.4
[06:06] <bddebian> go welshbyte, go welshbyte ;-)
[06:09] <welshbyte> seems to have worked :)
[06:13] <LaserJock> hmm, what has happend to edgy's sudo lately
[06:19] <LaserJock> hmm, so how do I tell sudo to keep my PATH
[06:21] <LaserJock> bddebian: do you know ^^ ?
[06:21] <bddebian> For su, I know it was su - but I don't know for sudo, sorry :-(
[06:21] <LaserJock> it hasn't bugged you yet?
[06:22] <bddebian> Everything bugs me :-)
[06:22] <LaserJock> well, I have my pbuilder scripts in ~/bin/
[06:22] <LaserJock> and today I noticed that I could no longer do sudo pbuilder-edgy
[06:22] <bddebian> Doh
[06:22] <LaserJock> I had to give it the full path
[06:24] <LaserJock> hmm?
[06:24] <LaserJock> pbuilder is run with sudo, right?
[06:26] <LaserJock> oh, silly me
[06:27] <LaserJock> my ~/bin scripts start with sudo, I don't need to call them with sudo
[06:27] <LaserJock> doh
[06:27] <bddebian> heh
[06:27] <LaserJock> I've been doing too much pbuilder howto writing
[06:27] <LaserJock> where you do sudo pbuilder directly
[06:28] <Hobbsee> heh
[06:28] <Hobbsee> sarah@sarah:~$ cat /usr/local/bin/edgybuild
[06:28] <Hobbsee> #!/bin/bash
[06:28] <Hobbsee> pdebuild --buildresult ../ --configfile /home/sarah/pbuilder/edgy/pbuilderrc --auto-debsign --debsign-k 7D2BCE85
[06:28] <Hobbsee> LaserJock: ^
[06:29] <Hobbsee> LaserJock: so not exactly needing to sudo it
[06:29] <LaserJock> hmm, interesting
[06:29] <welshbyte> doesn't it get confusing having a computer with the same name as you? :)
[06:29] <Hobbsee> welshbyte: not really
[06:29] <Hobbsee> welshbyte: why would it?
[06:30] <Hobbsee> i'm the only one who uses this machine
[06:30] <LaserJock> heh, well mine are all familiar terms for me
[06:30] <LaserJock> photon, electron, proton, etc. ;-)
[06:30] <welshbyte> oh just wondered
[06:31] <Hobbsee> welshbyte: and i'm incredibly shocking in naming things
[06:31] <LaserJock> I'm supprised it's not sarah@Hobbsee :-)
[06:32] <Hobbsee> LaserJock: hehe.  i dont use hobbsee much in RL - like, i answer to it, but people usually call me sarah
[06:32] <welshbyte> Hobbsee: oh i know what you mean, i have a hard time naming stuff too. i just got lucky when i fell upon the naming scheme for my computers :)
[06:33] <Hobbsee> of course, in RL, it's obvious that i'm female anyway, so there's no point in not disclosing the nme
[06:33] <Hobbsee> *name
[06:33] <LaserJock> true
[06:34] <welshbyte> oops, just noticed i was still set as away
[06:35] <bddebian> Speaking of which, I have got to get my arse to bed.  Gnight folks
[06:35] <welshbyte> bddebian: g'night
[06:35] <bddebian> welshbyte: Are you going to re-upload gnu-smalltalk?
[06:35] <welshbyte> bddebian: just done it
[06:35] <bddebian> Sweet, I'll check it in the morning.  Thanks again!
[06:36] <welshbyte> cheers :)
[07:23] <LaserJock> Hobbsee: did you merge maxima?
[07:24] <Hobbsee> LaserJock: yes
[07:24] <Hobbsee> LaserJock: i probably didnt need to, but yeah
[07:24] <LaserJock> k
[07:24] <LaserJock> thanks
[07:24] <Hobbsee> LaserJock: not a problem :)
[07:25] <Hobbsee> LaserJock: unfortunately, the machine i like building on is awol at the moment
[07:25] <LaserJock> I wish the GUI worked but that's my problem
[07:26] <Hobbsee> true
[07:26] <LaserJock> I got almost 10 bug emails about that today
[07:27] <LaserJock> I guess that's how fixes get done
[07:27] <LaserJock> pester the devs with emails until they can't stand it anymore ;-)
[07:27] <jsgotangco> wha? the great LaserJock is not aware of the procedure? heh
[07:27] <LaserJock> oh, I am
[07:28] <LaserJock> I'm just not used to being on the recieving end so much :-)
[07:28] <jsgotangco> heh
[07:28] <jsgotangco> that last xorg-core update had tons of bugs
[07:28] <LaserJock> lol, poor rodrigo
[07:28] <LaserJock> I feel bad for him
[07:29] <Hobbsee> LaserJock: yeah...i'd hate to be him right now
[07:30] <LaserJock> well, the thing is I don't think he signed on to do X maintaining
[07:30] <LaserJock> he is Edubuntu technical lead
[07:31] <LaserJock> yep
[07:32] <LaserJock> at least rodrigo has the guts to take on X for a while
[07:32] <Hobbsee> LaserJock: good point that
[07:32] <LaserJock> either that or being the newest employee made him draw the short straw
[07:33] <Hobbsee> heh
[07:34] <crimsun> hopefully he has been getting help from everyone.
[07:34] <crimsun> I know Andrew and I have been rejecting and marking duplicates of 57153 since early yesterday
[07:34] <LaserJock> yeah
[07:35] <Hobbsee> crimsun: wish the bugtracker had gone down during that time, rather than a few hours ealrier :P
[07:36] <LaserJock> heh
[07:52] <jsgotangco> well rodrigo had the X experience with conectiva
[09:01] <Arbiter> i need a REVU admin
[09:02] <Arbiter> Hobbsee: ping
[09:02] <Hobbsee> Arbiter: pong.  i'm not a revu admin though
[09:03] <Arbiter> Hobbsee: i know :)
[09:03] <Arbiter> would you review 3 packages? :D
[09:04] <Arbiter> debian-servicemenu attach-to-email-servicemenu kcmpureftpd :)
[09:04] <Hobbsee> wow, you've been busy
[09:04] <Arbiter> note: *-servicemenu have licensing issues
[09:05] <Arbiter> (the websites say that are licensed under GPL license but no license file or GPL comment in files are provided)
[09:05] <Arbiter> (nor a copyright notice)
[09:06] <Arbiter> i asked upstream to include those details for the next release of the packages
[09:07] <Arbiter> Hobbsee: anyway... links are http://revu.tauware.de/details.py?upid=2935 (kcmpureftpd) - http://revu.tauware.de/details.py?upid=2925 (attach-to-email-servicemenu) - http://revu.tauware.de/details.py?upid=2923 (debian-servicemenu)
[09:08] <Arbiter> :)
[09:08] <Hobbsee> yay for ssh
[09:08] <Arbiter> all tested in edgy pbuilder and installed on my local machine
[09:08] <Arbiter> and everything seems to work :)
[09:09] <Sp4rKy> hey
[09:12] <Arbiter> Hobbsee: https://launchpad.net/+builds/vernadsky (4th line) <-- yes! :D
[09:13] <Hobbsee>  Arbiter nice :)
[09:14] <Arbiter> slomo: ping
[09:17] <Arbiter> Hobbsee: where i can post some kubuntu artwork proposals?
[09:17] <Hobbsee> Arbiter: um.  on the wiki.  there i s apage :P
[09:19] <Nafallo> Hobbsee: wrong. there is more than one page on the wiki :-)
[09:19] <Hobbsee> Nafallo: nyah :P
[09:21] <Arbiter> :)
[09:25] <Arbiter> Hobbsee: https://wiki.kubuntu.org/Artwork/Incoming/Kubuntu-Edgy-Ideas?
[09:25] <Hobbsee> Arbiter: looks good
[09:57] <Arbiter> heya Gloubiboulga
[09:57] <Arbiter> :D
[09:58] <Gloubiboulga> hello arbiter :)
[10:00] <Arbiter> i'll be back soon
[10:00] <Arbiter> ah Gloubiboulga could you review this? http://revu.tauware.de/details.py?upid=2935 (kcmpureftpd)
[10:01] <Gloubiboulga> Arbiter, not now, but I'm adding it on my TODO list
[10:02] <Arbiter> thanks a lot
[10:02] <Arbiter> :)
[10:02] <Arbiter> i've uploaded also attach-to-email-servicemenu but it has the same license issue as debian-servicemenu
[10:02] <Arbiter> grrr
[10:02] <Arbiter> :P
[10:06] <Toadstool> good morning
[10:18] <Goshawk> how can i obtain my password in REVU? the lostpw.py script seems to don't work with me
[10:19] <Gloubiboulga> Goshawk, have you already uploaded a package on REVU ?
[10:19] <Goshawk> Gloubiboulga: sure, it's splashy
[10:20] <Gloubiboulga> ok, then you should be able to recover your password...
[10:21] <Gloubiboulga> you need to ping a REVU admin
[10:21] <Goshawk> Gloubiboulga: yep i'm but when i should encrypt mesage with gpg
[10:21] <Goshawk> there is no text to encrypt/decript in the html page
[10:21] <Gloubiboulga> sounds like a bug
[10:22] <Toadstool> hmm I think siretart told something about a broken pw_recover.py or something like that a while ago
[10:22] <Goshawk> yep i talked with sirestart, but i've not my password
[10:23] <Goshawk> so i can comment on REVU
[10:25] <Toadstool> Goshawk: do you know that splashy is already packaged in Debian Sid?
[10:25] <Goshawk> Toadstool: sure i know
[10:25] <Toadstool> uhuh
[10:25] <Toadstool> forget about that :p
[10:25] <Goshawk> but it's not in ubuntu
[10:26] <Goshawk> Toadstool: i'm one of the developers and i know the debian maintainer
[10:26] <Toadstool> ok
[10:27] <Toadstool> you should file a bug asking for a sync, and poke a MOTU here to confirm it
[10:27] <phanatic> morning :)
[10:27] <Toadstool> heya phanatic
[10:28] <phanatic> hey Toadstool
[10:28] <phanatic> ajmitch: thanks for your review, i'll upload a new package soonish
[10:30] <Toadstool> Goshawk: I may not be very well awoken, I didn't notice the changes in the B-Deps... sorry
[10:30] <Toadstool> Goshawk: you should list that kind of changes in the changelog imho
[10:31] <Goshawk> Toadstool: ok. so i should repackage it
[10:31] <Toadstool> and you shouldn't change the "This package was debianized by" line
[10:31] <Toadstool> repackage it?
[10:31] <Goshawk> and... if we want a fully integration in ubuntu, there are some things to change
[10:32] <Goshawk> Toadstool: repackage or create a new ubuntu version ubuntu1 ---> ubuntu2
[10:32] <Goshawk> Toadstool: https://launchpad.net/distros/ubuntu/+source/lsb/+bug/56882
[10:32] <Ubugtu> Malone bug 56882 in lsb "/etc/lsb-base-logging.sh should be in usplash package" [Untriaged,Unconfirmed] 
[10:32] <Goshawk> that fiel in in usplash in debian, in ubuntu it's in lsb-base
[10:32] <Toadstool> Goshawk: just apply your modifications to ubuntu1 and reupload it to REVU as ubuntu1
[10:34] <Goshawk> Toadstool: ah so i don't need to put anotehr version, REVU gets the lastest package
[10:34] <Toadstool> yep
[10:35] <Goshawk> can i confirm that bug?
[10:39] <Toadstool> Goshawk: confirming one's own bugs is generally speaking not a good idea but I think you can with this one :)
[10:40] <Goshawk> Toadstool: i'm configming it because it's there from some dys without attenctions
[12:47] <phanatic> could anybody have a look at this please: http://revu.tauware.de/details.py?upid=2936
[01:29] <\sh> moins
[01:49] <imbrandon> phanatic: not orig.tar.gz but theres a diff
[01:50] <phanatic> imbrandon: what's the problem?
[01:50] <imbrandon> there is no orig.tar.gz
[01:50] <phanatic> oh
[01:50] <phanatic> dput didn't put it :)
[01:51] <imbrandon> did you build with debuild -S -sa ?
[01:51] <phanatic> dpkg-buildpackage -rfakeroot -S
[01:51] <phanatic> should be the same
[01:51] <phanatic> :)
[01:52] <azeem> except for the -sa
[01:52] <azeem> which is the crucial point here
[01:52] <phanatic> yay
[01:53] <phanatic> i got the point
[01:53] <imbrandon> also did you read ajmitch comment about it shouldnt be versiond natively ?
[01:54] <phanatic> yeah, forgot to change the revision number :/
[01:54] <phanatic> in debian/changelog
[01:55] <phanatic> will upload soon
[01:58] <Arbiter> any reviewer around?
[01:58] <Arbiter> if yes could you review http://revu.tauware.de/details.py?upid=2935 (kcmpureftpd) thanks :)
[02:01] <phanatic> could someone delete olive? it got stuck :( got a 553 response...
[02:05] <phanatic> Uploading via ftp olive_0.1-0ubuntu1.dsc: Error '553 Could not create file.' during ftp transfer of olive_0.1-0ubuntu1.dsc
[02:05] <phanatic> :)
[02:09] <Arbiter> heya cbx33
[02:12] <siretart> slomo: http://incoming.debian.org/ffmpeg_0.cvs20060823-1.dsc
[02:13] <slomo> siretart: cool :) will you care for it or shall i?
[02:13] <cbx33> Hi Arbiter
[02:13] <cbx33> howz it goin
[02:13] <siretart> slomo: I'm busy today, if you have time, please do it
[02:14] <siretart> slomo: sam just told me on #debian-devel
[02:14] <Sp4rKy> hi
[02:15] <Sp4rKy> dpkg-parsechangelog: error: cannot open debian/changelog to find format
[02:15] <Sp4rKy> what must i do
[02:15] <Sp4rKy> i've a changelog.in
[02:16] <azeem> Sp4rKy: why do you have a changelog.in?
[02:16] <Sp4rKy> azeem, because the source was already debiannized
[02:16] <azeem> that's not a reason
[02:16] <Sp4rKy> so i've recreated debian/
[02:16] <azeem> remove the debian/ then, and or patch it properly in the .diff.gz
[02:16] <Sp4rKy> so i have to patch the configure
[02:17] <Sp4rKy> for it don't look at debain/changelog.in ?
[02:17] <azeem> why should it look at changelog.in?
[02:18] <Sp4rKy> because it create debian/changelog from debian/changelog.in
[02:18] <azeem> what is "it"?
[02:19] <Sp4rKy> configure
[02:19] <azeem> why does configure muck around with debian/changelog?
[02:20] <slomo> siretart: i'll try to get it updated later :)
[02:20] <Sp4rKy> i don't know why, but configure create changelog from changelog.in
[02:20] <siretart> slomo: sync or merge?
[02:21] <Mithrandir> Sp4rKy: make configure stop doing that.  It sounds like upstream is doing seriously wrong things.
[02:21] <slomo> siretart: merge... we need at least the epoch again ;)
[02:21] <siretart> slomo: I see
[02:21] <Arbiter> slomo: do you have some free time? :D
[02:22] <slomo> Arbiter: not really... why?
[02:22] <Sp4rKy> Mithrandir, i've already talked with upstream, but they doesn't wan't change anything (it's enlightenment)
[02:22] <Arbiter> there's libgimp-cil waiting for your review :)
[02:22] <Hobbsee> slomo: you're in charge of xine-lib, right?
[02:23] <tseng> Hobbsee: he is in charge of everything
[02:23] <Hobbsee> tseng: point.
[02:23] <Mithrandir> Sp4rKy: well, it's a blatant violation of Debian and Ubuntu policy, so just patch it out.
[02:24] <siretart> Hobbsee: what is it with xine-lib?
[02:24] <Sp4rKy> Mithrandir, k
[02:24] <Sp4rKy> thx
[02:24] <azeem> Sp4rKy: is the debian/ dir shipped in their release tarballs?
[02:24] <azeem> or just cvs/svn/whatever?
[02:24] <slomo> Hobbsee: you might want to talk to siretart :) he cares more for it lately
[02:24] <Sp4rKy> azeem, don't know
[02:25] <Hobbsee> siretart: slomo:  ah okay.  m4b playback.  i've got a patch for it, from kde upstream/gentoo, but it's giving me grief in applying it.
[02:25] <Hobbsee> siretart: do you care enough to eyeball it, change it, fix it, etc?
[02:25] <slomo> Hobbsee: wtf is m4b? another variant of a mp4 container format? ;)
[02:25] <Hobbsee> change is simple - it seems to be the introducing of a patch system at all that is causing greif
[02:26] <Hobbsee> slomo: i think so, yeah
[02:26] <siretart> Hobbsee: Ive seen quite some interesting patches in the gentoo repo that you pointed me in the bugreport
[02:27] <siretart> Hobbsee: I'd like to talk to flameyes about them. he is also xine upstream, and I wanted to ask him why those patches arn't upstream yet
[02:27] <Hobbsee> siretart: fair enough
[02:27] <siretart> Hobbsee: I'd need to find some hours to go through the gentoo patchsets and integrate them into the debian package. then I will remerge them in the ubuntu package.
[02:28] <siretart> Hobbsee: I have all branches in bzr, btw
[02:28] <Hobbsee> siretart: cool :)
[02:30] <Sp4rKy> does manpages are really needed ?
[02:30] <Sp4rKy> in a package ?
[02:31] <zul> yes
[02:32] <Toadstool> Sp4rKy: "If no manual page is available, this is considered as a bug and should be reported to the Debian Bug Tracking System (the maintainer of the package is allowed to write this bug report themselves, if they so desire). Do not close the bug report until a proper man page is available."
[02:32] <Toadstool> Debian Policy
[02:32] <Sp4rKy> sorry :p
[02:32] <Toadstool> no problem :)
[02:33] <Sp4rKy> gloubiboulga said me they 're not needed anymore
[02:34] <Toadstool> Sp4rKy: if lintian complains about something, there is a huge chance that this is required by the debian policy ;)
[02:35] <slomo> siretart: you will build xine against the new ffmpeg then?
[02:36] <Sp4rKy> Toadstool, says it to {my,your} mentor :)
[02:36] <Yagisan> Sp4rKy, we still need man pages.
[02:36] <siretart> slomo: I need to test this. currently, xine is built against the internal copy
[02:37] <Toadstool> Sp4rKy: heh
[02:37] <siretart> slomo: I need to do some tests. xine 1.1.3cvs has already a newer ffmpeg snapshot. the changes that needed to be done outside src/libffmpeg didn't look too bad, so I expect it to work
[02:37] <siretart> but I promise nothing :)
[02:45] <Sp4rKy> another question, if a lib which is only used by one application has a buggued soname, could i just put here in /usr/lib or must i put it in /usr/lib/foo
[02:45] <Sp4rKy> ?
[02:45] <azeem> buggered how exactly?
[02:50] <tseng> can anyone suggest a small tool to run from cron to do apt security updates in a (semi)automated fashion?
[02:51] <tseng> and don't say cfengine
[02:51] <tseng> *looks at update-apt*
[02:51] <thom> you could probably hack apticron up
[02:52] <tseng>   Update APT is a simple tool which will ensure that your local
[02:52] <tseng>  machine is kept up to date in a simple manner.
[02:53] <tseng> written by "The Other Steven K"
[02:53] <Sp4rKy> azeem, the name is libfoo.so.X.Y.Z and the soname is X.Y.Z
[02:53] <azeem> Sp4rKy: how did you figure out the soname is X.Y.Z?
[02:53] <tseng> but not quite it
[02:53] <azeem> or do you mean literally "X.Y.Z"
[02:54] <Sp4rKy> the somane is X.Y.Z
[02:55] <Sp4rKy> it's the result objdump write
[02:55] <azeem> Sp4rKy: how did you figure out the soname is X.Y.Z?
[02:55] <azeem> ok
[02:55] <Mithrandir> tseng: pkgsync or cron-apt too.
[02:55] <azeem> I suggest you rather fix this then
[02:56] <Mithrandir> I'd hope it's rather libfoo.so.X.Y.Z than just X.Y.Z (or preferably libfoo.X as the soname, but you can't always have it that way)
[03:02] <StevenK> tseng: There's another me?
[03:06] <tseng> StevenK: steve kemp
[03:06] <StevenK> Oh yeah
[03:06] <StevenK> skx
[03:06] <tseng> i thought you were him at first
[03:06] <tseng> so solly
[03:07] <StevenK> Heh
[03:15] <slomo> siretart: works fine here... mplayer still crashes but this is "only" a symbol collision problem... ffmpeg and mplayer both ship their own liba52 copies... :(
[03:15] <slomo> siretart: i'll fix mplayer later, ffmpeg is uploaded
[03:49] <Sp4rKy> i've an issue with my pbuilder
[03:49] <Sp4rKy> The following packages have unmet dependencies:
[03:49] <Sp4rKy>   libeet0-dev: Depends: zlib1g-dev but it is not going to be installed
[03:50] <Sp4rKy> and when i do a pbuilder login && apt-get install zlib1g-dev
[03:50] <Sp4rKy> The following packages have unmet dependencies:
[03:50] <Sp4rKy>   zlib1g-dev: Depends: zlib1g (= 1:1.2.3-6ubuntu4) but 1:1.2.3-13ubuntu1 is to be installed
[03:50] <Sp4rKy> this is a dapepr pbuilder
[03:52] <crimsun> so what is an edgy package doing in your dapper pbuilder?
[03:52] <Sp4rKy> edgy ?
[03:53] <Sp4rKy> this isn't an edgy package
[03:53] <crimsun> yes, that's edgy's zlib1g
[03:53] <crimsun> you claim it's a dapper pbuilder, but edgy's zlib1g is sourced (and therefore appears)
[03:54] <Sp4rKy> sorry, i don't understand
[03:54] <Sp4rKy> i've a dapper system and a dapper pbuilder
[03:54] <Sp4rKy> and twice have zlib1g
[03:55] <crimsun> in your dapper pbuilder, libeet0-dev cannot be installed because it depends on the dapper version of zlib1g-dev (1:1.2.3-6ubuntu4), but you have _edgy's_ zlib1g (1:1.2.3-13ubuntu1) installed in your pbuilder.
[03:56] <crimsun> thus the question is, "why do you have edgy's zlib1g in your dapper pbuilder?"
[03:56] <Sp4rKy> i don't know
[03:56] <Sp4rKy> so i've to reinstall my pbuilder ?
[03:57] <crimsun> not necessarily. perhaps. the better approach is to figure out why that edgy package is polluting your dapper pbuilder. check your pbuilder's sources.list.
[03:57] <crimsun> I'd walk backward from a ``pbuilder login''
[03:58] <crimsun> once you've logged into your pbuilder, ``apt-cache policy zlib1g''
[03:58] <Sp4rKy> i'm doing
[03:59] <Sp4rKy> zlib1g:
[03:59] <Sp4rKy>   Installed: 1:1.2.3-13ubuntu1
[03:59] <Sp4rKy>   Candidate: 1:1.2.3-13ubuntu1
[03:59] <Sp4rKy>   Version table:
[03:59] <Sp4rKy>  *** 1:1.2.3-13ubuntu1 0
[03:59] <Sp4rKy>         100 /var/lib/dpkg/status
[03:59] <Sp4rKy>      1:1.2.3-6ubuntu4 0
[03:59] <Sp4rKy>         500 http://fr.archive.ubuntu.com dapper/main Packages
[03:59] <Sp4rKy> root@Sp4rKy-laptop:/# cat /etc/apt/sources.list
[03:59] <Sp4rKy> deb http://e17.tuxfamily.org dapper e17
[03:59] <Sp4rKy> deb http://fr.archive.ubuntu.com/ubuntu/ dapper main restricted universe multiverse
[03:59] <crimsun> so. Why in the world do you have edgy's zlib1g installed?
[04:00] <Sp4rKy> don't know :/
[04:00] <Sp4rKy> so i just remove this library ?
[04:03] <crimsun> well, do you have edgy's version in the pbuilder's /var/cache/apt/archives/ ?
[04:04] <thom> Sp4rKy: apt-get install zlib1g/dapper
[04:04] <thom> and see what breaks
[04:05] <Sp4rKy> root@Sp4rKy-laptop:/# ls /var/cache/apt/archives/zlib1g*
[04:05] <Sp4rKy> /var/cache/apt/archives/zlib1g-dev_1%3a1.2.3-13ubuntu1_i386.deb  /var/cache/apt/archives/zlib1g_1%3a1.2.3-6ubuntu4_i386.deb
[04:05] <Sp4rKy> /var/cache/apt/archives/zlib1g_1%3a1.2.3-13ubuntu1_i386.deb
[04:06] <Sp4rKy> thom, works
[04:07] <crimsun> so yes, you do have edgy's zlib1g{,-dev} debs cached. Remove them, then apt-get update, then log out of your pbuilder.
[04:08] <crimsun> now if they're already in your base.tgz, you'll be back where you started before, which means you'll have to redo what you just did with ``pbuilder login --save-after-login''
[04:08] <Sp4rKy> k
[04:24] <\sh> re
[04:27] <Sp4rKy> now i've the same issue with libimlib2
[04:35] <hub> whiprush: the  thing on the pictures on your blog looks like a giant cock
[04:36] <hub> hey \sh
[04:37] <whiprush> hub: hehe, yeah
[04:38] <thom> whiprush: i did wonder why the girls looked so interested in it...
[04:38] <hub> :-)
[04:47] <siretart> slomo: making xine use external liba52 is on my list anyway
[04:47] <siretart> slomo: in fact, I've already done this in a branch
[04:57] <slomo> siretart: cool... but i was talking about mplayer ;)
[04:59] <slomo> siretart: and the easy workaround doesn't work at all :P grmpf...
[05:00] <\sh> siretart: do you have a bazaar branch for the fai changes you made in your last upload for dapper?
[05:14] <lfittl> could need some help with the following linda warning: "This package contains shared libraries and no shlibs file.", how exactly should the shlibs file look like?
[05:15] <slomo> lfittl: it should be created by dh_makeshlibs
[05:16] <lfittl> slomo: it is, but linda doesn't seem to like it
[05:16] <siretart> \sh: I'm sure that I have, however, the debdiff is quite small
[05:17] <lfittl> slomo: "libgrapple-1.0 0 libgrapple-1.0-0", can that be correct?
[05:17] <siretart> slomo: can't you build mplayer with the external liba52?
[05:17] <lfittl> slomo: source is at REVU, http://revu.tauware.de/details.py?upid=2931
[05:17] <slomo> siretart: probably... will still explode because of ffmpeg's own version
[05:17] <slomo> siretart: i'll try to use ffmpeg's version in mplayer later
[05:18] <siretart> slomo: err, ffmpeg uses an internal copy of lib52a?
[05:18] <siretart> you're sure?
[05:18] <slomo> siretart: by just linking to libavcodec.so.0d instead of the static liba52 stuff that is created in the mplayer build tree
[05:18] <slomo> yes
[05:19] <\sh> siretart: I'm asking, because I wanted to fix some nfsroot configs as well, so we could push it onto lp and work together
[05:19] <slomo> siretart: objdump -T /usr/lib/libavcodec.so.0d | grep a52 <--- all stuff in the so
[05:19] <\sh> siretart: how is life btw? :)
[05:24] <siretart> slomo: oh darn. perhaps you can check with sam about this?
[05:24] <\sh> brb
[05:24] <siretart> \sh: quite busy. I have a new part time job, but I'm quite busy with my thesis as well
[05:25] <slomo> siretart: sure... sam in #debian-devel?
[05:26] <siretart> slomo: right. I think on oftc only, but I'm not sure
[05:27] <slomo> siretart: here too... let's see what he says
[05:29] <lfittl> slomo: if you are too busy to investigate on my problem please say so, I will then re-search library packaging guide, .. ;)
[05:30] <slomo> lfittl: oh, sorry... yes that looks fine if the library is libgrapple-1.0.so.0 and the package name libgrapple-1.0-0
[05:30] <lfittl> slomo: hmm
[05:31] <slomo> maybe linda is broken :) StevenK?
[05:32] <lfittl> :)
[05:35] <welshbyte> linda on REVU is a bit old, if that's the one you're using (REVU is running breezy)
[05:35] <lfittl> welshbyte: no, I am using linda on edgy
[05:35] <slomo> siretart: and mplayer can't be built against system or ffmpeg liba52... it uses private functions :(
[05:35] <welshbyte> ah ok
[05:37] <bddebian> Heya gang
[05:37] <lfittl> hey bddebian
[05:38] <bddebian> Hi lfittl
[05:38] <lfittl> bddebian: linda seems to be wrong in this case (concerning libgrapple on REVU)
[05:39] <lfittl> bddebian: or do you have any idea what is wrong with the shlibs file?
[05:39] <bddebian> lfittl: Aye, I don't use REVU's linda/lintian.
[05:39] <bddebian> lfittl: It's missing or not generated for the proper package
[05:40] <AnAnt> bddebian: could you also review the elinks & freedict packages ?
[05:40] <bddebian> AnAnt: Sure, what the hell :)
[05:40] <AnAnt> bddebian: thanks !
[05:41] <AnAnt> worst meaning what ?
[05:41] <siretart> slomo: well, sam also maintains liba52. we should definitly fix that
[05:42] <slomo> siretart: well, mplayer and ffmpeg have to be fixed, right :) probably not too easy in the case of mplayer...
[05:44] <lfittl> bddebian: its contents are "libgrapple-1.0 0 libgrapple-1.0-0", and it is in the libgrapple-1.0-0 package, seems correct to me
[05:47] (bddebian/#ubuntu-motu) lfittl: Let me ssh in to my machine
[05:47] (bddebian/#ubuntu-motu) AnAnt: All MOTU's SHOULD be reviewers
[05:47] (lfittl/#ubuntu-motu) bddebian: :)
[05:47] (AnAnt/#ubuntu-motu) who are the MOTU
[05:47] (AnAnt/#ubuntu-motu) ?
[05:49] <lfittl> bddebian: will help with the reviewing as soon as I am a MOTU (could need your help/"+1" at the next TB meeting ;))
[05:49] <AnAnt> what is help/"+1" & TB ?
[05:49] <AnAnt> TB=testbench?
[05:50] <azeem> TB=Technical Board
[05:50] <AnAnt> oh,k
[05:50] <phanatic> any revu admins around by chance?
[05:50] <lfittl> help / "+1": that bddebian (hopefully :D) tells the technical board that I have done good work
[05:51] <bddebian> But of course :-)
[05:51] <AnAnt> I just gone to MOTU wiki page
[05:51] <AnAnt> does that mean that I can be a reviewer since I can upload ?
[05:51] <lfittl> hey dholbach :)
[05:52] <dholbach> hey bddebian, lfittl
[05:52] <zul> hey dholbach
[05:52] <bddebian> AnAnt: You are an MOTU?
[05:52] <AnAnt> bddebian: dunno, I can upload to REVU
[05:52] <bddebian> AnAnt: Oh and anyone can review but only MOTU's can advocate/upload to Ubuntu
[05:53] <AnAnt> k
[05:53] <bddebian> At least that is my understanding
[05:54] <AnAnt> kk
[05:56] <AnAnt> lionelp: you online ?
[05:56] <lionelp> AnAnt: yes
[05:56] <AnAnt> lionelp: great
[05:57] <AnAnt> lionelp: remember you once reviewed elinks that I uploaded?
[05:57] <lionelp> I remember yes
[05:57] <bddebian> AnAnt: I will look at it again also if needed
[05:57] <AnAnt> bddebian: thanks
[05:58] <AnAnt> bddebian: the thing is I compiled in it more options than  the one from debian, I was wondering is that the right thing to do, or is it better to add a new target called elinks-full ?
[05:59] <AnAnt> bddebian: I mean just like ubuntu added a lightweight target called elinks-lite
[05:59] <AnAnt> ?!
[05:59] <AnAnt> I got mixed up
[06:00] <AnAnt> bddebian: what did you mean by "it" when u said look at it again ?
[06:00] <AnAnt> bddebian: I was thinking that I was talking to lionelp
[06:00] <bddebian> AnAnt: Hmm..  Good question.  I kind of like the elinks-full idea but it might explode the archive a little
[06:00] <AnAnt> lionelp: ok, you had some comments on elinks, so I fixed them & uploaded elinks on July, I hope you would review it again
[06:01] <lionelp> I will have a look
[06:01] <AnAnt> lionelp: thanks
[06:01] <lionelp> That is not an easy question
[06:01] <AnAnt> which question ? the elinks-full one ?
[06:02] <lionelp> yep
[06:02] <AnAnt> well, I can help you answer it
[06:02] <AnAnt> I compiled it with the spidermonkey option, that is to enable javascript support
[06:02] <AnAnt> that option can cause elinks to crash sometimes (if java script was enabled during runtime)
[06:03] <rexbron> Hello
[06:03] <phanatic> raphink: hey, do you have time for a small revu fix? olive got stuck somewhere, and i cannot upload...
[06:03] <rexbron> what is the process for getting packages into the Universe
[06:03] <rexbron> is there a request form?
[06:04] <AnAnt> it seems the Debian guys compile in the options that they see are usually needed and that are stable
[06:04] <welshbyte> rexbron: have a look at https://wiki.ubuntu.com/MOTU/Packages/REVU
[06:04] <raphink> phanatic: sure you can now :)
[06:04] <AnAnt> btw, won't the recover page on REVU be fixed ?
[06:05] <lionelp> AnAnt: one of the problem you have to consider is that elinks is in main
[06:06] <AnAnt> lionelp: so ?
[06:06] <lionelp> but your build depends on package in universe
[06:06] <phanatic> raphink: thanks :)
[06:06] <lionelp> so it is not possible to do a single package with another target
[06:07] <AnAnt> lionelp: sorry I don't understand that last statement
[06:07] <lionelp> Ok, I try to make it more clear :)
[06:08] <lionelp> You have enabled more options for building elinks
[06:08] <AnAnt> yup
[06:08] <lionelp> with those options, you depends on package in universe
[06:08] <AnAnt> ok
[06:09] <lionelp> I was answering to your previous questions: this package can not be *the* elinks package even if you had a "light" and a "full" target to debian/rules
[06:09] <lionelp> you need to keep it in a different package
[06:10] <AnAnt> do you mean that it is bad that a package in main would depend on a package in universe ?
[06:11] <lionelp> AnAnt: that detail was probably missing in explanation, you are right :)
[06:11] <lionelp> yes, a package in main ca not depend on a package in universe
[06:12] <AnAnt> lionelp: ok, that means, that if I want to add those options, I'd better add a new build target called, elinks-full for example
[06:12] <AnAnt> lionelp: and leave the elinks target as it is
[06:13] <AnAnt> lionelp: just like elinks-lite, I just checked it, it is in universe/web
[06:13] <lionelp> You can not call you package elinks
[06:13] <lionelp> you have to call it elinks-full
[06:13] <AnAnt> lionelp: yes, that's what I mean, just like elinks-lite that Ubuntu added
[06:14] <lionelp> exactly
[06:14] <AnAnt> lionelp: both elinks & elinks-lite have same source package (that is elinks)
[06:14] <AnAnt> ok, gonna work on that
[06:15] <lionelp> AnAnt: you are right, both have the same source
[06:17] <bddebian> *\O/* LaserJock
[06:18] <LaserJock> hi bddebian
[06:19] <AnAnt> is there something called Replaces: in control file ? or does Conflicts: suffice ?
[06:19] <LaserJock> AnAnt: check out the Debian Policy
[06:19] <LaserJock> for proper usage
[06:20] <AnAnt> LaserJock: tell me, is the recover page on REVU still working for you ?
[06:20] <AnAnt> LaserJock: where's that debian policy ?
[06:20] <LaserJock> AnAnt: yes, it works for me
[06:20] <LaserJock> AnAnt: www.debian.org/devel/
[06:20] <AnAnt> LaserJock: what's the reason for that ?
[06:21] <LaserJock> reason for what?
[06:21] <AnAnt> LaserJock: that it works for you but not many others
[06:22] <LaserJock> If I new that it would probably be fixed :-)
[06:22] <AnAnt> yeah, right !
[06:23] <AnAnt> gotta go
[06:56] <bddebian> Where is all this spec stuff? I have to start getting some cheesy karma ;-P
[06:58] <LaserJock> heh
[06:58] <zul> hey LaserJock btw
[06:58] <LaserJock> I think http://launchpad.net/distros/ubuntu/+specs
[06:58] <LaserJock> brb, rebooting into Ubuntu
[07:02] <welshbyte> you know, i think developers of young libraries think "there's no point in writing a man page documenting this library since the API is going to change regularly" but really that's a great reason to ship an up-to-date man page with each release (grumble)
[07:03] <bddebian> :)
[07:04] <Arbiter> sigh sob nobody reviews my packages :D
[07:04] <bddebian> Arbiter: I didn't?
[07:04] <Arbiter> bddebian: i meant... me 'new' packages :D
[07:05] <Arbiter> kcmpureftpd for example :D
[07:05] <bddebian> I'm working on it, I'm working on it :-)
[07:05] <Arbiter> s/me/my
[07:06] <Arbiter> bddebian: thanks :)
[07:39] <Sp4rKy> i've a stange thing in one of my package
[07:40] <Sp4rKy> the deb contains normal files (/usr/...) but also contains debian/foo/... files
[07:40] <azeem> what is the full pathname to the foo files?
[07:42] <Sp4rKy> azeem, i've ./debian/eutils/usr/bin/e17genmenu
[07:42] <Sp4rKy> and usr/bin/e17genmenu
[07:42] <Sp4rKy> for example
[07:43] <azeem> so "/debian/eutils/usr/bin/e17genmenu" is inside the .deb?
[07:44] <Sp4rKy> yes
[07:44] <azeem> Sp4rKy: how did you invoke the .deb building process? pbuilder?
[07:44] <Sp4rKy> and /usr/bin/e17genmenu" to
[07:44] <azeem> the latter looks fine
[07:44] <Sp4rKy> yes
[07:44] <azeem> hrm, duno
[07:44] <azeem> gotta run now as well
[07:44] <Sp4rKy> ...
[07:47] <Sp4rKy> any idea ?
[07:49] <welshbyte> bddebian: i'm gonna grab some dinner... might look at those syncs/merges later if you're still around
[07:50] <bddebian> welshbyte: You ROCK man :-)
[07:50] <bddebian> welshbyte: Oh, I'm gonna upload your gnu-smalltalk btw :-)
[07:51] <welshbyte> bddebian: oh i meant to ask about that... could you check i put my name in all the right places? i put it in debian/changelog but left the maintainer name in debian/control and copyright the same
[07:53] <bddebian> welshbyte: Will do
[07:53] <welshbyte> bddebian: thanks, btw :)
[07:55] <bddebian> welshbyte: No, THANK YOU!
[07:59] <bddebian> welshbyte: Uploaded
[08:08] <bddebian> Heya carthik
[08:08] <carthik> hi bddebian
[08:12] <bddebian> Arbiter: Still around?
[08:14] <Arbiter> bddebian: here I am
[08:14] <Arbiter> but i have to go shortly
[08:17] <imbrandon> siretart: ping
[08:19] <Arbiter> bddebian: i have to go...
[08:19] <Arbiter> see you later
[08:20] <imbrandon> any revu admins alove ?
[08:20] <imbrandon> alive*
[08:30] <bddebian> Gah
[08:58] <bddebian> heh
[09:02] <aigarius> who should I talk to about a sync request for sbackup (sid->edgy)? also people want a backport to dapper-updates.
[09:03] <crimsun> dapper-updates isn't for backports
[09:03] <Mez> backports?
[09:04] <aigarius> well, there is n need to change anything
[09:04] <aigarius> in the code I mean
[09:04] <crimsun> file a bug using Malone against sbackup, then subscribe ubuntu-archive
[09:04] <crimsun> (for the sync from Sid)
[09:05] <aigarius> ok
[09:05] <aigarius> is there an automatic sync for universe packages? how long does that take?
[09:05] <bddebian> If you are sure it works and there are no Ubuntu changes
[09:06] <crimsun> no, it's no longer automatic. That stopped as of UVF.
[09:06] <crimsun> main's UVF, that is
[09:06] <aigarius> ah, I missed the UVF announcement
[09:06] <tseng> it was some time ago
[09:06] <tseng> edgy is a very short cycle
[09:08] <Sp4rKy> re
[09:08] <Sp4rKy> i've always my strange issue with one apckage
[09:08] <Sp4rKy> i've all files in /usr/* and in /debian/foo/usr/*
[09:09] <AnAnt> I want to compile elinks against python
[09:09] <AnAnt> and I put python-dev in Build depends
[09:10] <AnAnt> but yet it cannot detect libpython.so, because python2.4-dev puts libpython2.4.so without any libpython.so link
[09:10] <AnAnt> any solution for this ?
[09:16] <AnAnt> hmm
[09:16] <trappist> what to do when I change about 30 lines in a source pkg and do debuild -S and the debdiff is 30k lines long
[09:16] <crimsun> trappist: use filterdiff(1)
[09:16] <trappist> it shouldn't do that, right?
[09:16] <bddebian> AnAnt: What is trying to detect it, configure?  And if so, how?
[09:16] <trappist> crimsun: thanks
[09:16] <crimsun> AnAnt: fix elinks's configure.ac if it uses one.
[09:16] <AnAnt> bddebian: yes configure
[09:17] <AnAnt> bddebian: well, configure script has this -lpython
[09:17] <crimsun> and that's broken, so fix the configure script.
[09:17] <AnAnt> thre is configure.in
[09:17] <AnAnt> why is it broken ?
[09:18] <crimsun> because there is no such libpython.a
[09:18] <crimsun> therefore -lpython will fail utterly
[09:20] <AnAnt> is there a reason for not having a symbolic libpython.so pointing at the installed python library ?
[09:20] <bddebian> AnAnt: What if I have python2.3 and python2.4
[09:20] <AnAnt> ok
[09:22] <crimsun> see the new python-gobject? That's you!
[09:22] <trappist> crimsun: filterdiff isn't going to solve this problem.  debuild -S did a LOT of unexpected work.  unless you have another suggestion, I'm just going to diff my changes against a pristine source package
[09:23] <bddebian> crimsun: ??  He didn't fix dsextras.py afaik
[09:23] <crimsun> trappist: why wouldn't filterdiff work?
[09:23] <crimsun> trappist: pipe debdiff through filterdiff -i
[09:24] <crimsun> or -x if you want to use the opposite
[09:24] <trappist> crimsun: I can eliminate unwanted files, but that only solves about 20% of the problem.  for the rest, I'd need to know what lines to include or exclude, and I don't have a way to do that for the 30 or so patched files without way more work than I'm interested in doing
[09:25] <crimsun> I presumed you were using sane, pristine source, but ok.
[09:25] <trappist> I was
[09:26] <trappist> I did apt-get source, changed one line apiece in about 30 files, and got a 30k-line debdiff
[09:26] <trappist> it's never happened to me before
[09:27] <crimsun> looks like something's being (re)generated in the clean target
[09:27] <crimsun> 30k is quite excessive, though
[09:27] <crimsun> how are you generating the debdiff?
[09:28] <trappist> I say debuild -S, cd .., debdiff *.dsc
[09:29] <crimsun> what does debian/rules::clean have?
[09:29] <AnAnt> anyone knows what is that "sysconfig" in python ? is it some sort of class ?
[09:30] <trappist> crimsun: dh_testdir, make clean and distclean, rm -rf build, and dh_clean debian/lotsofstuff
[09:31] <crimsun> I wonder if upstream's make *clean is doing something nasty.
[09:31] <trappist> crimsun: I can see when I run debuild -S that a ./configure is being run
[09:31] <crimsun> perhaps timestamp skew?
[09:31] <crimsun> ouch, yeah, timestamp skew
[09:31] <trappist> crimsun: the package is apt
[09:32] <crimsun> the _source_ is apt?
[09:32] <trappist> yes
[09:32] <crimsun> ping mvo, then
[09:32] <trappist> ok, thanks - so it's true, it shouldn't be doing this
[09:33] <crimsun> apt may have its own bag of beans, in which case mvo would probably know why
[09:33] <AnAnt> I was once told that there is a python policy
[09:33] <trappist> ok
[09:33] <AnAnt> anyone knows the URL for it ?
[09:33] <crimsun> http://www.debian.org/doc/packaging-manuals/python-policy/index.html
[09:37] <AnAnt> thanks
[09:38] <crimsun> bddebian: is the ftbfs reproducible with 2.11.3-0ubuntu1?
[09:38] <bddebian> crimsun: I haven't tried it yet because the source wasn't on packages.ubuntu.com
[09:38] <bddebian> yet
[09:38] <crimsun> it has to be, since ... Setting up python-gobject (2.11.3-0ubuntu1) ...
[09:39] <crimsun> i386, btw.
[09:41] <AnAnt> the standards version should be 3.7.2, right ?
[09:42] <welshbyte> bddebian: so, what needs doing to ipac-ng?
[09:45] <bddebian> welshbyte: Need to pull the latest from Debian and see what Ubuntu changes (if any) need to be merged package into it
[09:45] <bddebian> crimsun: Oh, hmm
[09:45] <bddebian> Damn, I think there almost as many specs as there are bugs
[09:46] <gnomefreak> ok what am i missing :( why can some people get nvidia to work and i cant
[09:47] <gnomefreak> is there a differnt package that edgy needs that dapper didnt?
[09:48] <crimsun> more details and fewer vague handwaving, please
[09:52] <bddebian> \O/
[09:53] <bddebian>  /O\
[09:54] <AnAnt> ok, it worked !
[09:57] <AnAnt> why does one have to upload the orig tarball ?
[09:57] <AnAnt> if it already was uploaded before in REVU ?
[09:57] <gnomefreak> ok i got an mx4000 nvidia card and nvidia-glx installed and ran through the process 4 times and each time i choose nvidia as driver it doesnt start mainly i get the abi mismatch error
[10:00] <gnomefreak> hmmm
[10:01] <crimsun> afaik that "error" is just a warning
[10:01] <gnomefreak> wonders if i was missing libglitz-glx1
[10:01] <AnAnt> ?
[10:02] <gnomefreak> i thought it said [EE]  but i will check next time around after i install libglitz-glx1 and try
[10:03] <nixternal> crimsun: return: 206: Illegal number: -1
[10:03] <nixternal> ^^ flashplugin-nonfree
[10:03] <bddebian> crimsun: diacanvas still doesn't build.  seb128 told me that dsextras.py was unsupported :-(
[10:04] <AnAnt> why des one have to upload the orig tarball if it already was uploaded before in REVU ?
[10:07] <AnAnt> anyways, I'm on a dialup, and can't reupload the 3MB elinks orig tarball
[10:08] <AnAnt> so I uploaded the diff, dsc & changes file only
[10:08] <AnAnt> I hope that's ok
[10:08] <crimsun> no, since -sa requires the orig.tar.gz, too.
[10:09] <AnAnt> crimsun: I did -sd
[10:09] <crimsun> -sd?
[10:10] <AnAnt> from dpkg-buildpackage manpage: -sa forces the inclusion of the original  source;  -sd  forces  its  exclusion  and includes only the diff.
[10:12] <crimsun> yes, but you _cannot_ use -sd
[10:12] <AnAnt> yes, I just found that out !
[10:12] <AnAnt> the orig tarball previously uploaded is gone !
[10:13] <AnAnt> it will take ages to upload a 3MB tarball
[10:13] <crimsun> it takes me about 30 mins
[10:19] <Sp4rKy> nobody could help me with my debian/ in .deb
[10:28] <cr3> how can I recommend a package for sponsoring?
[10:44] <gnomefreak> do we package nvidia-glx or does nvidia send it already packaged?
[10:45] <gnomefreak> nvm wrong package anyway :(
[10:55] <bddebian> ggaaaahhh
[10:59] <bddebian> cr3: What do you mean by sponsoring?
[11:02] <bddebian> Heya LaserJock
[11:04] <welshbyte> boom
[11:04] <bddebian> bang
[11:05] <welshbyte> how can i re-check a man page after lintian told me there was an error in it?
[11:05] <welshbyte> don't really want to build the package again
[11:06] <bddebian> Unfortunately you can't as far as lintian is concerned.  At least afaik
[11:07] <welshbyte> bah
[11:24] <ryanakca> welshbyte: what... you want to look at the man page? man ./appname.number
[11:25] <bddebian> Later folks
[11:25] <welshbyte> ryanakca: no, i wanted to get the warnings and errors about man pages that lintian gives without having to run lintian
[11:25] <welshbyte> and i've just figured out how to do it :)
[11:26] <ryanakca> ooh... how?
[11:26] <ryanakca> this might save me some time down the read
[11:26] <ryanakca> s/read/road
[11:26] <welshbyte> man -lT <manpage> | grep warning
[11:26] <ryanakca> welshbyte: nice.. what are you packaging? kde or gnome or cli?
[11:27] <welshbyte> i'm just having a look at some merges at the moment
[11:28] <ryanakca> ah
[11:29] <welshbyte> actually
[11:29] <AnAnt> lionelp: ok, I added elinks-full package to elinks source package, please have a look at it
[11:30] <welshbyte> man -lT manpage > /dev/null might be better
[11:30] <lionelp> AnAnt: I will
[11:30] <AnAnt> lionelp: thanks
[11:30] <lionelp> the problem is that it should go in main
[11:30] <AnAnt> lionelp: elinks-full too ?
[11:30] <lionelp> and it is not doable by a MOTU :)
[11:30] <lionelp> (the source at least)
[11:31] <AnAnt> lionelp: well, it did contain an elinks-lite since dapper
[11:31] <AnAnt> lionelp: and they used to put the elinks-lite in universe it seems
[11:31] <lionelp> binary yes
[11:31] <lionelp> not source
[11:31] <AnAnt> lionelp: that's according to aptitude "Section: universe/web"
[11:32] <AnAnt> yes, so what ?
[11:32] <AnAnt> I think just as they handled elinks-lite they will handle elinks-full
[11:33] <AnAnt> the only feature I couldn't compile is FSP support
[11:33] <AnAnt> because it needs a package that doesn't exist
[11:34] <lionelp> note that elinks-lite is not Ubuntu specific
[11:34] <lionelp> it comes from Debian
[11:34] <AnAnt> lionelp: are you sure ? I don't think I saw it in Debian
[11:35] <lionelp> I have juste checked
[11:35] <lionelp> http://packages.qa.debian.org/e/elinks.html
[11:35] <AnAnt> oh yes, indeed
[11:36] <AnAnt> well, ok
[11:37] <AnAnt> btw, do you mean the REVU is not for main packages ?
[11:37] <lionelp> AnAnt: yes
[11:38] <AnAnt> oh
[11:38] <AnAnt> what should I do then ?
[11:39] <lionelp> hum... not sure of what you have to do
[11:39] <lionelp> maybe sending a mail to ubuntu-motu will be a first step and you will have more point of view
[11:40] <AnAnt> REVU is not for multiverse either, right ?
[11:40] <lionelp> it can be for multiverse
[11:40] <AnAnt> then why the acroread package was removed ?
[11:42] <lionelp> It was not removed
[11:42] <lionelp> it was archived
[11:42] <AnAnt> oh, what does that mean ?
[11:42] <lionelp> Archied upload are packages that are not under work
[11:43] <lionelp> (for different reasons: uploaded, no answer from the uploader)
[11:43] <AnAnt> so what should I do about that ?
[11:43] <lionelp> http://revu.tauware.de/details.py?upid=2542 -> you will have the reason why it has been archived
[11:43] <AnAnt> ok
[11:44] <CarlFK> can someone review https://help.ubuntu.com/community/UpdatingADeb - I am about to use to to update mplayer - rather tweak before the run through
[11:44] <AnAnt> but debian doesn't have acroread , or does it call it another name
[11:44] <AnAnt> ?
[11:45] <micahcowan> apt-cache search acroread shows it for me
[11:45] <AnAnt> micahcowan: in debian ?
[11:45] <AnAnt> micahcowan: what's the package called ?
[11:46] <micahcowan> No, I'm running Ubuntu 6.06.
[11:47] <lionelp> AnAnt: it is said "Debian Multimedia" not "Debian" :)
[11:47] <AnAnt> oh
[11:47] <AnAnt> I didnt know that there is a difference
[11:47] <micahcowan> where would you look for that, instead of in packages.debian.org?
[11:47] <lionelp> It is another repository (not official) : http://www.debian-multimedia.org/
[11:48] <AnAnt> ok, back to elinks, you said I should send an email, what's the email address, and what should I say there ?
[11:48] <AnAnt> and what can they do ? as you mentioned that MOTUs  can't upload to main.
[11:50] <LaserJock> A MOTU can certainly review packages, etc.
[11:52] <lionelp> LaserJock: did you follow the discusion?
[11:53] <LaserJock> not a whole lot :-)
[11:53] <AnAnt> lionelp: ubuntu-motu@lists.ubuntu.com ?
[11:53] <lionelp> Ok, quickly : AnAnt uploaded a modified version of the elinks package on REVU (with other options)
[11:53] <lionelp> AnAnt: yes
[11:53] <AnAnt> lionelp: can a launchpad member send to it ?
[11:54] <LaserJock> ok
[11:54] <lionelp> elinks is in main (the source and the package) and the source also generate a elinks-lite in universe
[11:54] <lionelp> I do not realy know what we should do with this
[11:54] <LaserJock> hmm
[11:55] <LaserJock> ping a core-dev
[11:55] <lionelp> easy situation, isn't it ? :)
[11:55] <LaserJock> I'd ask mdz or somebody like that
[11:56] <lionelp> AnAnt: try to ping someone on #ubuntu-devel
[11:56] <AnAnt> there are many there
[11:57] <crimsun> what's the issue?
[11:57] <lionelp> crimsun: : AnAnt uploaded a modified version of the elinks package on REVU (with other options)
[11:57] <lionelp> elinks is in main (the source and the package) and the source also generate a elinks-lite in universe
[11:58] <crimsun> yes, but what's the issue?
[11:58] <crimsun> as long as the work is done against 0.11.1, it's fine
[11:58] <crimsun> should be fairly trivial to merge the work into 0.11.1-1ubuntu2 and upload
[11:59] <lionelp> packages on REVU and most of reviewer are MOTU
[11:59] <lionelp> if you think this can go in main, this is fine
[11:59] <lionelp> that is the question
[11:59] <crimsun> we'll look later
[11:59] <crimsun> are the changes against the current edgy/main source?
[12:00] <crimsun> (0.11.1-1ubuntu2)
[12:00] <AnAnt> yup
[12:00] <AnAnt> crimsun: yup
[12:00] <crimsun> then a few of the more experienced MOTU should look
[12:00] <AnAnt> so should I send an email to ubuntu-motu mailing list or not ?
[12:01] <crimsun> about reviewing it?
[12:01] <AnAnt> err, dunno
[12:01] <AnAnt> maybe
[12:01] <crimsun> I personally wouldn't send an e-mail, but if you think it will help, sure, go ahead
[12:02] <AnAnt> k, I sent email
[12:03] <lionelp> AnAnt: you can add a comment to your upload on REVU that will send an e-mail to motu-reviewer ML
[12:03] <AnAnt> lionelp: cannot add comment, recover page is not working
[12:03] <AnAnt> btw, what is ML ?
[12:04] <lionelp> motu-reviewers (at) tauware (dot) de
[12:04] <AnAnt> oh mailing list
[12:04] <lionelp> ah, sorry, I did not catch you question
[12:05] <AnAnt> hehe
[12:05] <lionelp> yes, you understand it well:)
[12:05] <AnAnt> crimsun: so generally if I do changes to a main package I can send it to REVU ?
[12:06] <crimsun> AnAnt: sure, but realise that you'd be addressing an even smaller group of people who can (and have resources) to review, approve, and upload
[12:07] <AnAnt> ok
[12:07] <crimsun> given the backlog on universe packages, don't be surprised if nothing ever happens for main ones
[12:07] <AnAnt> well, it's way past midnight, gotta go sleep
[12:07] <AnAnt> crimsun: oh , ok
[12:09] <gnomefreak> crimsun: let me know when you get a min i have error i dont understand