[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Binary package for spamassassin requires excessive dependencies?
On 2020-03-08 10:56 a.m., Greg Troxel
Can you check if the actual binary package lists those dependencies,
by fetching it separately and funning pkg_info on it?
I have built it locally and also see nothing like this; just wget,
gnup2, re2c and a bunch of perl modules.
pkg_info -S reports 93 MB. Which is a big, but nothing like what you
(Basically, we need to first understand if this is a bug in the built
package or a bug in pkgin).)
Using pkg_info the dependencies listed for spamassassin-3.4.2nb2.tgz fetched from
and for spamassassin-3.4.2nb2.tgz from the
8.1/All directory I receive the following list of dependencies:
So this seems as expected and fine.
In the process of doing this I needed to install wget since this was
a clean 9.0 install. I immediately found wget was exhibiting the
same behaviour (massive dependencies required). So it appears
nothing is wrong with the spamassassin package and the problem lies
Using the older pkg_add command for either spamassassin or wget
resulted in a core dump, so it appears something's really wrong
somewhere. Now to track down what and where.
This system is to go in a DMZ so I don't wish to install pkgsrc or
compilation tools on it since it will be slightly exposed to the
outside Internet. I could build the packages from pkgsrc on another
system, but I'd like to figure out what's gone wrong before
deploying this one.
I'll update this thread once I figure out where the problem is. If
anyone has any ideas please feel welcome to make suggestions.
Main Index |
Thread Index |