[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-07 23:30, Dave Ellis wrote:
When attempting to install the binary package spamassassin-3.4.2nb2
using onto a clean NetBSD 9.0 (amd64) system, an excessive number of
dependent packages appear to be required.
The binary package was sourced from
spamassassin doesn't appear to be available in the 9.0/All directory yet.
Seems odd as it builds just fine on 9.x and hasn't changed version for ages.
To summarize, using 'pkgin install spamassassin' reports 4,678
dependencies required totalling 23GB, most of which appear to be X11
related. X11 is not installed or required on this system, and shouldn't
be required for spamassassin. This seems excessive?
I'd agree. Something appears to have gone a bit mad there. The runtime
depends for spamassasin according to pkgin (from my locally built bin
$ pkgin sd spamassassin
This is a native 9.x build. An 8.x package would add openssl-1.1 as well.
Unless built with some exotic options I don't think any of those
packages would drag in all those dependencies so I suspect there is some
sort of corruption in the pkg-summary file pkgin is using. I normally
build with X11_TYPE=native so I don't know what would happen if the type
was set to modular (which appears to be what the bulk build was done
with). I'll try and set one up this afternoon as a test and see what
happens as I can do that fairly easily without compromising my running
I have had pkgin occasionally do strange things with dependencies but
nothing on this scale. :(
Main Index |
Thread Index |