[Bug 1412909] Re: Please raise Suggests for lib{pam, nss}-winbind to Recommends in trusty

[Dave Chiluk]

I just went through the exercise of attempting to validate this issue.

from an ubuntu-cloud-image, I enabled proposed.  I installed samba and
libpam-winbind.  Then ran do-release-upgrade.

Unfortunately even though samba 2:4.1.6+dfsg-1ubuntu2.14.04.5  was
installed on the other side of the upgrade, libnss-winbind was still not
installed.

@bdmurray if you think I did my test correctly please feel free to
reject the verification.  You might have to go back to the drawing
board.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1412909

Title:
  Please raise Suggests for lib{pam,nss}-winbind to Recommends in trusty

Status in samba package in Ubuntu:
  Triaged
Status in samba source package in Trusty:
  Fix Committed

Bug description:
  Test Case
  ---------
  In a precise system install samba and libpam-winbind
  Upgrade to trusty
  Observe that libnss-winbind is not installed

  With the version of the package from -proposed, after the upgrade
  libnss-winbind will be install on the system.

  -----------------------------------------------------------------------------

  The Debian packaging of Samba demoted the Recommends relationships to
  libpam-winbind and libnss-winbind to Suggests after one Debian
  release:

  samba (2:3.6.15-1) unstable; urgency=high

    * Team upload.
    * New upstream bugfix release. Closes: #707042
    * Update VCS URL's for new git repo.
    * The recommends for the separate libnss-winbind and libpam-winbind
      packages needed for the upgrade of winbind from squeeze to wheezy are no
      longer needed. Lowering them to suggests.
      Closes: #706434, #674853

   -- Ivo De Decker <ivo.dedecker at ugent.be>  Thu, 09 May 2013 11:55:03
  +0200

  Unfortunately this isn't enough for the Ubuntu LTS cycle. libpam-
  winbind was a separate package in Precise, but libnss-winbind wasn't,
  and the release-upgrader therefore doesn't know to install it. Can
  those relationships be restored to Recommends in trusty-updates? (This
  delta doesn't need to be kept past Trusty.)

  We upgraded a server from Precise to Trusty this weekend and it was
  really confusing to track down why nobody could log in any more. I
  know it's been a while since the Trusty release, but given that
  Precise is around for two more years, I strongly suspect we're not the
  last people to upgrade a winbind-using Precise machine, and
  configuring samba correctly is confusing enough as it is. :)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1412909/+subscriptions