Findings: The search command will only show "F" if the current candidate is forbidden. $ aptitude search .|grep ^.F iFA libscim8c2a - library for SCIM platform iF scim - smart common input method platform The only way to learn about other cases is to poke via $ grep -c ^Forbid /var/lib/aptitude/pkgstates 4 Let's compare two records,
Package: scim Unseen: no State: 1 Dselect-State: 2 Remove-Reason: 0 ForbidVer: 1.4.7-3 Package: scim-chewing Unseen: no State: 1 Dselect-State: 2 Remove-Reason: 0 ForbidVer: 0.3.1-3 $ aptitude show scim-chewing Package: scim-chewing State: installed Forbidden version: 0.3.1-3 Version: 0.3.2-1 We see the latter has already advanced past the forbidden version. Conclusion: one had better be careful about marking lots of packages forbidden, as once they have been upgraded past the forbidden version, the forbidden marker will still be left in the pkgstates file, so you will have to poke around in it to look for old ForbidVer entries to clear out with the install command, unless you want a lot of cruft accruing in the pkgstates file. Also the only way to find them is via looking in pkgstates itself. No search command will help you. Also, let's purge a package with a forbidden version marker. Now it looks like: Package: flashplayer-mozilla Unseen: no State: 4 Dselect-State: 4 Remove-Reason: 0 ForbidVer: 1:10.0.12.36-0.1 Well how do we remove the ForbidVer marker? According to the manual, we have to use the install command. But we don't want to install it, we want it purged. OK, we have to edit the pkgstates file then by hand. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
