[12:06] <sladen> spacey: interesting.  a 64MB download
[12:07] <sladen> the data can go in multiverse
[12:07] <sladen> which probably means having to put the engine in there aswell since I think there's a policy against free software where the only (current) way to use it is relying on non-free data files
[12:11] <spacey> yeh
[12:11] <spacey> goodnight
[12:41] <sladen> nice.  the source-code you can download doesn't match the binary you can download
[12:41] <sladen> *sigh*
[12:43] <\sh> sladen: this warbla thing?
[12:43] <sladen> warsow
[12:44] <sladen> neither does the binary download come with a "written offer" of where to download the source code
[12:44] <sladen> but then you ask and find that it's inside "the SDK"
[12:44] <\sh> oh joy
[12:44] <sladen> and then find that the source code in there doesn't contain the code to print the error that the binary is giving you...
[12:45] <\sh> sladen: so it doesn't work for you, too?
[12:45] <Erlang> well, that sure seems like a fun game
[12:51] <sladen> \sh: Error: R_Upload32_3D: texture (***r_dlighttexture***) is too large   ?
[12:52] <sladen> this URL:  http://www.quakesrc.org/forums/viewtopic.php?p=54650&sid=d484e44d62144e8a5e208659376ca7bf
[12:52] <sladen> includes the fix
[12:52] <sladen> but it's a bit hard to apply that when the context and the code is *completely missing*
[12:53] <\sh> sladen: yes
[01:04] <bmonty> nice, I just found a site that makes it so you can create vmware images with the player
[01:06] <LaserJock> bmonty: you can also use qemu
[01:07] <bmonty> LaserJock: yeah, I'm going to try both and see which I like better
[01:09] <bmonty> bbl
[01:25] <jabra> trying to install a debootstrap of debian
[01:26] <jabra> getting an error while doing the install
[01:29] <sladen> bmonty: qemu-img ?
[01:29] <sladen> bmonty: hint hint
[01:33] <plugwash> jabra and the error is?
[01:34] <plugwash> jabra try using cdebootstrap instead, its generally better at installing suites that are newer than the version of debootstrap
[01:35] <LaserJock> debootstrap should work fine though
[01:36] <Erlang> debootstrap can't bootstrap a 32 bit system on a 64 bit machine.  That suck.
[01:36] <LaserJock> ?
[01:36] <LaserJock> why not?
[01:37] <Erlang> because whenever you specify --arch=i386 it crashes unless has been done in the last week that I don't know about.
[01:37] <LaserJock> hmm, I didn't know that
[01:38] <Erlang> cdebootstrap works fine thought but it's only for Debian distro.
[01:38] <LaserJock> I don't have a 64-bit so I've never tried it but I know it worked in the past
[01:50] <plugwash> cdebootstrap debian and upgrade to ubuntu?
[01:56] <LaserJock> darn it, bzr isn't working :(
[01:57] <sladen> Erlang: can you file a bug pelase
[02:06] <Erlang> sladen: IMHO it's been filed in Debian for a while but I'll double check.
[02:07] <jabra> plugwash: thanks
[02:07] <jabra> will do
[02:11] <jabra> let you know how that goes
[02:14] <jabra> got an error
[02:14] <jabra> Couldn't install root!
[02:14] <jabra> ran the following
[02:14] <jabra> root # cdebootstrap sid /media/usbdisk-3/sid-root http://ftp.debian.org/debian
[02:15] <plugwash> what happens if you leave off the last parameter?
[02:15] <jabra> which is ? --arch i386?
[02:16] <sladen> Erlang: if it's happening in Ubuntu, file it in Ubuntu and link to the upstream bug report
[02:16] <jabra> retrying without the url
[02:16] <Erlang> sladen: working on that...
[02:17] <Erlang> or maybe the problem comes from pbuider.
[02:22] <Erlang> darn it's working now.
[02:23] <jabra> problem persists with cdebootstrap
[02:23] <jabra> E: Couldn't install root!
[02:24] <Erlang> sladen: in retrospect, it was a weird glitch with command line parsing in pbuilder.
[02:31] <jabra> persists with sarge as well as sid
[03:38] <crimsun> go bddebian, go! :)
[03:40] <tseng> @seen Yagisan
[03:40] <tseng> !seen Yagisan
[03:41] <bddebian> Heya tseng
[03:41] <tseng> Ubugtu: you are lame.
[03:41] <tseng> hi bddebian
[03:41] <bddebian> heh
[03:49] <tseng> bddebian: :<
[03:49] <bddebian> Aye
[03:50] <bluefoxicy> hey tseng
[03:50] <bluefoxicy> as far as devs go, what is the potential for a hardening team on Ubuntu?
[03:50] <tseng> Yagisan
[03:50] <tseng> is the man
[03:50] <bluefoxicy> I get the feeling nobody cares, mainly because the last group seems to have milled around and then you know... died
[03:50] <bluefoxicy> ah ok
[03:50] <tseng> if you like to talk
[03:51] <bluefoxicy> trulux just sort of moved to fedora
[03:51] <tseng> you and trulux can talk yourselves to death
[03:51] <bddebian> bluefoxicy: You may want to ... nevermind :-)
[03:51] <bluefoxicy> and the rest of them... like.... are wandering around like "the sky is blue~"
[03:51] <tseng> Yagisan is actually making forward progress
[03:51] <tseng> and
[03:51] <bluefoxicy> tseng:  hey at least I am able to talk in understandable english; although trulux is able to actually make things happen with selinux et al.
[03:51] <tseng> the CTO of canonical has SSP and NX on his hot list of features for edgy
[03:51] <bluefoxicy> ah
[03:51] <tseng> bluefoxicy: I respectfully disagree
[03:52] <bluefoxicy> tseng I wrote out a specification based on the UDU ProactiveSecurityRoadmap for a first step
[03:52] <tseng> Yagisan and I were involved in that
[03:53] <tseng> and ajmitch
[03:53] <bluefoxicy> there is FAR too much to do at once, so I wrote a spec that focuses on aslr, memory protections, PIE, and SSP
[03:53] <bluefoxicy> I saw
[03:53] <tseng> SSP would be a really nice first step
[03:53] <bluefoxicy> as far as I know the only progress that was made was getting dhclient3 and a few other daemons to behave wrt priv sep
[03:53] <bluefoxicy> yes
[03:53] <tseng> oh, most daemons in the default install are de-rooted now
[03:53] <tseng> its a good thing
[03:53] <bmonty> SSP = ?
[03:53] <bluefoxicy> I like SSP, but you can make no real guarantees on its effectiveness that I can see; then again, that analysis is rather fuzzy
[03:54] <tseng> the other things are pretty intrusive
[03:54] <tseng> ssp combined with aslr is pretty strong if you ask me
[03:54] <bluefoxicy> bmonty stack smash protection, FORTIFY_SOURCE and -fstack-protector
[03:54] <tseng> with nx, very strong
[03:54] <bmonty> bluefoxicy: thanks
[03:54] <bluefoxicy> tseng:  ASLR I say needs PIE AND heap randomization AND enforced non-executable memory to be considered effective.
[03:55] <tseng> bmonty: it adds a known random value to the end of a buffer and checks it after each write
[03:55] <tseng> bmonty: to detect under/overflow
[03:55] <tseng> if its triggered it kills the app immediately
[03:55] <tseng> before privelage escalation or whatever was the intended goal
[03:55] <bmonty> tseng: interesting, I think I remember reading about it once
[03:56] <bmonty> it is part of gcc already, right?
[03:56] <tseng> yes.
[03:56] <bluefoxicy> without PIE a crafty attacker can likely build a stack frame in the heap (which isn't randomized right now) and then return to the main executable (also not randomized) at an address where 'call' calls an interesting function (system()?)
[03:56] <tseng> bluefoxicy: that is nice, in theory
[03:56] <bddebian> Ohh
[03:56] <bmonty> wasn't there some negative performance issues associated with SSP?
[03:56] <bluefoxicy> PIE moves the main executable around with mmap(); heap randomization is separately implemented, but more effective on a PIE
[03:56] <tseng> in the real world, "crafty hackers" don't attack single systems
[03:57] <tseng> ssp is enough to stop your usual scripted botnet attacks
[03:57] <tseng> and canned scriptkiddie stuff
[03:57] <bluefoxicy> tseng:  A worm could be adapted
[03:57] <tseng> real hackers dont go after bluefox.net
[03:57] <bluefoxicy> tseng:  my current "classical attack case" is gaim, because it has an executable stack even on AMD64 and someone can remotely forcefeed you an attack whenever you're online.
[03:57] <tseng> bluefoxicy: it would be hard, and its a small target audience
[03:57] <tseng> its all theory
[03:57] <tseng> not a real threat
[03:57] <bluefoxicy> I do not care about target audience size.
[03:57] <tseng> it would be nice to have
[03:58] <tseng> but not a phase one goal
[03:58] <bluefoxicy> My concern is the theoretical "Ubuntu has 98% of the market share"
[03:58] <tseng> you cant just roll hardened gentoo into ubuntu
[03:58] <bluefoxicy> I am aware.
[03:58] <tseng> we know what a bitch it was to use
[03:58] <bluefoxicy> it wasn't that hard to use
[03:58] <tseng> it took us a year to get Xorg to do anything useful
[03:58] <bluefoxicy> yeah that.
[03:58] <tseng> and you have to mark java, mono, joeuserapp
[03:59] <bluefoxicy> what was hard about hardened gentoo was that the maintainers had to handle the breakage
[03:59] <bluefoxicy> you guys were the one telling X not to pie; and telling SSP not to apply to certain binaries
[03:59] <bluefoxicy> also tseng
[03:59] <bluefoxicy> PaX-style protections can be done via SELinux policy using the execstack, execheap, execmem, and execmod permissions
[04:00] <bluefoxicy> (so says pebenito; Fedora Core 5 somehow does it, it breaks metacity now)
[04:00] <tseng> thats nice
[04:00] <tseng> just adds another level to deal with
[04:00] <tseng> and break things
[04:00] <bluefoxicy> I'm aware.
[04:00] <zul> so anyways
[04:00] <tseng> I am thinking small
[04:00] <bluefoxicy> However, it would be easy enough to tell the SELinux policy to not mess with any given binary
[04:00] <tseng> SSP and NX
[04:01] <tseng> ASLR is pretty safe if you ask me
[04:01] <bluefoxicy> remember Exec Shield type NX gives no guarantees.
[04:01] <bluefoxicy> it's nice in theory, in practice you have a NX stack most of the time
[04:01] <bluefoxicy> but in practice you can never really make long-term predictions about if you're keeping that stack NX
[04:01] <bluefoxicy> and in practice, only the stack is ever NX
[04:02] <bluefoxicy> That being said, you do get something for free almost all of the time
[04:02] <tseng> and it almost always works
[04:02] <bluefoxicy> 'Almost always' works, yes
[04:02] <bluefoxicy> it just doesn't work for when you want to make hard-line security guarantees
[04:03] <bluefoxicy> (not that you ever can really give a "guarantee," we're talking about the Holding problem after all...)
[04:03] <tseng> yes we have seen PaX beaten in the last 2 years also
[04:03] <bluefoxicy> like I said, Holding problem
[04:03] <bluefoxicy> and PaX broke due to implementation bugs
[04:04] <bluefoxicy> of course it maintained the guarantee that the breakage has to be at kernel level, which nobody ever claimed to be absolutely protecting.
[04:04] <tseng> I know all of this, btw
[04:05] <bluefoxicy> yes I know
[04:05] <tseng> :)
[04:05] <bluefoxicy> oh tseng
[04:05] <bluefoxicy> I wrote a patch, not entirely complete but all of the code is there, that lets you adjust entropy in the kernel for mmap() and stack
[04:06] <bluefoxicy> the infrastructure is flexible, I used it to implement control over randomization levels of the stack and mmap() base via a kernel boot parameter
[04:07] <bluefoxicy> however, it's easy enough to make it do per-architecture entropy levels (i.e. 43 bits s/m for x86-64 and 19/8 bits s/m for IA-32) and also drop in SELinux hooks to control entropy levels fine-grained.
[04:07] <bluefoxicy> I have not found a way to convince mainline to eat it yet.
[04:08] <bluefoxicy> I am sure posting the first incomplete, hackish, ugly ass version didn't help.
[04:09] <bluefoxicy> I should remove the command line stuff and just make it per-architecture randomization
[04:09] <bluefoxicy> there is a paper that someone wrote that I can use to justify it, about brute forcing weak ASLR
[04:09] <bluefoxicy> PaX ASLR is considered "weak" in this context
[04:11] <tseng> like I said before
[04:11] <tseng> conceptually weak is alot better than not at all
[04:12] <bluefoxicy> I know
[04:51] <bmonty> bddebian: you are a vi hater?  I never would have guessed, :)
[04:51] <bddebian> Heh, I"m not a vi hater.  I hate emacs more ;-P
[04:52] <bmonty> well there, you and I agree!
[04:53] <bmonty> I'm hooked on vim and gvim
[04:53] <zul> bddebian: let me guess you use pico right? :)
[04:53] <jsgotangco> nano!
[04:53] <zul> same thing basically
[04:53] <bddebian> nano baby :-)
[04:54] <bddebian> Actually emacs can do some very cool shit, it just gets carried away :-)
[04:54] <crimsun> <3 vimdiff -g
[04:54] <zul> bddebian: why am i not surprised :)
[04:56] <bddebian> zul: 'cause you don't love me either? :-)
[04:57] <zul> bddebian: ding ding ding :)
[04:57] <StevenK> I have this feeling mplayer does it.
[04:57] <StevenK> Looks like I'm wrong.
[04:58] <bddebian> Bah, why am I even here..
[04:59] <bmonty> bddebian: cause you love the company of MOTUs?
[04:59] <bddebian> Yeah, I guess that's it :-)
[05:01] <bmonty> ...or did you beat all your video games? :P
[05:01] <bddebian> Nah, I could play Morrowind for centuries I think.  Sheesh that game is HUGE :-)
[05:02] <crimsun> our resident deity has to pass the time while his ponies arrive
[05:02] <bmonty> ponies?
[05:02] <crimsun> yeah, that's the basis of all the "omgponies" rage lately
[05:02] <crimsun> (thanks, barry! ;-)
[05:03] <bmonty> I guess I missed the ponies...damn
[05:05] <bmonty> oh well, time to go to bed....good night everyone
[05:05] <crimsun> 'night
[05:06] <bddebian> gnight bmonty
[05:36] <Erlang> anyone got a clue has to why 'moc' calls would be removed of a KDE application makefile after running automake
[06:05] <Erlang> nvm found it
[06:22] <mooseman089> how do you update the repo list in synaptic?
[06:36] <bddebian> mooseman089: System->Administration->Software Properties?
[06:37] <mooseman089> but where do you find new repos to add to the list?
[06:37] <Erlang> why new repos?
[06:37] <bddebian> Hmm, I always add them by hand
[06:37] <mooseman089> i dont know i thought they changed often or something
[06:38] <Erlang> the repos URL won't change AFAIK.
[06:39] <mooseman089> lol ok
[07:47] <Hobbsee> hey StevenK
[07:47] <Hobbsee> there was afl on?  there you go :P
[07:48] <Hobbsee> hey tuxmaniac
[07:48] <tuxmaniac> hey Hobbsee ..
[07:48] <tuxmaniac> morning all
[08:32] <magnal> why don't i find kynaptic in any repo anymore?
[08:37] <BlueT_> moin :3
[08:39] <magnal> BlueT_: what is moin?
[08:41] <BlueT_> magnal: moin means morning in some language :)
[08:41] <magnal> i thought that was an answer to my question
[08:45] <magnal> what is liblua?
[08:45] <freeflying|away> magnal:  it's ksynaptics not kynaptic
[08:46] <magnal> freeflying|away: i am talking about kynaptic, the kde equivalent of synaptic
[08:46] <magnal> freeflying|away: ksynaptics seems to be something else
[08:46] <magnal> freeflying|away: it used to be there in breezy and it seems dapper includes it nowhere and i wonder why
[08:47] <freeflying|away> magnal: we ship with adept defautly
[08:47] <magnal> freeflying|away: adept is not far as smart as synaptic
[08:47] <magnal> freeflying|away: i don't even understand why it is default
[08:48] <freeflying|away> magnal:  I don't think so
[08:48] <magnal> freeflying|away: ok, i know there are many things that adept doesn't have and synaptic has. now, is there *anything* at all that adept supports and synaptic does not?
[08:49] <BlueT_> freeflying|away: yo :p
[08:49] <freeflying|away> magnal: can you show me any examples
[08:50] <magnal> freeflying|away: adept doesn't support "complete" removal
[08:51] <freeflying|away> that's true
[08:51] <magnal> freeflying|away: now please show me something that adept supports and synaptic does not
[08:52] <Hobbsee> magnal: actually, the latest version has a "purge" button - not sure if that's the repo version though
[08:53] <magnal> freeflying|away: i really am willing to accept it that adept is better or at least as good as synaptic
[08:53] <magnal> freeflying|away: in fact, i wish adept were better, because i like the way it looks
[08:53] <Hobbsee> magnal: do you code at all?
[08:53] <freeflying|away> magnal: :)
[08:54] <magnal> Hobbsee: so do you think adept is just as good as synaptic?
[08:54] <magnal> Hobbsee: why asking if i code? :)
[08:54] <Hobbsee> magnal: no, well...no...neither is as good as apt-get/aptitude.
[08:55] <Hobbsee> magnal: so that you could add to it, if you wish.
[08:55] <magnal> Hobbsee: yes, i love aptitude
[08:55] <magnal> Hobbsee: i was only comparing synaptic to adept
[08:57] <magnal> Hobbsee: any idea what liblua50 is?
[08:58] <Hobbsee> magnal: only a very vague one  - use apt-cache search.
[08:58] <magnal> Hobbsee: it's weird that it looks like a vital dep in the recent dapper updates but.. it is not at all included in the original live (desktop) cd!
[08:58] <magnal> Hobbsee: i simply don't understand how this can happen
[08:59] <magnal> freeflying|away: does adept show a console on installation?
[08:59] <freeflying|away> magnal: it dose
[09:19] <magnal> freeflying|away: does adept show the size of the download on a column?
[09:21] <magnal> freeflying|away: ... or anywhere at all??
[09:21] <freeflying|away> magnal: you may have a try on adept, and you will get it
[09:22] <magnal> freeflying|away: i don't find it
[09:22] <magnal> freeflying|away: this is what i am trying
[09:22] <freeflying|away> magnal: I seldom use adept  :P
[09:23] <magnal> freeflying|away: synaptic is more complete
[09:23] <magnal> freeflying|away: and handy
[09:23] <freeflying|away> magnal: maybe, but I seldom use either
[09:23] <magnal> is adept default on both kubuntu and ubuntu, or does ubuntu use synaptic by default
[09:24] <Hobbsee> mmm...buildign machine = great heater!
[09:24] <Hobbsee> magnal: ubuntu = synaptic by default.
[09:25] <magnal> Hobbsee: does synaptic have an update notifier similar to adept notifier?
[09:25] <Hobbsee> magnal: yes, update manager - i believe it's a separate program
[09:26] <magnal> Hobbsee: thanks
[09:26] <magnal> freeflying|away: and thank you too
[10:46] <magnal> do the new updates for kubuntu include kde 3.5.3?
[10:47] <crimsun> yes, they do.
[10:47] <crimsun> I presume you read http://kubuntu.org?
[10:52] <magnal> crimsun: please explain to me why it wasn't included in the original desktop cd? i mean, it's strange to me that it was released earlier than the desktop cd and yet not on it.
[10:53] <magnal> s/\?/\./
[10:53] <kagou> hi
[10:53] <crimsun> magnal: pool froze before 3.5.3 was released
[10:54] <magnal> crimsun: i see. is 3.5.3 safe enough? or is it preferable to stay on 3.5.2 for now?
[10:55] <BazziR> magnal: does contain some bugs still.
[10:55] <crimsun> magnal: people have reported problems in #kubuntu with 3.5.3, for instance with volumes not being automounted upon insertion
[10:55] <pschulz01> Greetings.. I would like to package up some software but it's been written in quite a complicated way to support multiple platforms. It really needs to 'autotools'..
[10:55] <kagou> is it possible to generate directly a .dsc file without building the package with a debuild -us -uc ?
[10:56] <crimsun> pschulz01: heh, autotools can be beastly, too.
[10:56] <pschulz01> Has anyone hear dealt with upstream that are in a similar state?
[10:56] <_ion> kagou: Look at dpkg-buildpackage(1), keyword: -S
[10:57] <pschulz01> crimsun: Yes, I know.. but..
[10:58] <kagou> _ion: ok, i look at this. thnx
[11:24] <StevenK> kagou: dpkg-source can generate a .dsc directly
[11:27] <kagou> StevenK: thnx i'v founded :)
[11:35] <Seveas> imbrandon_, if you link imbrandon_ to imbrandon both nicks will be cloaked. To do that do this as imbrandon_: /quote ns link imbrandon password_of_imbrandon
[12:04] <Toadstool> heya MOTUs
[12:04] <kagou> i have problems with pbuilder. i try to tell it that it must add /var/cache/pbuilder/result in his search path when it build a package. Of course i'v generated in /var/cache/pbuilder/result a Pacake.gz
[12:04] <kagou> s/Pacake.gz/Package.gz
[12:04] <magnal> which the package that makes it possible to listen mp3s in amarok?
[12:06] <kagou> any ideas ?
[12:30] <BazziR> magnal: thats #kubuntu stuff ;) libxine-extracodecs
[12:40] <imbrandon_> thanks Seveas thought i had done that, but anyhow i did now
[12:41] <magnal> BazziR: btw, there is a huge (and unminimizable) left pannel of amarok's playlist. you can't imagine how much i hate that filescking pannel!! is there *any* way on earth i could MOVE IT AWAY from view (OTHER than recompiling amarok)??
[12:41] <imbrandon_> Seveas: any word on my @ubuntu/member cloak ? ;)
[12:45] <BazziR> magnal: you mean the context thingy?
[12:47] <magnal> BazziR: thanks.. somebody told me how to get it out of view.. it was much simpler than i could imagine. i only looked for it in the preferences
[02:28] <bmonty> hi \sh!
[02:29] <\sh> moins
[02:29] <Hobbsee> hi \sh
[02:30] <tseng> hi
[02:42] <Windkracht8> Hello all, Can someone point me to the easy est way to package a really small program(one executable, that's it)
[02:42] <Windkracht8> Do I have to follow the packaging help in ubuntu or is there a program/tool that can do some stuff for me
[02:44] <bmonty> Windkracht8: the packaging guide has what you need
[02:44] <_ion> I made an example for a friend today: wget -N http://johan.kiviniemi.name/tmp/packaging_rumor.{timing,script} && scriptreplay packaging_rumor.{timing,script}
[02:45] <ogra> _ion, cool idea to use scriptreplay
[02:50] <pschulz01>  Windkracht8: Also, have a look at the dh_make tool.
[02:52] <Windkracht8> My problem is that that's all to compile source and then create a package out of that, but I have already compiled it I just need to place a single executable in a package.
[02:52] <sladen> Posted by Zonk on Sunday June 04, @01:29AM
[02:52] <sladen> from the totally-hawesome dept.
[02:52] <sladen> Books
[02:53] <bmonty> Windkracht8: the process of creating a package includes compiling the source to create the binaries
[02:54] <\sh> Windkracht8: packaging binaries is not debian packages purpose...what you want is something like .bin packages, it's something like a shar archive
[02:54] <pschulz01> Windkracht8: Hmmm... you need a 'Make' script that installs the file into $PREFIX/usr/bin/<executible>.
[02:54] <Windkracht8> ok, that's to bad for me, I use Qt because qmake makes the Makefile for me, I don't know how to do that stuff
[02:55] <pschulz01> Does Qt use 'configure'?
[02:55] <Windkracht8> no
[02:56] <Windkracht8> well, I don't got a make script and don't know how to write one
[02:56] <Windkracht8> so, if I want to package, I'll have to learn that?
[02:56] <pschulz01> Does the Qt makefile support '$DESTDIR' in the 'Make instal' target?
[02:56] <bmonty> Windkracht8: at least some basics of makefiles...the packaging guide has some good info
[02:58] <Windkracht8> pschulz01, not sure, I'm looking now, normally with Qt I write a program and go: "qmake -project"(creates a project file) "qmake"(creates the Makefile) "make" and then I've got an executable.
[02:59] <pschulz01> Windkracht8: How do you 'install' a Qt program?
[02:59] <Windkracht8> copy to /usr/bin
[03:00] <pschulz01> Windkracht8: Is there anything like 'make install'?
[03:00] <Windkracht8> that's kind of what I'm trying to find out now, how to install my Qt program on a different system
[03:00] <pschulz01> Windkracht8: As a user (not root), type 'make install'
[03:01] <Windkracht8> not standard, it gives a 'make: Nothing to be done for `install'.'
[03:01] <bmonty> this would probably be a better discussion for #qt
[03:01] <Windkracht8> but I'm looking at the manual now
[03:01] <Windkracht8> well they send me to #ubuntu because I wanted a .deb
[03:02] <bmonty> Windkracht8: if that is what you want then you need to package the software as described in the packaging guide
[03:02] <Windkracht8> well, I think a .deb is the easiest way for the user
[03:03] <Windkracht8> then they can use dpkg
[03:03] <pschulz01> Windkracht8: Have to go.. good luck.
[03:03] <Windkracht8> thanks
[03:03] <bmonty> Windkracht8: if you are running ubuntu go System->Help->System Documentation and select "Ubuntu Packaging Guide"
[03:04] <bmonty> and with dapper users can use gdebi which will install the .deb file using a GUI
[03:04] <Windkracht8> yes I was looking at that, but I was hoping there would be a easier way to create a package without the need of compiling the program again
[03:08] <sivang> Windkracht8: you actually could, but this is mostly done in cases where the source is not available. Why would you not recompile the program?
[03:09] <Windkracht8> because I do not know how to write a Makefile
[03:10] <Windkracht8> and I think there's no need to recompile, because when I copy the single executable to another computer it works
[03:11] <Windkracht8> I just want to create a .deb so dpkg will put it in the right directory when I got an update
[03:11] <sivang> Windkracht8: what about users of outher architectures?
[03:11] <sivang> Windkracht8: you can't exopect them to just copy over the xecutable, or deb?
[03:12] <sivang> Windkracht8: writing a basic Makefile is not that hard, there\s a nice howto for using autotools to have them create it for you
[03:12] <sivang> Windkracht8: http://www.st-andrews.ac.uk/~iam/docs/tutorial.html
[03:14] <Windkracht8> well, copying over the executable is actually exactly what I want to do. That's what I'm doing at to moment I just want that automated
[04:35] <Hobbsee> bmonty: hehe.  yeah, kinda useful :P
[04:35] <bmonty> I've been trying to get evolution working on a new machine since yesteday afternoon and I was mistyping the hostname of the server :(
[04:36] <Hobbsee> hehe
[04:37] <StevenK> I've mistyped the hostname of a machine in DNS.
[04:37] <StevenK> That was fun.
[04:37] <bmonty> the really bad thing is it is a server on my own network that I use everyday
[04:37] <bmonty> StevenK: doh! yeah, I bet that was frustrating
[04:40] <Hobbsee> night all.
[05:12] <sladen> Finns still ecstatic about Lordi's surprise victory
[05:12] <sladen> EiTB, Spain - May 22, 2006
[05:12] <sladen> ... Tabloids on Monday featured 20-page supplements and posters of Lordi, and the growling monsters' song blared on radios and as background music on TV weather ...
[05:12] <sladen> Finns still ecstatic about Lordi's surprise victory
[05:12] <sladen> EiTB, Spain - May 22, 2006
[05:12] <sladen> oops
[05:12] <sladen> darn the middle button
[06:58] <zul> hmmm...quiet
[06:58] <bmonty> yup
[06:59] <tuxmaniac> zul:  find the reason?
[06:59] <zul> what reason?
[06:59] <tuxmaniac> zul: for channel to be quiet!
[06:59] <zul> oh...yeah...the diety is not here
[07:00] <tuxmaniac> :-)
[07:00] <zul> im going to go have a nap
[07:44] <bmonty> ajmitch: just so you know, ldapsearch with a URI with ldaps in it doesn't work on amd64 with the current package in ubuntu (2.2.26-5ubuntu2)
[07:48] <Toadstool> bmonty_away: uh ? it works for me...
[07:54] <kagou> hi
[07:54] <kagou> hey hub
[07:57] <phanatic> hi people
[07:58] <kagou> hi phanatic
[07:59] <phanatic> hey kagou
[08:20] <bmonty> Toadstool: when you use ldaps://ldapserver.com/ you can connect?
[08:20] <Toadstool> yep
[08:20] <bmonty> and you are using amd64?'
[08:20] <Toadstool> yeah
[08:21] <bmonty> huh, I wonder what the problem is for me then...I can't get the thing to give me any useful error messages
[08:21] <Toadstool> what's the error message?
[08:22] <bmonty> on a packet sniff I see the TCP three-way handshake, and then the server immediately sends a FIN
[08:22] <bmonty> ldap_sasl_interactive_bind_s: Can't contact LDAP server (-1)
[08:23] <Toadstool> the server doesn't support SASL, use the -x option for simple auth
[08:23] <bmonty> the exact same setup works fine on an i386 box on the same network
[08:23] <Toadstool> hum...
[08:23] <bmonty> it does do SASL, if I use a URI with ldap:// it does a SASL bind no problem
[08:24] <bmonty> plus I have other hosts using SASL to get account info from the server
[08:24] <Toadstool> can't help you testing that I don't have SASL on my own ldap server :/
[08:25] <bmonty> Toadstool: so maybe the problem is ldaps+SASL+amd64
[08:25] <Toadstool> yep
[08:25] <bmonty> I need to grab the package from debian and see if that solves the problem
[08:25] <Toadstool> at least it looks like it is something like that since it works without SASL
[08:26] <bmonty> actually it works without SSL
[08:26] <bmonty> SASL works fine
[08:27] <Toadstool> and SSL works fine alone :)
[08:27] <bmonty> Toadstool: yup
[08:30] <bmonty> problem is that libnss-ldap doesn't do SASL encryption :(
[10:39] <Seveas> imbrandon, the cloak has been set 5 minutes before that last message