[12:09] <Hobbsee> morning mpt 
[12:17] <mpt> cjwatson, ping
[12:18] <mpt> er, retract contentless ping
[12:19] <mpt> cjwatson, if the text of Ubiquity's navigation buttons will be "move[d]  ... into Ubiquity's own translation infrastructure", does that mean "Forward" can be renamed to "Next"?
[12:38] <mpt> afternoon Hobbsee 
[12:50] <neuralis> lifeless: i'm around now, can chat
[12:53] <lifeless> I'm free next session
[12:53] <lifeless> (in 10 minutes)
[12:57] <uenyioha> hey guys 
[12:57] <uenyioha> what pakages provides the linux header files
[12:57] <uenyioha> ?
[12:57] <popey> linux-headers
[12:57] <popey> surprisingly enough
[12:57] <uenyioha> i can't seem to be able to compile anything in edgy
[12:58] <uenyioha> does linux-headers also provide the socket programming headers?
[12:59] <uenyioha> i recall there's a package that one should install before attemping any c coding in breezy but i've forgotten the name
[12:59] <uenyioha> hoary too
[12:59] <Hobbsee> build-essential
[01:00] <uenyioha> right on...
[01:00] <uenyioha> thanks!
[01:24] <tfheen> ajmitch: you're aware that the kerberize-* specs won't be scheduled until they have a priority?
[01:26] <ajmitch> I thought they had been set to low priority
[01:27] <ajmitch> should they be low or medium?
[01:30] <tfheen> it's discussion, not implementation priority
[10:07] <jc-denton> hi all
[10:07] <jc-denton> ok i know that this is not reall a question for here
[10:07] <jc-denton> but in #ubuntu nobody ha an idea
[10:08] <jc-denton> how can i compile this example on edgy: http://tldp.org/LDP/lkmpg/2.6/html/x121.html ?
[10:08] <jc-denton> i also want to use the kernel shipped with edgy and not a custom kernel
[10:13] <lucas> by clicking "Next" at the bottom of the page
[10:47] <danielinu> Hi, I have a problem installing ubuntu Edgy Eft on a Dell PowerEdge because when I'm at the first reboot during the installation after the "Please stand by while rebooting the system." the computer doesn't do nothing.
[10:49] <abattoir> danielinu: this is a development channel, please try #ubuntu for support
[10:50] <danielinu> abattoir: ok, excuse me but now answer from #ubuntu :(
[10:50] <abattoir> danielinu: be patient, someone who knows might answer :)
[10:51] <danielinu> thanks
[11:20] <sivang> hmm , font's breakup after my last upgrade...
[11:21] <Fujitsu> sivang: Same.
[11:22] <sivang> Fujitsu: I guess some naming / font list have changed or were merged from debian without local patches of ours.
[11:22] <Fujitsu> You're getting some silly ultra-ugly serif font replacing everything?
[11:22] <sivang> Fujitsu: indeed, at least suspend to ram is back ;)
[11:22] <sivang> (was broken since yesterday's noon upgrade)
[11:23] <Fujitsu> I upgraded earlier today, broke upon reboot.
[11:23] <sivang> Fujitsu: you mean you couldn't boot?
[11:23] <Fujitsu> No, the fonts broke on reboot.
[11:25] <sivang> Fujitsu: ah, I just suspended to ram and when I came back the fonts were "broken"
[11:25] <TheMuso> Am I right in guessing from LP that feistyis now open?
[11:25] <Fujitsu> TheMuso: Has been for some days.
[11:25] <TheMuso> Right.
[11:26] <Fujitsu> Got a new something-or-other to upload?
[11:26] <TheMuso> Not yet.
[11:33] <TheMuso> I guess I'd better set up a feisty chroot.
[11:43] <visik7> is possible to have a non stripped vmlinux of the ubuntu kernel ?
[11:45] <visik7> the one of about 34Mb
[01:11] <sivang> hmm, dbus also seems broken to some extent
[01:12] <Fujitsu> How does that exhibit itself?
[01:12] <Fujitsu> Aha:
[01:12] <Fujitsu> dbus_bindings.DBusException: Could not get owner of name 'org.freedesktop.Hal': no such name
[01:13] <Fujitsu> (starting hal-device-manager)
[01:13] <Fujitsu> So, HAL seems to have ceased to exist. Fun.
[01:13] <sivang> or any other hal/dbus using program
[01:13] <sivang> Fujitsu: :)
[01:13] <sivang> let's see if we can fix it
[01:13] <sivang> and maybe later try to fix up the fonts problem :)
[04:01] <bddebian> Howdy
[04:45] <Mirv> should a sync request be done also for packages that are in debian, but not yet in ubuntu?
[04:46] <Mirv> martin pitt's script does seem to work only for packages already existing in ubuntu, or perhaps I'm just using it in a wrong way
[05:19] <Riot777> Hello I got development-like question about Ubuntu
[05:20] <Riot777> is /opt directory made by default after new Ubuntu (not Kubuntu, Xubuntu etc.) install 
[05:21] <_ion> It's a LFS directory, so i guess it should be there.
[05:28] <Riot777> I'm not sure about that if it's made in the installation process of ubuntu can I check it somehow ?
[05:28] <Riot777> any recommendations
[05:28] <Riot777> what scripts should I see etc.
[05:41] <Riddell> Riot777: yes it's made by default
[05:41] <Riot777> ok, thank you
[06:42] <pitti> sfllaw: can you please cross-check https://wiki.ubuntu.com/BugReportingTool ?
[06:46] <sivang> hmm yummy bug reporting tool
[08:19] <thiagocmartinsc> Hi !
[08:20] <thiagocmartinsc> I finish rematering Ubuntu Server Edgy following this doc: https://help.ubuntu.com/community/InstallCDCustomization
[08:20] <thiagocmartinsc> but I miss one thing...
[08:21] <thiagocmartinsc> anyone knows what is ExtraOverride ?
[08:21] <thiagocmartinsc> I see in: apt-ftparchive-deb.conf the line: ExtraOverride "path/to/indices/override.dapper.extra.main";
[08:22] <thiagocmartinsc> but.. I don't run extraoverride.pl < /media/cdrom0/dists/dapper/main/binary-i386/Packages > path/to/indices/override.dapper.extra.main
[08:22] <thiagocmartinsc> this is a problem ?!
[08:42] <thiagocmartinsc> ??
[08:50] <psusi> why on earth does the coreutils source package contain the original .tar.bz2 instead of the extracted source?
[08:51] <_ion> What's the problem with that?
[08:51] <psusi> source packages should contain source code?
[08:52] <psusi> you shouldn't have to extract the package, and then extract the source from the tarball in the package
[08:52] <Mithrandir> psusi: tarball in tarball is fine.
[08:53] <psusi> Mithrandir: fine in what way?
[08:53] <psusi> when you extract a source package, don't you expect to have source code?
[08:53] <Mithrandir> psusi: fine in the way that there's nothing wrong with it?
[08:54] <psusi> it seems odd to have to go through a second extraction... never seen a source package like that before
[08:54] <psusi> and I'm prety sure this package didn't used to do this because I've worked on it before
[08:55] <psusi> what does it gain?  why make things more complex?
[08:55] <thiagocmartinsc> _ion, take a look at the of freetype... there is 3 tarballs inside it.. :-D
[08:55] <Mithrandir> hello-dbs does it, apache1 does it, iirc, random other packages do.
[08:55] <Mithrandir> psusi: make clean is trivially simple.
[08:55] <psusi> what does make clean have to do with it?
[08:55] <_ion> .orig.tar.bz2 isn't allowed IIRC. Am i wrong?
[08:55] <Mithrandir> psusi: debian/rules clean should work.
[08:56] <psusi> should work for what?
[08:56] <Mithrandir> psusi: it should return the package to a pristine condition.  Tarball in tarball makes that easy.
[08:56] <psusi> I'm not trying to clean anything, just look at the source.. .and when I extracted the source package, I got a tarball inside to again extract
[08:56] <psusi> hrm....
[08:56] <psusi> how so?
[08:57] <psusi> how is a clean rule that cleans up first, and then tars up easier?
[08:57] <Mithrandir> the clean target can just be rm -rf build instead of unpatch-handle-failure-cases-make-distclean.
[08:57] <Mithrandir> uh, tars up?
[08:57] <psusi> make clean isn't supposed to discard any changes you have made
[09:01] <thiagocmartinsc> anyone knows if this doc: https://help.ubuntu.com/community/InstallCDCustomization works with Ubunru server Edgy  ?
[09:02] <thiagocmartinsc> i trying to rematerizing the server iso with my extra *.debs files on it... but after boot my CD.. there is lot of md5 errors...
[09:06] <thiagocmartinsc> computer?! hello computer?!
[09:06] <thiagocmartinsc> :-P
[09:07] <psusi> hrm... 
[09:07] <psusi> looks lie coreutils is not built with 64bit file size support
[09:08] <psusi> thiagocmartinsc: you need to update the md5sums.txt list like the wiki page says
[09:10] <thiagocmartinsc> but as wiki says: To build the repository, sign it, and update the MD5SUM file, you can use a script like this:
[09:10] <thiagocmartinsc> I'm use this script .. and it doesn't return any error.
[09:10] <thiagocmartinsc> all goes fine..
[09:12] <thiagocmartinsc> well.. I will revise all from the beginning ... but.. I think I need some help here...
[09:12] <thiagocmartinsc> thanks psusi
[09:14] <mc44> It seems there are a fair few specs that will not get discussed before the end of this conference; Could specs that don't get a chance for discussion at the conference still be approved, or are only specs that are approved at UDS going to be targeted for feisty?
[09:15] <thiagocmartinsc> psusi, maybe the variable "BUILD=/opt/firewall-image-dapper" must be "BUILD=/opt/cd-image/"..
[09:15] <Burgwork> mc44: any spec that gets approved can be worked on, but most specs require some sort of discussion
[09:15] <thiagocmartinsc> because at this time /opt/firewall-image-dapper doesn't exists...
[09:17] <pygi> hey dholbach ogra :)
[09:17] <dholbach> heya pygi
[09:18] <LaserJock> well, any spec can be worked on
[09:18] <LaserJock> some are just "official" goals
[09:19] <LaserJock> at least that's how I think of it
[09:19] <ogra> nope
[09:19] <ogra> "Please check the status of this specification in Launchpad before editing it. If it is Approved, contact the Assignee or another knowledgeable person before making changes."
[09:19] <ogra> thats the header every spec should have
[09:19] <LaserJock> well sure
[09:20] <mc44> ogra: he was talking about implementation I think
[09:20] <ogra> oh, right
[09:20] <LaserJock> but if somebody wants to write a spec and do it, they don't *have* to have it approved before working on it do they?
[09:20] <ogra> implementation is sorted in one of the first distro team meetings after the conference
[09:20] <mc44> I just wanted to know if a spec doesnt get scheduled for discussion by tommorrow whether there was any possibility it would be
[09:20] <mc44> accepted
[09:20] <LaserJock> I'm guessing not
[09:21] <LaserJock> but I don't think that should stop people from working on things
[09:21] <ogra> nah, it shouldnt
[09:21] <ogra> it will just not be "official"
[09:21] <mc44> sure, I was just hoping someone more qualified would work on it @:)
[09:21] <LaserJock> ah, well then that's an issue
[09:21] <Burgwork> I suggest you talk about any spec before you start into it
[09:28] <psusi> that's nice.... extracting the coreutils source package and attempting to immediately debuild -S it back fails
[09:29] <fabbione> have you considered installing the build-deps first?
[09:31] <psusi> you aren't supposed to need build-deps just to package the source
[09:32] <psusi> right?
[09:32] <LaserJock> right
[09:32] <LaserJock> did you install dbs?
[09:32] <mjg59> Erm.
[09:32] <psusi> ding.. search on the missing file just came up with dbs, yea, looks like it needs that ;)
[09:32] <psusi> the clean rule fails
[09:32] <psusi> looking for a dbs file
[09:33] <mjg59> "The Build-Depends and Build-Conflicts fields must be satisfied when any of the following targets is invoked: build, clean, binary, binary-arch, build-arch, build-indep and binary-indep."
[09:33] <LaserJock> apt-get install dbs
[09:33] <psusi> my.... is there a way to surpress the cleaning with debuild -S?
[09:33] <mjg59> -nc
[09:33] <keescook> LaserJock: is that right?  for doing debuild -S for things like l-r-m I needed things from the build-deps...
[09:34] <LaserJock> keescook: it depends
[09:34] <LaserJock> you need stuff for the clean rule
[09:34] <Zdra> hi, I'm managing public computer at university running ubuntu dapper. We have a problem: users lock their screen or click on "switch user" which lock the screen too. I'm currently working on a patch to remove all possibilities in the gnome-session gui to let the user only logout/reboot/halt the computer (no more hibernate, etc). I think this kind of work is needed by every one managing public computers, can this kind of think be 
[09:34] <Zdra> optional and integrated into ubuntu ?
[09:34] <mjg59> It's acceptable for a package to require the build-deps in order for the clean target to work
[09:34] <LaserJock> so the usual things are dpatch, cdbs, etc.
[09:34] <keescook> LaserJock: yeah... and there isn't a distinction made.  :(
[09:35] <LaserJock> keescook: yeah, but the usual suspects are the build helpers so I generally have them around anyway
[09:36] <psusi> shouldn't things that the makefile itself requires be pre-depends?
[09:36] <mjg59> No
[09:36] <mjg59> That's not what pre-depends means
[09:36] <psusi> hopefully this enables 64bit file support...
[09:41] <psusi> holy crap
[09:41] <psusi> I crashed gcc
[09:45] <psusi> can someone set #ubuntu to only allow registered users?  got some flooders
[09:45] <Burgwork> psusi: -ops
[09:46] <psusi> ahh
[10:14] <Zdra> hi, I want to work on a package's patch, but to apply the patch I have to apply previous patches, how can I do it ? and once I modified what I want, how to generate the new patch ?
[10:15] <_ion> What patch system does the package use?
[10:16] <Zdra> I don't know ... I'm not very familiar to package systems
[10:16] <cjwatson> sadly this is all hopelessly non-standard
[10:16] <Zdra> it's gnome-session
[10:16] <cjwatson> you have to figure it out from debian/control and debian/rules
[10:16] <_ion> See the package's build dependencies in debian/control. Is there anything with "patch" in it, or perhaps quilt?
[10:16] <cjwatson> figure out which patch system is in use, that is - and then 'dpkg -L whatever-the-patch-system-package-is' to look for tools
[10:17] <cjwatson> if it's gnome, it's probably cdbs, in which case cdbs-edit-patch will help you
[10:17] <cjwatson> yes, it's cdbs
[10:17] <Zdra> yeah seems to be cdbs
[10:17] <Zdra> I'll try that, thanks :)
[10:19] <_ion> (If it's cdbs + quilt, you might want to use quilt directly instead of cdbs-edit-patch)
[10:24] <Zdra> _ion: cdbs-edit-patch worked just perfect :)
[10:34] <raffael> hi. there is very annoing bug in edgy - libgnomevfs2 package, preventing from using samba shares in totem and rhytmbox. it's been already fixed and commited into gnome cvs. i just recompiled it and it works fine. i guess it's worth updating ubuntu package soon since people are still complaining on it. who is responsible for backporting patches?
[10:35] <fabbione> raffael: you need to file a bug in launchpad and the right people will be notified
[10:46] <raffael> i see it's already fixed in next package release, but targetted for feisty and marked as low urgency
[10:46] <raffael> still not backported for edgy
[10:46] <raffael> what a pity cause it really harms ubuntu image, my friends are dissapointed after upgrade to edgy
[10:47] <LaserJock> it generally needs to be in feisty before it gets backported
[10:50] <raffael> package was created 2 days ago so hopefully you are right
[10:50] <raffael> i'll leave it as is
[10:50] <raffael> thank you for information