DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
When I am doing a netinstall of "Etch" AMD64, I only select one package to install after I set up my APT sources. The only package is "Base System". Everything else including "Desktop Environment" is de-selected. When it tries to install the base system - I got an "aptitude failed" error message.
I got this the past 2 days in a row and I don't know what is wrong. There are only 4 sources on the east coast for AMD64 and I am selecting the "csail.edu" source that shows up 1st.
Anyone know why this is happening. I think the package that fails is python and when I rebooted my machine, I get a whole bunch of errors while booting into my system but it evenually does load fine as I am posting from it now via Firefox.
If I saw correctly, in your sources.list you have enabled both Etch (testing) and Sid (unstable) repositories. When you mix these branches you'll probably end with a lot of unmet dependencies, as I believe your case.
If you want to have only Etch, comment the lines that points to Sid (unstable).
It happens with either one and or both. If I just have 'Etch' repos, I get the same thing and if I just have 'unstable', still the same issue. I just happened to screenshot when both were un-commented.
If you never set the pin priorities it's really uncertain as to how the system chose which tree to install packages from, and may have put your system in an unusable state. I don't know of any easy way to tell exactly what the current state of your system is...
I would recommend you re-install and choose either testing OR unstable for your sources, but not both
If you never set the pin priorities it's really uncertain as to how the system chose which tree to install packages from, and may have put your system in an unusable state. I don't know of any easy way to tell exactly what the current state of your system is...
I would recommend you re-install and choose either testing OR unstable for your sources, but not both
As I explained, I did reinstall with just Tesing or Unstable and not both.
As I explained, I did reinstall with just Tesing or Unstable and not both.
I will try again, and hopefully see if it works.
I've never had the installer work with either testing or unstable as the source try using stable do the base install then change the sources.list and do a dist-upgrade to the branch you want.
That sounds about right, although you might start with stable at the net install. Then when you're done, nano /etc/apt/sources.list and change it to testing (not sure why it would matter, but the guy above said he had to do it that way). Then apt-get update && apt-get dist-upgrade.
If I'm not mistaken I don't think you can do a stable install when you are running the AMD64 kernel.. I think the default option is testing.
Your setup looks fine. I was more concerned that you had both repositories uncommented and had done an apt-get update which would have done who knows what to your package list and could have been the cause of apts inability to resolve dependencies for the package you were trying to install.
and the final command would be /etc/init.d/kdm start
That's a pretty bare system but theres nothing wrong with that..
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.