[12:16] <netzmeister> slomo are you there?
[12:29] <LaserJock> netzmeister: how is the packaging coming?
[12:30] <netzmeister> it looks good..
[12:30] <netzmeister> http://www.ubuntuusers.de/paste/317/
[12:30] <netzmeister> thats the result of lintian..
[12:31] <netzmeister> i have no idea..
[12:31] <netzmeister> :(
[12:32] <LaserJock> netzmeister: well the first couple are because it seems you don't have a manpage for each binary you're installing
[12:33] <LaserJock> netzmeister: and COPYING shouldn't be installed
[12:33] <netzmeister> how?
[12:33] <raphink> netzmeister: the best way to provide manpages for your package is using docbook
[12:34] <LaserJock> hi raphink
[12:34] <raphink> hi LaserJock <><
[12:34] <netzmeister> raphink:  okay, i used manedit
[12:34] <netzmeister> i've deleted the file COPYING but then the build process stopps with an error
[12:34] <raphink> got my repo up today LaserJock :) all automatized in bash :) look : http://packages.raphink.net
[12:34] <raphink> netzmeister: don't delete anything from the source
[12:34] <netzmeister> k
[12:34] <raphink> netzmeister: the only changes should bring to the dir are in debian/
[12:35] <raphink> don't add or remove anything but this dir
[12:35] <raphink> if you need to change things in the sources, you have to use patches
[12:35] <raphink> LaserJock: well css are not from me as you can guess ;)
[12:35] <netzmeister> raphink:  okay.
[12:36] <netzmeister> but i don't know what i could do, to solve the last errors..
[12:36] <LaserJock> raphink: am I going to have to report you to canonical ;-)
[12:36] <netzmeister> (manpage are no problems..)
[12:36] <raphink> LaserJock: why?
[12:36] <raphink> LaserJock: because of the logo ?
[12:37] <ajmitch> raphink: you doing naughty things?
[12:37] <LaserJock> raphink: copyrighted material ;-)
[12:37] <raphink> ajmitch: just having a repo
[12:37] <ajmitch> oh dear
[12:37] <raphink> LaserJock: I didn't modify the logo and it's used all around on the internet
[12:38] <LaserJock> raphink: np, I'm just to used to the doc team
[12:38] <raphink> LaserJock: no but if there's a good reason for you to say that, I'd be happy to know :)
[12:38] <raphink> ajmitch: what?
[12:40] <netzmeister> wb slomo
[12:40] <netzmeister> ups, auto reconnect. :)
[12:40] <raphink> hehe
[12:40] <netzmeister> *g*
[12:41] <ajmitch> raphink: the black helicopters should be overhead shortly
[12:41] <raphink> haha
[12:41] <raphink> ajmitch: no really tell me what part is wrong?
[12:41] <raphink> using the logo, using the revu css ?
[12:42] <ajmitch> raphink: even worse, you'll have this to deal with: http://ploum.frimouvy.org/images/cheerleader.png
[12:42] <raphink> llllllllloooooool
[12:42] <raphink> hehe
[12:42] <netzmeister> "W: codeblocks: non-dev-pkg-with-shlib-symlink usr/lib/libwxscintilla.so.0.0.1 usr/lib/libwxscintilla.so" :(
[12:42] <netzmeister> i have no idea. am i a b00n?
[12:42] <hub> netzmeister: the .so needs to go in the -dev pacakge
[12:43] <netzmeister> aha
[12:43] <hub> netzmeister: because it is only used when link with -l
[12:43] <netzmeister> o_O
[12:54] <netzmeister> "no-shlibs-control-file usr/lib/libcodeblocks.so.0.0.1" this error is past..
[12:54] <netzmeister> :)
[01:01] <netzmeister> http://www.ubuntuusers.de/paste/318/
[01:01] <netzmeister> 3 errors...
[01:02] <netzmeister> hub: i think my english is not good enough to understand the problem with the -dev package
[01:21] <netzmeister> okay, i'm out. cu later
[01:45] <marcin`> hi MOTU's again
[01:46] <marcin`> need some info how to create patches to orig sources that I could apply with package?
[01:46] <marcin`> could some point me to some docs about it?
[01:49] <crimsun> marcin`: you can either use the transcript of ajmitch's motu school lesson as a guide ( I think sladen made a good summary; check the motu mailing list archives ), or you can use the Debian NMG, or you can use what LaserJock has done thus far with the packaging guide
[01:51] <sladen> marcin`: http://www.paul.sladen.org/ubuntu/tutorial/01/  in fact I even checked it yesterday for something
[01:51] <ajmitch> crimsun: I didn't really cover that part
[01:52] <sladen> I might do a terse writeup/braindump/howto
[01:52] <ajmitch> \sh explained a bit previous to my ramble, on how to do patching
[01:52] <ajmitch> crimsun: btw I see that fixes have landed in alsa CVS for acer laptops like mine
[01:53] <sladen> ajmitch: would would be really useful is a ''how to add debian/patches/ to a package that doesn't have it
[01:53] <ajmitch> sladen: I probably have the logs of it somewhere
[01:53] <sladen> ajmitch: and a 2 minute guide to working with quilt (since even I gave up after 3hours of faffing)
[01:53] <ajmitch> since that wasn't me explaining it
[02:01] <marcin`> sladen: thanks but this tutorial is nice but unfortunately doesn't answer my question
[02:02] <marcin`> sladen: I know how to create package but don't know how to prepare packages that I could apply to orig sources
[02:03] <marcin`> sladen: so I know how to package - don't know how to prepare package that changes something in orig sources
[02:03] <marcin`> so guys... in MOTU school I see that dpatch is 'bad'
[02:04] <minghua> hello MOTU world
[02:06] <sladen> marcin`: I don't undersrand that;  everyone is telling me off if I don't use delta patches
[02:07] <ajmitch> the context is that it's not nice to add a patch system to an existing debian package, since that can & possibly will greatly annoy the debian maintainer
[02:08] <marcin`> ajmitch: I don't care about debian maintainer because package I create is not in debian yet
[02:08] <marcin`> ajmitch: but I need to patch orig source so.... ? what to do?
[02:08] <ajmitch> then use what you want
[02:09] <ajmitch> if you want to use dpatch on something you're doing yourself, that's fine
[02:09] <marcin`> ajmitch: ok let's say - cdbs...
[02:10] <marcin`> ajmitch: then could you give me url how to prepare patches?
[02:10] <ajmitch> include dpatch.mk, and use dpatch-edit-patch
[02:11] <tseng> if you are using cdbs you can include simple-patchsys
[02:11] <tseng> and put normal diffs in debian/patches
[02:13] <marcin`> I love it...
[02:13] <marcin`> guys - please... URL ?
[02:13] <marcin`> howto?
[02:13] <tseng> i thought I just gave you the howto
[02:13] <marcin`> (I know I know google is my friend)
[02:14] <tseng> apt-get source muine
[02:14] <tseng> learn by example
[02:18] <marcin`> tseng: ok thanks
[02:18] <marcin`> tseng: but just one thing
[02:19] <marcin`> tseng: how you create files in debian/patch ?
[02:19] <tseng> with diff
[02:19] <marcin`> tseng: sorry debian/patches
[02:19] <tseng> diff -ruN sourcetree.old sourcetree.new
[02:19] <tseng> or: cdbs-edit-patch
[02:20] <marcin`> and you need to be in source directory to run this right?
[02:21] <marcin`> anyway I'll try
[02:39] <crimsun> 'night guys (still recovering from stomach flu)
[03:33] <freeflying> siretart: ping
[03:34] <freeflying> raphink: ping
[03:35] <raphink> freeflying: pong
[03:35] <freeflying> raphink: need help again , hehe
[03:35] <raphink> with what?
[03:35] <freeflying> raphink: plz del scim-pinyin on revu
[03:35] <raphink> right
[03:36] <freeflying> raphink: thx, i'd reupload soon
[03:36] <raphink> done
[03:37] <freeflying> raphink: would u mind review it
[03:37] <raphink> hmm not right now
[03:37] <raphink> it's 3:37AM
[03:37] <raphink> so I'm not in a good state to review ;)
[03:37] <raphink> hehe
[03:37] <freeflying> hmm
[03:38] <raphink> ;)
[03:40] <minghua> freeflying: are you trying to upload scim-pinyin 0.5.91 to dapper?
[03:40] <freeflying> minghua: have a try
[03:41] <minghua> freeflying: I would appreciate a notice before your upload then (as the Debian maintainer, not as the fellow Ubuntu member), thanks
[03:43] <freeflying> minghua: work on this , just for the support of skim
[03:43] <KillerKiwi2006> anybody know if the CNR http://www.desktoplinux.com/news/NS7474779842.html rumor is ture?
[03:44] <minghua> freeflying: well, I don't agree with at least the removal of scim-chinese
[03:44] <dolson> KillerKiwi2006: geez, I sure hope not
[03:44] <minghua> freeflying: but as I have said, anybody can upload SCIM stuff in ubuntu, I am just asking for a notice to the Debian maintainer
[03:45] <freeflying> minghua: this due to the languag-pack depend on scim-pinyin
[03:45] <KillerKiwi2006> dolson: my thoughts exactlly
[03:45] <dolson> KillerKiwi2006: I hope someone higher up gives you an answer... I don't like where this is heading if it's true though
[03:46] <minghua> freeflying: 1. we are in feature freeze;  2. scim-pinyin 0.5.0 works just fine with skim without the special skim support part;  3. I don't agree with your style of im-switch support
[03:47] <minghua> freeflying: but I am not going to argue with you about this, you have you right to upload as you want (as long as you can find a sponsor)
[03:47] <minghua> freeflying: I am just asking for a notice, so I know what's going on with my Debian package in Ubuntu
[03:48] <ajmitch> KillerKiwi2006: who knows
[03:48] <freeflying> minghua: we make scim's module register scim to im-switch now ,how about it ?
[03:48] <minghua> freeflying: and if you keep your "we don't need to tell you about anything we do with scim in ubuntu", I am fine with that as well
[03:49] <minghua> freeflying: If you don't want to talk with me about scim, I don't mind.  I just ask for a _notice_.
[03:50] <freeflying> minghua: if you have interesting on those , I will tell you
[03:50] <minghua> freeflying: I have always had interest.  What about answering my mail to ubuntu-devel list?
[03:50] <dolson> KillerKiwi2006: if it was only used for things that aren't legal otherwise, then I would welcome it, but still wouldn't use it. I can't see it replacing synaptic/apt/etc though.. if it does, well, back to debian I go. :)
[03:51] <minghua> and I am busy this week
[03:51] <minghua> so I don't have time for ubuntu stuff
[03:51] <freeflying> minghua: right I can give private mail or mail to ml
[03:53] <ajmitch> dolson: of course it wouldn't replace apt, etc
[03:53] <ajmitch> the rest of the developers would have a fit
[03:53] <dolson> I am in good company then :)
[03:53] <dolson> the more I read about it, the more I think it's a good solution for the codec issues
[03:53] <KillerKiwi2006> Would would be 'better' is if CNR only installed into a cmg like klik.....
[03:54] <Amaranth> There is no way Ubuntu is using CNR
[03:54] <minghua> freeflying: mailing list, please.  thanks
[03:54] <dolson> no? the CEO of Linspire is posting on the Ubuntu forums
[03:54] <Amaranth> there are plans to move to SMART though, from what i've heard
[03:55] <Amaranth> michael robertson is posting to the ubuntu forums?
[03:55] <KillerKiwi2006> yes
[03:55] <Amaranth> i should say hi
[03:55] <KillerKiwi2006> i've seen some of his posts
[03:55] <dolson> no, it's Kevin Carmony
[03:55] <Amaranth> and see if i can get the job he gave to cody over me :P
[03:55] <dolson> Camony I mean
[03:55] <Amaranth> oh, who cares then :P
[03:55] <KillerKiwi2006> Was an interesting read about selling OOS in stores
[03:57] <Amaranth> "Absolutely," Carmony replied. "I've talked to Mark [Shuttleworth]  about it. We both like the idea a great deal. We'd just make a way to apt-get the CNR client for free, then Ubuntu users could choose to simply use apt, OR, for those who want the one-click convenience of CNR, they could try CNR for free for 15 days, and if they like it, pay for the service [$20 per year] .
[03:57] <Amaranth> so if anything it'd be optional
[03:57] <Amaranth> you guys made it sound like it was going to be mandatory
[03:58] <dolson> I did? No I didn't, I said I wouldn't use Ubuntu if it was
[03:58] <KillerKiwi2006> " 	anybody know if the .... rumor is ture?"
[03:59] <ajmitch> KillerKiwi2006: it's ok
[03:59] <dolson> anyhow, I like how he justifies it... "98% of the world will no way take the time to learn how apt-get works" and then goes on to say "he wouldn't put our client in the default distro but would have to be apt from a different location or downloaded and installed separately"
[03:59] <ajmitch> but asking here probably isn't the best place to verify any rumours
[04:00] <dolson> so... you need to learn how to apt in order to get CNR so that you don't have to apt
[04:00] <Amaranth> i wonder if he found out we were working towards a free CNR replacement and offered this to make people give up on the project
[04:00] <dolson> Amaranth: that's what SMART is, right? is there a web presence yet?
[04:01] <ajmitch> KillerKiwi2006: where in NZ, btw?
[04:01] <Amaranth> SMART is an apt replacement
[04:01] <KillerKiwi2006> auckland
[04:02] <dolson> hmm
[04:03] <Amaranth> http://labix.org/smart
[04:03] <ajmitch> Amaranth: so what is this CNR replacement you have?
[04:03] <Amaranth> maybe smart isn't an acronym, looks like i'm just shouting
[04:04] <Amaranth> ajmitch: for breezy we were working on turning g-a-i into that, i guess it already basically died
[04:04] <Amaranth> although it'll get there, bit by bit
[04:05] <Amaranth> dolson: "Canonical Ltd. - Is funding Smart development since September of 2005."
[04:06] <whiprush> I'd rather people just pay linspire the 20 bucks and bother then with support than them breaking their stuff with the forum script-of-the-day I guess.
[04:07] <ajmitch> Amaranth: last I heard the author was working on launchpad
[04:07] <Amaranth> whiprush: hehe, automatix is dead
[04:07] <Amaranth> i killed it
[04:07] <Amaranth> that was a fun day
[04:07] <dolson> how did you kill it? :D
[04:07] <ajmitch> Amaranth: no, plenty of people still love their automatix
[04:08] <dolson> and did you kill EasyUbuntu too?
[04:08] <Amaranth> ajmitch: But no one works on it anymore and it's not promoted.
[04:08] <Amaranth> EasyUbuntu? No, I help with that one. :)
[04:08] <dolson> awesome!
[04:08] <Amaranth> Sort of, I'm there for Python questions and such
[04:09] <dolson> cool. I read lots of bad things about Automatix.. and I didn't like that whole "I can killall zenity if I want to because no one uses it" thing
[04:09] <Amaranth> i killed automatix by making a fake fork called automatix-ng, forcing the author to admit defeat on the name issue, which made him so mad he quit working on it
[04:09] <dolson> lol
[04:09] <KillerKiwi2006> That was when he tried to change the lisence?
[04:09] <Amaranth> basically he got pissed and took him ball and went home
[04:10] <Amaranth> his
[04:10] <Amaranth> KillerKiwi2006: no, that was earlier
[04:10] <dolson> hahaha. that guy was a total jerk.. I couldn't believe the posts he was making
[04:10] <Amaranth> killall zenity, creating a root account, --force-yes on apt
[04:10] <Amaranth> it was scarily broken
[04:11] <dolson> yeah, I read all that. I'm reading your thread now, lol
[04:12] <TheMuso> automatix was a good idea though, but by the sounds of it, was badly coded.
[04:12] <TheMuso> IMO it was a good idea anyway.
[04:12] <KillerKiwi2006> i think easyubuntu was first....
[04:12] <Amaranth> TheMuso: that's why EasyUbuntu is around
[04:12] <Amaranth> it was
[04:12] <Amaranth> automatix was a fork of the original easyubuntu
[04:12] <Amaranth> which died
[04:13] <TheMuso> Right.
[04:13] <Amaranth> nalioth, robotgeek, keyes (original author), and me (sort of) are remaking it in python
[04:13] <ajmitch> all of it leaves a bad taste in my mouth
[04:13] <dolson> and came back stronger
[04:13] <KillerKiwi2006> it looks good
[04:13] <Amaranth> to basically be a sane automatix
[04:13] <dolson> it won't be in dapper, will it?
[04:14] <Amaranth> i don't believe so
[04:14] <dolson> that sucks :(
[04:15] <dolson> haha, I love that admin. "I'll start banning people for no good reason at all!$@#%@%"
[04:21] <dolson> *personal attack removed* -- damn! I always looked forward to arnieboy's childish insults
[04:23] <dolson> what's that KillerKiwi2006?
[04:23] <Amaranth> dolson: I have a copy
[04:23] <dolson> Amaranth: /msg me what he said :D
[04:23] <KillerKiwi2006> http://aluminum.sourmilk.net/reveal/
[04:23] <Amaranth> alerts
[04:23] <Amaranth> man, i must be tired
[04:23] <KillerKiwi2006> shows thumbnails of webpages visted in a timeline
[04:23] <dolson> oh nice
[04:24] <Amaranth> dolson: 'his effort with smeg took him more than a year and its still a bag of wormy bugs.. lol.. all the best with automatix :) Amaranth said to himself : "well since I cant do shit with smeg after everything, lets go and **** someone else's work and hog some limelight."'
[04:24] <dolson> too bad I am using Epiohany now
[04:24] <Amaranth> KillerKiwi2006: it shows thumbnail tooltips on the back and forward buttons too
[04:24] <dolson> Amaranth: lol
[04:25] <KillerKiwi2006> lol true
[04:25] <ajmitch> KillerKiwi2006: so you want to join the MOTUs in making ubuntu a better place? :)
[04:25] <dolson> yeah, you could package up automatix
[04:25] <KillerKiwi2006> :P
[04:25] <Amaranth> eek i'm getting easyubuntu bugs
[04:25] <dolson> with checkinstall
[04:25] <KillerKiwi2006> yup
[04:27] <dolson> Empty cup of Ubuntu ? lol
[04:28] <ajmitch> Amaranth: stop blaming the kiwis
[04:28] <Amaranth> dolson: means banned
[04:29] <dolson> Amaranth: yeah, who got that? Seth?
[04:29] <Amaranth> i guess
[04:31] <dolson> it seems to me that he's still working on automatix.. he's posting in his threads about it, and actually, surprisingly, he admitted that it was a stop-gap measure to counter the absense of.. wait for it... Linspire's CNR
[04:32] <Amaranth> ha
[05:02] <dolson> hmmm, does anyone know of a really simple app like Thoggen but for another format, such as XviD or MPEG?
[05:47] <LaserJock> ajmitch: ping?
[05:48] <ajmitch> LaserJock: yes?
[05:49] <LaserJock> ajmitch: do you use madison-lite?
[05:50] <ajmitch> yes
[05:50] <ajmitch> there's a working config on tiber
[05:50] <ajmitch> iirc /usr/local/bin/update-madison-lite-mirror & the config in /etc
[05:51] <LaserJock> I'm using it but I don't know how to update it
[05:52] <ajmitch> see above..
[05:54] <LaserJock> ok, thanks.
[05:57] <LaserJock> ajmitch: hmm, I'm not an admin, could you run it for me?
[05:57] <minghua> hi LaserJock
[05:57] <ajmitch> it was being run every 12 hours
[05:57] <LaserJock> hi minghua
[05:57] <minghua> LaserJock: any words from plotdrop upstream?
[05:57] <LaserJock> minghua: hmm, about the problem you had?
[05:57] <ajmitch> LaserJock: any reason it needs to be re-run now?
[05:58] <minghua> LaserJock: yeah, about needing libglade >= 2.6
[05:58] <LaserJock> ajmitch: not particularly, I was just comparing some stuff that hit debian pretty recently. If it is being update every 12 hrs it's ok
[05:58] <LaserJock> minghua: hmm, just a sec. let me search my email
[05:58] <minghua> LaserJock: and actually your build-dependency needs to be tightened as well
[05:59] <LaserJock> minghua: yeah? I'm always up for package improvement tips ;-)
[06:00] <LaserJock> minghua: ok, so upstream asked if you were by change compiling with gtk 2.6 but runnint 2.4
[06:01] <minghua> LaserJock: no, I built in a sarge chroot
[06:01] <minghua> LaserJock: it is gtk+ 2.6, but libglade 2.4
[06:01] <minghua> LaserJock: you have Build-Depends: libglade2-dev in debian/control
[06:01] <LaserJock> sarge has gtk2.6?
[06:02] <minghua> LaserJock: in my opinion it should be libglade2-dev (>= ...)
[06:02] <minghua> LaserJock: yes:
[06:02] <minghua> Package: libgtk2.0-0
[06:02] <minghua> Version: 2.6.4-3.1
[06:03] <LaserJock> and libglade is 2.4, hmm.
[06:04] <LaserJock> ok, so is the problem with libglade then
[06:05] <minghua> LaserJock: I don't really insist any change, a claim that plotdrop requires libglade >= 2.6 would be sufficient
[06:05] <minghua> and then I can say it can't be backported to sarge without a patch :-P
[06:06] <minghua> LaserJock: anyway it's not urgent at all, just happens come to mind
[06:06] <LaserJock> well, upstream told me he was interested in the problem
[06:26] <LaserJock> hi Gloubiboulga
[06:26] <Gloubiboulga> hey LaserJock
[06:27] <LaserJock> minghua: I'm going to email plotdrop upstream about your findings and see if he want's to change it to work or not. But I'll get the dep tightened anyway.
[06:28] <LaserJock> minghua: thank's for finding this
[06:28] <minghua> LaserJock: great, thanks
[06:47] <G0SUB> is everybody sleeping?
[06:47] <LaserJock> no exactly
[06:48] <TheMuso> G0SUB: Not here. Tis mid to alte arvo here in Sydney.
[06:48] <G0SUB> heh
[06:48] <G0SUB> do you guys need any help with some packaging or bug fixing?
[06:48] <G0SUB> I want to help
[06:50] <LaserJock> I think we are mostly iin bug fixing mode at this point
[06:50] <G0SUB> yes, I can help in fixing bugs
[06:52] <G0SUB> Gloubiboulga
[06:53] <Gloubiboulga> G0SUB?
[06:53] <G0SUB> Gloubiboulga when you send in debdiffs, why don't you close the bugs in the changelog?
[06:54] <Gloubiboulga> good question
[06:54] <G0SUB> Gloubiboulga you should always do that ... else it gives the uploader more pain
[06:55] <Gloubiboulga> you're certainly right
[06:55] <G0SUB> Gloubiboulga can you share a few bugs with me? it seems you are way too fast in fixing the bugs in malone
[06:55] <G0SUB> :)
[06:56] <Gloubiboulga> G0SUB, I've used http://tiber.tauware.de/~siretart/unmet/dapper-unmet.txt to find bugs to fix
[06:56] <G0SUB> oh, ok
[06:56] <G0SUB> Gloubiboulga thanks :)
[06:57] <Gloubiboulga> G0SUB, np ;)
[06:57] <Gloubiboulga> but browsing malone is also a good way to find some stuff to do
[06:57] <G0SUB> Gloubiboulga yes, I am doing that itself
[06:57] <Gloubiboulga> even if it's only triage, it's usefull
[06:57] <Gloubiboulga> cool :)
[06:58] <G0SUB> working on #31152 now
[06:58] <Gloubiboulga> malone 31152
[06:58] <Ubugtu> malone bug 31152 in gtick "Missing .desktop file" [Normal,Confirmed]  http://launchpad.net/bugs/31152
[06:58] <G0SUB> I will attach a debdiff
[06:58] <Gloubiboulga> there's a lot of missing desktop files...
[06:59] <G0SUB> Gloubiboulga yep, a LOT
[07:02] <TheMuso> Gloubiboulga: Do these packages have bugs regarding the unmet deps?
[07:02] <Gloubiboulga> TheMuso, some of them have bugs
[07:02] <TheMuso> Thanks.
[07:03] <Gloubiboulga> TheMuso, I've started a wab page with status for some of these packages
[07:03] <Gloubiboulga> some just FTBFS
[07:03] <TheMuso> Right.
[07:03] <Gloubiboulga> I could turn it in a wiki page for a collaborative work
[07:03] <Gloubiboulga> :)
[07:04] <TheMuso> Malone search doesn' seem to be working for me.
[07:04] <TheMuso> I enter a keyword, i.e a package name, and it sends me to the general info page about Ubuntu.
[07:05] <Gloubiboulga> I always use https://launchpad.net/distros/ubuntu/+source/<source package>
[07:05] <TheMuso> Ah right.
[07:06] <ajmitch> Gloubiboulga: http://revu.tauware.de/~sistpoty/MoM/wip.py
[07:07] <ajmitch> Gloubiboulga: we don't want to go back to using the wiki for thousands of packages - it gets unbearably slow & messy
[07:07] <Gloubiboulga> ok ajmitch
[07:11] <ajmitch> see you tomorrow
[07:12] <Gloubiboulga> cu ajmitch
[07:42] <dolson> Emmek Hiktory?
[07:43] <G0SUB> dolson ?
[07:43] <dolson> is that your patch, G0SUB?
[07:43] <G0SUB> dolson yes
[07:44] <dolson> it's "Emmet Hikory" ;)
[07:44] <G0SUB> oh, crap
[07:44] <G0SUB> dolson typo
[07:44] <G0SUB> dolson fix the typo and upload to revu please
[07:44] <zakame> hello MOTUs! :D
[07:44] <dolson> ok :)
[07:44] <dolson> hi zakame
[07:45] <G0SUB> zakame :) not a motu yet
[07:45] <G0SUB> dolson thanks :)
[07:45] <G0SUB> dolson are you wokring on something now?
[07:45] <dolson> G0SUB: I'm going to patch that and put it on REVU
[07:45] <G0SUB> dolson fine ...
[07:46] <dolson> you told me to
[07:46] <zakame> heya G0SUB!
[07:46] <G0SUB> dolson can you wait for me to fix the patch and attach it?
[07:47] <dolson> well it's going to be changed if I do the upload anyhow
[07:47] <G0SUB> I see
[07:47] <dolson> do you not have REVU access yet?
[07:47] <G0SUB> doesn't matter ... you go ahead then
[07:47] <G0SUB> dolson no, I haven't applied
[07:47] <dolson> ah, ok
[07:47] <G0SUB> dolson I usually got jpatrick to upload my patches directly
[07:48] <TheMuso> G0SUB: It is not hard to get REVU access.
[07:48] <dolson> you patched an old, non-ubuntu version
[07:48] <TheMuso> And doesn't take long.
[07:49] <G0SUB> dolson non-ubuntu?
[07:49] <dolson> nevermind, there is no ubuntu version. nonetheless, your patch fails on the changelog.. doesn't matter, since I have to change it anyhow
[07:49] <G0SUB> dolson do
[07:50] <TheMuso> Anybody got any ideas as to why a source package FTBFS according to Launchpad, including i386, but I have just managed to successfully build in pbuilder?
[07:51] <TheMuso> https://launchpad.net/distros/ubuntu/+source/supercollider/
[07:52] <dolson> G0SUB: you didn't change the version properly or the distro, just FYI
[07:53] <G0SUB> dolson i mistakenly pulled down the breezy source
[07:53] <dolson> it was still wrong :)
[07:53] <dolson> version shouldn't be -2, but -1ubuntu1
[07:53] <TheMuso> G0SUB: Are you working in a dapper chroot or an installed dapper setup?
[07:54] <dolson> distro should be dapper, not unstable
[07:54] <G0SUB> pbuilder
[07:54] <TheMuso> G0SUB: Yeah, but how did you get the source originally? do you simply have the dapper sources in your sources.list file?
[07:55] <G0SUB> well, I was supposed to be inside the chroot, but did the whole thing outside :)
[07:56] <G0SUB> TheMuso are you a motu?
[07:57] <TheMuso> G0SUB: No.
[07:57] <G0SUB> ok
[07:57] <TheMuso> But I have had a lot of experience in the past 4 years or so packaging software for various distros.
[07:57] <TheMuso> Not saying that I am an expert or anything.
[07:57] <TheMuso> Far from it.
[07:58] <TheMuso> But I have found that having a good directory structure st up for storing source packages and related files can help a lot.
[07:58] <TheMuso> When I found out about dchroot, I set one up straight away. I love it.
[07:59] <TheMuso> Good for having an environment to do work in that if it breaks, doesn't affect your every day work. Even if you are running dapper as an OS.
[07:59] <TheMuso> Thats what I have found anyway.
[08:20] <dolson> wtf
[09:27] <siretart> morning folks
[09:28] <G0SUB> siretart
[09:31] <siretart> G0SUB! :)
[09:34] <Lathiat> return
[09:36] <netzmeister> moin
[09:36] <siretart> hi netzmeister
[09:36] <netzmeister> hi siretart
[09:36] <netzmeister> :)
[09:36] <netzmeister> uhm i'm tired..
[09:36] <siretart> Lathiat: just wanted to tell you that avahi/zeroconf just ROCK. hard! :)
[09:37] <dholbach> good morning
[09:37] <netzmeister> hi dholbach
[09:37] <Lathiat> siretart: thanks :)
[09:38] <freeflying> hey dholbach
[09:38] <dholbach> hey netzmeister, freeflying
[09:38] <siretart> hey dholbach!
[09:38] <dholbach> hey siretart
[09:44] <Kagou> hi dholbach . I hope that i 'v well answered to your needs in https://launchpad.net/distros/ubuntu/+source/blender/+bug/33306
[09:44] <Ubugtu> malone bug 33306 in blender "French translation of blender.desktop" [Normal,Unconfirmed] 
[09:46] <dholbach> Kagou: looking
[09:48] <Kagou> i'm in the process of learning how to package / patch ... and do more than just report a bug
[09:49] <dholbach> Kagou: you made an unnecessary change to the changelog entry before
[09:49] <dholbach> Kagou: i'll remove that bit
[09:49] <Kagou> ok so it's not a obligation to do a "dch -i"
[09:50] <dholbach> no, not at all
[09:50] <Kagou> mmmh opkay
[09:50] <dholbach> it's just you modified the changelog entry before
[09:50] <dholbach>   [ Daniel Holbach ] 
[09:50] <dholbach>   * Fake sync from Sid, UVF permission granted by mdz.
[09:50] <dholbach>   [ VETSEL Patrice ] 
[09:50] <dholbach>   * -
[09:50] <dholbach>  -- VETSEL Patrice <vetsel.patrice@wanadoo.fr>  Wed,  1 Mar 2006 18:25:14 +0100
[09:50] <dholbach> that doesn't make sense
[09:50] <dholbach> as i uploaded 2.41-1ubuntu1 already
[09:50] <Kagou> ok
[09:52] <netzmeister> dholbach:  It looks good.. http://www.ubuntuusers.de/paste/318/
[09:52] <Kagou> just for information, do you know where is seb128 ?!
[09:53] <dholbach> not online yet
[09:53] <dholbach> netzmeister: still some stuff to fix
[09:53] <dholbach> netzmeister: but keep up the good work
[09:57] <siretart> dholbach: so we are allowed to do emergency 'fake' syncs?
[09:57] <dholbach> absolutely
[09:57] <dholbach> do a build1 please
[09:57] <siretart> ok
[09:57] <siretart> in breezy I was told not to do this. but ok
[09:57] <zakame> hi MOTUs!
[09:57] <dholbach> Kagou: seb128 just arrived
[09:58] <siretart> hi zakame
[09:58] <dholbach> siretart: this is a different situation
[09:58] <siretart> hi seb128! :)
[09:58] <zakame> hello siretart
[09:58] <siretart> dholbach: yes, I understand
[09:59] <Kagou> roo
[09:59] <Kagou> thnx dholbach
[09:59] <zakame> what's with the 'fake' syncs?
[10:11] <netzmeister> dholbach:  Thx.. but i think that this problem "non-dev-pkg-with-shlib-symlink usr/lib/libwxscintilla.so.0.0.1 usr/lib/libwxscintilla.so" is atm to heavy for me..
[10:11] <zakame> netzmeister: that's a lintian error
[10:11] <netzmeister> yes
[10:12] <netzmeister> zakame:  but i don't know how to fix it..
[10:12] <dholbach> netzmeister: i'd reccommend to get started with fixing minor bugs
[10:12] <dholbach> netzmeister: there you have a look at a lot of other packages - that's easier to start with
[10:12] <zakame> netzmeister: you probably need to read the libpkg-guide then :/ but I concur with dholbach
[10:13] <dholbach> apt-cache -i unmet   is a *very good start*
[10:14] <netzmeister> thx men.
[10:14] <netzmeister> i try later..
[10:44] <poningru> hi anyone around?
[10:45] <poningru> wanted to know if it was possible to package mythtv into one package/ meta package
[10:45] <poningru> as in right now inorder to install mythtv a user has to follow a giant howto/faq
[10:46] <poningru> https://wiki.ubuntu.com/InstallMythOnUbuntu
[10:46] <poningru> so is it possible to setup some meta package that will do this for them?
[10:47] <poningru> creation of some sort of guided walk through or something
[11:10] <TheMuso> WOuld the screen saver overriding the display of an app like xawtv be considered a bug? This never occurred in Breezy.
[11:15] <dolson> TheMuso: that's an issue with gnome-screensaver.. it's not limited to xawtv, it's limited to <insert almost any app or game here>
[11:19] <TheMuso> dolson: Thanks. I haven't been following that thread, as normally it wouldn't bother me. :)
[11:20] <dolson> TheMuso: I hope it's fixed before dapper ships :\ either that or reverted back to xscreensaver until gnome-screensaver is more useful.. but I have no say in the matter, so who knows
[11:21] <dholbach> it might help, if upstream got bug reports for the issues
[11:21] <TheMuso> Yeah. I don't mind really. Was just using xawtv and noticed that happening.
[11:25] <kelmo_lap> siretart, hi, perhaps i should continue working on wpa_supplicant now, before impatience sets in ; )
[11:27] <siretart> kelmo_lap: ah, hi Kel! I didn't know that you irc in this channel as well :)
[11:27] <kelmo_lap> siretart, well, i don't usually ; ) was doing some searching tonight
[11:28] <siretart> ah, I see :)
[11:29] <kelmo_lap> anyhow, i've hit a small bug in upstream, wpa_cli is doing strange things, so i'll do my best to write the best pre-up possible and get it commited
[11:40] <nomed> hi all
[11:40] <nomed> a question ...
[11:41] <nomed> if i attach a patch in launchpad should i change the status to "fix committed" ?
[11:43] <G0SUB> nomed no
[11:43] <nomed> k thanks
[11:43] <G0SUB> nomed only a MOTU will do it when he uploads the fix
[11:43] <nomed> fix commited is something that should be changed by the maint true ?
[11:43] <nomed> k
[11:44] <dholbach> nomed: "Fix committed" is fine
[11:44] <dholbach> or well
[11:44] <dholbach> nomed: be sure to assign it to 'motureviewers'
[11:44] <dholbach> nomed: G0SUB is right - the guy who will upload it will set Fix committed
[11:45] <dholbach> it's PENDINGUPLOAD
[11:45] <G0SUB> oh
[11:45] <dholbach> nomed: so "Unconfirmed" is probably fine
[11:45] <G0SUB> dholbach you scared me :)
[11:46] <siretart> kelmo_lap: I'm not sure if we really need to use wpa_cli at all
[11:46] <nomed> dholbach, ok
[11:46] <kelmo_lap> siretart, oh? what did you have in mind?
[11:46] <siretart> kelmo_lap: I'd rather generate a wpasupplicant config in ip-up.d, and start wpasupplicant just with that. on shutting down the interface, it gets removed
[11:47] <siretart> kelmo_lap: for which part do we need wpa_cli?
[11:47] <kelmo_lap> siretart, all of the runtime configuration
[11:47] <kelmo_lap> ssid proto key_mgmt pairwise etc etc
[11:48] <kelmo_lap> preauth
[11:48] <kelmo_lap> ap_scan
[11:48] <kelmo_lap> interface
[11:48] <siretart> kelmo_lap: err, right, but ifupdown doesn't handle runtime configuration anyway. it is just for bringing up and shutting down the interface only
[11:49] <siretart> kelmo_lap: If I'd want runtime configuration of interfaces, I'd use NetworkManager
[11:49] <kelmo_lap> siretart, bridge-utils, wireless-tools, they do not require X-conf tool to manage multiple devices with different configurations
[11:49] <kelmo_lap> and wpa i believe should be handled similarly
[11:51] <siretart> kelmo_lap: yes, I tend to agree, but I miss the point where ifupdown supports the user in any way with interface runtime configuration
[11:52] <kelmo_lap> siretart, you saw my (extremely simplified) example of an interfaces stanza that set interface parems required to use wpa via wpa_supplicant
[11:53] <kelmo_lap> in that the example the configuration file was provided
[11:53] <kelmo_lap> but that started me thinking
[11:53] <kelmo_lap> that all of the configuration options can be given to the interface via wpa_cli, without any configuration file at all
[11:54] <siretart> kelmo_lap: I didn't make too good experiences with wpa_cli
[11:55] <kelmo_lap> siretart, i think i have a decent handle on it now
[11:55] <kelmo_lap> lets see ; )
[11:55] <siretart> kelmo_lap: the scripts you mailed my just terminate the wpa_supplicant daemon. this can be handled via unix signals and pid files as well
[11:55] <siretart> kelmo_lap: so I don't see the necessity for using wpa_cli in ifupdown scripts at all.
[11:57] <siretart> kelmo_lap: and I don't think that ALL configuration options can be given via wpa_cli. what about options like ap_scan, and ctrl_interface and so on?
[11:58] <kelmo_lap> siretart, please give me the oppurtunity to finish polishing them up, so that i may explain with code, not hand waving
[11:58] <kelmo_lap> siretart, and yes, ctrl_interface and ap_scan can be given via wpa_cli
[11:59] <siretart> kelmo_lap: interesting. I'm looking very forward at looking at your proposal
[12:01] <kelmo_lap> siretart, it is indeed something experimental, and i've yet to prove it will completely work in reality, so you are quite justified to question it ; )
[12:02] <siretart> :)
[12:37] <kelmo> siretart: i would say it is basically working now
[12:38] <siretart> kelmo: cool :)
[12:39] <kelmo> siretart: i will show you what i have so far, so that we are in agreement before i spend much time bugfixing, adding all (feasable) features supported by wpa-supplicant and documenting
[12:39] <siretart> kelmo: sounds sane. where can I look at it?
[12:41] <kelmo> siretart: hehe, hang on man. i need to refresh my session, and grab a drink ; )
[12:48] <kelmo_lap> re
[12:53] <kelmo_lap> siretart, some code plus an interfaces stanza: http://rafb.net/paste/results/fVET8449.html
[12:53] <kelmo_lap> simple wpa rsn configuration, with psk
[12:54] <kelmo_lap> where, wpa-conf determines whether or not to use any setting defined in interfaces
[12:54] <kelmo_lap> whch may or mat not be desirable
[12:55] <kelmo_lap> but the imprtan thing is that just about *any* network can be supplied *after* running wpa_supplicant without a configuration file
[12:55] <kelmo_lap> important*
[12:56] <kelmo_lap> extra crap can sanitize user input (like use of caps, driver type to an extent)
[12:57] <kelmo_lap> crap being shell code ; )
[01:01] <kelmo_lap> could even allow a new network to be defined on top of an existing wpa_supplicant conf, thus overriding some settings, but i've not had enough time to play around with that yet
[01:04] <siretart> kelmo_lap: looks interesting. and I get a very vague idea why you object in creating a wpasupplicant configfile on the fly
[01:05] <siretart> kelmo_lap: I wonder if we can get along with that..
[01:06] <siretart> kelmo_lap: one thing: in the case of multiple interfaces: how does wpa_cli know to which wpasupplicant daemon it should connect?
[01:06] <kelmo_lap> $WPACLI -i $IFACE
[01:06] <siretart> ah. I see
[01:06] <kelmo_lap> wpa_cli -i eth1
[01:06] <marcin`> hi MOTU's
[01:06] <siretart> ah, and now I get the sanity check in line 18-20
[01:07] <marcin`> could someone review my emacs-* packages in REVU?
[01:07] <kelmo_lap> yes, thtis also the post-down code
[01:07] <kelmo_lap> that is*
[01:07] <siretart> right
[01:07] <siretart> so this works for you without any configuration file at all?!
[01:08] <kelmo_lap> yes
[01:08] <kelmo_lap> no .conf required
[01:08] <siretart> looks quite promising
[01:08] <siretart> what happens if a /etc/wpa_supplicant.conf is in the way? does it get ignored?
[01:08] <kelmo_lap> okay:
[01:09] <kelmo_lap> wpa-conf
[01:09] <kelmo_lap> if that is set to none
[01:09] <kelmo_lap> then all stuff must be defined in interfaces stanza
[01:09] <kelmo_lap> if it is set to, /etc/wpa_supplicant.conf
[01:09] <kelmo_lap> and that file exists
[01:10] <kelmo_lap> and is larger than 0kb
[01:10] <kelmo_lap> then we use that, and ignore anything defined in interfaces
[01:10] <kelmo_lap> apart from wpa-driver
[01:10] <kelmo_lap> which is mandatory
[01:11] <kelmo_lap> this is just like setting a wep key via a interfaces stanza
[01:11] <kelmo_lap> wpa_supplicant is often smart enough to not warrant some settings
[01:11] <siretart> hm. I see
[01:11] <kelmo_lap> most configs will require just ssid, driver + psk
[01:12] <siretart> my config requires an identity, and a password
[01:12] <kelmo_lap> yes
[01:12] <kelmo_lap> you can see i added them, but commented out for now
[01:12] <siretart> my other config requires a certificate, (but I count that as more complex setup)
[01:12] <kelmo_lap> well, these things can all be tested
[01:13] <kelmo_lap> i am sure even more advanced setups can be catered for
[01:13] <siretart> can we assume wpa-conf set to 'none' by default?
[01:13] <kelmo_lap> hmm
[01:13] <siretart> I'd like to minimize the required options in /e/n/i
[01:13] <kelmo_lap> okay, sec. let me think about a compromise
[01:14] <siretart> right. I'm talking about sane defaults only
[01:15] <kelmo_lap> this is about flexibility, not minimisation, at least from my POV
[01:15] <kelmo_lap> but you raise a good point
[01:15] <kelmo_lap> it *should* be handled differently
[01:16] <kelmo_lap> mm
[01:17] <kelmo_lap> i do honestly believe i have set a sane tunable though
[01:17] <kelmo_lap> either you have a .conf file or not ; )
[01:18] <siretart> yes
[01:18] <siretart> I'm thinking about upgrade paths
[01:18] <siretart> IIUC, you suggest that in future, we don't supply a /etc/wpa_supplicant.conf anymore by default
[01:18] <kelmo_lap> that would definately be possible
[01:19] <kelmo_lap> and cleaner too
[01:19] <siretart> but I expect most (if not all) users to have modified it, so dpkg detects admin local changes, and preserves it
[01:19] <siretart> in this use case, we have to think about what is expected to happen.
[01:20] <siretart> kelmo_lap: I like your scripts. would you like to import it in our experimental branch?
[01:21] <kelmo_lap> siretart, yep, i will do so some time soon
[01:21] <kelmo_lap> first i'd like to add as many wpa_cli variables may brain can handle for one night ; )
[01:22] <siretart> :)
[01:22] <kelmo_lap> siretart, so any suggested changes from your quick glance?
[01:23] <siretart> kelmo_lap: apart from the issue with /etc/wpa_supplicant.conf, none here (yet) :)
[01:23] <kelmo_lap> okay, will think about that
[01:24] <kelmo_lap> but i'd like to be able to supply a configuration file
[01:24] <siretart> kelmo_lap: How about dropping line 26 and 27?
[01:24] <kelmo_lap> err
[01:24] <kelmo_lap> they are two very important lines, imho
[01:25] <siretart> I'm thinking about what should happen if the admin does not suppliy a wpa-conf line
[01:25] <siretart> err, not dropping
[01:25] <siretart> argl. /me tired
[01:25] <siretart> I meant this branch should be executed if the admin did not specify a wpa-conf line
[01:26] <kelmo_lap> yes
[01:26] <kelmo_lap> indeed
[01:26] <siretart> this means changing it to an else, not dropping them completely
[01:26] <kelmo_lap> no, iirc
[01:27] <kelmo_lap> we dont want wpa_supplicant binding the interface when the admin has not asked to use it ; )
[01:28] <siretart> aaah, you need some indication if this should be handled via our hooks at all
[01:28] <siretart> now I get it
[01:28] <kelmo_lap> yes, or else we will execute some unwanted commands
[01:28] <siretart> kelmo_lap: how about renaming it from 'none' to 'auto'?
[01:28] <siretart> kelmo_lap: to indicate that the user uses the 'autoconfiguration' mode
[01:28] <kelmo_lap> that is slightly misleading nomenclature, but i get the idea
[01:29] <kelmo_lap> "auto" usually denotes "nothing else required"
[01:29] <siretart> I see
[01:29] <siretart> how about 'managed' then?
[01:29] <siretart> or is this misleading as well?
[01:29] <kelmo_lap> not at all ; )
[01:30] <siretart> :)
[01:30] <kelmo_lap> like i said, we can sanitise input will small "case" blocks
[01:30] <kelmo_lap> case $IF_WPA_CONF in; none|managed) . . .
[01:32] <siretart> right
[01:33] <kelmo_lap> same for case sensitive material
[01:33] <kelmo_lap> like RSN, WPA-PSK
[01:33] <kelmo_lap> we can allow rsn, wpa2 etc . .
[01:35] <siretart> lets check it into svn and play with it a bit. :)
[01:35] <siretart> kelmo_lap: btw, have you seen the request for compiling wpa_supplicant with madwifi-ng headers?
[01:36] <kelmo_lap> that is obsurd, i am maintainer of madwifi in debian
[01:36] <kelmo_lap> along with Loic
[01:36] <kelmo_lap> and am also upstream developer/supporter of madwifi
[01:37] <kelmo_lap> when madwifi-ng is ready for common use, it will be advertised ; )
[01:37] <siretart> I'm forwarding Svens patch to our list
[01:37] <siretart> kelmo_lap: but madwifi-dev is in non-free
[01:37] <kelmo_lap> siretart, i never intended to use madwifi-dev
[01:38] <kelmo_lap> what does that have to do with anything?
[01:38] <siretart> thats debian bug #354388
[01:38] <Ubugtu> debian bug 354388 in wpasupplicant "please recompile with madwifi-dev" [Wishlist,Open]  http://bugs.debian.org/354388
[01:39] <kelmo_lap> yes, that situation is sad
[01:40] <kelmo_lap> but unavoidable
[01:40] <siretart> hmm. his patch is too big for the mailing list :/ it is stuck in the moderation queue
[01:41] <kelmo_lap> when madwifi-ng is stable, i'll prepare and submit the dpatch for wpasupplicant
[01:41] <kelmo_lap> that is no problem
[01:41] <kelmo_lap> but first we (madwifi) would like to close a few outstanding issues, and not to forget the imminent name change (madwifi-ng => madwifi)
[01:42] <siretart> kelmo_lap: sven already prepared a dpatch, I just forwarded it to the bts
[01:42] <kelmo_lap> sure, but what happens when madwifi-ng decides to patch one of the files included in the dpatch (like just last wek)
[01:43] <kelmo_lap> week*
[01:43] <janimo> ping nomed, Gloubiboulga
[01:43] <kelmo_lap> madwifi-ng is volatile ; )
[01:43] <Gloubiboulga> hi janimo
[01:43] <nomed> janimo, pong
[01:43] <janimo> hi Gauvain
[01:43] <janimo> hi Daniele
[01:44] <janimo> Gauvain, can you please add the current dapper patch to battery?
[01:44] <janimo> or is it already there?
[01:44] <kelmo_lap> hi fella's, apologies for flooding the #chan ; )
[01:44] <janimo> I remember commiting that to alioth
[01:44] <Gloubiboulga> the patch ?
[01:44] <janimo> it's just that it doesn't detect when on battery
[01:44] <janimo> always says online
[01:45] <janimo> I patched libacpi in there a while ago
[01:45] <Gloubiboulga> I think the patch is still in the package
[01:45] <Gloubiboulga> I check
[01:45] <Gloubiboulga> nop, it's not...
[01:45] <Gloubiboulga> I'll add it
[01:45] <janimo> Gloubiboulga: or I can just do that since I downloaded
[01:45] <janimo> as you wish
[01:46] <Gloubiboulga> I can do it janimo
[01:46] <janimo> Daniele, is it clear regarding the libexec path?
[01:46] <janimo> Gloubiboulga: thanks
[01:46] <nomed> janimo, trying to read the mail ..
[01:46] <nomed> but google oops all the time :/
[01:47] <janimo> nomed, external plugins put directly under /usr/llib
[01:47] <janimo> others unedr /usr/lib/xfce4/panel
[01:47] <janimo> so you don;t need to specify libexec for the plugins they know where to put themselves
[01:47] <nomed> janimo, k
[01:47] <nomed> so external plugins go in
[01:47] <allee> kelmo_lap: read your pre-up/down script.  One suggestion s/wpa-conf none/wpa-configfile ignore/
[01:47] <janimo> it clutters /usr/lib imho but debian policy says that;s where libexec is
[01:48] <nomed>  /usr/lib/<plgin name>/xfce/panel-plugins
[01:48] <kelmo_lap> allee, hmm, also a good suggestion, thanks
[01:48] <nomed> even if it's really ugly
[01:48] <janimo> nomed, yes. just install cpugraph mailwatch or whichever external one and see where it put itself
[01:49] <allee> kelmo_lap: Just brainstroming: One advantage of a config file is that wpa_supplicant chosen between network setup on the fly.
[01:49] <nomed> janimo, if it's fine so .. i just don't need to specify libexec opt :)
[01:49] <allee> with your wpa_cli way one need several stanzas and map stuff and actively select between setups
[01:49] <kelmo_lap> allee, yes, indeed. that is why we must cater for simple + advanced setups
[01:49] <janimo> nomed, exactly cdbs makes it really easy
[01:50] <nomed> janimo, there is an issue i think on verve-plugin
[01:50] <nomed> it adds xfce4-panel
[01:50] <janimo> and don;t forget the gettext domain, look at minicmd from Gauvain for an example if you did not yet
[01:50] <janimo> nomed, adds?
[01:50] <nomed> yep
[01:50] <janimo> what do you mean adds xfce4-panel? to what? where? :)
[01:51] <nomed> Depends: ${shlibs:Depends}
[01:51] <kelmo_lap> allee, there needs to be more consideration of course, i have some thoughts in mind . . .
[01:51] <allee> kelmo_lap: I imagine that wpa_supplicant is like ifplugd for ethernet.  When link goes up (wpasuppl found a fiting wlan or lan cable blugged in.  ifup is fired up)
[01:51] <kelmo_lap> no
[01:51] <janimo> to that line, or gets put in there automatically as if it was a shlib
[01:51] <nomed> if i specify xfce4-panel (>= 4.3) i get two entries ..
[01:51] <janimo> delete xfce4-panel then if it still works
[01:51] <kelmo_lap> a wpa_supplicant bound interface is _always_ up
[01:52] <janimo> I saw that too in some otherplugins
[01:52] <nomed> janimo, k
[01:52] <janimo> it is inoffensive if a bit unecessary
[01:52] <kelmo_lap> just not configured with nework settings
[01:52] <kelmo_lap> if it is "downed", then wpaa_supplicant bails out
[01:52] <kelmo_lap> so it needs special attention
[01:52] <allee> kelmo_lap: yes it's up,  I use 'up' here.  the is a connection to another end that can be used to transmit IP
[01:53] <siretart> allee: kelmo_lap: I'm answering/discussing exactly this topic right now in a post to pkg-wpa-devel.
[01:53] <siretart> allee: perhaps you might want to subscribe that mailing list?
[01:53] <allee> siretart: subscribe URL?
[01:54] <Gloubiboulga> janimo, do we need to add some stuff in the POT files?
[01:54] <janimo> Gloubiboulga: I talked to Martin Pitt and he said that those need to be uptodate
[01:54] <kelmo_lap> allee, are you aware of a so called "wpa_cli action script"?
[01:54] <janimo> but honestly I don;t know what is meant by that in our case
[01:54] <janimo> I suppose some strings from .desktop need to be there
[01:54] <allee> kelmo_lap: yeah, saw it in manpage.  But right now I've used only the configfile with several networks
[01:55] <siretart> allee: http://lists.alioth.debian.org/mailman/listinfo/pkg-wpa-devel
[01:55] <janimo> but that can happen separately from this later if needed
[01:55] <Gloubiboulga> I can't help you on that janimo :(
[01:55] <allee> siretart: thx, subscribing ...
[01:55] <kelmo_lap> sure, and different ntworks require different settings
[01:55] <kelmo_lap> networks*
[01:55] <janimo> Gloubiboulga: I am reading gettext docs too at the moment :)
[01:58] <kelmo_lap> allee, i am just thinking how wpa_supplicant can best be leveraged by out networking scripts
[01:58] <kelmo_lap> our*
[01:58] <allee> kelmo_lap: one one hand I like your script.  At first wpa_supplicant stuff was so totally different.  After understanding the autoselect of network, I liked it more than this interfaces map crap (<- IMHO ;)
[01:58] <allee> kelmo_lap: Yes, I'm fighting right now with the same problem :)
[01:59] <kelmo_lap> this is my best idea yet! but i am open to better ones ; )
[01:59] <kelmo_lap> the daemon sucks a bit
[01:59] <kelmo_lap> and the ifup scripts that start the daemon suffer from the same limitations imho
[02:00] <siretart> Perhaps we should support both approaches in different modes of operation
[02:00] <siretart> see my post to pkg-wpa-devel
[02:00] <siretart> (just sent)
[02:01] <kelmo_lap> sure
[02:04] <kelmo_lap> well, have we explored just what the interfaces file is capable of?
[02:04] <kelmo_lap> can't you execute wpa_supplicant, by using these ifupdown hooks, set a dummy static ip on the $IFACE, and use ifplugd anyway?
[02:05] <kelmo_lap> or provide an action script that somehow refers ifup to an externally, network specific block of network settings?
[02:06] <kelmo_lap> ifup --interfaces=FILE possibly?
[02:06] <kelmo_lap> just throwing out ideas here . . .
[02:07] <kelmo_lap> these would be executed on association, deassociation events reported by a wpa_cli daemon
[02:07] <kelmo_lap> but that is a pipe dream right now ; )
[02:15] <siretart> kelmo_lap: you are mixing concepts here
[02:16] <siretart> kelmo_lap: the way wpasupplicant/ifplugd/ifupdown is used by the OP is imo very hackish
[02:16] <kelmo_lap> yes
[02:17] <siretart> ifplugd is a daemon to detect if there is a connection at layer2 (well, if the cable is plugged it, in fact) at all
[02:17] <siretart> if it detects presence, it fires up the interface
[02:18] <siretart> the hack in here is that the interface already has to be up for wpasupplicant to work
[02:18] <siretart> I'd rather say that his whole concept rather happens to work
[02:19] <kelmo_lap> so what have i confused?
[02:21] <siretart> I don't think that we should encourage such strange usage
[02:22] <kelmo_lap> wpa_cli action script is what i would offer as an alternative to those hacks
[02:22] <kelmo_lap> that was the point of my rant
[02:23] <siretart> hm. I have to think about in what way an action script can help here
[02:23] <kelmo_lap> it allows "true" roaming, all via wpa_supplicant
[02:23] <kelmo_lap> & wpa_cli
[02:24] <siretart> so you place a trigger for each essid
[02:24] <siretart> when entering essid X, then do these commands to authenticate properly
[02:25] <G0SUB> Gloubiboulga
[02:25] <kelmo_lap> well, authentication *is* the trigger
[02:26] <Toadstool> hi MOTUs
[02:26] <siretart> I think I didn't get how to use an action script then yet
[02:26] <Gloubiboulga> G0SUB, yep?
[02:26] <kelmo_lap> just network settings are required
[02:26] <kelmo_lap> to use the net
[02:26] <kelmo_lap> ie:
[02:26] <kelmo_lap> net A uses dhcp
[02:26] <G0SUB> Gloubiboulga nothing, just greeted you
[02:26] <kelmo_lap> net B requires a fixed ip
[02:27] <Gloubiboulga> oh, ok G0SUB :
[02:27] <Gloubiboulga> :)
[02:27] <kelmo_lap> you move from the field of association of net A to net B
[02:30] <kelmo_lap> okay, i had better correct the misinformation on that "please include madwifi-ng headers bug"
[02:35] <allee> siretart: if don't use ifplugd with wifi, but for ethernet, it's a great thing.  starting dhclient on startup is a hack. ifplugd is the right solution.
[02:36] <siretart> allee: ifplugd is the right solution for ethernet only. I rather happens to work with wifi interfaces as well
[02:36] <allee> siretart: for wlan I would like that wpasupplicant does the same.  When it find a fitting network (aka link up in ethernet) then fire up ifup
[02:37] <siretart> allee: you want a roaming/profile manager, like networkmanager is
[02:37] <kelmo_lap> allee, but wifi needs to already "up", just not configured to sense the network
[02:37] <allee> siretart: s/want/need/ ^^ ;)
[02:38] <siretart> allee: I think this is a bit out of scope of wpasupplicant. I could think about some roaming/profile manager which works without the gnome dependencies.
[02:38] <allee> kelmo_lap: with static ip the interface is also up, even when link is not up (aka no cable connected)
[02:38] <siretart> allee: or perhaps someone manages to port nm-applet as a plain textui application. that would rock
[02:38] <allee> kelmo_lap: interface up and link up are different things
[02:39] <allee> ifplugd check link up, not interface up  (Maybe that's the reason why ifplug works with wpa_supplicant too, have not tried this)
[02:40] <kelmo_lap> then i cannot explain the difference i see between ethernet and wireless that is fit enough for us both to uderstand ; )
[02:41] <allee> kelmo_lap: which difference do you see?
[02:42] <kelmo_lap> i'm afraid it is past my time to be making any more sense tonight, i'm shagged
[02:43] <allee> 'k np :)
[02:43] <kelmo_lap> http://rafb.net/paste/results/nwqOnf26.html
[02:43] <kelmo_lap> that takes into accoun the changes suggested to the wpa-conf part
[02:44] <kelmo_lap> as for the overall concept, it seems that is still up for debate
[02:44] <allee> kelmo_lap: by on my TODO for today is too try WEP and open Wifi with wpa_supplicant. You know if this is supported?
[02:45] <kelmo_lap> yes, it is
[02:45] <kelmo_lap> key_mgmt=NONE
[02:45] <allee> good.
[02:45] <kelmo_lap> its all in the example files provided by upstream
[02:46] <kelmo_lap> however, i really hate how that is active by default
[02:46] <kelmo_lap> ssid=any, without priority
[02:46] <kelmo_lap> (in default configuration file installed by debian package)
[02:57] <allee> kelmo_lap: wpa-conf = none|managed|ignore sounds like no config used.  wpa-use-conffile  yes|no|on|off maybe describes better what it does,
[02:58] <allee> kelmo_lap: + a wpa-conffile  (with default /etc/wpa_supplicant.conf) ??
[02:59] <kelmo_lap> no defaults, either the path to the file is correct, or not at all
[03:00] <allee> kelmo_lap: yes, of course! I meant default when not given ;)     # I better write what I thought :(
[03:10] <allee> kelmo_lap: one more suggestion. Add a test if a default route is defined.  If yes ifdown it (until we can ask use via dbus).
[03:11] <allee> kelmo_lap: mhmm, ethernet needs it too. so wifi is shut down when I plug in the netcable.
[03:11] <kelmo_lap> allee, please, can you translate that into code form? my brain is a bit tired right now ; ) (and i must take care of a few other things, like feeding one's self)
[03:12] <kelmo_lap> i'll get it into svn, than anyone can goto town on it
[03:12] <allee> kelmo_lap: I'll try, but I just realized that one need to handle interface start with  ifup eth0=my-setup
[03:20] <kelmo_lap> siretart, btw, upstream wpa_supplicant's Makefile need not be patched at all to include madwifi's headers
[04:03] <gouchi> Hi
[04:04] <gouchi> why speedtouch package has been removed on Dapper ?
[04:57] <dholbach> hub: i get the "open file dialog crash on amd64" too - doing a debug build
[04:58] <dholbach> hub: (abiword)
[04:59] <hub> dholbach: yeah. I don't because I don't have an amd64
[04:59] <hub> sorry about that
[04:59] <dholbach> hub: i get a debug bt
[05:12] <dholbach> hub: it FTBFS
[05:13] <hub> *sigh*
[05:13] <hub> dholbach: build log?
[05:13] <dholbach> hub: shall i attach the relevant part of the build log to the bug?
[05:13] <hub> dholbach: please
[05:13] <dholbach> bug 32780
[05:13] <Ubugtu> malone bug 32780 in nautilus "Dead links in trash cannot be deleted" [Normal,Unconfirmed]  http://launchpad.net/bugs/32780
[05:13] <dholbach> oops wrong one
[05:13] <dholbach> bug 32870
[05:13] <Ubugtu> malone bug 32870 in abiword abiword-gnome "Abiword crashes when opening a file" [Normal,Unconfirmed]  http://launchpad.net/bugs/32870
[05:21] <hub> dholbach: that  bug is a know bug
[05:22] <hub> dholbach: it is because of poppler
[05:22] <hub> dholbach: they change the API once again
[05:22] <hub> dholbach: CVS is up to date on that, at least in HEAD
[05:22] <hub> patch is quite trivial
[05:22] <dholbach> hub: ah nice
[05:24] <dholbach> hub: you have a viewcvs somewhere?
[05:24] <hub> yep
[05:24] <hub> http://www.abisource.com/viewcvs/cgi/viewcvs.cgi/
[05:25] <dholbach> http://www.abisource.com/viewcvs/cgi/viewcvs.cgi/viewcvs/cgi/viewcvs.cgi/viewcvs/cgi/viewcvs.cgi/viewcvs/cgi/viewcvs.cgi/ ? ;-p
[05:25] <hub> ???
[05:25] <dholbach> just kdding :)
[05:25] <hub> http://www.abisource.com/viewcvs/cgi/viewcvs.cgi/abiword-plugins/
[05:25] <dholbach> yeah
[05:25] <dholbach> i'm on it
[05:25] <dholbach> was just making fun of the repetition in "viewcvs/cgi/viewcvs.cgi/"
[05:26] <hub> yeah
[05:26] <hub> well I didn't install it
[05:26] <dholbach> nevermind :)
[05:32] <dholbach> hub: either viewcvs is lying or I'm too stupid - the newest changes in abiword-plugins/wp/impexp/pdf/xp are 11 months old (in HEAD)
[05:32] <dholbach> ah no
[05:32] <dholbach> sorry
[05:33] <dholbach> i'm too stupid so ;)
[05:36] <dholbach> hub: merci beaucoup
[05:37] <hub> bienvenue
[06:10] <dholbach> hub: attached an amd64 debug backtrace on bug 32870
[06:10] <Ubugtu> malone bug 32870 in abiword abiword-gnome "Abiword crashes when opening a file (on AMD64)" [Normal,Unconfirmed]  http://launchpad.net/bugs/32870
[06:46] <netzmeister> re
[06:47] <dolson> hey LaserJock
[06:48] <LaserJock> hi dolson
[06:54] <LaserJock> hi G0SUB and fredix
[06:54] <G0SUB> LaserJock :)
[06:55] <fredix> hi LaserJock
[06:59] <dholbach> have a nice evening
[06:59] <Gloubiboulga> cu dholbach
[07:00] <LaserJock> hi dholbach
[07:00] <LaserJock> bye dholbach
[07:09] <dolson> cya dholbach
[07:21] <netzmeister> hi
[07:21] <netzmeister> how is the naming scheme for manpages in the debian dir..?

