On giovedì 11 ottobre 2007, Otavio Salvador wrote: > Federico Giacomini <[EMAIL PROTECTED]> writes: > > > Why is etch still linked to the unstable distribution? How can I chroot > > into etch? > > This script is used by debootstrap as a "recipe" how to make the > chroot and currently there's no difference between them all except the > package versions and dependencies that are dynamicaly resolved. > > To chroot into etch you'd need to create a chroot using debootstrap > (man debootstrap) and then use chroot command to change to it (man > chroot). >
ok, thank you. Now I'm having problems in installing nearly any new packages while jailed within etch: # apt-get install dpkg-dev Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. Since you only requested a single operation it is extremely likely that the package is simply not installable and a bug report against that package should be filed. The following information may help to resolve the situation: The following packages have unmet dependencies: dpkg-dev: Depends: dpkg (>= 1.13.20) but it is not going to be installed Depends: perl5 Depends: perl-modules but it is not going to be installed E: Broken packages here is my /etc/apt/sources.list: deb http://ftp.debian.org/debian etch main contrib #non-free deb-src http://ftp.debian.org/debian etch main contrib #non-free deb http://security.debian.org/ etch/updates main contrib #non-free deb-src http://security.debian.org/ etch/updates main contrib #non-free what may be missing or misconfigured?