[00:30] <Hobbsee> danbh_intrepid: contentless pong
[00:52] <danbh_intrepid> lol
[00:54] <danbh_intrepid> Hobbsee: I figured I would ask you on irc regarding bug 280497 since I was unsure what info you were looking for.  Or, if I should follow up at all
[01:15] <Hobbsee> danbh_intrepid: well, seeing as it's on the sponsorship queue, and transmission doesn't yet replace clutch, a diff for that would be good.
[01:15] <Hobbsee> (so we don't leave stale binaries on a user's system)
[01:16] <Hobbsee> (apart from that, you're perfectly correct - i used incomplete as a "this is not ready to be done / sponsored yet"
[01:16] <Hobbsee> )
[01:18] <Hobbsee> danbh_intrepid: and i'd prefer not to approve the removal bug, until that debdiff is actually done and in the archive - just to make sure it actually does happen
[01:20] <danbh_intrepid> Hobbsee: cool, sounds good
[01:21] <Hobbsee> danbh_intrepid: did you want to provide a patch, or do you want me to just do it?
[01:21] <danbh_intrepid> well, I don't know how
[01:23] <danbh_intrepid> maybe someday, I've looked at some packaging docs in the past...  regardless, anything thats done will have to be done by others.  I mainly wanted to provide the info clearly
[01:24] <Hobbsee> ok, cool
[01:31] <Hobbsee> danbh_intrepid: fixed (well, the first half)
[01:32] <Hobbsee> drat, i can't unsubscribe bugs from u-u-s
[01:43] <ScottK> emgent: pong
[01:44] <ScottK> Hobbsee: Is it the clutch one?  If so, I'll do it
[01:44] <ScottK> If not, which bug?
[01:45] <Hobbsee> ScottK: yes, and i've already done it
[01:45] <ScottK> OK.  I guess I was confused by you saying you couldn't.
[01:47] <Hobbsee> ScottK: oh.  no, that was some java bug.
[01:47] <Hobbsee> jhove, or something
[01:47] <ScottK> I see.
[02:10] <emgent> ScottK: fast question, i know that it`snt a good time but.. i need your feedback for upload rapache "early eagle" in intrepid :)
[02:11] <emgent> this release is very stable and include big features, now it`s in rapache-devel PPA (~1 month in testing)
[02:13] <emgent> ScottK: if i open bug and I will write a report of it (new features, bug fixes ecc..) can i have some chances for include it in intrepid ?
[02:14] <emgent> i know that you are Server Team delegate.. :)
[02:17] <emgent> ScottK: anyway i go to sleep now, feel free to reply via mail, thanks and good night.
[02:42] <RAOF> Woah!  Who felt the need to upload nouveau?
[02:42] <RAOF> s/upload/sync?
[02:42] <wgrant> RAOF: I think it was bryce.
[02:43] <RAOF> Does it _work_?
[02:43] <wgrant> I heard that it doesn't build.
[02:43] <RAOF> I thought we (a) didn't have a libdrm that the kernel module will build against and (b) didn't have the kernel module?
[02:43]  * RAOF is totally unsurprised
[02:44] <wgrant> Sounds about right.
[02:45] <RAOF> Also, still have the baddevice, but I'm doing stuff now.
[02:45] <wgrant> RAOF: It shouldn't be a baddevice any more.
[02:46] <wgrant> And I know approximately why it happens now.
[02:46] <RAOF> I may need to restart.
[02:46] <wgrant> Yep.
[02:46] <RAOF> I'm a bit busy now, I'll try later.
[02:46] <wgrant> Some part of the X client stack is sending structs in the wrong order.
[02:46] <Hobbsee> oh dear.
[02:46] <wgrant> I can debug it myself now anyway, because I can use a remote amd64 client.
[02:47] <wgrant> (it only affects amd64 clients, which was why none of us could reproduce it)
[02:47] <RAOF> Hah.
[02:50] <wgrant> RAOF: See bug #267611
[02:50] <wgrant> The comments near the end in particular.
[02:51] <wgrant> Running gdb through things, it's sending out the struct verbatim.
[02:51] <wgrant> And nothing I can think of can convince gcc to be reorder it less.
[03:11] <stgraber> wgrant: oh, I just read your comments. Good you found the bug, now the problem is to find a fix :)
[03:15] <wgrant> stgraber: Yes - I'm very confused.
[03:15] <wgrant> This is the first time I've dealt with internal X stuff...
[03:16] <ajmitch> RAOF: slightly surpised about nouveau? :)
[03:16] <RAOF> ajmitch: Indeed.
[03:16] <ajmitch> ah well, that's cooperation for you
[03:17] <RAOF> I'm not surprised that it failed to build, though.
[03:18] <ajmitch> even if it builds, it likely won't work, right?
[03:18] <RAOF> Indeed.
[03:18]  * ajmitch wouldn't mind being able to use it one day, but until then it's not so useful
[03:19] <RAOF> You totally can now, just not with the packages in the archive.
[03:19] <ajmitch> by 'use it', is that limited to just 2D?
[03:20] <RAOF> Not necessarily.
[03:20] <ajmitch> most importantly, will it work with WoW? :)
[03:20] <RAOF> But certainly not _supported_ 3d.
[03:20] <RAOF> No.  Well, maybe.
[03:20] <ajmitch> that's the only important 3D app I have
[10:53]  * laga_ waves
[10:53] <laga_> \sh: lounge metal is awesome
[11:07] <slytherin> geser: persia: Please tell me if I should log a bug for this. The binary for libxstream-java is not present on archive mirror anywhere.
[11:08] <persia> slytherin, Does anything depend on it?
[11:09] <slytherin> persia: I think cglib, I don't remember exactly.
[11:10] <persia> slytherin, apt-cache rdepends tells me there are none (at least for amd64).  It's worth investigating: file a bug if you are certain it shouldn't be gone.
[11:11] <slytherin> persia: here is what apt-cache rdepends tells me - W: Unable to locate package libxstream-java
[11:11] <slytherin> persia: also check this - http://qa.ubuntuwire.com/debcheck/debcheck.py?dist=intrepid&package=groovy
[11:12] <slytherin> looks like it was lost in moving to universe and then back to multiverse
[11:13] <slytherin> slangasek: Need your help please. Binary for libxstream-java is lost. Seems to be result of activity you did on bug #268538
[11:14] <geser> looks like LP was hungry again
[11:14] <slytherin> not result exactly, side-effect
[11:14] <geser> cprov: are you around? can you check why LP ate libxstream-java?
[11:19] <geser> slytherin: LP likes to eat arch:all packages when they are moved between components
[11:20] <slytherin> :-)
[11:41] <slytherin> geser: I am wondering if I should check all other packages dealt under move to universe work.
[11:52] <persia> slytherin, That's probably a good idea
[12:37] <stefanlsd> Is anyone familiar with how bugzilla in intrepid is packaged? It extracts to individual tar.gz (seems like different languages). How do patches get applied in this case?
[12:48] <ia> hello, everybody. could you tell me please, if i would like to use some ppa repo from launchpad, where can i get *.asc key for such repo?
[12:48] <RainCT> ia: PPAs are not signed
[12:49] <ia> RainCT: oh, thank you very much. that's why i can't find it. :-)
[13:54] <james_w> DktrKranz: hi, it seems like you missed an open sponsor request open for xapian-omega
[13:55] <james_w> DktrKranz: ah, no, you did know about it. Why did you keep it open?
[13:59] <DktrKranz> james_w, gah! ... I didn't remember to have uploaded it. Sorry
[14:00] <james_w> no problem
[14:39] <slytherin> persia: cruisecontrol is going to be tough task. It has many build-deps which are not in Debian. :-)
[14:39] <persia> slytherin, refresh me : why did we want that?
[14:40] <slytherin> persia: not that we wanted it. It is one of the two packages on my radar. :-)
[14:41] <persia> slytherin, Ah.
[14:41] <slytherin> and as I said I am going to package it directly in Debian
[14:44] <persia> slytherin, You've a bunch to chase at m.d.o before DIF then :)
[14:45] <slytherin> persia: Let's see. I have made a call for help on debian java list.
[15:11] <AnAnt> persia: Hello, I'm reminding you of sl-modem
[15:14] <persia> AnAnt, When I rebooted today, I specifically re-enabled the modem in the BIOS as the first step to testing :)
[15:17] <slytherin> does anyone know off hand the url to be added in watch file for apache projects?
[15:18] <persia> slytherin, I don't think there's a mirror proxy for apache set up.
[15:27] <slytherin> silly question, all the packages that are needed for clean target should go in build-depends right?
[15:27] <RainCT> slytherin: yep
[15:32]  * persia wants a Build-Depends-Source: header, but it would be Ubuntu-specific, and not very useful in most cases.
[15:38] <slytherin> is anyone having trouble with seahorse not accepting passphrase for gpg key?
[15:40] <Yagisan> slytherin, I did. I ended up disabling the gpg-agent in my gpg.conf
[15:40]  * slytherin is doing same
[15:42]  * Yagisan sighs. I wonder which bright spark decided to disable ifup -a
[15:45] <Yagisan> there is a nice nasty surprise lurking in intrepid main now for anyone (such as me) foolish enough to be testing it on a server - last nights ifupdown update breaks networking.
[15:46] <persia> It works for me.
[15:47] <Yagisan> persia, have network-manager installed ?
[15:47] <persia> Yagisan, Hrm.  Changelog looked like it was doing the intelligent thing.  Do you by any chance have network-manager installed?
[15:47]  * laga_ blinks
[15:47]  * persia sighs at timing.
[15:47] <Yagisan> persia, not at all - hence bug #281984
[15:47] <persia> slytherin, It's working for me.
[15:48] <Yagisan> persia, I -er - wasn't impressed.
[15:48] <persia> Yagisan, understandably.
[15:49] <Yagisan> I lost my kvm farm :'(
[15:49] <persia> 0.6.8ubuntu9 worked fine?
[15:49] <Yagisan> yes
[15:50] <Yagisan> if you must use network-manager - you'd think it would at least pull it in
[15:51] <persia> Maybe just a logic error.  From looking at the changelog and associated mail, it appears like this was an attempt to unbreak ifupdown
[15:52] <persia> Yagisan, You don't happen to see what in http://launchpadlibrarian.net/18439221/ifupdown_0.6.8ubuntu9_0.6.8ubuntu10.diff.gz might cause the issue, do you?
[15:53] <Yagisan> +	} else if (auto_disabled() != 0) {
[15:53] <Yagisan> +		printf("WARNING: ifup -a is disabled in favour of NetworkManager.\n"
[15:53] <Yagisan> +			"  Set ifupdown:managed=false in /etc/NetworkManager/nm-system-settings.conf.\n");
[15:53] <Yagisan> +		exit (0);
[15:53] <Yagisan>  	}
[15:53] <Yagisan> ^^ that stands out
[15:54] <Yagisan> so - if I search up from there
[15:55] <Yagisan> persia, this looks like it may be it
[15:55] <Yagisan> +<<main functions>>=
[15:55] <Yagisan> +static int auto_disabled() {
[15:55] <Yagisan> +	static int initialized = 0;
[15:55] <Yagisan> +	static int auto_up_disabled = 0;
[16:00] <persia> Shouldn't "static int auto_up_disabled = 0;" mean it defaults to working unless specifically set to be broken?
[16:01] <persia> It *should* be broken for systems with network manager installed, or it exposes bug #256054
[16:02] <persia> Wait, no, I'm an idiot, and got caught by the same issue that probably caught the author.  0 is true.
[16:03] <persia> Or, no, that's not it.  Ignore that last line
[16:04] <james_w> +			int managed = iniparser_getboolean (ini_dict, "ifupdown:managed", -1);
[16:05] <stefanlsd> Is anyone familiar with how bugzilla in intrepid is packaged? It extracts to individual tar.gz (seems like different languages). How do patches get applied in this case?
[16:05] <james_w> the -1 is what to return if not found, e.g. the file is not there presumably
[16:05] <james_w> isn't -1 == TRUE?
[16:05] <Yagisan> persia, :/ it looks like it wants network-mager files - I don't have network-manager
[16:07] <persia> james_w, That's one of the things that is language dependent.  In C, if I remember correctly, 0 is false, and non-zero (including -1, 17, 2432349827, etc.) are true.
[16:08] <persia> Yagisan, Yeah.  I think maybe that section needs to check for the existence of the file, and if the file is absent, presume that it should just work.
[16:08] <james_w> yeah, just checked, if it's not found "managed" will evaluate to true, so it will set auto_up_disabled to 1
[16:09] <Yagisan> I just want it to not break the servers - network-manager is not in ubuntu-minimal, and if I get shockers like this - I'm less comfortable even testing new releases
[16:09] <james_w> Yagisan: I'll put together a fix, would you be willing to test it?
[16:10] <Yagisan> james_w, sure. server is amd64. when do you want a report back ?
[16:11] <james_w> Yagisan: actually, can you tell me if you have /etc/NetworkManager/nm-system-settings.conf
[16:11] <persia> Soonest is best (despite the hour).  With luck, we can fix it before people in NZ upgrade on Monday morning ...
[16:11]  * Yagisan is .au
[16:12] <persia> Yes, so you know exactly how soon some sysadmin is going to come in early to work on Monday and break the world :)
[16:12] <persia> (about 4 hours by my count)
[16:13] <Yagisan> james_w, no
[16:14] <james_w> Yagisan: then that's not the problem
[16:14] <Yagisan> persia, that was me ~14 hours ago
[16:15] <persia> james_w, Hrm.  So why would "managed" end up true on a server?  I'm sure there's a logic error somewhere, but don't see it.
[16:15] <james_w> http://paste.ubuntu.com/56681/
[16:16] <james_w> that's the code I'm looking at, just to check we're looking at the same thing
[16:18] <Yagisan> james_w, when I removed that file you asked for (this morning) I got networking back. I just did a quick check by touching a blank file there - and networiking went down again
[16:18] <persia> Which file?
[16:18] <Yagisan> /etc/NetworkManager/nm-system-settings.conf
[16:18] <persia> That should only be there if network manager is installed.
[16:19] <persia> If `touch /etc/NetworkManager/nm-system-settings.conf` is enough to break it, the check is clearly wrong.
[16:19] <Yagisan> it was at one stage. long long ago.
[16:19] <james_w> Yagisan: ok, so it is the issue
[16:19] <james_w> Yagisan: are you happy to test from a PPA, or is a debdiff better?
[16:19] <Yagisan> james_w, a ppa is fine
[16:20] <james_w> Yagisan: cool, it will take me a few minutes
[16:21] <james_w> Yagisan: would you adding the information that you have that file to your bug report?
[16:21] <Yagisan> I gave up on network-manager long ago when it finished on doing dhcp for static connections
[16:21] <Yagisan> james_w, editing it now
[16:21] <james_w> Yagisan: and I would like it if you would remove some of the ALL CAPS parts as well, I don't think they are constructive.
[16:22] <persia> james_w, I think I found it.  I think "int managed = int managed = iniparser_getboolean (ini_dict, "ifupdown:managed", 0);"iniparser_getboolean (ini_dict, "ifupdown:managed", -1);" should be "
[16:22]  * persia tries that again
[16:22] <persia> I think "int managed = iniparser_getboolean (ini_dict, "ifupdown:managed", -1);" shoud be "int managed = iniparser_getboolean (ini_dict, "ifupdown:managed", 0);"
[16:23] <james_w> persia: yeah, that's the change I'm making
[16:23] <Yagisan> neither was getting to spend sunday morning fixing the dammed servers instead of the other things I had to do. I'd have been roasted alive if I were to try and send a package like that to revu.
[16:24] <james_w> Yagisan: yes, I understand your frustration.
[16:25] <Yagisan> someone may want to adjust the Depends line so it pulls in network-manager as well considering it depends on it.
[16:26] <persia> No, it specifically *shouldn't* depend on network manager.
[16:26] <persia> If it does, the code should be fixed to not do that.
[16:27] <persia> The problem looks like a bad default setting, but it could also be an issue with how dictionary.c handles a missing file.
[16:27] <james_w> no, it does the right thing if the file is missing
[16:27] <Yagisan> persia, the message it states is that ifup -a is specifically  "disabled in favour of NetworkManager."
[16:28] <Yagisan> so a normal apt-get remove - not apt-get purge - will fail and hit this bug
[16:28] <persia> james_w, OK.  Hadn't read iniparser_load yet.  Thanks for the confirmation.
[16:28] <Yagisan> (?? when did motu start fixing main ??)
[16:29] <stgraber> Yagisan: the problem is that the current code "thinks" that NM is enabled for your device and then disables ifup as you don't want both ifup and NM messing with your NIC at the same time
[16:29] <persia> When you started complaining about it here :p
[16:30] <Yagisan> persia, I should do that more often - it's so much more productive ;)
[16:31] <Yagisan> stgraber, perhaps it should check for the network-manager binary as well as the config files ?
[16:32] <persia> Yagisan, You could have said something in #ubuntu-devel, which is arguably the more correct forum.
[16:32] <persia> Oooh.  That's a good idea.  Make sure the binary is installed, and *then* check the configuration.
[16:32] <lucas> aaasaazaaza
[16:32] <lucas> oops
[16:32] <persia> lucas, wrong terminal, or escaped binary snippet?
[16:33] <lucas> hanged terminal, but apparently what I was typing was still being sent
[16:35] <james_w> Yagisan: you can see it building on https://edge.launchpad.net/~james-w/+archive
[16:36] <james_w> Yagisan: please test once it is published, starting from a broken configuration
[16:36] <persia> james_w, is that just -1 -> 0 ?
[16:36] <james_w> I've replicated the issue here, and tested the fix
[16:36] <james_w> persia: yeah
[16:36] <Yagisan> persia, I could but last time I reported a bug, I got blown off to launchpad and #ubuntu
[16:36] <persia> What do you think about Yagisan's suggested guard against apt-get remove?
[16:37] <james_w> persia: makes sense to fix the immediate problem now, we can have a discussion on making it more robust when people networking isn't at risk
[16:37] <persia> Yagisan, Depends on the bug.  This is fairly core, and easy to fix.  Ask something less important, and even here you'll get blown off.
[16:37] <james_w> persia: it makes sense, but in theory this code should be robust enough to not need it. Defence in depth is reasonable though.
[16:38] <persia> james_w, Well, considering that the default answer to "Network Mangler is broken" was "remove it" for quite a while, I wonder if it's really that uncommon that the config file is present without the binaries.
[16:39] <james_w> persia: it actually breaks for those who upgrade ifupdown before network-manager currently, so we don't even need to look that far to find failure cases
[16:39] <Yagisan> it's not. When most of my hardy boxes go to intrepid, all of them will have the network-manager config files, but not the binary
[16:39] <james_w> persia: but now I see what you are getting at, and so yes, I think we should make that change
[16:40] <persia> Yagisan, Yes, but you manage all those boxes, so it's only one data point.  james_w point that it will break for *everyone* is probably a better defense to get this sponsored.
[16:41] <james_w> I don't think we'll have trouble finding a sponsor for this fix :-)
[16:41] <Yagisan> persia, if I have the wife complain - does that count as two data points ;)
[16:51] <Yagisan> huzzah - it built
[16:51] <james_w> just waiting for it to be published
[16:58]  * Yagisan twiddles thumbs
[17:01] <Yagisan> james_w, it's installed. I'll be back in a minute or two once the server reboots.
[17:02] <james_w> Yagisan: cool, you are starting from a broken configuration?
[17:02] <Yagisan> /etc/NetworkManager/nm-system-settings.conf now exists.
[17:02] <Yagisan> hopefully eth0, tap0 and br0 all come up.
[17:03] <Yagisan> hmm - better idea
[17:05] <Yagisan> james_w, sudo /etc/init.d/networking restart shows all interfaces up.
[17:09] <Yagisan> james_w, it worked fine on boot
[17:09] <james_w> Yagisan: thanks for the confirmation
[17:10] <Yagisan> thank you james_w and persia for looking at the problem
[17:10]  * Yagisan won't push his luck and complain about kernel bugs yet ;)
[17:12] <persia> For those, you'll want to ask in #ubuntu-kernel : the likelihood any of us can solve them is a lot lower.
[17:14] <Yagisan> persia, I wish I knew how to rebuild the intrepid kernel- I strongly suspect it's a libata problem - as the dvd-rw doesn't like the commands it's getting.
[17:17] <persia> Yagisan, apt-get source linux-image-2.6.27-7-generic should get you most of the way there.
[17:20] <persia> Yagisan, Also, please be more careful when filing bugs.  When finding a sponsor for the fix, th following comment was generated "the bugreport is a ranting chaos ..."
[17:20] <persia> It's a very important bug, and it's great to have it fixed, but better to avoid that :)
[17:24]  * Yagisan shrugs. my ranting bugs get fixed - my non-ranting bugs don't. I've taken to fixing whatever I can and bypassing the bug reporting system.
[17:25] <persia> Yagisan, I guess, although in this case the rant *delayed* the fix.
[17:26] <persia> james_w, On another note : thanks for chasing jd.  I'm curious though: do you read Japanese?
[17:26] <james_w> persia: nope
[17:28] <persia> Ah.  I had initially assigned that to myself, just because I figured I'd have an easier time testing, although on investgiation it turned out you had fixed it.  Fairly impressive, considering that there's a bug against it in Debian that the internals are in Japanese.
[17:28] <james_w> yeah, I grabbed the wrong source package, so the ancestry is wrong in the changelog.
[17:28] <james_w> luckily it didn't involve reading the comments :-)
[17:29]  * Yagisan can read some, but not more than a 4 year old can.
[17:29] <persia> Oh, is some of that Heinrich's changes in Debian then?
[17:30] <james_w> no, it just no longer has the build1 entry
[17:30] <james_w> there is an open sync request though
[17:31] <persia> I saw that.  I'm planning to poke shibata about it when I next see traffic, but it's a holiday weekend, so it's probably not until Tuesday at the earliest.
[17:32]  * james_w notes that there are a couple of jp-related sponsor requests open, perhaps good for someone with experience in that area
[17:32] <persia> Yeah.  I'll probably hit the sbackup one in the morning.  Any others worthy of specific note?
[17:33] <james_w> timidity was the other I was looking at
[17:33] <persia> And that's even a source package I've touched before :)
[17:35] <persia> Hrm.  I thought I fixed the init script already.  There's a fair bit of timidity work.  Thanks for the pointer.
[18:17] <emh> I've adapted a workaround for an X server bug from kpowersave to xprintidle.
[18:17] <emh> The debian/control file lists Milan Zamazal <pdm@debian.org> as the debian maintainer.
[18:18] <emh> I'll submit a patch to the author of xprintidle, Magnus Henoch <henoch@dtek.chalmers.se>, once I've tested it for a while.
[18:18] <persia> emh, Is there a bug in launchpad also?
[18:19] <emh> persia: I don't know.
[18:19] <emh> there is a bug here: http://bugs.freedesktop.org/show_bug.cgi?id=6439
[18:20] <persia> emh, OK.  So there are three places you can fix the bug to get it fixed in Ubuntu.
[18:21] <persia> You can fix it upstream, and Debian will get the new version, and then Ubuntu will get the new version.  It sounds like you're already planning to work with Magnus to do that.
[18:21] <emh> Yes, that seems like a good plan.
[18:22] <persia> You can get it fixed in Debian, in which case you want to open a bug in the Debian BTS, and submit the patch, so Milan can look at it.  It may or may not be suitable for Lenny, but at least Milan can make that decision.  It probably won't get seen if it only goes to Magnus until after the next release.
[18:23] <persia> You can get it fixed in Ubuntu.  Submitting the patch (or preferably a debdiff including the patch) in a bug in Launchpad is the best way to request this.  Someone will evaluate, and maybe apply.
[18:23] <persia> If you do open a bug in Launchpad, linking to the freedesktop.org and Debian bugs would be best.
[18:24] <persia> So, the path to take depends on the urgency of the bug, and the amount of energy you have to spend on it.
[18:27] <emh> Ok. Thank you. I currently have plenty of time and energy, so perhaps I'll pursue all 3 paths once I'm more confident that my changes work. It will be nice for learning about the processes involved.
[18:31] <stefanlsd> Anyone know any caveats about replacing libcgi-pm-perl with perl-modules?
[18:34] <persia> emh, Once you have something that works, you can ask here for help with all three processes.  We're going to be best at explaining about getting it straight into Ubuntu, but since we also send patches upstream and to Debian, we can provide some advice with that.
[18:35] <emh> persia: Ok. Another thing is that the code I adapted from kpowersave is GPL but xprintidle is BSD, so xprintidle will probably have to be relicensed under GPL?
[18:37] <persia> emh, That would be Magnus' decision.  It's unlikely Milan or anyone in Ubuntu would be willing to relicense.
[18:37] <persia> emh, I'd advise finding the solution, and letting Magnus know you have a GPL patch.  Ask if he wants the patch, or a description of the behaviour.
[18:38] <persia> If he doesn't want to relicense, he may want you to describe the solution in words, so he can reimplement it without having ever seen the other code.
[18:38] <persia> That way there's no license question.
[18:38] <emh> Clever :)
[18:43] <stefanlsd> anyone care to sponser - bug #280641 - need to fix this before i can put a CVE into it.
[18:50] <james_w> stefanlsd: why is that stopping you from doing the update for the CVE?
[18:51] <stefanlsd> james_w: i have the debdiff for the CVE already.  just it will need to be based on the updated version.
[18:51] <james_w> why not roll the fixes together?
[18:53] <stefanlsd> as far as i know, security fixes are just the security fix, no other changes.
[18:53] <james_w> stefanlsd: only for stable releases
[18:54] <james_w> stefanlsd: and a bug that prevented a security update from being installed would kind of nullify the point of the security update
[18:57] <stefanlsd> james_w: ok, if i can do it in both, i'll fix the diff. thanks
[18:58] <james_w> stefanlsd: do you know when libcgi-pm-perl was removed?
[18:58] <james_w> what source package was it built from?
[18:58] <stefanlsd> james_w: unsure.  but i suspect it was some time ago, from some of the other changelogs i've seen
[18:58] <laga_> james_w: it's probably in perl-modules now..
[18:59] <stefanlsd> laga_: yeah, it is
[19:12] <stefanlsd> james_w: fixed the diff to include the CVE
[19:13] <james_w> stefanlsd: what needs fixing in Debian?
[19:13] <sebner> james_w: sry, I was ill the last days. will prepare ssmtp updates back to dapper tomorrow :)
[19:14] <james_w> sebner: cool, thanks
[19:14] <james_w> get well soon
[19:14] <sebner> james_w: thx
[19:14] <stefanlsd> james_w: what do u mean?
[19:15] <james_w> stefanlsd: I don't see links to Debian bugs for either of the changes
[19:23] <stefanlsd> james_w: seems like libcgi-pm-perl is still in debian, so not an issue. http://security-tracker.debian.net/tracker/CVE-2008-4437  - best i can find on the cve.
[19:23] <james_w> stefanlsd: it might still be worth reporting
[19:25] <james_w> the security issue is marked as fixed in unstable
[19:25] <stefanlsd> james_w: will pass patches up to debian. yeah.
[19:25] <james_w> they've got the fix then, so I don't think there is a need to forward it
[19:25] <james_w> my dinner is ready now, I'll take a look after that
[19:25] <stefanlsd> james_w: kk. thanks :)
[19:55] <cbx33> hey guys
[19:55] <cbx33> can I still fix bugs in a package or is it too late now
[19:55] <cbx33> sorry I've been a little out of touch lately
[19:55] <stgraber> fix only is fine, if it requires a new upstream that also introduces new features you'll need a FFe though
[19:56] <cbx33> ok
[19:56] <cbx33> it's only a tiny app
[19:56] <cbx33> gisomount
[19:56] <cbx33> I saw that some bugs were raised that I should ought to fix
[19:57] <cbx33> I don't intend to add any new features
[19:57] <cbx33> but i would be fixing these bugs upstream
[19:57] <stgraber> if the new upstream is bugfix only, that should be fine
[19:57] <cbx33> ok
[19:58] <cbx33> how long do I have to fix these bugs?
[19:58] <stgraber> we'll enter RC freeze on Thursday IIRC, so best to have that fixed before then
[19:59] <stgraber> but as I guess it's an universe package, it should be possible to send bugfix only even after that date (I don't upload in universe so I'm not quite sure about that though)
[19:59] <cbx33> hehe
[19:59] <cbx33> I can upload to universe
[19:59] <cbx33> I think ;)
[20:20] <james_w> stefanlsd: "debian/maintenance"? bonkers
[20:20] <james_w> not your fault of course
[20:20] <stefanlsd> yeah. first time i've seen that system also.
[20:33] <james_w> stefanlsd: why ubuntu2.1?
[20:35] <stefanlsd> james_w: yeah. wanted to check about that.  was either 1.1 or 2.1.  i was under the impression that .1 would be just a security update.  wasnt sure what happened if it had another fix with it.
[20:36] <crevette> hello
[20:37] <james_w> stefanlsd: that only applies for updates the stable releases. The reason it is done is so that it doesn't use a version number where the same version number would be in the next release, which would mean there wasn't an upload path. That doesn't apply here, so I've made it just ubuntu2
[20:37] <james_w> hey crevette
[20:37] <crevette> hello james_w
[20:38] <stefanlsd> james_w: thanks. understood.
[20:44] <crevette> I'd be interested if someone can review  https://bugs.launchpad.net/ubuntu/+source/nemiver/+bug/262246
[20:44] <crevette> thanks
[20:47] <james_w> stefanlsd: doesn't work for me
[20:48] <james_w> Checking for          CGI.pm (v3.33)    found v3.29
[20:49] <slytherin> crevette: ping
[20:49] <crevette> slytherin: hello
[20:50] <slytherin> crevette: nautilus-sendto seems to be broken for some people, showing error obex not supported. Any idea?
[20:50] <crevette> hmmm no
[20:50] <crevette> It tested with my deviceds ant it was working
[20:51]  * crevette tries on its new phone
[20:51] <slytherin> crevette: It shows error for me too but then nothing is working on my side so Ican not say only nautilus-sendto is broken.
[20:52] <slytherin> crevette: does nautilus-sendto have depends on libbtctl?
[20:58] <stefanlsd> james_w: what doesnt work for you?
[20:59] <james_w> Checking for          CGI.pm (v3.33)    found v3.29
[20:59] <james_w> installing the package
[21:00] <james_w> http://paste.ubuntu.com/56776/
[21:04] <crevette> slytherin: do ypu have any error when you run the command from the terminal ?
[21:05] <slytherin> crevette: as I said bluetooth is not at all working for me. Probably hardware problem. So you will get no useful information from me.
[21:10] <crevette> slytherin: it seems nautilus-sendto just use plain bluez dbus APoi
[21:10] <crevette> API
[21:12] <slytherin> crevette: Ok. I will let you know the bug tomorrow if I find it. Too late for me now. Got to go.
[21:12] <crevette> okay good night slytherin
[21:17] <stefanlsd> wgrant: mm. bleh. just did it in vm and get the same error. sorry.  from what i've found. bugzilla does want 3.33. perl-modules doesnt have it.  debian recommends -  libcgi-pm-perl which replaces perl-modules CGI.pm with a later version (we dont have it)
[21:17] <emgent> evening
[21:17] <sebner> emgent: \o/
[21:17] <emgent> sebner: :)
[21:18] <stefanlsd> bleh. james_w ^
[21:18] <sebner> emgent: did you also participate at the ubuntu-it meeting?
[21:18] <james_w> stefanlsd: yeah, you might want to find out why we don't have it
[21:19] <emgent> sebner: no
[21:20] <stefanlsd> james_w: kk. thanks. will try find out.
[21:21] <sebner> emgent: what a pitty. Luca showed me the "I'm drunken because of the good wine" photos :P
[21:21] <emgent> hahah
[21:22] <emgent> i saw that.
[21:22] <sebner> ^^
[22:20] <rn114> hi, i'm having a play with creating .deb packages, and have successfully created a couple. however, having updated the sources i'm working from and done a few tweaks of the packaging no binaries actually end up in the .deb following running pbuilder on the .dsc
[22:20] <rn114> could anyone think of an obvious reason?
[22:23] <Elbrus> rn114: cleaning up the debian/files during the process was an obvious one for me the other day
[22:24] <Elbrus> rn114: do you try to build multiple binaries from one source?
[22:25] <rn114> Elbrus, im certainly not trying to
[22:25] <Elbrus> rn114: maybe you can show your rules file in a pastbin
[22:25] <Elbrus> !pastbin
[22:25] <rn114> yeah ill paste it up thanks
[22:25] <rn114> !pastebin
[22:26] <Elbrus> thats what I meant... :(
[22:26] <rn114> yeah :) here it is: http://paste.ubuntu.com/56800/
[22:27] <rn114> its quite simple, based off a dhbuild's production
[22:29] <Elbrus> I think you commented out the dh_install was that intensionally?
[22:31] <rn114> Elbrus, around line 79?
[22:31] <Elbrus> exactly
[22:32] <rn114> hmm, its a good point
[22:32] <rn114> i'm just going to diff with my old version to check if i missed that
[22:34] <rn114> thats the same as before, i think it should be handled by the dependency on install shouldnt it? that calls $(MAKE) install INSTALL_ROOT=$(CURDIR)/debian/mythtv and i think that should work
[22:35] <rn114> its strange because when i run pbuilder it does all the compilation and everything (and seems to do the install step as well) but then the .deb just doesn't contain any binaries!
[22:38] <Elbrus> rn114: I might be completely wrong, but either the install should be in DEBIAN instead of debian, or something like dh_install --sourcedir=debian/mythtv is needed (mind you I don't know the details of building yet).
[22:40] <Elbrus> rn114: maybe have a look at the man-page of dh_install
[22:44] <rn114> Elbrus, i think dh_install just copies a list of files and the make install command should handle that for me
[22:47]  * Elbrus just tries to find out where the files are copied to for the build.. is that in debian/<package>?
[22:49] <rn114> heres an example line from the build log file: cp -f "mythfrontend" "/tmp/buildd/mythtv-robin-18380/debian/mythtv/usr/local/bin/mythfrontend"
[22:49] <rn114> this is were it copies it
[22:58] <Elbrus> rn114: maybe you can also pastebin the build log? Just to see if I see something obvious...
[22:58] <rn114> its almost a megabyte!
[22:58] <rn114> i just cant really see much of a difference annoyingly
[23:04] <Elbrus> rn114: sorry, I am out of ideas... Somebody else???
[23:07] <Elbrus> one thing, shouldn't the INSTALL_ROOT not be DESTDIR? See: http://www.gnu.org/software/automake/manual/html_node/DESTDIR.html
[23:07] <Elbrus> s/not//
[23:11] <emgent> norsetto_: o/
[23:11] <norsetto_> emgent: \o/
[23:14] <sebner> hihu norsetto_
[23:15] <norsetto_> sebner, \\o//
[23:16]  * sebner is scared. Why does norsetto has 4 hands ^^
[23:16] <norsetto> sebner its the 2 heads which should be worrying
[23:17] <ajmitch> sebner: that's the legs flying up as he leaps in the air
[23:17] <sebner> norsetto: ^^
[23:17] <sebner> ajmitch: flying ^^
[23:23] <rn114> thanks for your thoughts Elbrus