[00:06] <RainCT> good night
[00:16] <bddebian> Heya gang
[00:25] <zul> hey Hobbsee
[00:25] <Hobbsee> hey zul!
[00:26] <zul> no one here but us goats
[00:27]  * Hobbsee is no goat
[00:31] <Nafallo> Hobbsee: can you prove that? :-)
[00:31] <Hobbsee> Nafallo: yeah - people hav eseen me
[00:32] <Fujitsu> Nafallo: Everyone knows she's a green alien. Duh.
[00:32]  * Hobbsee says "nyah.  try harder" at the cars outside.
[00:32] <Nafallo> :-P
[00:33]  * Nafallo ponders if "people" are trustworthy enough though ;-)
[00:33] <Hobbsee> well, they upload software that you're currently using, so...
[00:34] <zul> Fujitsu: i though we established the fact that Hobbsee is a zombie
[00:34] <Fujitsu> zul: Oops, so we did.
[00:40] <imbrandon> a zombie alien ?
[00:41] <imbrandon> btw hiya *
[00:42] <Hobbsee> heya!
[00:42] <Hobbsee> imbrandon: a *green* zombie alien!
[00:42] <imbrandon> hehe
[00:53] <ajmitch> hi
[00:53] <Fujitsu> It's an ajmitch! Run!
[00:53]  * ajmitch runs
[00:53] <Hobbsee> oh noes!
[00:54] <ajmitch> :(
[00:54]  * Hobbsee attacks ajmitch with the Long Pointy Stick of DOOM!!!!!!!!!!!!!!! ™
[00:54]  * Hobbsee coattacks Burgundavia with it, too.
[00:54]  * ajmitch scurries off back into his corner
[00:55] <imbrandon> i love packages that seem intresting but have no help or man or documentation whatsoever, even on the project website
[00:55] <zul> i think there is a manpage for ls
[00:55] <imbrandon> lol
[00:55] <imbrandon> mach is what i was speaking of
[00:56] <imbrandon> its supose to create rpm chroots, like debootstrap, replaces rpmstrap
[00:56]  * Fujitsu is glad that its secrets shall remain locked away forever.
[01:03] <Burgundavia> Hobbsee: apparently women hate me today. My gf was beating me up as well ;(
[01:04] <Hobbsee> Burgundavia: awww
[01:05]  * Hobbsee hugs Burgundavia
[01:07]  * slangasek beats up Burgundavia too, so he doesn't feel cheered that it's not a gender thing
[01:07] <StevenK> Hah
[01:07] <slangasek> hmm, s/doesn't/can/
[01:08] <Burgundavia> I hate you all
[01:08] <Burgundavia> I am going to run Gentoo now
[01:08] <ajmitch> excellent
[01:08] <bddebian> heh
[01:08] <ajmitch> our work here is done then
[01:08] <StevenK> Well, our job is done.
[01:08]  * StevenK grins, and high fives ajmitch 
[01:08] <LaserJock> hmm, I wonder why you need to agree to the Debian Machine Usage Policies to be a Debian Maintainer
[01:08]  * Hobbsee attacks slangasek and bddebian with the Long Pointy Stick of DOOM!!!!!!!!!!!!!!! ™ to make it appear random
[01:08] <LaserJock> is that just because of the buildds?
[01:10] <slangasek> Hobbsee: it may appear random to some, but the pattern is perfectly clear to me!
[01:10] <Hobbsee> slangasek: oh yes?
[01:10] <bddebian> hrmph
[01:10] <slangasek> absolutely
[01:10]  * Hobbsee wonders if you're better at patterns than those she was playing with mao are
[01:11] <Hobbsee> s/with mao/mao with/
[01:11] <slangasek> you're clearly poking people who IRC!
[01:11] <LaserJock> man, I suck at mao
[01:11] <LaserJock> although I played it at like 2 or 3am in a foreign country
[01:11] <LaserJock> and I was sick
[01:11] <LaserJock> so we'll blame it on that
[01:12] <LaserJock> soren can attest to how bad it was
[01:12] <slangasek> LaserJock: I think those are considered standard operating conditions for Mao, sorry :)
[01:12] <LaserJock> heh
[01:12] <Hobbsee> hehe
[01:12]  * Fujitsu wonders what this Mao thing is.
[01:12] <Hobbsee> Fujitsu: come to a UDS and find out
[01:13] <Fujitsu> Hah, like that's going to happen.
[01:13] <StevenK> Then come to Sydney and find out
[01:14] <Fujitsu> Maybe one day if I can convince my parents. Which isn't likely.
[01:15] <slangasek> ... maybe one day you'll be allowed to travel without parental approval?
[01:15] <slangasek> aside from the green alien zombies among us, people are known to age
[01:15] <Fujitsu> slangasek: That's a while off yet.
[01:16] <bddebian> Some of us faster than others :-(
[01:16] <slangasek> I did say age, not grow up
[01:17] <TheMuso> Well. I've just satisified my government election duties...
[01:17] <TheMuso> satisfied
[01:17] <StevenK> TheMuso: Did you have to?
[01:17] <TheMuso> StevenK: Of course.
[01:17] <StevenK> Voting just encourages them
[01:17] <StevenK> TheMuso: Was the form in Brallie?
[01:17] <Fujitsu> With any luck our beloved Mr. Howard will be gone soon...
[01:17] <TheMuso> StevenK: I think not.
[01:18] <bddebian> slangasek: Aye, and I'm already old.  I'll never grow up :-)
[01:18] <TheMuso> StevenK: I would use electronic voting, but I heard that it wasn't open source, so wasn't interested.
[01:18] <StevenK> Fujitsu: It's just a question if he gets replaced by Peter Costello or Kevin Rudd?
[01:18] <Fujitsu> StevenK: That's true.
[01:18]  * bddebian liked Howard
[01:19]  * StevenK prefers the latter, Peter Costello seeming like a jerk
[01:19]  * slangasek draws a correlation between bddebian's last two statements
[01:19] <PriceChild> !packaging | LaserJock
[01:19] <ubotu> LaserJock: packaging is  The packaging guide is at http://wiki.ubuntu.com/PackagingGuide - See https://wiki.ubuntu.com/UbuntuDevelopment NewPackages for information on getting a package integrated into Ubuntu - Other developer resources are at https://wiki.ubuntu.com/UbuntuDevelopment - See also !backports
[01:19] <Fujitsu> slangasek: Haha.
[01:19] <Fujitsu> StevenK: I don't particularly like either, but would prefer the latter. But I don't have to vote until next time.
[01:20] <PriceChild> LaserJock, did you mean to remove the / before NewPackages on that second link?
[01:22] <TheMuso> StevenK: Do you mind if I take care of openmovieeditor?
[01:22] <StevenK> TheMuso: Not overly
[01:26] <bddebian> slangasek: Right, I'm old and experienced enough to know that I don't want the government running my life..
[01:26]  * bddebian hides
[01:27] <frenchy> Did you see the "Kirribilli house for sale" joke? Rudd did say that he was going to come and live with me, in Canberra.
[01:27] <slangasek> you mean that you don't want the /Australian/ government running your life, right, you'd rather have the American government running your life?
[01:28] <frenchy> Well he'll be in The Lodge and I'll still be slumming it.
[01:29] <frenchy> Maybe I'll catch him at the local pub, or strip joint ... *** frenchy laughs at his own joke.
[01:33] <bddebian> slangasek: I am an American.  And I don't want to live in a nanny state, no. :-)
[01:35] <slangasek> oh, so you like Howard because he's Somebody Else's Problem
[01:35] <StevenK> slangasek: Would you mind checking why my gutenprint upload got rejected?
[01:35] <Hobbsee> StevenK: you forgot to sacrifice a goat to soyuz.
[01:35] <TheMuso> lol
[01:36] <slangasek> oh, is that why Hobbsee's insistent that she isn't a goat
[01:36] <StevenK> Hah
[01:36] <Hobbsee> haha
[01:36]  * Fujitsu normally uses goats for SCSI, but they might be useful for Soyuz too.
[01:36] <slangasek> StevenK: do I have a clue where to look for rejects?
[01:37] <StevenK> slangasek: There's a log on drescher
[01:37] <slangasek> called?
[01:37] <StevenK> That I have no clue about
[01:38] <Fujitsu> The directories with the upload bits should be in /srv/launchpad.net/ubuntu-queue/rejected, I think. Rejections should be logged to the lp_archive mailbox.
[01:39] <Hobbsee> slangasek: er, is there a new kernel upload planned before the alpha?
[01:39] <StevenK> Fujitsu: And how do you know that? :-)
[01:40] <persia> lamont: Sent.  Thanks
[01:40] <slangasek> Hobbsee: I haven't heard.
[01:40] <Fujitsu> StevenK: I don't quite recall.
[01:40] <persia> Hobbsee: It's still important to have a Rationale for syncs after DIF to explain why we're importing after the freeze (Freeze Exception Process)
[01:40] <slangasek> hmm, the lp_archive mailbox is rather Large
[01:41] <persia> Anyone using `debuild -k`: please only do this if you are a sponsor: it's far better to get your changelog identity entity to match your GPG keyring identity.
[01:41] <Fujitsu> slangasek: I'm not surprised. How many gigabytes?
[01:42] <slangasek> StevenK: wrong .orig.tar.gz referenced
[01:42] <slangasek> Fujitsu: 1.9 \o/
[01:42] <StevenK> There was no .orig.tar.gz in the .changes file
[01:42] <slangasek> StevenK: no, but there would have to be one in the .dsc
[01:42] <slangasek> and the checksum doesn't match the existing one
[01:42] <Fujitsu> slangasek: Nice.
[01:42] <StevenK> Ah, duh.
[01:42] <StevenK> I forgot about that
[01:43] <StevenK> slangasek: Danke, I'll sort that out soonish
[01:43] <TheMuso> StevenK: Did you not get an upload rejection email?
[01:44] <slangasek> that's just what I was going to ask, the mail I was peeking at is rather uploader-oriented
[01:44] <slangasek> actually, it looks pretty much identical to a dak reject :)
[01:44] <StevenK> I did, I just couldn't make sense of why it was talking about things in the archive.
[01:44] <StevenK> Oh wel
[01:44] <StevenK> well, even
[01:54] <GoldenPony> LaserJock!
[01:55] <TheMuso> Is it just me, or is requestsync getting the version number incorrect in the email subjects it produces, yet it gets the correct changelog?
[01:56] <persia> TheMuso: I don't think it's just you: I've seen a bunch of things in the sponsors queue with that issue.
[01:58] <TheMuso> persia: Ok, thats good to know.
[02:27] <LaserJock> !packaging
[02:27] <ubotu> packaging is The packaging guide is at http://wiki.ubuntu.com/PackagingGuide - See https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages for information on getting a package integrated into Ubuntu - Other developer resources are at https://wiki.ubuntu.com/UbuntuDevelopment - See also !backports
[02:28] <LaserJock> hmm, looks like he fixed it
[02:30] <Hobbsee> LaserJock: ponies!
[02:31] <LaserJock> trying to find a screw I lost in my grandfather's laptop
[02:46] <imbrandon> LaserJock: get it all sorted i see
[02:56] <LaserJock> goodness sakes
[02:56] <LaserJock> I was gonna say something and my laptop just turned off
[02:56] <LaserJock> apparently somebody unplugged me
[02:56] <imbrandon> heh
[02:56] <LaserJock> on reboot I had a ton of fsck problems
[02:56] <imbrandon> nice
[02:57] <LaserJock> had run fsck manually and there was a lot of stuff
[02:57] <LaserJock> hopefully I didn't lose too much data
[02:57] <imbrandon> probably only what you had open
[02:58] <LaserJock> well, that's fine then
[03:05] <imbrandon> wow someone actualy sugested use qemubuilder to build a i386 package on a x86_64 instead of a i386 chroot/pbuilder
[03:05] <slangasek> yes, let us bow our heads in shame
[03:06] <imbrandon> heh
[03:13] <TheMuso> c
[03:13] <Hobbsee> d
[03:13] <TheMuso> ugh wront tab
[03:13] <Hobbsee> TheMuso: c is right in any tab?
[03:13]  * persia suspects /c is useful to avoid gibber
[03:55] <DoYouKnow> hi
[03:55] <DoYouKnow> I am new
[03:55] <persia> DoYouKnow: Hi.
[04:04] <somerville32> Now that I've started doing packaging on my server (dunno why I didn't do this earlier), I can get a lot more done quicker
[04:04] <somerville32> AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ VS. Pentium II (Deschutes)
[04:06] <pwnguin> i should set up ccache and maybe distcc
[04:06] <pwnguin> is distcc the only way to get pbuilder to hit multicores?
[04:07] <persia> pwnguin: You don't want to do that: it means that your build won't match the buildd build, and may not work.
[04:08] <pwnguin> is there a problem with not matching the buildd build?
[04:08] <Hobbsee> pwnguin: yes.
[04:09] <pwnguin> I'm thinking that question deserves a two part answer
[04:10] <persia> pwnguin: Essentially, the main reason we bother to build things locally is to make sure that they will build on the buildds when they get uploaded.
[04:11] <persia> If you are just playing for private use, you'd do better to do a local build with `debuild`.
[04:11] <persia> If you want to build something as a candidate for the repositories, you'd do best to run a full Soyuz implementation, but that's annoying, and pbuilder does most of it.
[04:12] <pwnguin> wait
[04:12] <somerville32> Hmm
[04:12] <pwnguin> are there cases where things would build in parallel but not in pbuilder?
[04:12] <persia> The reason debuild is better for local use is that it takes advantage of the installed system, and so ./configure will often pull in libraries that may normally be excluded (depending on the build system).
[04:12] <somerville32> interdiff doesn't work that great
[04:13] <persia> pwnguin: Yes.  If there is accidental timestamp skew, make -j can become very confused.
[04:13] <persia> somerville32: How doesn't it work?
[04:13] <pwnguin> persia: then it would fail in parallel
[04:13] <somerville32> persia, I get hunking errors all the time
[04:14] <persia> pwnguin: Not necessarily: maybe it works in parallel because it can catch up, but breaks in serial due to the skew.
[04:14] <persia> somerville32: What's your command line?
[04:14] <somerville32> interdiff -z -p1 diff1 diff2
[04:15] <persia> somerville32: You get "hunking errors" from running interdiff, or trying to use that interdiff?
[04:15] <somerville32> I get hunking errors while running it
[04:16] <somerville32> Sometimes, I can't get any meaningful ouput at all
[04:16] <persia> somerville32: Could you put your diffs somewhere?  I've never seen that.
[04:16] <somerville32> I have two examples that I'll post in a second
[04:19] <imbrandon> pwnguin: distcc isnt very nice with pbuilder as it needs source/package changes ( -j X ) but ccache works well if setup right
[04:19] <imbrandon> with pbuilder
[04:19] <pwnguin> ah
[04:19] <pwnguin> i thought maybe pbuilder was smart about that stuff
[04:19] <imbrandon> heh no
[04:19] <pwnguin> but still, im thinking if it works in parallel
[04:20] <pwnguin> it works in series
[04:20] <imbrandon> plus there are programs that just fail peroid with distcc
[04:20] <imbrandon> pbuilder or not
[04:20] <pwnguin> right
[04:21] <pwnguin> i know distcc has limitations
[04:21] <imbrandon> AND icecream is better imho :)
[04:21] <pwnguin> well, i did ask if distcc was the only way
[04:22] <imbrandon> kde* is notorious for useing icecream vs distcc, never heard of it being used with pbuilder though
[04:22] <Hobbsee> [15:09] <pwnguin> I'm thinking that question deserves a two part answer <-- persia already answered the latter half.
[04:25]  * persia wonders if somerville32 encountered a grue
[04:26] <Hobbsee> he encounted a GoldenPony, i expect
[04:26] <persia> Don't GoldenPonies shiine in the dark, lighting the way to a happier place?
[04:27]  * somerville32 coughs something about Debian.
[04:27] <imbrandon> bah nuff $work for one night
[04:27] <imbrandon> time for a new theme
[04:28] <somerville32> What is this a sign of?
[04:28] <somerville32> Installing: /usr/share/locale/ar/LC_MESSAGES/notecase.mo
[04:28] <somerville32> /bin/sh: /tmp/buildd/notecase-1.6.9/debian/notecase: Permission denied
[04:28] <somerville32> I'm using CDBS
[04:28] <somerville32> (It says that for everything it tries to install)
[04:28] <imbrandon> that, cdbs = magic ?
[04:28] <persia> Not using fakeroot?
[04:29] <persia> filesystem full?
[04:29] <somerville32> I'm using pbuilder
[04:29]  * persia suspects /tmp is tmpfs and only 1/2 RAM, and can't build big things
[04:30]  * Hobbsee wonders if it's somethinga bout executability
[04:30] <Hobbsee> like, debian/rules not being executable
[04:31] <somerville32> debian/rules is executed
[04:31] <somerville32> I do see this: DEB_MAKE_CHECK_TARGET unset, not running checks
[04:32] <persia> Hobbsee: That's cause an error much earlier in the process.
[04:32] <Hobbsee> persia: ahhh
[04:32] <Hobbsee> persia: it's been so long since i've done it :)
[04:32] <persia> somerville32: the lack of running make check isn't a real error
[04:34] <persia> Err.  by "isn't a real error", I mean "is safe to ignore"
[04:35] <somerville32> It built on my other computer IIRC
[04:35] <persia> Does your other computer have more RAM?
[04:35] <somerville32> I don't see dh_checkperms or w/e it is called being run. Is there a CDBS setting for that?
[04:38] <persia> somerville32: Likely: there's a CDBS setting for everything.  On the other hand, your problem is not dh_fixperms: you're either running out of space or trying to write to a directory that doesn't exist (maybe you need a notecase.dirs file?)
[04:38] <somerville32> Most likely
[04:38] <somerville32> Well, I gotta jet. bbl
[04:39] <persia> somerville32: Please post your interdiff example when you can: that really sounds like a combinediff error, and I'd like to make sure it doesn't happen often.
[04:40] <somerville32> Sure thing
[06:19] <warp10> Hi all!
[06:31] <imbrandon> LaserRock!
[06:47] <imbrandon> pwnguin: btw if you havent seen it here is the info on http://en.opensuse.org/Icecream , its pretty KDE centric, but iirc it can be used for anything , its kinda a distcc-ng by suse
[06:55] <nixternal> it can be used by whatever you want, the only thing kde centric with I think is the client status window
[06:56] <pwnguin> well, distcc will probably be enough
[06:56] <pwnguin> i guess you can't really hack in parallel builds to a package after the fact though
[06:56] <pwnguin> err
[06:56] <pwnguin> not distcc,
[06:56] <pwnguin> ccache
[06:58] <pwnguin> from a time standpoint, perhaps i should just figure out debuild
[07:02] <imbrandon> debuild is essentialy the same as pbuilder only not preformed in a chroot, i.e. apt-get build-dep <package>; debuild <options>; ( from the main package directory )
[07:02] <persia> Er. No.  debuild doesn't pull build-deps.
[07:02] <imbrandon> common options are -S -sa for a source only ( REVU ) upload , just plain debuild if you were the last to make a change and -us -uc if you were not
[07:03] <imbrandon> persia: yea i added the apt-get build-dep bit :)
[07:03] <persia> imbrandon: to debuild?  Why?
[07:03] <imbrandon> debuild is essentialy the same as pbuilder only not preformed in a chroot, i.e. apt-get build-dep <package>; debuild <options>; ( from the main package directory )
[07:04] <imbrandon> 00:58 < pwnguin> from a time standpoint, perhaps i should just figure out debuild
[07:04] <persia> imbrandon: Further how are you parsing the build-deps?  Will it pull the build-deps from the apt-cache or from debian/control?
[07:04]  * persia attempts to calculate timezones and reviews backscroll
[07:04] <imbrandon> they way i did it it will get them from the debian/control of the last one in the archive :)
[07:05] <persia> imbrandon: Please don't do that: that completely breaks NBS processing.
[07:05] <imbrandon> persia: we're not talking about for something to be uplaoded
[07:05] <imbrandon> he is talking about using it for a personal build
[07:05] <persia> imbrandon: Ah.  OK.  No worries then :)
[07:06]  * persia still likes dpkg-checkbuilddep
[07:06] <persia> s
[07:06] <pwnguin> i do a lot of writing of new patches
[07:07] <pwnguin> pbuilder / debuild are helpful in that they already know the build process
[07:10] <imbrandon> oh wow , spam is getting worse, not just web 2.0 but "gibLink is a web 2.5 ..."
[07:10]  * imbrandon rolls eys
[07:10] <imbrandon> eyes even
[07:10] <pwnguin> gmail let through a spam that claimed to be from myself
[07:10] <imbrandon> heh
[07:10] <imbrandon> i complain about spam but gmail catches 90% of it
[07:10] <imbrandon> still a ton though
[07:11] <imbrandon> that makes it to my inbox
[07:11] <pwnguin> gmail's gotten better about catching russian spam
[07:11] <pwnguin> it used to not flag russian and japanese spam
[07:11] <pwnguin> i get maybe one a week
[07:11] <imbrandon> i just hate when you get 100000 returned emails for your domain becouse someone forged spam from your domain
[07:12] <pwnguin> but then i dont host a domain or place my email on my website
[07:12] <imbrandon> :)
[07:12] <imbrandon> gmail still handles my domain email but still
[07:13] <pwnguin> there's a backport of compiz?
[07:13] <imbrandon> yea, few days ago
[07:13] <pwnguin> oh, screensaver security type patches in it
[07:16] <warp10> Hi lionel. You are the last uploader for sword. May I request the sync for it?
[07:18] <Hobbsee> warp10: which version is currently in ubuntu, and which version is in debian?
[07:18] <warp10> Hobbsee: 1.5.9-6ubuntu1 and 1.5.9-7
[07:19] <Hobbsee> warp10: have you seen the changelog entry for the ubuntu version?
[07:19] <warp10> Hobbsee: yep!
[07:20] <Hobbsee> what does it say?
[07:20] <warp10> Hobbsee: just the sync request and Maintainer: change
[07:21] <imbrandon> the changelog has a sync request? was it a fakesync ?
[07:21] <Hobbsee> imbrandon: yeah, it's a fakesync.
[07:21] <warp10> imbrandon: fakesync indeed.
[07:21]  * Hobbsee remembers it
[07:21] <Hobbsee> warp10: that means that you cant sync it, as the debian and ubuntu tarballs are different.
[07:21] <Fujitsu> Why was it fakesynced?
[07:21] <Fujitsu> Ah.
[07:22] <warp10> Hobbsee: mmm... but shouldn't it be anyway synced after a version change?
[07:23] <Hobbsee> warp10: the tarballs don't get synced across, if the tarball name is the same.
[07:23] <Hobbsee> you have to apply the debian changes to the ubuntu package
[07:25] <warp10> Hobbsee: well, ok. I never met a fakesync before. Thanks for your hints!
[07:25] <Hobbsee> no problem
[07:26] <imbrandon> hte next sync can happen at 1.5.10/1.6 ( when a new tarbal is released upstream )
[07:26] <imbrandon> assuming there are still no ubuntu specific changes
[07:27] <imbrandon> that cant be dropped
[08:27] <geser> StevenK: can I ask you about your changes to pdftk? I was looking at it and my changes are included in the Debian changes but I'm not sure if some of your changes are still needed.
[08:27] <StevenK> Hum, wha? I made changes to pdftk? :-P
[08:27] <StevenK> geser: Do you mind waiting until I sort out abiword?
[08:28] <geser> sure
[08:31] <StevenK> geser: Okay, let me have a look while it builds.
[08:34] <geser> Debian builds now also with gcj-4.2 and g++-4.2 and it builds in a hardy pbuilder. So I don't know if those changes to the Makefile are still needed.
[08:34] <geser> Otherwise the package can be synced.
[08:38] <StevenK> geser: My only change for pdftk was a rebuild
[08:38] <StevenK> I only added a changelog entry
[08:40] <geser> StevenK: http://patches.ubuntu.com/p/pdftk/pdftk_1.40-2ubuntu3.patch lists you also for -2ubuntu1
[08:41] <geser> and the second patch has also ## general-fixes.dpatch by Steve Kowalik <stevenk@ubuntu.com>
[08:43] <StevenK> Oh, ubuntu3
[08:44] <StevenK> Hrm. If I recall this a was a hard fix
[08:46] <StevenK> geser: Right, I'm not certain that the Makefile patches are required anymore - if the compiler can find the paths itself, then drop it
[08:47] <StevenK> geser: If I recall, doko asked it was built against 4.2
[08:47] <geser> ok, thanks. I'll request a sync then.
[08:48] <StevenK> geser: Basically, the patch was to fix a build failure since it wasn't finding other class files referenced
[08:49] <geser> Debian changes in their build-gcc-4.2 patch the classpath for the GCJH calls. I guess for the same purpose
[08:49] <StevenK> Fair enough, sync it
[09:33] <imbrandon> RAOF: ping
[09:41] <imbrandon> welp i'm gonna call it an early night and see if i can get some sleep
[09:41] <imbrandon> gnight all
[09:41] <imbrandon> thanks slangasek
[10:16] <RAOF> imbrandon: pong!~
[10:18]  * persia encourages the use of Post-It™ notes when playing simulated table tennis
[10:19] <RAOF> Gah, missed lordkow.
[10:35] <persia> jpatrick: About styleclock: I was just adding a watch file, and noticed the rpath and shlibs issues.  Do you remember why this package sets a private library?
[10:36] <jpatrick> persia: nop
[10:36] <jpatrick> I think upstream's dead anyway
[10:37] <persia> jpatrick: Should we drop the package?  I'm just trying to clean up missing watch files for Ubuntu-only packages.
[10:37] <jpatrick> with KDE4 it should be ok to drop
[10:38] <persia> jpatrick: OK.  I'll file a removal request.  Thanks.
[10:48] <jpatrick> it this not a valid .install file: http://paste.ubuntu-nl.org/45682/ ?
[10:49] <persia> jpatrick: Below ----- only?
[10:49] <jpatrick> yep
[10:49] <jpatrick> above is the error I keep getting
[10:50] <persia> OK.  Is there a $(CURDIR)/usr/ ?
[10:50] <jpatrick> usr/ should be debian/tmp/usr
[10:51] <jpatrick> hmm, I could leave out the usr/ since there is no other package made
[10:51] <persia> jpatrick: Should be, but I'm not sure you can mix the "move bits from debian/tmp into subpackages" with raw installs (then again, I could be wrong).
[10:52] <persia> Ah, if you've only one package, then dh_install isn't in multipackage mode, and that won't work at all.  That's it.
[10:52] <persia> next, is there really a $(CURDIR)/tmp/buildd/tork-023... ?
[10:52] <persia> That just looks wrong to me.
[10:53] <jpatrick> lintian reports file-in-unusual-dir and dir-or-file-in-tmp for those files
[10:53] <jpatrick> I'm getting to get them into the right place
[10:54] <persia> I suspect there's something funny with your build system.  That's just not a good rule, as it will break for local builds, and will break for a version upgrade.
[10:54] <jpatrick> I have mailed upstream about it and he's very confused about what's happening
[10:55] <DaveMorris> can someone review my package please. http://revu.tauware.de/details.py?package=libserial
[10:55] <persia> jpatrick: The part that confuses me is why debian/tork/usr/share/man/man1/... is the wrong place.
[10:56] <jpatrick> persia: that's the thing :>
[10:56] <persia> jpatrick: Could you pastebin `dpkg --contents` for the binary if you don't have those funny lines (and get the lintian error)?
[10:58] <jpatrick> persia: http://paste.ubuntu-nl.org/45683/
[11:01] <persia> jpatrick: Thanks.  That's clearly wrong :)  How about a buildlog?
[11:02] <jpatrick> http://paste.ubuntu-nl.org/45685/
[11:03] <persia> Also, this should really be three packages: tork-tsocks, libtorksocks1, and libtorksocks-dev
[11:07] <persia> Hrm.  With this many icons, I'd check the size: it might even deserve a tork-common as well...
[11:08] <persia> jpatrick: OK.  I think I have it.  Could you paste upstream Makefile (after patching)?
[11:10] <jpatrick> persia: upstream will be estatic if you do :) being trying to get this to package for two months now: http://paste.ubuntu-nl.org/45686/
[11:12] <persia> jpatrick: That looks like Makefile.in : is that really the Makefile?
[11:12] <jpatrick> it's a Makefile.am
[11:12] <persia> Ah.  Could you run a build that doesn't delete afterwards, and also paste Makefile.in and Makefile?
[11:14] <jpatrick> how do you pbuild so it doesn't delete?
[11:15]  * persia doesn't use pbuilder and seeks support from others
[11:16] <pochu> you can login into pbuilder and then build it, but you will have to manually copy the files into /var/cache/pbuilder/buildd.../home/
[11:16] <persia> pochu: Thanks
[11:17] <jpatrick> I copied the src somewhere else ran "debian/rules build" from there
[11:20] <persia> jpatrick: Is this CDBS, or hand-built rules?
[11:21] <persia> nevermind.  I just checked the build-deps (headsmack)
[11:35] <james_w> Should merging of packages in main be left to -core-dev?
[11:36] <persia> slangasek: Regarding Alpha 1: how does that affect universe?  Should we be targeting wiping the NBS list, or is it not as critical?  As universe doesn't really affect the CD, would you prefer a universe freeze, or is it not essential?
[11:36] <Hobbsee> persia: soyuz will force it all to freeze, if it's like usual, universe gets a manual shove
[11:36] <persia> james_w: It depends.  If you know the package well, and have worked with it before, you can go ahead.
[11:36] <Hobbsee> erm.  which i still can't do.  bugger.
[11:36] <persia> Hobbsee: Not based on the recent mail to u-d@
[11:37] <james_w> persia: no I don't/haven't.
[11:37] <persia> james_w: If you're not a previous contributor to the package, it's best to leave the merge, unless you're working with a previous contributor.
[11:37] <james_w> persia: that makes sense. However I didn't notice until I'd actually done the work.
[11:37] <persia> james_w: In that case, best to leave it.  Sponsoring into main can take a while, and the packages are all assigned to specific developers.
[11:38] <Hobbsee> persia: oh, ignore me.  i havent actually read teh mail yet.
[11:38] <persia> Hobbsee: I try, but somehow I find it difficult :)
[11:38] <RainCT> hi
[11:38] <persia> hey RainCT
[11:38] <pochu> james_w: or ask the last uploader to review it if he can
[11:38] <Hobbsee> persia: :P
[11:39] <persia> Hmm.  I have a main merge.  Oops!
[11:39] <RainCT> I'm merging classpath and it has the following Ubuntu specific changes: * Add /usr/include/xulrunner to CLASSPATH_INCLUDES in configure  * And MOZILLA_CFLAGS       are those required for something or might just be needed for it to build?
[11:40] <persia> RainCT: Those are required to get the mozilla classes in the classpath.  I'd check in #ubuntu-mozillateam to get a better understanding about them
[11:40] <james_w> thanks persia
[11:41] <Hobbsee> slangasek: where can i find the information on what was discussed w.r.t the release team, at UDS?
[11:41] <persia> james_w: No problem.  Thanks for asking.
[11:43] <persia> Is KDE4 targeted for hardy, or will it still be KDE3.x?
[11:43] <RainCT> persia: ok, thx
[11:43] <Hobbsee> persia: it'll be there, but not by deafult
[11:43] <persia> Right then.  I shan't remove styleclock, just fix it.
[11:46] <jpatrick> persia: aha, I got the Makefile http://paste.ubuntu-nl.org/45690/
[11:47] <jpatrick> even tho it says Makefile.in...
[11:48] <persia> jpatrick: Makefile.in isn't Makefile, but it's closer :)
[11:48] <jpatrick> that was the Makefile in /tmp/build/obj-linux-thingy/src/tsocks
[11:49] <persia> jpatrick: Now I'm confused.  This is Makefile or Makefile.in?
[11:49] <jpatrick> Makefil
[11:49] <jpatrick> -e*
[11:50]  * persia hopes '*' doesn't indicate shell expansion :)
[11:50] <jpatrick> nop, correction :)
[11:56] <persia> jpatrick: Found it: line 66 sets the install directory to $(DESTDIR)$(torksocksmanpagedir), and line 412 sets torksocksmanpagedir to $(DESTDIR/$(mandir)/man1, which is a clear duplicate.
[11:56] <persia> The next step is to look at Makefile.in, to try to figure out why that happens, and the final step is to adjust Makefile.am to make it not happen.
[11:57] <jpatrick> persia: ok, will do
[11:58] <persia> jpatrick: Good luck, and thanks for tracking this down rather than trying to work around it with dh_install.
[11:58] <persia> DaveMorris: still about?
[12:00] <LucidFox> Hobbsee> Out of curiosity, will KDE4 be in universe or main?
[12:01] <DaveMorris> persia: for around 10 mins
[12:01] <persia> DaveMorris: You win then :)  Looking at libserial now...
[12:03] <persia> (and it will likely take longer than 10 minutes: no need to wait)
[12:04] <Hobbsee> LucidFox: universe, probably
[12:04] <Hobbsee> it's unsupported
[12:04] <LucidFox> ah
[12:06] <DaveMorris> well I'll bee back in around 10 then
[12:13] <persia> DaveMorris: Commented
[12:30] <DaveMorris> persia: any manuals I can read regarding the manpage problems?
[12:34] <persia> DaveMorris: I can't find one offhand.  Please let me know if you encounter one: it would be a valuable addition to the packaging guide.
[12:35] <DaveMorris> yeah, since I know nothing about manpages (except how to use them)
[12:37] <persia> DaveMorris: That's about where I stand :)  There might be something useful in /usr/share/doc/man-db/man-db-manual*, but I've not read it.
[12:40] <DaveMorris> After working on these packages I know why so many ppl just have packages on there site rather than putting them into the distros.  Because going from a package which can be installed and works to getting past revu is actually quite a big jump
[12:48] <persia> DaveMorris: It depends on how one defines "works", but I'd agree that the policy hurdles are often more difficult than just wrapping the package.  Thanks for trying: I think it's better for everyone when the package are in the distributions.
[13:40] <LucidFox> http://revu.tauware.de/details.py?package=libhiglayout-java <-- please nuke/archive, I've filed a sync request from Debian instead
[13:41] <persia> LucidFox: Archving.  Thanks.
[13:53] <LucidFox> I've uploaded an updated package for review: http://revu.tauware.de/details.py?package=qdvdauthor , and would also appreciate a review of http://revu.tauware.de/details.py?package=avidemux
[14:02] <persia> LucidFox: avidemux and qdvdauthor generate lintian output from the source: please adjust, check the binaries, and reupload.
[14:03] <LucidFox> how do I check lintian output from the source?
[14:04] <persia> LucidFox: lintian -iIv on the .dsc.  Alternately, look at the lintian link on the URLs you provided when requesting review.
[14:31] <\sh> moins
[14:34] <james_w> hi \sh.
[14:34] <james_w> could you give me some information on why http://patches.ubuntu.com/a/asc/asc_1.16.3.0-3ubuntu1.patch was necessary please?
[14:35] <\sh> phew..starting engines for the day just now :)
[14:35] <\sh> james_w, without it, it was FTBFSing in gutsy these days..
[14:36] <StevenHarperUK> Hi, how can I add translations to : https://edge.launchpad.net/ubuntu/+source/easycrypt
[14:36] <james_w> \sh: so you don't know what dependencies changed to make that necessary?
[14:37] <\sh> james_w, feisty..sry
[14:37] <\sh> james_w, nope..I'm just checking what the source is telling me, what it needs, and it gets it
[14:37] <persia> StevenHarperUK: How do you mean?  Do you want to add more .po files?
[14:38] <\sh> james_w, most likely a diff in libsdl1.2* deps...between debian and ubuntu these days...
[14:38] <StevenHarperUK> I have a PO file I want to use the launchpad feature to get more translations
[14:38] <james_w> \sh: thanks. I was talking to the games team about applying it themselves, and they wanted to understand why it was different.
[14:38] <\sh> james_w, if debians version works now, sync it
[14:38] <james_w> \sh: yeah, I'll try a test build of current sid in hardy.
[14:38] <persia> james_w: The reason was that there was massive library skew for feisty.  It's all sorted now.
[14:39] <\sh> james_w, bah...all build-dep changes are coming mostly from changed deps in build-deps of ubuntu...those changes are mostly shortliving changes
[14:39] <james_w> persia: so we should be able to drop the Ubuntu changes now?
[14:40] <persia> james_w: Always test build to check for sure, but usually that type of change isn't worth preserving (unless the changelog says something like "add aalib-dev to build-depends to support ASCII output).
[14:40] <\sh> james_w, try the debian version ... build it, if it's building without FTBFS it's ok to sync..if not, stay with it
[14:41] <persia> james_w: Also, if Ubuntu depends on a newer version of something, always preserve that, as it is usually related to some transition that has to be handled differently due to Ubuntu's frequent release cycle: many things get finished and dropped in Debian that need to be supported in Ubuntu due to massive user distribution.
[14:41] <james_w> yeah, of course I'll check, I was thinking more about pushing upstream.
[14:42] <StevenHarperUK> persia: what I want is to use launchpad to get translators to add new translations, the tab is greyed, how do I change that
[14:42] <james_w> StevenHarperUK: I think you might have to set it up for a project, rather than a source package. I'm just speculating though.
[14:43] <james_w> StevenHarperUK: also #launchpad is probably a more appropriate location for this question.
[14:43] <StevenHarperUK> I have uploaded a PO in the project, but its been sat in the Queue for ages (over a month)
[14:43] <persia> StevenHarperUK: I'm not sure about that.  I think only Ubuntu main is translated automatically, and for the rest you'd need to register a project in Launchpad, and enable Rosetta.  I may be wrong: it's worth looking at the Translations pages in Launchpad directly (I didn't find anything from a quick search).
[14:43] <StevenHarperUK> OK thanks
[14:45] <StevenHarperUK> persia: I have another Question - now that easycrypt is past the NEW queue : do I use REVU as the upload location for new VERSIONS : and just do the Bug raising as specified in the contributing pages?
[14:45] <persia> StevenHarperUK: You want to open a bug, and subscribe the sponsors.  For new upstreams, use an interdiff please, as debdiff is confusing.  Be sure your watch file works (or your get-orig-source).
[14:46] <persia> \sh: Is that a scripted away change?
[14:47] <StevenHarperUK> persia: do I just submit the new version -as I am upstream or do I have to make the diffs?
[14:47] <\sh> persia, I think it's new ati binary only aixgl support drivers fcking with my computer somehow
[14:47] <persia> \sh: Ah.  Sorry to hear that :(
[14:48] <persia> StevenHarperUK: The interdiff of the diff.gz files is useful, as it represents the new candidate revision for upload to the repository.  I'd expect you'll be making most changes upstream, so likely only debian/changelog would differ (making a small diff).  The sponsors will use the watch file to download your new upstream tarball.
[14:49] <LucidFox> I reuploaded qdvdauthor
[14:49] <\sh> Fujitsu, why did you set the status to invalid for bug #162385 ?
[14:49] <ubotu> Launchpad bug 162385 in drupal "[Security] Several Security Issues for drupal 5.x before 5.3" [Undecided,In progress] https://launchpad.net/bugs/162385
[14:49] <persia> \sh: It's really late there: you may wait ~8 hours for a response (although I may be mistaken)
[14:50] <Fujitsu> \sh: Note the extra task, to properly represent status.
[14:50]  * persia is mistaken
[14:50] <\sh> Fujitsu, ah ok...
[14:50] <Fujitsu> persia: That you are. I'm about to go to bed, though.
[14:50] <\sh> Fujitsu, sleep well :)
[14:50] <StevenHarperUK> persia: so to conclude, I make sure my watch file is correct (which it is), upload to REVU , and follow the bug raising guide and subscribing.
[14:50] <\sh> well, working on a python bug
[14:51] <persia> StevenHarperUK: Skip the REVU step: no need.  Just make sure your watch file is correct: make sure you have updated packaging (new .dsc, new .diff.gz), and attach the interdiff to the bug.  See https://wiki.ubuntu.com/MOTU/Contributing for instructions.
[14:52] <StevenHarperUK> persia: ta
[15:00] <geser> Hobbsee: Hi, are you doing give-backs?
[15:00] <Hobbsee> geser: bribes accepted.
[15:01] <geser> hmm
[15:01]  * Hobbsee can do givebacks, yes.
[15:01] <Hobbsee> whether i'm going to at this time of night is an interesting question :P
[15:02] <geser> Hobbsee: can you give-back advi on all arches for nxvl?
[15:03] <Hobbsee> geser: where?
[15:03] <Hobbsee> (gutsy, hardy)?
[15:03] <geser> hardy
[15:03] <Hobbsee> k
[15:03] <geser> thanks
[15:04] <\sh> oh wow...how do someone create a patch for python without knowing with patch is applying first?
[15:04] <Hobbsee> geser: all given back
[15:10] <norsetto> hello folks
[15:10] <persia> good evening norsetto
[15:10] <norsetto> hiya persia
[15:11] <persia> I hope I was stepping on your toes in my response: I think yours was much more concise.
[15:11] <geser> Hi norsetto
[15:11] <norsetto> hey geser
[15:11] <persia> Err..  s/was/wasn't/
[15:11] <norsetto> persia: lol
[15:12] <\sh> doko_, can you explain your patch system in python2.5? how are the patches applied, reading in which logical order ?
[15:15] <LucidFox> What's the difference between ${source:Version} and  ${binary:Version}?
[15:15] <james_w> LucidFox: they can differ in a binNMU.
[15:16] <james_w> i.e. it's possible to build new binaries with an increased version number without making a new source upload and building arch: all packages.
[15:17] <persia> james_w: Actually, we don't have binNMU in Ubuntu (but, yes).
[15:17] <james_w> http://wiki.debian.org/binNMU
[15:21] <persia> LucidFox: use (= ${binary:Version}) for arch:any depending on arch:any,  (= ${source:Version}) for arch:any depending on arch:all, and (>= ${source:Version}) for arch:all depending on arch:any.
[15:23] <james_w> \sh: there's an explicit list in debian/rules
[15:24] <\sh> james_w, yeah I just realized how crazy this is ...
[15:24] <Ubulette> who assigned bug 164123 to MOTU ? it should be mozillateam. In fact, i have the package ready for review.. just waiting for asac to come back.
[15:24] <ubotu> Launchpad bug 164123 in firefox-3.0 "Firefox 3 Gran Paradiso need upgrade" [Undecided,Confirmed] https://launchpad.net/bugs/164123
[15:25] <\sh> Ubulette, as it seems, that this package is in universe, it's motu land so it's correct...you need to catch those reports and push them to your team
[15:25] <persia> Ubulette: There's actually tons of bugs in universe randomly assigned to MOTU.  Feel free to reassign.
[15:26] <persia> Ubulette: If you have a working watch file or get-orig-source, sending it to the sponsors queue might get it uploaded faster (and yes, I know we've had this discussion before :) )
[15:27] <Kmos> ubotu: how about firefox 2.0.0.9 for gutsy ?
[15:27] <Kmos> Ubulette: how about firefox 2.0.0.9 for gutsy ?
[15:27] <Ubulette> no security fix in this one so no.
[15:27] <\sh> Kmos, i thought there was a report to -security
[15:27] <persia> Kmos: That'd be a backport, no?  Not something done by the mozillateam, eh?
[15:28] <Kmos> persia: can't be a SRU ?
[15:28] <Ubulette> maybe 2.0.0.10 in a few days
[15:28] <\sh> Ubulette, is this .jar exploit not fixed?
[15:28] <persia> !sru | Kmos
[15:28] <ubotu> Kmos: Stable Release Update information is at http://wiki.ubuntu.com/StableReleaseUpdates
[15:28]  * Kmos follow the link
[15:28] <persia> Kmos: Pay special attention to the criteria for SRU: it needs to be completely broken in some way.
[15:30] <Ubulette> \sh, I'll check but asac usually prefers to do ff2 himself. I do ff3.
[15:31] <\sh> Ubulette, reading the release notes of 2.0.0.9 there are no sec fixes inside...
[15:31] <Kmos> persia: if it has a security vuln. ubuntu-security team should handle it from -security repository, and can't be a SRU
[15:31] <persia> Kmos: Right.  And if it works for most people, it also can't be SRU.
[15:31] <\sh> Kmos, security vulnerability != completly broken ,-)
[15:31] <soothsayer> How should a package deal with a file superceding a file from another package? That is, package-2 needs to a different version of a file provided by package-1.
[15:31] <Kmos> \sh: yeah.
[15:32] <Kmos> persia: thanks
[15:32] <persia> soothsayer: There are a number of solutions, depending on the nature of the target file.  Could you share a little more context?
[15:32] <StevenHarperUK> persia: I have done all the stuff (moved all my SVN round) to make building the diff automated - but the diff file seems to have Date and times of the files in the diff and it mentions every file : is this correct?
[15:32] <Kmos> 2.0.0.9 isn't at hardy.. so can't be backported yet
[15:32] <persia> Kmos: No problems: you've not annoyed me lately, so you get good answers to questions :)
[15:32] <StevenHarperUK> persia: can I PM you the text
[15:32] <james_w> soothsayer: are these two binary packages built from one source?
[15:33] <soothsayer> persia: I'm happy to share context but I don't know very much about the internals of the two packages.
[15:33] <soothsayer> james_w: No.
[15:33] <Kmos> persia :) i hope i continue this way
[15:33] <james_w> soothsayer: what sort of file is it? (binary, config, docs?)
[15:33] <soothsayer> james_w: They are two libraries
[15:34] <soothsayer> Neither are packaged, I'm trying to build packages for them.
[15:34] <james_w> soothsayer: ah, that's tricky.
[15:34] <Ubulette> Kmos, I can easily prepare 2.0.0.9 for hardy but it's useless, 2.0.0.10 is almost out
[15:34] <james_w> soothsayer: are you just packaging the libraries, or dependent binaries?
[15:35] <soothsayer> james_w: Just the libs
[15:35] <james_w> soothsayer: and is it necessary to package both?
[15:35] <\sh> more important is, how do we get the sec fixes from .10 to gutsy ;)
[15:35] <Kmos> Ubulette: ok =)
[15:35] <soothsayer> james_w: I don't need to package either. Packages are just to make my life easier
[15:35] <\sh> reading about those .jar crap..it's important
[15:36] <james_w> soothsayer: yes, but why two versions?
[15:36] <james_w> soothsayer: do they have the same soname?
[15:37] <persia> StevenHarperUK: Could you pastebin it?
[15:37] <StevenHarperUK> persia: I have never used that, ill go try thou
[15:38] <persia> !pastebin | StevenHarperUK
[15:38] <ubotu> StevenHarperUK: pastebin is a service to post large texts so you don't flood the channel. The Ubuntu pastebin is at http://paste.ubuntu-nl.org (make sure you give us the URL for your paste - see also the #ubuntu channel topic)
[15:38] <soothsayer> james_w: The conflicting files are header files. I'll post a diff of the files, just a sec.
[15:38] <brandonperry> did anyone in here package hardinfo for gutsy?
[15:38] <StevenHarperUK> persia: http://pastebin.com/d44468f9
[15:39] <persia> brandonperry: No.
[15:39] <brandonperry> or was it just moved from the feisty repos to the gutsy?
[15:39] <brandonperry> k
[15:39] <james_w> soothsayer: ah, then these are -dev packages we are talking about, that's slightly different. It is possible to have two versions of a library installed at once, but headers are a lot more tricky.
[15:40] <StevenHarperUK> persia: http://paste.ubuntu-nl.org/45702/
[15:40] <persia> StevenHarperUK: What command did you use to generate that?
[15:40] <james_w> soothsayer: if the two versions are incompatible then you are a bit stuck.
[15:40] <soothsayer> james_w: Ah made a mistake. One library is already packaged and provided by Ubuntu. The other is not yet packaged and has the aforementioned conflict.
[15:40] <StevenHarperUK> persia: diff -urN debian.old debian > easycrypt.debian.patch
[15:40] <\sh> brandonperry, https://edge.launchpad.net/ubuntu/+source/hardinfo/
[15:40] <\sh> brandonperry, so you can see it came from debian
[15:40] <soothsayer> james_w:  http://www.pastebin.ca/795883
[15:40] <brandonperry> ah
[15:40] <soothsayer> ^ Diff of the files
[15:40] <brandonperry> ok
[15:40] <brandonperry> thanks
[15:41] <james_w> soothsayer: thanks
[15:41] <persia> StevenHarperUK: Ah.  I was hoping for the output of `interdiff -z easycrypt_0.2.1.11-0ubuntu1.diff.gz easycrypt_0.2.1.12-0ubuntu1.diff.gz`
[15:42] <StevenHarperUK> persia: ok that will be done
[15:42] <StevenHarperUK> persia: back soon
[15:42] <persia> brandonperry: Now, why did you ask?  If you have a question about the hardinfo packaging, we may be able to answer?
[15:42] <soothsayer> james_w: The two packages are 'gmp' (already packaged) and Linbox (which I'm trying to package)
[15:42] <brandonperry> well, it is completely unstable on gutsy
[15:42] <brandonperry> but is fine on feisty
[15:43] <james_w> soothsayer: so linbox uses a copy of gmp?
[15:43] <LucidFox> reuploaded avidemux: http://revu.tauware.de/details.py?package=avidemux
[15:43] <brandonperry> that is it
[15:43] <persia> brandonperry: Hmmm...  It looks like it's a newer version on gutsy.  You'd likely do best to file a bug report.
[15:43] <brandonperry> it isn't really a question as much as an observation
[15:43] <brandonperry> k
[15:44] <james_w> soothsayer: they don't look incompatible to me, so the solution would be to make linbox use the system gmp.
[15:44] <soothsayer> james_w: What do you mean exactly? It uses gmp and apparently needs a modified header file. It doesn't provide another version of gmp apart from the header
[15:44] <james_w> soothsayer: (also most people use diff -u, I personally find it much more readable)
[15:45] <james_w> soothsayer: it just has the header file? That's a little odd.
[15:45]  * persia suspects a private implementation
[15:46] <james_w> soothsayer: is your /usr/include/gmp++/gmp++.h the one from the packages gmp++?
[15:46] <soothsayer> http://www.pastebin.ca/795888
[15:46] <soothsayer> ^ diff -u
[15:47] <soothsayer> james_w: I believe so. I'll verify it...
[15:47] <james_w> soothsayer: thanks.
[15:47] <james_w> soothsayer: it may well be, but things like __GIVARO_GMP_VERSION_3 stick out.
[15:50] <james_w> soothsayer: also, I can't find /usr/include/gmp++/gmp++.h in Ubuntu.
[15:50] <soothsayer> james_w: You are right it is from Givaro.
[15:50] <soothsayer> james_w: Still, same problem only now neither library is already packaged.
[15:51] <james_w> libgmp3-dev provides /usr/include/gmpxx.h
[15:51] <james_w> soothsayer: you should see how the versions you have differ with that file.
[15:52] <james_w> soothsayer: is it http://ljk.imag.fr/CASYS/LOGICIELS/givaro/ ?
[15:53] <soothsayer> http://www.pastebin.ca/795893
[15:53] <soothsayer> james_w: Yes. The other package is at linalg.org
[15:53] <soothsayer> http://www.linalg.org
[15:53] <soothsayer> s/package/library
[15:57] <james_w> soothsayer: ok, this is quite odd, but it looks to me that you could package givaro, and then the other lib, but make it use givaro's copy of that header.
[15:58] <james_w> however the copyright situation of the givaro library might be a little shaky.
[15:59] <RainCT> davromaniak: ping
[15:59] <soothsayer> james_w: Are you sure that the two headers are compatible?
[16:00] <davromaniak> RainCT, pong
[16:00] <james_w> soothsayer: not *sure*, but the first diff you showed looks like they should be.
[16:00] <soothsayer> james_w: Alright, thanks.
[16:01] <james_w> soothsayer: maybe I was a bit quick on the copyright warning, I would check it carefully, but it looks like it might be ok.
[16:01] <RainCT> davromaniak: someone is asking me about dvdstyler, are you still working on this?
[16:02] <davromaniak> yes, but I don't a big amount of spare time to work on it
[16:02] <davromaniak> and the upstream tgz is not clean
[16:02] <soothsayer> james_w: Yeah, okay. I'll check out the copyright situation if I manage to get it packaged.
[16:02] <StevenHarperUK> persia: I have done the interdiff : and automated it all - does this look correct now please http://paste.ubuntu-nl.org/45704/
[16:06] <persia> StevenHarperUK: The format is correct.  I've a few comments about the content: firstly, why doesn't upstream adopt the manpage?  secondly, since 0.2.1.12 and 0.2.1.13 were never released as official .dsc, you don't need debian/changelog entries for them, thirdly it's preferred to state "New Upstream Version" rather than "no packaging changes": remember that when you edit debian/changelog, you do it with your distribution maintainer hat, rather th
[16:09] <StevenHarperUK> persia: What does adopt the manpage mean
[16:10] <persia> StevenHarperUK: Move the manpage from debian/ into the upstream sources, so it ends up in orig.tar.gz, and is installed by the upstream build system.  This way, if the package is used in another distribution, that distribution also gets to use the manpage.
[16:10] <StevenHarperUK> persia: can I please do that for 0.2.1.15?
[16:11] <soothsayer> james_w: If it turns out that they are not compatible, what are my options?
[16:11] <persia> StevenHarperUK: Certainly.  It's not a sponsorship block, just advice :)
[16:11] <StevenHarperUK> persia: its sound like good advice too
[16:11] <soothsayer> It's upstream's mistake right?
[16:11] <persia> StevenHarperUK: For the upload, I would prefer the removal of the extra changelog entries, and the use of "New Upstream Version" though.
[16:13] <StevenHarperUK> persia: Already done : please check - http://paste.ubuntu-nl.org/45710/
[16:13] <Ubulette> what's the path to get a new package in hardy ? I have Prism ready for a while. https://edge.launchpad.net/prism/   (It's a SVN release so far)
[16:13] <james_w> soothsayer: well, that would be why they were shipping a private copy, but as it's just the header file that would be a really bad idea.
[16:13] <StevenHarperUK> persia: hold on that s nto it
[16:13] <StevenHarperUK> persia: Not it
[16:13] <james_w> soothsayer: the best solution would be to modify linbox so it is compatible.
[16:13] <persia> StevenHarperUK: you're too late, but I'll wait :)
[16:14] <soothsayer> james_w: Okay thakns
[16:14] <soothsayer> *thanks
[16:15] <StevenHarperUK> persia: Here you go : http://paste.ubuntu-nl.org/45711/
[16:18] <james_w> soothsayer: no problem.
[16:19] <persia> StevenHarperUK: From a visual scan, that looks pretty good.  Please attach it to a bug and subscribe the sponsors team to request upload.
[16:19] <StevenHarperUK> persia: I will but should I not test it first?
[16:20] <persia> StevenHarperUK: I thought you already did that :)
[16:21] <RainCT> man-di: ping
[16:21] <StevenHarperUK> persia: doing it now, ta
[16:21]  * persia encourages abstention from contentless pings
[16:26] <StevenHarperUK> persia: Tests Pass ill get it submitted, thanks for you as usual superb help
[16:27] <persia> StevenHarperUK: No problem.  Thanks for taking the trouble to maintain your software in Ubuntu.  Now that you've done it once, I suspect future upgrades should go smoothly.
[16:27] <StevenHarperUK> Very smoothly : I have automated it all with scripts
[16:27] <StevenHarperUK> All in SVN if  your interested
[16:28] <StevenHarperUK> persia: http://www.squeezedonkey.com/svn/linux/branches/easycrypt/0.2.1.14/easycrypt/build_compare.sh
[16:30] <persia> StevenHarperUK: I tend to use dpkg-parsechangelog to get the current version, and then pull from VCS using that version as a tag with a get-orig-source rule in debian/rules.  Further, by using the VCS-* tags in debian/control, one can identify the branches for the debian revisions.  You may also be interested in the pristine-tar package.
[16:31] <StevenHarperUK> persia: ill add it into my list of things to investigate
[16:34] <persia> StevenHarperUK: Good luck.  My mechanisms may not be ideal for you, as I touch lots of software, whereas you're also doing the development, but there are more tools that support VCS* and get-orig-source which you could leverage int he future :)
[16:35] <Ubulette> so, noone for my question about getting Prism into hardy ?
[16:36] <persia> Ubulette: which question again?
[16:37] <Ubulette> persia, what do I have to do to 1st get it in there ?
[16:39] <persia> Ubulette: All new packages should go to REVU.  Once it's clean, and it gets two advocates, it gets uploaded.  You can get it through REVU faster by trying to make it as clean as possible and running all the automated checks before each upload.  Further, ask for review here once a day, and more often on Mondays to encourage people to look at it.
[16:41] <StevenHarperUK> persia: I have Subscribed the ubuntu-universe-sponsors team to my bug https://bugs.edge.launchpad.net/ubuntu/+source/easycrypt/+bug/164880 : is that the last step for now?
[16:41] <ubotu> Launchpad bug 164880 in easycrypt "Candidate revision easycrypt_0.2.1.14-0ubuntu1" [Undecided,Confirmed]
[16:42] <persia> StevenHarperUK: I usually recommend adding a short summary of the upstream changelog in the description of the bug to explain why the upgrade is a good idea, but at this point you wait.  The sponsors usually provide a response within a day or so.
[16:42] <StevenHarperUK> OK ill add that to  the bug
[16:43] <StevenHarperUK> and Ill mark it as passed, when it get uploaded And  builds for all
[16:44] <StevenHarperUK> persia: Ok i'm off to entertain kids now
[16:44] <StevenHarperUK> persia: Cya
[16:46] <Ubulette> persia, so I need to register to yet another system. damn. you guys know how to make life harder than it should be :P
[16:47] <Ubulette> ok, I joined w-w-c, now i wait ?
[16:47] <persia> Ubulette: No registration required.  Just join ~ubuntu-universe-contributors in LP.
[16:47] <Ubulette> u-u-x
[16:47] <Ubulette> u-u-c
[16:47] <Ubulette> damn fingers
[16:47] <persia> Ubulette: Right.  Unfortunately, I've forgotten how to resync the keyring, so we'll have to wait for another REVU admin
[16:48]  * DktrKranz should ask a REVU admin to add him to the reviewers group...
[16:50]  * persia looks for docs, hoping someone appears to provide guidance...
[16:56] <\sh> DktrKranz, there are bugreports on LP for tikiwikipikisikiklicki, right?
[16:57] <\sh> hooray..I just learned how dokos selfmade patch system is working for python
[16:58] <DktrKranz> \sh, only one open for tikiwikipikisikiklicki (bug 163833), but several CVEs
[16:58] <ubotu> Launchpad bug 163833 in tikiwiki "[tikiwiki] Multiple vulnerabilities possibly resulting in the remote execution of arbitrary code" [Undecided,New] https://launchpad.net/bugs/163833
[16:58] <persia> Right.  DktrKranz, Ubulette: I must apologize, but I don't seem to be able to figure out how to perform the tasks.  Please look for another admin in a few hours.
[16:59] <ScottK> Maybe imbrandon is awake?  I'm pretty sure he knows how.
[16:59] <DktrKranz> persia, No problem. Thanks for trying,
[16:59] <\sh> DktrKranz, ah cool...I'll assign it to me  and fix it after I won the fight with python :)
[16:59] <Ubulette> hmm; ok. it says it's also autosynced nightly. depends on when nightly is...
[17:00] <DktrKranz> \sh these one are for sure: CVE-2006-6457 CVE-2007-4554 CVE-2007-5423
[17:00] <ubotu> tiki-wiki_rss.php in Tikiwiki 1.9.5, 1.9.2, and possibly other versions allows remote attackers to obtain sensitive information (MySQL username and password) via an invalid (large or negative) ver parameter, which leaks the information in an error message. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-6457)
[17:00] <ubotu> Cross-site scripting (XSS) vulnerability in tiki-remind_password.php in Tikiwiki (aka Tiki CMS/Groupware) 1.9.7 allows remote attackers to inject arbitrary web script or HTML via the username parameter.  NOTE: this issue might be related to CVE-2006-2635.7. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-4554)
[17:00] <ubotu> Eval injection vulnerability in tiki-graph_formula.php in TikiWiki 1.9.8 allows remote attackers to execute arbitrary code via PHP sequences in the f array parameter. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-5423)
[17:01] <\sh> hmm.why are 6457 and 4554 not added to the bug then?
[17:01] <DktrKranz> \sh, which fight? I like fighting, even if I usually lose...
[17:01] <\sh> DktrKranz, just fixing python2.5 (CVE-2007-4965)
[17:01] <ubotu> Multiple integer overflows in the imageop module in Python 2.5.1 and earlier allow context-dependent attackers to cause a denial of service (application crash) and possibly obtain sensitive information (memory contents) via crafted arguments to (1) the tovideo method, and unspecified other vectors related to (2) imageop.c, (3) rbgimgmodule.c, and other files, which trigger heap-based buffer overflows. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-
[17:02] <\sh> DktrKranz, and fighting with dokos patch system
[17:02] <DktrKranz> another patch system to learn? Is it complex enough to be loved? :)
[17:03] <\sh> DktrKranz, it's one of those systems, you want to forget...but I know doko, so there is always a reason for this
[17:04] <DktrKranz> Is it in python2.5? I'm curious to see it, just for my reference
[17:05] <\sh> DktrKranz, yepp...apt-get source python2.5
[17:05]  * DktrKranz loves quilt now...
[17:10] <\sh> grmpf
[17:10] <\sh> my workstation fcks around with me...always crashing
[17:11] <man-di> RainCT: pong
[17:13] <DktrKranz> \sh, that's the main issue with developmet releases :)
[17:13] <\sh> DktrKranz, running gursy
[17:13] <\sh> gutsy
[17:13] <DktrKranz> ah...
[17:14] <\sh> think more a hardware problem...well nextmonth there is new hardware coming
[17:14] <DktrKranz> what about early upgrade, then? :D
[17:14] <\sh> crap
[17:14] <\sh> what is a good mp3/ogg player for the console?
[17:15] <persia> \sh: mpg123?
[17:15] <RainCT> man-di: about classpath, does the ./configure file still need to be patched in Ubuntu or are the changes in Debian now?
[17:15] <\sh> persia, looks like that mpg123 doesn't handle ogg somehow
[17:16] <man-di> RainCT: what is patched in Ubuntu?
[17:16] <man-di> RainCT: was this about the mozilla headers?
[17:16] <RainCT> man-di: yes. * Add /usr/include/xulrunner to CLASSPATH_INCLUDES in configure, * And MOZILLA_CFLAGS
[17:17] <persia> \sh: ogg123?
[17:17] <\sh> Package ogg123 is not available, but is referred to by another package.
[17:17] <\sh> This may mean that the package is missing, has been obsoleted, or
[17:17] <\sh> is only available from another source
[17:17] <\sh> E: Package ogg123 has no installation candidate
[17:18] <RainCT> \sh: I used xmms2 for a while
[17:18] <persia> RainCT: on the console?
[17:18] <RainCT> yes
[17:18]  * persia didn't know it did that
[17:18] <man-di> RainCT: I need to check
[17:19] <RainCT> it runs in the background so you can close the terminal and it continues playing, and switch songs from any window, etc. :)
[17:20] <persia> \sh: ogg123 is provided by "vorbis-tools".  Don't you have command-missing (or whatever it's called) installed?
[17:23] <\sh> persia, it doesn't matter ogg123 is broken somehow
[17:23] <\sh> ogg123 *.ogg
[17:23] <\sh> Creating link /home/shermann/.kde/socket-acer-p4-home.
[17:23] <\sh> can't create mcop directory
[17:23] <persia> \sh: Ah.  Sorry about that: I haven't tried it in a while.
[17:24] <\sh> but why the hell it has kde support?
[17:24] <persia> I'm really not sure why it pokes .kde though.
[17:24] <\sh> ah
[17:24] <\sh> this bastard had ogg123 -d arts
[17:24] <\sh> as default
[17:25] <persia> That's not right.
[17:25] <\sh> correct
[17:25] <persia> I don't suppose you're uploading the fix now?
[17:26] <\sh> lol
[17:28] <\sh> persia, it's gutsy
[17:28] <persia> \sh: Ah.  Not much we can do about that for gutsy, but maybe we can prevent annoying people in 5 months?
[17:29] <\sh> yepp...but first let me finish this python stuff
[17:31] <persia> \sh: Thanks.
[17:38] <\sh> hmmm...how is vorbis determine the default device if it's not alsa?
[17:41] <\sh> hmm...it's libao
[17:42] <\sh> first ogg123 tries config file setting, then it tries libao default device....
[17:42] <persia> \sh: libao2 should point to ALSA, and libao-pulse should point to pulseaudio.  Where do you want it to point?
[17:43] <\sh> persia, yes it should, but it doesn't point to alsa, as I saw just now
[17:43] <\sh> when you start ogg123 it wants arts
[17:43]  * persia grabs code, as this doesn't make sense
[17:43] <\sh> persia, right...
[17:44] <persia> \sh: And ogg123 -d alsa doesn't work?
[17:45] <\sh> persia, ogg123 -d alsa works,
[17:45] <\sh> but ogg123 -> points to arts by default...
[17:45] <\sh> so ao_default_driver_id is at fault it seems
[17:46] <\sh> hey jono
[17:46] <jono> hey \sh :)
[17:48] <LaserJock> hi jono
[17:48] <jono> heya LaserJock :)
[17:49] <\sh> persia, ok.../etc/libao.conf tells me that the default_driver=alsa09 is
[17:49]  * persia hunts an .ogg file
[17:50] <LaserJock> persia: looks like you been doing some wiki work today
[17:50] <LaserJock> :-)
[17:50] <persia> LaserJock: Not as much as I ought :(
[17:50] <LaserJock> something anyway
[17:50] <LaserJock> was that Launchpad page new?
[17:51] <persia> \sh: I think it's local: when I try it, it hits ALSA by default.
[17:51] <\sh> persia, do you have kde installed next to gnome?
[17:51] <persia> LaserJock: That LP page was ancient: early feisty: my first attempt at fulfilling your desire for process documentation.
[17:51] <persia> \sh: No.
[17:52] <\sh> persia, add kubuntu-desktop to your installation and try again
[17:52] <\sh> LaserJock, do you have kubuntu installed next to gnome=?
[17:52]  * persia doesn't have that much free disk space, and seeks a Kubuntu tester for ogg123 to replicate \sh's issue.
[17:52] <LaserJock> \sh: yes
[17:52] <persia> LaserJock: Do you have an ogg file?
[17:53] <LaserJock> hmm, surely somewhere, let me locate
[17:53] <\sh> LaserJock, ok...can you try ogg123...and tell me what it uses as output device? alsa or arts?
[17:53]  * persia points at http://www.vorbis.com/music/ for easy download if you have trouble
[17:53] <persia> (package is vorbis-tools)
[17:53] <LaserJock> ah sweet lots of .oggs
[17:54] <LaserJock> \sh: how would I tell what the output device would be? and should I do it in gnome or kde?
[17:54] <\sh> LaserJock, in gnome :)
[17:54] <persia> LaserJock: run it in a terminal: it prints the output device when it starts
[17:54] <LaserJock> ok, it says alsa
[17:55] <\sh> hmmm
[17:55] <\sh> gutsy?`
[17:55] <persia> OK.  Now try it in KDE, just in case (if you don't mind)
[17:55] <LaserJock> yep, gutsy
[17:55] <LaserJock> ok, one sec
[17:55] <persia> \sh: Have you already checked /etc/libao.conf?
[17:55] <\sh> persia, yepp it says default_device=alsa09
[17:56] <\sh> shermann@acer-p4-home:~$ cat /etc/libao.conf
[17:56] <\sh> default_driver=alsa09
[17:56] <persia> \sh: Try deleting the "09".  I'm fairly certain gutsy has the 1.0 API.
[17:56] <\sh> persia, hmmm..it was a new install earlier for this gutsy
[17:57] <\sh> persia, yepp...the 09 was the problem
[17:58] <\sh> persia, now I can listen to http://www.jamendo.com/album/5172 :)
[17:58] <persia> Hmmm...  I wonder how that happened.
[17:58] <persia> \sh: Is that your guitar & electronica experiment?
[17:59] <\sh> persia, nope...that a french group...playing a mixture of trance and  j.m-jarre
[17:59] <LaserJock> ok, back
[17:59] <LaserJock> it's arts in KDE
[17:59] <\sh> persia, it's in the source file of libao-0.8.8
[17:59] <persia> LaserJock: Interesting...
[18:00] <mok0> I think several packages, that have been modified in Ubuntu, are merely adding desktop entries and the like. Wouldn't it make more sense to let the package go unchanged, but with a companion package that supplies the Ubuntu-specific files. Just a thought.
[18:00] <LaserJock> mok0: actually, it makes the most sense to send the changes upstream
[18:01] <persia> mok0: No, because that would require extra infrastructure.  Amusingly, we have a package that contains all the .desktop files painfully extracted from each package to which we add them, but those .desktop files are excluded from view by default.
[18:01] <LaserJock> persia: does that include Universe packages?
[18:01] <LaserJock> I guess it might
[18:01]  * persia agrees with LaserJock, but encourages also passing to Debian because some upstreams take years to add them (even when you help with other patches to their code)
[18:01] <LaserJock> well sure
[18:02] <persia> LaserJock: Yep: app-install-data includes everything, which is one of the reasons I believe we need more desktop files.
[18:02]  * \sh grabs something to eat
[18:02] <LaserJock> I'm just saying making changes in Ubuntu are usually fine as long as you're sending stuff upstream
[18:02] <mok0> ... and, there may be several formats of desktopf files (?)
[18:02] <persia> mok0: There's only supposed to be one, but not everything is compliant.
[18:02] <\sh> persia, please change it in libao2 ,-) just change the libao.conf in debian/ dir
[18:03]  * persia encourages everyone to run http://people.ubuntuwire.com/~persia/find-missing-desktop and submit fixes.
[18:03] <mok0> It's just because I just looked at an entry where the only change as an added .desktop file
[18:04] <mok0> It got me thinking
[18:04] <persia> \sh: In 0.8.8-3 in hardy, I see alsa: Clint made it all better 1st July, but someone forgot to include it for gutsy :(
[18:05] <LaserJock> mok0: yes, they are trivial
[18:05] <persia> mok0: They are small, but if they are missing, the application doesn't show in Add/Remove programs, which isn't ideal.
[18:05] <LaserJock> mok0: but since debian traditionally doesn't emphasize .desktops because they have their own menu system
[18:05] <\sh> persia, would this be a case for an SRU?
[18:06] <persia> \sh: I don't think so: let me check the criteria again
[18:06] <persia> !sru
[18:06] <ubotu> Stable Release Update information is at http://wiki.ubuntu.com/StableReleaseUpdates
[18:06] <LaserJock> mok0: but as persia said, if there isn't a .desktop it won't show up in the menu or Add/Remove
[18:06] <nxvl> hi folks!
[18:06] <persia> LaserJock: As Debian gets more f.d.o compliant WMs, .desktop files are becoming more popular.
[18:06] <nxvl> where can i find the installer team?
[18:06] <mok0> But it would still be there if it was added in a xxxx-desktop package.
[18:07] <\sh> persia, it's not covered
[18:07] <persia> \sh: It's not a security issue, and there's no data loss.  Could we call it a "severe regression"?
[18:07] <\sh> persia, but "Bugs which may, under realistic circumstances, directly cause a security vulnerability" is wrong there too..because security issues are handled totally different...and aren't handled through -proposed...
[18:07] <persia> mok0: Right, but app-install-data wouldn't associate it with the right meta-data, and it wouldn't work properly.
[18:08] <mok0> persia: agreed. It would need some rules to be implemented when packages are installed
[18:08] <persia> \sh: The policy came before the new -security policy.  Go compain to TB if you want, but I don't think it matters much.
[18:08] <LaserJock> persia: that's what I hope
[18:09] <persia> LaserJock: which?
[18:09] <\sh> persia, tbh, I can't decide this..the problem is I don't know how many other apps are hit by this issue
[18:09] <LaserJock> persia: about Debian picking them up more
[18:09] <persia> \sh: 30 of them
[18:09] <LaserJock> mok0: that would certainly be doable, but my complaint about that would be that it really belongs upstream
[18:09] <persia> LaserJock: Ah, yes.  It's getting easier, and when they pick them up, they even install them in the right place these days.
[18:10] <LaserJock> mok0: so we should invest in things that shouldnt' be our problem
[18:10] <LaserJock> persia: yes, most at least see the usefulness of them, even if they don't use them directly
[18:10] <persia> LaserJock: What do you think about libao not using the correct output by default in gutsy as a "severe regression"?
[18:10] <mok0> LaserJock: As persia said, you can't expect upstream to service ubuntu. Plus, UI and desktop environments change all the time
[18:10] <LaserJock> mok0: it's not just Ubuntu
[18:10] <ScottK> persia: Did it work in Feisty?
[18:11] <LaserJock> mok0: it's the freedesktop.org standard
[18:11] <persia> mok0: Actually, the whole point of the f.d.o spec is so it won't change.
[18:11] <persia> ScottK: Yes.
[18:11] <mok0> LaserJock: Ok
[18:11] <\sh> persia, well, then its a severe regression
[18:11] <LaserJock> mok0: it's just that Ubuntu really cares about things showing up in Gnome/KDE menus
[18:11]  * \sh needs some food
[18:11] <mok0> But one solution doesn''t rule out the other...
[18:12]  * persia checks one more thing
[18:12] <mok0> We could have extra packages as long as they are needed
[18:12] <LaserJock> mok0: right, but there's really no advantage
[18:12] <LaserJock> mok0: merging .desktops is pretty trivial
[18:12] <mok0> less maintenance
[18:12] <LaserJock> but we'd have to maintain the giant database of .desktops
[18:12] <LaserJock> and worry about getting out of synce, etc.
[18:13] <mok0> LaserJock: :-) true
[18:13] <persia> mok0: No, because we still have to merge/demerge everything to match Debian, and if it's all in one package, we have a higher chance of conflicting timing
[18:13] <LaserJock> mok0: and actually, I think the maintanece pain is a good thing
[18:13] <mok0> LaserJock: what?
[18:13] <LaserJock> mok0: it encourages MOTUs to send things upstream so they get rid of it
[18:13] <persia> LaserJock: Would you be willing to process an SRU to make libao work on gutsy?  It's a 2 character change to the default configuration file.
[18:14] <persia> Not just MOTUs: Contributors too, as the Contributor gets assigned the merge.
[18:14] <LaserJock> persia: why me? :-)
[18:14] <persia> LaserJock: You can?
[18:14] <LaserJock> what's the current policy?
[18:14] <persia> !sru | laserjock (main)
[18:14] <ubotu> laserjock (main): Stable Release Update information is at http://wiki.ubuntu.com/StableReleaseUpdates
[18:16] <LaserJock> persia: oh, you need a core dev?
[18:16]  * LaserJock wondered why you couldn't just do it ;-)
[18:16] <persia> LaserJock: RIght :)
[18:16] <ScottK> Do we have a PDF tool that will let me fill out an encrypted PDF (the .deb from Adobe's site will do it)?
[18:17] <LaserJock> persia: bug #?
[18:18] <persia> Errr.  \sh: did you file a bug?
[18:18] <\sh> persia, I'll do just now
[18:18] <\sh> give me a sec
[18:18] <LaserJock> persia: so you guys got a different result than I did?
[18:19] <persia> LaserJock: No, your result is correct.  The problem is that it only works by accident in GNOME and it doesn't work in KDE.  It's calling the wrong ALSA API, and fails, so it drops to the fallback, and in GNOME that's ALSA, so one doesn't notice, but in KDE that's aRts, which is not what one expects.
[18:20] <LaserJock> what does one expect?
[18:20] <LaserJock> alsa both cases?
[18:21] <persia> LaserJock: Right, because it should be using the libao default driver, which should be "alsa", but it's set to "alsa09"
[18:21] <\sh> LaserJock, https://bugs.launchpad.net/ubuntu/+source/libao/+bug/164899
[18:21] <ubotu> Launchpad bug 164899 in libao "libao.conf in gutsy is wrong. (alsa09 is set as default)" [Undecided,New]
[18:22] <LaserJock> but does it still output?
[18:22] <LaserJock> albeit with the wrong driver
[18:22] <persia> LaserJock: Only if the client app has a fallback.  ogg123 has three methods: local, libao, and raw.  Not every app is so flexible.
[18:23] <LaserJock> ah
[18:23] <LaserJock> so libao is screwed
[18:23] <LaserJock> and we're just relying on the depending apps to fallback
[18:23] <persia> LaserJock: Right, because we didn't grab the bugfix from Debian before release.
[18:24] <persia> Debian bug #427903
[18:24] <ubotu> Debian bug 427903 in libao2 "change default driver in /etc/libao.conf" [Normal,Fixed] http://bugs.debian.org/427903
[18:26] <\sh> LaserJock, if you set it directly to alsa it plays, but not by default
[18:26] <LaserJock> ok, but as far as whether this is SRU, what goes wrong for the user?
[18:26] <persia> If the client app doesn't have a fallback, there's no audio.
[18:26] <LaserJock> ok, and how many are there?
[18:26] <persia> 27
[18:26] <LaserJock> that don't have a fallback
[18:27] <persia> Err.  That'll take some research.
[18:27] <LaserJock> right
[18:28] <LaserJock> it just seems hard to determine the importance
[18:29] <LaserJock> but possibly breaking 27 deps is pretty darn big
[18:30] <\sh> LaserJock, I think they are broken now
[18:31] <LaserJock> well, ogg123 isn't, do you have a few examples of some that are?
[18:32] <\sh> LaserJock, ogg123 is
[18:32] <\sh> LaserJock, defaults to alsa09 and tries arts first
[18:32] <\sh> LaserJock, mpg321 e.g.
[18:32] <\sh> mpg321 *.ogg
[18:32] <\sh> Creating link /home/shermann/.kde/socket-acer-p4-home.
[18:32] <\sh> can't create mcop directory
[18:32] <LaserJock> it falls back to something else
[18:32] <\sh> LaserJock, yes to arts
[18:32] <\sh> because libao finds arts, if there is arts on it..
[18:32] <LaserJock> I'm saying that to the user is that broken?
[18:33] <LaserJock> I realize it's broken in that it's not picking up alsa
[18:33] <persia> From a quick hunt, the following don't have fallback: waon, shell-fm, pytone (and likely other python-pyao rdeps), mpg321, mpc123, liquidsoap (unless you count icecast as a fallback), possibly libao-ruby1.8 clients, possibly libao-ocaml clients, gnomoradio, flac123, d4x, aldo, cdrdao
[18:34] <LaserJock> ok, excellent
[18:34] <LaserJock> that's what we need to se
[18:34] <LaserJock> *see
[18:35] <LaserJock> and this is fixed in Hardy, right?
[18:35] <persia> Mind you, that's just grabbing apps that have no other sound libraries as reverse depends.
[18:35] <persia> Yes, it's fixed in hardy due to autosync.
[18:35] <LaserJock> persia: seems fairly reasonable
[18:37] <persia> LaserJock: Right, but it's a minimal case: for instance I don't know what the default sound output for quake2 is: perhaps the user needs to tweak something internal to make it not use libao.
[18:37] <LaserJock> right
[18:38] <LaserJock> I just need some at least some estimate of immportance
[18:38]  * persia looks to \sh who has more experience with main SRUs
[18:40] <LaserJock> so I think that bug needs to get filled out with the necessary info and a patch and get Ubuntu SRU to approve
[18:41] <LaserJock> but it sounds like a reasonable SRU to me
[18:52] <\sh> persia, lol...I never did main SRUs :)
[18:52] <\sh> LaserJock, I'll give you more infos...as discussed here with a patch as well....and a debdiff for -proposed
[18:53] <LaserJock> \sh: well, with Main you need to follow the wiki page
[18:53] <\sh> LaserJock, yepp
[18:53] <LaserJock> and provide the info and subscribe the Ubuntu SRU team
[18:53] <LaserJock> once it's approved you can upload to -proposed
[18:53] <persia> \sh: Weren't you core?
[18:53] <LaserJock> and I can do that
[18:54] <LaserJock> if you like
[18:54] <\sh> persia, I was yes, but I never did SRUs for main or universe...
[18:54] <persia> Ah....  slacker!
[18:54] <\sh> persia, I never found something which is really so important that it had to be fixed asap :)
[19:06] <bmk789__> dfgjg          aeri tft
[19:07] <bmk789__> g]b/;[jyu;[ju;[jy]ewrdfcvbnmjhuy74569873216driufhjs8red04fo%^TI%ujik0
[19:08] <bmk789__> sorry, 4 year old found the keyboard
[19:09] <LaserJock> hehe
[19:10] <mok0> bmk789__: dfasdfk sf wer sfpåpu9ij asdfasd q asfa
[19:10] <mok0> :)
[19:19] <\sh> grmpf...bloody phone
[19:28] <scorpioxy> Hey guys. I have a question regarding a python panel applet package. Where does the whole pycentral and pysupport fall in a package where i have already defined its dependencies(which are minimal), is it needed?
[19:43] <LaserJock> scorpioxy: you need dh_pycentral or dh_pysupport in debian/rules
[19:43] <LaserJock> scorpioxy: if you're converting an old packge look for dh_python and replace it
[19:45] <\sh> persia, I just cound 27 apps which are using libao2
[19:45] <scorpioxy> LaserJock: Yes, but i still don't understand what it does. I read the manpage...but didn't understand it. Can you point me somewhere for a meaningful description? Or perhaps an explanation please...
[19:45] <\sh> count
[19:51] <ScottK> scorpioxy: What you want to look at is the Debian Python policy.  That'll explain why those are wanted.
[19:52] <avoine> what could be my mistake if when I build the package the files of the software are copie to debian/Myprog/ but the DEBIAN directory is not create?
[19:52] <scorpioxy> ScottK: I already did that, but let me take a look again, perhaps i missed something
[19:52] <LaserJock> avoine: how did you build the package?
[19:52] <avoine> debuild -b -uc -us
[19:54] <LaserJock> oh
[19:54] <avoine> maybe its setup.py that delete the DEBIAN folder
[19:54] <LaserJock> is that from a source package?
[19:54] <avoine> yes
[19:55] <LaserJock> and it has a debian/ directory?
[19:55] <avoine> yes
[19:56] <avoine> this is my debien/rules file: http://pastebin.ca/796117
[19:56] <avoine> *debian
[19:57] <scorpioxy> ScottK: Ok, i just read it again. And here's my problem. I don't think its relevant to what i'm building. You see it talks about modules and byte compiling modules. My app is a simple panel app so its dependencies are well know. Just python, and the gnome panel deps and so on...
[19:59] <ScottK> scorpioxy: What will your package do when the default Python changes from Python 2.5 to 2.6 and both are installed in the system?
[20:00] <scorpioxy> ScottK: Nothing! It uses env for default python...Is it supposed to do something?
[20:02] <ScottK> For a Python application it might not be needed.  But you do need to make sure you correctly support multiple Python's installed and version transitions.
[20:02] <\sh> scorpioxy, it could fail to run
[20:03]  * RainC1 wonders why the Liberation fonts aren't in the repo
[20:04] <LaserJock> RainC1: they aren't?
[20:04] <LaserJock> avoine: hmm, that seems at least reasonable
[20:04] <LaserJock> avoine: where were you looking for the DEBIAN folder?
[20:05] <scorpioxy> ScottK: Well, ok. I am not sure how and why though. If i depend on python >=2.5. Thanks anyway.
[20:05] <RainCT> LaserJock: no, unless they've renamed them :P. couldn't find them neither in Debian nor Ubuntu.. :S
[20:05] <avoine> in debian/penguintv/
[20:06] <ScottK> scorpioxy: I'd have to give you app a detailed review that I don't have time to to know for sure.  You may not need pycentral or pysupport.  Most of the policy is written for Modules.
[20:06] <scorpioxy> \sh: It doesn't do anything particularly complex. How do you think it could fail?
[20:06] <scorpioxy> ScottK: Yes that's what i understood from the policy. thanks
[20:06] <LaserJock> RainCT: actually I do think it's could be in a different package name
[20:07] <\sh> scorpioxy, syntax changes whatever...not necessary, but could happen..
[20:07]  * RainCT also searched in descriptions, btw
[20:07] <LaserJock> RainCT: I can't keep all the fonts straight. Are they the ones that Red Hat did?
[20:07] <RainCT> exactly
[20:08] <scorpioxy> \sh: ok thanks anyway
[20:10] <scorpioxy> One more general question. What do some people use as alternatives(if any) to the horrible autotools?
[20:12] <\sh> wasn't scons an alternative?
[20:12] <LaserJock> RainCT: I sure thought they were ar least in Hardy
[20:13] <\sh> SCons is a make replacement providing a range of enhanced features such
[20:13] <\sh>  as automated dependency generation and built in compilation cache
[20:13] <\sh>  support.
[20:13] <scorpioxy> \sh: Yup, scons, cmake, rake....there are a lot...i was interested in seeing if anybody is actually using something else
[20:14] <LaserJock> I've used cmake
[20:14] <scorpioxy> \sh: althoug, for me at least, scons sounded to focus on directed compilation much more than a general build tool
[20:15] <\sh> scorpioxy, well, dunno....when I have to use something, its auto*crap
[20:15] <valles_> hello all
[20:15] <\sh> scorpioxy, I'm an old m4 junky, spending lots of hours hacking sendmail m4 files  etc
[20:15] <RainCT> LaserJock: bug 113889
[20:15] <ubotu> Launchpad bug 113889 in ubuntu "[needs-packaging] Ubuntu needs the Liberation Fonts" [Wishlist,In progress] https://launchpad.net/bugs/113889
[20:16] <LaserJock> scorpioxy: I think most all KDE4 stuff is cmake these days
[20:16] <scorpioxy> LaserJock: yes, that's right...i am following some modules in kde..
[20:16] <scorpioxy> \sh: Well, the "used-to" factor plays a lot here
[20:17] <scorpioxy> although i was considering just how difficult it would be to move away from autotools because of all that legacy work already out there
[20:17] <scorpioxy> specifically debian and debian based systems i guess
[20:18] <\sh> ok...finished all python2.5 versions from edgy to gutsy...now I have to fix all python2.4 versions down to dapper, and several python2.3 and python2.2 versions :(
[20:18] <\sh> scorpioxy, for distros it's not important what build systems upstream uses...
[20:19] <\sh> scorpioxy, we are building packages with auto*foo, scons, cmake, whatever you can think of..there are some pitfalls, but this will be handled nicely by our buildd admins.
[20:22] <scorpioxy> \sh: So from these other systems, which one would you prefer...personally and technically? any opinion on that?
[20:24] <\sh> scorpioxy, nope...rake looks like ruby crap, scons has the power of python behind it, cmake is special for kde, auto* is quite balanced...
[20:26] <scorpioxy> \sh: very old school... thanks for the help
[20:26] <scorpioxy> LaserJock: thanks
[20:26] <LaserJock> I like some things about cmake
[20:26] <LaserJock> I think it might be a bit more limited than auto*
[20:28] <\sh> LaserJock, it's just like finding the right partner for life :)
[20:28] <LaserJock> hehe
[20:28] <LaserJock> I'm not sure my wife would like being compared to build systems ;-)
[20:29] <LaserJock> "You are lovely like cmake, but have the versatility of autotools"
[20:29] <scorpioxy> One more comment...i am so glad that they will finally deprecate bonbo for gnome-panel....there are some things in there that nobody knows anything about. they were written by micheal meeks and probably never changed since then...
[20:30] <scorpioxy> LaserJock: why not? efficiency, automation, no mistakes, speed...these are all great attribute for a human being
[20:30] <LaserJock> scorpioxy: I think she likes to think she's better than software :-)
[20:31] <\sh> LaserJock, hehe
[20:32] <scorpioxy> I think that there's few things better than a good piece of running code...but then again, i am not married....wonder why...
[20:36] <scorpioxy> well, that's all the time i have for hacking on packaging...thanks all
[20:36] <LaserJock> cya
[20:54] <\sh> hmmm..the handling of CVE  bugs are really crap regarding launchpad
[21:09] <TheMuso> Hey folks.
[21:10] <somerville32> Hiya
[21:17] <\sh> doko_, I won the fight with your python* patch system ;)
[21:22] <LaserJock> \sh: yes, there are several bugs open about LP's CVE handling
[21:22] <LaserJock> \sh: Fujitsu is, I think, working on some stuff to help the situation
[21:23] <\sh> LaserJock, I think some logical issues needs to be fixed...when you check bug #163845, e.g.
[21:23] <ubotu> Launchpad bug 163845 in python2.5 "[python] Multiple integer overflow vulnerabilities possibly resulting in the execution of arbitrary code or DoS" [Undecided,In progress] https://launchpad.net/bugs/163845
[21:23] <\sh> the CVE is valid for all major python versions we have, but only for python2.5 in gutsy, feisty and edgy
[21:24] <\sh> so I can't nominate for python2.5 just those three releases..because I have to include python2.4 for dapper
[21:36] <slangasek> persia: freezing universe is not essential at all, I don't think you need to worry about it
[21:54] <LaserJock> I hope this new "freeze" will work
[21:55] <LaserJock> I think it sounds more appealing
[22:06] <Fujitsu> \sh: That's bug #110195.
[22:06] <ubotu> Launchpad bug 110195 in malone "Nomination for a release on one source package shouldn't affect any others" [Undecided,New] https://launchpad.net/bugs/110195
[22:07] <Fujitsu> LaserJock: Can you please approve those tasks on \sh's bug? You have superpowers, don't you?
[22:19] <\sh> Fujitsu, I confirmed it ...
[22:22] <Fujitsu> \sh: Thanks.
[22:28] <Ubulette> how can I know if REVU synced my gpg key ?
[22:33] <somerville32> Ubulette, You see your upload :P
[22:34] <Ubulette> well, I'm waiting for this sync to push for the 1st time there.
[22:34] <somerville32> :)
[22:36] <Ubulette> so, what ? should I just push and wait ?
[22:36]  * somerville32 nods.
[22:36] <somerville32> Should show up in 5 mins or so
[22:36] <\sh> no risk no fun ,-)
[22:36] <Fujitsu> Ahhh, so it was bug #136634 that wiped out 60GB of mirror. Nice of it, really.
[22:36] <ubotu> Launchpad bug 136634 in libcompress-zlib-perl "Unable to download packages using Gutsy debmirror" [Undecided,Fix committed] https://launchpad.net/bugs/136634
[22:45] <\sh> hmm...can someone confirm that tix8.1-dev suddenly disappeared from dapper?
[22:46] <Fujitsu> \sh: Packages can't disappear from stable releases.
[22:46] <LaserJock> Fujitsu: which bug do I need to approve?
[22:47] <Fujitsu> LaserJock: Bug #163845
[22:47] <ubotu> Launchpad bug 163845 in python2.5 "[python] Multiple integer overflow vulnerabilities possibly resulting in the execution of arbitrary code or DoS" [Undecided,In progress] https://launchpad.net/bugs/163845
[22:48] <\sh> LaserJock, gutsy, feisty, edgy for python2.5, dapper for python2.5 is invalid
[22:48] <\sh> LaserJock, gutsy, feisty, edgy, dapper for 2.4
[22:48] <\sh> LaserJock, dapper for python2.3
[22:48] <LaserJock> same for 2.3?
[22:48] <LaserJock> ok
[22:49] <\sh> and give me a sec to add python2.2 for dapper
[22:49] <\sh> LaserJock, ok...python2.2 for dapper , too :9
[22:49] <LaserJock> only dapper for 2.3?
[22:50] <LaserJock> and 2.2
[22:50] <\sh> yepp
[22:50] <\sh> 2.3 and 2.2 for dapper only
[22:50] <\sh>  -> Considering build-dep tix8.1-dev (>= 8.1.3.93)
[22:50] <\sh> http://packages.ubuntu.com/cgi-bin/search_packages.pl?keywords=tix8.1-dev&searchon=names&subword=1&version=dapper&release=all
[22:50] <LaserJock> well crap
[22:50] <Fujitsu> LaserJock: You have no choice, you'll get all tasks for everything.
[22:50] <\sh> doesn't give me anything
[22:50] <LaserJock> it won't separate by package
[22:51] <Fujitsu> LaserJock: Corrrrrrect. Bug #110195, as above.
[22:51] <ubotu> Launchpad bug 110195 in malone "Nomination for a release on one source package shouldn't affect any others" [Undecided,Confirmed] https://launchpad.net/bugs/110195
[22:51] <LaserJock> right ....
[22:51] <\sh> argl
[22:51]  * LaserJock kicks LP
[22:51] <Ubulette> ok, upload to revu seemed fine.
[22:51] <\sh> LaserJock, so push it back with dapper
[22:51] <LaserJock> shall I just approve them all for now?
[22:51] <\sh> yepp
[22:52] <\sh> anyways, if this is right, that tix8.1-dev is not in dapper anymore, where is it then?
[22:52] <Fujitsu> \sh: What were you trying to build that wants it?
[22:52] <LaserJock> and I'll add a "me too" and motu tag to that bug
[22:53] <\sh> Fujitsu, python2.2 in dapper
[22:53] <Fujitsu> LaserJock: Thanks.
[22:53] <Fujitsu> \sh: Oh dear...
[22:53] <\sh> Fujitsu, http://archive.ubuntu.com/ubuntu/pool/main/t/tix8.1/ is empty
[22:53] <RAOF> imbrandon: Pong?
[22:53] <Fujitsu> \sh: Any tix8.2?
[22:53] <\sh> nope
[22:53] <LaserJock> that's a really annoying bug
[22:54] <Fujitsu> LaserJock: But it would be confusing otherwise! We couldn't possibly have an accurate representation of bug infestation...
[22:55] <LaserJock> well, this is why bug tasks are sometimes insufficent
[22:55] <LaserJock> we *should* be able to separate out what particular packages the bug affects, even if it is in different sources
[22:56] <Fujitsu> LaserJock: They're actually very useful for this sort of thing
[22:56] <Fujitsu> But that bug makes things annoying.
[22:56] <LaserJock> I agree
[22:56] <LaserJock> they are nice for this, but I don't know how exactly they would fix that bug
[22:57] <Ubulette> how long does it take for a package to appear on revu ?
[22:57] <LaserJock> wouldn't it make search results be off?
[22:57] <somerville32> 5 minutes
[22:57] <Fujitsu> LaserJock: The search results are already stuffed, they can't get much more broken.
[22:57] <Fujitsu> And I don't see how fixing it would make them off.
[22:58] <LaserJock> maybe not, but that's the only reason I could see for not fixing it
[22:58] <Ubulette> somerville32, hmm, 8min already. will I get an email if it failed ?
[22:59] <Fujitsu> LaserJock: Bug #163241 for an example of the stuff.
[22:59] <ubotu> Launchpad bug 163241 in malone "Searching distribution series bugs by component shows bug reports multiple times" [Medium,Confirmed] https://launchpad.net/bugs/163241
[22:59] <Fujitsu> Where stuff = braindead search results.
[23:00] <StevenHarperUK>  How long does a translation po take to get processed? Mine has been queued for ages https://translations.edge.launchpad.net/easycrypt/trunk/+imports
[23:01] <Fujitsu> StevenHarperUK: That is abnormally long, but there is a bit of a backlog at the moment. It shouldn't normally take more than a couple of weeks.
[23:01] <StevenHarperUK> Fujitsu: thanks, after that do updates take as long?
[23:03] <StevenHarperUK> Fujitsu: or is there a steamlined process?
[23:05] <LaserJock> Fujitsu: so as a workaround should we just Invalid the tasks we don't need?
[23:05] <Ubulette> revu hates me
[23:06] <Fujitsu> LaserJock: Correct.
[23:07] <Fujitsu> StevenHarperUK: I think they only need to be reviewed once.
[23:07] <Fujitsu> (apologises, X died on me)
[23:07] <Fujitsu> s/apologises/apologies/
[23:07] <Fujitsu> I make too many typos lately :(
[23:12] <LaserJock> ok Fujitsu and \sh, have another look at bug #163845
[23:12] <ubotu> Launchpad bug 163845 in python2.5 "[python] Multiple integer overflow vulnerabilities possibly resulting in the execution of arbitrary code or DoS" [Undecided,In progress] https://launchpad.net/bugs/163845
[23:14] <Fujitsu> LaserJock: Shudder.
[23:14] <LaserJock> yeah yeah
[23:14] <Fujitsu> There are a couple of tasks that I need to modify, but that looks right.
[23:14] <LaserJock> ok, enough from me though?
[23:17] <Fujitsu> I believe so.
[23:17] <LaserJock> Fujitsu: would it be possible to do some distributed rebuilding?
[23:18] <LaserJock> would that mess up anything by just giving people difference chunks of Universe to do?
[23:18] <Fujitsu> LaserJock: Ideally. pkern was doing some stuff with rebuildd, I believe.
[23:18] <Fujitsu> That would be the plan.
[23:18] <LaserJock> cause I've got an extra machine now
[23:18] <LaserJock> I could dedicate it to rebuilding for a while I guess
[23:19] <LaserJock> is just a matter of 1) get source 2)pbuild it 3) log results ?
[23:22] <Fujitsu> Probably saner to use sbuild, or whatever rebuildd uses.
[23:22] <Fujitsu> rebuildd is designed for just this sort of thing.
[23:22] <LaserJock> hmm
[23:22] <LaserJock> ok
[23:22] <Fujitsu> It replaces the wanna-build/buildd mess.
[23:23] <LaserJock> hmm, rebuildd looks great from the description
[23:25] <Ubulette> hmm, package is still not visible on revu, could someone help me ?
[23:25] <LaserJock> Fujitsu: you a revu admin now?
[23:25] <Fujitsu> LaserJock: No, but I can have a look at what's wrong.
[23:25] <\sh> LaserJock, looks very good the bugreport...could you set the importance to high, too? :)
[23:25] <Ubulette> Fujitsu, plz plz plz :)
[23:26] <Fujitsu> \sh: I can set that if you want.
[23:26] <Fujitsu> Ubulette: Looking.
[23:26] <Fujitsu> Ubulette: Which package?
[23:26] <Ubulette> prism
[23:26] <Fujitsu> Right, it was rejected.
[23:26]  * Fujitsu looks.
[23:26] <LaserJock> Fujitsu: I added the "motu" tag to that bug
[23:26] <LaserJock> hopefully we can get something going there
[23:27] <Fujitsu> Ah, of course, I don't have permission to view the .changes.
[23:27] <Fujitsu> LaserJock: Within a couple of years, hopefully.
[23:27] <LaserJock> file bugs now for Launchpad 5.0
[23:27] <LaserJock> ;-)
[23:27] <Fujitsu> Ubulette: You need to build with -sa.
[23:27] <Fujitsu> debuild -S -sa or so.
[23:28] <Ubulette> Fujitsu, I did with -S -sa (but with dpkg-buildpackage, like I always do)
[23:29] <Ubulette> Fujitsu, http://paste.ubuntu.com/2202/
[23:29] <Fujitsu> Ubulette: I can't see it...
[23:30] <Fujitsu> Hmm.
[23:30] <Fujitsu> THe .orig.tar.gz isn't in the incoming directory.
[23:30] <Fujitsu> Oh, there it is.
[23:30] <Fujitsu> I'm blind.
[23:30] <Fujitsu> Possibly a lack of key, but I can't do anything about that.
[23:34] <Ubulette> ok, thanks
[23:53] <RainCT> good night
[23:53] <Fujitsu> Night RainCT.
[23:56] <\sh> ok time to go to bed
[23:56] <\sh> good night guys
[23:56] <Fujitsu> Night \sh.
[23:57] <LaserJock> goodnight \sh_away