Re: Use of dpkg --set-selections is brain-dead?
- To: email@example.com
- Cc: firstname.lastname@example.org
- Subject: Re: Use of dpkg --set-selections is brain-dead?
- From: "Michael S. Peek" <email@example.com>
- Date: Fri, 01 Sep 2006 08:43:48 -0400
- Message-id: <44F82B04.firstname.lastname@example.org>
- In-reply-to: <email@example.com>
- References: <44F5FD04.firstname.lastname@example.org> <email@example.com> <44F6F055.firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <44F74D26.email@example.com> <firstname.lastname@example.org>
That could very well be I suppose. I've been hacking on my script,
re-run, hack some more, etc...
On Thu, 31 Aug 2006 16:57:10 -0400, Michael S. Peek wrote:
... If I specify: lpr- and cupsys-bsd+ (which conflicts w/ lpr),
then apt-get chokes on cupsys-bsd, saying that it can't proceed because it
conflicts w/ lpr (duh, that's what the lpr- on the command line was for).
It should work. That's the trick I used to play. Now I'm thinking that
your whole package management system is in some kind of weird stage now...
Is there a command to force dpkg to check and rebuild the database?
(This is on a test machine, so I could just reinstall it, but what would
I do on a user's machine where reinstalling is, at best, a last resort?)