Discussion:
nss dependency problem, seamonkey
Riccardo Mottola
2014-03-21 14:04:56 UTC
Permalink
Hi,

I am trying to install seamonkey as a binary package, since it is too
much to compile on my ol' thinkpad (I know it requires > 1G of RAM to
link properly on linux). I already have some packages built from pkgsrc,
but I hope they don't conflict.

Anyway here my ouput:
narsil$ sudo pkg_add
ftp://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/i386/6.0_2013Q3/All/seamonkey-2.21.tgz
pkg_add: Warning: package `seamonkey-2.21' was built for a platform:
pkg_add: NetBSD/i386 6.0 (pkg) vs. NetBSD/i386 6.1.3 (this host)
pkg_add: Warning: package `nspr-4.10nb1' was built for a platform:
pkg_add: NetBSD/i386 6.0 (pkg) vs. NetBSD/i386 6.1.3 (this host)
pkg_add: Warning: package `nss-3.15.1' was built for a platform:
pkg_add: NetBSD/i386 6.0 (pkg) vs. NetBSD/i386 6.1.3 (this host)
pkg_add: Conflicting PLIST with nss-3.15.1: include/nss/nss/crmf.h
pkg_add: Can't install dependency nss>=3.15
pkg_add: 1 package addition failed


narsil$ pkg_info | grep nss

tells me I have no nss installed... what's the conflict about?

Riccardo
Greg Troxel
2014-03-21 14:13:31 UTC
Permalink
Post by Riccardo Mottola
I am trying to install seamonkey as a binary package, since it is too
much to compile on my ol' thinkpad (I know it requires > 1G of RAM to
link properly on linux). I already have some packages built from
pkgsrc, but I hope they don't conflict.
narsil$ sudo pkg_add
ftp://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/i386/6.0_2013Q3/All/seamonkey-2.21.tgz
So, the basic rule is that all your packages have to be built
consistently from the same sources, with consistent options. So if you
have checked out pkgsrc sources -r pkgsrc-2013Q3 and all your installed
packages are from that, you should be ok.

Of course, you are free to violate this basic rule. But if so, please
let us know when asking questions :-)
Post by Riccardo Mottola
pkg_add: NetBSD/i386 6.0 (pkg) vs. NetBSD/i386 6.1.3 (this host)
pkg_add: NetBSD/i386 6.0 (pkg) vs. NetBSD/i386 6.1.3 (this host)
pkg_add: NetBSD/i386 6.0 (pkg) vs. NetBSD/i386 6.1.3 (this host)
So these messsages should be ok
Post by Riccardo Mottola
pkg_add: Conflicting PLIST with nss-3.15.1: include/nss/nss/crmf.h
pkg_add: Can't install dependency nss>=3.15
pkg_add: 1 package addition failed
It looks like it's trying to install nss as a dependency.

Do you have PKGPATH set to any other area other than 2013Q3?

How were the other installed packages installed?
Riccardo Mottola
2014-03-21 14:38:41 UTC
Permalink
Hi,
Post by Greg Troxel
So, the basic rule is that all your packages have to be built
consistently from the same sources, with consistent options. So if you
have checked out pkgsrc sources -r pkgsrc-2013Q3 and all your installed
packages are from that, you should be ok.
Of course, you are free to violate this basic rule. But if so, please
let us know when asking questions :-)
I did so.. Instlaling my own was the only way getting Emacs to work, do
you remember?
Post by Greg Troxel
Post by Riccardo Mottola
pkg_add: Conflicting PLIST with nss-3.15.1: include/nss/nss/crmf.h
pkg_add: Can't install dependency nss>=3.15
pkg_add: 1 package addition failed
It looks like it's trying to install nss as a dependency.
Do you have PKGPATH set to any other area other than 2013Q3?
How were the other installed packages installed?
Other packages either come from here or where compiled by myself from
plgsrc, but nss is not among them since it is not even installed.

My PKG_PATH is empty! (I suppos eyou mean that an not PKGPATH)

I'm used that if you pkg_add something from the "All" directory of the
binary repository, all dependency get sucked in from there.

I did try to set
PKG_PATH="ftp://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/i386/6.0_2013Q3/All"

I get then a very similar error:
pkg_add seamonkey-2.21
pkg_add: Warning: package `seamonkey-2.21' was built for a platform:
pkg_add: NetBSD/i386 6.0 (pkg) vs. NetBSD/i386 6.1.3 (this host)
pkg_add: Conflicting PLIST with seamonkey-2.21:
include/seamonkey/mozINewMailNotificationService.h
pkg_add: 1 package addition failed

