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.
Distribution: Debian /Jessie/Stretch/Sid, Linux Mint DE
Posts: 5,195
Rep:
dist-upgrade to Testing --NOT Recommended--
Yesterday I did an dist-upgrade to Debian Testing. I was running a mixed Woody-Sarge-Etch-Sid system, and I wanted a little bit of consistency.
Had I better not done it... This installs KDE 3.4, and that is what I had not expected in Etch, but only in Unstable. I should have checked it before with apt-search showpkg kdesktop
Three errors which I find extremely annoying popped up in the first five minutes I used KDesktop:
- When Konqueror (file mode) reopens when a KDE session is restored, the tree view has disappeared. You have to restart every Konqueror instance again to get it back.
- The "devices" tree has disappeared, and when you click devices it says "protocol not supported: device"
- KMail keeps complaining at about every action that it wants to use KWallet. You cannot store your passwords in KMail anymore, no matter how hard you try.
Oh.. and a fourth one: (In KMail again)
- When you forward a HTML mail, HTML code in the body is being forwarded to the recipient. This means that the recipient actually sees garbage. In the old version it was converted to plain text.
I am wondering what more I'll encounter. I had not expected this in "Testing"
If I am wrong and some of these are not bugs, but just my inability to recognize a proper setting, let me know.
This is not a bug, but still annoying. In the previous KDE, when you moved the mouse over the icons in the panel, the icon would blow up. It was configurable. Now it doesn't do that anymore but if you move your mouse over the icon, a window appears telling you what the function is. The only problems are that the first window is animated and takes about half a minute to appear, and the size is 150x300 pixels.
It seems to me that you're STILL running a mixed machine even after an upgrade because you've probably got some packages stil from sid on your machine. Hmm...
My thought is that you'll still have some applications, libraries, etc. from sid because you can't downgrade to Etch packages if you've got packages from Sid on your computer that are newer.
The title of this thread “dist-upgrade to Testing --NOT Recommended–“ is misleading.
It should probably read “don’t try to dist-upgrade when using a mixed system”. Been there, done that, won’t do it again.
Upgrading “pure” Sarge to Etch is not only easy to do, but you’ll probably be happier with the end result than trying to net-install Etch. The only nonobvious thing you need to do is to convert from xfree86 to xorg before doing the full dist-upgrade.
Starting with “pure” Sarge:
-apt-get install apt-listbugs # Unless you already installed it
-Change apt sources to testing (including security)
-apt-get update
-apt-get install xserver-xorg # Run from a tty, in case X crashes
-reboot
-apt-get install kernel-image-2.6-686 # or smp, etc. to get the latest Etch kernel
-reboot
-apt-get -f install
-apt-get dist-upgrade
-reboot
I am wondering what more I'll encounter. I had not expected this in "Testing"
As far as I understand all encountered by you problems doesn't exist in REAL "Testing" distribution. Your problem is simple - you have broken packages. This is probably because of not downgraded packages and/or old config files (which you may try to use instead of new ones). I know very well what means to have mixed distribution, and what problems may be faced when upgrading. I didn't faced most possible (and sometimes major) problems only because when I'm doing something, I understand what I'm doing. In other word, support (and upgrading) of mixed distribution isn't thing for simple user. You may choose between two choices: simplicity - then use only packages which belongs to your current distribution, and perform upgrade to newer one when needed; or hard way: learn GNU/Linux, learn its structure and architecture, at least up to level of understanding how to do something unusual like mixing different distribution without problem, and how to upgrade without problem. When you learn this, this "hard way" will be "simple" for you. Important thing is: don't panic! This is primary rule. With Linux there is no not solvable problems. And in most cases solving some "hard problems" is very simple, you only need to analyze the situation. First, try to downgrade some (or even all) of your packages to your current "Testing" distribution. This probably will help. Also check your config file. If you are trying to use old ones, then try standart new configs instead - if this is change something from bad to good, then there is some problem with old configs.
Location: 1st hop-NYC/NewJersey shore,north....2nd hop-upstate....3rd hop-texas...4th hop-southdakota(sturgis)...5th hop-san diego.....6th hop-atlantic ocean! Final hop-resting in dreamland dreamwalking and meeting new people from past lives...gd' night.
Distribution: Siduction, the only way to do Debian Unstable
Posts: 506
Rep:
Did you change your /etc/apt/preferences file before trying to dist-upgrade to etch or unstable?
Without proper preperation you will have a mixed system either way...downgradeing or upgradeing.
commenting out all entries not related to etch in sources.list as well.
To maintain a pure testing system,add this ;
Code:
APT::Default-Release "testing";
to the file /etc/apt/apt-conf.Delete whatever else is there or comment out the lines not related.
I think thats it.Same holds true to downgradeing from unstable to testing.or if you want a unstable system follow all but useing unstable as reference.
Edit;
the above smiley is a D with two :'s before it
Last edited by ironwalker; 11-07-2005 at 06:43 PM.
Distribution: Debian /Jessie/Stretch/Sid, Linux Mint DE
Posts: 5,195
Original Poster
Rep:
Wow... I had not expected being flamed like this.
Now, you mean that the broken Konqueror (protocol is not supported: devices) is a result of a mixed system? And so is the password storage of KMail?
I googled for those two errors, and both have a bug report filed.
Are they not "real"?
And please believe me, I do understand a little bit what I am doing. I am not complaining about breaking my system. (Thank gawd it is my home desktop, not my laptop!) I am not a Windoze user who switched two months ago. I have done a dist-upgrade often on a variety of systems (both console and KDE), but that was before KDE 3.4 was released in "testing".
If the community (I mean you ) is convinced that KDE 3.4 does not have the errors I just described, I rest my case, and remove my warning. I had a reason to dist-upgrade the system, but that reason was not to get KDE 3.4. And thanks for the good advice. I am serious.
Yes, and I should have checked apt-cache showpkg. That was the first line in my original post, which pretty much closes the circle, doesn it?
ironwalker: The files /etc/apt/preferences and /etc/apt/apt.conf don’t exist on either my Sarge or Etch systems (even as hidden files), but oddly enough, they do on my fedora systems.
Searching Sarge /etc for files containing “sarge”, “3.1" or “stable” turned up debian_version, issue and issue.net, which all change to “testing/unstable” after the dist-upgrade. It was something I looked at/for before and after the dist-upgrade. In fedora, you install fedora-release-whatever before an upgrade, but I couldn’t find anything like that in debian.
Do you think that the version change is or should be referenced somewhere else?
P.S. jlinkels: You’re not being flamed. I know flaming when I see it and this isn’t flaming. This is purely educational. Every time someone tells me I did something wrong, I usually learn something.
Location: 1st hop-NYC/NewJersey shore,north....2nd hop-upstate....3rd hop-texas...4th hop-southdakota(sturgis)...5th hop-san diego.....6th hop-atlantic ocean! Final hop-resting in dreamland dreamwalking and meeting new people from past lives...gd' night.
Distribution: Siduction, the only way to do Debian Unstable
Posts: 506
Rep:
From my understanding you can just make those files.
I'm running strictly Debian "testing" and should have a minimum of crud in the system as i reinstalled from Sarge a few months ago (after a meltdown using sid) and have been following "testing" since then. I followed the suggestion from "WhatsHisName" to install xserver-xorg and that went well. I'm running the latest kernel.
What i don't understand is that when i do "apt-get dist-upgrade" it wants to remove a fair number (68) of packages, including those for k3b (which i like to have) and abiword, amarok and digikam (which i can do without). Perhaps k3b is considered broken??? ... any thoughts?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.