[03:34] <the_Kane> hey
[04:13] <doko> hi tmarble 
[04:14] <tmarble> doko: guten tag!
[04:15] <tmarble> you will be glad to know that I (almost) have a complete Ubuntu mirror built up within the Sun global internet
[04:15] <doko> woot!
[04:15] <doko> how's _07 going?
[04:16] <tmarble> for some reason our rsync's can only do about 2 GB at a time?  
[04:16] <tmarble> in any case it's almost ready
[04:16] <tmarble> the DLJ bundles for _07 were *almost* ready for release.... I have proposed some somewhat aggressive changes to the README
[04:17] <tmarble> to explicitly enable the very creative (and cool) packaging that you have done, doko, for Java
[04:17] <tmarble> as part of the process the committee wanted to wait until we had peer review from a person who, unfortunately is on vacation
[04:18] <doko> ahh, until when?
[04:18] <tmarble> that person is due to return monday 6/19.... However, in the meantime, I have submitted my changes for peer review
[04:19] <tmarble> to one of the senior technical people within the Java organization... he told me that he would be able to begin his review
[04:19] <tmarble> yesterday.. I have not heard anything back yet.
[04:19] <tmarble> I'm sorry for the delay
[04:20] <doko> and any news about the differing class files in rt.jar?
[04:20] <tmarble> doko, you previously mentioned running chroot environments.... I'm wondering if you do this, for example, to test things (prospective packaging)
[04:20] <tmarble> on edgy while running in dapper (for example)
[04:21] <tmarble> no news on rt.jar... I will see what I can do today about that
[04:23] <doko> install dchroot and debootstrap, debootstrap from http://people.ubuntu.com/~doko/
[04:24] <tmarble> so you are saying "yes, that's the way to test java on edgy"?
[04:24] <doko> I think, that's the best way without upgrading your host environment to edgy, which will be broken very soon ...
[04:25] <tmarble> great.. thanks for the clarification
[04:25] <tmarble> btw... are you going to Paris next week?
[04:25] <doko> run: debootstrap edgy /srv/chroot/edgy
[04:25] <doko> yes, I'll be there
[04:25] <tmarble> regrettably this is not the summer I go to France :-(
[04:26] <doko> then in /etc/fstab add
[04:26] <doko> proc            /org/chroot/edgy32/proc         proc    defaults,auto   0 0
[04:26] <doko> devpts          /org/chroot/edgy32/dev/pts      devpts  defaults,auto   0 0
[04:26] <doko>  /home           /org/chroot/edgy32/home         none    rw,bind         0 0
[04:26] <doko>  /tmp            /org/chroot/edgy32/tmp          none    rw,bind         0 0
[04:26] <doko> (using the correct paths ...)
[04:26] <doko> add the edgy chroot in /etc/dchroot.conf
[04:27] <doko> mount -a
[04:28] <tmarble> so is  /srv/chroot/edgy the filesystem on the HOST (e.g. Dapper) where the chroot is to be installed?
[04:28] <doko> then copy /etc/resolv.conf into /src/chroot/edgy/etc/
[04:28] <tmarble> and, if so, how much space do you usually use?
[04:28] <tmarble> FWIW I usually use resolvconf
[04:29] <doko> yes, space: what you install in that chroot ;)
[04:29] <tmarble> hehe
[04:29] <doko> you might want to install libnss-db on both the host and the chroot to keep user information in sync
[04:30] <tmarble> ok, cool
[04:31] <tmarble> [OT]  how is the python packaging thing going with Debian?
[04:42] <doko> going forward ...
[04:42] <tmarble> great