date:20160131

Re: Fritzing PORT

2016-01-31 Thread Patrick Hess

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/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: New port assistance for mlr

2016-01-31 Thread Kurt Jaeger

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
> CMAKE_ARGS+=  -DFLEX_EXECUTABLE:STRING=${LOCALBASE}/bin/flex
> CXXFLAGS+=-I${LOCALBASE}/include/flex
> .endif

This works if the port uses cmake. Unfortunatly, miller does not use cmake.

-- 
p...@opsec.eu+49 171 3101372 4 years to go !
___
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: New port assistance for mlr

2016-01-31 Thread jungle Boogie

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 build log that I can show him?

-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
xmpp: jungle-boo...@jit.si
___
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: opensmtpd / openssl 1.0.2_8 problem

2016-01-31 Thread Vitaly Magerya

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 got hit by this?
>>
>> Jan 29 18:08:36 mail smtpd[31270]: smtp-in: session 16287480c99a20ee: 
>> connection from host mail.ptrcrt.ch [192.168.1.1] established
>> Jan 29 18:08:36 mail smtpd[31268]: warn: lka -> pony: pipe closed
>> Jan 29 18:08:36 mail smtpd[31267]: warn: control -> pony: pipe closed
>> Jan 29 18:08:36 mail smtpd[31265]: warn: parent -> pony: pipe closed
>> Jan 29 18:08:36 mail smtpd[31266]: warn: queue -> pony: pipe closed
>> Jan 29 18:08:36 mail smtpd[31271]: warn: ca -> pony: pipe closed
>> Jan 29 18:08:36 mail smtpd[31269]: warn: scheduler -> control: pipe closed
>>
>> At this point the service goes down.

I'm seeing the same problem, and I'd really, really like to have my
smtpd running again.
___
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: New port assistance for mlr

2016-01-31 Thread 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 you have the build log that I can show him?

http://people.freebsd.org/~pi/logs/textproc__miller-93a-1454241832.txt

-- 
p...@opsec.eu+49 171 3101372 4 years to go !
___
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: New port assistance for mlr

2016-01-31 Thread Rainer Hurling

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 you have the build log that I can show him?
> 
> http://people.freebsd.org/~pi/logs/textproc__miller-93a-1454241832.txt
> 

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
CMAKE_ARGS+=-DFLEX_EXECUTABLE:STRING=${LOCALBASE}/bin/flex
CXXFLAGS+=  -I${LOCALBASE}/include/flex
.endif

HTH,
Rainer

___
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: Fritzing PORT

2016-01-31 Thread Kurt Jaeger

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/local/lib/qt5/bin/rcc -name phoenixresources phoenixresources.qrc -o 
qrc_phoenixresources.cpp
gmake[1]: /usr/local/lib/qt5/bin/rcc: Command not found

The qt4 rcc seems to work if one builds on a normal host, but
not in poudriere.

-- 
p...@opsec.eu+49 171 3101372 4 years to go !
___
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: Fritzing PORT

2016-01-31 Thread Kurt Jaeger

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 4 years to go !
___
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: Fritzing PORT

2016-01-31 Thread Patrick Hess

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@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: opensmtpd / openssl 1.0.2_8 problem

2016-01-31 Thread BjörnSchümann

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 works fine, 1.0.2f does not.
> > 
> >>
> >> Anybody else got hit by this?
> >>
>
> 
> I'm seeing the same problem, and I'd really, really like to have my
> smtpd running again.

I'm seeing it too. I tried running opensmtpd in debug-mode and got a few 
more messages:
Jan 30 15:02:30 mail smtpd[8899]: debug: smtp: new client on listener: 
0x8028c40
Jan 30 15:02:30 mail smtpd[8899]: smtp-in: session 02216b8ac1045eac: 
connection 
from host [...] established
Jan 30 15:02:30 mail smtpd[8897]: debug: lka: looking up pki "[...]"
Jan 30 15:02:30 mail smtpd[8899]: debug: session_start_ssl: switching to 
SSL
Jan 30 15:02:30 mail smtpd[8899]: debug: pony: rsae_sign
Jan 30 15:02:30 mail smtpd[8897]: warn: lka -> pony: pipe closed
Jan 30 15:02:30 mail smtpd[8894]: warn: parent -> pony: pipe closed
Jan 30 15:02:30 mail smtpd[8900]: warn: ca -> pony: pipe closed
Jan 30 15:02:30 mail smtpd[8896]: warn: control -> pony: pipe closed
Jan 30 15:02:30 mail smtpd[8895]: warn: queue -> pony: pipe closed
Jan 30 15:02:30 mail smtpd[8898]: warn: scheduler -> control: pipe closed

And the service goes down. I reverted back to openssl 1.0.2_6 to get it 
working a again. 

I think someone should file a bug.





___
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: opensmtpd / openssl 1.0.2_8 problem

