I know I haven’t written anything for a month or so. This post is merely a public request for gentoo users who use sys-libs/freeipmi to jump in and test the new version otherwise freeipmi will lose the stable keywords and everything that depends on that will be reverted back to ~arch tree soon. If you do not want this to happen, come to the freeipmi bug and post your testing results.
This is yet another amd64 test request :). I consider every X11 stabilization quite critical since it affects pretty much all Gentoo users. So, if you feel bored and you want to do a selfless good deed, do some testing on the following two bugs and report back :)
Update: These packages are now stable on amd64 architecture. Thank you all for your reports
Just a quick post to let you know that we have a new KDE stable candidate. However, as you already know, time is money, and we have neither of these two. So, personally, I will not build or test this version of KDE. If you want to see this version stable in your pretty AMD64 box, grab the list, build it, and report problems. If we get good results, it is more likely for me to spend a night stabilizing it. Otherwise, we will go straight to KDE-4.6.4. As a side note, I would like to thank our amd64 Arch Testers for the wonderful work they’ve done so far :)
Update 2011/06/06: I would like to thank all the users who tested the new KDE. The stabilization will take place on Thursday, 9th of June 2011 @ 23:00 UTC
Recently I joined Gentoo AMD64 team. I always wanted to become an archer and bring the stable branch in a more sane condition. Fortunately, amd64 members are already doing an amazing work, and amd64 stable branch is in a pretty well state. So how do I plan to do the keywording and stabilization?
I am going to use two different ways. First, I will use my old Athlon AMD64 single core / 1,5GB@333Mhz of RAM as a stable platform to do the stabilizations of small packages. This is a quite old CPU so I can’t do much there. On the other hand, I owe a new Phenom X3 machine with 2GB@800Mhz of RAM. However, this machine is running testing Gentoo with plenty of masked packages as well ^_^
So the only choice I had to take advantage of this is to build a stable chroot :)
Those are the steps I followed :) ( Might be wrong, but hey, they worked for me :p )
1 ) mkdir /mnt/gentoo-stable
2 ) Download the latest autobuild from your preferred mirror.
3 ) mv stage3-amd64-20091217.tar.bz2 /mnt/gentoo-stable
4 ) cd /mnt/gentoo-stable && tar xvjpf stage3-amd64-20091217.tar.bz2
5 ) cp -L /etc/resolv.conf /mnt/gentoo-stable/etc && cp -L /etc/passwd /mnt/gentoo-stable/etc && cp -L /etc/shadow /mnt/gentoo-stable/etc 6 ) Adjusted my make.conf 7 ) Created a custom init script for the host machine 8 ) rc-update add gentoo-stable on my host machine 9 ) Done -------------------------------------------------------------------
Now all you need to do is to run
chroot /mnt/gentoo-stable /bin/bash && source /etc/profile && env-update
See? It wont take more than 5′ to have a brand new stable Gentoo :)
ps: As you may have notitced, I am binding my cvs checkout of portage to /mnt/gentoo-stable/usr/portage. This means that the chroot is using my cvs portage to build the packages. Of course, you can always bind your rsync clone of portage by using/
mount -o bind /usr/portage /mn/gentoo/usr/portage :)
Trivial procedure but I had to mention it :)
Disclaimer: I used 32bit chroot guide from Gentoo docs as a tutorial reference :)