[01:58] <bddebian> Heya gang
[02:00] <limac> hey
[02:00] <blueyed> Hi bddebian
[02:04] <bddebian> Hello limac, blue
[02:04] <bddebian> err blueyed
[02:04] <limac> hey
[02:05] <blueyed> good night. ツ (smiley copied from JanC)
[02:06] <JanC> blueyed: and I copied it from Seveas  ;)
[02:06] <bddebian> bunch of plagairists
[02:07] <JanC> hehe
[02:07] <blueyed> lol. thought so. must put this on some hotkey.. :)
[02:07] <JanC> blueyed: if you use xchat, it has an auto-replace function
[02:08] <blueyed> JanC: I want this everywhere..
[02:08] <JanC> normally it's used to fix "teh" → "the" typos
[02:08] <JanC> but I use it to make typing nice unicode symbols easier
[02:10] <blueyed> Now I have it in konversation at least =)
[02:18] <nenolod> hi, does anyone know if "# comments" are allowed in debian/control ?
[02:19] <RAOF> nenolod: Yup.  Why wouldn't they be?
[02:19] <nenolod> ok, thanks ;)
[02:20] <LaserJock> nenolod: why do you want to add a comment?
[02:20] <nenolod> LaserJock, "# $Id control v1.67 ... nenolod Exp $"
[02:20] <nenolod> LaserJock, :)
[02:21] <nenolod> e.g. RCSID
[05:06] <LaserJock> man this channel is crazy tonight, woohoo
[05:07] <StevenK> Ponies!
[05:08] <LaserJock> gotta write some code to mash Fortran and Python together
[05:09] <bddebian> ugh
[05:15] <superm1> LaserJock, then does it become pytran or Forthon?
[05:16] <LaserJock> hehe
[05:17] <bddebian> Forth ;-P
[05:18]  * bddebian wonders if anyone "gets" that
[05:19] <StevenK> Boo, hiss
[05:19]  * StevenK beats bddebian with a SPARC PROM manual
[05:19] <bddebian> heh
[05:21] <LaserJock> ohhhh, I think I love lambda functions
[05:21] <RAOF> Quick, simple anonymous functions are lovely things.
[05:22] <joejaxx> StevenK: lol
[05:22] <joejaxx> how is everyone doing ? :)
[05:29] <superm1> hey joejaxx
[05:29] <superm1> you still got that BT keyboard you bought at UDS?
[06:15] <joejaxx> superm1: yeap
[06:15] <superm1> joejaxx, did you use it with ubuntu at all ever?
[06:15] <joejaxx> no i have not
[06:15] <superm1> joejaxx, ah i see
[06:15] <superm1> i just bought one myself
[06:15] <joejaxx> my laptop that has bluetooth is a Broadcom 4328 AGN
[06:16] <joejaxx> so i do not know if bluetooth works as i have to use ndiswrapper
[06:16] <joejaxx> ah ok
[06:16] <joejaxx> how is that coming along?
[06:17] <superm1> well it paired fine
[06:17] <superm1> i picked up a cheap BT usb adapter
[06:17] <superm1> and it works and all
[06:17] <superm1> except for the fn key
[06:17] <superm1> and consequently the fn buttons
[06:17] <joejaxx> ah ok
[06:17] <joejaxx> yeah
[07:05] <dholbach> good morning
[07:06] <LaserJock> morning dholbach
[07:06] <dholbach> hey LaserJock
[07:06] <superm1> good morning dholbach
[07:06] <dholbach> heya superm1
[07:08] <TheMuso> Hey dholbach
[07:09] <dholbach> hey TheMuso
[07:17] <LaserJock> dholbach: is the new SRU policy that only 1 ~motu-sru ack is needed, or 2?
[07:18] <persia> Do we have members of ~motu-sru yet?  (and I thought one)
[07:18] <dholbach> persia: just announced it
[07:19] <LaserJock> I wish we could do 2, but I guess that's already been decided
[07:19]  * persia catches up on mail
[07:19] <dholbach> LaserJock: pitti's proposal says "... require an ack from a team member before the upload is done"
[07:34] <kagou> Good morning
[07:34] <joejaxx> Good MOrning
[07:34] <joejaxx> lsddjflskdjfskld
[07:34] <joejaxx> Good Morning*
[07:38] <dholbach> LaserJock: might be a good idea, if the new motu-sru team met once and decide on the workflow and everything - what do you think?
[07:39]  * Fujitsu agrees that two acks is a good idea.
[07:39] <imbrandon> moins all
[07:39] <Fujitsu> yourebrandon!
[07:39] <imbrandon> heh
[07:39] <dholbach> congratulations LaserJock, imbrandon, jdong, TheMuso, dktrkranz btw :)
[07:39] <StevenK> "No, *I'm* Brandon!"
[07:40] <StevenK> Aww, my -sru hat is gone
[07:40] <imbrandon> StevenK: hehe
[07:40] <dholbach> StevenK: seems we didn't get your "hey, I'd like to" mail in time - but there's still motu-uvf :)
[07:41] <LaserJock> dholbach: yeah, I think a little IRC meeting or at least an email discussion would be good to start things off
[07:41] <dholbach> LaserJock: rock on - pitti will be delighted
[07:41] <StevenK> dholbach: I didn't want to, though. :-)
[07:42] <dholbach> StevenK: don't complain about missing hats then :)
[07:42] <LaserJock> we need to figure out what to do with the 7 existing ~motu-sru bugs
[07:42] <StevenK> dholbach: :-P
[07:42] <joejaxx> StevenK: maybe it is just invisible :)
[07:42] <dholbach> LaserJock: looks like you have an agenda already :)
[07:42] <LaserJock> dholbach: yep
[07:42]  * dholbach gets more coffee and some bits of breakfast
[07:42] <imbrandon> heh yea
[07:44] <imbrandon> LaserJock: are we just gonna use the -motu list ? e.g. where whould i mail a meeting proposal time? i think a short irc meeting to kick things off quickly would work and longer stuff on the ML
[07:45] <LaserJock> imbrandon: I think using -motu is good
[07:45] <imbrandon> k
[07:45] <LaserJock> gives a chance for feedback
[07:46] <LaserJock> the oldest bug sub'd to ~motu-sru is from 2007-07-25
[07:47] <LaserJock> we should make sure the wiki is updated if it isn't already and let people know we're open for business
[07:47] <LaserJock> and decide on what we want to do with the old ones
[07:48] <LaserJock> I'm guessing just taking them as-is would be fine
[07:48] <imbrandon> yea, you said there is less than 10 old ones? i say if they still apply ( e.g arent superceeded etc ) me and you could probably knock those out quickly
[07:48] <imbrandon> and if they are old-ish then reject them asking for an update
[07:49] <dholbach> LaserJock: you ROCK :)
[07:49] <LaserJock> imbrandon: there are 7 (1 assigned and 6 sub'd)
[07:49] <imbrandon> i'm just getting awake and havent opened a browser yet, but i'll check the queue first thing ( after email )
[07:49] <imbrandon> LaserJock: cool, thats not too bad of a backlog
[07:50] <LaserJock> imbrandon: no, not at all
[07:50] <imbrandon> luckly i think all of us overlap nicely on irc so irc meetings shouldent be hard to setup
[07:50] <imbrandon> heh
[07:52] <imbrandon> StevenK: wasent you reciently using qdvdauthor ? was it just using it or was you updating it ( there is a mail on -motu about adding a mplayer dep , and i am guessing that would kick it to multiverse )
[07:53] <geser> good morning
[07:53] <joejaxx> Good Morning geser
[07:53] <imbrandon> heya geser
[07:54] <LaserJock> it doesn't look like StableReleaseUpdates has been updated
[07:54] <StevenK> imbrandon: I wasn't updating it, I was attempting to use it and wanting to kill myself.
[07:54] <imbrandon> ahh hehe
[07:54] <imbrandon> ok
[07:56] <TheMuso> Thanks guys. Yeah a meeting sounds good, please keep me posted.
[07:56] <TheMuso> Back in a while.
[07:59] <superm1> imbrandon, would making it a recommend like I had mentioned to the poster kick it to multiverse too though?
[08:00] <imbrandon> i dont think so
[08:00] <superm1> i think that should be sufficient then
[08:00] <imbrandon> but if the program is useless without it its kinda a depend not recomend
[08:00] <superm1> well if you have preconverted files though
[08:00] <superm1> i'm pretty sure it works out okay
[08:00] <superm1> or if they are recorded in the correct format
[08:00] <persia> superm1: "Recommends" still makes it multiverse: you need Suggests: (see debcheck output for examples)
[08:00] <superm1> o
[08:01] <imbrandon> ahh in that case might as well make it a depend, as "preconverted" files use case is slim
[08:01] <persia> Really?  Remixing MPEGs from the digital camera or phone is that rare?
[08:02] <imbrandon> persia: slimer than someone ripping a dvd and remixing it, yea, visit the forums hehe
[08:02] <persia> imbrandon: Right, but which is the advertised normal use case?
[08:02] <imbrandon> persia: both
[08:02] <superm1> well also they still need to be the right resolution
[08:02] <superm1> most phones or cameras dont shoot in 720x480
[08:02]  * persia notes that ripping & remixing DVDs is usually outside accepted uses of the media
[08:03] <persia> superm1: Good point.
[08:04] <superm1> admittedly though someone will want to investigate this for sure.  i wouldn't expect mplayer to be used for the conversion, but rather ffmpeg or mencoder
[08:04] <imbrandon> yea mencoder should be used imho, but who knows what they hardcoded in
[08:04] <imbrandon> i havent looked
[08:05] <imbrandon> either way though both are multiverse are they not?
[08:05] <superm1> well yeah
[08:05] <LaserJock> bah, I hate dealing with data that's larger than RAM
[08:06] <imbrandon> LaserJock: heh
[08:06] <LaserJock> I'm trying to parse a 350MB data file
[08:06] <LaserJock> in python ...
[08:06] <LaserJock> and not have it take a century to do
[08:06] <LaserJock> or run out of RAM
[08:07] <RAOF> LaserJock: You can't use the fun of iterators to do that?
[08:07] <persia> LaserJock: parse it bit by bit
[08:07] <LaserJock> persia: yeah, that's the hard part
[08:07] <imbrandon> LaserJock: yea just grab chunks
[08:07] <RAOF> Why am I unable to switch to a VT?
[08:07] <imbrandon> RAOF: hardy? no idea, i noticed i couldent earlier
[08:07] <imbrandon> too
[08:07] <soren> RAOF: ConsoleKit, I belive.
[08:07] <RAOF> Ah.  Yay.
[08:08] <imbrandon> soren: ? ouch
[08:08] <LaserJock> the data is actually 25k consecutive experiments that have 502 lines each and I want to average groups of them
[08:08] <imbrandon> so when my X breaks i'm screwed heh
[08:08] <soren> RAOF: You actually switch to another VT, but then ConsoleKit switches you back, IIRC.
[08:08] <soren> imbrandon: No, in that case, you're fine, actually.
[08:08] <RAOF> soren: Yeah, that's what it looks like.
[08:08] <persia> LaserJock: Right.  Read 25k.  Set a couple variables, forget the 25K.  Read the next 25k.
[08:08] <imbrandon> yea thats the behavure i noticed too
[08:09] <imbrandon> soren: not really, i had some funky VerRefresh values and needed a VT
[08:09] <soren> imbrandon: If X isn't running, you can switch VT.
[08:09] <imbrandon> X was running but not usefull
[08:09] <LaserJock> persia: yeah, my advisor wrote a fortran program to do that, but it writes each average to a file
[08:09] <soren> imbrandon: Ah, point.
[08:09] <LaserJock> persia: so I end up with 25k files and I need to do stuff on the data so I'd like to keep it available
[08:10] <imbrandon> soren: is it the intended behavure? e.g is this a bug or a mis-feature ?
[08:10] <soren> imbrandon: Bug.
[08:10] <imbrandon> kk good :)
[08:10] <soren> imbrandon: Ian fixed it in Gutsy, buyt his patch was dropped, afaics.
[08:10] <imbrandon> ahh, yay for bad syncs heheh
[08:10] <LaserJock> imbrandon: who needs a VT
[08:10] <imbrandon> LaserJock: i do regularly
[08:11] <imbrandon> :)
[08:11] <persia> LaserJock: Rock and a hard place.  If you put it all in memory, you don't have any less.  To not have it doubled, read each chunk and stuff into an array, then reset, and load the next chunk.
[08:11] <LaserJock> persia: yeah, I'm working on it
[08:20] <superm1> imbrandon, could i grab you to look over the backport you were looking for a pbuilder log on again?  I attached it earlier today. bug 173684
[08:21] <imbrandon> superm1: sure, i'm about to reboot but i'll grab it before i do
[08:21] <ubotu> Launchpad bug 173684 in gutsy-backports "Please backport mythstream 0.18.1 from hardy" [Undecided,New] https://launchpad.net/bugs/173684
[08:21] <superm1> ok cool thx
[08:21] <\sh> moins
[08:23] <imbrandon> superm1: done, ok brb rebooting
[08:23] <RAOF> Anyone want to test the things needed for the kvm backport?
[08:24]  * imbrandon dosent have the hardware to or i would
[08:24] <soren> RAOF: Which version are you about to backport?
[08:24] <RAOF> imbrandon: You can test that the new bochsbios works with the old qemu
[08:24] <persia> RAOF: Might be worth pinging intuitivenipple (in -bugs or -devel), who has a fair bit of interest in kvm
[08:25] <RAOF> soren: I was thinking the one currently in Hardy, why?

