On 5/28/07, Jan de Groot wrote:

Hi all,

gcc-4.2.0 and glibc 2.6 have been in testing for a while now. I haven't received many bugs for this one and we still have some small todos open.

Please test these packages very carefully, as these packages are very important for everyones system.

I added a bug-catcher in flyspray: http://bugs.archlinux.org/task/7295 Please add new bugs for anything new you find that isn't linked to that one. If possible, link it to this bug-catcher. I hope to see gcc 4.2.0 and glibc 2.6 in current very soon after the bugs on that list are fixed.

I personally haven't tested them at all. Is it safe to use these for building packages for the repos? This may sound like a stupid question but it scares me away from trying them out. -Dan

Am Dienstag, 29. Mai 2007 11:04:03 schrieb Roman Kyrylych:

I always thought it's a bad idea to build anything for current/extra/unstable/community with packages from testing installed.

:-/

Won't those packages require libgcc 4.2.0 then? AFAIR Jan said about some incompetible exported symbols.

To make sure nothing will break you should use testing on your system and only build packages within chroot-environment. I have four of these: arch32-community, arch64-current, arch64-extra and arch64-community. This way you can be sure that a package from current does not depend on some from extra, too. -- Pierre Schmitz Clemens-August-Straße 76 53115 Bonn Telefon 0228 9716608 Mobil 0160 95269831 Jabber pierre@jabber.archlinux.de WWW http://www.archlinux.de