Printable View
Hi,
Does anything particular happen in the Knoppix release cycle when Debian squeeze goes to stable (hopefully this year ;)) or is the Debian testing/stable cycle unrelated?
Just curious.
The custom kernel, the Knoppix specific packages, and the Knoppix-centric boot process seem to make a minefield of upgrading to a full flotilla of squeeze packages.
There was a post not too long ago, where someone reported that they'd done a lot of upgrades, some even beyond what you describe, and they didn't seem to think it was overly problematic. You can easily upgrade whatever you like with Synaptic, though you'll want to add some Squeeze repositories, I'm sure - just be ready to try again if something isn't compatible. If you look in the appropriate forum, I'm sure you'll find the upgrade related discussion.
Cheers!
Krishna :mrgreen:
The nice thing about the thumb drive install: it is already compressed for easy backup to hard disk before booting for an upgrade session.
However, my hard drive install is what I am thinking of heavily upgrading. The drive already has Grub installed for dual booting into Windows. I did something kind of cool. I followed the instructions to install Clonezilla on my hard drive. It worked first time!
Now I have a Clonezilla item on my Grub menu. It makes an iso image of the Knoppix partition in 4 minutes including boot time. Then I reboot into Knoppix for upgrades.
Slow progress. I'll look for that post.
As Homer Simpson would say, DOH!
I forgot to change /etc/apt/apt.conf.d/00knoppix fromto "testing" .Code:APT::Default-Release "stable";
So, during upgrades, dependency resolutions of not-installed stable packages got a preference of 990, while not-installed testing/experimental packages got a preference of 500 and installed testing/experimental packages, 100.
That sure will put a damper on upgrades.
I am certainly not the debian package management expert, but it seems synaptic stores its own settings and configurations, and some of the settings may not be consistent with 'apt' or 'dpkg'.
For example, if I bring up synaptic GUI, click settings->preferences->distribution and check 'prefer version from "testing", the configuration changes is then stored in /root/.synaptic/synaptic.conf.
If one execute command lines to upgrade and install packages, it will be unlikely that the above synaptic configuration will be consulted.
Ahh, I see this is true.
I don't know much about Synaptic. Mostly use aptitude. But I have been using Synaptic more because Knoppix features it.
That file would explain why Synaptic has offered much different dependency resolutions.
Thanks. That should make things far less confusing! :-D