[08:25] <RAOF> soren: Is there a new one in the works?
[08:25] <soren> RAOF: I'll be uploading a new one either today or tomorrow.
[08:25] <soren> RAOF: Upstream is shooting releases out like mad these days :)
[08:25] <RAOF> soren: Right.  So, I'll kill that backport request, and check that the new one works on Gutsy.
[08:26] <RAOF> :)
[08:26] <RAOF> C'mon apt-file, finish updating so I can crash my videocard reverse-engineering the POST sequence.
[08:28] <jonnymind> Helllo,
[08:29] <jonnymind> I received an update on bug 174470 asking to "link the source package".
[08:29] <ubotu> Launchpad bug 174470 in ubuntu "Package for the Falcon Programming Language" [Wishlist,Confirmed] https://launchpad.net/bugs/174470
[08:29] <persia> jonnymind: Add a link to the REVU candidate in the bug description.
[08:29] <jonnymind> Should I provide a link to the revu entry?
[08:29] <jonnymind> Ok, thanks.
[08:31] <Fujitsu> Yay, namespace collision.
[08:32] <jonnymind> Fujitsu: you mean me?
[08:33] <soren> Wow, there's a shocker. vmware-tools doesn't build on hppa.
[08:34] <Fujitsu> soren: That's *absolutely terrible*.
[08:34] <Fujitsu> jonnymind: Right, I thought the falcon package I'd seen referenced was the repository generation tool.
[08:34] <jonnymind> Oh.Ok, as I proposed, an alternate valid name may be falconpl.
[08:34] <jonnymind> it's also the name of the site...
[08:34] <soren> Fujitsu: Especially since I explicitly stated Architecture: i386 amd64. Go figure.
[08:35] <jonnymind> fujitsu: may you please add a note on the bug, so I remember to upload a name-changed package this night?
[08:35] <Fujitsu> soren: Did the sbuild notice that?
[08:36] <Fujitsu> jonnymind: Oh, falcon is probably OK.
[08:36] <soren> Fujitsu: Nope. http://launchpadlibrarian.net/10821083/buildlog_ubuntu-hardy-hppa.open-vm-tools_2007.11.21-64693-0ubuntu1_FAILEDTOBUILD.txt.gz
[08:36] <jonnymind> fujitsu: acked. However, I am ready to change the name if needed.
[08:38] <Fujitsu> soren: Hm. I knew Soyuz bits didn't respect the Architecture field, and I guess their mangled sbuild doesn't either.
[08:39] <soren> Fujitsu: Well, it's a bit more complicated than that.
[08:39] <soren> Fujitsu: It has an arch: all binary package in it, too, so dpkg cleverly sets "Architecture: any" in the .dsc.
[08:39] <persia> soren: Get someone update P-a-s and reupload.
[08:39] <soren> persia: I know, I know. I just still think it's silly.
[08:40] <Fujitsu> soren: Oh, so it wasn't Architecture: i386 amd64.
[08:40] <persia> soren: I completely agree with that :)
[08:40] <soren> Fujitsu: There are two binary packages that are i386 amd64, and one binary-indep package.
[08:43] <Fujitsu> Right, but Soyuz shouldn't have to think to look at the binaries.
[08:44] <soren> Fujitsu: Agreed.
[08:44] <soren> Fujitsu: ...but dpkg also shouldn't say Arch: any, when it's really arch: i386 amd64 all.
[08:44] <soren> IMO.
[08:45] <Fujitsu> It should be Architecture: i386 amd64.
[08:45] <soren> I don't think it's a bug per se. Looking at the dpkg code reveals that it's quite intentional.
[08:45] <soren> Fujitsu: Debatable.
[08:45] <Fujitsu> Or possibly all too, but I don't think so.
[08:45] <Fujitsu> Right;
[08:45] <Fujitsu> s/;/./
[08:47] <soren> I hadn't thought about the arch: all package when I started this light rant .)
[08:47] <soren> s/\.)/:)/
[08:48] <Fujitsu> sbuild could well bail out at the start if it is in fact an Architecture: i386 amd64 package.
[08:49] <persia> Fujitsu: stock sbuild does
[08:49] <Fujitsu> persia: Right, that's why I thought Soyuz's might.
[08:50] <Fujitsu> But Soyuz's is very special with a `th'
[08:50] <persia> Fujitsu: :)
[08:51] <siretart_> persia: what is 'stock' sbuild?
[08:52] <persia> siretart_: In my book, the currently shipped Ubuntu version (now hardy).
[08:52] <siretart_> persia: heh
[08:52] <imbrandon> moins siretart_
[08:53] <persia> siretart_: It's fair to say that different people have different definitions of "stock", so sid, lenny, etch, dapper, and gutsy sbuilds would qualify for others.
[08:53] <siretart_> persia: the packaged one in debian/ubuntu is actually a bastardised fork of the 'original' sbuild used on the debian buildds
[08:53] <imbrandon> yea stock imho would be debian stable, anything else should be noted heheh , just kidding, current released ubuntu actualy imho
[08:53] <siretart_> persia: however, it has many very useful features and bugfixes added, which the original one is lacking. and many buildd admins seem to run a locally modified version
[08:53] <persia> siretart_: Makes sense.  I suspect Soyuz of sharing that parentage, but not having the experience of BTS and LP along the way.
[08:55] <siretart_> I'd expect soyuz's sbuild to be a custom fork derived from http://db.debian.org/debian-admin/Packages
[08:55] <siretart_> heyha imbrandon
[08:55] <persia> siretart_: That would make the most sense.
[09:03] <imbrandon> UDS-MTV was ~nov 2005 correct ?
[09:04] <StevenK> imbrandon: Sounds about right, it was the one before Sevilla
[09:04] <imbrandon> yea
[09:04] <Fujitsu> Sevilla was April, wasn't it?
[09:04] <Fujitsu> That makes it Nov 2006.
[09:04] <imbrandon> eer yea 06 not 05
[09:04] <imbrandon> good catch
[09:05] <StevenK> Oh yeah, I forgot imbrandon can't count.
[09:05] <Fujitsu> Heh.
[09:05] <indraveni> hi all
[09:05] <Fujitsu> Hi indraveni.
[09:05] <indraveni> if I am creating a debian package which need to overwrite  a file created by any other package, then I am facing a problem, like, couldnot overwrite the file alacarte.mo creating by alacarte package.
[09:06] <Fujitsu> indraveni: Don't overwrite said file.
[09:06] <persia> indraveni: Why do you seek to overwrite the file (the correct method depends on the reason)?
[09:06] <soren> indraveni: Explain how it "needs to overwrite a file created by another package"?
[09:06] <Fujitsu> Particularly a translation.
[09:06] <indraveni> I am done some localisation and withou creating the complete package for each and everyt
[09:07] <indraveni> i am trying to convert the po to mo files and place them in the locales
[09:07] <persia> indraveni: You really don't want to do it that way: you want to push your .po files to all the individual packages.
[09:07] <imbrandon> man my mother-inlaw got my daughter a digital camera for xmass, i was just trying it out, this thing sucks, almost so bad as to not give it to her at all
[09:07] <indraveni> yes, but my aspect it, just by installing one package, its should provide a localised desktop for gnome,
[09:08] <indraveni> *is
[09:08] <Fujitsu> indraveni: We have language packs for that.
[09:08] <indraveni> persia, if i do as per your said, then I need to recompile each and every pacakge
[09:08] <persia> indraveni: I understand, but the infrastructure doesn't support that well at all.  It'd be much better to push it all to GNOME with your localisations, so no extra package is required.
[09:09] <indraveni> persia, yes, but it will take time, i feel
[09:09] <persia> indraveni: Well, maybe, but more likely you can get others to recompile all the packages (and yes, it will take time).
[09:10] <indraveni> persia, so there is no other way to remove this conflict ?
[09:10] <persia> indraveni: Not for that purpose.
[09:10] <geser> indraveni: if possible try to get your translation accepted by the gnome project so others benefit from it to
[09:14] <jonnymind> Ppl, I sign off. Later.
[09:49] <_polto_> hello all
[09:54] <imbrandon> ello _polto_
[09:59] <_polto_> hello imbrandon
[10:23] <_polto_> Fujitsu, so i continue here..
[10:23] <Fujitsu> _polto_: Most probably.
[10:24] <\sh> Fujitsu, do you happen to know if there is a CVE pending for the latest drupal 5.3->5,4-> 5.5 fixes 5.4 fix?
[10:24] <Fujitsu> \sh: I haven't looked, sorry. I've been a little busy over the past week.
[10:24] <\sh> Fujitsu, me too :)
[10:25] <\sh> Fujitsu, and I didn't find anything about it
[10:25] <\sh> not even for the 5.4 fix
[10:25] <Fujitsu> Checked security-tracker.d.n?
[10:25] <\sh> not now
[10:25] <_polto_> where is a new version of liblivemedia , this new release contain patches we needed for compatibility with our hardware. (network camera) I used PPA before to have our own patched version of liblivemedia, but i think others could also benefit of updates in the new version. Can somebody update libelivemedia to the last version ?
[10:25] <\sh> nothing
[10:25] <Fujitsu> !info liblivemedia-dev hardy
[10:25] <ubotu> liblivemedia-dev: multimedia RTSP streaming library. In component universe, is optional. Version 2007.02.20-2 (hardy), package size 885 kB, installed size 3712 kB
[10:26] <Fujitsu> Debian bug #453449
[10:26] <ubotu> Debian bug 453449 in livemedia-utils "New upstream available" [Wishlist,Open] http://bugs.debian.org/453449
[10:27] <_polto_> live.2007.12.07
[10:27] <_polto_> thanks !
[10:27] <Fujitsu> I'll watch Debian, and if they don't act, I will. If I don't, poke in here in a couple of weeks.
[10:28] <_polto_> cool, i'll do. thanks
[10:29] <frenchy> Hi all, is today the last day to get advocates on REVU for hardy?
[10:33] <\sh> Fujitsu, do you have the powers to upload to security testing somehow?
[10:34] <Fujitsu> \sh: No, but I can modify stuff on the Debian security tracker.
[10:35] <geser> frenchy: FeatureFreeze is around Valentine's day, so you still have some time
[10:36] <\sh> Fujitsu, hmm...that doesn't help ;) we could need a universe-security queue, and later on our security team can push them to -security
[10:36] <frenchy> geser: Thanks a lot!  Few, I thought that my days were numbered.
[10:37] <Fujitsu> \sh: That would be nice. I suspect we will get that once security moves into Soyuz.
[10:37] <\sh> ok cacti fixed ...the new fixes I have to check and let's see if I will request my first cve id ;_9
[10:39] <Fujitsu> Yay!
[10:39] <geser> frenchy: this week is DebianImportFreeze, that's when we stop automatically pulling packages from Debian, only on request after that
[10:40] <proppy> geser: is the freeze already in place ?
[10:40] <frenchy> geser: Thanks, I wasn't sure if that meant "new package freeze" but that's cleared it up.
[10:41] <geser> proppy: afaik no, the wiki says Dec 14th
[10:41] <proppy> geser: ok thanks :)
[10:41] <\sh> CVE-2007-6279 CVE-2007-6278 CVE-2007-6277 hooray for libflac
[10:41] <ubotu> Multiple double-free vulnerabilities in Free Lossless Audio Codec (FLAC) libFLAC before 1.2.1 allow user-assisted remote attackers to execute arbitrary code via malformed (1) Seektable values or (2) Seektable Data Offsets in a .FLAC file. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-6279)
[10:41] <ubotu> Free Lossless Audio Codec (FLAC) libFLAC before 1.2.1 allows user-assisted remote attackers to force a client to download arbitrary files via the MIME-Type URL flag (--&gt;) for the FLAC image file in a crafted .FLAC file. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-6278)
[10:41] <ubotu> Multiple buffer overflows in Free Lossless Audio Codec (FLAC) libFLAC before 1.2.1 allow user-assisted remote attackers to execute arbitrary code via large (1) Metadata Block Size, (2) VORBIS Comment String Size, (3) Picture Metadata MIME-TYPE Size, (4) Picture Description Size, (5) Picture Data Length, (6) Padding Length, and (7) PICTURE Metadata width and height values in a .FLAC file, which result in a heap-based overflow; and large (8) VORBIS Comme
[10:45] <RAOF> asac: Ping!  I'd like to know about the status of firefox-dev, libxul, and xulrunner1.9 in hardy. (IE: what would you like me to build-depend on :))
[10:57] <pochu> RAOF: xulrunner1.9 is now in main, and there are plans to port apps to it, AFAIK. So use it ;)
[10:58] <pochu> asac: that's right, isn't it? ^
[10:58] <asac> RAOF: yes, use xulrunner-1.9-dev
[10:58] <asac> there might be a bit coding required ... (mostly build-system)
[10:58] <asac> if you need support ask on #ubuntu-mozillateam
[10:59] <pochu> asac: I need to port liferea to xul 1.9... any hints? :)
[10:59] <asac> https://wiki.ubuntu.com/XulrunnerGecko
[10:59] <pochu> asac: thank you
[10:59] <asac> pochu: i think lifearea is a bit tricky
[10:59] <asac> you have to wait for python gtkmozembed
[10:59] <asac> ??
[10:59] <pochu> python? Liferea is C
[10:59] <asac> really ... last time i looked it looked like a mix
[11:00] <asac> if its just C the instructions should be good enough to start with
[11:00] <pochu> asac: ok, I'll look into it. thanks again :)
[11:00] <asac> pochu: see how far you get and ask for help if get stuck :)
[11:25] <RAOF> asac, pochu: Thanks.  xulrunner-1.9-dev it is.
[11:27] <RAOF> I wonder why miro goes to the trouble of having a --xine-driver commandline option when they hardcode the driver to "xv" anyway...
[11:30] <RAOF> Oh, wow.  That looks like a bit of work.
[11:30] <StevenK> RAOF: Hrm?
[11:33] <RAOF> StevenK: Porting apps to xulrunner-1.9
[11:34] <StevenK> RAOF: Ask asac for help.
[11:34] <RAOF> StevenK: Oh, I will if I run into trouble.
[11:35] <RAOF> The wiki seems fairly self-explainatory.
[11:35] <RAOF> It just suggests that the Miro merge isn't going to be done tonight.
[11:35] <persia> RAOF: I seem to remember tracking down some crasher with miro going through xine and into xv (or do I misremember).  Perhaps the hardcoding was to avoid that?
[11:35] <RAOF> persia: There's a bunch of "XINE_DRIVER_HACK" code lying around there, yes.
[11:36]  * StevenK has this feeling that he is starting too late to do a run through Maraudon
[11:36] <RAOF> persia: But that was when Xine itself was dying in Xv.  So hardcoding Xv  as the driver you want deosn't seem like a good way to get around that bug.
[11:37] <persia> RAOF: I thought the bug was xine not checking xv state properly, and by having miro do it directly, the bug wasn't exposed, but my memory for that is poor, as I'm not really familiar with any of miro, xine, or xv.
[11:38] <RAOF> persia: Hm.  That's possible.  I do remember running through that bug, but not enough of the details.
[11:38] <persia> RAOF: Then we're in the same state :)
[11:39] <asac> RAOF: working on miro?
[11:39] <RAOF> Still, the hardcoding doesn't make sense (and my patch to actually respect the --xine-driver commandline option won't influence any workarounds they have)
[11:40] <RAOF> asac: Yup.
[11:40]  * RAOF should probably mark this in LP.
[11:40] <asac> RAOF: please get together with Ubulette ... he worked on this at some point
[11:40] <asac> RAOF: was miro the application that uses python + C api of gtkmozembed?
[11:41] <RAOF> asac: On the xulrunnerisation?  Cool.
[11:41] <RAOF> asac: Yup, that'd be miro.
[11:41] <asac> RAOF: yes ... he was waitinf for my python package
[11:41] <asac> RAOF: i guess you will need it too
[11:41] <asac> RAOF: i will ping you later today ... have to cleanup the patch and upload to ppa or something i guess
[11:42] <RAOF> Great.
[11:42] <RAOF> I'll fix up the rest of the merge, then see about xuling it.
[11:42] <persia> Does anyone have Dell hardware?  I think http://revu.ubuntuwire.com/details.py?package=firmware-tools is mostly good, but I can't test (leftovers are confusing versioning scheme (hard to fix due to third party repos) and differentiating \- and \(hy in the manpage).
[11:42] <asac> RAOF: yes ... make sense to do the merge and then the porting
[11:43] <RAOF> asac: But block on the porting before uploading, right?
[11:43] <dfiloni> persia: wxwidgets2.8 in REVU where is? I don't find it
[11:44] <persia> dfiloni: hidden :)  http://revu.ubuntuwire.com/details.py?package=wxwidgets2.8 is the URL.  All my comments are in the bug.  I'm still curious if it's worth patching the autogenerated file.
[11:45] <dfiloni> persia: do you think is good?
[11:45] <persia> s/the bug/bug #133888/
[11:45] <ubotu> Launchpad bug 133888 in wxwidgets2.8 "upgrade wxwidgets2.8 to the 2.8.4.2 release" [Wishlist,Confirmed] https://launchpad.net/bugs/133888
[11:45] <persia> dfiloni: I think so, I just don't understand if the dpatch is required or not.  Robin's latest comment makes me think not.
[11:46] <dfiloni> persia: I used dpatch to fix wxPython/wx/build/build_options.py file
[11:51] <persia> dfiloni: I know, but Robin says it is an autogenerated file, (although the build log makes it appear to be used).  I just don't know enough about that file to have an understanding of how it should work (and my WX knowledge is all on the C++ side: not the python bindings)
[11:52] <dfiloni> persia: in the previous version (2.8.4) the file was fixed
[11:53] <persia> dfiloni: I saw that, which is why I thought the dpatch was correct.  At this point, I'm hoping someone with more python knowledge than I will express an opinion.  If you're sure, just put a comment in the bug that it is the correct behaviour, and subscribe the sponsors queue (my build system can't handle that package anyway)
[11:55] <dfiloni> persia: now I'm working at 2.8.7.1 version, but lintian show me a lot of warnings or errors that I want to fix
[11:56] <persia> dfiloni: Thanks for that.  I agree with pochu that it's likely best to get 2.8.6.1 in now, and update later, rather than waiting (unless you're likely to finish in the next couple days).
[11:56] <pochu> s/next couple days/today/ :-P
[11:56] <dfiloni> persia: I don't think I can finish this weeks
[11:57] <persia> dfiloni: Understood.  It's best to take the time to get it right, so let's move ahead with 2.8.6.1: it just needs confirmation that the dpatch is correct, and can be pushed to the sponsors queue.
[11:57] <persia> pochu: Do any of your clients use the python bindings?  Can you verify the dpatch?
[11:59] <StevenK> Queue!
[11:59] <persia> StevenK: ?
[12:00] <RAOF> Hm.  It seems UNSW is burning down.
[12:00] <StevenK> persia: http://www.jonobacon.org/?p=1083
[12:00] <StevenK> RAOF: Oh?
[12:00] <imbrandon> persia: jono's name means Queue in lang
[12:00] <persia> Aha!
[12:00] <StevenK> Finnish
[12:00] <jono> haha
[12:00] <RAOF> StevenK: Well, either that or they've chosen an odd time of the day to run big firere drills
[12:01] <StevenK> Er, yeah.
[12:01] <Hobbsee> RAOF: that's not good.  i don't want o hear of any other disasters anywhere in sydney.
[12:01]  * persia enjoys the complete lack of relation of finnish to nearly anything else
[12:01] <StevenK> Hobbsee: The amount of tarps on roofs around here is disturbing me
[12:01]  * Hobbsee also hopes that if we get another hailstorm, we get it soon.
[12:01] <Hobbsee> StevenK: i havent' actually seen any - but i'll admit that i wasn't looking too hard.
[12:02]  * RAOF obviously lives in the *safe* part of Sydney.
[12:02] <StevenK> Where safe == boring
[12:02] <RAOF> Or, alternatively, doesn't get around much.
[12:02] <imbrandon> man this camera my mother-in-law got my daughter is horrible, here is the "test" picture i took with it a little bit ago
[12:02] <imbrandon> http://www.imbrandon.com/images/album/unsorted/page/1/photo/work-area
[12:02]  * Hobbsee hasn't dared to call the insurance company yet
[12:02] <Hobbsee> StevenK: did westpoint lose power?
[12:03] <StevenK> Hobbsee: Not that I noticed
[12:04] <RAOF> Ok.  That's a night.  Bed awaits.
[12:04] <StevenK> imbrandon: Is that a digital camera or a phone?
[12:04]  * persia suspects most phones have higher resolution
[12:04] <imbrandon> digital camera, for a 10 year old, just plain nasty
[12:04] <StevenK> Er, yeah.
[12:04] <StevenK> I could paint a better picture
[12:05] <RAOF> imbrandon: Your theme is borken in ff-3 :).
[12:05] <RAOF> Also.  Urgh.
[12:05] <imbrandon> lol yea exactly, i'm pondering not giving it to her and just buying one for her myself, this thing is nuts, but i dont wanna piss of the mother-in-law
[12:05] <Fujitsu> Uuurgh.
[12:05] <imbrandon> RAOF: yea it is in IE7 too, i'll work a bit more on it tomarrow :)
[12:05] <pochu> persia: you mean a python app using the wx bindings? I can try, sure.
[12:05] <RAOF> Maybe it's an artistic phone?
[12:05] <StevenK> imbrandon: Make/model?
[12:06] <StevenK> Hell, my digital camera is two years old, and it does much better
[12:06] <imbrandon> Model #98379 from Sakar International
[12:06] <persia> pochu: Thanks.  That's the last bit of confirmation I think is required before it can be sponsored (as I'm not sure how to evaluate whether the dpatch is required).
[12:06]  * persia 's phone is > 2 years old and does better
[12:06] <StevenK> imbrandon: There's your problem
[12:13] <imbrandon> yea i'm just not even gonna give this to her, hell it even has to have a special app in wine to get the pics off anyhow
[12:13] <imbrandon> i can get hear a better one for $50 cheap
[12:13] <imbrandon> thats linux friendly and tons better res
[12:13] <imbrandon> s/hear/her
[12:13] <pochu> persia: woops, spe uses 2.6 even if 2.8 is available :)
[12:13] <imbrandon> i'll just keep this one on the shelf so if the mother-in-law ever asks about it
[12:14] <imbrandon> i still have it arround :)
[12:14]  * pochu wonders what to use instead...
[12:15] <pochu> phatch... and I'm the maintainer :P
[12:18] <ruoso> Hi... I'm the maintainer of gnome-mag in debian. The gnome-mag package in ubuntu does not support the colorblind accessibility filters... the latest version (just uploaded) supports it just fine with the colorblind applet... how does it work to get that features to ubuntu?
[12:19] <persia> motu-sru team: should candidate SRUs be subscribed for approval?
[12:19] <pochu> ruoso: is it that the schemas installation?
[12:20] <ruoso> pochu, not only that, but also the linking with libcolorblind
[12:20] <ruoso> the ubuntu version doesn't seems to be linked with it
[12:20] <ruoso> the last upload is about the gconf schemas i mean
[12:22] <DktrKranz> persia, I think subscribing motu-sru is enough, but there should be consensus on procedures
[12:23] <pochu> ruoso: if nobody does it, I'll merge it with Debian tomorrow, so we get the fix.
[12:23] <imbrandon> persia: yea subscribe so its in our queue
[12:23] <pochu> dholbach_: it's your merge ^ wanna do it? If not, mind me doing it? :)
[12:24] <ruoso> pochu, thanks... I've already tested in a friend's computer doing a backport to the latest stable... and it worked just fine (except that ubuntu seem to be using python2.5 by default)
[12:24] <ruoso> and I needed to change the install file
[12:24] <persia> Thanks DktrKranz, imbrandon.  Pending formal announcement of the procedure, I'll suggest subscribing the team while processing the sponsors queue.
[12:25] <imbrandon> persia: sounds good
[12:26] <DktrKranz> imbrandon, what about defining a preliminary roadmap to be discussed during next MOTU meeting?
[12:27]  * persia likes the combination of team coordination with the general meeting to allow non-members to heckle :)
[12:27] <imbrandon> DktrKranz: yea i think we should get a small irc meeting to get the plem roadmap going in the next day or so assuming we can get everyone on
[12:27] <imbrandon> and then a more formal one etc at the next -motu meeting if needed/wanted
[12:27]  * Hobbsee heckles persia
[12:28] <persia> Hobbsee: My dead uncle could do a better job of heckling today.  Did you learn stage presence from a bear?

