[05:44] <dholbach> gooooood morning
[05:47] <superm1> Laney, i didn't keep up this weekend, did you sort out that mplayer problem?
[05:48] <superm1> good mornin dholbach
[05:50] <nxvl> dholbach: already here? good morning!
[05:50] <dholbach> hiya superm1, hi nxvl!
[06:01] <StevenK> -rw-r--r-- 1 steven users 2.5M 2008-05-03 14:22 multisync_0.82-8.1.diff.gz
[06:01] <StevenK> -rw-r--r-- 1 steven users 1.9M 2004-07-27 09:47 multisync_0.82.orig.tar.gz
[06:01]  * StevenK sobs
[06:02] <superm1> that reminds me of what i seem to remember being a 13M diff.gz on VLC a few releases back
[06:03] <persia> Off all the diffs I've prepared, the largest are typically those of which I'm proudest (although I do wish those weren't for dead upstreams so they could be integrated)
[06:04] <wgrant> vlc never had a particularly large diff.gz. But it had a lot of diff in the tarball.
[06:15] <tuxmaniac> good morning folks
[06:20] <superm1> Laney, well i'm going to be afk for a bit, so if you can add an update to bug 262832 or unassign it from yourself if you're not going to be taking care of it, that'd be great.
[07:24] <tuxmaniac> hello everybody. http://daniel.holba.ch/harvest/handler.py?pkg=gnumeric <-- four bugs have been resolved upstream but the fixes are in the GNOME VCS. Is it worthwhile/recommended to apply those patches to the current intrepid version though it is not released?
[07:25] <tuxmaniac> also would it require any exception? I hope not as it does not add any feature but fixes 4 bugs
[07:27] <dholbach> tuxmaniac: you could try to get in touch with upstream and ask when their next release is due - you could then ask for a FFe for that, if it takes too long for them to release a new version, you could try to patch the current gnumeric package
[07:27] <dholbach> tuxmaniac: best to ask in #ubuntu-desktop as well
[07:27] <ScottK> Would we get it naturally through a release we would normally expect to get before release?
[07:27] <dholbach> maybe there are update plans already
[07:27] <persia> tuxmaniac: Generally no freeze exception is required for bugfix only, although if you introduce a new version, documentation is appreciated.
[07:29] <dholbach> tuxmaniac: we're at 1.8.3 in intrepid and 1.9.2 has been released (this might be an unstable release, so best to chat with the upstream folks and ask)
[07:29] <tuxmaniac> dholbach: ok thanks
[07:29] <dholbach> anytime
[07:43] <didrocks> morning o/
[07:56] <wgrant> What is Playdeb and why is it on Planet?
[07:56] <wgrant> It sounds awfully like Getdeb.
[08:00] <persia> wgrant: It is part of getdeb.
[08:00] <persia> As for why it's on planet, the bzr history will tell you who added the feed.
[08:03] <\sh> getdeb was mentioned the last time on linux-community.de and I had to explicitly add a comment that this repo is third party, and no bugs should be filed against ubuntu for those packages...sounds like "remember, remember the 5th of november. the gunpowder, treason, and plot. I know of no reason why the gunpowder treason should ever be forgot"
[08:05] <wgrant> persia: He added it himself, it seems.
[08:05] <wgrant> Odd that we have such Members.
[08:08] <tuxmaniac> hello motus. I have re-uploaded gresistor after fixing lincese issues. If a MOTU can review and comment on http://revu.ubuntuwire.com/details.py?package=gresistor (may be advocate if found OK) I will go ahead with rising an exception. hopefully it gets approved since it is a small package and definitely not going to break things.
[08:09] <wgrant> The freeze isn't there to be ignored.
[08:10] <tuxmaniac> wgrant: i didnt get the point.
[08:10] <wgrant> The point of a freeze isn't really to just say that this new package probably won't break anything. It's not something we really want, so I don't think it should receive a freeze exception. But I'm not on motu-release.
[08:11] <Laney> superm1: Do you think disabling ivtv is a viable option?
[08:11] <tuxmaniac> wgrant: ok. so I wait for the next cycle.
[08:15] <persia> \sh: Fawlkes!
[08:16] <persia> wgrant: You might have a chat with such a party, if you like.  I know most of the games listed there are also in the repos, and most of the exceptions either have licensing issues or are in SVN waiting for squeeze to open to be uploaded.
[08:17] <wgrant> I've little time for much Ubuntu activity until mid-November, unfortunately.
[08:18] <wgrant> And initiating discuss with a person in that category is guaranteed to absorb time.
[08:22] <persia> wgrant: Understood.  Perhaps someone else will do it.  I know that the first response to that post was by a member of the Debian Games team, wondering why playdeb was separate.
[08:32] <Laney> superm1: Debdiff on bug #262832 if you're interested
[08:36] <Laney> Hey, if anyone cares, the u-u-c logo on LP has a nontransparent background
[08:40] <persia> Laney: Perhaps you've a version with a transparent background?
[09:11] <huats> moring everyone
[09:15] <laga> i just need another ACK for http://revu.ubuntuwire.com/details.py?package=mythtv-theme-metallurgy-wide - so if someone has a few minutes to spare i'd appreciate it if they could look at it
[10:17] <Iulian> Good morning
[10:17]  * Iulian yawns!
[10:18] <dholbach> Iulian: great session yesterday!
[10:19] <Iulian> dholbach: Uhmm, yeah, thanks :)
[10:20] <dholbach> well done - we have a lot of excited new folks in there :)
[10:20] <Iulian> Yup, I noticed. I wanted to answer some more questions but I didn't have the chance. ;)
[10:21] <AnAnt_> Hello, can someone have a look at this bug #254368 , I filed the bug about one month ago , yet no one responded to it
[12:07] <directhex> i wonder why command-not-found is a forkbomb on the machine
[12:50] <nxvl> good morning
[12:54] <huats> hey nxvl
[13:07] <Koon> hello nxvl
[13:09] <Koon> DktrKranz: I have a fix for a nagios2 issue that can be SRU'd in two ways, could you comment on the SRU-team preferred way so that I push the right debdiff ? see bug 252686
[13:26] <DktrKranz> Koon, ah... I remember it a bit. Some times ago I asked kirkland about regression potential for a lsb SRU. You may want to ask him if he's fine with it, otherwise you can proceed with nagios2 (unless there are more packages affected)
[13:26] <Koon> DktrKranz: thanks !
[13:46] <kirkland> DktrKranz: hey there
[13:47] <kirkland> DktrKranz: I've been basically 'gone' for 2 weeks, you might have to repeat your lsb question, as I don't remember :-/
[13:49] <DktrKranz> kirkland, I imagined ;)   We were discussing about a potential lsb SRU (bug 252686), since you touched lsb lately, your opinion is important here.
[13:49] <Koon> kirkland: look at bug 252686. The bug is in LSB, but it's probably better to workaround it in nagios2, in a SRU setting
[13:50]  * kirkland looks....
[13:50] <Koon> DktrKranz: I have another nagios2 SRU lined up (bug 231004) so I can combine the two
[13:53] <kirkland> Koon: DktrKranz: I support the lsb sru patch
[13:53] <kirkland> I'll add a comment to the bug
[13:54] <DktrKranz> great, thanks!
[13:54] <kirkland> however, I recognize that the nagios2 patch introduces the path with least chance of regression
[13:54] <Koon> kirkland: I couldn't find another bug that would get fixed by a LSB SRU
[13:54] <kirkland> if we get any resistance for the LSB patch, we'll push the nagios2 one instead
[13:54] <kirkland> Koon: hmm, interesting
[13:55] <kirkland> Koon: well, i think the nagios2 patch would be much easier to SRU
[13:55] <Koon> kirkland: and since I already have a SRU for nagios2 for another bug...
[13:55] <kirkland> Koon: LSB is so fundamental, and used by every init script that it will come under heavy, heavy scrutiny
[13:56] <kirkland> Koon: oh, you're SRU'ing something else for nagios2?
[13:56] <kirkland> Koon: definitely roll this into there
[13:56] <Koon> bug 231004, already acked
[13:56] <Koon> ok, will do
[13:58] <kirkland> Koon: okay, given that information, add this one-liner to the patch, and a note in the changelog, referencing the other bug
[13:58] <Koon> kirkland: I'm on it
[13:59] <DktrKranz> Koon, given that, I'm happy with nagios2 double-SRU. When you have your debdiff ready, ping me for sponsorship, if you don't find others
[13:59] <Koon> DktrKranz: ok, thanks
[14:02] <kirkland> Koon: DktrKranz: comment added to https://bugs.launchpad.net/ubuntu/+source/nagios2/+bug/252686
[14:39] <Koon> DktrKranz: combined debdiff ready on bug 252686
[14:41] <DktrKranz> Koon, thanks. I'll do a quick review and then sponsor it. I'll make sure this is fixed in Intrepid before proceeding and update bug accordingly.
[14:43] <Koon> DktrKranz: note that intrepid ships nagios3. The bin/mail issue is fixed there, and killproc has been fixed in LSB during the debian merge.
[14:43] <Koon> DktrKranz: thanks!
[14:44] <DktrKranz> so, Intrepid rocks!
[14:44] <Koon> DktrKranz: always :)
[15:09] <bddebian> Heya gang
[15:09] <up_the_irons> I'm trying to backport a hardy package to dapper, and I"m getting: dpkg-gencontrol: warning: unknown substitution variable ${binary:Version},  I guess my dpkg-dev is too old, can someone remind me what the old version of this variable was called?
[15:10] <persia> bddebian, bddebian, bddebian, bddebian, bddebian, bddebian, bddebian, bddebian, hail!
[15:10] <bddebian> Heh, heya persia
[15:12] <directhex> up_the_irons, usually you replace foo:Bar with foo-bar, IME
[15:12] <up_the_irons> directhex: gotcha
[15:12] <up_the_irons> i'll try that, thanks
[15:12] <directhex> no promises. no warranty is implied. try at your own risk. IANAL. IDDQD.
[15:13] <up_the_irons> :)
[15:17] <directhex> IDKFA.
[15:19] <DktrKranz> Koon, uploaded to -proposed.
[15:20] <Koon> DktrKranz: great ! thx
[15:20] <DktrKranz> I used 2.11-1ubuntu1.3, though
[15:28] <Onkel_Donald_> hi
[15:31] <iulian> Hey
[15:32] <Onkel_Donald_> wie kann ich sehn ob ich jemanden eingeladen hab also geworben`?
[15:32] <iulian> !de | Onkel_Donald_
[15:34] <iulian> Huh, what did he say?
[15:36] <laga> "how can i see if i invited someone, i.e. (recruited|advertised) someone?"
[15:36] <laga> doesn't make sense to me
[15:37] <iulian> Weird.
[17:13] <NCommander> Hola
[17:13] <jpds> Hola NCommander.
[17:14] <NCommander> I'm currently cramped in a tiny room and I'm loosing my mind :-/
[17:14] <NCommander> how goes it for you jpds ?
[17:15] <jpds> NCommander: Great, great.
[17:15] <sebner> NCommander: delirium?
[17:15] <NCommander> No, overcrowded classroom
[17:15] <sebner> ah kk ^^
[17:17] <iulian> Yikes!
[17:18] <iulian> That must be painful.
[17:22] <NCommander> so what are you up to jpds ?
[17:23] <jpds> NCommander: Watching #ubuntu-classroom.
[17:24] <jpds> NCommander: Oh, and check out: http://www.gnu.org/fry/
[18:03] <balachmar> Hi, just followed the tutorial. And have found one item in harvest that I would like to fix. checkgmail. But it is a unmetdeps. How should this be fixed?
[18:06] <persia> balachmar: Generally it's important to find out which dependency is unmet, why it was listed as a dependency, and with what it may be replaced.
[18:11] <balachmar> persia: If you could have a look at the bugreport: https://bugs.launchpad.net/ubuntu/+source/checkgmail/+bug/201555 . Am I right in thinking that this bug should be thought of as resolved because the dependancies should be met in intrepid, apart from one. Which is handled in another bug report?
[18:23] <persia> balachmar: That's quite a mess of related issues, but yes, the bug history makes it look like that bug isn't the place to start detangling it.
[18:23] <persia> That said, if checkgmail really *needs* those libraries, they ought be Depends: rather than Recommends:
[18:24] <persia> Reading more carefully, it appears it just acts strangely with them as Recommends, but actually works.
[18:51] <balachmar> persia: yes I have read that as well, so what would be the way to go? Mark it as closed or something?
[18:51] <persia> balachmar: If you think it's fixed, you could mark it as closed.  Have you tested it in intrepid?
[18:52] <balachmar> will do that in my VM (after the upgrade, I am currently testing the upgrade proces)
[18:52] <persia> Generally I think anything mark Fix Released should have been confirmed as actually closed, rather than theoretically closed.
[18:52] <persia> The exception being certain classes of bugs against removed packages.
[18:53] <balachmar> persia: Will check it in my VM. Thanks for the help so far. Will be back with more info.
[19:44] <vadi2> Hi, quick question, is this license allowed in universe: http://creativecommons.org/licenses/by/3.0/
[20:14] <Coper> Hi, dholbach was holding a lession in how to fix a bug in a package, and I just wonder how I can make debuild to find my secret key, It says that it can't be found even but I have set the correct email and fullname in my bashrc.
[20:17] <geser> Coper: compare the name and email address from the last changelog entry with your gpg uid (incl. comments)
[20:18] <Yasumoto> Hey guys. I'm trying to work on https://bugs.edge.launchpad.net/ubuntu/+source/matplotlib/+bug/263608 - I added depends python-gtk2 to debian/control, but when I try to run debuild -S, it's telling me that I don't have python-numpy installed (which I do) does anyone happen to have any suggestions?
[20:19] <geser> Yasumoto: have you the exact error message at hand?
[20:19] <Yasumoto> I'll paste it
[20:23] <Yasumoto> geser: http://paste.ubuntu.com/42806/
[20:25] <Coper> geser: When I created my gpg key I was using a comment dose that mean that I always have to use the complete name (comment) email in all changelogs?
[20:26] <geser> Coper: either that or tell debuild which key to use
[20:28] <Coper> geser: okey thanks.
[20:30] <geser> Yasumoto: are you trying to build the package on hardy or intrepid?
[20:30] <Yasumoto> intrepid
[20:31] <Coper> When I have build a package with pbuild build <package>, how can I then test the package so it's works correct? is there a way to chroot in to that enviroment?
[20:31] <geser> you can login into a pbuilder with "pbuilder login"
[20:32] <Yasumoto> and the packages are located in /var/cache/pbuilder/result
[20:52] <Yasumoto> geser: I just installed python-numpy-dbg, and it looks like its building
[20:58] <Coper> geser: when I using pbuild login I only come to a empty enviroment but it dosen't look like the package that was build is installed.
[21:00] <geser> Coper: after pbuilder login you get the same empty environment like before a package is build
[21:00] <geser> you need to copy it into the chrooted environment (while you're in it) and can then install it
[21:25] <coppro> wait, boost is still 1.34.1 in Intrepid?
[21:25] <coppro> fail!
[21:36] <Coper> If I want to verify that a bug still exist in latest development branch is it only to create a pbuild enviorment and update it to intrepid and login and try to install the package that is buggy?
[21:54] <stefanlsd> Coper: As far as I understand it, pbuild environment may not replicate the bug properly. It may be better to install Intrepid in a vm (vm-builder could help) and test it there.
[21:55] <stefanlsd> Does anyone know if there is any documentation or would be willing to help me understand symbols?
[22:05] <albert23> stefanlsd: the first part of https://wiki.ubuntu.com/MOTU/School/LibraryPackaging may get you started
[22:09] <devfil> slangasek: ping
[22:13] <Coper> I found a bugreport that wanted a package to be updated to latest from upstream, the report is not linked to any other bugzilla but I found the same issue in debians bugzilla. Should I just link the issue from LP to debian?
[22:14] <Coper> or should we update our package in ubuntu to latest from upstream?
[22:14] <jdong> we need freeze exceptions at this point, right? *checks calendar*
[22:15] <bobbo> jdong: yeah we hit FF
[22:15] <Coper> okey, but the LP issue should be linked to debian anyway?
[22:23] <wgrant> Hmmm.
[22:23] <wgrant> Interesting logic, this.
[22:24] <jpds> Coper: Yes, so we can track it's status there.
[22:24] <wgrant> People are starting their own repositories because we are apparently too slow because we don't have enough manpower, thus removing some possible manpower from us. This is smart.
[22:25] <laga> wgrant: playdeb.net?
[22:25] <wgrant> laga: Correct.
[22:25] <laga> yeah, that seems a bit silly.
[22:26] <laga> i wonder if they don't like the QC imposed by REVU
[22:27] <superm1> what about if we instituted a mandatory number of packages to be revu'd within a given release to keep ~ubuntu-dev rights?  it would keep people up on skills and help out a bit.
[22:28] <liw> speaking of review speed... could I bri... interest anyone in looking at one or both of my two packages? :)
[22:28] <liw> (python-fstab and system-cleaner; the second depends on the first)
[22:28] <wgrant> liw: Why aren't they in sid?
[22:29] <liw> wgrant, because I don't want to upload them there until after lenny's release, Debian has enough to do during the freeze as it is
[22:29] <wgrant> That is a good reason. You may continue.
[22:31] <emgent`nl> hello
[22:31] <torkel> Any chance that openafs could be synced with the debian version? Just new debian revision. Or do I need to do a FFe?
[22:31] <wgrant> torkel: A new Debian revision shouldn't need a FFe, unless it introduces new features.
[22:32] <torkel> no, just minor fixes
[22:33] <torkel> I need to fill bugs against it anyway, because it does not build on 2.6.27, but I think it is better to do it against 1.4.7.dfsg1-5 rather then 1.4.7.dfsg1-3 which is currently in the archives
[22:58] <RainCT> how can I tell dh_pycentral to exclude some files when I'm using CDBS (with distutils)
[22:58] <RainCT> ?
[23:48] <lzantal> where can I get more info on motu-school