[00:02] <ethana2> adinc ran into this missing package also
[00:02] <ethana2> ..he was considering compiling something from source
[00:03] <adinc> yes, i would appreciate if there would be a package for truecrypt
[00:04] <ethana2> ok :)  ..that is all
[00:38] <buttterz> evening
[00:40] <buttterz> adinc , has this become a package yet? if not i have created one.
[00:40] <adinc> buttterz: truecrypt?
[00:40] <buttterz> adinc yes
[00:40] <adinc> no there is no pcakgae for it yet
[00:41] <adinc> unfortunately not
[00:41] <buttterz> ok well haha i have packaged a deb
[00:41] <adinc> can we have it
[00:41] <buttterz> certainly, i'll put it up after i get my mother -- she broke her ankle haha -- this is about earlier correct.
[00:41] <buttterz> i saw you in +1
[00:42] <adinc> yes
[00:42] <adinc> when can we expect this?
[00:43] <buttterz> hopefully tonight otherwise tomorrow -- are you a dev here? ive been trying to pick up a mentor because i used to be a debian dev and freebsd dev -- i am not that familiar with ubuntu because i haven't used it enough yet -- just started in production and on a few workstation of my own in hte home
[00:43] <buttterz> though debian and ubuntu are at there base the same.
[00:43] <adinc> buttterz: no, i'm not, i'm new to ubuntu aswell (comming from debian)
[00:44] <buttterz> alright well i'll try to have it committed asap -- if thats what they call it here :)
[00:44] <adinc> yes, they talk about repository and committing it
[00:44] <adinc> like cvs
[00:45] <buttterz> i figured as much -- well cvs is what i'm most familiar with anyways -- thats all we use in freebsd really
[00:45] <buttterz> even for ports kernel etc
[00:45] <adinc> for sources sure
[00:45] <buttterz> i should be around later but i must leave now
[00:46] <buttterz> away messages will be logged if you have other things to say
[00:46] <buttterz> evening
[00:46] <adinc> good evening and thank you
[00:51] <adrian_2002ca> hey all, so i'm a new bug-buster and i've been bustin for a day or so....im at a loss about bug 200406...i've looked up  the user(Jaakan Shorter) and it seems he's got a lot of programs crashing with SIGSEGV...would this mean maybe it's his setup(drivers, hardware etc. doing it>?)
[00:51] <ubotu> Launchpad bug 200406 in torcs "torcs-bin crashed with SIGSEGV in GfParmGetStr()" [Medium,New] https://launchpad.net/bugs/200406
[00:53] <adrian_2002ca> the thing is i cant really replicate the bug and looking at the source, i dont see the problem jump out and bite me..
[00:53] <adrian_2002ca> even when looking carefully
[00:55] <adrian_2002ca> also, theres a new version out
[00:55] <adrian_2002ca> 1.3.0-3
[00:55] <adrian_2002ca> anyone there?
[00:56] <adrian_2002ca> anyone?
[01:02] <slangasek> \sh_away: erm, why did you ship a bunch of lintian overrides for empty files and directories in libzend-framework-php instead of just cleaning them out of the package?
[01:11] <bddebian> Heya gang
[01:12] <RAOF> Heya bddebian
[01:13] <bddebian> Hi RAOF
[01:15] <protonchris> hey bddebian
[01:16] <bddebian> Hi protonchris
[02:05] <Fujitsu> RAOF: Ah, thanks, that seems to have got the module to load.
[02:06] <RAOF> Fujitsu: Great.  I will, at some point, get around to fixing that properly.  But since it always WorksForMe, it never really seems very urgent :)
[02:12] <StevenK> Bwahaha. One of my friends voicemail messages is "You've reached <x>. Leave a message with the warden."
[02:16] <protonchris> Heh.  nice.
[02:17] <buttterz> hey all
[02:17] <buttterz> it seems someone has already been working on this after i have a .deb for true crypt
[02:17] <buttterz> i'm not exactly familiar with launchpad as we do not use it in freebsd but the link where some information about this is https://code.launchpad.net/truecrypt-deb/trunk
[02:19] <Fujitsu> RAOF: Even got dual-head working with RandR 1.2.
[02:19] <Fujitsu> Very nice indeed.
[02:20] <RAOF> Fujitsu: Oh, yes.  Yes it is.
[02:20] <Fujitsu> Configuring dualhead with the blob is ridiculous.
[02:20] <Fujitsu> I can't get it working in Hardy.
[02:20]  * StevenK wonders if randr can rotate seperate heads.
[02:20] <RAOF> Fujitsu: As long as you don't mind !{3d, suspend}, it's _much_ nicer in every way than the blob.
[02:20] <RAOF> StevenK: Yes.
[02:20] <Fujitsu> StevenK: Yes.
[02:20] <StevenK> Heh, stereo too. :-P
[02:21] <StevenK> I wait for 3D. Suspend I don't care about, since it's a desktop.
[02:22] <RAOF> 3d kinda works ish.
[02:22]  * RAOF suspects StevenK wants WoW-capable 3d, and that's not there yet :)
[02:23] <StevenK> Even crack-attack-capable 3D would be cool.
[02:23] <Fujitsu> I normally run Compiz, but I can live without it.
[02:23] <Fujitsu> (and this is only my work machine; my home machine is Intel)
[02:23] <StevenK> (That's just a shedload of vertices and transforms)
[02:23] <Fujitsu> It's so fast, and the colours seem nicer than nv.
[02:24] <RAOF> Fastest 2d X driver available right now :)
[02:24] <Fujitsu> Not bad.
[02:25] <RAOF> Everyone else, they say gnome-system-monitor takes too much CPU.  Nouveau don't know what they takin' about.
[02:26] <RAOF> On the other hand, every now and then someone breaks LVDS, and I get a nice white...blue...green screen.
[02:26] <Fujitsu> For some reason it didn't get a correct EDID from one of my monitors (only got 1280x800 instead of 1440x900), but manually adding the mode worked.
[02:28] <StevenK> RAOF: I do wonder, though -- Nvidia have not helped this process at all, like say, Intel or AMD, so why should they get an open-source driver 'for free' as it were.
[02:29] <StevenK> Although, of course, it's more for the community at large, rather than Nvidia.
[02:30] <RAOF> They already provide a (terrible) open-source (kinda) driver.
[02:30] <Fujitsu> nv is really really bad.
[02:30] <RAOF> And they get a driver because we want a driver.  A lot.
[02:31] <RAOF> Maybe once nouveau works sufficiently well, they'll be motivated to help? (This seems unlikely).
[02:32] <StevenK> Indeed. The fact that they haven't helped by now points to them not helping at all.
[02:33] <RAOF> It sucks.  What can you do, except not buy nvidia hardware?
[02:34] <StevenK> But that means using fglrx, which is even interesting and esoteric than the blob.
[02:35] <Fujitsu> Old Radeons work OK with ati.
[02:35] <StevenK> Old Radeons weren't really up to par with Nvidia's of the time.
[02:36] <StevenK> (More's the pity, even.)
[02:36] <RAOF> _New_ radeons aren't really up to par with nvidias, but the gap isn't as bad.
[02:37] <StevenK> Mmmmmm. I last compared a 9200 and an GeForceFX 5-something, and that was noticeable
[02:38] <RAOF> Hm.  Interesting.  pulseaudio stops outputting sound at all if I drop the mixer level <=30%.
[02:38] <StevenK> It goes softer and then silence?
[02:39]  * StevenK tries to figure out how to bend Apache to his will
[02:39] <RAOF> Yup
[02:39] <jdong> RAOF: ha that's not as fun as my macbook
[02:39] <jdong> RAOF: the headphone volume slider is logarithmic
[02:39] <jdong> RAOF: I found out.... the hard way.
[02:40] <RAOF> That seems like correct behaviour to me.  _Hearing_ is logarithmic.
[02:40] <StevenK> jdong: Are your ears still ringing?
[02:40] <StevenK> RAOF: But only for certain directions
[02:40] <jdong> StevenK: I don't know, it's too hard to tell :D
[02:40] <StevenK> Haha
[08:08] <sherl0ck> hey i lost my post in the forums, anyone help?
[08:09] <sherl0ck> it was a tutorial i was wrting
[08:41] <skwashd> hi all
[08:41] <skwashd> how do i find out why a motu maintained package was dropped from a release?
[08:43] <soren> skwashd: http://people.ubuntu.com/~ubuntu-archive/removals.txt
[08:43] <soren> sherl0ck: I think you've got the wrong channel.
[08:44] <sherl0ck> ok
[08:44] <skwashd> soren: thanks ... not the most user friendly list ... but hey it works :)
[08:46] <skwashd> soren: and now is too late to get it back in for hardy ... right?
[08:46] <soren> skwashd: Depends.
[08:47] <skwashd> it was dropped from debian after it was orphaned ... and so ubuntu did the same (the maintainer - ajmitch is AWOL)
[08:47] <skwashd> now it is in debian unstable again ... and the gutsy debs should still work with hrady
[08:48] <skwashd> either way i would like to see it make a come back in 1 form or another
[08:49] <skwashd> soren: which side of depends does this case fall :)
[08:49] <soren> skwashd: File a feature freeze exception request along with a sync request.
[08:49] <\sh> moins
[08:49] <soren> skwashd: If it's been in the archive before, I don't think it'll be a problem, but it's not up to me.
[08:49] <skwashd> okay ... i take it that is covered in the feature freeze page on wiki?
[08:56] <skwashd> man i hate launchpad
[08:56] <skwashd> soren: i have tried to find how to file a bug against motu-release and phpgroupware ... and i can't manage to do it for either
[08:57] <soren> skwashd: File a bug against phpgroupware and subscribe motu-release.
[08:58] <skwashd> soren: ok ... thanks
[08:58]  * skwashd brute forces lp
[09:30] <tbf> ScottK: "if the archive admins will look at it" - "look at it" in which sense? (gnome-lirc-properties, LP #192368)
[09:30] <ubotu> Launchpad bug 192368 in ubuntu "[FFe] Please add gnome-lirc-properties" [Wishlist,New] https://launchpad.net/bugs/192368
[09:32] <tbf> slangasek: did someone talk to you already, regarding gnome-lirc-properties?
[09:32] <slangasek> er, no
[09:33] <slangasek> I don't understand why this is a concern - syncing packages is easy, it's the reviewing that's hard :)
[09:34] <slangasek> i.e., if it gets a FFe from motu-release, there's no reason for ubuntu-archive not to rubber-stamp it, time allowing; of course I can't guarantee that time will allow, but I don't think the sync queue is so backed up as to suggest it's full until release?
[09:35] <tbf> slangasek: can you add a comment like this to the ticket?
[09:38] <slangasek> not at the moment
[09:54] <\sh> slangasek: do we only support lpia archs with x86 processors?
[10:08] <slangasek> \sh: what?
[10:08] <slangasek> \sh: lpia is the low-power Intel architecture, what other lpia is there that doesn't have an x86 processor?
[10:18] <\sh> slangasek: I thought lpia is the synonym for everything which is mobile
[10:20] <slangasek> no
[10:20] <slangasek> lpia is an architecture
[10:25] <\sh> hmm...wine on lpia?
[10:25] <soren> Why not?
[10:25] <\sh> soren: well, it's building now
[10:26]  * \sh needs to find someone who could test it on real hardware ;)
[11:01] <Daviey> a/win 7
[11:05] <ScottK> tbf: It was my impression from the bug that this was a new package we were discussing.
[11:06] <tbf> ScottK: yup, it is. but it's also the first time i go that far with pushing a package - so i might ask stupid questions
[11:07] <ScottK> The deadline for new packages was 6 weeks ago.  The archive admins generally have other things to be focusing on at this point in the process.
[11:10] <tbf> ScottK: yes, work on that project was started very late (only three weeks before the deadline)
[11:12] <tbf> well ScottK, have you read slangasek's comment?
[11:12] <tbf> (10:34:34) slangasek: i.e., if it gets a FFe from motu-release, there's no reason for ubuntu-archive not to rubber-stamp it, time allowing; of course I can't guarantee that time will allow, but I don't think the sync queue is so backed up as to suggest it's full until release?
[11:13] <tbf> ScottK: reads to me, that there still is a small chance to let it slip in
[11:13] <ScottK> I saw that.  I'm not sure he realized it was a new package.  New packages take a lot more time to review than existing ones.
[11:13] <ScottK> I haven't really formed an opinion yet if we should approve it or not.
[11:14] <ScottK> Gotta run for a bit.
[11:16] <tbf> ScottK: configuring remote controls on linux is quite dreadful still. this program could improve the experience dramatically.
[11:16] <tbf> scottk: well, but i am biased as i was tasked to write it
[11:16] <tbf> scottk: see you
[11:52] <mok0> eeek, hardy upgrade not working...
[11:59] <Hobbsee> slangasek: ah, right.  Fair enough.  Obviously, i don't know, anyway :)
[12:01] <sistpoty|work> hi folks
[12:07]  * french1 thanks slangasek for fixing his NetworkManager
[12:14] <sebner> ahoi sistpoty|work
[12:14] <sistpoty|work> hi sebner
[12:16] <tbf> sistpoty|work: hey
[12:16] <sistpoty|work> hi tbf
[12:34] <Iulian> Hi
[13:12] <Iulian> Can someone please ACK bug #206515 ?
[13:12] <ubotu> Launchpad bug 206515 in libebml "Please sync libebml-dev 0.7.7-3.1 (universe) from Debian unstable (main)" [Wishlist,New] https://launchpad.net/bugs/206515
[13:22] <jcastro> rexbron: ping me when you're around
[13:23] <\sh> ok...wine for lpia compiled
[13:24] <\sh> I wonder if this works
[13:24] <\sh> hey jcastro how are you doing? :)
[13:26] <rexbron> jcastro: what's up?
[13:31] <buttterz> morning
[13:33] <Hobbsee> hi jcastro
[13:33] <jcastro> hi \sh, rexbron, Hobbsee!
[13:34] <jcastro> rexbron: did you ever get openexr in a ppa?
[13:34] <rexbron> jcastro: yes, mine https://edge.launchpad.net/~rexbron/+archive
[13:34] <jcastro> rock, thanks.
[13:35] <jcastro> rexbron: do the blender guys know about your ppa?
[13:35] <rexbron> jcastro: I am still working on getting bleeding edge setup
[13:35] <jcastro> ok
[13:35] <rexbron> when that is working, I will let them know
[13:36] <rexbron> or you rather
[13:36] <jcastro> seeing the open movie thing on blogs today reminded me
[13:36] <rexbron> jcastro: In the mean time, cory has lent me some space on one of his personal boxes
[13:36] <jcastro> rexbron: were you still looking for a host?
[13:37] <jcastro> rexbron: maybe blender itself might provide space, since it will be directly helping them out?
[13:38] <jcastro> should I ask someone?
[13:38] <\sh> 1.5.1 /window 11
[13:38] <\sh> grmpf
[13:38] <\sh> I don#t get it today
[13:38] <buttterz> hello
[13:40] <rexbron> jcastro: I intend for this to be larger than just blender
[13:40] <rexbron> but in the mid-term, that is an option
[13:40] <jcastro> ok
[13:42] <Iulian> \sh: Why don't you use just /win instead of /window? Or you like the TAB key? ;)
[13:44] <\sh> Iulian: well, it doesn't help when you forget the /
[13:45] <Iulian> Heh, indeed.
[13:46] <_ruben> i just try to stay under 20 windows and dont use /window for anythingn other than closing windows :p
[13:46]  * Iulian likes ctrl+n/p
[13:50] <DktrKranz2> Hobbsee: mind give-back collectd and wmnut in Hardy? Thanks. (I lagged, sorry if asked twice)
[13:53] <Hobbsee> done
[13:53] <ScottK> Please don't forget about Bug #204895 is you're looking for stuff to work on.
[13:53] <ubotu> Launchpad bug 204895 in cfv "Packages failed archive rebuild test possibly due to python-central transition" [Undecided,In progress] https://launchpad.net/bugs/204895
[13:55] <emgent> heya
[13:58] <jdong> vorian: new ktorrent 3.0.1, when you feel bored feeel free to UVF it.
[13:58] <vorian> danke jdong
[13:58] <vorian> :)
[13:59] <vorian> prolly later on tonight
[13:59] <jdong> thank you :)
[13:59] <jdong> I've got an eeepc to set up today ;-)
[13:59] <vorian> no, thank you jdong :)
[13:59] <vorian> w00t
[13:59] <vorian> thats fun
[13:59] <jdong> it is indeed
[14:00] <vorian> would someone be so kind as to sponsor bug 206278 for me?
[14:00] <ubotu> Launchpad bug 206278 in keurocalc-kde4 "keurocalc-kde4 needs strict versioned dependency on keurocalc-kde4-data" [Medium,Confirmed] https://launchpad.net/bugs/206278
[14:39] <sping> hello
[14:39] <buttterz> hi whatsup
[14:40] <sping> a library of mine (liburiparser1) is rather outdated in ubuntu but up to date in debian
[14:40] <sping> is there any chance to get it updated before hardy?
[14:40] <sping> what would i have to do?
[14:41] <mok0> sping: are there fixed bugs in the new version?
[14:42] <sping> mok0: there were several major things fixed in between. (0.6.0 --> 0.6.4)
[14:42] <sping> mok0: wait a sec
[14:42] <mok0> sping: then it should be possible to get a ffe
[14:43] <buttterz> sping i expect that should not be a problem
[14:45] <mok0> sping: report a needs-sync bug on LP, and reference the bugs that have been fixed... at this time, we can only accept syncs that fix bugs
[14:46] <sping> mok0: changes include crash fixes. i don't have any bug numbers though since the were never filed somewhere.
[14:46] <sping> mok0: i could attach an assembled changelog, would that be okay?
[14:46] <mok0> sping: perfect
[14:47] <sping> mok0: i'm no expert on that bug some fixes might affect security
[14:48] <sping> mok0: escpecially since the bugs were reported by someone doing a security review :-)
[14:48] <mok0> sping: are there apps that depend on uriparser?
[14:48] <buttterz> who would i talk to about getting a .deb committed to the repository
[14:49] <sping> mok0: recent fapg and herrie (through libspiff)
[14:49] <mok0> sping: it needs to be verified that they will not suffer from the upgrade
[14:49] <mok0> buttterz: what deb are you talking about?
[14:50] <buttterz> this is a truecrypt wrapper --
[14:50] <mok0> buttterz: If it's a new package, you have to submit it for review
[14:50] <sping> mok0: nono, the fixes fixed security issues, they did not introduce such
[14:50] <sping> mok0: herrie and fapg both run fine with the latest version in debian
[14:51] <mok0> sping: Ah, ok, sounds good then. Put a statement to that effect in your bug report
[14:51] <sping> mok0: okay
[14:51] <buttterz> mok0 , i used to do this with debian until they just let me do it myself -- any place in particular or should i just check the site
[14:51] <mok0> buttterz: Is the package in debian?
[14:53] <mok0> buttterz: If so, it will be sync'ed automatically for interpid
[14:54] <StevenK> "Intrepid"
[14:54] <StevenK> Not "Interpid"
[14:55] <buttterz> haha thanks i was like what?? between pid's
[14:55] <mok0> mok0: ooops
[14:56]  * mok0 thinks ibex is easier to type... 
[14:56] <buttterz> i see so you are talking about ibex -- the issue though is that several people who have been using truecrypt have been experiencing issues on their machines
[14:56]  * buttterz agrees
[14:56] <sping> mok0: how do i make the sync request ask for a ffe?
[14:56] <buttterz> so i made up this package -- and it just needs a sponser -- i already took care of it in debian because like i said -- they just let me cvs now
[14:57] <buttterz> people have been having issues on heron not ibex it seems
[14:57] <mok0> sping: you subscribe "motu-release" to the bug
[14:58] <sping> mok0: ? okay :-)
[14:58] <mok0> buttterz: If it's in hardy, you should do what sping is doing, file a needs-sync bug with a description of the bugs fixed
[14:58] <mok0> sping: you know what I meant by "subscribe"?
[14:59] <buttterz> is that the equivalent here to getting a sponsor?  how impersonal we have gotten with our work
[15:00] <mok0> buttterz: packages in Debian are automatically incorporated, but at this time, there is a feature freeze on hardy, so everything needs to get a reception
[15:00] <mok0> s/reception/exception
[15:01] <sping> mok0: i think so, but there's no such field yet. i guess that will come after submit?
[15:01] <buttterz> ok...i'll figure this out so i can do it myself again i hate waiting.
[15:01] <buttterz> thanks for the help gents
[15:01] <mok0> buttterz: If it's a straight sync (with no Ubuntu mods) all you need is the go-ahead and the archive admins will do it
[15:02] <mok0> buttterz: that's what the motu-release guys do: issue the go-ahead that the modification is sane and not just an introduction of new features
[15:03] <buttterz> well its smart to package something like this for ubuntu users since its intended to be easy to use -- truecrypt installations are done mostly by sys admins -- not 12 year olds starting linux
[15:04] <mok0> buttterz: what is the name of the package?
[15:05] <buttterz> though its based on source because of the stupid truecrips license is not dfsg compliant
[15:05] <buttterz> which sucks nuts because i can't make them binary -- just automate the process
[15:07] <mok0> buttterz: easycrypt?
[15:12] <sping> mok0: https://bugs.launchpad.net/ubuntu/+source/uriparser/+bug/206578
[15:12] <ubotu> Launchpad bug 206578 in uriparser "[sync-request] Update to 0.6.4 from Debian, please, please" [Undecided,New]
[15:13] <mok0> sping: cool
[15:13] <sping> mok0: great you like it :-)
[15:14] <mok0> sping: it should be taken care of now
[15:14] <sping> mok0: that would be great
[15:15] <rockstar_> There's a MOTU session today, right?
[15:15] <mok0> sping: the mr team will look at it, and subscribe the archive admin if they accept the update
[15:23] <mok0> rockstar_: there's a motu school at 20:00 UTC
[15:24] <rockstar_> mok0, Yea, that's what I had in my calendar, wanted to make sure everything was good.
[15:25] <mok0> rockstar_: In #ubuntu-classroom
[15:25] <mok0> Can't remember the subject though
[15:25] <rockstar_> FTBFS
[15:26] <rockstar_> I believe...
[15:27] <YokoZar> Should I be happy that Wine outranks tracker in popcon?
[15:31] <sistpoty|work> sping: see my comments on the FFe
[15:33] <geser> rockstar_: yes, the topic is FTBFS
[15:51] <ScottK> sistpoty|work: Re the uriparser FFe, since it just a sync, if it's sane I think we should do it despite the lack of rdepends.  Who knows what else may use it and I agree from the changelog that there are potentially security concerns with the version we have.
[15:52] <sistpoty|work> ScottK: well, I guess the question to ask for a test of the functionality will also provide information to what a library per se might be useful ;)
[15:53] <sistpoty|work> ScottK: but I don't have a too strong opinion to not have it in ;)
[16:04] <sping> sistpoty|work: that's you, i see
[16:04] <sistpoty|work> yep
[16:04] <sping> sistpoty|work: just replied
[16:06] <sping> sistpoty|work: fapg >=0.39 in debian depends on uriparser, ubuntu has 0.38
[16:07] <sping> sistpoty|work: herrie depends on libspiff in debian, it is not in ubuntu yet it seems
[16:08] <sistpoty|work> sping: would there be a reason, why we'd need the newer fapg?
[16:08] <sistpoty|work> sping: to the diffstat: best would be debdiff between new and current source package | diffstat
[16:09] <sistpoty|work> sping: build log: package build log from pbuilder or similar
[16:09] <sping> sistpoty|work: feature-wise for sure but there was fix as well that might be security related
[16:09] <sistpoty|work> sping: ok
[16:09] <sistpoty|work> sping: install log, messages dpkg gives you when installing/purging the new package
[16:11] <sping> sistpoty|work: on ubuntu hardy or on debian?
[16:11] <sistpoty|work> sping: on hardy, as you are targetting hardy ;)
[16:11] <\sh> motu-release people: 11th april will wine 0.9.59 released..10th april is finalfreeze ... is it ok to upload wine after the 10th?
[16:12] <sping> sistpoty|work: good point
[16:16] <slangasek> ScottK: oh, new package, hmm, dunno then.
[16:16] <ScottK> Yeah.  Thought so.
[16:26] <\sh> slangasek: what I need to do to request a change for PAS for a special package? let's say add lpia for wine
[16:27] <slangasek> \sh: use the contact information printed at the top of the P-a-s file
[16:27] <\sh> slangasek: and then discuss it...i guess
[16:30] <Laney> Where should I start trying to debug/fix this? "** (process:24341): WARNING **: Unable to register service: Connection ":1.50" is not allowed to own the service "com.intel.ppmd" due to security policies in the configuration file"
[16:37] <pochu> hi jdong, any chances you can comment on bug 204928? thanks
[16:37] <ubotu> Launchpad bug 204928 in amule "[FeatureFreeze Exception] New aMule 2.2.0 pre-release snapshot and build with uPnP " [Undecided,Incomplete] https://launchpad.net/bugs/204928
[16:43] <bddebian> Heya gang
[16:43] <ScottK> pochu: stani released today, so it's your turn now.
[16:45] <sistpoty|work> hi bddebian
[16:46] <emgent> heya gang :)
[16:46] <bddebian> Heya sistpoty|work
[16:46] <sistpoty|work> hi emgent
[16:47] <bddebian> Hi emgent
[17:25]  * sistpoty|work heads home
[17:25] <sistpoty|work> cya
[18:42] <LaserJock> umm, so if a package doesn't use any patch system, doesn't it have to manually apply patches in debian/rules?
[18:42] <RainCT> ??
[18:43] <LaserJock> a package has no patch system like dpatch/quilt
[18:43] <LaserJock> it must manually apply patches in debian/rules, right?
[18:44] <RainCT> LaserJock: I've always seen the changes being applied directly if a package (from Debian) has no patch system (or in some cases a patch system being added, like when it's a CDBS package)
[18:44] <RainCT> LaserJock: bug I guess that would be an option too :)
[18:45] <LaserJock> well, there is a patches/ directory
[18:45] <LaserJock> with a 3.9MB patch in it
[18:45] <LaserJock> but I don't think it's even being used
[18:45] <RainCT> LaserJock: heh. Perhaps there's a commented line for it in debian/rules or something?
[18:46] <LaserJock> nope
[18:46] <LaserJock> bu there is a README in patches/
[18:46] <ScottK> LaserJock: I've seem that done before.
[18:46] <LaserJock> says it can be applied using patch
[18:46] <ScottK> It called patch directly IIRC.
[18:46] <LaserJock> but it's not doing it
[18:46] <ScottK> Yes.
[18:46] <LaserJock> so it's just sitting there I guess
[18:47] <geser> LaserJock: have you checked if the patch is already applied?
[18:47] <LaserJock> oh, good question
[18:47] <geser> and only for documentation purposes in debian/patches?
[18:47] <mario_limonciell> LaserJock, its possible that it's an unused patch currently too
[18:47] <mario_limonciell> that was deactivated at some point for some undoumented reason
[18:47] <mario_limonciell> or hopefully documented in debian/changelog
[18:50] <LaserJock> I think it was included upstream
[18:50] <LaserJock> and now it's just a dead patch
[18:54] <LaserJock> it's almost entirely autotools cruft
[19:00] <adinc> buttterz: hi, any changes?
[19:02] <adinc> to the truecrypt package
[19:12] <kiko> hello hello
[19:12] <kiko> anyone seen cody around?
[19:13] <ScottK> YokoZar: Thought you might be interested in this http://vince-debian.blogspot.com/2008/03/flashing-sony-dvd-burner.html
[19:14] <YokoZar> ScottK: weird
[19:42] <james_w> Hi all, just a reminder that there is a MOTU School session on FTBFS (Fails to build from source) in 20 minutes in #ubuntu-classroom
[19:42] <ScottK> Someone who cares about chess might want to look at filing an FFe for getting pychess updated from 0.8 beta to the final release.
[20:00] <james_w> FTBFS session starting now in #ubuntu-classroom.
[20:23] <adinc> buttterz: ping!
[20:36] <mok0> Fujitsu: ping
[20:39] <adinc> is someone here who maintains the kernel package for hardy?
[20:39] <LaserJock> most likely not in here
[20:39] <RainCT> adinc: try in #ubuntu-devel
[20:39] <LaserJock>  the #ubuntu-kernel channel would be the place
[20:39] <slangasek> or #ubuntu-kernel...
[20:39] <adinc> RainCT: ok thank you
[20:39] <adinc> so many ubuntu channels ;)
[20:39] <RainCT> true ^^
[20:40] <adinc> anyone here who makes use of a iwl3945 driver for a intel wireless device?
[20:40] <slangasek> yes
[20:40] <adinc> i'm new to ubuntu and i need to say: very good
[20:40] <adinc> slangasek: do you use it with hardy and the kernel package which comes with it?
[20:40] <slangasek> is this about one of the 5 open iwl3945 bugs that are currently being worked on? :)
[20:41] <adinc> slangasek: i'm sure it is. i've seen two bug reports filed which describe the problem i see with iwl3945 module
[20:41] <slangasek> adinc: yes; presumably you have a bug with it though, I can probably help you better if you tell me what your issue is rather than asking me what I'm using :)
[20:41] <adinc> slangasek: right, the driver can be loaded without problems into the kernel
[20:42] <adinc> when the device then is configured, like with iwconfig wlan0 essid MYNET the module makes log that the microcode has an error
[20:42] <adinc> i'm looking desperatly for a solution without compiling a new kernel myself
[20:43] <slangasek> and you saw an existing bug report about this issue? what was the bug number?
[20:43] <adinc> an launchpad 185470
[20:43] <ubotu> Launchpad bug 185470 in linux "iwl3945 not functioning : microcode error" [Unknown,In progress] https://launchpad.net/bugs/185470
[20:43] <slangasek> ok, well, that's not a bug I'm familiarwith, and it's not one that I experience on my version of the chipset
[20:43] <adinc> i'm new to ubuntu but people reported that the old module ipw3945 does work
[20:44] <adinc> slangasek: so whats the solution then?
[20:44] <adinc> i've used new ucodes from intelwireless side and made md5 hash over it, which was the same
[20:45] <adinc> the actuall error which occurs is iwl3945 not functioning : microcode error
[20:46] <slangasek> hardy doesn't support the ipw3945 module; your choices are a) stick with an earlier Ubuntu release until this is resolved (which may or may not occur before the release of Ubuntu 8.04), b) compile your own driver, c) press the issue in the bug report, making yourself available through Launchpad to the kernel developers for testing any fixes
[20:47] <adinc> slangasek: how can i make myself available, i made a comment to the bug
[20:48] <adinc> slangasek: if i wanted to compile it myself, i would need to right compiler, sources of the same kernel etc. since this is a notebook i was trying to avoid this
[20:48] <slangasek> adinc: a follow-up comment saying "I'm happy to test any proposed fixes"? :)
[20:48] <adinc> slangasek: ok, i can do this
[20:48] <slangasek> yes, I didn't say that compiling your own driver was a *good* option... :)
[20:48] <ScottK> adinc: Idling in #ubuntu-kernel doesn't hurt either.
[20:48] <slangasek> right
[20:49] <adinc> ScottK: ok, so many ubuntu channels...
[20:49] <ScottK> Yep.
[20:49] <jpatrick> adinc: you have no idea mate
[20:50] <adinc> jpatrick: how you mean?
[20:50] <jpatrick> adinc: I must be sitting in ~23 ubuntu channels right now
[20:51] <adinc> ;)
[20:51] <adinc> jpatrick: but i suppose you do a good job helping people. i'm sure many people are thankfull for this
[20:54] <jpatrick> adinc: ubuntu ops team, at your service
[20:54] <adinc> jpatrick: i'm sorry for my english, but i didin't understand ;)
[21:05] <tbf> slangasek, ScottK: anything i can do for helping the FFe?
[21:05] <tbf> /the/my/
[21:05] <ScottK> tbf: I've not had time to look at it yet, but assuming it's all filled out, then no.
[21:49] <LaserJock> hmm, we should get upload karma depending on the length of our changelogs :-)
[21:50] <mok0> LaserJock: heh
[21:50] <sebner> LaserJock: that would help to have a better documented changelog :P
[21:51] <RainCT> good idea, I like writting long changelog entries :P
[21:51] <DktrKranz> sebner, argh. I asked you to reduce URL lenght :)
[21:51] <LaserJock>  * I
[21:51] <LaserJock>    - changed one thing
[21:52] <LaserJock>    - changed another
[21:52] <RainCT> hahah
[21:52] <DktrKranz> * I
[21:52] <DktrKranz> * changed
[21:52] <DktrKranz> more karma
[21:52] <LaserJock> what about ascii art changelog entries? :-)
[21:52] <DktrKranz> which app does it?
[21:52] <sebner> DktrKranz: hm?
[21:52] <DktrKranz> let's add them to build-essential
[21:53] <lucas> actually, I would rock to have changelog entries such as "did that, because in Ubuntu, we do XXX"
[21:53] <lucas> it's often difficult to understand why some change was made, from the debian maintainer POV
[21:53] <lucas> it would probably help to get changes merged back in debian
[21:54] <sebner> DktrKranz: what URL ?
[21:54] <DktrKranz> sebner, a merge managed some days ago, I asked you to limit to 80 chars
[21:55] <sebner> DktrKranz: wasn't that sispoty?
[21:55] <RainCT> heh
[21:55] <DktrKranz> lucas, good point, but I think good rationales in bug reports could help more, but that would improve patches.ubuntu.com usage
[21:56] <DktrKranz> sebner, dunno, I'm sure I asked you something similar
[21:56] <sebner> DktrKranz: can you tell me the package name?
[21:56] <DktrKranz> hard to remember :)
[21:57] <sebner> hrh
[21:57] <sebner> I haven't done many merges recently
[21:57] <sebner> especially none that you approved
[21:57] <sebner> Wired
[21:58] <DktrKranz> sebner, opencv
[21:58] <sebner> that was weeks ago xD
[21:59] <sebner> DktrKranz: you are wired
[21:59] <sebner> bug #201185
[21:59] <ubotu> Launchpad bug 201185 in opencv "Merge opencv 1.0.0-4 from Debian(Unstable)" [Wishlist,Fix released] https://launchpad.net/bugs/201185
[22:00] <sebner> nothing to complain I suppose :P
[22:00] <DktrKranz> no, just a looooong url you avoided
[22:01] <sebner> To a perfect line not more than 80chars :P
[22:01] <ScottK> Actually less than 80.
[22:02] <sebner> ScottK: I said *not more* than 80 ^^
[22:06] <DktrKranz> see you tomorrow :)
[22:06] <sebner> DktrKranz: ciao
[22:07] <Fujitsu> mok0: You rang?
[22:07] <mok0> Fujitsu: yes
[22:07] <mok0> Fujitsu: I have a question concerning petsc that you merged the other day
[22:08] <mok0> Fujitsu: I am looking at illuminator that depends on it
[22:08] <Fujitsu> mok0: OK, I remember it.
[22:09] <mok0> I tried to merge illuminator 0.11.0, but it fails to build on hardy. It builds fine on sid
[22:09] <Fujitsu> mok0: What's the error?
[22:09] <mok0> Fujitsu: the build fails in the configure script:
[22:10] <mok0> Fujitsu: "configure: error: "PETSc libraries not found""
[22:10] <geser> mok0: check how it checks for them and why it fails
[22:11] <mok0> Fujitsu: after "checking for PetscPrintf in -lpetsc... no"
[22:11] <Fujitsu> My changes aren't exactly huge.
[22:11] <mok0> Fujitsu: there's a newer version in unstable now
[22:11] <Fujitsu> I disabled spooles support, and made it build by dropping an LDFLAG that should be ignored anyway, but...
[22:12] <Fujitsu> Argh, 3 new versions already!?
[22:12] <mok0> My sid sbuilder loads petsc-dev version  2.3.3-9
[22:12] <mok0> ... and I am not sure if that is related to the problem
[22:12] <mok0> Fujitsu: yes, arrrghh
[22:12] <Fujitsu> Can you try to build it in sid with petsc-dev 2.3.3-6?
[22:13] <mok0> How would I do that?
[22:13] <mok0> Specify the build-depends?
[22:13] <Fujitsu> pbuilder login, install the build-deps, then manually install the old petsc over the top, perhaps.
[22:13] <mok0> Fujitsu: sure
[22:40] <synic> what are the package naming conventions for beta packages?
[22:40] <synic> something like exaile_0.2.12+beta1~gutsyppa1 ?
[22:40] <Fujitsu> synic: ~beta1
[22:41] <ScottK> synic: ~beta1~gutsy~ppa1
[22:41] <synic> ok
[22:41] <Fujitsu> And you'll want a hyphen in there somewhere.
[22:41] <ScottK> Right.
[22:41] <Fujitsu> 0.2.12~beta1-0ubuntu1~ppa1~gutsy1
[22:41] <ScottK> Yeah.  What he said.
[22:41] <synic> heh
[22:41] <synic> wow.
[22:42] <synic> is there a document describing this?
[22:42] <Fujitsu> Is there any other way to do it?
[22:42] <RainCT> heh
[22:42] <RainCT> nice version number :)
[22:43] <RainCT> Fujitsu: uhm.. 0.2.12~beta1-0~gutsy1 perhaps? but its better as you said it
[22:44] <sebner> gn8 folks
[22:45] <RainCT> Fujitsu: dpkg --compare-versions 0.2.12~beta1-0~gutsy1 lt 0.2.12~beta1-0ubuntu1~ppa1~hardy1; echo $?
[22:45] <RainCT> 0
[22:45] <RainCT> well I'm off.. good night
[22:45] <Fujitsu> Night RainCT.
[22:53] <LaserJock> does it matter what order you put bzr options?
[22:54] <LaserJock> I'm trying to do a lightweight checkout but it doesn't seem so light
[22:54] <LaserJock> I assume bzr checkout --lightweight is the proper way to do it
[22:55] <james_w> LaserJock: yep
[22:56] <LaserJock> :(
[22:56] <LaserJock> it's gonna take me like an hour to do this checkout
[22:56] <LaserJock> all I want is a little directory :(
[23:05] <vixinu> hey
[23:58] <ScottK2> LaserJock: That is quick for bzr.