Jump to content
Read the Funtoo Newsletter: Summer 2023 ×
  • 0

emerge dev-libs/nss-3.17.1 fail





because of an compile error with dev-libs/nss-3.17.1 I'm currently not able to do a world update with "emerge -av --update --newuse --deep --with-bdeps=y --keep-going @world". I've got the following error:


>>> Emerging (1 of 1) dev-libs/nss-3.17.1
 * nss-3.17.1.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ...                                                        [ ok ]
 * nss-3.14.1-add_spi+cacerts_ca_certs.patch SHA256 SHA512 WHIRLPOOL size ;-) ...                                [ ok ]
 * nss-pem-015ae754dd9f6fbcd7e52030ec9732eb27fc06a8.tar.bz2 SHA256 SHA512 WHIRLPOOL size ;-) ...                 [ ok ]
>>> Unpacking source...
>>> Unpacking nss-3.17.1.tar.gz to /var/tmp/portage/dev-libs/nss-3.17.1/work
>>> Unpacking nss-3.14.1-add_spi+cacerts_ca_certs.patch to /var/tmp/portage/dev-libs/nss-3.17.1/work
unpack nss-3.14.1-add_spi+cacerts_ca_certs.patch: file format not recognized. Ignoring.
>>> Unpacking nss-pem-015ae754dd9f6fbcd7e52030ec9732eb27fc06a8.tar.bz2 to /var/tmp/portage/dev-libs/nss-3.17.1/work
>>> Source unpacked in /var/tmp/portage/dev-libs/nss-3.17.1/work
>>> Preparing source in /var/tmp/portage/dev-libs/nss-3.17.1/work/nss-3.17.1/nss ...
 * Applying nss-3.15-gentoo-fixups.patch ...

 * Failed Patch: nss-3.15-gentoo-fixups.patch !
 *  ( /usr/portage/dev-libs/nss/files/nss-3.15-gentoo-fixups.patch )
 * Include in your bugreport the contents of:
 *   /var/tmp/portage/dev-libs/nss-3.17.1/temp/nss-3.15-gentoo-fixups.patch.out

 * ERROR: dev-libs/nss-3.17.1 failed (prepare phase):
 *   Failed Patch: nss-3.15-gentoo-fixups.patch!
 * Call stack:
 *     ebuild.sh, line   93:  Called src_prepare
 *   environment, line 2995:  Called epatch '/usr/portage/dev-libs/nss/files/nss-3.15-gentoo-fixups.patch'
 *   environment, line  877:  Called die
 * The specific snippet of code:
 *               die "Failed Patch: ${patchname}!";
 * If you need support, post the output of `emerge --info '=dev-libs/nss-3.17.1'`,
 * the complete build log and the output of `emerge -pqv '=dev-libs/nss-3.17.1'`.
 * The complete build log is located at '/var/tmp/portage/dev-libs/nss-3.17.1/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/dev-libs/nss-3.17.1/temp/environment'.
 * Working directory: '/var/tmp/portage/dev-libs/nss-3.17.1/work/nss-3.17.1/nss'
 * S: '/var/tmp/portage/dev-libs/nss-3.17.1/work/nss-3.17.1/nss'

>>> Failed to emerge dev-libs/nss-3.17.1, Log file:

>>>  '/var/tmp/portage/dev-libs/nss-3.17.1/temp/build.log'

Sie build.log attached. Output of emerge --info '=dev-libs/nss-3.17.1' see emerge_info.txt.


nss-3.16.5 compiles fine. Will try to mask 3.17.1 now and try to run world update again.








Link to comment
Share on other sites

7 answers to this question

Recommended Posts

  • 0

echo ">=dev-libs/nss-3.17" >> /etc/portage/package.mask


should do the job. Since world update is a little big this time I'll start later in the evening to finally start it ;-) But "emerge -av --update --newuse --deep --with-bdeps=y --keep-going @world" doesn't tell me that there is a problem using nss 3.16.5 so I hope everything compiles fine.

Link to comment
Share on other sites

  • 0

Same problem here.  And 3.16.5 does work.


It's odd, because 3.17 looks like it ought to have the same problem, but evidently that emerged fine at some point.


For those worried about the recent critical vulnerability in nss, Mozilla states it is also fixed in 3.16.5 (see https://www.mozilla.org/security/announce/2014/mfsa2014-73.html) so masking 3.17.1 should not leave you vulnerable.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...