Re: testing buildd && gcc-3.4 transition
Hi, On Wed, Aug 04, 2004 at 03:21:08PM -0300, Peter Cordes wrote: > I don't plan to boot pure64 on these machines soon, just use it as a > chroot, so does it make sense to just change my sources.list and apt-get > dist-upgrade from the gcc-3.4 archive, or should I re-install from scratch? > (Or should I apt-get install --reinstall everything from the new archive > with a clever shell command?) I have not tried it, but upgrading should work, like it did for the gcc-3.2 transition in sid some years ago (after woody released). But I would wait until the archive is complete, there are still some hundred packages missing compared to pure64. Greetings Frederik Schueler -- ENOSIG
Re: testing buildd && gcc-3.4 transition
On 04-Aug-04 15:21, Peter Cordes wrote: > On Tue, Aug 03, 2004 at 02:14:59PM +0200, Goswin von Brederlow wrote: > > deb http://debian-amd64.alioth.debian.org/gcc-3.4 sid main contrib non-free > > I have a pure64 chroot that I set up based on John's tarball a long time > ago. I've apt-get dist-upgraded it a few times from alioth more recently, > but it's been a month since I touched it now, I think. > > I don't plan to boot pure64 on these machines soon, just use it as a > chroot, so does it make sense to just change my sources.list and apt-get > dist-upgrade from the gcc-3.4 archive, or should I re-install from scratch? > (Or should I apt-get install --reinstall everything from the new archive > with a clever shell command?) Probably all of the three mentioned methods will work (I tried all of those methods myself and did not find any problems). To be on the safe side, a reinstall from scratch is certainly the best choice - followed by 'apt-get install --reinstall everything'. However, there are still about 400 packages missing from the amd64/gcc-3.4 archive and it will take a few more days to (fix and) upload those. Mixing the gcc-3.3 and gcc-3.4 based archives is NOT recommended. So if you need one or more of those missing packages, it will probably be better to wait a few more days. BTW, booting directly into pure64 or amd64/gcc-3.4 is working quite well. There is no need to use i386 and install amd64 in a chroot anymore. Regards Andreas Jochens
Re: testing buildd && gcc-3.4 transition
On Tue, Aug 03, 2004 at 02:14:59PM +0200, Goswin von Brederlow wrote: > deb http://debian-amd64.alioth.debian.org/gcc-3.4 sid main contrib non-free I have a pure64 chroot that I set up based on John's tarball a long time ago. I've apt-get dist-upgraded it a few times from alioth more recently, but it's been a month since I touched it now, I think. I don't plan to boot pure64 on these machines soon, just use it as a chroot, so does it make sense to just change my sources.list and apt-get dist-upgrade from the gcc-3.4 archive, or should I re-install from scratch? (Or should I apt-get install --reinstall everything from the new archive with a clever shell command?) -- #define X(x,y) x##y Peter Cordes ; e-mail: X([EMAIL PROTECTED] , des.ca) "The gods confound the man who first found out how to distinguish the hours! Confound him, too, who in this place set up a sundial, to cut and hack my day so wretchedly into small pieces!" -- Plautus, 200 BC
Re: testing buildd && gcc-3.4 transition
Jonas Meurer <[EMAIL PROTECTED]> writes: > hello, > > i'm interested in the latest plans on creating a testing buildd, and if I started the archive creation yesterday. Currently alioth does a GID renumbering so I can't check its progress. It might even have been killed or completly mess up now. But it can be easily restarted. Yesterday pure64 has slightly over 7000 source packages in sync with sarge and successfully compiled. That leaves about 1100 source packages with newer versions, patches, dep-wait, failed or not-for-us. So it doesn't look too bad for sarge amd64. > this will be realized. i like the idea, as it provides a somehow better > and more secure distribution for (just as example) production servers, > that don't like to be rebooted or unavailable in any case every now end > then, because many people rely on them. We need at least one person, better two, that can take over the job of a security team once sarge is released. Mainly that means making sure the sarge buildd builds any security releases from debian. But there might be amd64 security bugs or bugs in packages we have to patch for sarge. In those cases a new patched source has to be made. > second, i'dd like to know how gcc transition from 3.3 to 3.4 goes on, > and if it will superseed the old 3.3 archive soon. > when 3.4 includes much better amd64 support, that would be interesting > for all amd64 port users. About ~1000 sources failed to build and none are left needs-build. A lot are just the same failed, dep-wait and not-for-us as pure64 has. On top of that all the tiff depending packages have failed I think draging down all gnome builds too. I don't think its wise to switch before the tiff transition is done. Too many failed packages. > i'm asking as we have a dual cpu opteron system that will get setup as > a server soon, and therefore a amd64 testing tree > .oO(with gcc 3.4 compiled)Oo. would be very useful. > > bye > jonas The archive is on alioth. When installing just choose deb http://debian-amd64.alioth.debian.org/gcc-3.4 sid main contrib non-free I'm not sure anyone has tried this yet and reports are welcome. MfG Goswin
testing buildd && gcc-3.4 transition
hello, i'm interested in the latest plans on creating a testing buildd, and if this will be realized. i like the idea, as it provides a somehow better and more secure distribution for (just as example) production servers, that don't like to be rebooted or unavailable in any case every now end then, because many people rely on them. second, i'dd like to know how gcc transition from 3.3 to 3.4 goes on, and if it will superseed the old 3.3 archive soon. when 3.4 includes much better amd64 support, that would be interesting for all amd64 port users. i'm asking as we have a dual cpu opteron system that will get setup as a server soon, and therefore a amd64 testing tree .oO(with gcc 3.4 compiled)Oo. would be very useful. bye jonas
