Thanks grizzler. I thought that might be the case but felt it necessary to ask the question.

I must admit that, as a "serial upgrader", I keep my distros running until I eventually retire them to use a different one. I do worry from time to time about the new config files that sometimes arrive with newer software and think I might be missing out on some wonderful new feature.

Still, I firmly believe in "if it ain't broke don't fix it" and so I just keep bumbling along with my ancient config files...

Thank you very much Schoelje I think it worked! I will put your advice in my notes on how to fix a problem like this for the future.

Of course it told me the default was to keep my current version but I knew that was wrong so replaced it with the " install the package maintainer's version" after running the "D" option to show the diff.

Gonzalo_VC: The repos you have listed are the same ones I currently use for my SolydX 32-bit install. As far as I know, they have not been superseded.

Note that, now Jessie is the new Debian Stable, the official SolydXK edition has dropped the "Home" suffix as this is the only edition until the Enthusiasts Edition (based on Debian Testing) is released by the community.

Zill wrote:Gonzalo_VC: The repos you have listed are the same ones I currently use for my SolydX 32-bit install. As far as I know, they have not been superseded.
Note that, now Jessie is the new Debian Stable, the official SolydXK edition has dropped the "Home" suffix as this is the only edition until the Enthusiasts Edition (based on Debian Testing) is released by the community.

Yea, thanks, Zill.
I read another part of this forum and am doing the dist-upgrade to Jessie... wish me luck I don't know what to expect after upgrading and rebooting (will the system look like SolydXK, yet?).
It's a netbook from one of my "offspring" (people I recommend and install them GNU/Linux). The Atom processor, even if some models are dual-thread, rather run 32 bits than 64 bits. Hence, I have to stick to 32 bits Debian here, and not the newer SolydXK versions, that are 64 bits only.

imagemagick (8:6.8.9.9-1) unstable; urgency=high
Obsolete config scripts (Magick-config, MagickCore-config,
MagickWand-config, Wand-config and Magick++-config) are
not multi-arch safe and thus have been removed from /usr/bin.
.
Moreover, these scripts are superseded by pkg-config
facilities.
.
However as a courtesy to our users, these scripts have
been moved to
/usr/lib/$DEB_HOST_MULTIARCH/ImageMagick-$VERSION/bin-$QUANTUMDEPTH/
where $DEB_HOST_MULTIARCH is the multi-arch triplet and
$QUANTUMDEPTH is the current quantum depth. $VERSION is the upstream
version without the revision number.
.
Please note that these scripts will be definitively removed after
jessie.
-- Bastien Roucariès <roucaries.bastien+debian@gmail.com> Sun, 19 Oct 2014 12:12:20 +0200
amd64-microcode (2.20141028.1) unstable; urgency=medium
This release drops support for automatically applying microcode updates
without a reboot. The microcode updates can still be applied without a
reboot through manual action of the system administrator.
:

Gonzalo_VC: You might also like to remove packages from deb-multimedia.org as the current SolydXK ISOs have replaced these with packages directly from the Debian repos.

Grizzler has kindly produced a script for this (Remove deb-multimedia.org - dmo) which I have used and worked well for me but first you do need to check which multimedia packages you currently use to make sure you find suitable replacement(s). For example, ffmpeg has been replaced by avconf and this can cause problems in certain circumstances.

Thanks, guys, for I have a kind of broken / looping upgrade. Some packages take more than half an hour to install, and in the end, I keep receiving the message from my previous post. I'm planning of wiping the hard drive if I cannot resolve this

Hey All, I'm pretty late to this upgrade. I installed solydK about a year ago but I ended up letting the install languish. So it's still running mid 2014 packages. Anyway, I updated my apt sources.list and did an apt-get update but now I see...

Fetched 15.0 MB in 8s (1,815 kB/s)
Reading package lists... Done
W: There is no public key available for the following key IDs:
9D6D8F6BC857C906
W: There is no public key available for the following key IDs:
7638D0442B90D010
W: There is no public key available for the following key IDs:
7638D0442B90D010
NO_PUBKEY CBF8D6FD518E17E1

I have not begun the dist upgrade yet. Any help would be appreciated! Thanks!