Then I did "su -" to execute in root's clean environment
narsil# pkg_add
ftp://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/i386/6.0_2013Q3/All/seamonkey-2.21.tgz
pkg_add: Warning: package `seamonkey-2.21' was built for a platform:
pkg_add: NetBSD/i386 6.0 (pkg) vs. NetBSD/i386 6.1.3 (this host)
pkg_add: Conflicting PLIST with seamonkey-2.21:
include/seamonkey/mozINewMailNotificationService.h
pkg_add: 1 package addition failed


hmm, perhaps I do have a cache of binary packages somewhere?

Riccardo
Greg Troxel
2014-03-21 15:12:22 UTC
Permalink
Post by Riccardo Mottola
Hi,
Post by Greg Troxel
So, the basic rule is that all your packages have to be built
consistently from the same sources, with consistent options. So if you
have checked out pkgsrc sources -r pkgsrc-2013Q3 and all your installed
packages are from that, you should be ok.
Of course, you are free to violate this basic rule. But if so, please
let us know when asking questions :-)
I did so.. Instlaling my own was the only way getting Emacs to work,
do you remember?
Yes, but I and the others have no idea if that was the same system.

But building your own isn't the issue. It's building from a different
set of pkgsrc sources. So if you do *everything* from 2013Q4 and dont
have non-default options to control the overall build, you should be ok.
Post by Riccardo Mottola
Post by Greg Troxel
Post by Riccardo Mottola
pkg_add: Conflicting PLIST with nss-3.15.1: include/nss/nss/crmf.h
pkg_add: Can't install dependency nss>=3.15
pkg_add: 1 package addition failed
It looks like it's trying to install nss as a dependency.
Do you have PKGPATH set to any other area other than 2013Q3?
How were the other installed packages installed?
Other packages either come from here or where compiled by myself from
plgsrc, but nss is not among them since it is not even installed.
My PKG_PATH is empty! (I suppos eyou mean that an not PKGPATH)
yes, sorry.
Post by Riccardo Mottola
I'm used that if you pkg_add something from the "All" directory of the
binary repository, all dependency get sucked in from there.
I did try to set
PKG_PATH="ftp://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/i386/6.0_2013Q3/All"
pkg_add seamonkey-2.21
pkg_add: NetBSD/i386 6.0 (pkg) vs. NetBSD/i386 6.1.3 (this host)
include/seamonkey/mozINewMailNotificationService.h
pkg_add: 1 package addition failed
Then I did "su -" to execute in root's clean environment
narsil# pkg_add
ftp://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/i386/6.0_2013Q3/All/seamonkey-2.21.tgz
pkg_add: NetBSD/i386 6.0 (pkg) vs. NetBSD/i386 6.1.3 (this host)
include/seamonkey/mozINewMailNotificationService.h
pkg_add: 1 package addition failed
So I would not only look to clean out caches, but donwload seamonkey and
it's dependencies explicitly so you can run pkg_info on them. Then you
can try to install them one at a time and perhaps get better insight.

As a check for how your installed system is, update your pkgsrc tree to
pkgsrc-2013Q4 and then run "pkg_chk -uq". Ideally you'll have empty
output, showing that all your installed packages are from 2013Q4.
Ottavio Caruso
2014-03-21 15:23:03 UTC
Permalink
Post by Riccardo Mottola
My PKG_PATH is empty! (I suppos eyou mean that an not PKGPATH)
I'm used that if you pkg_add something from the "All" directory of the
binary repository, all dependency get sucked in from there.
Can you not just use pkgin to do the job of checking dependencies?
--
Ottavio
Greg Troxel
2014-03-21 15:28:42 UTC
Permalink
Post by Ottavio Caruso
Post by Riccardo Mottola
My PKG_PATH is empty! (I suppos eyou mean that an not PKGPATH)
I'm used that if you pkg_add something from the "All" directory of the
binary repository, all dependency get sucked in from there.
Can you not just use pkgin to do the job of checking dependencies?
Yes. But pkgin has no magic to avoid problems from builds of different
branches, and I've seen it get a little confused when I've been doing
inconsistent updates.
pkgin will lead you down the path of only using packages from the
repository, which if a consistent quarterly build, is a good plan.
Ottavio Caruso
2014-03-21 15:31:59 UTC
Permalink
Post by Greg Troxel
pkgin has no magic to avoid problems from builds of different
branches
but it will suggest to update/downgrade to the packages which are
consistent to the branch it's pulling from. True, it has its
limitations, but it's the only tool I've been using for 5 months now
and it's doing its job.
--
Ottavio
Riccardo Mottola
2014-03-21 14:52:38 UTC
Permalink
Post by Riccardo Mottola
narsil$ sudo pkg_add
ftp://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/i386/6.0_2013Q3/All/seamonkey-2.21.tgz
It all starts that I should have used
ftp://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/i386/6.0_2013Q4/All/seamonkey-2.23.tgz

that is "Q4" and not "Q3", that would give me also a 2.23 evrsion
(thanks Ottavio).

However, the result changes little:

narsil$ sudo pkg_add -u
ftp://ftp.netbsd.org/pub/pkgsrc/packages/NetBSD/i386/6.0_2013Q4/All/seamonkey-2.23.tgz
pkg_add: Warning: package `seamonkey-2.23' was built for a platform:
pkg_add: NetBSD/i386 6.0 (pkg) vs. NetBSD/i386 6.1.3 (this host)
pkg_add: Warning: package `nss-3.15.4' was built for a platform:
pkg_add: NetBSD/i386 6.0 (pkg) vs. NetBSD/i386 6.1.3 (this host)
pkg_add: Conflicting PLIST with nss-3.15.1: include/nss/nss/crmf.h
pkg_add: Can't install dependency nss>=3.15.3
pkg_add: 1 package addition failed


Riccardo
Ottavio Caruso
2014-03-21 21:46:51 UTC
Permalink
Post by Riccardo Mottola
pkg_add: NetBSD/i386 6.0 (pkg) vs. NetBSD/i386 6.1.3 (this host)
pkg_add: Conflicting PLIST with nss-3.15.1: include/nss/nss/crmf.h
pkg_add: Can't install dependency nss>=3.15.3
Try:

# pkg_admin rebuild

or even better install pkgin and let it do the job.
--
Ottavio
Riccardo Mottola
2014-03-24 11:03:18 UTC
Permalink
Hi,
Post by Ottavio Caruso
# pkg_admin rebuild
or even better install pkgin and let it do the job.
pkg_admin rebuild

did its job and I isntalled seamonkey and it works fine :) thanks.

I never used pkgin... I'll have a look!


Riccardo

Loading...