[00:00] <Laney> mok0: Cool. bug #306698 awaits your ack then
[00:02] <Laney> I mean bug #306694
[00:02] <Laney> silly requestsync
[00:08] <mok0> Laney: unfortunately, -4 FTBFS,  there is a trivial error that is fixed in the upcoming version
[00:08] <Laney> It didn't ftbfs for me
[00:09] <mok0> Laney: you probably built in on i386
[00:09] <Laney> No, amd64
[00:09] <mok0> Laney: if works using debuild
[00:09] <Laney> I used pbuilder
[00:10] <mok0> Laney: hmm, well it fails using sbuild on anything but i386 -- it worked for me too, initially, but it fails on Debians buildds
[00:10] <Laney> mmm ok
[00:10]  * Laney tries with sbuild
[00:12] <mok0> Laney: I am waiting for -5 to appear, I don't know what the status of it is... bddebian said he uploaded it
[00:12] <Laney> mok0: Ah, it fails there
[00:13] <mok0> Laney: feisty little problem
[00:13] <mok0> Laney: it's a simple fix in rules
[00:16] <StevenK> mok0: For Feisty?
[00:17] <mok0> StevenK: nono, I meant the problem is "feisty" :-)
[00:27] <quentusrex> who builds phpmyadmin for ubuntu???
[00:27] <quentusrex> I'd like to take a look at their debian/* package folder...
[00:27] <mok0> quentusrex: what do you mean "who"
[00:28] <mok0> quentusrex: apt-get source phpmyadmin
[00:28] <quentusrex> where would that put the soruce?
[00:28] <quentusrex> source*
[00:28] <mok0> quentusrex: in a subdir in cwd
[00:29] <quentusrex> thanks
[00:29] <mok0> quentusrex: cd /tmp and try it
[00:29] <quentusrex> unable to find the source package for it..
[00:30] <Hobbsee> got universe sources in your /etc/apt/sources.list?
[00:31] <quentusrex> nope...
[00:31] <quentusrex> just the deb, not the deb-src
[00:32] <mok0> quentusrex: just duplicate that line, change deb to deb-src
[00:32] <mok0> quentusrex: then do apt-get update
[00:32] <quentusrex> ok, thanks for the help so far mok0
[00:33] <quentusrex> I'm trying to build a web gui for an application and I want to package it similiar to how phpmyadmin is packaged.
[00:33] <mok0> quentusrex: np I'm bored anyway :-)
[00:33] <quentusrex> :)
[00:34] <quentusrex> this is awesome. thanks mok0 it's exactly what I needed.
[00:34] <quentusrex> :)
[00:35] <quentusrex> I'm still very new to packaging, but I've got 2 different pieces of software that aren't packaged yet.
[00:35] <mok0> quentusrex: you know the dget command?
[00:35] <quentusrex> dget? nope. I know dput.
[00:35] <mok0> quentusrex: anywhere you can find a URL to a .dsc file, you can get the source package using "dget -ux <url-to-dsc>
[00:36] <quentusrex> aah, cool.
[00:36] <quentusrex> I probably wont' remember that when I need it, but that's good to know.
[00:36] <quentusrex> also, mok0 what are your views on GPL? and on MPL? or BSD?
[00:37] <quentusrex> I'm trying to gather opinions on the different licenses.
[00:37] <mok0> quentusrex: Oh, I'm a GPL fanboy
[00:37] <quentusrex> y?
[00:37] <mok0> quentusrex: it gives you the max protection as an author
[00:37] <mok0> quentusrex: from being ripped off
[01:17] <quentusrex23> What's the difference between GPL 3 and GPL 2?
[01:28] <samd> hi
[01:30] <RAOF> Hello.
[01:30] <RAOF> quentusrex23: Any number of things, most famously anti-DRM language.  Why?
[01:31] <samd> i just made a gui made in python  for an already existing command line application, i would like to publish it, where should i start? sorry if im little bit new to this thing
[01:32] <RAOF> If you don't have any other hosting, making a launchpad project for it and uploading it there is a good start.
[01:32] <RAOF> In fact, even if you _do_ have other hosting, making a launchpad project and uploading it there is a good start :)
[01:33] <samd> alright, i already have a launchpad account, after uploading it, what do you think about posting in some forums, to publish it?
[01:38] <LimCore> hi. I made a trivial patch that allows user to avoid data corruption in situation when he is on low power UPS and he needs to quickly shut down box (without stupid confirmations etc) - just press power button x2 -  https://bugs.launchpad.net/ubuntu/+bug/285141    can it be applied/used?
[01:38] <LimCore> its intended for 8.04
[01:40] <Hobbsee> 8.04.  why?
[01:40] <LimCore> I didnt test it yet on 8.10  But indeed, I will
[01:42] <Hobbsee> well, 9.04 is the development release, so you'd probably need to target it for that
[01:42] <LimCore> mhm I perhaps will also
[01:42] <LimCore> but all users inclding 8.04 etc will benefit. This *actually* lead me to data lost, more then once
[01:50] <Hobbsee> darn data loss.
[01:50] <Hobbsee> Apparently hitting the power button once does shut down the computer.
[01:50] <LimCore> works on 8.10 as well
[01:50] <crimsun> Hobbsee: :-)
[01:50] <LimCore> Hobbsee: it does not
[01:51] <Hobbsee> does here.
[01:51] <Hobbsee> fortunately, firefox does well at restoring sessions
[01:51] <LimCore> on 8.10 if I press power button, then system shutdowns after 60 seconds which is too long
[01:51] <LimCore> and if I am in gnome. in kde afair not at all
[01:52] <Hobbsee> when the power button is pressed:  shutdown
[01:52] <Hobbsee> rather than 'ask me'
[01:52] <Hobbsee> problem solved.
[01:52] <crimsun> yeah, g-p-m setting
[01:52] <LimCore> I want to be asked
[01:52] <LimCore> but I want also emergency way to tall computer that I really need to shut it down NOW
[01:52] <Hobbsee> you want to be asked, and you want to be able to shut it down, no questions asked.
[01:52] <Hobbsee> pull the power plug, then?  ;)
[01:52] <TheMuso> Kinda like the default gpm setting of not suspending or hibernating when closing the laptop lid.
[01:53] <TheMuso> You would expect after a fresh install, when you close the laptop lid, the laptop would suspend...
[01:53] <Hobbsee> TheMuso: you do?
[01:53] <LimCore> TheMuso: I hope that it will NOT, since this is not fully working
[01:53] <TheMuso> Hobbsee: Well thats what hasw happened to me with fresh installs.
[01:53] <TheMuso> LimCore: You have a point.
[01:53] <TheMuso> I have working suspend/resume however.
[01:53] <Hobbsee> TheMuso: i don't remember mine doing that, but maybe i changed it
[01:54] <LimCore> by default it does not suspend on 8.10
[01:54] <TheMuso> This is what I mean.
[01:54] <LimCore> this is a good thing for the above reason - this is highly experimental and unstabl
[01:54] <crimsun> LimCore: that's not a big surprise, really.  2.6.27 is abysmal for suspend+resume on many, many models.
[01:54] <LimCore> I loose sound after hibernation (so do number of users)
[01:54] <LimCore> plus I use encrypted swap.
[01:55] <LimCore> I dont think it would work at all
[01:55]  * Hobbsee muttesr that there's no good solution for everyone.
[01:55] <crimsun> LimCore: and the lost sound after hibernation should be resolved shortly (I've already done the SRU work)
[01:55] <LimCore> but can we finish my topic first as well :)
[01:55] <Hobbsee> like, for those who want people to be able to shut down, even when the machine is locked, and those who want the machine being locked to actually lock it.
[01:55] <TheMuso> crimsun: Uploaded pulse for jaunty with pmutils hook.
[01:55] <TheMuso> And I'm heading offline.
[01:55] <crimsun> TheMuso: danke
[01:56] <LimCore> I want both  1) normally be nicelly asked    2) in EMERGENCY (can not use monitor and/or keyboard) be able to tell PC to shut down NOW.    My patch does it. And no other thing does that
[01:56] <coppro> I could go for such a patch
[01:56] <Hobbsee> how does it tell it's in an emergency, and not just a person randomly pressing buttons?
[01:56] <Hobbsee> or something bumping against the keyboard by accident?
[01:56] <coppro> but usually, aren't you so frozen that you need to do a hard shutdown?
[01:57] <coppro> and actually, if I press the shutdown button, I don't think I get prompted
[01:57] <Hobbsee> this sounds like the case of nokia phones, which say "lets allow emergency calls even when the phone is locked"
[01:57] <LimCore> Hobbsee: no. If the machine is locked, then it only makes sense to allow to still shut it down if one have phisical access to PC power button (my patche does that too).  Why? because, if he has phisical access, then if he is "bad guy" then he can anyway shut it down (hole the power key)   and if he is a normal user then he should be able
[01:57] <coppro> wait, that's my power button... maybe confusing with something else
[01:57] <coppro> stupid laptops
[01:57]  * Hobbsee --> out
[01:58] <LimCore> Hobbsee: pressong twice the POWER button (the one on PC case, not the one on keyboard)  and twice in 10 seconds
[01:58] <Hobbsee> LimCore: how do you propose to eliminate accidental keypresses, or people who don't understand what it does?
[01:58] <Hobbsee> well, in the case of laptops, that's probably not so hard if you have stuff on it
[01:58] <coppro> I don't get prompted...
[01:58] <LimCore> as above?  if someone is pressing PC case power button randomly then he is anyway 3 seconds away from hard-reseting it or hard-poweroff
[01:58] <Hobbsee> or something's bumping against it.
[01:59] <Hobbsee> at least make it a difficult to hit key combo
[01:59] <coppro> Hobbsee: he's talking about the power case button
[01:59] <coppro> normally one does not bump such a thing accidentally
[01:59] <LimCore> Hobbsee: well, twice in 10 seconds.   Plus, consider that if no desktop (manager) is running, then just _1_ key press will do shutdown -h now.  So my patch both makes it easier to shut down when needed (as I want)  AND makes it harder to by accident shut down
[01:59] <coppro> since it is almost always recessed into the case
[01:59] <Hobbsee> coppro: on a laptop?
[02:00] <coppro> Hobbsee: on a laptop, it's usually either recessed or a slide switch, in my experience
[02:00] <LimCore> the POWER button.    not the sleep/power-off/suspend  buttons on some keyboards (inc. some laptops)
[02:00] <LimCore> the one that if you hold for 4 seconds will anyway hard-shutdown always
[02:01] <LimCore> the one connected directly to bios/something
[02:01] <coppro> yeah, but if I press that, I get a soft shutdown, no prompt
[02:02] <LimCore> coppro: if you press the real POWER button, then by default you get prompt (if WM runnig) or shutdown if not.    With my patch, you can to press it x2 (better if no monitor/keyboard)  and you HAVE to press it x2 not x1 (so, more safe if no WM)
[02:02] <coppro> LimCore: not for me
[02:02] <coppro> watch
[02:02] <LimCore> strange. this is not the default behaviour
[02:03] <LimCore> anyone can confirm what is the default?  what happens if you press your POWER button
[02:04] <LimCore>  /whois copp
[02:10] <coppro> I rest my case
[02:10] <LimCore> coppro: try clean install, the default /really/ is as I described.   So, you can not shut down cleanly ubuntu with just power button, and this leads to hard shutdwon == data lost as I explained
[02:11] <coppro> LimCore: could be a KDE thing
[02:11] <coppro> also, missed the data loss thing
[02:11] <coppro> shutting down and all
[02:12] <LimCore> coppro: on clean 8.10, gnome, power button (the pc one) == prompt
[02:12] <LimCore> same on 8.04, kde, except no prompt
[02:13] <LimCore> coppro: you are not banned on #ubuntu right? :P  you can do a quick poll for me.  Or just ask some friends (if such polling is not wellcomed)
[02:13] <LjL> polling on #ubuntu is not very welcome
[02:13]  * jdong points out he will be banned in #ubuntu shortly afterwards.
[02:13] <LimCore> ok, can any of you guys also press the power button to help us quickly confirm?
[02:14] <LjL> jdong: that "he" is ambiguous. i am, as a matter of fact, going to ban you shortly... but how were you to know that?
[02:14] <jdong> haven't we had this nonsensical discussion 3 months ago?
[02:14] <jdong> LjL: one too many innuendos? :)
[02:14] <jtechidna> my computer immediately shuts down when I press my power button. I am confident enough that I will not press it
[02:14] <jdong> I think that is the case in KDE
[02:14] <jtechidna> yeah, KDE here too
[02:14] <jdong> but not in GNOME hwen g-p-m responds correctly.
[02:14] <jdong> I regularly use the power button to trigger the logout menu
[02:15] <jdong> that's GNOME.
[02:15] <LimCore> right
[02:15] <jtechidna> though come to think about it powerdevil might have this feature now in KDE 4.2...
[02:15] <jdong> it has the acpi event hook necessary?
[02:15] <jdong> $older_ubuntu_version had this capability for KDE too
[02:15] <LimCore> ok so my patch then sorts this out, benefits   1) just 1 power button does not shutdown without confirmation (safe)   and  2) x2 press ALWAYS shut down (better)
[02:15] <jdong> I strongly disagree with #2.
[02:16] <jdong> (1) I don't want two power button preses to shut down my machine
[02:16] <jdong> (2) Many times ACPI generates spurious events
[02:16] <jtechidna> actually
[02:16] <jdong> we've already said the last time we had this discussion we do NOT want a magical forced shutdown button sequence.
[02:16] <jtechidna> powerdevil allows you to configure what you do when you press the power button
[02:16] <jtechidna> interesting
[02:16] <LimCore> jdong: you are speaking for entire ubuntu community or for who?
[02:17] <jdong> LimCore: you are speaking for the entire Ubuntu community or for whom?
[02:17] <LimCore> I am presenting objective arguments that are universal, like this one:
[02:17] <jdong> if you don't believe me feel free to open it up on devel-discuss.
[02:17] <LimCore> jdong: so how users can otherwise shut down the PC if monitor and/or keyboard can not be used
[02:17] <jdong> guarantee you that you will NOT get any consensus for a dual-press forced shutdown.
[02:18] <jdong> the potential for a disabled input device is *NOT* an excuse to work in a hidden poweroff sequence to every other input device.
[02:18] <jdong> what the hell is next? A magical thumb drive that reboots when you insert it?
[02:19] <jdong> #ubuntu-motu is not for pushing controversial new ideas as if it were a bugfix. Please use a discussion mailing list for that.
[02:19] <jdong> I believe we've been down this road 3-4 months ago, too.
[02:19] <LimCore> this is not every other input device,  but this is the input device that allows to shutdown PCs sine before 1980's, and that in nowdays ubuntu allows a shutdown too so it seems logical
[02:20] <jdong> *puts channel on ignore*
[02:20] <jdong> this is ridiculous.
[02:21] <effie_jayx> hey all, can anyone tellme in what package I could find the Sys::Mmap perl module?
[02:22] <LimCore> effie_jayx: if you know file name of that lib, you could use apt-file search filename (install apt-file and  apt-file update  first)
[02:23] <effie_jayx> LimCore,  I am trying to create a package for Zoneminder 1.24 and it just complains about it using the Sys::Mmap
[02:23] <effie_jayx> module for perl
[02:24] <effie_jayx> I get no file name
[02:26] <jdong> I don't think we have Sysm::Mmap
[02:29] <effie_jayx> thanks
[02:29] <jdong> we have a lot of other things that think they're Mmap.pm
[02:29] <jdong> you can probably tell at this point my knowledge of Perl is restricted to stupid commandline tricks
[02:30] <effie_jayx> jdong,  well I am merely trying to satisfy a dependency for the package to build :S
[02:30] <effie_jayx> not a big perlmonger myself
[02:44] <ScottK> For Sys::Mmap the package name would be libsys-mmap-perl if we have it.
[02:53] <effie_jayx> ScottK,  there is one for ruby, not for perl. I found a way for it not tu use Sys::Mmap
[03:21] <miik> dud, put XBMC center in repo
[05:46] <RAOF> I win!  Who wants to do a copyright-less review of nouveau-kernel-source?
[05:47] <crimsun> how much $incentive is involved?
[05:48] <RAOF> You get a shiny fast featureful 2d driver for your nvidia card.
[05:48] <crimsun> hmm.
[05:48] <LaserJock> shiny *and* fast?! woah there ;-)
[05:49] <rjune_> which nvidia cards?
[05:49] <RAOF> Approximately all of them.
[05:56] <crimsun> sure, I'll take a look in a sec.  Just doing SRU work atm.
[05:58] <RAOF> It should appear on revu.
[06:03] <RAOF> Ahem.  Allow me to upload the right version!
[07:44] <didrocks> Laney: I can do it this evening at home (let's say in 12 hours), it must not be long :)
[08:35] <darius12> I am interested to attempt packaging eclipse 3.4.1 for ubuntu
[08:35] <darius12> It seems like quite a big task
[08:36] <darius12> what would be the best way to recruit for help?
[08:39] <pmjdebruijn> darius12: do you have any packaging experience...
[08:39] <pmjdebruijn> darius12: eclipse really isn't the best way to start
[08:40] <darius12> well, I haven't any "official" packaging experience. But I have my own ppa and have been building linux from scratch - based distros for a few years
[08:43] <darius12> plus it seems nobody else is going to do it (at least soon) and I believe even a medium quality package will be helpful to lots of people
[08:48] <pochu> darius12: see bug 123064, there were some people working on it there. Also you can ask for help/guidance on #debian-java on OFTC
[08:49] <darius12> yes I 've seen both this bug (and its 8 duplicates) as well as the Debian bug #432350
[08:49] <darius12> (it also extends to 3.4)
[08:50] <darius12> so I 'm going to email those people first I guess
[10:21] <pochu> wow @ Paris party
[10:32] <logari81> hi, could anyone take a look here:
[10:32] <logari81> http://revu.ubuntuwire.com/details.py?package=pdfshuffler
[10:32] <logari81> it is my first upload in revu, and I don't have much experience with packaging either
[10:32] <logari81> I would be thankful for any help
[10:34] <emgent> \sh: ping
[10:39] <pmjdebruijn> logari81: check your lintian file...
[10:51] <logari81> pmjdebruijn: missing-python-build-dependency--> I can't understand which is the missing dependency, in ppa it could be built without warnings/errors
[10:52] <logari81> also: should the lintian file be warning-free? or just error-free?
[10:52] <Laney> Programs that can run with any version of Python must begin with #!/usr/bin/python or #!/usr/bin/env python (the former is preferred). They must also specify a dependency on python, with a versioned dependency if necessary.
[10:52] <Laney> logari81: You should get it completely clean
[10:55] <pmjdebruijn> logari81: I'm not entirely sure... lintian also mentions a certainty
[10:56] <logari81> Laney: that means I should add ${python:Depends} in Build-Depends list?
[10:57] <Laney> logari81: No, python:Depends goes in normal Depends:. You should build-depend on python or pythonX.Y if you need a specific version.
[10:57] <Laney> http://wiki.debian.org/DebianPython/NewPolicy
[11:07] <logari81> Laney: that is exactly the guide I have followed, but in the section "Using python-central" there is no reference for python in Build-Depends
[11:07] <logari81> also in the following example https://wiki.ubuntu.com/PackagingGuide/Python there is no such entry either, is there any newer/better example to compare?
[11:07] <hefe_bia> logari81: Left you a comment. This should get rid of the lintian errors and I have mentioned a few other things that might be of concern.
[11:08] <logari81> hefe_bia: thanks a lot
[11:09] <Laney> logari81: It might help to look at some other packages which use python-central
[11:09] <Laney> apt-cache rdepends python-central
[11:09] <hefe_bia> logari81: However I'm also quite new to packaging (especially python). So there might be errors...
[11:11] <logari81> Laney, thanks I ll check it out, I ll also try to apply the suggestions of hefe_bia and come back
[11:11] <rjune_> how does one verify  the dev environment really is Jaunty?
[11:13] <hefe_bia> rjune_: It's Jaunty if you installed Jaunty or upgraded to it ;) Or are you talking about setting up a chroot or something?
[11:15] <hefe_bia> rjune_: But I usually develop on the stable version and use pbuilder to build for the development version - and then check the installation / runtime behavior in a VM of the development version (Jaunty).
[11:16] <hefe_bia> Of course that only works if you don't need new features or libraries from the dev version during development.
[11:18] <rjune_> hefe_bia: setting up a chroot
[11:18] <rjune_> I installed via pbuilder, then followed the upgrade instructions for the chroot
[11:18] <rjune_> I just want to verify it
[11:27] <hefe_bia> rjune_: Hmm. I don't know. I always use pbuilder-dist and create a new base .tgz for each development version. You could maybe log into your pbuilder environment and check the sources.list.
[11:28] <rjune_> hefe_bia: ok. thanks
[12:38] <mok0> bddebian: ping
[13:34] <bddebian> mok0: Uh oh, what'd I do this time?
[13:34] <mok0> bddebian: heh
[13:35] <mok0> bddebian: I just wondered what's become of gltglarea... I can't see release -5 appearing
[13:35] <bddebian> Hmm, odd
[13:35] <mok0> bddebian: did you upload it?
[13:36] <mok0> bddebian: perhaps it clashed with my attempts?
[13:37] <bddebian> Hmm, it shouldn't but I see I didn't get an ACCEPT message back
[13:38] <mok0> bddebian: Last time I got one too, and it was pretty quick
[13:41] <bddebian> Weird, they aren't sitting in incoming
[13:42] <mok0> bddebian: you have a successful *.upload file?
[13:44] <bddebian> No, that's the funny part
[13:50] <mok0> bddebian: I have to run off to a seminar, bbl!
[13:58] <miik> dude, put XBMC in repo now!!!
[13:58] <miik> hurry up guys
[14:34] <lfaraone> hi, does cdbs automagically handle configuration files?
[15:40] <mok0> lfaraone: what configuration files?
[16:23] <lfaraone> mok0: those installed by a package. if I ship new config files, does cdbs automagically generate the script that asks the user if they want to replace their existing ones?
[16:27] <hyperair> has anyone heard of libsigx++?
[16:28] <lfaraone>  Hi, is it safe to assume that when a user installs a PAM module that they want it enabled for all SSH logins?
[16:33] <rjune> no
[16:37] <jdong> probably not.
[16:37] <jdong> especially when ti comes to PAM err on the side of caution.
[16:38] <lfaraone> jdong: Should I add it as a debconf prompt?
[16:39] <lfaraone> jdong: and is there a place where debconf is well-documented for us noobs?
[16:39] <jdong> lfaraone: I think that's a good idea
[16:39] <jdong> default to no but debconf prompt
[16:40] <lfaraone> jdong: ok, how exactly would I do that?
[16:40] <jdong> I have no idea :)
[16:40] <jdong> never used debconf before
[16:41]  * lfaraone panics.
[16:41] <Laney> It's not too bad lfaraone
[16:41] <lfaraone> Laney: Oh?>
[16:41] <Laney> I used http://www.fifi.org/doc/debconf-doc/tutorial.html
[16:41] <hyperair> what does 0c2a mean?
[16:42] <Laney> Something to do with some transition
[16:44] <Laney> hyperair: http://irclogs.ubuntu.com/2008/08/19/%23ubuntu-motu.html I asked then
[16:52] <hyperair> Laney: where can i find more details about it? is there another combination? like 1c2a, or perhaps 0c1a?
[16:52] <Laney> hyperair: I don't know :(
[16:53] <hyperair> damn
[16:53] <Laney> I didn't dig any deeper
[16:53] <hyperair> i'm thinking of packaging sigx++
[16:53] <hyperair> but if i can't figure out these tags i can't
[16:53] <azeem> if you package something new, you don't need them
[16:53] <azeem> they were used when the C++ ABI changed and all C++ libs had to be recompiled
[16:53] <hyperair> azeem: eh? then what's it called?
[16:54] <azeem> hyperair: as usual
[16:54] <hyperair> when does the C++ ABI change?
[16:54] <azeem> when it changes
[16:54] <Laney> Man I bet that transition took a long time
[16:54] <hyperair> specifically which package makes it change?
[16:54] <azeem> hyperair: g++?
[16:54] <Laney> or a lot of effort
[16:54] <Laney> or both
[16:54] <azeem> not sure when the last change was, mabye 4.1->4.2
[16:54] <azeem> or 4.0->4.1
[16:55] <hyperair> oh
[16:55] <hyperair> azeem: so if i'm packaging a new library, what do i call the package with the runtime libs?
[16:55] <azeem> 17:49 < azeem> hyperair: as usual
[16:55] <hyperair> and what's the usual
[16:55] <azeem> see the library packaging guide
[17:05] <james_w> DktrKranz: hi, I saw you uploaded boxbackup, is half the package still failing to actually build?
[17:16] <lfaraone> slangasek: care to look over the upstream source of a PAM module I'm packaging? I'm not qualified to audit the source, and james_w tells me you're a PAM expert.
[17:19] <DktrKranz> james_w: only ARM, actually
[17:20] <jpds> lfaraone: I think he's at a session at UDS at the moment.
[17:20] <DktrKranz> other ports are FULLYBUILT
[17:21] <james_w> DktrKranz: DebugMemLeakFinder.cpp:543: error: '::free' has not been declared
[17:21] <james_w> make[2]: *** [../../debug/lib/common/DebugMemLeakFinder.o] Error 1
[17:21] <james_w> it doesn't fail the build though
[17:22] <lfaraone> jpds: ah, kk.
[17:22] <DktrKranz> james_w: ah... interesting... it fails internally but build process doesn't fail itself
[17:22] <DktrKranz> james_w: looking at debian buildds report, it has the same issue
[17:22] <james_w> interesting is one word for it
[17:39] <crimsun> superm1: anything I should be aware of for grub2 (particularly whether you've tested Debian experimental's snapshot from 2008-12-01)?
[17:39] <crimsun> (hmm, raof would be useful here, too)
[18:04] <quadrispro> RainCT: hi!
[18:04] <RainCT> hi
[18:12] <logari81> hi, I ve just uploaded my corrections here http://revu.ubuntuwire.com/details.py?package=pdfshuffler
[18:12] <logari81> and got this message:
[18:12] <logari81> http://revu.ubuntuwire.com/?archive=4208
[18:18] <quadrispro> RainCT: about http://revu.ubuntuwire.com/details.py?upid=4207 -> as you can see (http://paste.ubuntu.com/83619/), man page seems ok, I don't understand the lintian error, can you give me help?
[18:20] <pochu> quadrispro: .SH "NAME"
[18:20] <pochu> \&\fBInstallation Report Generator\fR \- A small tool to collect installation data for support purposes
[18:20] <pochu> that line is wrong
[18:20] <pochu> what's the binary name?
[18:21] <quadrispro> pochu: ahh! binary's name is installation-report-generator!
[18:21] <pochu> then it should be:
[18:21] <pochu> \&\fBinstallation-report-generator\fR \- A small tool to collect installation data for support purposes
[18:22] <quadrispro> ah-ah! thank you very much pochu!
[18:22] <pochu> quadrispro: test with lexgrog
[18:22] <pochu> quadrispro: e.g. "lexgrog manpage.1"
[18:22] <quadrispro> yes, sure
[18:22] <quadrispro> thanks!
[18:22] <pochu> it should be able to read the WHATIS section
[18:22] <pochu> quadrispro: no problem :)
[18:38] <slangasek> lfaraone: url?
[18:47] <quadrispro> RainCT: now installation-report-generator should be ok (really! :))
[18:48] <RainCT> quadrispro: cool, I'll have a look at it when I've a moment :)
[19:04] <lfaraone> slangasek: http://code.google.com/p/ppp-pam
[19:07] <slangasek> lfaraone: aha, that one.  hrm, there was an ITP for this in Debian already, wasn't there?
[19:09] <lfaraone> slangasek: Yes, I filed it :)
[19:09]  * slangasek chuckles
[19:13] <lfaraone> slangasek: I've got package fever, this is my second package this month (the other is pending ftpmaster
[19:14] <lfaraone> approval)
[19:15] <slangasek> lfaraone: there also seem to be two ITPs for this under different names: 448404, and 506112
[19:16]  * directhex is waiting also on debian NEW
[19:16] <hefe_bia> mok0: Hi! Does your offer to have a look at tomboy-blogposter still stand? ;)
[19:16] <lfaraone> slangasek: Oh? Who filed the other?
[19:16] <slangasek> lfaraone: see the provided bug # :)
[19:18] <hefe_bia> Of course everybody else is invited to have a look to: tomboy-blogposter is a small plugin to post notes from tomboy to your blog. It's been advocated before by mok0 and sikon, only a few little issues where left. (See http://revu.ubuntuwire.com/details.py?package=tomboy-blogposter)
[19:18] <slangasek> lfaraone: so you're looking for an upstream audit, here?
[19:20] <lfaraone> slangasek: An audit of upstream, yes.
[19:22] <lfaraone> slangasek: turns out there is another dupe: 451029
[19:22] <slangasek> yes, though that one has already been merged
[19:24] <lfaraone> slangasek: so which person should I ask?
[19:24] <lfaraone> (if they are still doing work on it)
[19:24] <slangasek> both? :)
[19:24] <slangasek> follow up to the bug and point out that there are two ITPs under different names
[19:25]  * directhex advocates things which make tomboy more featureful
[19:25] <directhex> hefe_bia, if it's not been written for the mono 2.0 transition, you get a severe poking, mmkay?
[19:25]  * directhex looks
[19:28] <lfaraone> slangasek: kk.
[19:31] <hefe_bia> directhex: since the new upstream release, gmcs2 is used explicitly. Last time I checked it built fine under Jaunty. (Dec 6) Should I expect more problems?
[19:33] <directhex> commentes.
[19:33] <directhex> commented.
[19:35] <hefe_bia> directhex: ah, I see.
[19:37] <lfaraone> Hi, I've got a project which has a licence with a clause very close to mozilla's branding clause. Can it be in universe?
[19:37] <lfaraone> ( http://www.alice.org/index.php?page=license
[19:37] <directhex> every bugger needs to write their own license, don't they ¬_¬
[19:38] <lfaraone> directhex: esp. universities. we're having the same trouble with scratch, which is MIT's edu-software. (same category as alice, too)
[19:40] <hefe_bia> directhex: So if I bump the version number for mono-devel and change the build file to use csc, I'll be fine?
[19:41] <lfaraone> Hm... that's sponsored by the NSF w/ public funds. I'm not sure if that licence is compatable with the grant...
[19:41]  * lfaraone sends an angry email.
[19:41] <directhex> hefe_bia, i'm only checking mono compliance. poke people like mok0 for the other bits (though if they're happy there...)
[19:43] <hefe_bia> directhex: ok, I meant only regarding mono compliance.
[19:43] <hefe_bia> So best thing would be to tell upstream to use csc, too.
[19:45] <directhex> hefe_bia, only debian & ubuntu have a "csc", so upstream needs to think carefully
[19:45] <hefe_bia> directhex: I see.
[19:46] <directhex> hefe_bia, in apps with autofoo, you can use ./configure NAME_OF_COMPILER_VAR=/usr/bin/csc
[19:47] <directhex> hefe_bia, e.g. ./configure GMCS=/usr/bin/csc
[19:47] <directhex> hefe_bia, though this one has no config
[19:47] <lfaraone> directhex: oh lord: http://www.i2p2.de/licenses
[19:50] <hefe_bia> directhex: the packages uses a CC variable in the Makefile. I can just override it in rules.
[19:50] <directhex> hefe_bia, well, okay then!
[19:51] <directhex> though "CC" is wrong, it's not a C compiler ;)
[20:02] <hefe_bia> directhex: right ;) I'll pass that along...
[20:10] <hyperair> is anyone familiar with the scons build system?
[20:11] <azeem> hehe, poor guy
[20:21] <hyperair> huh?
[21:39] <TheMuso> i/c
[22:00] <jdong> would anyone cry if I were to propose shoving VLC in a not-very-restrictive apparmor profile?
[22:00] <jdong> at least intuitively I don't think it has any excuse to be executing anything, right? :)
[22:01] <Nafallo> jdong: should give more installations of mplayer. go ahead! ;-)
[22:01] <jdong> :P
[23:17] <Laney> Wow, this place is quiet when UDS is going on
[23:17]  * Laney strokes MOTUs
[23:17]  * StevenK glares at Laney
[23:17] <dholbach> hi Laney
[23:17]  * Laney withers away
[23:17] <Laney> hi dholbach
[23:17] <Laney> enjoying your very own session?
[23:18] <dholbach> Laney: my very own session?
[23:18] <Laney> effective horsemen ;)
[23:18] <dholbach> well... we've a bunch of people here and it's about the Baconator and Mr Castro as well :)
[23:18] <Laney> mmm
[23:21] <Laney> the audio feeds are too unstable