[12:31] <minghua> siretart: if I want to get reviewer priviledge on REVU, are you the right person to ask?
[12:34] <siretart> minghua: yes. tell me your login id
[12:35] <minghua> siretart: minghua@rice.edu
[12:37] <siretart> minghua: try reviewing now
[12:42] <bddebian> Heya gang
[12:42] <Erlang> lo
[12:43] <minghua> siretart: forgot to bring my gpg key with me :-(  will test as soon as possible, thanks!
[12:43] <minghua> hi bddebian
[12:43] <bddebian> Hello Erlang, minghua
[12:43] <siretart> minghua: you should be able to comment on any upload now
[12:45] <minghua> siretart: good, that's all I need.  I'll test later.
[12:48] <hub> what's wrong with upstream no willing to check for a required library in configure?
[12:59] <siretart> hub: they have no clue or interest? ;)
[01:00] <hub> that is what I think
[01:01] <hub> https://savannah.nongnu.org/bugs/index.php?func=detailitem&item_id=16159
[01:01] <hub> I'm packaging this library to get sflphone after
[01:01] <hub> (a friend of mine work on sflphone)
[02:11] <minghua> welcome back LaserJock :-)
[02:12] <ajmitch> hi
[02:12] <minghua> hi ajmitch
[02:16] <LaserJock> hi minghua and ajmitch
[02:16] <raphink> hi ajmitch minghua LaserJock
[02:17] <LaserJock> hi raphink ;-)
[02:17] <raphink> :)
[02:17] <raphink> I get 19000 karma today
[02:17] <raphink> I had 500 yesterday
[02:17] <ajmitch> raphink: it got adjusted :)
[02:17] <LaserJock> 12177 for me, woot!
[02:17] <raphink> ajmitch hehe nice :)
[02:18] <raphink> well it's just fair that devs get more karma than translators ;)
[02:18] <Erlang> I went from 94 to 3400 something yesterday.
[02:18] <ajmitch> 65765 now :)
[02:18] <raphink> specs give the most karma
[02:18] <ajmitch> yeah
[02:18] <ajmitch> and you can write specs on your own products :)
[02:18] <raphink> riddell got up to 111k
[02:18] <raphink> with lots of specs
[02:18] <raphink> ajmitch hehe ;)
[02:18] <LaserJock> "to infinity and beyond!"
[02:18] <raphink> at least it's logical
[02:18] <ajmitch> raphink: one of the top 5 has about 15 specs on some product he works on
[02:18] <raphink> you won't think a translator is "more active" than a core-dev anymore ;)
[02:19] <raphink> hehe
[02:19] <Erlang> I just started triaging like 2 weeks ago.  I didn't know triaging was that valuable.
[02:19] <ajmitch> especially as karma has some value for ubuntu affiliates & partners now..
[02:19] <raphink> Erlang: it wasn't, so far
[02:19] <ajmitch> raphink: still no karma for uploads though
[02:20] <raphink> ajmitch that will come, hopefully
[02:20] <LaserJock> ajmitch: no? that stinks
[02:20] <raphink> there should be karma for package maintenance and uploads
[02:20] <raphink> and more karma for main packages
[02:20] <raphink> obviously
[02:20] <ajmitch> " Launchpad Activity
[02:20] <ajmitch> 
[02:20] <ajmitch> 5 points for each full time employee in the top 100 Launchpad users at the time application is made."
[02:20] <ajmitch> for the ubuntu partners programme
[02:20] <Erlang> I need some advice on bug: 32159.  It look important to me.
[02:20] <minghua> yeah there have been karma inflation recently :-)
[02:21] <ajmitch> raphink: there'd also be karma for branch commits once we switch to hct, too
[02:21] <ajmitch> so that not only the uploader gets karma
[02:21] <raphink> good :)
[02:21] <raphink> at least it's good to have a nice karma :)
[02:21] <ajmitch> why should I get huge karma for sponsoring 100 uploads, for example?
[02:22] <raphink> somehow it was frustrating to keep having a karma under 1000
[02:22] <ajmitch> yeah
[02:22] <ajmitch> my karma did get over 2K with the old numbers
[02:22] <raphink> nice :)
[02:22] <raphink> mine was at 500 currently
[02:23] <LaserJock> ajmitch: is there a URL that describes how much karma for each activity
[02:23] <ajmitch> LaserJock: nope, they don't want to encourage people doing things just for karma points ;)
[02:24] <raphink> hehe
[02:24] <raphink> that's safe
[02:25] <ajmitch> so I encourage people to just keep bug fixing & uploading :)
[02:25] <ajmitch> we have a large pile of bugs
[02:26] <ajmitch> and a growing number of complaining users who don't like their bugs being ignored :)
[02:26] <ajmitch> malone doesn't help sometimes..
[02:26] <raphink> it's not useful
[02:26] <raphink> the search functions are not very good so far
[02:27] <ajmitch> s/not very good/often horrible/
[02:27] <raphink> yes indeed
[02:30] <ajmitch> raphink: caught up on the KDE upload backlog?
[02:30] <raphink> how do you mean?
[02:30] <ajmitch> wasn't there a large pile of KDE fixes to get uploaded?
[02:31] <ajmitch> and you wanted into main so you could help out, and keep the pile down?
[02:31] <raphink> hmm not right now
[02:31] <raphink> I wanted into main to be able to apply fixes directly and sponsor uploads if needed
[02:31] <raphink> to help out
[02:31] <raphink> ;)
[02:31] <ajmitch> right
[02:31] <raphink> I did a few fixes last week
[02:31] <raphink> on k3b, systemsettings and others
[02:32] <raphink> saved time to riddell for sure as I could just fix them and upload
[02:34] <ajmitch> hi hub
[02:35] <ajmitch> hm, how many people know the rules we agreed on for fixing/patching debian packages for dapper?
[02:36] <ajmitch> eg not adding dpatch, not making gratuitous changes?
[02:36] <raphink> it's stated clearly on the wiki iirc
[02:36] <ajmitch> sure, but is it clear enough?
[02:37] <raphink> not sure
[02:37] <hub> ajmitch: I don't know the rules, but I usually do common sense
[02:37] <ajmitch> there's a few fixes assigned to motureviewers, we'd want to check them
[02:37] <ajmitch> hub: sure
[02:37] <hub> ajmitch: is it easy to become debian developer?
[02:37] <ajmitch> we got a few complaints from debian for adding dpatch, etc
[02:37] <ajmitch> hub: it's long & painful :)
[02:37] <hub> :-/
[02:38] <raphink> yeah :(
[02:38] <hub> 'cause otherwise I would just package there and sync in universe
[02:38] <raphink> even ian murdock is still waiting
[02:38] <raphink> LOL
[02:38] <hub> LOL
[02:38] <raphink> not kidding
[02:38] <raphink> he's in the list
[02:38] <raphink> not done with the NM process
[02:38] <ajmitch> hub: average wait just to get an AM assigned is around 6 months at the moment
[02:39] <hub> AM?
[02:39] <ajmitch> application manager
[02:39] <hub> ah
[02:39] <raphink> hub: https://nm.debian.org/nmlist.php
[02:39] <ajmitch> who sends you questions, reviews what you do, etc
[02:39] <hub> so I just should forget
[02:39] <ajmitch> (s)he files a report for the front desk
[02:39] <raphink> hub: see how many people you know in this list ;)
[02:39] <hub> it is more the cathedral than the bazaar
[02:39] <ajmitch> who approves & then passes it onto the debian account manager for processing :)
[02:40] <ajmitch> all this may take > 1 year on average
[02:40] <raphink> yet there are some awful packages in Debian ...
[02:40] <ajmitch> sure
[02:40] <raphink> it seems to me that the awful packages are not from DDs themselves
[02:40] <raphink> but rather DDs sponsoring bad packages
[02:40] <raphink> without reviewing well enough
[02:40] <raphink> so it's a lack of review from DDs on other contributors' work
[02:41] <raphink> more than a bad work from DDs themselves
[02:41] <raphink> or so it seems to me
[02:42] <ajmitch> yeah
[02:42] <ajmitch> DDs aren't perfect ;)
[02:42] <raphink> of course :)
[02:42] <bddebian> They aren't?
[02:42] <crimsun> no, only bddebian is.
[02:42] <raphink> I'd like my reviewing guide to be read by some DDs, improved and spread
[02:42] <raphink> lol
[02:43] <crimsun> ow.
[02:43] <raphink> ouch
[02:43] <ajmitch> bddebian: play nice
[02:43] <hub> raphink: I wonder if I shouldn't sit and write a complete Debian Packager Guide
[02:43] <ajmitch> complete?
[02:43] <bddebian> ajmitch: Oh sure, don't make him be nice to me.. :-)
[02:43] <hub> ajmitch:600pages
[02:43] <ajmitch> do you have 10 years?
[02:43] <raphink> hub: LaserJock is doing it
[02:43] <raphink> for ubuntu
[02:43] <hub> raphink: oh
[02:44] <raphink> hub: if you want to help just talk to him
[02:44] <hub> raphink: ok
[02:44] <LaserJock> sorry, I was writing an email
[02:44] <hub> I still have to schedule time
[02:44] <raphink> ajmitch: indeed
[02:44] <hub> LaserJock: it is OK
[02:44] <hub> maybe I should just write code
[02:44] <LaserJock> hub: right now, what I've got is at doc.ubuntu.com
[02:45] <hub> LaserJock: ok
[02:45] <LaserJock> hub: you are certainly welcome to contribute :-)
[02:45] <hub> I was more thinking "for hardcopy printing"
[02:45] <LaserJock> hub: in fact right now it is just me and I have a deadline
[02:45] <hub> LaserJock: oh
[02:45] <LaserJock> hub: it is also shipped on the cds
[02:45] <LaserJock> hub: it is a part of the ubuntu-docs package
[02:45] <LaserJock> hub: you can view it in the Gnome or KDE help
[02:46] <LaserJock> although the KDE version is quite old I think
[02:46] <hub> and in devhelp? :-)
[02:47] <LaserJock> I don't think so
[02:47] <hub> could be usefull
[02:47] <hub> and not hard to do
[02:47] <LaserJock> although I just got all the ubuntu docs into the doc-base registry
[02:47] <hub> I'll investigate
[02:47] <LaserJock> do you can view it with dwww or doc-central
[02:48] <raphink> hub: a hardcopy printing would be nice... but how many people would buy that?
[02:48] <hub> raphink: not sure. that is more "the publisher business"
[02:48] <crimsun> I would, but I'm a corner case. I really dislike reading from a screen.
[02:48] <hub> worst case scenario it would just be online
[02:48] <hub> crimsun: I would too
[02:48] <raphink> crimsun: same here
[02:48] <raphink> hmm sure
[02:48] <LaserJock> same here
[02:49] <hub> in fact I have to much book to move in less than 2 month
[02:49] <hub> *sigh*
[02:49] <raphink> I think a publisher most likely would refuse publishing this
[02:49] <ajmitch> I wouldn't, but that's because I'm unlikely to spend money on a packaging guide
[02:49] <raphink> but it's worth writing
[02:49] <ajmitch> certainly worth writing
[02:49] <hub> raphink: O'Reilly or No Starch comes to mind
[02:49] <LaserJock> ajmitch: well, I'd *read*. I'm not committing to buying  ;-)
[02:49] <raphink> sure hub
[02:49] <hub> but that is not the problem
[02:49] <BrianG> can anyone here "pull in a new package" of BitTornado 0.3.15 so that it can be included into Breezy backports?
[02:49] <hub> would be refused, I would put it online
[02:50] <BrianG> https://lists.ubuntu.com/archives/ubuntu-backports/2006-March/000760.html
[02:50] <raphink> it can even be a book under Documentation GPL as "dive into python" with an online version and a printed one
[02:50] <crimsun> BrianG: we're way past upstream version freeze (UVF); you'd need to write a UVF exception
[02:50] <BrianG> i dont write things, i just ubuntu
[02:50] <crimsun> and because it's in main, the hurdle is much higher
[02:50] <BrianG> use*
[02:50] <BrianG> heh
[02:51] <softwarecommie> I just joined this channel; are you talking about documentation for packaging?
[02:51] <LaserJock> softwarecommie: yeah, somewhat
[02:52] <raphink> softwarecommie: currently, yes
[02:52] <softwarecommie> ok
[02:53] <raphink> ok well
[02:53] <BrianG> crimsun: how do i write a UVF? is that like some kind of form letter?
[02:53] <raphink> I'll head to bed
[02:53] <raphink> bye
[02:53] <crimsun> bye raphink
[02:53] <LaserJock> cya raphink
[02:54] <BrianG> UVF exception rather
[02:56] <crimsun> BrianG: https://lists.ubuntu.com/archives/ubuntu-motu/2006-February/000545.html
[02:56] <hub> to reply to raphink, who is gone, the ultimate goal would be to get it under both licenses
[02:57] <BrianG> crimsun: thanks
[02:57] <crimsun> BrianG: note that it's a main package, not a universe package.
[02:58] <BrianG> tell that to John Dong :)
[02:58] <crimsun> who's requesting it, he or you?
[02:58] <BrianG> what does that mean? i'm just basicly trying to use the new version of BitTornado
[02:58] <BrianG> me, but he sent me to MOTU
[02:59] <BrianG> do i have to be able to make the package myself in order to request a UVF exception?
[02:59] <crimsun> incorrect workflow
[03:00] <crimsun> no, but it sure helps if there is a Ubuntu package of it already
[03:00] <BrianG> ah
[03:00] <BrianG> so i'm totally in limbo and not really sure what i'm doing
[03:00] <BrianG> should i go and report a bug?
[03:01] <Amaranth> it's probably too late to get a new bittornado into dapper
[03:01] <Amaranth> so it can't go into backports either
[03:01] <crimsun> BrianG: yes, file a bug, but be aware that you're dealing with a main package
[03:01] <BrianG> so i'm barred from the tracker i use untill October?
[03:01] <crimsun> barred? no one's barred
[03:02] <BrianG> what's that mean.. a main package?
[03:02] <BrianG> well i am from the tracker..
[03:02] <BrianG> they refuse any old versions of bittornado
[03:02] <crimsun> we (MOTU) only handle universe and multiverse packages
[03:02] <BrianG> okay
[03:02] <crimsun> (a few of us have main upload rights, but that's a small fraction)
[03:03] <crimsun> the process for requesting a UVF exception differs slightly between main and universe/multiverse packages
[03:03] <BrianG> so i shouldn't have been sent to MOTU in the first place, right?
[03:03] <BrianG> being that it's a main package
[03:03] <crimsun> you've seen the directions for the latter. For the former, you still need the information, but you have to ask one of the core devs (mdz iirc)
[03:04] <crimsun> right, you were misdirected (hence, "incorrect workflow")
[03:04] <BrianG> thanks for the information
[03:07] <LaserJock> hi minghua
[03:07] <minghua> hi LaserJock and everyone
[03:08] <crimsun> 'lo minghua
[03:08] <yves> hi
[03:09] <LaserJock> minghua: do you use KDE at all?
[03:10] <minghua> LaserJock: not really.  all my KDE usage is for testing scim
[03:10] <LaserJock> ok fine
[03:30] <softwarecommie> does anyone here know of something I may be able to work on or where I can go to find something?
[03:31] <crimsun> softwarecommie: we have thousands of bugs awaiting your triage skills in https://launchpad.net/distros/ubuntu/+bugs
[03:34] <softwarecommie> looks good, thanks
[03:48] <Kyral> ....I hate GCC 4 right now
[04:09] <nictuku> could someone please review 2176 in REVU?
[04:11] <crimsun> it's native?
[04:12] <nictuku> ubuntu native, you mean?
[04:12] <nictuku> it's a universe candidate-candidate
[04:12] <crimsun> or debian-native, irrelevant, really
[04:12] <crimsun> but is it from upstream or your own made-for-{Debian,Ubuntu} package?
[04:13] <nictuku> I am upstream and debianized it
[04:13] <crimsun> are you _positive_ you want -X in the version, then?
[04:14] <crimsun> normally if it's native, you'd make it 0.3, not 0.3-1
[04:14] <nictuku> hmm I'll read about that in the policy then
[04:14] <nictuku> thank you
[04:15] <crimsun> also, change the target distribution
[04:15] <crimsun> [unless you're packaging specifically for Debian Sid and want to sync it over] 
[04:16] <nictuku> ok
[04:16] <crimsun> don't build-dep on build-essential
[04:16] <minghua> nictuku: I find that both debian/control.in and debian/control exist
[04:17] <nictuku> doesn't control.in creates control everytime by cdbs?
[04:17] <minghua> nictuku: are you sure that's desired (I don't know anything about cdbs)?
[04:17] <crimsun> yes, and if cdbs is adding build-essential, that's /nasty/
[04:17] <nictuku> I guess I did
[04:18] <crimsun> years in copyright(s) == good
[04:18] <crimsun> looks ok for a cursory glance aside from those
[04:19] <nictuku> ah, btw,  if I use ${python:Depends}, it gets my default python for its dependency - python2.4. But the software is supposedly agnostic. Is there any problem to use manual values there?
[04:20] <nictuku> crimsun, years in copyright, you mean in debian/copyright or in the source files?
[04:20] <crimsun> both.
[04:20] <crimsun> notes added
[04:21] <minghua> it's good to talk to upstream directly, huh? :-)
[04:23] <crimsun> minghua: absolutely :)
[04:23] <nictuku> I'll abuse of your helpfulness and send some other packages I need reviewing too hehe
[04:27] <nictuku> https://dev.ubuntubrasil.org/trac/pycacic/ticket/16
[04:27] <crimsun> minghua: your suggestion of 1.1+revertedto+1.0.2 is fine
[04:27] <crimsun> RE: wesnoth
[04:29] <nictuku> what release should I use now? "dapper" ?
[04:29] <crimsun> nictuku: yes
[04:29] <crimsun> granted, there's always something akin to: xserver-xorg-input-synaptics           0.14.3+seriouslythistime-0ubuntu3
[04:29] <minghua> crimsun: okay, thanks.  not really my suggestion though (the OP's)
[04:31] <nictuku> crimsun, is it wrong, as mingua believes, to have both debian/control and debian/control.in in a cdbs package?
[04:31] <nictuku> *minghua
[04:32] <minghua> nictuku: I am just speculating :-)  as I've said I don't know anything aboug cdbs at all
[04:33] <crimsun> nictuku: it's not wrong per se, but it's certainly a bit cluttered
[04:33] <nictuku> yes, sorry, I got your point.
[04:34] <nictuku> strange thing is debian/rules clean does not delete debian/control, as I would expect
[04:36] <crimsun> clean::
[04:36] <crimsun>    rm -rf debian/control
[04:36] <crimsun> s/-rf/-f/
[04:36] <nictuku> how does universe updates work? will it only accept security updates when dapper is released?
[04:37] <crimsun> nictuku: essentially.
[04:37] <nictuku> hmm will do
[04:38] <minghua> security + critical bug fix (data loss, for example), I suppose
[04:38] <crimsun> yep
[04:38] <minghua> we have dapper-security _and_ dapper-updates after all
[04:41] <nictuku> clean:: rm -r debian/control is bad. dpkg-buildpackage does a clean *after* creating debian/control :-). I'll have to pick a better time for that
[04:42] <LaserJock> minghua: did you happen to read ubuntu-science today?
[04:43] <ajmitch> nictuku: why would you even consider removing it? :)
[04:43] <crimsun> nictuku: then use pre-clean
[04:43] <minghua> LaserJock: yes, actually just 20 minutes ago, and was admiring your persistence on the education/science issue :-)
[04:44] <LaserJock> minghua: lol, I'm starting to wonder if I'm totally out of my mind :-)
[04:44] <crimsun> of course you are, just like every grad student is/has been
[04:44] <LaserJock> well, at least I'm not alone
[04:44] <minghua> LaserJock: no you are not.  in principle I agree with you
[04:45] <nictuku> ajmitch, well the guys here made my mind about that. it's useless to distribute debian/control if you ahve debian/control.in
[04:45] <crimsun> nictuku: it's not useless, no
[04:45] <minghua> LaserJock: I just don't think it's worth discussing in detail before we really have the choice
[04:46] <LaserJock> minghua: well, it all got started because seb128 said he wouldn't add a Science menu until there were enough apps to populate it
[04:46] <nictuku> crimsun, that was my personal conclusion from what you guys tried to say, and I got it wrong again.. :-)
[04:46] <crimsun> nictuku: not wrong, just be careful with choosing extremes
[04:47] <ajmitch> nictuku: my personal opinion, shared by many, is that debian/control should never be rewritten automatically at build time
[04:47] <minghua> LaserJock: hmm, now I remeber you've told me that.  what happens if we have a .desktop with only Science, but not Education?
[04:47] <minghua> LaserJock: it will end up in menu "Others"?
[04:47] <LaserJock> minghua: usually it goes to Other :(
[04:48] <LaserJock> minghua: but I really hate having to put Education on a non-educational app just to get it out of Other
[04:48] <minghua> LaserJock: in that case I am on your side, Other is better than Education for research-only apps
[04:48] <nictuku> ajmitch, I should then make it static and stop cdbs from re-creating it. All changes I must make after that will go to debian/control... right?!
[04:49] <ajmitch> nictuku: that's one option
[04:49] <nictuku> it's prettier IMO
[04:49] <ajmitch> or you can use control.in, but only update it when you want to
[04:49] <ajmitch> which I don't like myself :)
[04:49] <LaserJock> minghua: and eventually if there are enough apps in Other than I can really have a case to ask seb128 for a Science menu and it would be quite trivial to do since the .desktop files would be in place
[04:49] <nictuku> DEB_AUTO_UPDATE_DEBIAN_CONTROL := yes           s/yes/no/ :-)
[04:50] <ajmitch> nictuku: yeah, that's evil stuff there
[04:50] <nictuku> I've even read that was not recommended, but I forgot it there
[04:51] <minghua> LaserJock: exactly.  and a long Other menu has more pressure than a long Education menu ;-)
[04:51] <minghua> nictuku: does that auto-update-debian/control rewrite the Build-Depends: line as well?
[04:52] <ajmitch> minghua: it will if @cdbs@ is used
[04:52] <LaserJock> does the 2nd item of http://ftp-master.debian.org/REJECT-FAQ.html have any baring on the debian/control issue?
[04:53] <nictuku> yes, replacing @cdbs@ for garbage, including "build-essential"
[04:53] <minghua> ajmitch, nictuku:  Hmm, I remember it's explicitly forbidden in Debian, let me check
[04:54] <nictuku> I've remove that as you guys recommended, anyway. And I agree it's really bad
[04:54] <nictuku> *removed
[04:55] <ajmitch> minghua: it is :)
[05:00] <minghua> ajmitch: good to be confirmed.  but I can't seem to find the reference :-(
[05:07] <minghua> the firefox in dapper (which used pango) is pretty broken for me
[05:13] <Se7h> hi
[05:13] <Se7h> LaserJock im with a 'litle' problem here
[05:16] <LaserJock> what's up Se7h
[05:17] <nictuku> sorry if I'm cluttering the revu notification mailing-list with my buggy and frequent dput's..
[05:18] <Se7h> LaserJock i've been unable to build this python library, cus it seems that after 'building X in ...'
[05:18] <G0SUB> minghua: which language?
[05:18] <Se7h> it wont find the python-dev files
[05:19] <Se7h> must be some 'trick i dont know
[05:19] <Se7h> lol
[05:19] <minghua> G0SUB: sorry, what are you refering to?  firefox?
[05:19] <nictuku> should I really mention nmu in my packages?
[05:19] <LaserJock> nictuku: not if it is for Ubuntu
[05:20] <minghua> nictuku: lintian warning?  just ignore it
[05:20] <nictuku> in a native package, I mean
[05:20] <nictuku> ok
[05:20] <G0SUB> minghua: yeah, firefox
[05:21] <LaserJock> Se7h: is python-dev a build-dep?
[05:21] <minghua> G0SUB: no, it doesn't has much to do with language, just slow rendering, jerky response, unusually small fonts, etc.
[05:21] <G0SUB> oh!
[05:22] <minghua> and all these go away if I use MOZ_DISABLE_PANGO=1
[05:24] <LaserJock> if you have remove non-free parts of a original tarball should you rename the package .dfsg. ?
[05:25] <Se7h> LaserJock a build-dep? how so ?
[05:25] <minghua> LaserJock: some rename the package name, some rename the version number, I don't think I've seen a consensus
[05:26] <LaserJock> Se7h: is it in the build dependencies of the source package?
[05:26] <LaserJock> minghua: but dfsg is the way to go?
[05:27] <minghua> LaserJock: well, maybe not, but dfsg definitely catches eyes, so that's probably the reason I see them :-P
[05:27] <Se7h> LaserJock oh right...forgot that part
[05:27] <Se7h> lol
[05:27] <minghua> LaserJock: I'm quite sure there are changes like from foo_1.2.3 to foo_1.2.3a
[05:27] <LaserJock> I'm just wondering if I should suggest it in the packaging guide
[05:28] <minghua> LaserJock: ask on #ubuntu-devel, perhaps?
[05:28] <minghua> it's even worth a mail to ubuntu-devel@l.u.c IMO
[05:28] <minghua> (if said package is not in debian, that is)
[05:29] <nictuku> I think REVU 2178 fixed all problems minghua and crimsun noticed in pycacic. thanks!
[05:30] <minghua> nictuku: what is the pycacic/control file for?
[05:31] <nictuku> oops
[05:31] <Se7h> LaserJock it was just that dumb me :p
[05:32] <nictuku> minghua, ornament :-)
[05:32] <nictuku> (fixed)
[05:33] <LaserJock> Se7h: well, hopefully it will work now
[05:35] <minghua> nictuku: you have the old FSF address in debian/copyright, but that's a minor issue
[05:35] <minghua> nictuku: I am not qualified to review python package though, so I can only check these cosmetic issues
[05:35] <nictuku> I really appreciate your help
[05:42] <nictuku> hmm Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA  02110-1301  USA
[05:49] <nictuku> for x in $(find .); do ~/fsf.sh $x;done  :-)
[05:52] <minghua> hi jaldhar
[05:58] <LaserJock> hi Hobbsee
[05:58] <Hobbsee> hi LaserJock
[06:01] <ajmitch> hey Hobbsee
[06:01] <Hobbsee> hey ajmitch
[06:36] <Se7h> LaserJock
[06:36] <Se7h> cp: omitting directory `examples/data'
[06:36] <Se7h> make: *** [install]  Error 1
[06:36] <Se7h> is that 'omitting' considered an error ?
[06:39] <nictuku> considered by what?
[06:39] <nictuku> "cp" will not return an error code, if that's what you ask
[06:40] <nictuku> it's a warning since cp didn't receive the -r parameter
[06:40] <Se7h> well yea, so why is it giving me an error  on pbuilder?
[06:40] <nictuku> and tried to cp a directory
[06:40] <nictuku> is it the only element being copied?
[06:41] <Se7h> no
[06:41] <Se7h> but everything else works fine
[06:41] <nictuku> indeed
[06:41] <nictuku> it does return an error code
[06:41] <nictuku> code 1
[06:44] <yves> I've just dput nwu to revu:2182
[06:44] <Se7h> nwu ?
[06:45] <yves> nwu is being written as request by a postponed spec for dapper
[06:45] <yves> could somone please take a look?
[06:46] <yves> it's a somewhat complex package - it took me and MarioMeyer many days of work
[06:47] <Se7h> whats nwu ?
[06:48] <yves> Network wide updates for systems which use APT.
[06:48] <yves> https://dev.ubuntubrasil.org/trac/nwu/wiki
[06:50] <Se7h> haum, looks nice
[06:51] <yves> thanks
[09:47] <dholbach> good morning
[09:59] <fabo> hi dholbach
[09:59] <fabo> robitaille: i replied about vtiger on the ML
[09:59] <dholbach> hey fabo
[10:02] <robitaille> fabo:  thanks.
[10:53] <phanatic> hi people
[11:14] <phanatic> hi people
[11:17] <Tm_T> moin
[11:18] <phanatic> hi Tm_T
[11:18] <Tm_T> no idea what I should do to Kopete package ;(
[11:18] <Tm_T> phanatic: hi
[11:41] <verwilst> hellow!
[11:41] <phanatic> hi verwilst
[11:41] <verwilst> if anybody has time to update pure-ftpd to the one in debian ( .21 ), i would be very grateful :d
[11:41] <verwilst> ( managers starting to nag :p )
[11:42] <verwilst> the uvf exception has been approved
[11:42] <verwilst> but i'm not a motu
[11:42] <verwilst> so i can't upload it myself :(
[11:42] <dholbach> verwilst: which bug was it
[11:42] <dholbach> verwilst: sorry, I didn't come around to do it yesterday and forgot
[11:42] <verwilst> hehe no problem :d
[11:42] <verwilst> euh
[11:42] <verwilst> lemme check
[11:43] <verwilst> 34346
[11:43] <dholbach> righto
[11:43] <dholbach> i'll do it now
[11:43] <verwilst> dholbach, cool, i owe you a beer ;)
[11:43] <verwilst> we have 1 apache server running here on dapper
[11:43] <verwilst> and customers have some probs with ftp ;)
[11:43] <dholbach> verwilst: nevermind... you did good work on it - so thank YOU!
[11:43] <verwilst> which will be fixed as soon as .21 is in dapper :)
[11:44] <verwilst> hehe np ;)
[11:46] <verwilst> we all benefit ;)
[11:47] <dholbach> i'll run a quick build through pbuilder to check
[11:47] <verwilst> yip
[11:47] <verwilst> doesn't take long to compile
[11:48] <dholbach> (only if you have abiword building in the meantime on the same box :-p)
[11:48] <verwilst> :p
[11:48] <verwilst> i've noticed network-manager 0.6.1 got into dapper
[11:48] <verwilst> sweetness
[11:48] <verwilst> dapper will rule so much :$
[11:49] <dholbach> and even more if you guys all show up on next friday's HUG DAY :)
[11:49] <verwilst> next friday?
[11:49] <verwilst> what time?
[11:49] <dholbach> yep
[11:49] <dholbach> all day
[11:49] <verwilst> oh
[11:49] <verwilst> i think i could help out a but
[11:49] <verwilst> bit
[11:49] <verwilst> ( hug or bug day? :p )
[11:49] <dholbach> http://wiki.ubuntu.com/UbuntuBugDay
[11:50] <verwilst> lol dholbach, freudian slip? :p
[11:50] <dholbach> "...in Ubuntu land every day is a hug day, but some hug days are special, they are bug days too..."
[11:50] <verwilst> heh :p
[11:50] <verwilst> damned hippies
[11:50] <verwilst> :d
[11:51] <phanatic> verwilst: lol :)
[11:51] <dholbach> pfffft
[11:51] <ajmitch> with flowers in his hair... ;)
[11:52] <dholbach> that's the spirit
[11:52] <verwilst> :)
[11:55] <dholbach> ajmitch: good thinking
[11:55] <ajmitch> dholbach: plus I want to see how fast this box can build ;)
[11:55] <phanatic> hi raphink
[11:55] <raphink> hi phanatic
[12:00] <dholbach> verwilst: uploaded
[12:13] <Toadstool> hi motus
[12:14] <ajmitch> hi
[12:23] <ajmitch> great, found 1 simple rebuild already
[12:29] <verwilst> dholbach, thanks a lot dude
[12:29] <verwilst> dholbach, how long till the mirrors update?
[12:32] <azeem> y
[12:32] <azeem> oops
[12:32] <ajmitch> hi azeem
[12:32] <azeem> hi Andrew :)
[12:41] <verwilst> dholbach, 1.0.21-1build1?
[12:41] <verwilst> shouldn't it be -1ubuntu1?
[12:41] <verwilst> :)
[12:50] <ajmitch> verwilst: not if it's taken without change from debian
[12:50] <verwilst> oh
[12:50] <verwilst> didn't know that :)
[12:51] <ajmitch> eg apt-rpm is uninstallable & can be fixed (if anyone actually cares ;) ) by a simple rebuild - so I'd upload with the only change being a changelog entry with build1 appended
[12:53] <ogra> initially the idea of -XbuildX was a different one, but sice autosyncing doesnt work in launchpad yet, we abuse it for syncs like that
[12:53] <ajmitch> ewblib currently underway..
[01:10] <ajmitch> azeem: interesting, ghemical doesn't build on AMD64?
[01:11] <ajmitch> ah, already reported in debian
[01:18] <azeem> ajmitch: yeah :(
[01:18] <azeem> I tried to take a look at it last week, but couldn't figure that C++ 64bit stuff out
[02:06] <TheMuso> dholbach: ping
[02:06] <dholbach> TheMuso: pong
[02:16] <Toadstool> ajmitch, azeem: about ghemical and amd64, there are 3 casts to change if you want it to build on amd64, 2 in src/view.cpp and 1 in src/camera.cpp
[02:16] <azeem> Toadstool: do you have a patch?
[02:16] <azeem> I couldn't figure out the last one
[02:17] <Toadstool> not yet but I can make one quickly
[02:17] <azeem> that would rock
[02:17] <Toadstool> 2 seconds then :)
[02:17] <azeem> Toadstool: can you mail the Debian and/or Ubuntu bug?  (I think there's a Malone bug filed as well)
[02:17] <azeem> I'm off now
[02:17] <Toadstool> ok
[02:17] <azeem> cheers, ta
[02:46] <siretart> Mez: around?
[02:51] <siretart> sorry, just a test
[02:51] <Toadstool> azeem: bug 36421
[02:51] <Ubugtu> Malone bug 36421 in ghemical "ghemical FTBFS on amd64" [Normal,Unconfirmed]  http://launchpad.net/bugs/36421
[03:41] <bddebian> Heya gang
[04:19] <siretart> crimsun: around?
[04:49] <siretart> crimsun: unping
[04:52] <bddebian> Heh
[04:53] <bddebian> Hey folks, anymore word about getting \sh some cashola?  I got an e-mail asking for my e-mail but haven't heard any more?
[04:58] <lucas> can I sync ruby-pkg-tools ? it's a small package used by the debian ruby team, but ruby packages depend on it
[05:00] <truz24> who is \sh?
[05:01] <bddebian> truz24: Stephan Hermann
[05:20] <Erlang> JDE has been NMUed in Debian to fix 4841.  Does that require a sync from Debian or I can just apply the NMU patch and upload to REVU?
[05:28] <bmonty> Erlang: if it is just a patch we can sync it from debian
[05:30] <Erlang> it's a few dozen line.
[05:31] <Erlang> it's reported as a major bug, is there any way I can indicate that it need to sync?
[05:32] <bmonty> we can do a "fakesync" of it...i.e. get the debian package, update the changelog for dapper, make sure that it builds on dapper and upload it
[05:33] <bmonty> if you want to make a debdiff of the updated package, I'll take a look at it
[05:34] <Erlang> will do
[05:34] <ogra> dont forget to merge ubuntu and debian changelogs ;)
[05:35] <bmonty> Erlang: also use -v<last ubuntu version> when you build the source package
[05:36] <Erlang> ogra: got an example?
[05:37] <bmonty> Erlang: see changelog for flashplugin-nonfree
[05:37] <bmonty> or do a search on dapper-changes for "fakesync"
[05:39] <ogra> https://wiki.ubuntu.com/MOTU/Packages/Merging
[05:39] <ogra> it has a section about the changelogs
[05:41] <Erlang> thank you.  I'll read that.
[05:42] <ogra> dpkg-genchanges -s -v<version> -sa is your friend as well :)
[05:43] <ogra> just make sure the changelog entries from the former ubuntu package dont get lost, you can even do it manually :)
[05:48] <bmonty> ogra: I think you have to bring in the old ubuntu changelog entries manually
[05:48] <bmonty> or is there a better way?
[05:51] <ogra> bmonty, the above :) its described in all the MOM reports
[05:51] <ogra> http://people.ubuntu.com/~scott/ongoing-merge/gnubiff/REPORT
[05:51] <ogra> for example
[05:52] <ogra> the genchanges should merge the changelogs
[05:55] <bmonty> ogra: ok, that is essentially how I do merges :)
[05:55] <ogra> good :)
[05:56] <ogra> but you can as well just move the last ubuntu changelog over and add the missing entries from the debian changelog ... its nearly no work
[05:56] <ogra> usually there are not many versions during 6 months :)
[05:58] <bmonty> ogra: I thought from your comment above that there was maybe some automated way to merge the changelogs I didn't know about
[05:59] <ogra> the dpkg-genchanges command described in the report, yes
[06:32] <slomo_> bmonty: hi... FYI, there are some UVF exceptions from you that need some additional informations
[06:32] <bmonty> slomo_: hmm, ok I'll look...I thought I had handled them all
[06:33] <slomo_> bmonty: https://launchpad.net/people/motu-uvf/+assignedbugs
[06:36] <Erlang> bmonty: Okay I've got the debdiff.  Shall I append as a patch to 4841 ?
[06:59] <bmonty> Erlang: yeah, please add the debdiff to the bug
[06:59] <Erlang> ok
[07:03] <Erlang> done.
[07:05] <bmonty> Erlang: I gotta go out for awhile, but I'll check it later this afternoon
[07:06] <Erlang> thank you.  take your time.
[07:15] <bmonty> Erlang: did you make this debdiff against the latest debian package?
[07:23] <bmonty> Erlang: I can't apply your debdiff against the 2.3.5-1.1 version of the debian package, did you use the debian package as the base for your debdiff?
[07:31] <Erlang> I've applied the patch from the BTS on the Ubuntu package.
[07:40] <Erlang> It's me that have to go now.  If the patch doesn't work leave it there and I'll redo it 'by the book' this afternoon.
[09:20] <Erlang> bmonty: are you there?
[10:05] <dolson> WHOA. my karma just jumped from ~250 to over 8000 in one day, WTF?
[10:10] <Gloubiboulga> dolson, I've read that working on bugs gives you more karma now
[10:10] <dolson> ah
[10:10] <LaserJock> dolson: karma was, umm, reworked
[10:10] <dolson> that's a LOT more karma
[10:16] <Erlang> yes karma was substancially reworked dolson.  some people are over 100k now.
[10:18] <Lure> Erlang: much more than 100k: https://launchpad.net/people/seb128 ;-)
[10:19] <Erlang> oh my
[10:19] <Erlang> does anybody here have time to explain me what is wrong with a diff I've made for JDE?
[10:23] <Erlang> ok. :D
[10:23] <LaserJock> wher is yhe diff?\
[10:24] <Erlang> https://launchpad.net/distros/ubuntu/+source/jde/+bug/4841
[10:24] <Ubugtu> Malone bug 4841 in jde "(dapper) jde 2.3.5-1 fails to install" [Major,Confirmed] 
[10:25] <Erlang> I've took the Debian NMU and applied it on the Ubuntu package.  bmonty was onto it but I had to leave.
[10:27] <LaserJock> Erlang: when you want a sync it is better to diff against the version you are wanting to sync
[10:28] <LaserJock> Erlang: and "should fix" isn't as encouraging as "fixes" ;-)
[10:30] <Erlang> ok I think I understand now.
[10:31] <Erlang> no, actually, I don't.
[10:33] <Erlang> LaserJock: anyway, is the patch appliable/acceptable? If not I'll simply redo-it By The Book.  I'm here to learn.
[10:36] <LaserJock> Erlang: I'd just take the Debian source and add your changelog entry (the version should be build1 not ubuntu1) and then build the source and debdiff
[10:37] <Erlang> okay.
[10:39] <Erlang> why build1 in this case?
[10:40] <Toadstool> good night here
[10:42] <LaserJock> Erlang: -Xbuild1 version I think is a lower version than -X so it will be automatically overridden for Dapper+1, or something to that effect anyway
[10:43] <sladen> Erlang: probably because syncs are broken
[10:43] <LaserJock> Erlang: if you do Xubuntu1 then it is a higher version than X
[10:43] <Erlang> That makes sense.
[10:47] <Erlang> got the new diff.
[10:57] <Erlang> ok, I've got a patch, but since this package has no Ubuntu-specific change to merge back, it's only my name and comments in the changelog... that sounds totally useless to put on Malone.
[11:01] <LaserJock> well, that is why usually a MOTU does that since it is sort of trivial
[11:01] <LaserJock> but it is useful to know that it builds in a current dapper pbuilder
[11:02] <Erlang> LaserJock: I guess that's why nobody was that enthusiastic when I said I wanted to patch earlier...
[11:03] <LaserJock> well, somebody has to figure out that we need a sync and that it works ok without any additional patches
[11:05] <Erlang> Is it bad, in any way, for me, for example, to build the package myself and make it available through a link on the BTS?
[11:07] <LaserJock> Erlang: what do you mean?
[11:08] <LaserJock> the package is in Debian, right? and we just need to fakesync it in Ubuntu, right?
[11:08] <Erlang> yes.
[11:11] <Erlang> ..ooo nvm
[11:18] <LaserJock> CarlFK: heah, did you get your pbuilder to work and everything?
[11:24] <LaserJock> hi minghua
[11:34] <minghua> hi LaserJock
[11:35] <minghua> LaserJock: we seems to have many .desktop bugs now :-)
[11:35] <LaserJock> yep
[11:35] <zyga> minghua: .desktop bugs?
[11:36] <minghua> zyga: wishlist bugs that add .desktop file to packages that don't have one
[11:36] <zyga> oh
[11:36] <zyga> I can help you
[11:36] <zyga> I always hate when that happens
[11:36] <zyga> and I whish I could add such .desktop files
[11:37] <minghua> zyga: great.  please look at https://launchpad.net/people/motuscience/+assignedbugs
[11:38] <zyga> minghua: can I just assign one bug to myself?
[11:38] <zyga> oh some have desktop files attached
[11:39] <minghua> zyga: I would prefer you just add a comment saying you are working on it
[11:39] <zyga> okay
[11:39] <minghua> zyga: and I believe all of them have .desktop file attached
[11:39] <zyga> so how can I work on them? make debdiffs that add those desktop files?
[11:40] <LaserJock> but we need to make sure that they are valid , etc.
[11:40] <zyga> okay I'll just pick one up, add a comment and try to verify it
[11:41] <minghua> yeah, basically the work is reviewing, building and testing, uploading.
[11:41] <minghua> zyga: can you upload to universe?
[11:41] <zyga> minghua: no
[11:41] <zyga> not yet unfortunatly
[11:42] <zyga> I lost my key some time ago and I did not managed to get my new key signed
[11:42] <minghua> zyga: then a verified debdiff would be good
[11:47] <zyga> can I add [pl]  translations to the desktop files?
[11:50] <minghua> zyga: sure, feel free
[11:51] <zyga> minghua: should I sign my debdiffs?
[11:51] <minghua> not necessary IMO
[11:52] <minghua> debdiffs are supposed to be reviewd
[11:52] <minghua> reviewed*
[11:52] <zyga> okay
[11:53] <zyga> okay I'm almost done with one package, should I confirm it and attach a debdiff to the bug report?
[11:54] <minghua> zyga: did you do the building (in pbuilder) and testing?
[11:55] <zyga> minghua: I did the build (not in pbuilder, I did do testing)
[11:55] <zyga> I assume the dependencies are the same
[11:55] <minghua> zyga: okay, attach the debdiff and say that you've built and tested in the comments
[11:55] <zyga> okay
[11:56] <minghua> zyga: I don't see much point of confirming it, but it definitely won't hurt