2016-01-31 Thread Pietro Cerutti

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 1.0.2e works fine, 1.0.2f does not.
>> 
>>> 
>>> Anybody else got hit by this?
>>> 
>>> Jan 29 18:08:36 mail smtpd[31270]: smtp-in: session 16287480c99a20ee: 
>>> connection from host mail.ptrcrt.ch [192.168.1.1] established
>>> Jan 29 18:08:36 mail smtpd[31268]: warn: lka -> pony: pipe closed
>>> Jan 29 18:08:36 mail smtpd[31267]: warn: control -> pony: pipe closed
>>> Jan 29 18:08:36 mail smtpd[31265]: warn: parent -> pony: pipe closed
>>> Jan 29 18:08:36 mail smtpd[31266]: warn: queue -> pony: pipe closed
>>> Jan 29 18:08:36 mail smtpd[31271]: warn: ca -> pony: pipe closed
>>> Jan 29 18:08:36 mail smtpd[31269]: warn: scheduler -> control: pipe closed
>>> 
>>> At this point the service goes down.
> 
> I'm seeing the same problem, and I'd really, really like to have my
> smtpd running again.

As a workaround, you can downgrade OpenSSL to 1.0.2e.

Please follow progress here:
https://github.com/OpenSMTPD/OpenSMTPD/issues/650

-- 
Pietro Cerutti
g...@freebsd.org

PGP Public Key
http://gahr.ch/pgp
___
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

2016-01-31 Thread portscout

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
+-+
games/simsu | 1.3.1   | 1.3.2
+-+
net-mgmt/weathermap | 1.1.1   | 9.0.0
+-+


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"

Re: New port assistance for mlr

2016-01-31 Thread Kurt Jaeger

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/.libs/liboutput.a lib/.libs/libmlr.a dsls/.libs/libfdsl.a 
> > dsls/.libs/libpdsl.a -lm
> > /usr/bin/ld: undefined reference to symbol `_end' (try adding -lc)
> > //lib/libc.so.7: could not read symbols: Bad value
> > cc: error: linker command failed with exit code 1 (use -v to see invocation)

> I believe this is because you're using clang and mlr is expecting gcc.

If I build with gcc:

--- mlrp ---
/usr/local/bin/ld: //usr/lib/libc_p.a(sbrk.po): undefined reference to symbol 
'_end'
//lib/libc.so.7: error adding symbols: DSO missing from command line
collect2: error: ld returned 1 exit status

-- 
p...@opsec.eu+49 171 3101372 4 years to go !
___
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: New port assistance for mlr

2016-01-31 Thread Kurt Jaeger

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 list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Did pkg drop ftp support?

2016-01-31 Thread Helmut Schneider

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
> > pkg: invalid scheme pkg+ftp
> > pkg: Cannot parse configuration file!
> > [helmut@BSDHelmut1064 ~]$
> > 
> > Was ftp support dropped?
>
> Unless you want to use SRV records on your domain, just using ftp://
> and setting mirror_type to NONE for your repository should work fine

Did so. 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"

Re: Did pkg drop ftp support?

2016-01-31 Thread Matthew Seaman

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 configuration file!
> [helmut@BSDHelmut1064 ~]$
> 
> Was ftp support dropped?

No, this has not officially changed that recently.  There was a change
last November that limited the valid URL schemes in a repo.conf only to
the ones originally intended[+].  There never should been a 'pkg+ftp://'
URL scheme officially -- if it ever worked, that was a bug.

FTP support is still available, but you need URLs of the form:

url: "ftp://ftp.mysite/pub/FreeBSD/ports/${ABI};

This implies mirror_type = none, ie. that the listed FTP site simply
contains the repository with all the various packages available.

The 'pkg+http' or 'pkg+https' URL forms are special for when SRV records
are used for mirroring, which is a consequence of the requirement in RFC
2616 that only simple hostnames are used for http:// or https:// URLs.
If you're using a pkg+http:// or pkg+https:// URL then you must have
mirror_type = srv.

Cheers,

Matthew

[+] Introduced here:
https://github.com/freebsd/pkg/commit/9c2896737d2a5c2505cfb0c568a955c21881bf50

Bug fixed here:
https://github.com/freebsd/pkg/commit/833b65e043fa92a3fd6eda8372c70464a44d8d51

signature.asc
Description: OpenPGP digital signature

Re: Did pkg drop ftp support?

2016-01-31 Thread Dave Horsfall

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-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Did pkg drop ftp support?

2016-01-31 Thread Helmut Schneider

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?

___
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: Did pkg drop ftp support?

2016-01-31 Thread Tobias Kortkamp

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 mirror_type to NONE for your repository should work fine. Or try
adding to /usr/local/etc/pkg.conf

   VALID_URL_SCHEME = ["pkg+ftp"];

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
> pkg: invalid scheme pkg+ftp
> pkg: Cannot parse configuration file!
> [helmut@BSDHelmut1064 ~]$
> 
> Was ftp support dropped?
> 
> ___
> 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@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Fritzing PORT

Re: New port assistance for mlr

Re: New port assistance for mlr

Re: opensmtpd / openssl 1.0.2_8 problem

Re: New port assistance for mlr

Re: New port assistance for mlr

Re: Fritzing PORT

Re: Fritzing PORT

Re: Fritzing PORT

Re: opensmtpd / openssl 1.0.2_8 problem

Re: opensmtpd / openssl 1.0.2_8 problem

FreeBSD ports you maintain which are out of date

Re: New port assistance for mlr

Re: New port assistance for mlr

Re: Did pkg drop ftp support?

Re: Did pkg drop ftp support?

Re: Did pkg drop ftp support?

Did pkg drop ftp support?

Re: Did pkg drop ftp support?

19 matches

Site Navigation

Mail list logo

Footer information