| Author |
Message |
detaos
|
|
Post subject: how to tell when a package has been superseded
 Posted: 23.03.2011, 15:27
|
|
Team Member
Joined: 2010-08-26
Posts: 166
Location: floating in the ether
Status: Offline
|
|
question be example:
Code:
# apt-get dist-upgrade
...
The following packages will be REMOVED:
console-terminus ...
The following NEW packages will be installed:
console-setup-linux ...
...
from reading the `upgrade warnings` forum, console-terminus is being superseded by console-setup-linux. my question is, how was this determined?
this situation comes up rather often in sid and i'd like be able to do the research myself instead of waiting for an answer in the forum. thanks all. |
_________________
#aptosid-art ftw!
(what would cleary do?)
|
| |
|
|
|
 |
|
ibgb
|
|
|
Post subject: RE: how to tell when a package has been superseded
Posted: 23.03.2011, 20:10
|
|
Joined: 2010-09-11
Posts: 42
Status: Offline
|
|
Sometimes you find can it in the changelog of the new package.
In the situation you refer to, the latest entry in the changlog for console-setup-linux includes:
Quote:
* Include Terminus font in the compiled packages. Do not depend, but
conflict and provide console-terminus. New upstream version of the
Terminus font (4.32).
see: console-setup-linux changelog
Not easy to do though, if the package that might include such a change doesn't have a name that seems an obvious candidate and is included in a bunch of other new packages being installed. |
|
|
| |
|
|
|
|
|
DonKult
|
|
|
Post subject: Re: RE: how to tell when a package has been superseded
Posted: 23.03.2011, 22:01
|
|
Team Member
Joined: 2010-09-02
Posts: 485
Status: Offline
|
|
|
ibgb wrote:
Not easy to do though, if the package that might include such a change doesn't have a name that seems an obvious candidate and is included in a bunch of other new packages being installed.
Exactly. Looking at names can give an indication. If the package is no longer available for unstable is a very strong one, but that is most of the time too far away (the process of removal from the archive is a semi-automatic one) from the problems first occurrence. So looking yourself if a package is still build from source can give an indication. Breaks/Conflicts/Provides are pointers you can identify with 'apt-cache rdepends' … but in the end it is experience and "luck". |
_________________
MfG. DonKult
"I never make stupid mistakes. Only very, very clever ones." ~ The Doctor
|
| |
|
|
|
|
|
|
|
Post subject: RE: Re: RE: how to tell when a package has been superseded
Posted: 23.03.2011, 23:04
|
|
Moderator
Joined: 2010-09-11
Posts: 469
|
|
1) intelligent guessing methode...
look the names of newly upgrade/installed package, and see which one looks related to the removed package.
when you have suspected ones, you can check with
$ apt-get -s install <package>
(it's a similation, and can be from user prompt... or can be from root...)
and see if the package will be removed by that...
if guessing doesn't work then,
2) bruto force methode...
try half, or third, or fourth of the packages to be upgraded with
$ apt-get -s install <packages>
(you can use middle button clicking to copy from apt's output)
and see if the package will be removed by that... if so, iterate the methode
untill you can narrow the packages to one or two...
... if the last one suspected package wants to upgrade another package in the "rest", this another package can be the grand cause...
if the packae will not removed... iterate with the rest of packages...
when you find the package, you can compare the dependencies with apt-cache show <package>...
to see the exact reasons... when not clear
1) ask apt-get why. with "-o Debug::pkgProblemResolver=1"
and read the output carefully...
2) ask DonKult for explanation. :) |
|
|
| |
|
|
|
|
|
DeepDayze
|
|
|
Post subject: RE: Re: RE: how to tell when a package has been superseded
Posted: 24.03.2011, 14:01
|
|
Joined: 2010-09-11
Posts: 616
Location: USA
Status: Offline
|
|
Now that last one...just be wary of any answers you get from DonKult   |
|
|
| |
|
|
|
|
|
|
