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
Also even if at the 31st choice we finally get to keep all,
the next day we will still be facing the same problem.
Yes, usually it is just a temporary situation. Upstream was just in the
middle of sending out some packages, etc. But even so,
not for one minute should users be left digging for the
Package: aptitude
Version: 0.8.13-5+b1
Severity: wishlist
In #1064958 we see the usual choice after choice.
Well how about number each choice as it is shown to the user?
With letters, so as not to confuse them with the numbers being shown.
Not just for debugging purposes, but for everyday use.
There it finally was, way down at like the 31st choice.
Accept this solution? [Y/n/q/?] n
XX. The following actions will resolve these dependencies:
Keep the following packages at their current version:
1) apt [2.7.12 (now)]
2) apt-utils [2.7.12 (now)]
3) at-spi2-core
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
Processing control commands:
> severity -1 normal
Bug #1064969 [aptitude] aptitude: can't upgrade apt due to rename of library
package
Severity set to 'normal' from 'serious'
--
1064969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064969
Debian Bug Tracking System
Contact
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
Processing commands for cont...@bugs.debian.org:
> found 1064969 0.8.13-5
Bug #1064969 [aptitude] apt: can't upgrade with aptitude
Marked as found in versions aptitude/0.8.13-5.
> retitle 1064969 aptitude: can't upgrade apt due to rename of library package
Bug #1064969 [aptitude] apt: can't
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
Processing control commands:
> reassign -1 aptitude
Bug #1064969 [src:apt] apt: can't upgrade with aptitude
Bug reassigned from package 'src:apt' to 'aptitude'.
No longer marked as found in versions apt/2.7.12+nmu1.
Ignoring request to alter fixed versions of bug #1064969 to the same values
Package: aptitude
Version: 0.8.13-5+b1
Severity: wishlist
Imagine there are 1000 different combinations of
Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:
Remove the following packages:
1) libapt-pkg6.0 [2.7.12 (now, unstable)]
2)
13 matches
Mail list logo
