On 2016-04-01 16:24:47 +0100, Manuel A. Fernandez Montecelo wrote:
> If you didn't have several versions enabled at the same time, libecm0
> would maybe be detected as "obsolete" and maybe then apt-get
> dist-ugprade would decide to go ahead with the upgrade and remove the
> obsolete package. But
More info about this. In my system, with unstable and the old libecm0
and gmp-ecm installed by hand (so they are "obsolete"):
# apt-get -s install gmp-ecm
...
The following additional packages will be installed:
libecm1
The following NEW packages will be installed:
libecm1
The following
Control: tags -1 + moreinfo
2016-04-01 0:29 GMT+01:00 Vincent Lefevre :
>> If the above is indeed what happens, the end result is not very useful
>> in this particular case; but from aptitude's POV if the user marks for
>> upgrade is because it doesn't want the current
Hi,
On 2016-03-31 21:05:57 +0100, Manuel A. Fernandez Montecelo wrote:
> 2016-03-31 12:55 Vincent Lefevre:
> > ypig:~> aptitude why gmp-ecm
> > i libecm0 Recommends gmp-ecm (= 6.4.4+ds-5)
>
> Side note: If I recall correctly, "aptitude why" explains the current
> state of the system, not
Hi,
2016-03-31 12:55 Vincent Lefevre:
Package: aptitude
Version: 0.7.8-1
Severity: important
On upgrade from the UI, aptitude wants to remove the gmp-ecm package.
The given reason is:
gmp-ecm was installed automatically; it is being removed because all of the▒
packages which depend upon
5 matches
Mail list logo