[Aptitude-devel] Bug#979186: Bug#979186: aptitude: in the TUI, "+" changes the version of some packages in an inconsistent way

[Axel Beckert]

Control: tag -1 + unreproducible moreinfo

Hi Vincent,

thanks for the very detailed bug report.

Vincent Lefevre wrote:
> After starting aptitude, I type "[" over "Upgradable Packages" and
> get:
> 
> [...]
>   --\ libs           Collections of software routines (9)
>     --\ main           The main Debian archive (9)
> i A gvfs                       1.46.1-1                 1.46.1-2                
> i A gvfs-daemons               1.46.1-1                 1.46.1-2
> i A gvfs-libs                  1.46.1-1                 1.46.1-2
> [...]
> 
> Then I type "+" over "gvfs". I get:
> 
> [...]
>   --\ libs           Collections of software routines (9)
>     --\ main           The main Debian archive (9)
> iBA gvfs             +1024 B   1.46.1-1                 1.46.1-2
> i A gvfs-daemons               1.46.1-1                 1.46.1-1
> i A gvfs-libs                  1.46.1-1                 1.46.1-1
> [...]
> userspace virtual filesystem - GIO module
> Some dependencies of gvfs (broken, 1.46.1-1) are not satisfied:                ▒
>                                                                                ▒
>   * gvfs (upgrade, 1.46.1-1 -> 1.46.1-2) depends on gvfs-common (= 1.46.1-2)   ▒
>     [UNAVAILABLE]                                                              ▒
>   * gvfs (upgrade, 1.46.1-1 -> 1.46.1-2) depends on gvfs-daemons (>= 1.46.1-2) ▒
>   * gvfs (upgrade, 1.46.1-1 -> 1.46.1-2) depends on gvfs-libs (= 1.46.1-2)     ▒
> 
> Notice that the versions of gvfs-daemons and gvfs-libs in the last
> column have changed from 1.46.1-2 to 1.46.1-1!
> 
> Then when I type Ctrl-u to undo the last action, I get:
> 
> [...]
>   --\ libs           Collections of software routines (9)
>     --\ main           The main Debian archive (9)
> i A gvfs                       1.46.1-1                 1.46.1-2                
> i A gvfs-daemons               1.46.1-1                 1.46.1-1
> i A gvfs-libs                  1.46.1-1                 1.46.1-1
> [...]
> 
> The versions are still the changed ones.

I agree that this behaviour is strange and I also believe that this
happened to you.

Unforunately I can't reproduce this here as it automatically upgrades
gvfs-daemons and gvfs-libs here. It then reports gvfs-backends and
gvfs-fuse as broken and (IMHO correctly) suggests to upgrade them,
too.

Can you do an aptitude-create-state-bundle either before (preferred)
or after that situation and upload it somewhere?

Oh, and what is your setting of aptitude::Auto-Install (aka
"Automatically resolve dependencies of a package when it is selected")
and maybe other settings which might play a role here?

Tried it with both, on (see above) and off. But even in the latter
case I can't reproduce this:

iBA gvfs          5  +1024 B   408 kB   1.46.1-1  1.46.1-2
i A gvfs-common   0            3632 kB  1.46.1-1  1.46.1-2
i A gvfs-daemons  1            561 kB   1.46.1-1  1.46.1-2
i A gvfs-libs  	  0            471 kB   1.46.1-1  1.46.1-2

Do you have any special /etc/apt/preferences* settings which might
play a role here, too?

(All these questions should also be answered by providing a aptitude
state bundle.)

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe at debian.org>, https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/aptitude-devel/attachments/20210104/39ade236/attachment.sig>