Re: Bacula 9.2.1 fails on 10.4:

2018-08-27 Thread Dan Langille
> On Aug 27, 2018, at 7:26 PM, Yuri Pankov wrote: > > Dan Langille wrote: >> Why would Bacula 9.2.1 compile on 11.2 but fail on 10.4? >> The error is: >> bsock.c:439:20: error: use of undeclared identifier 'ENODATA' >> The complete build logs are at the following URLs. Can you see the cause. >>

Re: Bacula 9.2.1 fails on 10.4:

2018-08-27 Thread Yuri Pankov
Dan Langille wrote: Why would Bacula 9.2.1 compile on 11.2 but fail on 10.4? The error is: bsock.c:439:20: error: use of undeclared identifier 'ENODATA' The complete build logs are at the following URLs. Can you see the cause. 11.2:

Bacula 9.2.1 fails on 10.4:

2018-08-27 Thread Dan Langille
Why would Bacula 9.2.1 compile on 11.2 but fail on 10.4? The error is: bsock.c:439:20: error: use of undeclared identifier 'ENODATA' The complete build logs are at the following URLs. Can you see the cause. 11.2:

Re: Samba dependency to Bind

2018-08-27 Thread Xavier
On 27/08/2018 20:35, Xavier wrote: > Hi, to all, > > I tried to upgrad samba47 to 4.7.9 as it is in ports HEAD. > > But the build process fails upon dns/bind dep : > >> ===> samba47-4.7.9 depends on package: bind911>=9.11.0.0 - not found >> >> ===> bind911-9.11.4P1_1 conflicts with installed

Samba dependency to Bind

2018-08-27 Thread Xavier
Hi, to all, I tried to upgrad samba47 to 4.7.9 as it is in ports HEAD. But the build process fails upon dns/bind dep : > ===> samba47-4.7.9 depends on package: bind911>=9.11.0.0 - not found > > ===> bind911-9.11.4P1_1 conflicts with installed package(s): > bind913-9.13.2_1 Thxs

Committer needed: emulators/emulationstation

2018-08-27 Thread Kirk Coombs
Could I get a committer to take a look at this PR, which has been out there a couple of weeks? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230537 This is a new port for the excellent frontend that’s used by RetroPi for navigating emulators and ROMs. Thanks! Kirk Coombs

Re: dialog4ports-0.1.6 screwed up ?

2018-08-27 Thread Baptiste Daroussin
On Mon, Aug 27, 2018 at 01:45:47PM +0200, Axel Rau wrote: > Thanks Bapt, > > but… > > > Am 27.08.2018 um 13:30 schrieb Baptiste Daroussin : > > > > On Mon, Aug 27, 2018 at 01:25:20PM +0200, Axel Rau wrote: > > >> [build3:devel/librelp] root# printenv | grep DIALOG > >> [build3:devel/librelp]

Re: dialog4ports-0.1.6 screwed up ?

2018-08-27 Thread Axel Rau
Thanks Bapt, but… > Am 27.08.2018 um 13:30 schrieb Baptiste Daroussin : > > On Mon, Aug 27, 2018 at 01:25:20PM +0200, Axel Rau wrote: >> [build3:devel/librelp] root# printenv | grep DIALOG >> [build3:devel/librelp] root# grep DIALOG /etc/make.conf [build3:devel/librelp] root# make rmconfig

Re: dialog4ports-0.1.6 screwed up ?

2018-08-27 Thread Baptiste Daroussin
On Mon, Aug 27, 2018 at 01:25:20PM +0200, Axel Rau wrote: > Hi all, > > make config does not work with various ports. > dialog4ports says: Skipping ‚config‘ as NO_DIALOG is defined Somewhere you defined "NO_DIALOG" meaning dialog4ports is not executed. Either remove it or cleanup the old

dialog4ports-0.1.6 screwed up ?

2018-08-27 Thread Axel Rau
Hi all, make config does not work with various ports. dialog4ports says: Skipping ‚config‘ as NO_DIALOG is defined I have no idea whats going on here: [build3:devel/librelp] root# make config ===> Building/installing dialog4ports as it is required for the config dialog ===>

Re: Ports vs packages

2018-08-27 Thread Stefan Esser
Am 26.08.18 um 21:55 schrieb Gregory Byshenk: > On Sun, Aug 26, 2018 at 01:01:24PM +0200, Jos Chrispijn wrote: >> On 26-8-2018 2:07, Pete Wright wrote: >>> one thing i do for my systems is if there is an update to a port i >>> need/want to test before the official build cluster is done is run a