Re: apt-listchanges
On Fri, 23 May 2003 15:10:12 +0200, Hans Gubitz wrote:
>
> I am running testing. The last update broke the system:
>
> 93 packages upgraded, 9 newly installed, 9 to remove and 7 not
> upgraded.
> Need to get 0B/128MB of archives. After unpacking 51.2MB will be used.
> Do you want to continue? [Y/n]
> /bin/sh: line 1: /usr/bin/apt-listchanges: Datei oder Verzeichnis
> nicht gefunden
> E: Failure running script /usr/bin/apt-listchanges --apt || test $? -ne 10
>
> Any hint?
Hello Hans,
With different numbers I had these exact error-messages today as well. I
noticed that apt-listchanges was marked as "to remove" for some reason
(I never tagged it in any way myself before the upgrade), so perhaps it
tripped over itself.
I worked around it by doing
oval:~# dpkg --purge apt-listchanges
The installation of packages then went smoothly. I imagine there are
more elegant solutions, but this worked.
Reinstalling apt-listchanges seems to be a problem right now though:
oval:~# apt-get install apt-listchanges
Reading Package Lists... Done
Building Dependency Tree... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:
Sorry, but the following packages have unmet dependencies:
apt-listchanges: Depends: python-apt but it is not going to be
installed
E: Sorry, broken packages
Bug #193277 against python-apt earlier this week is marked as done and
may offer some further insight. The problem of installing
apt-listchanges on my testing system seems to persist however.
(Sorry for any thread breakage in this post due to incomplete or
incorrect headers. I am not subscribed to the list and am replying from
the news feed to Linux.debian.user manually, and I am uncertain how to
reply correctly from news: to mail: ).
Tony Rowe
Reply to: