I cannot tell what is wrong with the state of your machine. If I were you I would try the hard way, let remove the package and tried to reinstall it. But be aware, that this might break the system installation.

If purging and reinstalling the two packages via apt-get does not work, I would try the dpkg command to install the new packages (and maybe remove the old ones first) directly.

Code:

dpkg --purge ...

Code:

dpkg --install ...

Maybe you have to --force-... things. See the man page of dpkg. I guess one of the following force-things might become interesting: remove-reinstreq, remove-essential, breaks...

It says thats a dpkg bug. A patch exists and i suspect its uploaded soon. If that happens: Download dpkg.deb and install it with dpkg -i. After that 'apt-get dist-upgrade -f' should fix your problem with e2fsprogs. But please avoid 'apt-get update' until then. Adding more packages to the list of upgradable packages isn't a good idea if the system is in an inconsistent state.

You are "just" unlucky to be hit by it…

_________________MfG. DonKult
"I never make stupid mistakes. Only very, very clever ones." ~ The Doctor

usgs

Post subject:Posted: 05.07.2011, 01:01

Joined: 2010-10-03
Posts: 21

Status: Offline

Solved! I did what DonKult recommended. Before doing what he wrote, I had changed my debian mirror 3 times. Originally I had deb http://ftp.us.debian.org/debian/. Then, about 2 or 3 days ago, I switched to the debian mirror at MIT (in the US). I still had my e2fsprogs troubles with the new mirror so I changed next to the debian mirror at the U. of Chicago (in the US), but no luck. So I made the final switch today to the debian mirror in Canada, http://ftp.ca.debian.org/debian/ . Then I did what DonKult wrote for me. That seems to have worked! The problem ended. Also, I updated my kernel so I now have the latest one, 2.6.39-2.slh.2-aptosid-686. I then didn't have to burn a CD with the latest lite version of Aptosid and install it-- I suppose I still have an older version with the latest kernel. [Yes? Or did today's installation of the latest kernel make my aptosid the latest?] I wonder though why many past d-u's never offered me the latest kernel. Why would that have happened? Would some package/file being held back prevent a d-u from offering the latest kernel or would my now solved problem with e2fsprogs have prevented the latest kernel from being offered to me in a d-u?

I wonder too if the big US holiday (today is Monday, 4th of July, Independence Day here in the US) had anything to do with US mirrors possibly not being updated quickly. Canada celebrated Canada Day on Friday 1 July so perhaps their holiday didn't interfere with my switch today to the mirror in Canada-- I don't know.

[And thanks to all here who were interested in helping me! ]

arwa

Post subject:Posted: 05.07.2011, 07:04

Joined: 2010-09-11
Posts: 183

Status: Offline

Quote:

Or did today's installation of the latest kernel make my aptosid the latest?

If you did a complete dist-upgrade your aptosid installation should be the most recent version, so there is nothing newer.

To automatically get the latest kernel installed, you should have the meta packages installed. e.g. for 64bit:

linux-image-aptosid-amd64
linux-headers-aptosid-amd64

I think for 32bit the names are ending with "-i686" or something like this.

slam

Post subject:Posted: 05.07.2011, 08:29

Team Member

Joined: 1970-01-01
Posts: 607
Location: w3
Status: Offline

arwa wrote:

...To automatically get the latest kernel installed, you should have the meta packages installed. e.g. for 64bit:

linux-image-aptosid-amd64
linux-headers-aptosid-amd64

I think for 32bit the names are ending with "-i686" or something like this.

They are installed by default in Aptosid, if they are missing they have been manually de-installed by the user - so, he really should know.
Greetings,
Chris