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.

With apt:

zira:~> apt install -s gvfs
[...]
The following packages have unmet dependencies:
 gvfs : Depends: gvfs-common (= 1.46.1-2) but 1.46.1-1 is to be installed
        Depends: gvfs-daemons (>= 1.46.1-2) but 1.46.1-1 is to be installed
        Depends: gvfs-libs (= 1.46.1-2) but 1.46.1-1 is to be installed
E: Unable to correct problems, you have held broken packages.

zira:~> apt-show-versions -a gvfs-common
gvfs-common:all 1.46.1-1 install ok installed
gvfs-common:all 1.38.1-5 stable  ftp.fr.debian.org
No stable-updates version
gvfs-common:all 1.46.1-1 testing ftp.fr.debian.org
No unstable version
No experimental version
gvfs-common:all/testing 1.46.1-1 uptodate
zira:~> apt-show-versions -a gvfs-daemons
gvfs-daemons:amd64 1.46.1-1 install ok installed
gvfs-daemons:amd64 1.38.1-5 stable   ftp.fr.debian.org
No stable-updates version
gvfs-daemons:amd64 1.46.1-1 testing  ftp.fr.debian.org
gvfs-daemons:amd64 1.46.1-2 unstable ftp.fr.debian.org
No experimental version
gvfs-daemons:amd64/testing 1.46.1-1 upgradeable to 1.46.1-2
zira:~> apt-show-versions -a gvfs-libs
gvfs-libs:amd64 1.46.1-1 install ok installed
gvfs-libs:amd64 1.38.1-5 stable   ftp.fr.debian.org
No stable-updates version
gvfs-libs:amd64 1.46.1-1 testing  ftp.fr.debian.org
gvfs-libs:amd64 1.46.1-2 unstable ftp.fr.debian.org
No experimental version
gvfs-libs:amd64/testing 1.46.1-1 upgradeable to 1.46.1-2

So the upgrade cannot be done due to gvfs-common, but this doesn't
explain the strange behavior in the interface.

I've attached the pkgstates file, in case it is needed.

Hi Vincent,

thanks for the very detailed bug report.

Vincent Lefevre wrote:

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

It's available here for a short period:

https://www.vinc17.net/aptitude.bundle

(I created it at about the same time as my bug report; the bug is
also reproducible when running aptitude as a normal user, so that
I could test in a non-destructive way).

My only settings concerning aptitude:

Aptitude::UI::Package-Display-Format "%c%a%M %p %Z %24v %24V";

Aptitude::UI::Styles {
  // Add bold to avoid a readability issue.
  SolutionActionApproved { fg white; bg green; set bold; };
};

Aptitude::ProblemResolver::SolutionCost "safety, removals";

Explanation: For security, make sure that the Flash plugin is never installed.
Package: flashplugin-nonfree:any
Pin: version *
Pin-Priority: -1

Hi Vincent,

Vincent Lefevre wrote:

Thanks! Fetched it.

These shouldn't be relevant.

That might play in here, thanks!
[…]

Probably not relevant either.

Will have a closer look later, earliest this evening.

		Regards, Axel

(reproducible with the bundle)

Hi,

Any news?