Re: Gnutls depends on unbound. Why?
@lbutlr wrote:
When trying to update gnutls it wants to install unbound.
I do not want unbound since my server is already running bind.
make config shows nothing at all that implies unbound is required, and the only
option that is even close to being related is IDN support which certainly
doesn’t require unbound, but disabling this option doesn’t change anything.
It's actually the DANE option, which brings in unbound.
# portmaster --show-work gnutls
===>>> Currently installed version: gnutls-3.5.18
===>>> Port directory: /usr/ports/security/gnutls
===>>> Starting check for all dependencies
===>>> Gathering dependency list for security/gnutls from ports
===>>> Installed converters/libiconv
===>>> Installed devel/gettext-runtime
===>>> Installed devel/gettext-tools
===>>> Installed devel/gmake
===>>> Installed devel/libunistring
===>>> Installed devel/pkgconf
===>>> NOT INSTALLEDdns/unbound
===>>> Installed math/gmp
===>>> Installed ports-mgmt/pkg
===>>> Installed print/indexinfo
===>>> Installed print/texinfo
===>>> Installed security/ca_root_nss
===>>> Installed security/libtasn1
===>>> Installed security/nettle
===>>> Installed security/p11-kit
===>>> Installed security/trousers
Also, when actually running postmaster gnutls it says it will install unbound
AND ldns, and also upgrade p11-kit, none of which are mentioned in —show-work.
I thought show work would show ALL the dependancies down the tree (Unbound
depends on ldns), don’t know where p11-kit shows up.
Trying to dig further,
# pkg info -Rx gnutls
Shows only the following dependancies (In deps { … }:
trousers
p11-kit
nettle
libtasn1
ca_root_nss
indexinfo
gmp
libidn2
libunistring
gettext-runtime
Which is a different list than —show-work lists.
So I am quite confused.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Gnutls depends on unbound. Why?
When trying to update gnutls it wants to install unbound.
I do not want unbound since my server is already running bind.
make config shows nothing at all that implies unbound is required, and the only
option that is even close to being related is IDN support which certainly
doesn’t require unbound, but disabling this option doesn’t change anything.
# portmaster --show-work gnutls
===>>> Currently installed version: gnutls-3.5.18
===>>> Port directory: /usr/ports/security/gnutls
===>>> Starting check for all dependencies
===>>> Gathering dependency list for security/gnutls from ports
===>>> Installed converters/libiconv
===>>> Installed devel/gettext-runtime
===>>> Installed devel/gettext-tools
===>>> Installed devel/gmake
===>>> Installed devel/libunistring
===>>> Installed devel/pkgconf
===>>> NOT INSTALLEDdns/unbound
===>>> Installed math/gmp
===>>> Installed ports-mgmt/pkg
===>>> Installed print/indexinfo
===>>> Installed print/texinfo
===>>> Installed security/ca_root_nss
===>>> Installed security/libtasn1
===>>> Installed security/nettle
===>>> Installed security/p11-kit
===>>> Installed security/trousers
Also, when actually running postmaster gnutls it says it will install unbound
AND ldns, and also upgrade p11-kit, none of which are mentioned in —show-work.
I thought show work would show ALL the dependancies down the tree (Unbound
depends on ldns), don’t know where p11-kit shows up.
Trying to dig further,
# pkg info -Rx gnutls
Shows only the following dependancies (In deps { … }:
trousers
p11-kit
nettle
libtasn1
ca_root_nss
indexinfo
gmp
libidn2
libunistring
gettext-runtime
Which is a different list than —show-work lists.
So I am quite confused.
--
'Dojo! What is Rule One?' Even the cowering challenger mumbled along to
the chorus: 'Do not act incautiously when confronting little bald
wrinkly smiling men!’
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
check_mssql_collection
Hello. I was using a PHP based script to check MSSQL servers in my Nagios installations. However, it seems php56-mssql has no equivalent in he php71 world. So, while searching for an alternative, I found this: https://github.com/NagiosEnterprises/check_mssql_collection As anyone already tried porting it? If not I might give it a try. bye & Thanks av. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: U[dating Bind912 wants ghostscript?
On 07 Sep 2018, at 02:44, Rainer Hurling wrote: > Am 07.09.18 um 09:46 schrieb @lbutlr: >> >> Were does this dependency on doxygen come from, and why does that then want >> to install ghostscript and tex? > devel/protobuf-c seems to be the culprit: > > OPTIONS_DEFINE= DOXYGEN > OPTIONS_DEFAULT=DOXYGEN Thank you, I was about to post back that I’d found it. Changed the options for ptoyobuf-c to not install the documentation and reinstalled without tex and Ghostscript. -- The voice of the majority is no proof of justice. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: U[dating Bind912 wants ghostscript?
Am 07.09.18 um 09:46 schrieb @lbutlr: > I went to update my install of Bind9 and it wanted to install a lot o new > things, including ghostscript (which I have been careful to keep off my > system due to many remotely exploitable vulnerabilities and a lack of need). > In fact, there were a lot of new packages it wanted to install which appear > to all be depended on doxygen. > > Were does this dependency on doxygen come from, and why does that then want > to install ghostscript and tex? > > > ===>>> bind912-9.12.1P2 >> (18) > > ===>>> The following actions will be taken if you choose to proceed: > Upgrade bind912-9.12.1P2 to bind912-9.12.2P1_2 > Upgrade json-c-0.13 to json-c-0.13.1 > Upgrade protobuf-c-1.3.0_1 to protobuf-c-1.3.1 > Install devel/doxygen devel/protobuf-c seems to be the culprit: OPTIONS_DEFINE= DOXYGEN OPTIONS_DEFAULT=DOXYGEN > Install print/ghostscript9-agpl-base > Upgrade poppler-data-0.4.8 to poppler-data-0.4.9 > Install print/tex-dvipsk > Install devel/tex-web2c > Upgrade zziplib-0.13.62_2 to zziplib-0.13.69_1 > Install print/texlive-texmf > Install print/tex-basic-engines > Install print/texlive-base > Install devel/t1lib > Install graphics/poppler > Upgrade nspr-4.19 to nspr-4.20 > Upgrade nss-3.38 to nss-3.39 > Install print/harfbuzz-icu > Install print/tex-formats > Upgrade protobuf-3.5.2,1 to protobuf-3.5.2_1,1 > > I looked in the make config for bin912 and didn't see anything that implied > doxygen was needed, > > I went ahead and did postmaster -i bind912 and said no to Doxygen which meant > the only things updated were bind, json, protobuff-c and protobuff. which is > much more in line with what I was expecting. > > However, during the compile process, doxygen, ghostscript, and the various > tex packages were installed anyway. > > What has changed in the build instructions for bind912? > > ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ devel/lua-luarocks | 3.0.1 | 3.0.2 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
U[dating Bind912 wants ghostscript?
I went to update my install of Bind9 and it wanted to install a lot o new things, including ghostscript (which I have been careful to keep off my system due to many remotely exploitable vulnerabilities and a lack of need). In fact, there were a lot of new packages it wanted to install which appear to all be depended on doxygen. Were does this dependency on doxygen come from, and why does that then want to install ghostscript and tex? ===>>> bind912-9.12.1P2 >> (18) ===>>> The following actions will be taken if you choose to proceed: Upgrade bind912-9.12.1P2 to bind912-9.12.2P1_2 Upgrade json-c-0.13 to json-c-0.13.1 Upgrade protobuf-c-1.3.0_1 to protobuf-c-1.3.1 Install devel/doxygen Install print/ghostscript9-agpl-base Upgrade poppler-data-0.4.8 to poppler-data-0.4.9 Install print/tex-dvipsk Install devel/tex-web2c Upgrade zziplib-0.13.62_2 to zziplib-0.13.69_1 Install print/texlive-texmf Install print/tex-basic-engines Install print/texlive-base Install devel/t1lib Install graphics/poppler Upgrade nspr-4.19 to nspr-4.20 Upgrade nss-3.38 to nss-3.39 Install print/harfbuzz-icu Install print/tex-formats Upgrade protobuf-3.5.2,1 to protobuf-3.5.2_1,1 I looked in the make config for bin912 and didn't see anything that implied doxygen was needed, I went ahead and did postmaster -i bind912 and said no to Doxygen which meant the only things updated were bind, json, protobuff-c and protobuff. which is much more in line with what I was expecting. However, during the compile process, doxygen, ghostscript, and the various tex packages were installed anyway. What has changed in the build instructions for bind912? -- For my birthday I got a humidifier and a de-humidifier... I put them in the same room and let them fight it out. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
