Re: The future of the amd64 port

2006-04-27 Thread cbergmann
Well, I removed the old entries. The problem is clearly introduced by the new entries. Interestingly, although the packages provided by Sarge and Etch should theoretically be the same, they behave differently. I tried this with diff, which is one of the about 20 packages affected on my system:

Re: The future of the amd64 port

2006-04-27 Thread Goswin von Brederlow
[EMAIL PROTECTED] writes: Well, I removed the old entries. The problem is clearly introduced by the new entries. Interestingly, although the packages provided by Sarge and Etch should theoretically be the same, they behave differently. I tried this with diff, which is one of the about 20

Re: The future of the amd64 port

2006-04-26 Thread Olleg Samoylov
I have server with etch debian. After I changed source list to debian.org many packages want upgrade to the same version. Is there any tricks to prevent this? -- Olleg Samoylov smime.p7s Description: S/MIME Cryptographic Signature

Re: The future of the amd64 port

2006-04-26 Thread cbergmann
Hi Olleg, I have just stumbled across a similar (the same?) problem. I am running Sarge with addition of some Etch packages. After switching sources.list from http://ftp.de.debian.org/debian-amd64/debian/ etch main contrib non-free to http://ftp.de.debian.org/debian/ etch main contrib

Re: The future of the amd64 port

2006-04-26 Thread Andrew Schulman
I am running Sarge with addition of some Etch packages. After switching sources.list from http://ftp.de.debian.org/debian-amd64/debian/ etch main contrib non-free to http://ftp.de.debian.org/debian/ etch main contrib non-free, aptitude wants to install about 20 packages from Sarge

Re: The future of the amd64 port

2006-04-26 Thread Stephen Cormier
On Wednesday 26 April 2006 09:40, [EMAIL PROTECTED] wrote: aptitude wants to install about 20 packages from Sarge 3.1r0 again in the identical version to that already installed. Worst of all, after reinstalling these packages, aptitude keeps repeating the request to reinstall with every run!

Re: The future of the amd64 port

2006-04-26 Thread Goswin von Brederlow
Andrew Schulman [EMAIL PROTECTED] writes: I am running Sarge with addition of some Etch packages. After switching sources.list from http://ftp.de.debian.org/debian-amd64/debian/ etch main contrib non-free to http://ftp.de.debian.org/debian/ etch main contrib non-free, aptitude

Re: The future of the amd64 port

2006-04-11 Thread Goswin von Brederlow
Joey Hess [EMAIL PROTECTED] writes: Goswin von Brederlow wrote: Can we list the amd64.debian.net mirrors as sarge only and the debian mirrors as etch/sid? Not sure if the Master file had that info. The sarge installer contains a copy (or 2) of the mirror list, so changing Mirrors.masterlist

Re: The future of the amd64 port

2006-04-11 Thread rickh
contrib non-free deb-src ftp://ftp.us.debian.org/amd64/ testing main contrib non-free Would someone please clarify the exact syntax. -- View this message in context: http://www.nabble.com/The-future-of-the-amd64-port-t1421829.html#a3861420 Sent from the debian-amd64 forum at Nabble.com

Re: The future of the amd64 port

2006-04-11 Thread Matthias Julius
rickh [EMAIL PROTECTED] writes: I should know this, but my choices for sources.list repositories have always been provided by the installation program. Now it seems that I'll have to change it, and I'm not sure what the exact change should be. I'm guessing something like: deb

Re: The future of the amd64 port

2006-04-11 Thread Steffen Grunewald
On Tue, Apr 11, 2006 at 06:19:51AM -0700, rickh wrote: I should know this, but my choices for sources.list repositories have always been provided by the installation program. Now it seems that I'll have to change it, and I'm not sure what the exact change should be. I'm guessing something

Re: The future of the amd64 port

2006-04-11 Thread David Liontooth
rickh wrote: I should know this, but my choices for sources.list repositories have always been provided by the installation program. Now it seems that I'll have to change it, and I'm not sure what the exact change should be. I'm guessing something like: deb ftp://ftp.us.debian.org/amd64/

Re: The future of the amd64 port

2006-04-10 Thread Kurt Roeckx
On Sun, Apr 09, 2006 at 06:47:14PM -0400, Joey Hess wrote: (Please CC me, I forget if I'm subscribed.) At what point should Mirrors.masterlist be updated to remove the amd64.debian.net mirrors and stop listing all the main mirror network as !amd64? As used in the installer? I guess as long

Re: The future of the amd64 port

2006-04-10 Thread Goswin von Brederlow
Kurt Roeckx [EMAIL PROTECTED] writes: On Sun, Apr 09, 2006 at 06:47:14PM -0400, Joey Hess wrote: (Please CC me, I forget if I'm subscribed.) At what point should Mirrors.masterlist be updated to remove the amd64.debian.net mirrors and stop listing all the main mirror network as !amd64?

Re: The future of the amd64 port

2006-04-10 Thread Joey Hess
Goswin von Brederlow wrote: Can we list the amd64.debian.net mirrors as sarge only and the debian mirrors as etch/sid? Not sure if the Master file had that info. The sarge installer contains a copy (or 2) of the mirror list, so changing Mirrors.masterlist for etch will not affect sarge, aside

The future of the amd64 port

2006-04-09 Thread Joerg Jaspert
Hi, as some of you already noticed amd64 is now included in Debian unstable and soon in testing also[1]. This renders parts of amd64.debian.net unnecessary now (but please read on, especially mirror admins the last paragraph, thanks). As inclusion of AMD64 in Debian is now at a point where