SEO

I have what was a debian woody install that has been upgraded to a
testing install.
I apt-get update, apt-get dist upgrade frequently with No problems
untill now.
Since a day or so ago the output is _always_ the same.
6 packages are "updated" but are replaced with the same version...
I can still apt-get install whatever i like but these are the only
packages that ever appear in an apt-get dist-upgrade.

I have tried
apt-get update
apt-get upgrade
aps-get clean

How can I solve this and get back to proper dist-upgrades?

Many thanks,

Rage

apt-get output follows:

root@azrael:/home/rage# apt-get clean
root@azrael:/home/rage# apt-get dist-upgrade
Reading Package Lists... Done
Building Dependency Tree... Done
Calculating Upgrade... Done
The following packages will be upgraded:
bash cron enlightenment enlightenment-data klogd sysklogd
6 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 4030kB of archives.
After unpacking 0B of additional disk space will be used.
Do you want to continue? [Y/n]
Get:1 http://the.earth.li testing/main bash 3.0-15 [793kB]
Get:2 http://the.earth.li testing/main enlightenment-data 1:0.16.7.2-1
[2667kB]
Get:3 http://the.earth.li testing/main cron 3.0pl1-87 [58.8kB]
Get:4 http://the.earth.li testing/main sysklogd 1.4.1-17 [56.9kB]
Get:5 http://the.earth.li testing/main klogd 1.4.1-17 [38.3kB]
Get:6 http://the.earth.li testing/main enlightenment 1:0.16.7.2-1 [417kB]
Fetched 4030kB in 5s (704kB/s)
(Reading database ... 85649 files and directories currently installed.)
Preparing to replace bash 3.0-15 (using
..../archives/bash_3.0-15_i386.deb) ...
Unpacking replacement bash ...
Setting up bash (3.0-15) ...

(Reading database ... 85649 files and directories currently installed.)
Preparing to replace enlightenment-data 1:0.16.7.2-1 (using
..../enlightenment-data_1%3a0.16.7.2-1_all.deb) ...
Unpacking replacement enlightenment-data ...
Preparing to replace cron 3.0pl1-87 (using .../cron_3.0pl1-87_i386.deb) ...
Stopping periodic command scheduler: cron.
Unpacking replacement cron ...
Preparing to replace sysklogd 1.4.1-17 (using
..../sysklogd_1.4.1-17_i386.deb) ...
Stopping system log daemon: syslogd.
Unpacking replacement sysklogd ...
Preparing to replace klogd 1.4.1-17 (using .../klogd_1.4.1-17_i386.deb) ...
Stopping kernel log daemon: klogd.
Unpacking replacement klogd ...
Preparing to replace enlightenment 1:0.16.7.2-1 (using
..../enlightenment_1%3a0.16.7.2-1_i386.deb) ...
Unpacking replacement enlightenment ...
Setting up enlightenment-data (0.16.7.2-1) ...

Setting up cron (3.0pl1-87) ...
Starting periodic command scheduler: cron.

Setting up enlightenment (0.16.7.2-1) ...

Setting up klogd (1.4.1-17) ...
Stopping kernel log daemon: klogd.
Starting kernel log daemon: klogd.

Setting up sysklogd (1.4.1-17) ...
Stopping system log daemon: syslogd.
Starting system log daemon: syslogd.

localepurge: Disk space freed in /usr/share/locale: 244K
--


***********************************
* *
* EuropeSwPatentFree *
* *
***********************************

On Wed, 15 Jun 2005 12:47:44 +0100, Rage
<rage@nospam.com> wrote:
> I have what was a debian woody install that has been upgraded to a
> testing install.
> I apt-get update, apt-get dist upgrade frequently with No problems
> untill now.
> Since a day or so ago the output is _always_ the same.
> 6 packages are "updated" but are replaced with the same version...
> I can still apt-get install whatever i like but these are the only
> packages that ever appear in an apt-get dist-upgrade.
>
> I have tried
> apt-get update
> apt-get upgrade
> aps-get clean
>
> How can I solve this and get back to proper dist-upgrades?
>
You could try using aptitude to hold those 6 packages.

Bill Marcum wrote:
> On Wed, 15 Jun 2005 12:47:44 +0100, Rage
> <rage@nospam.com> wrote:
>
>>I have what was a debian woody install that has been upgraded to a
>>testing install.
>>I apt-get update, apt-get dist upgrade frequently with No problems
>>untill now.
>>Since a day or so ago the output is _always_ the same.
>>6 packages are "updated" but are replaced with the same version...
>>I can still apt-get install whatever i like but these are the only
>>packages that ever appear in an apt-get dist-upgrade.
>>
>>I have tried
>>apt-get update
>>apt-get upgrade
>>aps-get clean
>>
>>How can I solve this and get back to proper dist-upgrades?
>>
>
> You could try using aptitude to hold those 6 packages.

Nope, tried holding them, no change.
Unheld them,no change.

Thanks for trying though.

Rage

--
***********************************
* *
* EuropeSwPatentFree *
* *
***********************************

Rage wrote:

> I have what was a debian woody install that has been upgraded to a
> testing install.
> I apt-get update, apt-get dist upgrade frequently with No problems
> untill now.
> Since a day or so ago the output is _always_ the same.
> 6 packages are "updated" but are replaced with the same version...
> I can still apt-get install whatever i like but these are the only
> packages that ever appear in an apt-get dist-upgrade.
>
> I have tried
> apt-get update
> apt-get upgrade
> aps-get clean
>
> How can I solve this and get back to proper dist-upgrades?

Shot-in-the-dark; have you tried the following sequence:

apt-get --fix-missing update
apt-get -f dist-upgrade

This has got me out of similar apt/dpkg package upgrade loops (but not
exactly your situation). Another option is to try a different mirror
in /etc/apt/sources.list and run the twoo commands above again. Good
luck

HTH,

James
--
The amount of time between slipping on the peel and landing on the
pavement is precisely 1 bananosecond.

Centurion wrote:
>
> Shot-in-the-dark; have you tried the following sequence:
>
> apt-get --fix-missing update
> apt-get -f dist-upgrade
>
> This has got me out of similar apt/dpkg package upgrade loops (but not
> exactly your situation). Another option is to try a different mirror
> in /etc/apt/sources.list and run the twoo commands above again. Good
> luck

It appears that the situation has changed today, the only misbehaving
package is now cron....
I suspect it may be due to package maintainers fixing problems, the
problem should be gone soon...

Unfortunately the --fix-mssing and -f switches did not help the cron
problem.

Thanks for trying. :-)

Rage

--
***********************************
* *
* EuropeSwPatentFree *
* *
***********************************