Thanks for the info, it does look like the status and available files are out of sync. Not sure why this should have occured as I used 2.2 test 1 CD set and apt-get'ed the test 3 updates (this worked fine). I got the offical 2.2 on CD, install these (agian via apt) and these get out of sync. I've looked to see if there is method to get apt (or something offical) to resync these, but can't see one.
I'll hack around with this for a bit (if I get this fixed I'll post my solution) but if anyone knows a easy solution that would save me some time. cheers for help chaps Jon On Sun, Sep 24, 2000 at 11:46:32PM -0600, Bruce Sass wrote: > On Sun, 24 Sep 2000, Debian User wrote: > > just upgraded my system from a mix of Test 1 and Test 3 to the full 2.2 > > release. > > Noticed that I now appear to have alot of "Obsolete/local Optional packages" > > now showing in dselect. According to the docs the best way to get rid of > > this > > (as these packages are the current versions) is to run apt-get [packages] or > > remove and reinstall them. apt-get doesn't seem to work, tells me that the > > most up to date version of installed (this error didn't supprise me). > > Anyone > > got a easier hack to do this via a script of something, or any ideas as to > > how > > I can sort this out. > > I can think of two likely scenarios that would give these symptoms... > > dselect marks any package that appears in /var/lib/dpkg/status > and not in /var/lib/dpkg/available, as "Obsolete/local"; if packages are > installed from archives not pointed to by /etc/apt/sources.list the > "apt-get update" (or whatever the correct syntax is for updating the > local list of available packages) command would build an incomplete > Packages DB. > > dselect uses the "status" and "available" text files, apt uses something > else (/var/apt/cache, ..., iirc). I would assume that using the apt > method(?) in dselect automatically syncs the two Packages DBs - is there > an apt command to force that syncing? > > > later, > > Bruce >
