On Tue, Aug 23, 2016 at 09:08:48PM +0200, Raúl wrote:
> Hello!
>
> grateful for the great work on the ports
> I don't remember last problem upgrading with them, Awesome!
> just a little setback
>
> upgraded using portmaster, everything went apparently fine
> followed pkg-message to update schema
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
Lars Engels escribió:
WITH_PKGNG=yes
you can savely remove this
Removed, thanks!
Do you have the output from portmaster?
https://turing.b2n.org/owncloud/index.php/s/zmFcqMX8EHEpJRl
Thanks a lot in advance.
___
freebsd-ports@freebsd.or
This error message does not appear if I install devel/libcli.
But then:
Performing sanity check of icinga2 configuration:
/usr/local/lib/icinga2/libremote.so: Undefined symbol
"_ZTVN6icinga18GetScopeExpressionE"
FAILED
___
freebsd-ports@freebsd.org
Walter Schwarzenfeld escribió:
This error message does not appear if I install devel/libcli.
But then:
Same here.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
On Wed, Aug 24, 2016 at 12:17:00PM +0200, Raul wrote:
>
> Walter Schwarzenfeld escribió:
>
> > This error message does not appear if I install devel/libcli.
> > But then:
>
> Same here.
From your portmaster logfile:
===> icinga2-2.5.1 depends on shared library: libconfig.so - found
(/usr/l
Lars Engels escribió:
This error message does not appear if I install devel/libcli.
Can you try to-rebuild libconfig and then icinga2 again?
sure
still, no changes
[]
# service icinga2 restart
Performing sanity check of icinga2 configuration:
/usr/local/lib/icinga2/libremote.so: Unde
Cause I only had a quick look in it, I have not configured it,
but
if I remove USESßssl
It seems to start (So I have eror messages, but it seems they are only
of missing cofiguration). Please, test it.
___
freebsd-ports@freebsd.org mailing list
htt
Forgot to mention, I have libressl as default, maybe this causes the
problem.
___
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"
Walter Schwarzenfeld escribió:
...
if I remove USESßssl
I have openssl from ports.
Removed ssl from USES and yes, starts without problem.
Basic configuration here, logs are clean and icingaweb2 also likes it.
Is this a PR case?.
___
freebsd-port
On Wed, Aug 24, 2016 at 02:36:24PM +0200, Raul wrote:
>
> Walter Schwarzenfeld escribió:
>
> ...
> > if I remove USESßssl
>
> I have openssl from ports.
>
> Removed ssl from USES and yes, starts without problem.
> Basic configuration here, logs are clean and icingaweb2 also likes it.
Strange.
On Wed, Aug 24, 2016 at 03:01:53PM +0200, Lars Engels wrote:
> On Wed, Aug 24, 2016 at 02:36:24PM +0200, Raul wrote:
> >
> > Walter Schwarzenfeld escribió:
> >
> > ...
> > > if I remove USESßssl
> >
> > I have openssl from ports.
> >
> > Removed ssl from USES and yes, starts without problem.
>
Dear all,
Am 24.08.2016 um 15:12 schrieb Lars Engels:
> I do not have *ssl from ports installed, so Icinga 2 uses the SSL
> version from base. That's why it works for me.
I face the exact same problem. I think SSL is required if you want to
talk to icinga installation on other hosts?
I personally
I updated my FreeBSD/amd64 10-STABLE system yesterday to r304677. Ever since,
/usr/local/bin/deluged from the net-p2p/deluge port has been generating these
messages in my system logs:
WARNING pid 54659 (python2.7): ioctl sign-extension ioctl c0206933
I rebuilt and reinstalled the port
On Wed, Aug 24, 2016 at 8:54 AM, Paul Mather <
freebsd-li...@gromit.dlib.vt.edu> wrote:
> I updated my FreeBSD/amd64 10-STABLE system yesterday to r304677. Ever
> since, /usr/local/bin/deluged from the net-p2p/deluge port has been
> generating these messages in my system logs:
>
> WARNING pid 546
On 2016-08-23 14:42, Matt Smith wrote:
On Aug 22 20:39, Mathieu Arnold wrote:
ports-committers is a *NEVER POST DIRECTLY TO* list, so, moving it to
ports@ where this belongs a lot more.
+--On 22 août 2016 20:30:15 +0200 Bernard Spil
wrote:
| Curious to know how we should procede with the upgr
On Aug 24 21:18, Bernard Spil wrote:
Today new vulnerabilities with (3)DES and BlowFish were made public and
I believe we'll see release of another paper which is OpenSSL 1.1
related with the release of OpenSSL 1.1.0. I have no knowledge if the
paper/report contained vulnerabilities that have p
Bernard Spil writes:
> Today new vulnerabilities with (3)DES and BlowFish were made public
You're referring to something different than the HTTPS/OpenVPN
attacks? Because it really wouldn't be accurate to describe those
as vulnerabilities in the ciphers.
Interested
___
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"
Hi,
Hire Developers as per Requirements :-
* iPhone Mobile Apps Developer
* iPad/iPod Mobile Apps Developer
* Android Mobile Apps Developer
* Web Designers
* Web Apps Developer
* .Net Programmers
* PHP Programmers
* Hybrid/Native Apps Developer
*
20 matches
Mail list logo
