Hello Sergey, or anyone else affected,

Accepted nss into groovy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/nss/2:3.55-1ubuntu3.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: nss (Ubuntu Groovy)
       Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-groovy

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1908818

Title:
  pure packaging of libnss3

Status in nss package in Ubuntu:
  Fix Released
Status in nss source package in Groovy:
  Fix Committed
Status in nss source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

   * A packaging error in the current version has led library symlinks
     to be broken and in the wrong place.

   * Fix by applying the later change to Groovy as well

  [Test Plan]

   * install libnss3
   * check (path depends on the architecture) the lib links
     $ dpkg -L libnss3 | grep MULTIARCH
     # ^^ should be empty
     $ ll /usr/lib/x86_64-linux-gnu/libfreebl3.so
     # vv should look like that:

  lrwxrwxrwx 1 root root 17 Feb 16 15:18 
/usr/lib/x86_64-linux-gnu/libfreebl3.so -> nss/libfreebl3.so
  root@h:~# ll /usr/lib/x86_64-linux-gnu/libfreebl*
  lrwxrwxrwx 1 root root 18 Feb 16 15:18 
/usr/lib/x86_64-linux-gnu/libfreebl3.chk -> nss/libfreebl3.chk
  lrwxrwxrwx 1 root root 17 Feb 16 15:18 
/usr/lib/x86_64-linux-gnu/libfreebl3.so -> nss/libfreebl3.so
  lrwxrwxrwx 1 root root 22 Feb 16 15:18 
/usr/lib/x86_64-linux-gnu/libfreeblpriv3.chk -> nss/libfreeblpriv3.chk
  lrwxrwxrwx 1 root root 21 Feb 16 15:18 
/usr/lib/x86_64-linux-gnu/libfreeblpriv3.so -> nss/libfreeblpriv3.so

  [Where problems could occur]

   * I first was afraid, that no matter how bad the paths would
     have been we'd need to retain them for anyone using them
     already. But the existing links go into nowhere since they
     are relative therefore the regression risk should be minimal

  root@g:~# ll '/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so' 
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.so' 
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk' 
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk'
  lrwxrwxrwx 1 root root 18 Sep 29  2020 
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk' -> nss/libfreebl3.chk
  lrwxrwxrwx 1 root root 17 Sep 29  2020 
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so' -> nss/libfreebl3.so
  lrwxrwxrwx 1 root root 22 Sep 29  2020 
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk' -> nss/libfreeblpriv3.chk
  lrwxrwxrwx 1 root root 21 Sep 29  2020 
'/usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.so' -> nss/libfreeblpriv3.so

   * never the less, to be clear - if problems occur they would be in 
     loading these libraries. E.g. a user could have had this package
     and a self built nss on his system, after the change it might load the 
     packaged one.

  [Other Info]
   
   * n/a

  ---

  
  dpkg -L libnss3
  /.
  /usr
  /usr/lib
  /usr/lib/${DEB_HOST_MULTIARCH}
  /usr/lib/x86_64-linux-gnu
  /usr/lib/x86_64-linux-gnu/libnss3.so
  /usr/lib/x86_64-linux-gnu/libnssutil3.so
  /usr/lib/x86_64-linux-gnu/libsmime3.so
  /usr/lib/x86_64-linux-gnu/libssl3.so
  /usr/lib/x86_64-linux-gnu/nss
  /usr/lib/x86_64-linux-gnu/nss/libfreebl3.chk
  /usr/lib/x86_64-linux-gnu/nss/libfreebl3.so
  /usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.chk
  /usr/lib/x86_64-linux-gnu/nss/libfreeblpriv3.so
  /usr/lib/x86_64-linux-gnu/nss/libnssckbi.so
  /usr/lib/x86_64-linux-gnu/nss/libnssdbm3.chk
  /usr/lib/x86_64-linux-gnu/nss/libnssdbm3.so
  /usr/lib/x86_64-linux-gnu/nss/libsoftokn3.chk
  /usr/lib/x86_64-linux-gnu/nss/libsoftokn3.so
  /usr/share
  /usr/share/doc
  /usr/share/doc/libnss3
  /usr/share/doc/libnss3/changelog.Debian.gz
  /usr/share/doc/libnss3/copyright
  /usr/share/lintian
  /usr/share/lintian/overrides
  /usr/share/lintian/overrides/libnss3
  /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk
  /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so
  /usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk

  as we can see soft links to libraries do nor resolve
  ${DEB_HOST_MULTIARCH} to x86_64-linux-gnu

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: libnss3 2:3.55-1ubuntu3
  ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
  Uname: Linux 5.8.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Dec 20 14:36:10 2020
  SourcePackage: nss
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to