www/hiawatha error

[ascilia]

Hi,
sending this because there is no maintainer for this port.
This port doesn't run anymore on 13, probably because of regexp changes.
It fails with message :
"Error in regexp '\s*(;\s*)?--(\s|')
Error initializing SQL injection detection."
Problem is at the beginning of session.c I think.
___
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: FreeBSD Port: openhab2-2.5.11 - openhab3?

[Thomas Gude via freebsd-ports]

Hi Frank, Alexander,

thanks for your feedback. Meanwhile I had created a port of my own, which was 
quite easy with the openhab2 port as template. One remark to your version: I 
have noticed that the openHAB folks have changed their naming scheme and have 
omitted the major version number from the package name, so the name of the 
openHAB 3 package on Linux is just ‚openhab‘ as opposed to ‚openhab3‘. I think 
that should also be reflected in the FreeBSD port.

Kind regards,
Thomas.

> Am 15.04.2021 um 20:03 schrieb Frank Preußer :
> 
> Hello everybody
>  
> openhab3 runs in a TrueNAS jail for me. I once attached the necessary files 
> to you, these must then be added to the /usr/ports/misc/ directory
> then simply enter the command "make install clean" in the two directories.
> And take the same options after the openhab2 install
>  
> Bye Frank.
>  
> Von: Alexander Leidinger 
> Gesendet: Sonntag, 11. April 2021 15:01
> An: Thomas Gude 
> Cc: po...@freebsd.org ; frank.preus...@hotmail.de 
> 
> Betreff: Re: FreeBSD Port: openhab2-2.5.11 - openhab3?
>  
>  
> Quoting Thomas Gude  (from Fri, 9 Apr 2021 
> 12:11:19 +0200):
>  
> > Hi netchild,
> > 
> > I am happily using the openhab2 port on my FreeBSD home server. The 
> > openHAB guys have released the new 3.0 version quite some time ago 
> > and I am wondering if you (or anyone else) have plans for (or are 
> > even already working on) a port for FreeBSD. Would be nice to get 
> > your feedback or thoughts on this.
>  
> Frank Preusser (in CC) has send me an openhab 3 port. I didn't had the 
> possibility to have a look at this. The last thing I remember is that 
> there were some issues still left (IIRC some java error). I'm not sure 
> if it migrates the openhab2 config. With openhab2 there was an update 
> script to update from a previous version of openhab2. I had to ... 
> sort of replace ... it with something similar, no idea how openhab-3 
> is doing this. I just remember that in the release notes it was 
> mentioned that they renamed from "openhab2" to "openhab".
>  
> Bye,
> Alexander.
> -- 
> http://www.Leidinger.net alexan...@leidinger.net: PGP 0x8F31830F9F2772BF
> http://www.FreeBSD.orgnetch...@freebsd.org  : PGP 0x8F31830F9F2772BF
>  
> 

___
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: [PATCH] net/bird2: add multicast patch from bird mailing list

[Jason A. Donenfeld]

Hi Olivier,

Great! Thanks for doing that.

Now just waiting for Bernhard to bump wireguard-kmod to the latest,
and we'll have working babel-over-wg again:
https://lists.zx2c4.com/pipermail/wireguard/2021-April/006634.html

Jason
___
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

