Re: dselect/dpkg
On Wed, 3 Feb 1999, rrr wrote:
> > If you are trying to correct a status file, i.e., it thinks this or
> > that package are not installed but they really are, there's no good
> > way to do that that I can think of, and even some reasons never to do
> > that.
>
> Unfortunately, this is what I want to do. i.e. dselect/apt doesn't know
> that (huge download stuff like xbase, gimp, etc) is installed. I thought
> about modifying package-state by hand, but decided against that. I
> thought there would be some script out there that could parse some kinda
> list of what each package actually installs - and validate with a criteria
> of "is EVERY file this package installs, installed?" - if so change
> package-state to "installed (or not-installed)".
Unfortunately, you still have problems with versions of packages with this
solution. I forget if your problem involved wiping out all the status-old
and status-yesterday* files as well. These would seem to help in your
situation. Also, some kind of logging of what has been installed (Ben was
discusing this earlier in January on the devel list) would be helpful to
reconstruct the file. Unfortunately, this doesn't exist yet. Like I was
saying before (but don't practice myself, on my own system at least) this
is what backups are for.
Good luck,
Brandon
+--- ---+
| Brandon Mitchell * bhmit1@mail.wm.edu * http://www.resnet.wm.edu/~bhmit1 |
| Throughout history, UNIX systems have regulary been broken into, beaten, |
| brutalized, corrupted, commandeered, compromised, and illegally fscked. |
| -- UNIX System Administration Handbook |
--
To UNSUBSCRIBE, email to debian-testing-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: