Your message dated Sat, 29 Mar 2008 21:18:06 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#473275: nss: libsoftokn3 is missing
has caused the Debian Bug report #473275,
regarding nss: libsoftokn3 is missing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
473275: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=473275
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: nss
Version: 3.12.0~beta2
Severity: normal
Tags: patch
Hi,
while building mozldap, svrcore and fedora directory server on my debian
sid box, I noticed that linking to softokn3 failed, since neither the
.so nor the .so.1d files are included in the libnss* packages.
I've used the following (sorry no proper dpatch for the softokn
manifest) fix:
diff -up nss-3.12.0~beta2/debian/libnss3-dev.links.orig
nss-3.12.0~beta2/debian/libnss3-dev.links
--- nss-3.12.0~beta2/debian/libnss3-dev.links.orig 2008-03-29
19:12:07.000000000 +0100
+++ nss-3.12.0~beta2/debian/libnss3-dev.links 2008-03-29 19:12:51.000000000
+0100
@@ -2,4 +2,5 @@ usr/lib/libnss3.so.1d usr/lib/libnss3.so
usr/lib/libnssutil3.so.1d usr/lib/libnssutil3.so
usr/lib/libsmime3.so.1d usr/lib/libsmime3.so
usr/lib/libssl3.so.1d usr/lib/libssl3.so
+usr/lib/libsoftokn3.so.1d usr/lib/libsoftokn3.so
usr/lib/pkgconfig/nss.pc usr/lib/pkgconfig/xulrunner-nss.pc
diff -up nss-3.12.0~beta2/debian/libnss3-1d.symbols.orig
nss-3.12.0~beta2/debian/libnss3-1d.symbols
--- nss-3.12.0~beta2/debian/libnss3-1d.symbols.orig 2008-03-29
19:13:05.000000000 +0100
+++ nss-3.12.0~beta2/debian/libnss3-1d.symbols 2008-03-29 19:13:12.000000000
+0100
@@ -1119,6 +1119,12 @@ libsmime3.so.1d libnss3-1d #MINVER#
[EMAIL PROTECTED] 3.12.0~1.9b1
[EMAIL PROTECTED] 3.12.0~1.9b1
[EMAIL PROTECTED] 3.12.0~1.9b1
+libsoftokn3.so.1d libnss3-1d #MINVER#
+ [EMAIL PROTECTED] 3.12.0~beta2-1
+ [EMAIL PROTECTED] 3.12.0~beta2-1
+ [EMAIL PROTECTED] 3.12.0~beta2-1
+ [EMAIL PROTECTED] 3.12.0~beta2-1
+ [EMAIL PROTECTED] 3.12.0~beta2-1
libssl3.so.1d libnss3-1d #MINVER#
[EMAIL PROTECTED] 3.12.0~1.9b1
[EMAIL PROTECTED] 3.12.0~1.9b1
diff -up nss-3.12.0~beta2/debian/rules.orig nss-3.12.0~beta2/debian/rules
diff -up nss-3.12.0~beta2/mozilla/security/nss/lib/softoken/manifest.mn.orig
nss-3.12.0~beta2/mozilla/security/nss/lib/softoken/manifest.mn
--- nss-3.12.0~beta2/mozilla/security/nss/lib/softoken/manifest.mn.orig
2008-03-29 19:13:50.000000000 +0100
+++ nss-3.12.0~beta2/mozilla/security/nss/lib/softoken/manifest.mn
2008-03-29 19:14:36.000000000 +0100
@@ -43,6 +43,7 @@ REQUIRES = dbm
LIBRARY_NAME = softokn
LIBRARY_VERSION = 3
+SO_VERSION = 1d
MAPFILE = $(OBJDIR)/softokn.def
DEFINES += -DSHLIB_SUFFIX=\"$(DLL_SUFFIX)\" -DSHLIB_PREFIX=\"$(DLL_PREFIX)\"
-DSOFTOKEN_LIB_NAME=\"$(notdir $(SHARED_LIBRARY))\"
-DSHLIB_VERSION=\"$(LIBRARY_VERSION)\"
hth,
Michele
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
On Sat, Mar 29, 2008 at 07:34:30PM +0100, Michele Baldessari <[EMAIL
PROTECTED]> wrote:
> Package: nss
> Version: 3.12.0~beta2
> Severity: normal
> Tags: patch
>
>
> Hi,
>
> while building mozldap, svrcore and fedora directory server on my debian
> sid box, I noticed that linking to softokn3 failed, since neither the
> .so nor the .so.1d files are included in the libnss* packages.
libsoftokn3 is in /usr/lib/nss, and you don't have to link against it: libnss
loads it dynamically. That's also why it doesn't appear in the .pc file nor
in nss-config's output anymore.
Mike
--- End Message ---