And even in a simple case line cnee:
qaa:~> aptitude install -s cnee
The following packages will be REMOVED:
libxnee0{u}
The following packages will be upgraded:
cnee{b}
1 packages upgraded, 0 newly installed, 1 to remove and 263 not upgraded.
Need to get 50.4 kB of archives. After
On 2024-02-28 17:28:51 +0100, Sven Joachim wrote:
> No, in this case it is a problem with aptitude's resolver which
> manifests itself due to the following configuration setting:
>
> > Aptitude::ProblemResolver::SolutionCost "safety, removals";
>
> This does cause aptitude to hold apt back by
On 2024-02-29 14:11:41 +0900, Simon Richter wrote:
> Hi,
>
> On 2/28/24 23:49, Vincent Lefevre wrote:
>
> > # aptitude install apt
> > The following packages will be upgraded:
> >apt{b} apt-doc
> > 2 packages upgraded, 0 newly installed, 0 to remove and 180 not upgraded.
> > Need to get 1622
Hi,
On 2/28/24 23:49, Vincent Lefevre wrote:
# aptitude install apt
The following packages will be upgraded:
apt{b} apt-doc
2 packages upgraded, 0 newly installed, 0 to remove and 180 not upgraded.
Need to get 1622 kB of archives. After unpacking 0 B will be used.
The following packages
On 2024-02-28 18:32:20 +0100, Vincent Lefevre wrote:
> OK, but it appears that now, there are *many* other packages in
> a similar situation, and sometimes, aptitude wants to remove a
> potentially important package (see below). The resolution should
> be automatic in case of package rename.
>
>
Hi Vincent,
I'm having similar problems, but I think it may be related to the t64
upgrade that is going on. I get the following when doing aptitude
full-upgrade:
13 packages upgraded, 0 newly installed, 4 to remove and 0 not upgraded.
Need to get 5759 kB of archives. After unpacking 1241
On 2024-02-28 17:28:51 +0100, Sven Joachim wrote:
> On 2024-02-28 15:49 +0100, Vincent Lefevre wrote:
> > So, I suppose that this is also the case for aptitude: if aptitude
> > cannot upgrade just because of a rename, then this is a problem in
> > the involved packages.
>
> No, in this case it is
Control: severity -1 normal
On 2024-02-28 15:49 +0100, Vincent Lefevre wrote:
> Source: apt
> Version: 2.7.12+nmu1
> Severity: serious
>
> While there are no upgrade issues with apt itself (according
> to "apt install -s apt"), aptitude does not want to upgrade
> apt automatically, while this
On 2024-02-28 15:56:56 +0100, Julian Andres Klode wrote:
> aptitude is not our chosen tool for distribution upgrades, as such
> failures there are not release critical for the packages. So while
> this is release critical for aptitude, it's a wishlist bug for apt
> that probably would end up being