[12:28] <Hobbsee> :P
[12:28] <Hobbsee> muhahahaha
[12:29]  * Hobbsee wins.
[12:29] <DktrKranz> imbrandon, I'll be in Rome without internet access on Dec 12/13, no problem to take it tomorrow or friday
[12:30] <StevenK> persia, exit stage left
[12:30] <StevenK> :-P
[12:30] <pochu> persia: phatch works fine with python-wxgtk2.8. Updating the bug report.
[12:31] <persia> pochu: Great!  Stick it in the sponsors queue, and we'll hope someone has a larger build-server quota than I :)
[12:32] <pochu> persia: cool, doing it!
[12:41] <ruoso> pochu, lool will be uploading a new version soon which fixes some other things (like python policy conformance).. you probably want to wait for him to finish before the sync...
[12:56] <dholbach_> pochu: which merge?
[13:05] <persia> dholbach: gnome-mag (although that may not help you unless pochy is around to see your response :) )
[13:05] <dholbach> pochu: no, I'm happy if you take care of it
[13:09] <pochu> dholbach: ok.
[13:09] <pochu> persia: pochy? :P
[13:09] <pochu> ruoso: sure, will wait for it.
[13:13] <persia> oixgy: finger drift :)
[13:17] <Ubulette> RAOF: what about miro ?
[13:17] <StevenK> Ubulette: RAOF is undoubtedly in bed.
[13:17] <Ubulette> oh
[13:17] <StevenK> Ubulette: I can ring him if you like ... :-P
[13:18] <Ubulette> nm, i'll wait
[13:20] <StevenK> Ubulette: There was a :-P on that line for a reason. :-)
[13:21] <Ubulette> :)
[13:39]  * persia seeks julien lavergne
[13:47] <slicer> Ok, I'm a bit of a noob.. If you install ubuntu-server, can you still apt-get/aptitude packages from the desktop edition in an easy manner?
[13:48] <imbrandon> yes , exactly the same
[13:48] <persia> slicer: It's just a different meta-package, with a different set of default applications (and a different set of things shipped on the CD).
[13:49] <slicer> Can I quote you on that? I have a end-user who is being a .. er.. nice word... "problem"?
[13:49] <persia> slicer: If you like, but I'm not sure how strong a quote is compared to your statement, or a pointer at the code :)
[13:50] <slicer> Considering I've been told I know nothing about Ubuntu, it seems I'll have to quote outside sources.
[13:50] <slicer> At times, it's really hard to keep a civil tone with some people.
[13:51] <imbrandon> slicer: heh, sounds like you need a new class of people to associate with
[13:51] <imbrandon> :)
[13:52] <zul> morning
[13:53] <imbrandon> moins zul
[13:55] <zul> hey imbrandon how goes the battle?
[13:59] <imbrandon> good good, bout to sleep for a few hours then work on some SRU stuff :)
[13:59] <imbrandon> night all
[13:59] <zul> ooooh..
[14:01]  * persia seeks stephane brunner
[14:08] <dsop> okay, today is revu day, so i'll try again. Please, is there some motu that's willing to review my package. I still search for a second advocate
[14:09] <ScottK> dsop: Generally it helps if you also provide a link to the package on REVU.
[14:10] <dsop> ScottK: okay, sorry.
[14:10] <dsop> the package url is http://revu.tauware.de/details.py?package=gcutils
[14:11] <dholbach> persia: seems he has not added his IRC nick to his LP profile :/
[14:12] <persia> dholbach: Yep.  That's why he gets a general "* persia seeks ..." annoucement (although sometimes I do that when I'm just feeling lazy). :)
[14:12] <dholbach> persia: hehe
[14:35] <Ubulette> persia, about the menu stuff (in seamonkey), you just want me to use the new "Categories" in my desktop files, right ? like for ex chatzilla, s/Categories=GTK;Network;IRCClient;/Categories=Application;Network;Communication;/   ?
[14:36] <persia> Ubulette: Sortof.  "Application" is a deprecated category.  I don't remember offhand, but I think I was suggesting updates to your menu files, as policy changed from "Apps/..." to "Applications/...".
[14:37] <Ubulette> ix:~/bzr/seamonkey-1.1.dev/debian/menu_dir$ grep Apps/ *desktop
[14:37] <Ubulette> ix:~/bzr/seamonkey-1.1.dev/debian/menu_dir$
[14:37] <Ubulette> i'm puzzled
[14:40] <Ubulette> persia: ^^
[14:40] <mruiz> hi dholbach
[14:41] <persia> Ubulette: menu, not desktop
[14:41] <dholbach> hiya mruiz
[14:41] <Ubulette> ohh
[14:43] <mruiz> dholbach, do you have time to guide me with some questions about hardware-monitor ?
[14:44] <dholbach> mruiz: sure - just ask, if it's not me who answers, somebody else will :)
[14:44] <mruiz> ^^
[14:45] <mruiz> dholbach, REPORT file says that we have conflicts with three files: debian/control, src/monitor-impls.cpp and src/monitor-impls.hpp
[14:46] <dholbach> did you try resolving them?
[14:47] <mruiz> also I consulted about them in the changelog
[14:48] <\sh> woosah....documention: done, server move: done
[14:48] <mruiz> dholbach, differences are related to "iowait" calls
[14:48] <dholbach> mruiz: ah yes, I remember some bug about it
[14:49] <mruiz> dholbach, I think bug 81599
[14:49] <ubotu> Launchpad bug 81599 in hardware-monitor "hardware-monitor cpu monitoring should not include iowait" [Undecided,Fix released] https://launchpad.net/bugs/81599
[14:50] <dholbach> mruiz: seems that http://launchpad.net/~jazzva is working on it too
[14:50] <dholbach> mruiz: got a mail from him this morning
[14:51] <mruiz> dholbach, but I said that I'm working on it -> DaD
[14:52] <dholbach> mruiz: best to coordinate with Jazzva then
[14:52] <mruiz> sure!
[14:52] <dholbach> alrightie :)
[14:52] <dholbach> looks like the patch still needs to be applied
[14:52] <mruiz> yes... I was looking for information in Debian as well
[14:53] <dholbach> nice
[14:53] <mruiz> dholbach, I'll send an email to jazzva. I started to work on this merge during the last week
[14:54] <dholbach> great - thanks a lot
[14:55] <mruiz> dholbach, wait me a minute... I'm writing the email to avoid double work
[14:56] <RainCT> hey
[15:06] <mruiz> dholbach, email -> done :-)
[15:07] <dholbach> great
[15:28] <Volans> Hi, I'm administrator of Italian forum. I developed a Firefox extension to quickly browse sections provided by Italian Community. Extension is published on Mozilla Addons Sandbox, I would like to know if you think it is possible to include it into Universe repository.
[15:30] <persia> Volans: Likely, but you might get better information on what is required in #ubuntu-mozillateam
[15:31] <nxvl_work> dholbach: i was just looking for you
[15:31] <Volans> ok, then I will ask first on mozillateam and after here?
[15:31] <dholbach> nxvl_work: how can I help you?
[15:32] <nxvl_work> dholbach: on saturday i will give a talk about patch systems, and as the audience is not a very expert one i will make a little packaging 101, and i'm wondering if you have some slides i can use for it?
[15:33] <persia> Volans: We're happy to help, but only a small minority of us understand how to package a firefox extension.
[15:34] <dholbach> nxvl_work: I'm sorry - I have no slides for it, but for the patch systems section I'd use https://wiki.ubuntu.com/PackagingGuide/PatchSystems
[15:35] <dholbach> nxvl_work: https://wiki.ubuntu.com/PackagingGuide/Recipes might also be interesting (the first two probably)
[15:36] <nxvl_work> dholbach: yes, i was using the wiki pages for my slides, but i was looking for a quick and little packaging 101
[15:37] <nxvl_work> well, i will base it on your IRC lessons
[15:37] <nxvl_work> :D
[15:37] <dholbach> nxvl_work: hehe, nice
[15:37] <dholbach> nxvl_work: I'll put some effort into producing that kind of 'material' from the packaging guide, but it'll take a bit
[15:37] <Volans> persia: thanks for your attention, for the realization I am in contact with Italians motu, I would like only to know if you think it is possible to include the deb package into Universe, when finished
[15:37] <dholbach> nxvl_work: I'll definitely let you know
[15:38] <persia> Volans: The criteria for inclusion is that two members of ~ubuntu-dev believe it to be useful.  As there are more than two MOTU from Italy, I'd be surprised if it had trouble reaching that, as long as it is actually useful.
[15:39] <DaveMorris> apachelogger: I fixed the control file for cpptest - http://revu.tauware.de/details.py?package=cpptest
[15:41] <apachelogger> DaveMorris: will take another look asap
[15:41] <Volans> persia: thanks for the suggestion ;) i will ask the mozillateam for more specific requirement and after if all it's ok male the package itself
[15:42] <Volans> *make
[15:42] <persia> Volans: Great.  Thanks for taking the trouble to try to get your application into Ubuntu.
[15:42] <nxvl_work> dholbach: i need to send my slides on Wednesday, so i will send you a copy also, to maybe they help you
[15:42] <dholbach> nxvl_work: you're a hero, thanks for that
[15:42]  * dholbach hugs nxvl_work
[15:43]  * nxvl_work hugs dholbach back
[15:43] <ScottK> nxvl_work: Did you see pitt's motu-school lecture on patching systems that's on the wiki?
[15:45] <dholbach> Jordan turned Martin Pitt's lecture into https://wiki.ubuntu.com/PackagingGuide/PatchSystems :-)
[15:45]  * dholbach hugs laserRock
[15:45] <ScottK> dholbach: Thanks.  Since everything's been moved, I have a hard time finding stuff anymore.
[15:46]  * apachelogger notes that dholbach might be in huging mood ^_^
[15:46] <coNP[uni]> Hey MOTus!
[15:46] <apachelogger> ahoy coNP[uni]
[15:46] <dholbach> ScottK: Martin's lecture should be still in the same place: https://wiki.ubuntu.com/MOTU/School/PatchingSources
[15:46] <dholbach> so no need to despair :)
[15:47] <ScottK> dholbach: OK.  Good then.
[15:47] <dholbach> hey coNP[uni], hey apachelogger!
[15:47] <persia> apachelogger: You happen to be the uploader for the least-recently-updated package on REVU.  Please upload a new revision :)
[15:48] <nxvl_work> ScottK: where on the wiki?
[15:48] <apachelogger> persia: which package would that be?
[15:48] <nxvl_work> ScottK: on the motu-school web?
[15:48] <nxvl_work> s/web/page/
[15:48] <dholbach> nxvl_work: http://wiki.ubuntu.com/MOTU/School
[15:48] <dholbach> most of the logs are tagged with CategoryArchive though
[15:49] <dholbach> and were improved and put into the PackagingGuide namespace
[15:50] <persia> apachelogger: libksquirrel
[15:51] <persia> (err..  second highest on Needs Work.  Sorry)
[15:51] <apachelogger> persia: upstream needs to release a new version first
[15:51] <nxvl_work> dholbach, ScottK: thnx, i will take a look
[15:51] <apachelogger> missing license copies and stuff
[15:51] <persia> apachelogger: Ah.
[15:52]  * apachelogger throws a comment in
[15:52] <apachelogger> oh
[15:52] <persia> apachelogger: Neither of your reviewers caught that :)
[15:52] <apachelogger> actuall he did already
[15:53] <apachelogger> persia: hehe, I'm all bitch about that, as Hobbsee noted - I got some packages rejected because of missing license copies
[15:57] <apachelogger> meh
[15:57] <apachelogger> cpptest is having far too many files :|
[15:57]  * imbrandon really isnt here but persia if you would archive xbiso, i dont have the time to properly pay attn to it right now ( anyone else is welcome to adopt it if you know a up and comming motu hopefull )
[15:58] <persia> imbrandon: Just leave a comment asking someone to adopt it.  There are quite a number of contributors who regularly troll REVU.
[15:58] <imbrandon> k
[15:58]  * persia notes that anyone who does adopt it will likely get an easy review from imbrandon
[15:59] <imbrandon> yup lol
[15:59] <Ubulette> could someone please archive seamonkey on revu ? asac sponsored it.
[16:02] <persia> Ubulette: done
[16:06] <imbrandon> ok note added http://revu.ubuntuwire.com/details.py?package=xbiso
[16:06] <imbrandon> ^^ any MOTU hopfulls here is some low hanging fruit for you ^^
[16:06] <persia> dholbach: Thanks for sending the ubotu note: it had slipped far to deep on my list.
[16:11] <apachelogger> DaveMorris: advocated cpptest
[16:25] <afflux> hi, any revu admin available for nuking/archiving http://revu.ubuntuwire.com/details.py?package=psi ? This upload wasn't intentional.
[16:27] <persia> afflux: I'll archive it (I don't like nuking unless there's a good reason not to host it)
[16:28] <afflux> persia: ah right, thanks
[16:28] <persia> afflux: No problem :)
[16:30] <Ubulette> is an lp bug needed for an upgrade 0ubuntu2 ?
[16:31] <ScottK> Ubulette: If you are looking for sponsorship, yes.  Make a bug and attach the debdiff.
[16:32] <Ubulette> it's not a merge, nobody is working in parallel on that
[16:32] <apachelogger> Mez: is the mumble dev on irc?
[16:33] <Mez> slicer, ping from apachelogger
[16:33] <apachelogger> ah :)
[16:34] <slicer> Huh?
[16:34] <Mez> slicer, <apachelogger> Mez: is the mumble dev on irc?
[16:34] <slicer> apachelogger: Ah. Hi.
[16:34] <apachelogger> slicer: ahoy http://revu.ubuntuwire.com/details.py?package=mumble please at least address persia's 1+2
[16:34] <apachelogger> then I might give an advocate ;-)
[16:35] <slicer> Hold.
[16:35] <slicer> Already done, just haven't uploaded it.
[16:35] <slicer> As I didn't have a 3.7.3 compliant lintian to verify with.
[16:35] <apachelogger> ok
[16:35] <slicer> I still don't, but I can upload it... ;)
[16:36] <apachelogger> slicer: hehe, I'll come back to you if lintian complains ;-)
[16:37] <slicer> BTW, when we release 1.1.2 of Mumble, do we go through revu again or just submit a debdiff-ish patch somewhere?
[16:38] <apachelogger> slicer: through revu again, but then it only needs one advocate AFAIK
[16:38] <apachelogger> Mez: right?
[16:39]  * Mez isnt sure
[16:39] <apachelogger> Mez: about the revu or the one advocate? ;-)
[16:40] <Mez> er... depends on who your sponsor is really
[16:40] <Mez> tehre shouldnt be that many changes to the actual package... just the source
[16:41] <slicer> The will-be diff for the debian/ directory is .. er.. 4 lines or so for 1.1.2
[16:41] <Mez> changelog entry ?
[16:42] <slicer> BTW, dh_makeshlibs complains something fierce about libmumble, but just ignore it. For some reason it expects libraries to resolve their symbols.
[16:44] <DaveMorris> apachelogger: since norsetto advocated it before that small change does it mean it can be uploaded now?
[16:45] <apachelogger> DaveMorris: no, he has to readvocate
[16:46] <mruiz> dholbach, all changes are related to the inclusion of iowait (bug 81599). Then, we have to preserve Ubuntu changes and merge the package ;-)
[16:46] <ubotu> Launchpad bug 81599 in hardware-monitor "hardware-monitor cpu monitoring should not include iowait" [Undecided,Fix released] https://launchpad.net/bugs/81599
[16:49] <shodges_> hey, i'm working on a project in my spare time, and will be looking for the correct way to package it in the near future...
[16:50] <slicer> apachelogger: new mumble on revu.
[16:51] <shodges_> The reason I ask is that it's not a single component, theres the core program "Medes", and numerous bundles of data files for each website - which will need to depend on the core package
[16:52] <shodges_> I'm hoping to build numerous packages, one for each "data bundle" (essentially a collection of images and config files) with names matching the website they launch, like "googlemaps"
[16:53] <shodges_> I was wondering what peoples thoughts were on this?
[16:54] <slicer> Does it all come from a single .tar.gz?
[16:56] <shodges_> no, i plan to separate the project into a core "medes-X.X.X.tar.gz" followed by "webapp1-X.X.X.tar.gz" "webapp2-X.X.X.tar.gz", etc
[16:56] <shodges_> if that makes sense
[16:58] <slicer> I may be wrong, but I think you then need to package each of them completely separately. You can easily make the webapp-blipp depend on medes.
[16:58] <apachelogger> yup
[16:59] <shodges_> thats great, thats exactly what I want to do. Cool, I'll work for that approach
[16:59] <\sh> apachelogger, how was the amarok channel party? :)
[16:59] <apachelogger> \sh: well, exhausting, but fun, but exhausting ;-)
[16:59] <apachelogger> exhausting fun I'd say :P
[16:59] <\sh> apachelogger, are you back at home or still near KA?
[17:00] <apachelogger> nah, went home yesterday afternoon
[17:00] <slicer> apachelogger: Are you looking at Mumble now, btw?
[17:00] <\sh> apachelogger, shame..wednesday is another day at xmas market to kill some glühwein ;)
[17:00] <apachelogger> slicer: yes, but only the old version :P
[17:00] <apachelogger> \sh: lol, I have to write a book report tomorrow ;-)
[17:01] <slicer> apachelogger: Ah, ok. Do you want me to stick around?
[17:01] <apachelogger> slicer: well if it's no problem for you, else I just toss my comments on revu
[17:01] <\sh> apachelogger, I wanted to attend, but my GF had a party with her cameroonian club in cologne...so I was staying in cologne
[17:02] <apachelogger> \sh: next time maybe ;-)
[17:02] <apachelogger> slicer: dh_installexamples and dh_link don't do anything, please remove
[17:02] <slicer> apachelogger: Thing is I have to eat sometime in the next two hours. And if you're looking through it right now, I'll postpone. If you're .. ok, you are. nevermind.
[17:02] <\sh> apachelogger, give me a ring when you are nearby :)
[17:03] <slicer> apachelogger: Done.
[17:03] <apachelogger> \sh: aye :)
[17:05] <apachelogger> slicer: you don't provide an init script, do you?
[17:05] <slicer> apachelogger: Yes, it's in scripts/
[17:06] <slicer> apachelogger: And copied into the debian/ dir so dh_..er..something finds it.
[17:06] <apachelogger> ah, right, there
[17:07] <apachelogger> slicer: does the demon run by default?
[17:09] <slicer> apachelogger: Errr. Huh?
[17:09]  * slicer builds the binary and checks to see what dh_installinit actually does.
[17:10] <apachelogger> slicer: well, from what I see it shouldn't
[17:13] <jpatrick> slicer: you can also view it's manpage
[17:13] <jpatrick> "dh_installinit - install init scripts into package build directories"
[17:13] <slicer> Aye, but it also says it sets up symlinks etc etc.
[17:14] <slicer> So the question is, what exactly does it do? :)
[17:14]  * apachelogger extracts the deb
[17:14] <slicer> apachelogger: Ok, installing the murmur .deb will automatically call the init script.
[17:15] <slicer> apachelogger: Which will start the server.
[17:15] <apachelogger> ok
[17:15] <apachelogger> bad thing
[17:15] <apachelogger> IMHO this shouldn't happen without user interaction
[17:15] <slicer> "aptitude install murmur" is user interaction? ;)
[17:16] <apachelogger> as is aptitude icecast
[17:16] <apachelogger> well
[17:16] <apachelogger> IMHO
[17:16] <slicer> Ok, so..
[17:16] <slicer> Err.
[17:16] <apachelogger> either you should provide a debhelper thingy to ask whether to activate it
[17:16] <slicer> START_DEAMON=no added to the defaults and check it in the init script?
[17:16] <apachelogger> or
[17:17] <apachelogger> yep
[17:17] <apachelogger> well
[17:17] <apachelogger> slicer: what defaults?
[17:17] <slicer> apachelogger: The ones I'm about to add?
[17:17] <apachelogger> ok
[17:17] <apachelogger> should go into /etc/security/
[17:17] <slicer> Huh? Not /etc/defaults ?
[17:18] <apachelogger> öhm
[17:18] <slicer> That's what dh_installinit seems to indicate.
[17:18] <apachelogger> or defaults
[17:18] <apachelogger> slicer: defaults then ;-)
[17:18]  * apachelogger didn't had a look into that for quite some time
[17:19] <slicer> apachelogger: Ok. Here's the thing. Is there a way to determine if the script is called from the command line or if it's called from rc?.d ?
[17:20] <slicer> Most init scripts which do have a defaults file simply exit unless the magic line in /etc/defaults/XX is set, and it's kind of annoying that when you manually /etc/init.d/package start, nothing happens.
[17:20] <apachelogger> true
[17:20] <apachelogger> but there is no way to determine AFAIK
[17:20] <apachelogger> slicer: you might output an error message though
[17:21] <apachelogger> so one at least knows what to do
[17:22] <slicer> Ah, avahi has a good example. Stealing code.
[17:22] <ScottK> slicer: I don't think that's most inits that do that.
[17:23] <ScottK> Spamassassin is by default configured for spamd to do nothing, but that's an unusual case.
[17:23] <ScottK> DKIM-Milter uses /etc/defaults and runs with nothing set in defaults.
[17:23] <ScottK> For more examples.
[17:24] <slicer> Er. I think it was pulseaudio.
[17:25] <slicer> Which annoyed me, as I had to read the init script to find that it needed a defaults file.
[17:25] <slicer> But avahi prints a warning, which is exactly what I want.
[17:26] <slicer> I assume it's quite sane to check that value only in 'start'? Otherwise, you can get scenarios where the user first starts the service, then edits defaults, then has no way of stopping it.
[17:26] <ScottK> If there is a reasonable default configuration, it's much better to set it up that way by default.
[17:26] <apachelogger> slicer: true
[17:29] <shodges_> Oh, another quick question. I was reading up about the PPA, it sounds really useful but there were a couple of things that weren't clear to me:
[17:29] <shodges_> How many packages can you publish on it at any one time? I think its just 1, but not sure if I understood it correctly
[17:30] <RainCT> shodges_: you've up to 1GB space
[17:30] <DaveMorris> shodges_: the limit is set via space
[17:30] <shodges_> ah ok cool
[17:30] <DaveMorris> although I've got over 1GB
[17:30] <shodges_> also, does it build packages for other architectures automatically? like i386/amd64/ppc? I havent tried using it yet, but thought i'd take a stab later tonight
[17:30] <RainCT> DaveMorris: heh. well.. if they don't add a delete option they can't complain :P
[17:31] <DaveMorris> Estimated archive size:              2.8 GiB
[17:31] <Daviey> DaveMorris is a rogue user
[17:31]  * RainCT is looking for a packaging bug
[17:35] <shodges_> damn, some people have like 500 binaries in their ppa!
[17:42] <shodges_> thanks for your help everyone, I think I have what I need to get started now
[17:45] <slicer> apachelogger: Was there anything else, btw?
[17:46] <apachelogger> slicer: didn't notice anything else, I'll have another look with the defaults stuff
[17:46] <apachelogger> norsetto: hey, please have a look at cpptest
[17:47] <norsetto> apachelogger: I advocated it already, was there a change that needs to be looked at?
[17:48] <apachelogger> norsetto: yes http://revu.ubuntuwire.com/details.py?package=cpptest
[17:50] <norsetto> apachelogger: did you build it already? If so and you have a .changes please upload it
[17:51]  * apachelogger checks the directory
[17:51] <apachelogger> yeah, built already ;-)
[17:52] <norsetto> apachelogger: let me know when you have uploaded and I'll mark it as done and archive.
[17:53] <RainCT> is current standards version in Ubuntu 3.7.2 or 3.7.3?
[17:54] <jpatrick> RainCT: .3
[17:54] <RainCT> ok, thanks :)
[17:59] <apachelogger> persia: http://revu.ubuntuwire.com/details.py?package=libksquirrel about 3): I doubt that thoose scripts/bins have very much use for anyone directly (also considering only one provides a --help anyway), so IMO it doesn't make much sense to include 16 manpages with mostly not existing content
[18:01] <apachelogger> norsetto: it's in new
[18:01] <slicer> apachelogger: It's on revu now.
[18:01]  * apachelogger is going to set the bug to fix commited
[18:02] <norsetto> apachelogger: danke
[18:02] <slicer> I'll go get something to eat, back in 30 minutes or so.
[18:02] <apachelogger> norsetto: hehe, yw ;-)
[18:03] <apachelogger> DaveMorris: thanks for your work :)
[18:04] <RainCT> Can someone please tell me a translation into German for "Application for partitioning a disk" (starting with a verb preferably, for a menu entry)? (I'd probably make at least 1 writting mistake :P)
[18:04] <DaveMorris> np, now to get my other 2 accpeted
[18:04] <norsetto> RainCT: whats a writting mistake ?
[18:05] <RainCT> norsetto: that lol
[18:05] <Nightrose> RainCT: "Programm zum Partitionieren einer Festplatte" - can´t think of one starting with a verb
[18:05] <Nightrose> would sound strange
[18:06] <apachelogger> well
[18:06] <apachelogger> the english version doesn't start with a verb
[18:06] <apachelogger> how could the german? :P
[18:07] <Nightrose> well different language means different structure of sentences sometimes
[18:07] <Nightrose> but not always ;-)
[18:07] <apachelogger> Nightrose: smart ass :P
[18:08] <RainCT> well.. the Catalan translations I added starts with a verb :)
[18:08] <Nightrose> *lol*
[18:11] <DaveMorris> apachelogger: who handles backports of new packages we upload?
[18:11] <apachelogger> DaveMorris: the ubuntu-backports team
[18:11] <DaveMorris> do they auto do it or do I need to ask them?
[18:12] <apachelogger> ask, via bug report
[18:12] <DaveMorris> thanks
[18:12] <apachelogger> attach the changelog and a build log, ensure it build/installs/works properly
[18:12] <apachelogger> ScottK knows all the magic ;-)
[18:13] <ScottK> DaveMorris: Feel free to ping me with the bug number when it's done.
[18:34] <RainCT> uhm.. if a menu entry needs root privilegies, how can I achieve this so that it works for both GNOME and KDE?
[18:35] <ScottK> RainCT: Look at disk-manager on REVU.  They have a disk-manager-root script that works through that.
[18:35] <ScottK> I don't know a simpler way.
[18:37] <RainCT> ScottK: will look at it, thanks
[18:39] <ScottK> RainCT: I think that it could, perhaps, be abstracted into a useful general solution for the problem.
[18:40] <ScottK> RainCT: When you look at it, be sure to look at the Kubuntu integration patch in debian/patches.
[18:42]  * RainCT doesn't like the idea to add a python dependency
[18:43] <jonnymind> Good evening to all.
[18:43] <apachelogger> RainCT: just add another desktop file
[18:43] <RainCT> hm.. it should work if done in bash, or?
[18:43] <apachelogger> one only shown in KDE
[18:43] <apachelogger> using kdesudo
[18:43] <apachelogger> and another shown elsewhere using gksu
[18:44] <RainCT> s/it should/should it/
[18:45]  * RainCT blames Qt for now showing in which source file each translation is.. :(
[18:46] <RainCT> new question, any good tool for searching in many different files?
[18:47] <geser> rgrep aka grep -r doesn't work?
[18:48] <RainCT> geser: great, thanks!
[19:01] <RainCT> ScottK: eh.. why is that kde integration patch requried? I have kdesu but not kdesudo with kde-base installed
[19:05] <slicer> apachelogger: I'm back, but I got called back to work. Could you just post your comments on revu?
[19:05] <ScottK> RainCT: Are you on Feisty or Gutsy?
[19:06] <apachelogger> slicer: sure
[19:06] <slicer> apachelogger: Thanks.
[19:07] <ScottK> RainCT: The XAUTHORITY bit is the most important part.
[19:08] <RainCT> ScottK: Gutsy
[19:09] <ScottK> RainCT: I'll have to look into that then.  I thought we switched to kdesudo (I have both).
[19:14] <RainCT> I'll go with this  http://paste.ubuntu-nl.org/47714/   (the last line is just a test, of course)
[19:14] <RainCT> perhaps not very nice, but well.. it works :)
[19:19] <ScottK> RainCT: Now what about Xubuntu and Fluxbuntu?
[19:20] <ScottK> ;-)
[19:20] <RainCT> what do those use?
[19:26] <ScottK> RainCT: No idea.  I know imbrandon knows about Fluxbox.
[19:27] <RainCT> imbrandon: ping? :)
[19:28] <ScottK> RainCT: I think sommerville32 knows about Xubuntu.
[19:33]  * RainCT is asking in #xubuntu..
[19:38] <RainCT> ScottK: Xubuntu uses gksudo
[19:39] <ScottK> OK.
[19:41] <geser> Hi bddebian
[19:46] <macd> I see flash 9r115 in the repos but gutsy still wants to install r48, (which also has the md5 bug) but manually installing http://archive.ubuntu.com/ubuntu/pool/multiverse/f/flashplugin-nonfree/flashplugin-nonfree_9.0.115.0ubuntu2_i386.deb works fine
[19:46] <bddebian> Heya gang
[19:46] <bddebian> Hi geser
[19:48] <pochu> hey bddebian
[19:49] <bddebian> Hi pochu
[19:49] <pochu> macd: there's a backport request I think
[19:49] <macd> r115 is for hardy, r48 causes some sites music to not play, would it be approriate todo a gutsy backport?
[19:49] <macd> pochu, you must have been typnig at the same time ;P
[19:49] <macd> I've been looking on LP for a bug that has a backport request, but can't seem to find it
[19:50] <ScottK> macd: Are you looking in the gutsy-backports project?
[19:50] <macd> ScottK, most likely not, could you point me there
[19:51] <ScottK> https://bugs.launchpad.net/gutsy-backports
[19:51] <ScottK> macd:  ^^^
[19:51] <macd> tyvm
[19:52] <macd> no results for flashplugin, I'll just file one
[19:58] <macd> is there a particular team/person should be assigned? desktop-bugs or?
[19:59] <ScottK> macd: No.  Just file the bug.  If you can test the hardy package on gutsy, then mark it confirmed.
[20:01]  * macd already did that ;P
[20:01] <macd> installs/removes/purges fine
[20:02] <macd> Is there anything like a normal bug i.e. debdiff or anything that it needs?
[20:02] <ScottK> No.  The archive-admins have a magic script.
[20:02] <ScottK> macd: Does it run?  That's the other key point to test.
[20:03] <macd> yes, it runs and fixes the issue in the gutsy version
[20:03] <ScottK> macd: Say all that in the bug and I'll approve it to go to the archive admins.
[20:03] <macd> just reading through some of adobes changes, I can't see how noone reported a bug earlier
[20:04] <ScottK> macd: They probably just whined on forums that no developer reads rather trying to help solve the problem.
[20:04] <macd> ScottK, yeah typical users ;P, the bug report already has that it fixes the issue, and that it works on gutsy :)
[20:05] <ScottK> macd: What bug #?
[20:05] <macd> bug 175370
[20:05] <ubotu> Launchpad bug 175370 in gutsy-backports "Please backport flashplugin-nonfree from Hardy to Gutsy (i386)" [Undecided,Confirmed] https://launchpad.net/bugs/175370
[20:05]  * ScottK looks
[20:06]  * ScottK approves
[20:07] <ScottK> macd: Now it's just when the archive admins have time to look at it.
[20:09] <macd> ty :)
[20:09] <torkel> hm, shouldn't flashplugin-nonfree have been built for amd64 by now too?
[20:10] <macd> looks like the hardy one has problems with konq/nspluginwrapper
[20:12] <ScottK> torkel: AMD64 seems to be lagging significantly right now.  Not sure why.
[20:20] <RainCT> how can I let a package remove some files when it gets purged?
[20:21] <ScottK> RainCT: Look at the postrm in most any package with a conffile.
[20:23] <RainCT> ScottK: ok, thanks. can you think of any small package with a conffile? :P
[20:23] <pochu> pbuilder
[20:24] <pochu> err, did you say small? :-)
[20:24] <RainCT> heh
[20:24] <pochu> Installed-Size: 984
[20:24] <pochu> In fact it's easy :)
[20:25] <pochu> I think that's KB though
[20:28] <RainCT> uhm.. I can't find any special there..
[20:28] <RainCT> except a "pbuilder-uml.files" file :P. what's a files file? xD
[20:31] <RainCT> ah, I see. «it is used while building packages to record which files are being generated. [...] It should not exist in a shipped source package». is this a bug in pbuilder's package ? :P
[20:35] <RainCT> ScottK: it seems that conffiles are removed automatically when purging..
[20:36] <ScottK> RainCT: Look at dkim-milter's source package.
[20:36] <RainCT> but I need to remove log files :(
[20:36] <ScottK> It give you the basic script for checking if your are purging.
[20:38] <RainCT> thanks ScottK
[20:38] <ScottK> RainCT: No problem.
[20:45] <warp10> Hi all!
[21:02] <norsetto> hey warp10, welcome back
[21:03] <warp10> Hi norsetto, thanks! It has been a long (lost) fight against a bad adsl usb modem :(
[21:41] <RAOF> Ubulette: Still here?  I just heard that you were working on xulrunnering miro, and I'm merging it now.
[21:41] <RAOF> (For some sufficiently generalised concept of "now")
[21:43] <maiatoday> norsetto?
[21:43] <norsetto> maiatoday: yes m'am?
[21:44] <maiatoday> will you look at my debdiff pastebin for bug 133935, please
[21:44] <ubotu> Launchpad bug 133935 in libimage-exiftool-perl "missing xmp2iptc.args and iptc2xmp.args" [Wishlist,Confirmed] https://launchpad.net/bugs/133935
[21:45] <norsetto> maiatoday: sure, just few sec. and I'll check it out
[21:46] <maiatoday> ty, http://pastebin.com/d400ed2ae
[21:49] <norsetto> maiatoday: can you remember me the bug number?
[21:50] <maiatoday> 133935
[21:50] <norsetto> bug 133935
[21:50] <ubotu> Launchpad bug 133935 in libimage-exiftool-perl "missing xmp2iptc.args and iptc2xmp.args" [Wishlist,Confirmed] https://launchpad.net/bugs/133935
[21:51] <norsetto> maiatoday: this is a single binary package?
[21:52] <Flare183> bug 110377
[21:52] <ubotu> Launchpad bug 110377 in p7zip "sfx module not found" [Undecided,Confirmed] https://launchpad.net/bugs/110377
[21:52] <maiatoday> norsetto, uhm not sure?
[21:53] <maiatoday> ls
[21:54] <norsetto> maiatoday: you can use apt-cache to check it (there are also many other ways)
[21:54] <maiatoday> oops
[21:54] <norsetto> maiatoday: for instance "apt-cache showsrc libimage-exiftool-perl" tells me there is only one binary
[21:55] <maiatoday> norsetto, ok I see
[21:55] <norsetto> maiatoday: that makes a difference if you have to make sure that the examples are installed in a certain binary package only
[21:55] <norsetto> maiatoday: these two files, are they in the root of the source tree?
[21:56] <maiatoday> norsetto, yes
[21:56] <norsetto> maiatoday: ok, just two little things
[21:56] <norsetto> maiatoday: 1) we fix this for the development release
[21:57] <norsetto> maiatoday: which means ....?
[21:57] <maiatoday> oops s/gutsy/hardy
[21:57] <norsetto> maiatoday: ok
[21:58] <norsetto> maiatoday: 2) You need to list all changes in the changelog
[21:58] <maiatoday> ok so that includes the maintener field change too like you said last time?
[21:58] <norsetto> maiatoday: yes
[21:59] <maiatoday> norsetto: okeydokey brb
[21:59] <norsetto> maiatoday: I don't see it in the pastebin, but how wide is it your changelog ?
[22:00] <norsetto> maiatoday: never mind, it fits in the 80 columns limit
[22:01] <maiatoday> norsetto: I didn't make mine wider than what was there before, but I'll try to remember 80 col
[22:02] <norsetto> maiatoday: I'm really nittypicking here, but instead of " * add rules to put xmp2iptc.args and iptc2xmp.args in /usr/share/doc/libimage-exiftool-perl on installation. (Closes: #133935)
[22:02] <norsetto> maiatoday: I would just say "* add installation of example files (xmp2iptc.args and iptc2xmp.args) (LP: #133935)
[22:03] <norsetto> maiatoday: note that the correct syntax is LP: #xxxxx
[22:04] <maiatoday> norsetto: how would you phrase the maintainer field change?
[22:04] <norsetto> maiatoday: there is a standard text that update-maintainer use
[22:05] <norsetto> maiatoday: Modify Maintainer value to match the DebianMaintainerField specification
[22:05] <maiatoday> norsetto: ok I'll go look for it
[22:06] <norsetto> maiatoday: a last one, the way you did it is allright, but you could also do it differently
[22:06] <maiatoday> norsetto: with the examples file instead?
[22:06] <norsetto> maiatoday: yes
[22:06] <norsetto> maiatoday: its pretty much a question of personal taste
[22:06] <maiatoday> norsetto: I thought since it was just two files rules would be ok
[22:07] <norsetto> maiatoday: for me it is, but some people don't like to fiddle with rules too much
[22:07] <norsetto> maiatoday: just leave it as is, but be prepared to defend your choice :-)
[22:07] <ScottK> maiatoday: I usually use, "*  Changed maintainer to MOTU"
[22:08] <StevenHarperUK> Can anyone here remove a PPA upload?
[22:08] <DaveMorris> StevenHarperUK: goto #launchpad
[22:08] <norsetto> StevenHarperUK: don't think so, try #launchpad
[22:08] <StevenHarperUK> ta
[22:10] <norsetto> maiatoday: before uploading the debdiff and subscribing u-u-s, just check that it builds and installs correctly (you can also check it with dpkg -c)
[22:11] <maiatoday> norsetto: ok, I will recheck build and install, thanks for meticulous crit :)
[22:13] <norsetto> maiatoday: no, thx to you for *your* work :-)
[22:21] <bigon> keescook: hi, shouldn't be a good idea to take a new svn snapshot for gtimelog?
[22:21] <keescook> bigon: probably, but I haven't checked on the upstream svn repo.
[22:26] <norsetto> scottk: do you remember why we never uploaded wine-0.9.46+ ?
[22:26] <ScottK> norsetto: IIRC we released Gutsy with the latest there was at the time.
[22:27] <ScottK> norsetto: I've asked Scott Ritchie to prepare newer packages for Hardy, but haven't seen any.
[22:27] <norsetto> ScottK: ah ok, I thought 0.9.46 was much older than that
[22:27] <ScottK> norsetto: No, but I'd love to get some newer stuff in Hardy and then backport it.
[22:28] <norsetto> ScottK: well, I just used his package on revu to make 0.9.50 for personal use
[22:28] <norsetto> ScottK: not that it makes any difference on my machine ....
[22:28] <ScottK> norsetto: I didn't know he had a package on revu
[22:29] <ScottK> \sh_away: What do you think of the WINE 0.9.50 package on REVU?
[22:29] <ScottK> norsetto: If \sh_away likes it, I'll look at it for sponsoring.
[22:30] <norsetto> ScottK: its 0.9.49 on revu
[22:30] <ScottK> Ah.
[22:30] <ScottK> \sh_away: .49 then
[22:30] <ScottK> norsetto: OK.  Maybe you should look at uploading the package you made then.
[22:31] <RainCT> good night
[22:31] <norsetto> ScottK: I just dropped in the new tarball (its out since few days only), didn't check if there was a need to do something else
[22:31] <ScottK> norsetto: OK.  Well let's see what \sh_away has to say.  You need to talk him into re-applying for MOTU.
[22:37] <norsetto> こんばんは proppy-san
[22:39]  * persia notes for general consumption that it's not important for a description to start with a verb, so long as it is a verbal phrase, and that people should examine app-install before installing two .desktop files for a single binary, as it may have unintended effects.
[22:40] <proppy> norsetto: oyyyy
[22:40] <norsetto> Oh man, don't you love altavista, try this: good evening -> (Japanese) こんばんは -> (English) It is dense, it is, it is
[22:40] <Ubulette> 今晩はみんな  (I didn't know this channel was utf8 compliant. すごいよ)
[22:41] <proppy> norsetto: my kana input is off, can't remember the crazy command to put it back :)
[22:41] <persia> ここに
[22:42] <persia> Err..  Please use English in this channel (and why doesn't kanji completion work today)
[22:42] <norsetto> ubulette: you are telling this to somebody in particular?
[22:43] <Ubulette> no, to everyone, but just for fun. do you read japanese ?
[22:44] <norsetto> ubulette: well, had fun at looking at the automatic translation :-)
[22:45] <proppy> Ubulette: so sad I can't read kanji yet
[22:45] <Ubulette> i barely have an occasion to practice my japanese.
[22:45] <Ubulette> same for chinese btw
[22:45] <Ubulette> even worse
[22:45] <persia> proppy: Learn three characters a day, every day.  In a year, you'll know more than the average Japanese person.
[22:46] <proppy> persia: we finished the kanatana training today
[22:46] <Ubulette> I knew the famous 1845 a couple of years back but I forgetting fast :(
[22:46] <Ubulette> 'm
[22:46] <proppy> persia: I will play 'kanatest' everyday to the final test next week :)
[22:47] <persia> proppy: That's the spirit
[22:47] <proppy> persia: have you try apt-get install kanatest ?
[22:47] <proppy> persia: it's great really
[22:48] <Ubulette> kana could be learned in less than 3 hours providing motivation (read + write)
[22:48] <Ubulette> kanji could take forever
[22:48] <persia> proppy: Yep.
[22:49] <proppy> Ubulette: If you know a good method let me know
[22:50] <proppy> Ubulette: I'm stalling filling page and page of the same kana for learning them one by one
[22:50] <Ubulette> proppy, you're french right ?
[22:50] <proppy> Ubulette: learning them in sequence was good at the beginning but it's hard then to random access them
[22:50] <proppy> Ubulette: yep
[22:51] <Ubulette> proppy, Yves Maniette wrote a small book for kana in 3 hours.
[22:51] <proppy> http://maniette.fr/ ?
[22:51] <proppy> cool
[22:51] <proppy> thanks for the hint
[22:52] <Ubulette> his kanji book is good too but just to write and recognize, not read
[22:52] <Ubulette> "les kanji dans la tete"
[22:53] <proppy> Ubulette: what is the title of the kana book ?
[22:54] <Ubulette> i don't know if it's released. I had a preview from Yves to beta test. Let me check
[22:55] <proppy> woo beta pdf :)
[22:55] <proppy> hope there is an bzr branch available :)
[22:58] <proppy> Ubulette: http://www.nanzan-u.ac.jp/SHUBUNKEN/publications/miscPublications/Remembering_the_Kana.htm
[22:58] <proppy> Remembering the Kanji I: A Complete Course on How Not to Forget the Meaning and Writing of Japanese  Characters
[22:58] <proppy> rench adaptation:Yves Maniette
[22:59] <proppy> I see, there are french adaptation of foreign book
[22:59] <Ubulette> there are tons of books for kana. I don't think it's that useful. kanji on the opposite, yes
[23:01] <proppy> Ubulette: it's always worth to have something to read on something you learn :)
[23:01] <proppy> I mean for me it's worthy
[23:02] <norsetto> proppy: zen and the art of debian packaging?
[23:03] <SWAT> I want to add a mysqldump command to a package rules (to backup the old database upon installation), but this requires the mysql (root) password. What's the nicest way to handle this? Just let the user fill in the password?
[23:04] <proppy> norsetto: zen and the art of packaging windows software ? :)
[23:04] <norsetto> proppy: what does it mean actually? zen I mean ....
[23:06] <proppy> norsetto: I use to read a graphics programming book from M Abrash  who talk about zen timer programming :)
[23:07] <norsetto> proppy: oh my, the ineluctable fps
[23:11] <persia> norsetto: x52pro advocated on REVU (The test won't link).  Tested great, with a couple wishlist notes.  Feel free to fix them or not :)
[23:12] <norsetto> persia: only a couple!?
[23:12] <persia> norsetto: As usual, your packaging doesn't cause me to complain :)  It's just that the examples don't work by default :(
[23:13] <norsetto> persia: strange, it works for me, what is the problem?
[23:13] <persia> norsetto: "" vs. <> for one, and the need to manually track down the /usr/lib/foo.so links for the other.
[23:14] <persia> norsetto: With a small edit, and the right command line, it worked for me.
[23:14] <persia> (but it's just an example, so not likely critical)
[23:14] <norsetto> persia: I see, I wonder why it didn complain with me though
[23:15] <persia> norsetto: Interesting question.  I got lots of "undefined symbol" errors from ld.
[23:15] <norsetto> persia: no no, its good to know, this needs fixing
[23:15] <persia> norsetto: Fixing is good :)  I'm not sure that a packaged client would encounter the issues though.
[23:15] <proppy> Ubulette: I downloaded the english version
[23:20] <persia> norsetto: I just noticed: the -dev might want to depend on libusb-dev as well.
[23:22] <norsetto> persia: ah ah, that could be the problem
[23:22]  * Flare183 is away: Gone away for now.
[23:23] <persia> norsetto: It's not the entire problem: gcc -o x52test x52test.c still didn't work with that installed.  There's likely something about hints odd as well (but I don't understand what)
[23:23] <norsetto> persia: I had forgotten I installed that when I first tried out the compilation from source
[23:23] <norsetto> persia: well, you need to add -lx52pro of course
[23:23] <proppy> norsetto: persia: Ubulette: have a good night
[23:24] <norsetto> proppe: bonne nuit bon proppy
[23:24] <proppy> I have to attend to leweb3 tomorrow, I should go to sleep
[23:24] <persia> norsetto: Right.  I'm an idiot :)  Never mind then: just the dependency should do it.
[23:24] <Ubulette> proppy, oyasuminasai
[23:25] <persia> Err, and s/""/<>/
[23:25] <norsetto> persia: thanks for that, I had totally forgotten it
[23:25] <persia> norsetto: No problem.  Thanks for backporting it to work with my kit :)
[23:25] <norsetto> persia: well, now I can switch off the bloody leds when I startup linux :-)
[23:26] <persia> norsetto: you don't like basking in the full dawn glow of your joystick?
[23:26] <proppy> Ubulette: hay jane bye bye
[23:27] <Ubulette> proppy, dream in kanji :)
[23:27] <norsetto> persia: hehe, got all lights dimmed but the one in the corridor outside (my wife thinks I'm lonewolfing already)
[23:35] <cdm10> So, I've learned how to make a package using dh_make to generate the debian filestructure, python distutils to create the installer, and dpkg-buildpackage to build the package.
[23:36] <cdm10> However, if I make some changes and want to create another version without going through the process of changing the rules file and all that, what do I change to change the version name so I can just change it and dpkg-buildpackage it again?
[23:38] <persia> cdm10: Every time you run dpkg-buildpackage -S it will generate a new source, including any changes you've made.  If you've released it, and need to force a revision update, add a changelog entry with dch -i (but you likely don't need this).
[23:38] <cdm10> persia: Well, I just want my new package to supercede the old in my PPA, which necessitates bumping the version number.
[23:39] <persia> cdm10: That would be publishing it (in the PPA).  Just add a changelog entry, describing the changes, and with a new version number.
[23:39] <persia> s/version number/revision number/
[23:40] <cdm10> persia: alright. What if I make a new version of the program and want to bump the version, say, from 0.1 to 0.2 rather than the revision number (0.1-1 --> 0.1-2)
[23:41] <persia> cdm10: If you're upstream, that works.  I'd suggest you want 0.1-1 -> 0.2-0private1, so that you could later upgrade to 0.2-0ubuntu1 if you were to put it in the repositories.
[23:43] <cdm10> persia: I'm not really asking about what to do when it comes to bumping version numbers... I just want to know how to do it. Like, what files to change, what commands to run, before I run dpkg-buildpackage.
[23:51] <RAOF> cdm10: In that case, the answer is: debian/changelog.  That's where the package version comes from.  It may complain if it can't find an appropriately versioned .orig.tar.gz, though.
[23:51] <cdm10> ok
[23:51] <RAOF> cdm10: Bumping the upstream version is the same as bumping the revision.
[23:52] <bigon> keescook: I've made a new snapshot for gtimelog, I will try to push it in debian
[23:52] <cdm10> RAOF: can you explain the names of the parts of a package version? a-b-ubuntuc
[23:52] <cdm10> or ppac or cdmc or whatever
[23:53] <keescook> bigon: cool :)
[23:54] <RAOF> cdm10: $UPSTREAM_VERSION-$DEBIAN_REVISION[ubuntu$UBUNTU_REVISION] is the general format.
[23:55] <cdm10> RAOF: alright. So, if I'm releasing packages in my own PPA, what should my versions be?
[23:55] <norsetto> cdm10: you may want to add a ~ppaXY to that
[23:56] <persia> Or even $UPSTREAM_VERSION-$DEBIAN_REVISION[$VENDOR$VENDOR_REVISION] to generalize.
[23:56] <cdm10> so, if I'm writing an app that I'm packaging myself for my own ppa, I do: $upstream
[23:56] <cdm10> damn
[23:56] <cdm10> enter key got in the way
[23:57] <cdm10> $appversion-ppa$package-revision
[23:57] <RAOF> And for packages not in the official archives you generally want to have a ~ somewhere in your version string, so that you don't block an official version.
[23:57] <cdm10> so if i change something about the packaging but not the app, i change the $package-revision?
[23:57] <RAOF> Yes.
[23:58] <RAOF> I'd suggest $appversion-0~ppa$package-revision, though, since it's got a debian/ubuntu revision of 0.
[23:59]  * persia notes that $appversion-0ppaX sorts lower than both -0ubuntu1 and -1 and doesn't require the use of the confusing ~
[23:59] <RAOF> True.  Although I'm not sure how confusing `~` really is.