[07:24] <netzmeister> "codeblocks.devel"
[07:24] <netzmeister> ?
[07:24] <LaserJock> no
[07:24] <netzmeister> :(
[07:25] <LaserJock> section is what section of man
[07:25] <netzmeister> ah okay..
[07:25] <LaserJock> do you have any of the .ex files from dh_make?
[07:26] <LaserJock> nm, look at http://www.debian.org/doc/maint-guide/ch-dother.en.html#s-manpage
[07:28] <netzmeister> LaserJock:  my manpages are "codeblocks.1" and "code_runner.1"
[07:28] <netzmeister> but he did not compile them..
[07:28] <netzmeister> in the deb...
[07:30] <LaserJock> netzmeister: do you have dh_manpages in your debian/rules
[07:31] <netzmeister> LaserJock:  "dh_installman"
[07:31] <netzmeister> is that wring?
[07:31] <netzmeister> wrong
[07:33] <LaserJock> no, that is ok, do you have codeblocks.manpages in debian/ ?
[07:33] <netzmeister> codeblocks.1
[07:33] <netzmeister> yes
[07:34] <LaserJock> no
[07:34] <LaserJock> you want a file called "codeblocks.manpages" in debian/
[07:34] <LaserJock> it lists the location of you man page
[07:34] <LaserJock> man dh_installman
[07:34] <netzmeister> k
[07:45] <Xoritor> hello everyone
[07:45] <LaserJock> hi Xoritor
[07:45] <Xoritor> i am going to be asking some package building questions... hope this is the right place
[07:45] <LaserJock> go for it
[07:46] <Xoritor> i am hoping to update the prelude stuff and build some snort+prelude
[07:46] <Xoritor> as well as add the preludedb stuff
[07:46] <Xoritor> and provide preludedb+msql and preludedb+postgresql
[07:46] <Xoritor> and some samhain+prelude packages
[07:46] <Xoritor> my first question is:
[07:47] <Xoritor> when using dpkg-buildpackage is there a different pathing/ld.so.conf/env ?
[07:48] <Xoritor> what is the prefered method of building packages from source trees?
[07:48] <LaserJock> from original source?
[07:48] <LaserJock> dh_make helps
[07:48] <Xoritor> i looked on the wikki/fourms/website (devel section) and saw several diff options but nothing coherent
[07:48] <Xoritor> dh_make helped a TON
[07:48] <Xoritor> yes from original sources
[07:49] <Xoritor> oh... and im building them for dapper x86 and x86_64
[07:49] <LaserJock> ok, so where are you having the problem?
[07:49] <Xoritor> hope to have them "ready to ship" by dapper ship date
[07:50] <Xoritor> dpkg-buildpackage errors out where ./configure && make does not
[07:50] <LaserJock> ah, ok
[07:50] <Xoritor> i did notice that dpkg-buildpackage sees 486 where ./configure sees 686
[07:51] <Xoritor> is checkinstall a good method or a bad method for supportable packages?
[07:51] <LaserJock> so what is the error? if it is more than a line or two you can use pastebin.ubuntu-nl.org
[07:51] <LaserJock> bad
[07:51] <Xoritor> oh and im doing this in a chroot
[07:51] <Xoritor> LaserJock, thats what i thought
[07:51] <LaserJock> we try to discourage checkinstall if you want to distribute your .debs at all
[07:51] <Xoritor> can i paste in here?
[07:51] <Xoritor> should i use a pastebin
[07:51] <Xoritor> its not very long
[07:51] <LaserJock> if it is short
[07:52] <Xoritor> 2 lines... maybe 3
[07:52] <netzmeister> LaserJock:  Thx, it works.. ahh btw. congratulation. I read the TB report. :-)
[07:52] <LaserJock> netzmeister: thanks
[07:52] <LaserJock> Xoritor: go for it
[07:52] <Xoritor> .libs/prelude-client.o: In function `prelude_client_init':/root/build/libprelude-0.9.5/src/prelude-client.c:158: undefined reference to `gcry_md_hash_buffer'
[07:52] <Xoritor> collect2: ld returned 1 exit status
[07:52] <Xoritor> thats the error that returns with dpkg-buildpackage
[07:53] <Xoritor> that does not happen with ./configure && make
[07:53] <Xoritor> same chroot
[07:53] <Xoritor> same source tree
[07:53] <LaserJock> hmm, wonder if it is the optimizations buildpackage uses
[07:53] <Xoritor> hmm
[07:53] <Xoritor> how can i see those
[07:53] <Xoritor> im new to .debs
[07:53] <Xoritor> :-/
[07:53] <Xoritor> sorry if i ask n00b questions
[07:54] <Xoritor> i worked for Red Hat for the last 3 years so i am more familiar with .rpms
[07:54] <Xoritor> and any "reference" material would be helpful
[07:54] <LaserJock> umm, I'm  not entirely certain what is default but you can set the CFLAGS in debian/rules
[07:55] <Xoritor> aaah
[07:55] <Xoritor> cool
[07:55] <Xoritor> im going to start it all over from scratch again... so i may be in and out
[07:56] <Xoritor> not sure if i want to start with a new chroot
[07:56] <Xoritor> or not
[07:56] <Xoritor> and what is pbuilder?
[07:56] <Xoritor> is that just for rebuilding .debs?
[07:56] <LaserJock> pbuilder will build the .debs in a chroot
[07:56] <LaserJock> a clean chroot
[07:56] <Xoritor> thats what i thought
[07:56] <LaserJock> so you can make sure you have the dependencies right
[07:57] <LaserJock> it is pretty standard for us
[07:57] <Xoritor> i think i am going to blow away my chroot and make sure the deps are correct
[07:57] <Xoritor> i want to make 100% sure
[07:57] <LaserJock> Xoritor: I'd check out http://www.debian.org/doc/maint-guide/ch-dreq.en.html#s-rules and http://www.debian.org/doc/debian-policy/ch-files.html#s10.1
[07:57] <Xoritor> its soooo easy to build with the debootstrap...
[07:57] <Xoritor> man
[07:58] <LaserJock> Xoritor: you could just build a pbuilder within your chroot
[07:58] <Xoritor> i have that now...
[07:58] <Xoritor> but pbuilder wont work with source trees right?
[07:58] <Xoritor> only .debs
[07:58] <Xoritor> ?
[07:59] <LaserJock> umm, you use pbuilder to build the .debs from the source package
[07:59] <Xoritor> oh...
[07:59] <azeem> there's pdebuild which is probably being run from the source tree
[07:59] <Xoritor> let me read the man again and ask some senseable questions
[07:59] <Xoritor> heh
[08:00] <Xoritor> bbiab (with more knowlege)
[08:00] <LaserJock> np
[08:00] <Xoritor> err
[08:00] <Xoritor> s/ knowlege/ knowledge
[08:00] <LaserJock> hi azeem, thanks for the upload btw.
[08:01] <azeem> cheers
[08:01] <azeem> you were lucky my ThinkPad was up when I got the mail, it's mostly broken right now :-/
[08:01] <bmonty> Xoritor: you can start pbuilder from inside the source tree, use "pdebuild"
[08:02] <azeem> I should get the GPG key off it to my crappy old notebook to be a bit more productive
[08:02] <LaserJock> azeem: ouch
[08:03] <LaserJock> azeem: I'm trying to work from OSX these days. Makes it a bit more difficult :(
[08:04] <azeem> :-/
[08:04] <LaserJock> but I've got a Debian sarg box set up with a dapper chroot so..
[08:12] <Xoritor> hmm
[08:13] <Xoritor> so how do i add a package to the pbuilder chroot so it can "satisfy" the deps?
[08:13] <azeem> what is unsatisfied?
[08:13] <Xoritor> gnutls
[08:13] <Xoritor> probably gnutls-dev
[08:14] <azeem> so you Build-Depend on gnutls-dev, and pbuilder cannot install that?
[08:14] <Xoritor> it was on gnutls... prolly just needed the -dev part
[08:14] <Xoritor> :-/
[08:14] <Xoritor> im a moron sometimes
[08:14] <azeem> "it was"?
[08:14] <azeem> I am not quite sure what you are trying to do
[08:14] <azeem> did you run pbuilder and/or pdebuild and got an error message
[08:14] <azeem> ?
[08:15] <Xoritor> the Build-Depend part had gnutls not gnutls-dev
[08:15] <azeem> ok
[08:15] <Xoritor> pdebuild and it said it could not find gnutls
[08:15] <azeem> of course, gnutls-dev does not exist eitehr
[08:15] <azeem> either
[08:16] <Xoritor> cause its not gnutls its libgnutls-dev or libgnutls12
[08:16] <Xoritor> sheesh... not enough caffine i think ;-)
[08:16] <Xoritor> azeem, sorry im a PITA, and thx for the prod
[08:16] <azeem> no problem
[08:16] <Xoritor> sometimes i think i should be hit with a cattle prod
[08:17] <Xoritor> i was up till 3 am watching defensive driving videos and taking those online exams
[08:17] <Xoritor> :-/
[08:17] <Xoritor> so my attention is not all here yet
[08:29] <Xoritor> to "clean up" and "start over" i can just remove the files that are not my source tree right?
[08:30] <LaserJock> Xoritor: well, you could just get rid of the source and re-untar the source tarball. does that make sense?
[08:30] <Xoritor> yea
[08:30] <Xoritor> but the sources are really compiled in the source tree right?
[08:31] <Xoritor> they are moved into the chroot and compiled
[08:31] <Xoritor> or does it effect the chroot and compile in the source tree?
[08:32] <Xoritor> well it errored out anyways
[08:32] <LaserJock> woah, I'm not following you. Can you explain what your doing exactly?
[08:33] <Xoritor> heh
[08:33] <Xoritor> in the source tree i used the pdebuild command
[08:33] <LaserJock> k
[08:33] <azeem> pdebuild probably just makes a source package for you and builds that in the chroot
[08:33] <LaserJock> azeem: right
[08:34] <Xoritor> if i want to "compile again" i can just remove the files that are ../<packagename>_<version>.*
[08:34] <Xoritor> right?
[08:34] <Xoritor> or do i need to do it _all_ from scratch again?
[08:34] <azeem> just rerun pdebuild, I'd say
[08:34] <LaserJock> yeah
[08:34] <Xoritor> oh?
[08:34] <Xoritor> really?
[08:34] <Xoritor> hmm
[08:34] <azeem> this is pbuilder, you will need to rerun
[08:36] <LaserJock> Xoritor: you're making it too hard on yourself ;-)
[08:37] <Xoritor> LaserJock, like i said i come from the .rpm world ;-)
[08:37] <Xoritor> hahahahaha
[08:37] <Xoritor> with .rpm if its not hard, it does not work
[08:37] <Xoritor> heh
[08:38] <Xoritor> but so far i am loving what i find
[08:38] <Xoritor> once i wrap my head around it
[08:38] <Xoritor> and thank you both for the help
[08:38] <LaserJock> hmm, people usually say that .debs are harder than .rpms. I've never done an .rpm so I don't know.
[08:39] <LaserJock> Xoritor: np
[08:39] <Xoritor>  if you have ever hand written a spec file you will not say that
[08:39] <Xoritor> they are HORRID
[08:39] <trappist> I have, and I still think specs are easier
[08:39] <trappist> they're both nightmares
[08:39] <Xoritor> trappist, agreed on the last statement
[08:40] <LaserJock> can't make it too easy ;-)
[08:40] <trappist> yeah there's definitely a limit on that
[08:40] <trappist> I think more of it could probably be automated
[08:40] <Xoritor> this is much more automated than hand writing a spec
[08:41] <LaserJock> some of the problem is that it is that there are a few different ways of doing each task
[08:41] <LaserJock> it is an individual thing
[08:41] <trappist> yeah.  I just recently heard of debuild, when I've been using dpkg-buildpackage like a chump.
[08:42] <LaserJock> I started out on debuild. I've never used dpkg-buildpackage directly
[08:42] <Xoritor> one of my buddies is looking for a good version control system... any recomendations
[08:42] <LaserJock> we use bzr quite a bit here
[08:42] <Xoritor> he has lots of binaries to store and does not want them to be "new copies"
[08:42] <trappist> Xoritor: svn
[08:42] <LaserJock> but it is fairly new
[08:43] <Xoritor> trappist, svn they ruled out for some reason
[08:43] <trappist> I can't imagine
[08:43] <trappist> I love it
[08:43] <LaserJock> yeah, I either use svn or bzr
[08:43] <LaserJock> but I don't do much
[08:43] <trappist> makes cvs look ghetto
[08:43] <Xoritor> lol
[08:43] <LaserJock> lol
[08:44] <Xoritor> i like svn more than cvs myself
[08:44] <Xoritor> never used bzr
[08:45] <trappist> oh, bzr is distributed
[08:45] <trappist> so it's more like git than svn?
[08:45] <LaserJock> yeah, I believe so
[08:46] <LaserJock> http://bazaar-vcs.org/ is the place to check it out I think
[08:46] <trappist> google thought launchpad was the place to go
[08:46] <LaserJock> not really if you want very much info
[08:47] <Xoritor> any tools that do binary diff?
[08:47] <LaserJock> but bzr is used a lot in anything Ubuntu because it is supported by Canonical and seems to be one of Mark's pet projects
[08:47] <Xoritor> hehehe
[08:48] <LaserJock> it's written in python after all ;-)
[08:48] <Xoritor> i guess my build deps are not right... or my arch does not work correctly
[08:48] <Xoritor> still errors out
[08:49] <LaserJock> Xoritor: the FAQ at the site I said above has a question about Binary files
[08:50] <Xoritor> yea i looked it says it stores them but not as diffs (i dont know why they need binary diffs)
[09:02] <sanpera> can anybody tell me the proper way to submit a patch against a universe package?
[09:03] <sanpera> should i just create a bug and attach the debdiff?
[09:03] <sanpera> in malone?
[09:04] <LaserJock> yes
[09:04] <sanpera> thank you!
[09:05] <Xoritor> how can i change the "arch" pdebuild builds for?
[09:07] <Xoritor> Architecture: any
[09:07] <Xoritor> change that in the rules?
[09:07] <LaserJock> no
[09:08] <LaserJock> man pbuilder gives --binary-arch
[09:08] <LaserJock> perhaps that might help
[09:08] <Xoritor> hmm
[09:08] <LaserJock> I've never done it so I'm not sure
[09:09] <Xoritor> odd that it will build for 686 and not 486... maybe there is something else i am missing
[09:10] <LaserJock> what arch's do you want to use?
[09:10] <Xoritor> well... 686 is fine
[09:11] <Xoritor> i dont have any need of 486 or 386 really
[09:11] <Xoritor> but if i want to submit it for others it needs to be built for them right?
[09:11] <LaserJock> umm, wouldn't you just do i386?
[09:12] <Xoritor> yea
[09:12] <Xoritor> but it says its builing for 486 (i dunno why)
[09:13] <LaserJock> what does the name of the .deb say?
[09:13] <Xoritor> ./configure finds 686 when used by iteslf
[09:13] <Xoritor> what .deb?
[09:13] <LaserJock> the result from pbuilder
[09:13] <Xoritor> i dont have a .deb
[09:13] <Xoritor> it dies
[09:14] <LaserJock> ok
[09:14] <Xoritor> it errors out
[09:14] <Xoritor> but the ./configure && make does not
[09:14] <Xoritor> the only diff i see from me running ./configure && make and pdebuilder is the arch
[09:15] <LaserJock> ok, so did you try different CFLAGS?
[09:15] <Xoritor> using the same CFLAGS i think
[09:19] <plugwash> didn't debian scrap i386 support some time ago?
[09:22] <LaserJock> well, I don't know what they are actually but the arch is i386
[09:22] <LaserJock> seems it is wanting to do 486 for Xoritor
[09:22] <Xoritor> when you compile something what do these 2 lines look like for you?
[09:23] <Xoritor> checking build system type... i686-pc-linux-gnu
[09:23] <Xoritor> checking host system type... i686-pc-linux-gnu
[09:23] <Xoritor> checking target system type... i686-pc-linux-gnu
[09:23] <Xoritor> err.. 3 lines
[09:23] <Xoritor> ;-)
[09:23] <Xoritor> thats what i get from ./configure
[09:23] <azeem> that looks right
[09:24] <Xoritor> but when i do the pdebuild it says i486-pc-linux-gnu
[09:24] <Xoritor> :-/
[09:24] <Xoritor> and it dies
[09:24] <Xoritor> not at ./config but later on
[09:24] <azeem> how does it die?
[09:25] <Xoritor> i manually put i686-pc-linux-gnu rules this time so maybe that will fix it
[09:25] <azeem> is the package passing the system types to configure maybe?
[09:25] <Xoritor> it was something about an undefined ref...
[09:25] <Xoritor> cant remember exactly
[09:25] <Xoritor> .libs/prelude-client.o: In function `prelude_client_init':/root/build/libprelude-0.9.5/src/prelude-client.c:158: undefined reference to `gcry_md_hash_buffer'
[09:25] <Xoritor> there it is
[09:26] <Xoritor> but that does not happen with ./configure && make
[09:26] <Xoritor> it only happens with pdebuild and dpkg-buildpackage
[09:27] <Xoritor> and the only diff i have seen is that both pdebuild and dpkg-buildpackage set the arch to 486 instead of 686
[09:27] <Xoritor> ok that was NOT it
[09:27] <Xoritor> heh
[09:27] <Xoritor> got the same error setting arch to 686
[09:27] <Xoritor> :-/
[09:28] <Xoritor> maybe i missed a dep someplace
[09:28] <bmonty> Xoritor: thats why you use pbuilder, you are missing a build dep :)
[09:28] <Xoritor> :-D
[09:28] <azeem> gcry_* is from libgcrypt
[09:28] <Xoritor> oh heck how did you find that?
[09:28] <azeem> I knew it :)
[09:29] <azeem> well, I am not 100% sure, but I think it is
[09:29] <Xoritor> azeem, the magic man (or woman if your a woman)
[09:29] <Xoritor> hahaha
[09:29] <LaserJock> Xoritor: that is why you have to have smart people like azeem around
[09:30] <Xoritor> added libgcrypt11-dev on and we shall see
[09:30] <Xoritor> ;-)
[09:31] <Xoritor> anyone ever played with prelude+snort+samhain+mysql ?
[09:31] <Xoritor> oh and +snortsam
[09:31] <Xoritor> heh
[09:32] <Xoritor> adaptive cooperative reporting firewalls
[09:32] <Kyral> Hey
[09:32] <Kyral> :D
[09:32] <LaserJock> hi Kyral
[09:33] <Xoritor> hi
[09:36] <LaserJock> Kyral: how are classes?
[09:40] <Kyral> LaserJock: ehh Math got better when I stopped taking notes with the Laptop lol
[09:40] <Kyral> I'm really considering trying Gentoo's new installer
[09:45] <LaserJock> me too
[09:45] <Kyral> Maybe on my laptop
[09:49] <LaserJock> I'm trying out Q on my intel iMac right now
[09:49] <Kyral> Q?
[09:52] <Xoritor> you know Q... he was the alien on star trek
[09:52] <Xoritor> ;-)
[09:52] <hub> LaserJock: intel iMac?
[09:52] <hub> damn
[09:52] <Xoritor> LaserJock, seems to have all the cool toys
[09:52] <Xoritor> ;-H
[09:52] <hub> if only I had one to port AbiWord to MacOS X
[09:52] <LaserJock> Kyral: Q is cool OSX port of qemu
[09:53] <LaserJock> well, it isn't exactly my personal machine, but my boss bought a couple for the lab ;-)
[09:53] <LaserJock> I can pretty much do whatever I want with it though
[09:54] <hub> LaserJock: you lucky
[09:54] <LaserJock> sorta, it has been a bit difficult
[09:54] <LaserJock> I can't put Ubuntu on it and fink and darwinports don't work very well
[09:55] <LaserJock> and Thunderbird just freezes all the time
[09:55] <Xoritor> :-/
[09:55] <hub> LaserJock: well I would only use it for AbiWord MacOS X?
[09:55] <hub> LaserJock: I have a PC for Linux
[09:55] <hub> and MacMini for MacOS X PPC
[09:56] <LaserJock> I do too but I spend ~10 hrs a day on the iMac and ~30min on the Ubuntu box at home
[09:56] <LaserJock> so I'm learning to work on Ubuntu from the mac ;-)
[09:57] <LaserJock> for instance, I'm trying to see how fast qemu would be on it
[09:57] <LaserJock> Flight4 wouldn't install
[09:58] <LaserJock> but Breezy worked ok
[09:58] <LaserJock> and I'm trying the Gentoo livecd right now
[09:58] <Kyral> I need a blank lol
[09:58] <LaserJock> blank what?
[09:59] <Kyral> CD
[09:59] <Kyral> To burn the ISO
[09:59] <LaserJock> oh, I don't burn isos anymore ;-)
[10:02] <LaserJock> oh, that's pretty. Those Gentoo guys did a good job on the boot graphics
[10:02] <Xoritor> LaserJock, linky?
[10:03] <LaserJock> no, I'm just booting it up in qemu
[10:03] <Xoritor> oh
[10:03] <Xoritor> :-/
[10:03] <Xoritor> i would like to see something pretty
[10:03] <LaserJock> how do you take a screenshot in OSX?
[10:04] <Xoritor> you dont have to go through that much hassel
[10:04] <hub> LaserJock: apple-shift-3
[10:04] <Xoritor> im sure there are some if i get my lazy a$$ to google them
[10:08] <LaserJock> Xoritor: here is a shot once it is booted up http://chem.unr.edu/~mantha/gentoo_livecd1.png
[10:09] <Xoritor> its pretty
[10:09] <Xoritor> thank you
[10:11] <LaserJock> that is cool, they have a FAQ, a CLI installer and a GUI installer
[11:14] <marcin`> hello MOTU
[11:15] <marcin`> need help - I want to repackage some old package thas is maintained by someone
[11:16] <marcin`> but package contains software from 2002 while last upstream is from 2006
[11:16] <marcin`> and I would like to package new upstream, change package scripts (implement CDBS)
[11:16] <marcin`> and put into REVU
[11:17] <marcin`> my question is - what should I put into 'Maintainer:' field in control file?
[11:17] <marcin`> my credentials or current debian maintainer?
[11:27] <marcin`> LaserJock: ping
[11:27] <netzmeister> pong
[11:27] <marcin`> I need some help
[11:28] <marcin`> 1. question above - about maintainer credentials...
[11:28] <marcin`> could you answer this?
[11:28] <azeem> if you repackage from scratch, you're the maintainer
[11:28] <marcin`> ok
[11:28] <azeem> marcin`: does it matter a lot whether you're in the Maintainer: field?
[11:28] <marcin`> then bigger problem
[11:29] <marcin`> azeem: not really but I got some custom build script that put my credentials automagically
[11:29] <azeem> that seems odd
[11:29] <azeem> why are you doing this?
[11:29] <marcin`> azeem: so for some other credentials I need to modify them manually and add -k<mykeyid> to package
[11:29] <raphink> lol
[11:30] <azeem> you edit debian/control's Maintainer: field?
[11:30] <azeem> automatically, that is
[11:30] <marcin`> no I got set of templates that use @MAINTAINER_NAME@ @MAINTAINER_MAIL@ etc.
[11:31] <azeem> for making new packages?
[11:31] <marcin`> yup
[11:31] <marcin`> anyway now about big problem....
[11:32] <marcin`> raphink: you also could take a look
[11:32] <raphink> not right now
[11:32] <marcin`> today I realized that libphp-jpgraph is pretty much outdated - 2002
[11:32] <marcin`> so I started to work on new upstream release
[11:33] <marcin`> and then in 'copyright' I found notice form current debian maintainer
[11:33] <marcin`> that he didn't upgraded intentionally because new version of jpgraph is on dual license
[11:34] <marcin`> QPL 1.0 (Qt Free License) For non-commercial, open-source and educational use
[11:34] <marcin`> and JpGraph Professional License for commercial use
[11:35] <marcin`> so this is not compliant with DFSG #6 (I'm not sure what is DFSG but this is in that notice)
[11:35] <azeem> DFSG are the Debian Free Software Guidelines
[11:35] <marcin`> and the problem is ( raphink it's to you also) that this package is available as standalone in 1.5.2 version on GPL
[11:36] <marcin`> but is also included in vtigercrm that me and ArmeBosse and raphink and some other guys would like to have in debian/ubuntu
[11:36] <azeem> so the new version probably could be put into multiverse
[11:37] <azeem> is it that much better that it warrants moving it from universe to multiverse
[11:37] <azeem> ?
[11:37] <raphink> talking about vtiger marcin`, would you like me to put it on my repo so it's available ?
[11:37] <marcin`> and this version included in vtigercrm is not on GPL unfortunately
[11:37] <raphink> marcin`: since it won't be in dapper, I can build it for both dapper and breezy and put it on
[11:37] <marcin`> I just wanted to remove this from vtiger and set as dependency
[11:38] <marcin`> raphink: ok but please wait for a while ok?
[11:38] <raphink> sure
[11:38] <marcin`> raphink: this package that is in REVU is really nothing special
[11:38] <raphink> ok :)
[11:38] <marcin`> raphink: I still work pretty hard on this stuff
[11:38] <raphink> ok fine :)
[11:38] <raphink> take your time to get it well :)
[11:38] <marcin`> raphink: and I'll have it ready pretty soon - and with new 4.2.4 version
[11:38] <raphink> good
[11:39] <marcin`> raphink: sure - but now I don't know what to do with this jpgraph stuf...
[11:39] <marcin`> raphink: if this dual license is not compatible with DFSG then we got a problem
[11:39] <raphink> indeed we do
[11:41] <marcin`> raphink: I didn't know about this while ArmeBosse prepared copyright and he mentioned QPL only
[11:41] <raphink> :(
[11:41] <marcin`> raphink: but I started to
[11:41] <azeem> maybe Ubuntu considers the QPL fine for universe
[11:41] <marcin`> raphink: 'strip' vtiger and remove parts that are already available in debian
[11:42] <marcin`> raphink: and set these things as dependency
[11:42] <raphink> mhm
[11:42] <marcin`> raphink: so I removed adodb directory while everything that is in this dir is in libphp-adodb already
[11:42] <marcin`> raphink: and it works perfectly
[11:42] <raphink> good :)
[11:43] <marcin`> raphink: then I created libphp-log4php (in REVU if you can please take review this package :) )
[11:43] <raphink> well not right now I don't feel like reviewing really :--
[11:43] <raphink> I rather feel like taking a pause actually
[11:44] <raphink> while my comp is pbuilding
[11:45] <marcin`> raphink: and then I started to repackage this jpgraph and found this problem
[11:45] <bmonty> for a package that build-deps on libx11-dev, anyone know what would cause "configure: error: X Window System not found"?
[11:45] <azeem> bmonty: some autoconf checks look for libxt for some reason I think
[11:46] <marcin`> raphink: with license... anyway about review - no problem... but I need this package to be in universe with vtigercrm
[11:46] <azeem> bmonty: if you have the build tree around still, inspect config.log
[11:46] <raphink> marcin`: you won't get anything in universe before 2 months so don't worry ;)
[11:47] <marcin`> raphink: sure but as you know I work on this package because I use this software comercially
[11:47] <raphink> yes
[11:48] <bmonty> azeem: thanks, libxt-dev fixed it
[11:48] <marcin`> raphink: so I will work on this - but this license issue is pretty important
[11:48] <raphink> yes
[11:49] <marcin`> hehhh jpgraph for commercial usage -> 106.25 Euro ;/
[11:50] <raphink> :(
[11:57] <thierry> LaserJock : ok we really need to talk with dev guys to know if we get the terminal apps in the menu, it would save a lot of time to people working on .desktop files
[12:02] <LaserJock> thierry: ok, just a sec