[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
+-+
devel/py-spyder | 3.2.7   | v5.0.1
+-+
games/exult | 1.7.0.20210415  | 
snapshot-v1.7.0.20210417
+-+


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

Reported by:portscout!
___
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"

Boost versions

[Willem Jan Withagen via freebsd-ports]

Hi,

Ceph has moved to Boost 1.75, so now it is build with the project.
Which is of course a pity.

Are there any plans to also get Boost 1.75 in ports?

--WjW
___
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: Boost versions

[Kurt Jaeger]

Hi!

> Ceph has moved to Boost 1.75, so now it is build with the project.
> Which is of course a pity.
> 
> Are there any plans to also get Boost 1.75 in ports?

There is this one PR which touches the topic:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246106

It looks like a major undertaking!

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
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: Boost versions

[Li-Wen Hsu]

On Sat, Apr 17, 2021 at 6:58 PM Kurt Jaeger  wrote:
>
> Hi!
>
> > Ceph has moved to Boost 1.75, so now it is build with the project.
> > Which is of course a pity.
> >
> > Are there any plans to also get Boost 1.75 in ports?
>
> There is this one PR which touches the topic:
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246106
>
> It looks like a major undertaking!

I don't think office@ currently has enough manpower to maintain boost
ports. I suggest we need to seek a new maintainer or form a group to
maintain it.

I am also interested in updating boost, but I don't think I can
maintain it solely. I can help on porting, allocating resource to
test, but I don't think I can fix all the issues during upgrading and
exp-run myself alone. I hope the maintenance of the  complex ports
like this can be a team work.

Is anyone interested in joining the effort?

Best,
Li-Wen
___
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: Boost versions

[Willem Jan Withagen via freebsd-ports]

On 17-4-2021 13:09, Li-Wen Hsu wrote:

On Sat, Apr 17, 2021 at 6:58 PM Kurt Jaeger  wrote:


Hi!


Ceph has moved to Boost 1.75, so now it is build with the project.
Which is of course a pity.

Are there any plans to also get Boost 1.75 in ports?


There is this one PR which touches the topic:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246106

It looks like a major undertaking!


Why is that?
If I look at what is in phabricator, the largest part is diffs on the
plist?



I don't think office@ currently has enough manpower to maintain boost
ports. I suggest we need to seek a new maintainer or form a group to
maintain it.

I am also interested in updating boost, but I don't think I can
maintain it solely. I can help on porting, allocating resource to
test, but I don't think I can fix all the issues during upgrading and
exp-run myself alone. I hope the maintenance of the  complex ports
like this can be a team work.

Is anyone interested in joining the effort?


I am importing boost 1.75 raw into Ceph, and build it there.
That seems to work for what ceph needs.

There used to be several versions of Boost in parallel.
So perhaps that is the best way to avoid having to deal with ABI/API 
breakage...

After that it is up to the maintainers of the dependant packages to
update their package and start using boost-1.75.

The report in bugzilla suggests that that is all what other maintainers ask.

Or am I too simple in thinking this?

--WjW


___
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: Boost versions

[Kurt Jaeger]

Hi!

> > > > Ceph has moved to Boost 1.75, so now it is build with the project.
> > > > Which is of course a pity.
[...]
> > > It looks like a major undertaking!

> Why is that?
> If I look at what is in phabricator, the largest part is diffs on the
> plist?

Getting the port to build is one thing.

> There used to be several versions of Boost in parallel.

Yes. I have no idea how easy that would be.

The bigger part is, as you described:

> So perhaps that is the best way to avoid having to deal with ABI/API
> breakage...
> After that it is up to the maintainers of the dependant packages to
> update their package and start using boost-1.75.

There is the implicit assumption that a patch that updates
boost for all the dependent ports should also provide fixes
if those ports fail to build after the update. That is
the major task.

> Or am I too simple in thinking this?

No.

The normal way would be to provide the patch, testbuild all the
depends, list the broken ports in the PR and then a small group of
folks can try to fix them one by one.

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
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: Boost versions

[Willem Jan Withagen via freebsd-ports]

On 17-4-2021 14:16, Kurt Jaeger wrote:
Getting the port to build is one thing. 

Right that is probably not very complicated.
But the API/ABI changes are indeed a pain.
Reason for all kinds of trouble with Ceph as well.


There used to be several versions of Boost in parallel.

Yes. I have no idea how easy that would be.

Neither do I, it is just a vague recollection.
But there must be more libraries with that same challenge?


The bigger part is, as you described:


So perhaps that is the best way to avoid having to deal with ABI/API
breakage...
After that it is up to the maintainers of the dependant packages to
update their package and start using boost-1.75.

There is the implicit assumption that a patch that updates
boost for all the dependent ports should also provide fixes
if those ports fail to build after the update. That is
the major task.


There are "only" 490 ports that have boost in their Makefile.

Or am I too simple in thinking this?

No.

The normal way would be to provide the patch, testbuild all the
depends, list the broken ports in the PR and then a small group of
folks can try to fix them one by one.


I have no experience in that.
Keeping up with Ceph is already quite a task, since that is a very fast 
moving task.


--WjW
___
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: ssh_dispatch_run_fatal on Rpi4 building www/firefox

[bob prohaska]

On Sat, Apr 17, 2021 at 02:22:42PM +0100, tech-lists wrote:
> Hi,
> 
> On Wed, Apr 14, 2021 at 08:49:43AM -0700, bob prohaska wrote:
> > While attempting to compile www/firefox on an RPi4 running -current
> > the make process stopped with
> > 
> > Bad packet length 3554809687.
> > ssh_dispatch_run_fatal: Connection to 192.168.1.11 port 22: Connection
> 
> Is your compiling done on the microsd?
>
 
No, mechanical SATA drive in a USB3 case.

The immediate oddity was that make, running in the background,
was stopping when the ssh connection dropped. Normally, disconnecting
the controlling terminal on a background job doesn't kill the job.
 
> If it is, then that's your problem. The microsd is too slow. It causes
> bottlenecks and timeouts all over the place.
>
Agreed, but this wasn't a timeout. Maybe another misleading error message?

After several restarts of make in www/firefox which all stopped with
the same error I tried using the serial console. Make ran without
complaint and made considerable progress. 
 
When I learned of the -E option to ssh I stopped the make session,
set up error logging, ran make clean in www/firefox and started over.

Make subsequently ran to completion and produced a runnable www/firefox.
This tempts me to think whatevever  triggered the error was among the 
dependencies, which is difficult to understand and much harder to repeat.  

Thanks for replying!

bob prohaska

___
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: www/hiawatha error

[Mateusz Piotrowski]

Hi,

On 16/04/2021 16:49, asci...@free.fr wrote:

Hi,
sending this because there is no maintainer for this port.
This port doesn't run anymore on 13, probably because of regexp changes.
It fails with message :
"Error in regexp '\s*(;\s*)?--(\s|')
Error initializing SQL injection detection."
Problem is at the beginning of session.c I think.
___
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"


Cool, thanks for the report. Could you open a problem report on Bugzilla 
(https://bugs.freebsd.org/bugzilla/)? Thanks!


Regards,

Mateusz

___
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: Boost versions

[Willem Jan Withagen via freebsd-ports]

On 17-4-2021 13:09, Li-Wen Hsu wrote:

On Sat, Apr 17, 2021 at 6:58 PM Kurt Jaeger  wrote:


Hi!


Ceph has moved to Boost 1.75, so now it is build with the project.
Which is of course a pity.

Are there any plans to also get Boost 1.75 in ports?


There is this one PR which touches the topic:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246106

It looks like a major undertaking!


Why is that?
If I look at what is in phabricator, the largest part is diffs on the
plist?



I don't think office@ currently has enough manpower to maintain boost
ports. I suggest we need to seek a new maintainer or form a group to
maintain it.

I am also interested in updating boost, but I don't think I can
maintain it solely. I can help on porting, allocating resource to
test, but I don't think I can fix all the issues during upgrading and
exp-run myself alone. I hope the maintenance of the  complex ports
like this can be a team work.

Is anyone interested in joining the effort?


I am importing boost 1.75 raw into Ceph, and build it there.
That seems to work for what ceph needs.

There used to be several versions of Boost in parallel.
So perhaps that is the best way to avoid having to deal with ABI/API 
breakage...

After that it is up to the maintainers of the dependant packages to
update their package and start using boost-1.75.

The report in bugzilla suggests that that is all what other maintainers ask.

Or am I too simple in thinking this?

--WjW


___
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"

portlint -A for git?

[Junho Choi]

Hi,

portlint -A complains about $FreeBSD$ is missing but it's moved in git I
believe.

Is it a safe guess not to have $FreeBSD$ in port Makefile?

-- 
Junho Choi  | https://saturnsoft.net
___
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: portlint -A for git?

[Dan Mahoney (Ports)]

So does rclint :(

> On Apr 17, 2021, at 10:15 PM, Junho Choi  wrote:
> 
> Hi,
> 
> portlint -A complains about $FreeBSD$ is missing but it's moved in git I
> believe.
> 
> Is it a safe guess not to have $FreeBSD$ in port Makefile?
> 
> -- 
> Junho Choi  | https://saturnsoft.net
> ___
> 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"