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
Hi!
> > libtool: link: cc -g -pg -Wall -std=gnu99 -O2 -pipe -fstack-protector
> > -fno-strict-aliasing -fstack-protector -o mlrp mlrp-mlrmain.o
> > cli/.libs/libcli.a containers/.libs/libcontainers.a
> > stream/.libs/libstream.a input/.libs/libinput.a mapping/.libs/libmapping.a
> > output/.li
Hi!
Have a look at
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206785
It's not building on 9, but otherwise it looks fine.
--
p...@opsec.eu+49 171 3101372 4 years to go !
___
freebsd-ports@freebsd.org mailing
Hi,
url: "pkg+ftp://ftp.mysite/pub/FreeBSD/ports/${ABI}";
worked fine until ~2 weeks ago. Now I get an error message when running
pkg:
[helmut@BSDHelmut1064 ~]$ sudo pkg update
pkg: invalid scheme pkg+ftp
pkg: Cannot parse configuration file!
[helmut@BSDHelmut1064 ~]$
Was ftp support dropped?
There's a new option for limiting the number of valid URL schemes in
pkg.conf. Running `pkg config VALID_URL_SCHEME` prints a list of valid
URL schemes, but pkg+ftp is not a that list for me. Maybe an oversight?
Unless you want to use SRV records on your domain, just using ftp:// and
setting mirr
Tobias Kortkamp wrote:
> On Sun, Jan 31, 2016, at 03:46 PM, Helmut Schneider wrote:
> > Hi,
> >
> > url: "pkg+ftp://ftp.mysite/pub/FreeBSD/ports/${ABI}";
> >
> > worked fine until ~2 weeks ago. Now I get an error message when
> > running pkg:
> >
> > [helmut@BSDHelmut1064 ~]$ sudo pkg update
>
On 31/01/2016 14:46, Helmut Schneider wrote:
> Hi,
>
> url: "pkg+ftp://ftp.mysite/pub/FreeBSD/ports/${ABI}";
>
> worked fine until ~2 weeks ago. Now I get an error message when running
> pkg:
>
> [helmut@BSDHelmut1064 ~]$ sudo pkg update
> pkg: invalid scheme pkg+ftp
> pkg: Cannot parse configur
And besides, FTP is a broken protocol, for those who care about security.
--
Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-por
Hi!
On 31 January 2016 at 04:15, Kurt Jaeger wrote:
> Hi!
>
> Have a look at
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206785
>
> It's not building on 9, but otherwise it looks fine.
Wow, thank you!
Do I need to contact the maintainer and see why it won't build on 9?
Do you have the
Hi!
> Do I need to contact the maintainer and see why it won't build on 9?
The problem is that the port requires a recent flex, but 9.3 has
an older version. So for 9.3 the makefiles need some patch
to use the proper flex version.
> Do you have the build log that I can show him?
http://people.f
Hi!
> > The problem is that the port requires a recent flex, but 9.3 has
> > an older version. [...]
> I had a nearly similar problem with graphics/qgis. This way it works for me:
>
> .if ${OPSYS} == FreeBSD && ${OSVERSION} < 100
> BUILD_DEPENDS+= flex>=2.5.39:${PORTSDIR}/textproc/flex
Am 31.01.16 um 17:57 schrieb Kurt Jaeger:
> Hi!
>
>> Do I need to contact the maintainer and see why it won't build on 9?
>
> The problem is that the port requires a recent flex, but 9.3 has
> an older version. So for 9.3 the makefiles need some patch
> to use the proper flex version.
>
>> Do yo
Kurt Jaeger wrote:
> Project ERROR: Unknown module(s) in QT: xml printsupport concurrent
Quick guess: Try adding these modules to USE_QT5 in the port's Makefile.
Patrick
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listi
On 01/29/16 22:00, Pietro Cerutti wrote:
> On 2016-Jan-29, 19:29, Pietro Cerutti wrote:
>> I got reproducible errors in opensmtpd since I upgrade OpenSSL to
>> 1.0.2_8 today. 1.0.2_4 is fine. I'm bisecting versions right now.
>
> OpenSSL 1.0.2e works fine, 1.0.2f does not.
>
>>
>> Anybody else go
Hi!
> Kurt Jaeger wrote:
> > Project ERROR: Unknown module(s) in QT: xml printsupport concurrent
>
> Quick guess: Try adding these modules to USE_QT5 in the port's Makefile.
Yes, thanks. That solved that part, now it fails because the QT5
ports collection does not yet have a rcc port:
/usr/loca
Kurt Jaeger wrote:
> now it fails because the QT5 ports collection does not yet have a rcc port:
In the transition from Qt 4 to 5, many of these packages were reorganized,
and rcc has now found its place in qt5-buildtools.
Patrick
___
freebsd-ports@fre
Hi!
> Kurt Jaeger wrote:
> > now it fails because the QT5 ports collection does not yet have a rcc port:
>
> In the transition from Qt 4 to 5, many of these packages were reorganized,
> and rcc has now found its place in qt5-buildtools.
Ah! On it!
--
p...@opsec.eu+49 171 3101372
Vitaly Magerya gmail.com> writes:
>
> On 01/29/16 22:00, Pietro Cerutti wrote:
> > On 2016-Jan-29, 19:29, Pietro Cerutti wrote:
> >> I got reproducible errors in opensmtpd since I upgrade OpenSSL to
> >> 1.0.2_8 today. 1.0.2_4 is fine. I'm bisecting versions right now.
> >
> > OpenSSL 1.0.2e wor
On 31 Jan 2016, at 21:51, Vitaly Magerya wrote:
>
>> On 01/29/16 22:00, Pietro Cerutti wrote:
>>> On 2016-Jan-29, 19:29, Pietro Cerutti wrote:
>>> I got reproducible errors in opensmtpd since I upgrade OpenSSL to
>>> 1.0.2_8 today. 1.0.2_4 is fine. I'm bisecting versions right now.
>>
>> OpenSSL
19 matches
Mail list logo
