Comment 11 for bug 1970264

On Wednesday, May 04 2022, Michael Kiermaier wrote:

> @Brian Murray
> In the process, I see the following:
>
> apt-get install autofs/jammy-proposed
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> Selected version '5.1.8-1ubuntu1.1' (Ubuntu:22.04/jammy-proposed [amd64]) for 'autofs'
> The following packages will be REMOVED:
> autofs-ldap
> The following packages will be upgraded:
> autofs
>
>
> Removing autofs-ldap is not o.k., it seems that some dependency entry
> needs to be adjusted. (Maybe this should be checked in general: Are
> there other packages depending on autofs-5.1.8-1ubuntu1?)

Thanks for verifying, Michael.

Unfortunately I cannot reproduce the problem when using a Jammy
container with both autofs and autofs-ldap installed. Here's what I see
after I enable the -proposed repository and issue the same command
you're using:

# apt-get install autofs/jammy-proposed
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Selected version '5.1.8-1ubuntu1.1' (Ubuntu:22.04/jammy-proposed [amd64]) for 'autofs'
The following package was automatically installed and is no longer required:
  libfreetype6
Use 'apt autoremove' to remove it.
The following additional packages will be installed:
  autofs-ldap
The following packages will be upgraded:
  autofs autofs-ldap
2 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Need to get 327 kB of archives.
After this operation, 1024 B of additional disk space will be used.
Do you want to continue? [Y/n]

As you can see, autofs-ldap is marked to be upgraded along autofs, which
makes sense since autofs-ldap has a versioned dependency on autofs.
This leads me to believe that you probably have autofs-ldap pinned or
held by dpkg, which would prevent it from being upgraded. Could you
please double check this?

Thanks,

--
Sergio
GPG key ID: E92F D0B3 6B14 F1F4 D8E0 EB2F 106D A1C8 C3CB BF14