Debian massive upgrade trouble

[SiborgZ]

Hi,
lately, I've switched internet connections and finally manage to pursue a full dist-upgrade to my debian distro ( over 800 mb of package updates ).

Anyway, aside from the fact that many updates screwed up my configuration and I'm still trying to fix the whole thing, I'm having problems finishing the actual upgrade with apt-get. I'm receiving the following error:

-----------------
Unpacking kdelibs-data ( from .../kdelibs-data_4%3a3.4.2-2_all.deb) ...
dpkg: error processing /var/cache/apt/archives/kdelibs-data_4%3a3.4.2-2_all.deb (--unpack):
trying to overwrite `/usr/share/doc/kde/HTML/en/common/fdl-license', which is also in package kdelibs3
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/kdelibs-data_4%3a3.4.2-2_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
-----------------

Also, I'm receiving the following error at bootup
"lsmod: QM_MODULES Function not implemented"

I know this problem is related with kernel 2.6 migration and module-init-tools, but I've already updated this package in the past and my kernel already is 2.6.9 and hasn't changed since upgrade.

Would someone have any hints about what to do ?
Thanks a lot

[oz]

If it were me...

I'd backup any important data and config settings, then do a fresh "netinstall" and skip the upgrade process altogether.

[SiborgZ]

naah .. I like challenges

By the way, I fixed part of the problem by moving to 'sarge' tree in sources.list instead of 'testing' ..

[St. Joe]

By the way, I fixed part of the problem....

What problem(s) remain?

[SiborgZ]

Mostly everything

I managed to resolve the module-init-tools warning, but clearly, my modules aren't recognized ...

I receive following errors for every modules

>> FATAL: Error inserting MODULE_NAME : Invalid module format

Moreover, since I had trouble recompiling my kernel (2.6.9). Strangely enough, when compiled under gcc4.0, it produces errors while gcc3.3 works fine. Anyway, I still receive warning about versions mismatch at boot up

>> snd: version magic `2.6.9 SMP preempt K7 gcc-3.3' should be `2.6.9 K7 gcc-3.3`

This warning should be resolved by kernel modules reinstallation, but it doesn't seem to work ...

anyway .. I'm quite spent now
Thanks for the help

[SiborgZ]

Okay, I think everything works now !

I had to recompile my kernel from scratch ( linux 2.6.12 as of now ) ... it stopped for good modules warnings and errors.

Still, I wonder about apt-get and different version trees. Right now, I'm still using sarge distro packages version as followed

deb http://http.us.debian.org/debian sarge main non-free contrib
deb-src http://http.us.debian.org/debian sarge main non-free contrib
deb http://non-us.debian.org/debian-non-US sarge/non-US main contrib non-free
deb-src http://non-us.debian.org/debian-non-US sarge/non-US main contrib non-free

As specified at beginning of thread, using the unstable or testing version ended up in installation errors and/or package mismatch.

Furthermore, the non-us tree of unstable and testing packages ended with
404 not found errors during apt-get update.

Would anyone know causes of such errors and ways to bypass them.
Many packages are only available in testing/unstable version of debian !!

Thanks a lot

[Mystic_Slayer]

Did you do apt-update before you downloaded everything. I think so you did, but still you can never forget to ask.

Try to make your own Kernel, and than upgrade, because you have everything you need in your kernel.
It looks like your kernel doesn´t support everything you need.

Maybe you should try to use a standard Sarge kernel?

[SiborgZ]

yes I did apt-get update before upgrade .. but what troubles me most is the
404 not found errors during the actual apt-get update !!!

Anyway, I could try installing a pre-compiled kernel, but I don't see why it should conflict with packages installation.

[piper_]

Just delete or comment out the non-us entries, they are gone forever so you should *delete* them


Prior to the release of Debian 3.1, United States laws placed restrictions on the export of certain defense articles, which, unfortunately, included some types of cryptographic software. PGP and SSH, among others, fell into this category. It was legal however, to import such software into the US.
To prevent anyone from taking unnecessary legal risks, some Debian
packages were only available from a site in Leiden, The Netherlands, until the release of Debian 3.1, which incorporates this software thanks to changes in United States law.
You should not need the non-US archive unless you are using a version of Debian from before Debian 3.1."

Therefore it is recommended to delete all lines referring to this non-US sources, as they are not relevant any more.

Takin from a thread at Kanotix

[SiborgZ]

That explains it ! Thanks !

I added testing and unstable sources to my apt sources.list and managed to pursue a complete upgrade .. thanks again !