[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Obsolete and broken packages



-----BEGIN PGP SIGNED MESSAGE-----

On 29 Sep 1999, Jonas Steverud wrote:

> When I start dselect I get this:
> 
>     --- Obsolete and local packages present on system ---
>     ----- Obsolete/local Standard packages -----
>     ------- Obsolete/local Standard packages in section libs -------
>  *** Std libs     liblockfile0 0.1-6       <none>
>     ----- Obsolete/local Optional packages -----
>     ------- Obsolete/local Optional packages in section base -------
>  *== Opt base     kernel-image 2.0.35-3    <none>
>     ------- Obsolete/local Optional packages in section libs -------
>  *** Opt libs     libjpegg6a   6a-12       <none>
>     ----- Obsolete/local Extra packages -----
>     ------- Obsolete/local Extra packages in section libs -------
>  *** Xtr libs     clanlib0-dis 0.1.16-2    <none>

"Obsolete/local" means that a deb is installed that's not on any of the
sources in your apt sources.list (or equivalent)

> 1. Can I safely purge kernel-image? I have a custom-built kernel
>    2.2.10. (Using kernel-package or whatever the program is.)

Go for it.

> 2. Can I purge the other files or are they bound to turn up in the
>    (near?) future? The reason I ask is I have found other packages to
>    become obsolete and then turn up after a couple of weeks. (My mind
>    might have been tampered with though.)

Sometimes the mirror maintainers just misadjust something, and a package
gets lost. Other times, a package is removed from the distribution for
being obsolete.

Just recently i removed liblockfile0 from my own system when the the final
dependancy on it was removed. IIRC it has been replaced with liblockfile1

clanlib0-display-whateveritis i removed a long time ago, since i never
used that display target. YMMV.

xloadimage still depends on libjpegg6a, so i'm keeping that one on my
system for the moment. Hopefully soon the dependancy is fixed.

> 3. Dselect says that fonty is broken. One of the files
>    (/etc/init.d/fonty) is missing on my system (I didn't want it to be
>    ran so I removed it) and now dpkg can't install and configure it
>    properly. (It was some time since I installed it so I don't
>    remember the exact errormessage.) How can I repair the package
>    and/or tell dpkg the package is not broken? Edit the status-file?
>    (Which says "Status: hold ok half-configured".)

Without the exact error message, i don't know what advice to give...
Others surely have more experience with this than i.


- -- 
  finger for PGP public key.

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: noconv

iQCVAwUBN/KRSb7M/9WKZLW5AQFrBwQAoH2pcwH8AL2R07w5SuhszMJYieS+Zlt2
na2OC9DQpLrBG09FhD2EAYCio6rC28iHGtVrR/ExJOQmcP3NnI99HzKteCoH/lqz
CiFWs+SuRNrjWAIKPt1O3wA8D8RABLtDhX+56hpz0nK+MdhxZjpmT/XTKRb7fF1h
z5ph3G6fIco=
=2xYW
-----END PGP SIGNATURE-----


Reply to: