[06:48] <orbisvicis> how do you build packages like gcc 4.6 and eglibc which appear to depend on each other ?
[06:49] <RAOF> orbisvicis: From an archive which already contains a version of the other :)
[06:51] <orbisvicis> RAOF: example? this isn't the normal source archive ?
[06:52] <RAOF> This is basically a bootstrap problem.
[06:52] <RAOF> You need eglibc to build gcc, but you can't build eglibc without gcc.
[06:53] <RAOF> Since we've already got an archive with gcc in it, though, you can build the new eglibc with the current gcc.  And the next gcc with the current eglibc.
[06:54] <orbisvicis> you mean an archive like a pre-compiled .deb?
[06:55] <RAOF> I mean the current set of packages.  The repositories.
[06:55] <RAOF> To *start* though, you do indeed need to upload some bootstrapping packages; a prebuilt gcc, for example.
[06:57] <orbisvicis> ok I see
[07:01] <RAOF> But you only need to do that once.  After you've got a working compiler, you can use that compiler to build a new compiler :)
[08:13] <dholbach> good morning
[08:22] <geser> good morning dholbach
[08:25] <dholbach> hi geser
[08:34] <ajmitch> morning dholbach, geser
[08:34] <dholbach> hi ajmitch
[08:34] <geser> Hi ajmitch
[10:30] <Laney> morning
[10:31] <sladen> good morning La
[10:31] <sladen> tab-completion-fail
[10:33] <Laney> greetings
[10:33] <Laney> didn't see you at the lecture :-(
[10:33] <sladen> oh you went.  Woo!
[10:33] <sladen> back right, at the top
[10:34] <sladen> and then standing next to the camera man
[10:34] <Laney> did you arrive late?
[10:34] <sladen> "he's changing the tape, so if you're going to say anything important, hold on a moment"
[10:34] <Laney> I was around before for ages
[10:34] <sladen> 5 minutes late.  Missed the free food
[10:34] <Laney> ah
[10:34] <sladen> he was just explaining that he wasn't using slides when I sneaked in
[10:34] <Laney> fair
[11:29] <Laney> what's the difference between an 'attempted' and a 'failed' build, as far as sbuild is concerned?
[11:30] <azeem_> Laney: (AFAIK attempted is an sbuild state, while failed is a buildd state, i.e. the failed attempt has been acknowledged by a buildd admin)
[11:30] <azeem_> not sure that's the case for Ubuntu, though
[11:32] <Laney> azeem_: these are both in mail from my local sbuild
[11:35] <azeem_> Laney: hrm :)
[11:36] <Laney> oh well
[11:37] <azeem_> Laney: right, I think then it's rather attempted == dpkg-buildpackage failed, failed == something else (like apt-get build-dep) failed
[11:37] <Laney> aha
[11:38] <azeem_> from what I've gathered from a quick look through my sbuild logs
[16:45] <dupondje> What things need to be done these days?
[16:45] <dupondje> Can do some work :)
[17:14] <dupondje> bdrung: there ?
[17:14] <bdrung> dupondje: yes, but i shouldn't
[17:14] <bdrung> dupondje: why?
[17:16] <dupondje> audacious-plugins seems uninstallable
[17:16] <dupondje> audacious-plugins: Depends: audacious-plugins-data (>= 3.2.1-1ubuntu1)
[17:16] <bdrung> dupondje: wait. it's stuck in NEW
[17:17] <bdrung> https://launchpad.net/ubuntu/+source/audacious-plugins/3.2.1-1ubuntu1
[17:17] <bdrung> dupondje: you said, that you could do some work?
[17:17] <dupondje> sure :)
[17:17] <bdrung> dupondje: vlc fails on powerpc and kfreebsd: https://buildd.debian.org/status/package.php?p=vlc
[17:18] <bdrung> it would be nice if these are fixed (the proper way to get the fixes upstream)
[17:19] <dupondje> I see if I can do something with it :)
[17:30] <dupondje> bdrung: btw, audacious is still broken :) It tries to load plugins in openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/audacious/Output", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
[17:30] <dupondje> while its in /usr/lib/audacious/
[17:52] <dupondje> https://bugs.launchpad.net/ubuntu/+source/audacious-plugins/+bug/939698
[17:52] <dupondje> could somebody sponsor :) So we can listen to musuc again :D
[17:58] <bdrung> dupondje: done
[17:59] <dupondje> thx
[18:03] <dupondje> bdrung: the VLC ftbfs is fixed already upstream? http://git.videolan.org/?p=vlc.git;a=commitdiff;h=46f74073685b29544dd55b3494f82e77fe9b4b6b
[18:04] <bdrung> dupondje: that's for kfreebsd
[18:04] <bdrung> powerpc is still open
[18:05] <arand> ScottK: Thanks for sponsoring! :D I take it you're looking at redeclipse-data as well?
[18:05] <ScottK> arand: I didn't see a bug for that.
[18:06] <arand> https://bugs.launchpad.net/ubuntu/+bug/934952
[18:06] <ScottK> (I'm looking in the release team queue)
[18:07] <arand> The URT is subscribed there, it seems, do I need to do something else?
[18:07] <ScottK> No.
[18:07] <ScottK> Doing it now.
[18:07] <arand> Yay! :)
[18:26] <dholbach> RTs etc. of FixIt Friday news would be appreciated. :-)
[20:37] <cemc> I would like to rebuild suphp with some options changed. the package in lucid is 0.7.1-1 . what would be the appropriate name to name my package and upload in ppa to not get in trouble with future builds of the package? something like suphp-0.7.1-1+cemc1 would be ok?
[20:42] <micahg> yes, adding +foo is a good option as you'll get any updates from the main repo and know to rebuild your package
[20:43] <cemc> micahg: let's say a security update comes along to suphp-0.7.1-1. what would that name be then?
[20:43] <micahg> 0.7.1-1ubuntu0.10.04.1
[20:44] <cemc> micahg: and 0.7.1-1ubuntu0.10.04.1 > suphp-0.7.1-1+cemc1 right?
[20:44] <micahg> oops, no it's not :)
[20:44] <cemc> it's not?
[20:44] <cemc> hm
[20:44] <micahg> that trick only works on Ubuntu versions :(
[20:45] <cemc> any suggestions?
[20:45] <micahg> so, 0.7.1-1cemc1 should work though
[20:45] <cemc> as long as it's not 0.7.1-1whoo1 ?
[20:45] <cemc> ;)
[20:45] <micahg> right
[20:46] <cemc> what about 0.7.1-1ubuntu0+cemc1 ?
[20:47] <micahg> that would work too
[20:47] <micahg> cemc: you can use dpkg --compare-versions to check these things
[20:49] <cemc> micahg: didn't know that, thanks ;)
[21:19] <at332> Anyone here?
[21:20] <at332> Hello?
[21:20] <broder> !ask | at332
[21:23] <at332> I would like to get started in ubuntu development but I'm not quite sure where to start.  Do you have any suggestions on where I could start?
[22:13] <dupondje> Can you do a powerpc build with pbuilder ?
[22:14] <RAOF> dupondje: If you've got some way to run PPC code, yes.
[22:14] <RAOF> Oooh, and qemus
[22:15] <RAOF> qemu-user-static includes a PPC emulator, so you can build a PPC chroot fairly easily.
[22:15] <jtaylor> if it doesn't crash yes
[22:15] <jtaylor> unfortunatly it does mostly
[22:15] <jtaylor> precise ppc emu is broken (or was two days ago)
[22:16] <dupondje> lets see if we can build ... :)
[22:17]  * RAOF would build a chroot with mk-sbuild --arch=powerpc precise, but that'll build an sbuild system.
[22:17] <dupondje> pbuilder-dist precise powerpc create
[22:17] <dupondje> trying :)
[22:19] <jtaylor> if it works try installing libmagick-dev please )
[22:23] <dupondje> E: Can't mmap an empty file
[22:23] <dupondje> hmz
[22:24] <jtaylor> the oneiric one works
[22:24] <jtaylor> but you can't upgrade
[22:32] <turbotax> anyone have smtp sender for sell pls pm me now ill pay with libertyreserve
[22:47] <dupondje> E: /etc/schroot/chroot.d/sbuild-precise-powerpc: line 10 [precise-powerpc] union-type: Unknown filesystem union type ‘overlayfs’
[22:47] <dupondje> hmz :)