Re: amd64 sources.list file

2005-09-22 Thread Kaare Olsen
On Wed, 21 Sep 2005 21:07:04 -0700
lordSauron <[EMAIL PROTECTED]> wrote:

> basically I should reinstall using an amd64 disk?

Yes, and don't forget to save any data you want to keep if you're
installing over your current configuration.

-- 
Regards, Kaare - 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: amd64 sources.list file

2005-09-21 Thread lordSauron
basically I should reinstall using an amd64 disk?



Re: amd64 sources.list file

2005-09-21 Thread Cyril Chaboisseau
 On Sept. 21st, Kaare Olsen wrote:
> > okay... I think I now have figured out why the system refuses to
> > install amd64 packages, perferring the i386 packages: it still thinks
> > it's an i386 system.  
> 
> In addition to what Len Sorensen said on a doing a fresh install, here's
> how I've successfully "upgraded" a couple of i386 systems to the amd64
> port without having to set everything up again.
> 
> Beware, the following general steps are from memory:
> 
> - Run "dpkg --get-selections > my_installed_packages" on your current
> i386 system.
> 
> - Store /etc/*, /home/*, /var/log/*, /var/www/*, and whatever else you
> want to keep (don't forget the newly created my_installed_packages file)
> in a safe place, e.g. on another drive where you can get at them from a
> fresh installation.
> 
> - Check again that you haven't forgotten anything important on your
> current system.
> 
> - Install sarge using a netinst CD image; i.e. the fresh install Len
> Sorensen mentioned.
> 
> - When the fresh install is finished, copy the my_installed_packages
> file to the system.
> 
> - Remove architecture dependant packages from your my_installed_packages
> file (e.g. kernel-image, linux-image, alsa-modules ...).  Apt may refuse
> to install them, however, so this step may be unnecessary.
> 
> - Run "dpkg --set-selections < my_installed_packages" to mark your
> previously installed packages for installation.
> 
> - Run e.g. "apt-get update ; apt-get upgrade" (possibly also "apt-get
> dist-upgrade).  Aptitude may do a better job of this.

and a little apt-get dselect-upgrade
:-)

http://www.debian.org/doc/manuals/quick-reference/ch-package.en.html


this techniques works really great but expect that a few packages will
remain unavailable in the new arch (amd64) which is not problematic at
all

'still, from time to time re-run the dselect-upgrade and you might find
that yet another package has found it's way to AMD64

lately there was valgrind and qemu

few more to come very soon...

-- 
Cyril Chaboisseau


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: amd64 sources.list file

2005-09-21 Thread Kaare Olsen
On Wed, 21 Sep 2005 12:15:18 -0700
lordSauron <[EMAIL PROTECTED]> wrote:

> okay... I think I now have figured out why the system refuses to
> install amd64 packages, perferring the i386 packages: it still thinks
> it's an i386 system.  

In addition to what Len Sorensen said on a doing a fresh install, here's
how I've successfully "upgraded" a couple of i386 systems to the amd64
port without having to set everything up again.

Beware, the following general steps are from memory:

- Run "dpkg --get-selections > my_installed_packages" on your current
i386 system.

- Store /etc/*, /home/*, /var/log/*, /var/www/*, and whatever else you
want to keep (don't forget the newly created my_installed_packages file)
in a safe place, e.g. on another drive where you can get at them from a
fresh installation.

- Check again that you haven't forgotten anything important on your
current system.

- Install sarge using a netinst CD image; i.e. the fresh install Len
Sorensen mentioned.

- When the fresh install is finished, copy the my_installed_packages
file to the system.

- Remove architecture dependant packages from your my_installed_packages
file (e.g. kernel-image, linux-image, alsa-modules ...).  Apt may refuse
to install them, however, so this step may be unnecessary.

- Run "dpkg --set-selections < my_installed_packages" to mark your
previously installed packages for installation.

- Run e.g. "apt-get update ; apt-get upgrade" (possibly also "apt-get
dist-upgrade).  Aptitude may do a better job of this.

- Copy your stored directories and files back, taking care when
restoring /etc/* as there may be architecture dependant settings.

You should be able to performed the last two items in the reverse order,
but I don't remember in which order I did this.

Good luck!

-- 
Regards, Kaare - 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: amd64 sources.list file

2005-09-21 Thread Lennart Sorensen
On Wed, Sep 21, 2005 at 12:15:18PM -0700, lordSauron wrote:
> okay... I think I now have figured out why the system refuses to
> install amd64 packages, perferring the i386 packages: it still thinks
> it's an i386 system.  So, I spent about 3 hours hunting down where I
> could change what the system thinks of itself, and found nothing. 
> Basically, I need to change the system such that it will install the
> amd64 packages instead of the i386 ones (all the errors were
> apparently b/c the amd64 mirrors didn't have a package list for i386
> packages, which was what apt and kynaptic and kpackage were all
> looking for (I think through dpackage, but I'm still not sure...))
> 
> So, does anyone know what to do?  I'm pretty much stumped myself, so
> any input, even a pointer to a file I should su root / nano would be
> great.  Thanks for listening to my pathetic newbie problems, and have
> a great day!

Switching architecture on an installed system is NOT supported at this
time.  Best you can do is debootstrap onto another partition the other
architecture and then reboot to that partition, or better yet: do a
fresh install.

Len Sorensen


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: amd64 sources.list file

2005-09-21 Thread lordSauron
okay... I think I now have figured out why the system refuses to
install amd64 packages, perferring the i386 packages: it still thinks
it's an i386 system.  So, I spent about 3 hours hunting down where I
could change what the system thinks of itself, and found nothing. 
Basically, I need to change the system such that it will install the
amd64 packages instead of the i386 ones (all the errors were
apparently b/c the amd64 mirrors didn't have a package list for i386
packages, which was what apt and kynaptic and kpackage were all
looking for (I think through dpackage, but I'm still not sure...))

So, does anyone know what to do?  I'm pretty much stumped myself, so
any input, even a pointer to a file I should su root / nano would be
great.  Thanks for listening to my pathetic newbie problems, and have
a great day!



Re: amd64 sources.list file

2005-09-18 Thread lordSauron
well, the whole [this|that] is programmer for "this" OR "that", so I
just assumed that meant that you could paste that into sources.list
and it would be like (overly simplified: )

deb this
deb that

so if that's the problem then I can totally see that...  BTW if you
ever see the little pieplate sign (|) that's programmer for OR in most
languages I know of, and && is AND.  So if you see me doing weird
notations like that, just remember that programmers rule the internet
- always have, and most likely always will.  One programmer isn't
going to change diddly-squat, but collectively...



Re: amd64 sources.list file

2005-09-18 Thread Greg Madden
On Sunday 18 September 2005 02:22 pm, lordSauron wrote:
> okay.  I've been happily screwing around with my sources.list file,
> and I'm positively baffled.  None of the amd64 servers appear to work
> for me.  Thus, I'm starting a whole thread for the discussion of what
> looks to become a nice, big, fat, hairy, penguin-eating problem.
>
> My big question: what servers for both packages and sources to those
> packages will work for me (your average Californian).  I've been
> working a little bit with netselect, and that was certainly
> interesting for it to find what appeared to be some of the most
> obscure servers in existance.  So, I'm just going to paste the entire
> contents of the sources.list file I have right now, and let people
> yell at me for doing boneheaded things (if something wasn't working
> or I didn't want it, I commented it out instead of deleting it - a
> very good practise most of the time)
>
> === /etc/apt/sources.list ===
> # the main Debian packages.
> # deb http://204.152.191.7/debian/ stable main contrib
> # Uncomment the deb-src line if you want 'apt-get source'
> # to work with most packages.
> # deb-src http://204.152.191.7/debian/ stable main contrib
>
> deb [ftp|http]://mirror.espri.arizona.edu/debian-amd64/debian/
> [sarge|sid] main contrib
> deb-src [ftp|http]://mirror.espri.arizona.edu/debian-amd64/debian/
> [sarge|sid] main contrib

I use this one, I don't know what the {ftp\http} is about, but mine 
works with http only in the source, and picking only one version, sid 
or sarge. Use a browser to see if the address's are online and what is 
available.

>
> deb [ftp|http]://debian.csail.mit.edu/debian-amd64/debian/
> [sarge|sid] main contrib
> deb-src [ftp|http]://debian.csail.mit.edu/debian-amd64/debian/
> [sarge|sid] main contrib
>
> # deb http://amd64.debian.net/debian-amd64/ [sarge|sid] main contrib
>
> # deb http://mirrors.geeks.org/debian/dists/sid/ contrib main
> non-free
>
> # deb http://debian.csail.mit.edu/debian-amd64/debian/ testing main
> contrib non-free
> # deb http://debian.csail.mit.edu/debian-amd64/debian/ unstable main
> contrib non-free
>
> # the non-US Debian packages.
> # deb http://debian.tu-bs.de/debian-non-US/ stable/non-US main
> contrib # Uncomment the deb-src line if you want 'apt-get source'
> # to work with most non-US packages
> # deb-src http://debian.tu-bs.de/debian-non-US/ stable/non-US main
> contrib === /etc/apt/sources.list ===
>
> That's what I have right now.  Any help would be greatly appreciated.
> I'd like to stop running everything in i386 emulation mode - even
> though the processor can natively do everything in x86, I'd still
> like to use the extra 32 bits - just for the heck of it, if you will.
>  Plus I'd love to help develop for Linux, or even possibly help
> compile packages or that sort of a thing once I can lock down the
> situation and get eveything nice and happily 64-bit.
>
> Have a nice day!

-- 
Greg Madden


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]