pkgs for aarch64 updated until April?

[Ronald Klop]

Hello,

Is it on purpose that pkgs for aarch64 are only updated until April.

http://pkg.freebsd.org/FreeBSD:11:aarch64/
http://pkg.freebsd.org/FreeBSD:12:aarch64/

Is this temporarily or should I look into compiling ports for this  
platform?


Regards,
Ronald.
___
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: pkgs for aarch64 updated until April?

[Ronald Klop]

On Thu, 31 May 2018 23:41:35 +0200, Sean Bruno  wrote:




On 05/31/18 08:32, Ronald Klop wrote:


Hello,

Is it on purpose that pkgs for aarch64 are only updated until April.

http://pkg.freebsd.org/FreeBSD:11:aarch64/
http://pkg.freebsd.org/FreeBSD:12:aarch64/

Is this temporarily or should I look into compiling ports for this
platform?

Regards,
Ronald.
___
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"




Temporary due to hardware problems.  The hardware problem should be
fixed next week and then packages will resume.

sean



Understandably. Thanks for your reply and the work on the project.

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

databases/mongodb34 only_for_archs=amd64?

[Ronald Klop]

Hi maintainer of mongodb34,

I'm trying to build mongodb34 on aarch64 (RPI3) now to use it with  
databases/unifi5. I will let you know how it works. I see messages on the  
web that it works on Linux on ARM.
Any known reason we have this architecture disabled? (Apart from available  
hardware for you to test.)


As the RPI's are pretty limited device this issue also caught my attention:
Bug 228494 - databases/mongodb34: Remove WITH_DEBUG=yes
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228494

Regards,
Ronald.
___
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: Archives of last quarterly package builds?

[Ronald Klop]

Van: grarpamp 
Datum: donderdag, 2 augustus 2018 22:21
Aan: freebsd-ports@freebsd.org
CC: freebsd-...@freebsd.org
Onderwerp: Re: Archives of last quarterly package builds?


> I've asked for this but the answer is
> "no we don't do that..  and have no plans to".

What is the rationale? Or is another model of pkg build,
distribution, and archiving coming?

It seems no more would be needed than
- an update to release / handbook / mirror info noting their status
as "final, to be removed [to archives] on date + timeframe", say 1 year.
- simple sysadmin on pkg / web side as part of each quarter activity.
- some storage space.
- obviously they are the final builds of the branch, thus frozen.

Anything else / prereqs missing to doing that?
 


I'm not involved in any pkg building, so don't take me too seriously.
Keeping archives also means keeping packages with security vulnerabilities. Why 
would somebody put that on the internet?

Regards,
Ronald.

___
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: OpenVPN produces garbage on TAP on -current

[Ronald Klop]

I'm running a very recent 12-current too and latest openvpn from pkgs. No 
problems.
I did not change anything in the defaults for the SSL-library it uses.

Ronald.

Van: Gleb Popov 
Datum: maandag, 6 augustus 2018 10:30
Aan: Lars Schotte 
CC: FreeBSD Ports , FreeBSD current 

Onderwerp: Re: OpenVPN produces garbage on TAP on -current


On Sun, Aug 5, 2018 at 11:51 PM, Lars Schotte  wrote:

> Here a bit of paste:
> https://paste.fedoraproject.org/paste/Hn4M2JqZ~5xccLWOVD1xUw/raw
> just to illustrate how it does not work.
>
> TAP device works good inside OS (FreeBSD current) however, everything
> that comes over OpenVPN is just garbage.
>

I'm using CURRENT from June 10 and tap device works fine for me with
OpenVPN 2.4.6_1


> --
>  Lars Schotte
>  Mudro?ova 13
> 92101 Pie??any
> ___
> 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-curr...@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-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: Packages don't seem to update for around a week right now

[Ronald Klop]

On Sat, 11 Aug 2018 00:43:08 +0200, Maxim Filimonov  wrote:


Kevin,

Looks like you're absolutely right.

Moreover, my packages got updates just now. Thank you all for your time  
and patience.





You can see the status of pkg building here:
https://pkg-status.freebsd.org/builds?type=package

current and past builds per platform/version are displayed here:
http://beefy9.nyi.freebsd.org/jail.html?mastername=111amd64-default
http://beefy9.nyi.freebsd.org/build.html?mastername=111amd64-default&build=476857

Regards,

Ronald.




wbr, Maxim Filimonov
c...@bein.link




On 11 Aug 2018, at 01:19, Kevin Oberman  wrote:

On Fri, Aug 10, 2018 at 1:37 PM Nathan Owens via freebsd-ports <
freebsd-ports@freebsd.org > wrote:

I haven’t got any lately. I think I heard on BSDNow that builds are  
done

on certain days for different ARCHs


Sent from Yahoo Mail for iPhone


On Friday, August 10, 2018, 2:16 PM, Maxim V Filimonov 
wrote:

Hello everyone,

I have a bunch of 11.2 machines set up to have the latest packages. The
problem is, the latest pkg branch hasn't been updated since Aug 1.  
What's
the matter with that? Is it just me, or something happened/is  
happening?




wbr, Maxim V Filimonov
c...@bein.link



First, I don't believe that they are doing scheduled update any longer,
just starting a new one when the old one is completed. This means that  
the
time between updates is highly variable.Ones with BIG builds like  
chromium,
libreoffice, etc. can really slow things down. Still, this is a LONG  
time.


I have seen no update since the new xorgserver port resulted in the  
removal
of many, many small X ports that are now consolidated into xorgserver.  
This
also meant the rebuild a a LARGE number of ports that depend on the  
removed
ports. I had to build over a hundred ports after this on the system  
where I
build all ports as opposed to using packages. I'm suspicious that this  
lead

to some problem with the package building system that is preventing the
completion of an update.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com 
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
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"

___
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: Compiling firefox on Raspberry Pi 2

[Ronald Klop]

On Sat, 20 Oct 2018 05:32:14 +0200, bob prohaska   
wrote:



Attempts to compile firefox63 on an RPI2 fail with
===>  rust-1.29.2 is only for aarch64 amd64 i386, while you are running  
armv6

(reason: requires prebuilt bootstrap compiler).
*** Error code 1

while compilation of firefox-esr stops with
dt_modtext:/usr/src/cddl/contrib/opensolaris/lib/libdtrace/common/dt_link.c(856):  
arm not implemented
dtrace: failed to link script  
/usr/ports/www/firefox-esr/work/firefox-52.8.0esr/js/src/devtools/javascript-trace.d:  
an error was encountered while processing jsarray.o
gmake[5]: ***  
[/usr/ports/www/firefox-esr/work/firefox-52.8.0esr/config/rules.mk:788:  
js-dtrace.o] Error 1
gmake[5]: Leaving directory  
'/usr/ports/www/firefox-esr/work/.build/js/src'
gmake[4]: ***  
[/usr/ports/www/firefox-esr/work/firefox-52.8.0esr/config/recurse.mk:71:  
js/src/target] Error 2

gmake[4]: Leaving directory '/usr/ports/www/firefox-esr/work/.build'
gmake[3]: ***  
[/usr/ports/www/firefox-esr/work/firefox-52.8.0esr/config/recurse.mk:33:  
compile] Error 2

gmake[3]: Leaving directory '/usr/ports/www/firefox-esr/work/.build'
gmake[2]: ***  
[/usr/ports/www/firefox-esr/work/firefox-52.8.0esr/config/rules.mk:523:  
all] Error 2


Can anybody suggest workaround for either problem?


Not a workaround. Buy you can try to port rust to armv6. Which will  
benefit some other ports also.

Rust has tier 2 support for linux/arm, so it might be not so hard to do.
https://forge.rust-lang.org/platform-support.html

For Firefox-esr, try to disable DTRACE in the build options of the port.  
It says it is not implemented on arm.


Regards,
Ronald.




Thanks for reading,

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"

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

12-stable ports for arm/arm64?

[Ronald Klop]

Hello,

I now the release process of 12.0 is ongoing. But I'm wondering when the pkg 
building for arm and arm64 will start? Is that after the releng/12.0 branch 
next week?
https://www.freebsd.org/releases/12.0R/schedule.html

Or are there other plans?

Regards,

Ronald.

___
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: ninja error building webkit2-gtk3 on rpi3

[Ronald Klop]

On Thu, 08 Nov 2018 02:18:57 +0100, bob prohaska   
wrote:


Ports are at 484411, system is at 133. Attempts to compile  
webkit2-gtk3

stops with


 -c DerivedSources/JavaScriptCore/unified-sources/UnifiedSource86.cpp
ninja: build stopped: subcommand failed.
===> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure  
to

the maintainer.



Do this part of the message. Before building:

export MAKE_JOBS_UNSAFE=yes

That will give a more clear error.

Regards,
Ronald.





*** Error code 1

Stop.
make: stopped in /usr/ports/www/webkit2-gtk3

I can't find a more detailed statement of what went wrong anywhere in the
make output.

Thanks for reading, any suggestions appreciated.

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"

___
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: 12.0-RC1: unifi5 can't be installed due to mongodb34 build failure

[Ronald Klop]

On Sat, 24 Nov 2018 04:59:50 +0100, Andrey Pevnev   
wrote:


Or you can install mongodb36 and it would probably work. Works fine for  
me (I know Ubnt says they want 3.4).


I asked for this in a PR.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233482

Regards,
Ronald.





On Nov 23, 2018, at 11:35 AM, Kurt Jaeger  wrote:

Hi!

After upgrading my FreeBSD machine to 12.0-RC1, unifi5 can't be  
installed

due to mongodb34 build failure. It looks like caused by openssl change.
Is there anything in progress?


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

has a patch. If you find the time, can you build and test it ?

--
p...@freebsd.org +49 171 3101372  2 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"


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

[Ronald Klop]

On Thu, 06 Dec 2018 08:55:25 +0100, Daniel Morante   
wrote:


This port www/webcalendar expired back in 2016-01-25 due to PHP 5.4  
being EOL.  However the author of this application has recently updated  
it to use PHP 7 and moved the code base to Github:  
https://github.com/craigk5n/webcalendar/releases/tag/v1.2.9


Any chance you could update and re-enable this port?  If there is no  
maintainer, I would be happy to take it over.



One way forward is to create a PR (see https://bugs.freebsd.org/) with a  
patch which makes the port working again.
As the port is currently deleted it does not have a maintainer (I guess)  
so you can pick it up immediately probably.


As a reference this is the list of previous PRs about this port.
https://bugs.freebsd.org/bugzilla/buglist.cgi?bug_status=__open__&bug_status=__closed__&bug_status=New&bug_status=Open&bug_status=In%20Progress&bug_status=Closed&bug_status=UNCONFIRMED&f0=OP&f1=OP&f2=product&f3=component&f4=alias&f5=short_desc&f7=CP&f8=CP&j1=OR&list_id=264894&o2=substring&o3=substring&o4=substring&o5=substring&o6=substring&order=changeddate%20DESC%2Cbug_id&query_format=advanced&v2=webcalendar&v3=webcalendar&v4=webcalendar&v5=webcalendar&v6=webcalendar

Regards,

Ronald.
___
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: Deletion of the grpn port

[Ronald Klop]

On Wed, 26 Dec 2018 20:52:58 +0100, Bob Willcox  wrote:


I just noticed that grpn has been delete from the freebsd ports. This is
apparently due to its use of glib12 (which is deprecated) and lack of a
maintainer. Anyone know how much difference there is between glib12 and  
the
current version (glib20 I believe)? I've been using grpn for more years  
than I

can remember and hate to see it disappear.



As the application does not look very fancy  
(http://lashwhip.com/grpn.html) I think it might be quite easy. The  
hardest part is finding somebody willing to do the work for you. Or you  
could try it yourself.
You could try to contact the original author also. As the latest version  
of this port is from 2002 I don't know how active he is on this project  
nowadays.


Regards,
Ronald.
___
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"

committer for PR 235057

[Ronald Klop]

Hello,

I'm looking for a committer for this PR.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235057
databases/mongodb36: support arm64/aarch64

The issue is reviewed + timed out afaik.

Regards,
Ronald.

___
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: unifi5-5.10.20

[Ronald Klop]

On Wed, 24 Apr 2019 02:57:57 +0200, Doug Sampson   
wrote:



feld-

Are there any plans to upgrade the unifi port to 5.10.21? I appear to be  
having some difficulty running 5.10.20 on five APs and wondered if  
5.10.21 would be out any time soon?



You can try the port https://www.freshports.org/net-mgmt/unifi-devel/ in  
the meantime.


Regards.
Ronald.




~Doug

Doug Sampson
IT Administrator | DawnSignPress, Inc.
858-768-0486
do...@dawnsign.com |  
dawnsign.com

[facebook_icon_small]facebook.com/DawnSign
[email_signature_resized]

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

net-mgmt/unifi5 committer?

[Ronald Klop]

Hi,
The maintainer timed out. Is anybody willing to commit this? Hopefully before 
the quarterly branch.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238623



Regards,


Ronald 
___

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: Any alternatives to NONE cipher ssh or bbcp for gigabit+ zfs send/recv?

[Ronald Klop]

On Thu, 08 Aug 2019 19:13:24 +0200, Freddie Cash  wrote:


We have gigabit fibre between our main data centre and our off-site data
centre across town.  We do zfs send/recv of our backups between the sites
over a dedicated gigabit fibre link.  Our ZFS storage servers are running
older AMD Opteron (pre-bulldozer) CPUs, so there's very little in the way
of encryption extension support.

Running zfs send/recv over regular SSH gives horrible throughput (100-250
Mbps max).

In the past, we compiled the openssh-portable port with the HPN patches  
and

NONE cipher.  That allowed us to saturate the gigabit link for zfs
send/recv and rsync transfers.  Then those were removed from the port and
base OpenSSH.  (There were patches floating around for awhile, but we try
not to build from source anymore.)

Then we found bbcp, which works great for the zfs send/recv process,
saturating the gigabit link.  Doesn't work for rsync, but that's okay (we
only use rsync for our regular backup process, and that's limited by the
remote school's Internet link).

An update [1] to the bbcp port broke some things, but we found the  
magical

combination of command-line options to make it work reliably in our
environment.  And a project was underway to update bbcp [2] to a newer
version and make it work better on FreeBSD, but it fizzled out.  And now
the bbcp port has been removed.

We have an archived copy of the bbcp package that works for us on FreeBSD
12 (amd64).  We'll continue to use that as long as it works (probably  
until

FBSD 12 is EoL).

Are there any alternatives to HPN/NONE cipher / bbcp to allow an older
Opteron system to saturate a gigabit link with zfs send/recv or rsync?
This is strictly over a private network, so encryption is only needed for
the authentication bit, not for the actual data transfer.  Preferably
something that's available in the ports tree as a binary package.  :)

Suggestions?

[1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197035
[2] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229115

(Thanks to all who attempted to keep bbcp working on FreeBSD.  Sounds  
like

it wasn't much fun, but we really appreciate the effort.)



Does mbuffer do the job for you?
https://www.freshports.org/misc/mbuffer
It has minimal support for limiting which host can connect:  -I : :  
use network port  as input, allow only host  to connect

https://www.freebsd.org/cgi/man.cgi?query=mbuffer&sektion=1&apropos=0&manpath=FreeBSD+9.0-RELEASE+and+Ports

Something like this might work:
Server: mbuffer -I client-ip:8000 | zfs recv
Client: zfs send | mbuffer -O server-ip:8000

You might setup the server process using ssh to keep it flexible.
Client: ssh -F server-ip 'mbuffer -I client-ip:8000 | zfs recv'
Client: zfs zend | mbuber -O server-ip:8000

Regards,
Ronald,
___
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"

fast aarch64 computer for creating a port?

[Ronald Klop]

Hello,

I'm trying to create a port for Mongodb 4.2. To aarch64 and amd64.
Especially my RPI3 for aarch64 takes about 2 days to compile this. Does the 
FreeBSD community have a fast aarch64 machine I could use to do test work? 
Maybe some access to a jail could be provided.

Regards,
Ronald.

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

looking for a committer for databases/mongodb* (security)

[Ronald Klop]

Hello,

I'm looking for a committer for these PRs.

First (containing vuxml entries also):
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239717 (mongodb34  
security update)


And then these two dependencies:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240126 (mongodb36  
security update)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241078 (mongodb34  
followup update)


I've fixed all suggestions in the PRs and verified on #freebsd-ports (irc)  
that the PRs are in good enough shape now.


Regards,
Ronald.
___
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"

scons and python3?

[Ronald Klop]

Hi,

For porting mongodb42 I need scons with python3.
There are some attempts on making the scons port flavored, but that did  
not work out.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237122
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230734
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239792

What is the way forward?
- A port like scons-py3 as a slave port of scons?
- If I could overwrite MAKE_CMD to "MAKE_CMD=python3 ${SCONS}" it would  
help, but it is fixed in /usr/ports/Mk/Uses/scons.mk


Any thoughts?

Regards,

Ronald.
___
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: scons and python3?

[Ronald Klop]

Cc-ing some of the people from the PRs. I don't know if they are still 
interested.

Would a master ports construction be a possible solution to the scons+python3 
problem?

diff -urN /usr/ports/devel/scons/Makefile devel/scons/Makefile
--- /usr/ports/devel/scons/Makefile2019-10-02 21:51:04.0 +0200
+++ devel/scons/Makefile2019-10-24 11:48:48.997995000 +0200
@@ -14,7 +14,7 @@

RUN_DEPENDS=gm4:devel/m4

-USES=python:2.7 shebangfix
+USES?=python:2.7 shebangfix
USE_PYTHON=autoplist distutils

NO_ARCH=yes


And the sub-port:
$ cat devel/scons-py3/Makefile
# $FreeBSD: head/devel/scons/Makefile 513618 2019-10-02 19:51:04Z sunpoet $

MASTERDIR=${.CURDIR}/../scons
PKGNAMESUFFIX=-py3
USES=python:3.5+ shebangfix

.include "${MASTERDIR}/Makefile"


With a little adjustment of /usr/ports/Mk/Uses/scons.mk this might work or not?
Addition of ${scons_ARGS}=py3 maybe?
(I'm not a master of the ports system, so please enlighten me if I miss 
something.)

Regards,
Ronald.

PS: My goal is still a port of mongodb42 which requires python3 for SCons.


Van: Ronald Klop 
Datum: maandag, 21 oktober 2019 22:22
Aan: freebsd-ports@freebsd.org
Onderwerp: scons and python3?


Hi,

For porting mongodb42 I need scons with python3.
There are some attempts on making the scons port flavored, but that did  
not work out.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237122
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230734
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239792

What is the way forward?
- A port like scons-py3 as a slave port of scons?
- If I could overwrite MAKE_CMD to "MAKE_CMD=python3 ${SCONS}" it would  
help, but it is fixed in /usr/ports/Mk/Uses/scons.mk


Any thoughts?

Regards,

Ronald.
___
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: scons and python3?

[Ronald Klop]

I created PR 241463 with my changes.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241463

This works for me to create a new port (mongodb42) using scons+python3. And it 
is backwards compatible for existing ports with python2 AFAIK.

If this needs more work from my side, please tell.

Regards,
Ronald.

Van: Ronald Klop 
Datum: donderdag, 24 oktober 2019 12:09
Aan: freebsd-ports@freebsd.org, Sunpoet Po-Chuan Hsieh , Eir Nym 

Onderwerp: Re: scons and python3?


Cc-ing some of the people from the PRs. I don't know if they are still 
interested.

Would a master ports construction be a possible solution to the scons+python3 
problem?

diff -urN /usr/ports/devel/scons/Makefile devel/scons/Makefile
--- /usr/ports/devel/scons/Makefile2019-10-02 21:51:04.0 +0200
+++ devel/scons/Makefile2019-10-24 11:48:48.997995000 +0200
@@ -14,7 +14,7 @@
 
 RUN_DEPENDS=gm4:devel/m4
 
-USES=python:2.7 shebangfix

+USES?=python:2.7 shebangfix
 USE_PYTHON=autoplist distutils
 
 NO_ARCH=yes



And the sub-port:
$ cat devel/scons-py3/Makefile
# $FreeBSD: head/devel/scons/Makefile 513618 2019-10-02 19:51:04Z sunpoet $

MASTERDIR=${.CURDIR}/../scons
PKGNAMESUFFIX=-py3
USES=python:3.5+ shebangfix

.include "${MASTERDIR}/Makefile"


With a little adjustment of /usr/ports/Mk/Uses/scons.mk this might work or not?
Addition of ${scons_ARGS}=py3 maybe?
(I'm not a master of the ports system, so please enlighten me if I miss 
something.)

Regards,
Ronald.

PS: My goal is still a port of mongodb42 which requires python3 for SCons.

 
Van: Ronald Klop 

Datum: maandag, 21 oktober 2019 22:22
Aan: freebsd-ports@freebsd.org
Onderwerp: scons and python3?
>
> Hi,
>
> For porting mongodb42 I need scons with python3.
> There are some attempts on making the scons port flavored, but that did  
> not work out.

> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237122
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230734
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239792
>
> What is the way forward?
> - A port like scons-py3 as a slave port of scons?
> - If I could overwrite MAKE_CMD to "MAKE_CMD=python3 ${SCONS}" it would  
> help, but it is fixed in /usr/ports/Mk/Uses/scons.mk

>
> Any thoughts?
>
> Regards,
>
> Ronald.
> ___
> 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"




___
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: scons and python3? (PR 241463)

[Ronald Klop]

On Fri, 25 Oct 2019 04:05:34 +0200, Tatsuki Makino  
 wrote:



Can it be solved with USE_PYTHON=concurrent and FLAVOR?


I don't know. If I look at the previous attempts to use flavors. It seems  
hard to keep it backwards compatible. But not all patches of all efforts  
are available via the PRs. So I'm not sure what the real problems are with  
flavouring.
I'm especially interested in the patches of  
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237122 (by sunpoet) to  
look at and learn what has already been tried.


Regards,
Ronald.
___
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"

pkgs for aarch64 head not building anymore

[Ronald Klop]

Hi,

The pkg build for aarch64 head crashes.

http://thunderx1.nyi.freebsd.org/build.html?mastername=head-arm64-default&build=p523508_s356869

The error is:

"
install  -m 0644 /wrkdirs/usr/ports/ports-mgmt/pkg/work/pkg-1.12.0/NEWS  
/wrkdirs/usr/ports/ports-mgmt/pkg/work/stage/usr/local/share/doc/pkg/NEWS

> Compressing man pages (compress-man)
Bad system call
Bad system call
===
===
===>  Building package for pkg-1.12.0
Bad system call
*** Error code 140
"

See the bottom of:  
http://thunderx1.nyi.freebsd.org/data/head-arm64-default/p523508_s356869/logs/errors/pkg-1.12.0.log


It is the third failure in a row with the same error.
http://thunderx1.nyi.freebsd.org/jail.html?mastername=head-arm64-default

Is this because of this?
Host OSVERSION: 132
Jail OSVERSION: 1300076

Anyways. I don't know who maintains this, so I write to the mailinglists  
of ports and arm.


Regards,
Ronald.
___
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"

Xorg 1.20 no mouse buttons

[Ronald Klop]

Hello,

Since my upgrade to Xorg 1.20 things seem to work except that no mouse  
buttons work. Pointer movement works good still.
I'm running a fairly recent FreeBSD 13-CURRENT in VirtualBox (On Windows  
10). The mouse is a touchpad on my Lenovo IdeaPad laptop.


Previously it worked using fine.

What can I do or debug to fix this?

Regards,
Ronald.


[23.241]
X.Org X Server 1.20.7
X Protocol Version 11, Revision 0
[23.241] Build Operating System: FreeBSD 13.0-CURRENT amd64
[23.241] Current Operating System: FreeBSD sjakie 13.0-CURRENT FreeBSD
13.0-CURRENT #4 r357762M: Sun Feb 16 12:16:08 CET 2020
builder@sjakie:/data/src/obj-freebsd-current/data/src/freebsd-current/amd64.amd64/sys/GENERIC-NODEBUG
amd64
[23.241] Build Date: 22 February 2020  07:06:47AM
[23.241]
[23.241] Current version of pixman: 0.38.4
[23.241]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[23.241] Markers: (--) probed, (**) from config file, (==) default
setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[23.241] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Feb 24
19:18:14 2020
[23.244] (==) Using system config directory
"/usr/local/share/X11/xorg.conf.d"
[23.246] (==) No Layout section.  Using the first Screen section.
[23.246] (==) No screen section available. Using defaults.
[23.246] (**) |-->Screen "Default Screen Section" (0)
[23.246] (**) |   |-->Monitor ""
[23.247] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[23.247] (==) Automatically adding devices
[23.247] (==) Automatically enabling devices
[23.247] (==) Not automatically adding GPU devices
[23.247] (==) Max clients allowed: 256, resource mask: 0x1f
[23.262] (==) FontPath set to:
/usr/local/share/fonts/misc/,
/usr/local/share/fonts/TTF/,
/usr/local/share/fonts/OTF/,
/usr/local/share/fonts/Type1/,
/usr/local/share/fonts/100dpi/,
/usr/local/share/fonts/75dpi/,
catalogue:/usr/local/etc/X11/fontpath.d
[23.263] (==) ModulePath set to "/usr/local/lib/xorg/modules"
[23.263] (II) The server relies on udev to provide the list of input
devices.
If no devices become available, reconfigure udev or disable
AutoAddDevices.
[23.263] (II) Loader magic: 0x435010
[23.263] (II) Module ABI versions:
[23.263]X.Org ANSI C Emulation: 0.4
[23.263]X.Org Video Driver: 24.1
[23.263]X.Org XInput driver : 24.1
[23.263]X.Org Server Extension : 10.0
[23.263] (--) PCI:*(0@0:2:0) 80ee:beef:: rev 0, Mem @
0xe000/134217728, BIOS @ 0x/65536
[23.263] (II) LoadModule: "glx"
[23.265] (II) Loading /usr/local/lib/xorg/modules/extensions/libglx.so
[23.292] (II) Module glx: vendor="X.Org Foundation"
[23.292]compiled for 1.20.7, module version = 1.0.0
[23.292]ABI class: X.Org Server Extension, version 10.0
[23.292] (==) Matched vboxvideo as autoconfigured driver 0
[23.292] (==) Matched modesetting as autoconfigured driver 1
[23.292] (==) Matched scfb as autoconfigured driver 2
[23.292] (==) Matched vesa as autoconfigured driver 3
[23.292] (==) Assigned the driver to the xf86ConfigLayout
[23.292] (II) LoadModule: "vboxvideo"
[23.292] (II) Loading
/usr/local/lib/xorg/modules/drivers/vboxvideo_drv.so
[23.294] (II) Module vboxvideo: vendor="Oracle Corporation"
[23.294]compiled for 1.20.7, module version = 1.0.1
[23.294]Module class: X.Org Video Driver
[23.294]ABI class: X.Org Video Driver, version 24.1
[23.294] (**) Load address of symbol "VBOXVIDEO" is 0x801b8d010
[23.294] (II) LoadModule: "modesetting"
[23.294] (II) Loading
/usr/local/lib/xorg/modules/drivers/modesetting_drv.so
[23.295] (II) Module modesetting: vendor="X.Org Foundation"
[23.295]compiled for 1.20.7, module version = 1.20.7
[23.295]Module class: X.Org Video Driver
[23.295]ABI class: X.Org Video Driver, version 24.1
[23.295] (II) LoadModule: "scfb"
[23.295] (II) Loading /usr/local/lib/xorg/modules/drivers/scfb_drv.so
[23.297] (II) Module scfb: vendor="X.Org Foundation"
[23.297]compiled for 1.20.7, module version = 0.0.5
[23.297]ABI class: X.Org Video Driver, version 24.1
[23.297] (II) LoadModule: "vesa"
[23.297] (II) Loading /usr/local/lib/xorg/modules/drivers/vesa_drv.so
[23.298] (II) Module vesa: vendor="X.Org Foundation"
[23.298]compiled for 1.20.7, module version = 2.4.0
[23.298]Module class: X.Org Video Driver
[23.298]ABI class: X.Org Video Driver, version 24.1
[23.298] (II) VBoxVideo: guest driver for VirtualBox: vbox
[23.298] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[23.298] (II) scfb: driver for 

Re: Xorg 1.20 no mouse buttons

[Ronald Klop]

It works again.
Changed back from virtualboxvideo from drm-devel-kmod to the driver from  
virtualbox-ose-additions. But did some other changes at the same time  
also. Not sure yet what happened, but it was integration of the mouse with  
virtualbox which failed somehow.


Regards,
Ronald.



On Wed, 26 Feb 2020 20:40:14 +0100, Ronald Klop   
wrote:



Hello,

Since my upgrade to Xorg 1.20 things seem to work except that no mouse  
buttons work. Pointer movement works good still.
I'm running a fairly recent FreeBSD 13-CURRENT in VirtualBox (On Windows  
10). The mouse is a touchpad on my Lenovo IdeaPad laptop.


Previously it worked using fine.

What can I do or debug to fix this?

Regards,
Ronald.


[23.241]
X.Org X Server 1.20.7
X Protocol Version 11, Revision 0
[23.241] Build Operating System: FreeBSD 13.0-CURRENT amd64
[23.241] Current Operating System: FreeBSD sjakie 13.0-CURRENT  
FreeBSD

13.0-CURRENT #4 r357762M: Sun Feb 16 12:16:08 CET 2020
builder@sjakie:/data/src/obj-freebsd-current/data/src/freebsd-current/amd64.amd64/sys/GENERIC-NODEBUG
amd64
[23.241] Build Date: 22 February 2020  07:06:47AM
[23.241]
[23.241] Current version of pixman: 0.38.4
[23.241]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[23.241] Markers: (--) probed, (**) from config file, (==) default
setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[23.241] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Feb 24
19:18:14 2020
[23.244] (==) Using system config directory
"/usr/local/share/X11/xorg.conf.d"
[23.246] (==) No Layout section.  Using the first Screen section.
[23.246] (==) No screen section available. Using defaults.
[23.246] (**) |-->Screen "Default Screen Section" (0)
[23.246] (**) |   |-->Monitor ""
[23.247] (==) No monitor specified for screen "Default Screen  
Section".

Using a default monitor configuration.
[23.247] (==) Automatically adding devices
[23.247] (==) Automatically enabling devices
[23.247] (==) Not automatically adding GPU devices
[23.247] (==) Max clients allowed: 256, resource mask: 0x1f
[23.262] (==) FontPath set to:
/usr/local/share/fonts/misc/,
/usr/local/share/fonts/TTF/,
/usr/local/share/fonts/OTF/,
/usr/local/share/fonts/Type1/,
/usr/local/share/fonts/100dpi/,
/usr/local/share/fonts/75dpi/,
catalogue:/usr/local/etc/X11/fontpath.d
[23.263] (==) ModulePath set to "/usr/local/lib/xorg/modules"
[23.263] (II) The server relies on udev to provide the list of input
devices.
If no devices become available, reconfigure udev or disable
AutoAddDevices.
[23.263] (II) Loader magic: 0x435010
[23.263] (II) Module ABI versions:
[23.263]X.Org ANSI C Emulation: 0.4
[23.263]X.Org Video Driver: 24.1
[23.263]X.Org XInput driver : 24.1
[23.263]X.Org Server Extension : 10.0
[23.263] (--) PCI:*(0@0:2:0) 80ee:beef:: rev 0, Mem @
0xe000/134217728, BIOS @ 0x/65536
[23.263] (II) LoadModule: "glx"
[23.265] (II) Loading  
/usr/local/lib/xorg/modules/extensions/libglx.so

[23.292] (II) Module glx: vendor="X.Org Foundation"
[23.292]compiled for 1.20.7, module version = 1.0.0
[23.292]ABI class: X.Org Server Extension, version 10.0
[23.292] (==) Matched vboxvideo as autoconfigured driver 0
[23.292] (==) Matched modesetting as autoconfigured driver 1
[23.292] (==) Matched scfb as autoconfigured driver 2
[23.292] (==) Matched vesa as autoconfigured driver 3
[23.292] (==) Assigned the driver to the xf86ConfigLayout
[23.292] (II) LoadModule: "vboxvideo"
[23.292] (II) Loading
/usr/local/lib/xorg/modules/drivers/vboxvideo_drv.so
[23.294] (II) Module vboxvideo: vendor="Oracle Corporation"
[23.294]compiled for 1.20.7, module version = 1.0.1
[23.294]Module class: X.Org Video Driver
[23.294]ABI class: X.Org Video Driver, version 24.1
[23.294] (**) Load address of symbol "VBOXVIDEO" is 0x801b8d010
[23.294] (II) LoadModule: "modesetting"
[23.294] (II) Loading
/usr/local/lib/xorg/modules/drivers/modesetting_drv.so
[23.295] (II) Module modesetting: vendor="X.Org Foundation"
[23.295]compiled for 1.20.7, module version = 1.20.7
[23.295]Module class: X.Org Video Driver
[23.295]ABI class: X.Org Video Driver, version 24.1
[23.295] (II) LoadModule: "scfb"
[23.295] (II) Loading /usr/local/lib/xorg/modules/drivers/scfb_drv.so
[23.297] (II) Module scfb: vendor="X.Org Foundation"
[23.297]compiled for 1.20.7, module version = 0.0.5
[23.297]ABI class: X.Org Video 

pkgs for aarch64 stopped building

[Ronald Klop]

Hi,

If I take a look at the pkg build server of aarch64: 
http://thunderx1.nyi.freebsd.org/ things are broken.

- head-arm64-default is already broken for a couple of weeks, because it can't 
build 'pkg'
- 113arm64-quarterly stays in 'parallel_build' while all cpu's are idle.

Is there maintenance being done? Where should I report this?

Regards,
Ronald.

___
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: Xorg 1.20 no mouse buttons

[Ronald Klop]

Hi,

I needed "sysctl kern.evdev.rcpt_mask=6" to switch from sysmouse to  
"hardware mouse". That fixed mouse integration with VirtualBox.


Still have weird behaviour. Two finger swipe down & up (which normally  
only scrolls) makes the browser go back. With xev I see that next to  
logical button 4 & 5 for scrolling this also triggers logical buttons 8 &  
9. Swipe down presses 8 & 9 and up releases the buttons. Why?


Regards,
Ronald.


On Thu, 27 Feb 2020 19:42:34 +0100, Daniel Morante via freebsd-ports  
 wrote:



Roland,

Your issue might be related to this bug:  
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244110


On 2/26/2020 5:29 PM, Ronald Klop wrote:

It works again.
Changed back from virtualboxvideo from drm-devel-kmod to the driver  
from virtualbox-ose-additions. But did some other changes at the same  
time also. Not sure yet what happened, but it was integration of the  
mouse with virtualbox which failed somehow.


Regards,
Ronald.



On Wed, 26 Feb 2020 20:40:14 +0100, Ronald Klop   
wrote:



Hello,

Since my upgrade to Xorg 1.20 things seem to work except that no mouse  
buttons work. Pointer movement works good still.
I'm running a fairly recent FreeBSD 13-CURRENT in VirtualBox (On  
Windows 10). The mouse is a touchpad on my Lenovo IdeaPad laptop.


Previously it worked using fine.

What can I do or debug to fix this?

Regards,
Ronald.


[23.241]
X.Org X Server 1.20.7
X Protocol Version 11, Revision 0
[23.241] Build Operating System: FreeBSD 13.0-CURRENT amd64
[23.241] Current Operating System: FreeBSD sjakie 13.0-CURRENT  
FreeBSD

13.0-CURRENT #4 r357762M: Sun Feb 16 12:16:08 CET 2020
builder@sjakie:/data/src/obj-freebsd-current/data/src/freebsd-current/amd64.amd64/sys/GENERIC-NODEBUG  
amd64

[23.241] Build Date: 22 February 2020  07:06:47AM
[23.241]
[23.241] Current version of pixman: 0.38.4
[23.241] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[23.241] Markers: (--) probed, (**) from config file, (==) default
setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[23.241] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Feb 24
19:18:14 2020
[23.244] (==) Using system config directory
"/usr/local/share/X11/xorg.conf.d"
[23.246] (==) No Layout section.  Using the first Screen section.
[23.246] (==) No screen section available. Using defaults.
[23.246] (**) |-->Screen "Default Screen Section" (0)
[23.246] (**) |   |-->Monitor ""
[23.247] (==) No monitor specified for screen "Default Screen  
Section".

Using a default monitor configuration.
[23.247] (==) Automatically adding devices
[23.247] (==) Automatically enabling devices
[23.247] (==) Not automatically adding GPU devices
[23.247] (==) Max clients allowed: 256, resource mask: 0x1f
[23.262] (==) FontPath set to:
/usr/local/share/fonts/misc/,
/usr/local/share/fonts/TTF/,
/usr/local/share/fonts/OTF/,
/usr/local/share/fonts/Type1/,
/usr/local/share/fonts/100dpi/,
/usr/local/share/fonts/75dpi/,
catalogue:/usr/local/etc/X11/fontpath.d
[23.263] (==) ModulePath set to "/usr/local/lib/xorg/modules"
[23.263] (II) The server relies on udev to provide the list of  
input

devices.
If no devices become available, reconfigure udev or disable
AutoAddDevices.
[23.263] (II) Loader magic: 0x435010
[23.263] (II) Module ABI versions:
[23.263] X.Org ANSI C Emulation: 0.4
[23.263] X.Org Video Driver: 24.1
[23.263] X.Org XInput driver : 24.1
[23.263] X.Org Server Extension : 10.0
[23.263] (--) PCI:*(0@0:2:0) 80ee:beef:: rev 0, Mem @
0xe000/134217728, BIOS @ 0x/65536
[23.263] (II) LoadModule: "glx"
[23.265] (II) Loading  
/usr/local/lib/xorg/modules/extensions/libglx.so

[23.292] (II) Module glx: vendor="X.Org Foundation"
[23.292] compiled for 1.20.7, module version = 1.0.0
[23.292] ABI class: X.Org Server Extension, version 10.0
[23.292] (==) Matched vboxvideo as autoconfigured driver 0
[23.292] (==) Matched modesetting as autoconfigured driver 1
[23.292] (==) Matched scfb as autoconfigured driver 2
[23.292] (==) Matched vesa as autoconfigured driver 3
[23.292] (==) Assigned the driver to the xf86ConfigLayout
[23.292] (II) LoadModule: "vboxvideo"
[23.292] (II) Loading
/usr/local/lib/xorg/modules/drivers/vboxvideo_drv.so
[23.294] (II) Module vboxvideo: vendor="Oracle Corporation"
[23.294] compiled for 1.20.7, module version = 1.0.1
[23.294] Module class: X.Org Video Driver
[23.294] ABI class: X.Org Video Driver, version 24.1
[23.294] (**) Load address of symbol "VBOXVIDEO"

Re: Pkg repository is broken...

[Ronald Klop]

On Sat, 07 Mar 2020 01:38:55 +0100, Greg 'groggy' Lehey   
wrote:



On Friday,  6 March 2020 at 12:29:44 +0100, Lars Engels wrote:

On Wed, Mar 04, 2020 at 03:16:14PM +1100, Greg 'groggy' Lehey wrote:


Any workarounds in the meantime?  This must affect a lot of people,
including those who use 12-:

  pkg: wrong architecture: FreeBSD:12.0:amd64 instead of  
FreeBSD:12:amd64
  pkg: repository FreeBSD contains packages with wrong ABI:  
FreeBSD:12.0:amd64


Still broken for me on 12.1.


Strange.  Mine cleared up automatically the following day.

It's also strange how few replies I have received.  Two private
messages (why?), yours, and that was it.  You'd think that people
would be screaming.

Greg



I'm not screaming because I'm settling with the situation and starting to  
make workarounds.
And wondering where the official communication of the community is.  
Nothing about this situation on www.freebsd.org. All information about the  
situation seems scattered through the mailinglists.


Things are working for me on 13-CURRENT again, but still broken on  
12.1-RELEASE. See attachment.


Ronald.Sat Mar  7 09:06:04 UTC 2020
Updating FreeBSD repository catalogue...
[freebsd12.klop.ws] Fetching meta.conf: . done
[freebsd12.klop.ws] Fetching packagesite.txz: .. done
Processing entries: ..
pkg: wrong architecture: FreeBSD:12.0:amd64 instead of FreeBSD:12:amd64
pkg: repository FreeBSD contains packages with wrong ABI: FreeBSD:12.0:amd64
Processing entries... done
Unable to update repository FreeBSD
Error updating repositories!
___
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: Xorg 1.20 no mouse buttons

[Ronald Klop]

On Thu, 05 Mar 2020 23:24:46 +0100, Michael Gmelin  wrote:





On 5. Mar 2020, at 14:46, Ronald Klop  wrote:

Hi,

I needed "sysctl kern.evdev.rcpt_mask=6" to switch from sysmouse to  
"hardware mouse". That fixed mouse integration with VirtualBox.


Still have weird behaviour. Two finger swipe down & up (which normally  
only scrolls) makes the browser go back. With xev I see that next to  
logical button 4 & 5 for scrolling this also triggers logical buttons 8  
& 9. Swipe down presses 8 & 9 and up releases the buttons. Why?


Hi,

Please check/post the outputs of:
libinput list-devices
xinput list
xinput list-props 


See atttachments. "unnamed" is the vboxmouse driver which comes with the  
virtualbox-ose-additions pkg.


Ronald.






-m



Regards,
Ronald.


On Thu, 27 Feb 2020 19:42:34 +0100, Daniel Morante via freebsd-ports  
 wrote:

Roland,
Your issue might be related to this bug:  
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244110

On 2/26/2020 5:29 PM, Ronald Klop wrote:
It works again.
Changed back from virtualboxvideo from drm-devel-kmod to the driver  
from virtualbox-ose-additions. But did some other changes at the same  
time also. Not sure yet what happened, but it was integration of the  
mouse with virtualbox which failed somehow.

Regards,
Ronald.
On Wed, 26 Feb 2020 20:40:14 +0100, Ronald Klop  
 wrote:

Hello,
Since my upgrade to Xorg 1.20 things seem to work except that no  
mouse buttons work. Pointer movement works good still.
I'm running a fairly recent FreeBSD 13-CURRENT in VirtualBox (On  
Windows 10). The mouse is a touchpad on my Lenovo IdeaPad laptop.

Previously it worked using fine.
What can I do or debug to fix this?
Regards,
Ronald.
[23.241]
X.Org X Server 1.20.7
X Protocol Version 11, Revision 0
[23.241] Build Operating System: FreeBSD 13.0-CURRENT amd64
[23.241] Current Operating System: FreeBSD sjakie 13.0-CURRENT  
FreeBSD

13.0-CURRENT #4 r357762M: Sun Feb 16 12:16:08 CET 2020
builder@sjakie:/data/src/obj-freebsd-current/data/src/freebsd-current/amd64.amd64/sys/GENERIC-NODEBUG  
amd64

[23.241] Build Date: 22 February 2020  07:06:47AM
[23.241]
[23.241] Current version of pixman: 0.38.4
[23.241] Before reporting problems, check http://wiki.x.org
  to make sure that you have the latest version.
[23.241] Markers: (--) probed, (**) from config file, (==)  
default

setting,
  (++) from command line, (!!) notice, (II) informational,
  (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[23.241] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Feb 24
19:18:14 2020
[23.244] (==) Using system config directory
"/usr/local/share/X11/xorg.conf.d"
[23.246] (==) No Layout section.  Using the first Screen section.
[23.246] (==) No screen section available. Using defaults.
[23.246] (**) |-->Screen "Default Screen Section" (0)
[23.246] (**) |   |-->Monitor ""
[23.247] (==) No monitor specified for screen "Default Screen  
Section".

  Using a default monitor configuration.
[23.247] (==) Automatically adding devices
[23.247] (==) Automatically enabling devices
[23.247] (==) Not automatically adding GPU devices
[23.247] (==) Max clients allowed: 256, resource mask: 0x1f
[23.262] (==) FontPath set to:
  /usr/local/share/fonts/misc/,
  /usr/local/share/fonts/TTF/,
  /usr/local/share/fonts/OTF/,
  /usr/local/share/fonts/Type1/,
  /usr/local/share/fonts/100dpi/,
  /usr/local/share/fonts/75dpi/,
  catalogue:/usr/local/etc/X11/fontpath.d
[23.263] (==) ModulePath set to "/usr/local/lib/xorg/modules"
[23.263] (II) The server relies on udev to provide the list of  
input

devices.
  If no devices become available, reconfigure udev or disable
AutoAddDevices.
[23.263] (II) Loader magic: 0x435010
[23.263] (II) Module ABI versions:
[23.263] X.Org ANSI C Emulation: 0.4
[23.263] X.Org Video Driver: 24.1
[23.263] X.Org XInput driver : 24.1
[23.263] X.Org Server Extension : 10.0
[23.263] (--) PCI:*(0@0:2:0) 80ee:beef:: rev 0, Mem @
0xe000/134217728, BIOS @ 0x/65536
[23.263] (II) LoadModule: "glx"
[23.265] (II) Loading  
/usr/local/lib/xorg/modules/extensions/libglx.so

[23.292] (II) Module glx: vendor="X.Org Foundation"
[23.292] compiled for 1.20.7, module version = 1.0.0
[23.292] ABI class: X.Org Server Extension, version 10.0
[23.292] (==) Matched vboxvideo as autoconfigured driver 0
[23.292] (==) Matched modesetting as autoconfigured driver 1
[23.292] (==) Matched scfb as autoconfigured driver 2
[23.292] (==) Matched vesa as autoconfigured driver 3
[23.292] (==) Assigned the driver to the xf86ConfigLayout
[23.292] (II) LoadModule: "vboxvideo"
[23.292] (II) Loading
/usr/local/lib/xorg/modules/drivers/vboxvideo_drv.so
[

Re: python 2.7 marked as deprecated and EOL while 2.7.18 RC is available

[Ronald Klop]

On Fri, 17 Apr 2020 14:11:11 +0200, Dewayne Geraghty  
 wrote:


Its very confusing building ports at the moment.  At  
https://www.python.org/

there is a release candidate for 2.7.18, while our python 2.7 has been
marked as deprecated with an expiration date.  Can the Expiration Date of
2020-12-31 be retracted?

It appears that devel/scons, at least, requires python 2.7 to run; though
it builds with 3.7.
Regards, Dewayne.


Scons is a special one.
Mongodb36 & mongodb40 use scons+python27 to build.
Mongodb42 uses scons+python37 to build. But this port can't be made  
because scons is currently build for python2 only.


I created PR https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241463 a  
while ago to try to flavor scons. I hope the maintainer of the port will  
take a look sometime in the future.


So this kind of a catch-22. Mongodb can't be upgraded to python3  
supporting versions because scons can't be upgraded.


I have no idea if mongodb36 and -40 will be converted to python3 upstream  
any day.


Regards,

Ronald.
___
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: python 2.7 marked as deprecated and EOL while 2.7.18 RC is available

[Ronald Klop]

On Sun, 19 Apr 2020 01:40:29 +0200, Kevin Oberman   
wrote:


I see both mate-menu and mate-applets require python27, but both build  
fine

and seem to be running well when built with py37. It is possible that one
or more applets that I don't use do require py27, but I see no reason for
that requirement on mate-menus. The menus seem to be fine.

Inkscape is another. It  builds and runs on py37, but I have no  
confidence
that it runs properly. I have not used inkscape in years and I don't  
really

know how to test it. I am dubious.

math/gnumeric is one I use daily and it explicitly states in the build  
that
2.x is required and it is not yet compatible with python3+. It appears  
that

the default is to simply build gnumeric without Python bindings in which
case python2 is not required, but the port makes use of it, so it  
probably

needs at least some massaging.

The big one is scons. It is required by virtualbox-ose, and that is  
rather

important.



See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241463 for a attempt  
to flavor scons for python 2 and python 3.
Otherwise I don't see how new ports (wanting python3 to buid) can use  
scons while existing ports keep building using python 2 for the coming  
months.


NB: mongodb36 and 40 want scons with python 2. Mongodb42 (not in  ports  
yet) wants scons for python 3.


Regards,
Ronald.



--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683





___
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: python 2.7 marked as deprecated and EOL while 2.7.18 RC is available

[Ronald Klop]

On Sun, 19 Apr 2020 01:57:36 +0200, Dima Pasechnik  
 wrote:



scons ought to be updated to version 3 (the latest is 3.1.2), and
supports both python 2.7+ and 3.5+



Scons in ports is 3.1.1. This can compile and run with python 2 and 3. But  
our USES=scons framework does not know how to instruct scons to run with  
which python version.


See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241463 for a attempt  
to flavor scons for python 2 and python 3.
Maintainer of the port is rather silent. Does not accept nor reject the  
proposed solution.


Regards,
Ronald.




lilypond is another story - noone seems to have bitten the bullet and
ported it to Python 3.
But I don't see a problem in keeping Python 2.7 available for some
time in FreeBSD - it just should stop being default one.



On Sun, Apr 19, 2020 at 7:41 AM Kevin Oberman   
wrote:


I see both mate-menu and mate-applets require python27, but both build  
fine
and seem to be running well when built with py37. It is possible that  
one
or more applets that I don't use do require py27, but I see no reason  
for

that requirement on mate-menus. The menus seem to be fine.

Inkscape is another. It  builds and runs on py37, but I have no  
confidence
that it runs properly. I have not used inkscape in years and I don't  
really

know how to test it. I am dubious.

math/gnumeric is one I use daily and it explicitly states in the build  
that
2.x is required and it is not yet compatible with python3+. It appears  
that

the default is to simply build gnumeric without Python bindings in which
case python2 is not required, but the port makes use of it, so it  
probably

needs at least some massaging.

The big one is scons. It is required by virtualbox-ose, and that is  
rather

important.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683


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

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

looking for committer of databases/mongodb42

[Ronald Klop]

Hi,

The scons+python3 blocker is fixed and this port is ready AFAIK.

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

It is portlinted and compiles and runs on aarch64 also.

Does somebody have some time to take a look and commit this new port?

Regards,
Ronald.
___
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"

Fwd: unifi5, mongodb and python2

[Ronald Klop]

Hi,

Looking for some feedback on this. Or should I just go ahead and create PRs?

Ronald.

Van: Ronald Klop 
Datum: vrijdag, 12 juni 2020 11:08
Aan: f...@freebsd.org
Onderwerp: unifi5, mongodb and python2


Hi,

Currently unifi5 uses mongodb36. Mongodb36 and mongodb40 are marked as 
deprecated because they use python2 in the build stage. Both will expire/be 
removed on 2020-12-31 unless somebody (or upstream) fixes this.

Mongodb42 uses python3 and will stay, but we don't know if it is compatible yet.

Upgrade of mongodb is only supported in these steps according to the documentation: 
3.6 -> 4.0 -> 4.2.

So to help the users of Unifi5 on the quarterly branches the following scheme 
would be possible.

* Switch unifi5 to mongodb40 before the next branch 2020Q3 (around 1th of July).
* Then before 2020Q4 (1th of October) switch to mongodb42.

This gives the people running on quarterly branches an easy upgrade path.
Of course it should be tested if unifi5 runs on mongodb40 and -42 first. I can 
do that in my home setup the coming week. Maybe more testers are welcome, 
because my setup is pretty simple.

Do you have thoughts about this?

Regards,
Ronald.
 

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

committer for some mongodb ports updates?

[Ronald Klop]

Hi,

Would somebody like to commit these PR's before the quarterly branch?

security/vuxml mongodb issue 


databases/mongodb36: Update to 3.6.18 -> fixes the vuln in the previous issue

databases/mongodb40: Update to 4.0.19 -> fixes pkg distribution because of 
wrong license definition in Makefile

Regards,
Ronald.

___
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: committer for some mongodb ports updates?

[Ronald Klop]

Van: Kurt Jaeger 
Datum: maandag, 29 juni 2020 20:22
Aan: Ronald Klop , freebsd-ports@freebsd.org
Onderwerp: Re: committer for some mongodb ports updates?


Hi!

> > databases/mongodb36: Update to 3.6.18 -> fixes the vuln in the previous 
issue
> >
> > databases/mongodb40: Update to 4.0.19 -> fixes pkg distribution because of 
wrong license definition in Makefile
>
> Testbuilds@work

Done. Also: mongodb40-tools 8-}

--
p...@opsec.eu+49 171 3101372Now what ?


Thank you!
___
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: Fwd: unifi5, mongodb and python2

[Ronald Klop]

Yes, I'm testing stuff.

Unifi5 runs with mongodb40 for some time now in my house setup.
But I had issues upgrading to mongodb42. Which I'm looking into. It seems to 
work in my current setup.
I got a little bit swamped by all the different versions of unifi5, mongodb and 
a jail which was connecting to the server of the host which did not help. :-)

In the meantime there were updates to mongodb ports which I test-compiled on my 
RPI3 which takes a loong time to build.

Interesting setups:
unifi5 mongodb36 clean install  (Works)
unifi5 mongodb40 clean install
unifi5 mongodb42 clean install

unifi5 mongodb40 upgrade from mongodb36  (Works)
unifi5 mongodb42 upgrade from mongodb40
unifi5 mongodb42 upgrade from mongodb36

What I find interesting is that Unifi does "setting mongodb features compatibility 
version to 3.6". This should not be possible on 4.2 because Mongodb only supports 1 
version back. I saw errors/crashes about this, but can't reproduce it. Which might have 
to do with my jail-problems mentioned above.

If somebody beats me to test the different combinations of the software and 
creates PRs, please do. I hope to find some time this or next week.

Regards,

Ronald.


Van: Doug Sampson 
Datum: maandag, 6 juli 2020 20:17
Aan: Dave Cottlehuber , Kurt Jaeger , Ronald 
Klop 
CC: freebsd-ports 
Onderwerp: Re: Fwd: unifi5, mongodb and python2


Is there any movement on this issue? I don't see a PR? I have an installation 
facing this issue.

~Doug

From: owner-freebsd-po...@freebsd.org  on behalf of 
Dave Cottlehuber 
Sent: Wednesday, June 17, 2020 9:34 AM
To: Kurt Jaeger; Ronald Klop
Cc: freebsd-ports
Subject: Re: Fwd: unifi5, mongodb and python2

On Wed, 17 Jun 2020, at 09:04, Kurt Jaeger wrote:
> Hi!
>
> > Looking for some feedback on this. Or should I just go ahead and create PRs?
>

Sounds good to me.

I have recently done a few mongo Mongo mongo upgrades would I can prep some 
notes on that, perhaps in the wiki? We could reference it in the pkg-message 
perhaps?

Dave
___
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: Gracefully killing and restarting a port build....

[Ronald Klop]

Van: bob prohaska 
Datum: woensdag, 8 juli 2020 05:47
Aan: freebsd-ports@freebsd.org
Onderwerp: Gracefully killing and restarting a port build


While compiling www/chromium on a Pi3B it has become clear that the
default -j4 isn't going to work (yes, I know, ya told me).

On the plus side, it hasn't crashed, despite several days of
continuous swapping  with 1-2GB of swap in use. Kudos to the
VM folks.

Now I'd like to (gracefully) stop the make and restart it with more
sane -j values. -2 seems like a reasonable start.

A simple
kill  aimed at the original make doesn't seem to do anything. Even
kill -9  appears to have no effect on the c++ threads, which are
still running minutes afterwards.

Now it seems rather like I'm stuck: The original  is gone, but
c++ is still grinding away as if nothing has changed..

Is there a better way to accomplish a clean(ish) stop and restart of
a multi-threaded make process?

Thanks for reading, apologies if it's a dumb question,

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"






Kill the leaf nodes of the process tree. So kill the c++ processes. Or type 
ctrl-c if you have control of the terminal.
If you are running the compile in a jail (like poudriere) you might use "killall -j 
 c++" or something similar.
Pkill can be usable also.
BTW: How graceful a restart works is outside of the scope of the ports 
framework and depends a lot on the structure of the chromium build process 
itself.

Regards,
Ronald.

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

Forbidden access on http://pkg.freebsd.org/FreeBSD:13:amd64/

[Ronald Klop]

Hi,

I had a nice script which periodically checks if there are updates for the pkgs.
Since last night it gets a "Forbidden" status asking for the directory listing.

Is this on purpose?
And what is the best way to check if there are updates as a non-root user?

Regards,
Ronald.


Van: Cron Daemon 
Datum: dinsdag, 14 juli 2020 09:55
Aan: ron...@klop.ws
Onderwerp: Cron  bin/verify_site.sh "amd64_pkgs" 
"http://pkg.freebsd.org/FreeBSD:13:amd64/";


fetch: http://pkg.freebsd.org/FreeBSD:13:amd64/: Forbidden




___
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: Fwd: unifi5, mongodb and python2

[Ronald Klop]

On Mon, 06 Jul 2020 21:15:58 +0200, Ronald Klop   
wrote:



Yes, I'm testing stuff.

Unifi5 runs with mongodb40 for some time now in my house setup.
But I had issues upgrading to mongodb42. Which I'm looking into. It  
seems to work in my current setup.
I got a little bit swamped by all the different versions of unifi5,  
mongodb and a jail which was connecting to the server of the host which  
did not help. :-)


In the meantime there were updates to mongodb ports which I  
test-compiled on my RPI3 which takes a loong time to build.


Interesting setups:
unifi5 mongodb36 clean install  (Works)
unifi5 mongodb40 clean install
unifi5 mongodb42 clean install

unifi5 mongodb40 upgrade from mongodb36  (Works)
unifi5 mongodb42 upgrade from mongodb40
unifi5 mongodb42 upgrade from mongodb36

What I find interesting is that Unifi does "setting mongodb features  
compatibility version to 3.6". This should not be possible on 4.2  
because Mongodb only supports 1 version back. I saw errors/crashes about  
this, but can't reproduce it. Which might have to do with my  
jail-problems mentioned above.


If somebody beats me to test the different combinations of the software  
and creates PRs, please do. I hope to find some time this or next week.


Regards,

Ronald.



Hi,

I did some tests on unifi5-5.13.29.

First install:
 36. Works (gives a WebGUI)
 40. Works (gives a WebGUI)
 42. Works (gives a WebGUI, but already found an error, see below)

Upgrade
 36 > 40 Works
 40 > 42 Works partly and needs manual action [1]

[1] MongoDB has a "featureCompatiblityVersion" on the database. Unifi  
actively sets this to "3.6" on startup. MongoDB-4.2 will not start if  
featureCompatiblityVersion=3.6. So you need to set  
featureCompatiblityVersion=4.0 before starting mongodb42.

Steps:
 1. start unifi with mongodb40
 2. run "mongo --port 27117" > db.adminCommand( {  
setFeatureCompatibilityVersion: "4.0" } )

 3. stop unifi
 4. remove mongodb40; install mongodb42
 5. start unifi


!!! BUT: !!!
The WebGUI runs and clicking around seems to work. As a first test I  
clicked "Compact Database" in Settings > Maintenance. This gives an error  
because $eval is not supported anymore.

https://docs.mongodb.com/manual/release-notes/4.2-compatibility/#remove-support-for-the-eval-command

I don't know if there are more of these things yet, but it will mean we  
already know some things do not work with mongodb42.


I will install mongodb42 in my home setup and run it for a couple of days.  
Mongodb40 runs without problems here for some weeks now.


Ronald.




 Van: Doug Sampson 
Datum: maandag, 6 juli 2020 20:17
Aan: Dave Cottlehuber , Kurt Jaeger ,  
Ronald Klop 

CC: freebsd-ports 
Onderwerp: Re: Fwd: unifi5, mongodb and python2
 Is there any movement on this issue? I don't see a PR? I have an  
installation facing this issue.

 ~Doug

From: owner-freebsd-po...@freebsd.org   
on behalf of Dave Cottlehuber 

Sent: Wednesday, June 17, 2020 9:34 AM
To: Kurt Jaeger; Ronald Klop
Cc: freebsd-ports
Subject: Re: Fwd: unifi5, mongodb and python2
 On Wed, 17 Jun 2020, at 09:04, Kurt Jaeger wrote:
> Hi!
>
> > Looking for some feedback on this. Or should I just go ahead and  
create PRs?

>
 Sounds good to me.
 I have recently done a few mongo Mongo mongo upgrades would I can prep  
some notes on that, perhaps in the wiki? We could reference it in the  
pkg-message perhaps?

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

___
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: Chromium (& derivatives) and Python 2.7

[Ronald Klop]

The same problem is going to happen with mongodb36 I presume. It uses python2 
to build, but does not need it to run.
Would it be possible to remove python2 as a RUN_DEPENDS at the end of 2020, but 
keep it as a BUILD_DEPENDS in the ports framework?

This might save some usefull ports.

How are other projects (like Debian, etc.) solving this?

Regards,
Ronald.


Van: Adriaan de Groot 
Datum: maandag, 27 juli 2020 21:36
Aan: freebsd-ports@freebsd.org
Onderwerp: Chromium (& derivatives) and Python 2.7


The Chromium build system -- and as a consequence, also QtWebEngine -- still
uses Python 2.7. This is going to be a real problem about six months down the
line, and I have no idea how upstream is going to deal with it. I've heard
there are patches buried deep within the chocolate factory, but not from
reliable sources.

QtWebEngine is an even specialer case, since it's an LTS and also the last LTS
in the Qt5 series, and I have real doubts about upstream -- The Qt Company --
being able or willing to deal with Python 2.7 deprecation there.

Has anyone in FreeBSD tried to port the stuff over? I got about an hour or two
into the porting process (making configure accept Python 3 is easy, but
there's all these wretched code-generating scripts) and hit a brick wall of
templating engines doing sensible Python 2.7 things.

[ade]



 

___
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: Portmaster and less

[Ronald Klop]

PAGER=more portmaster...
I do this with mergemaster. Somehow someone decided that the behavior of less 
is the best and made it the default a while ago.


Probably this https://reviews.freebsd.org/D13465
Something about "the nineties", but no further rationale.


Regards,
Ronald.

Van: "@lbutlr" 
Datum: 31 juli 2020 22:25
Aan: FreeBSD 
Onderwerp: Portmaster and less



When postmaster displays the package messages after installing, it calls less, 
which forces you to hit 'q' to exit, and when you quit less, it clear the 
buffer on the screen and returns you to the display of the compile process.

Is there anyway to change this behavior so that less is called with -E / 
--QUIT-AT_EOF? Or can I just tell postmaster to cat this files so they appear 
in my terminals scroll back no matter what?

(I think the discarding that text that is paged by less is a terminal emulator 
or tmux setting, but haven’t looked into that.)




--
'Never say die, master. That's our motto, eh?' I CAN'T SAY IT'S EVER
REALLY BEEN MINE. --Hogfather

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

devel/sigar breakage on 13-current

[Ronald Klop]

Hi,

I noticed cassandra3/4 is not build on 13-current. It does build on 11 and  
12.
The cause is breakage in the devel/sigar port on 13-current. It is a  
fairly recent breakage.


works:  
http://beefy18.nyi.freebsd.org/data/head-amd64-default/p541901_s363088/logs/sigar-1.7.3_2.log


broken:  
http://beefy18.nyi.freebsd.org/data/head-amd64-default/p543559_s363627/logs/errors/sigar-1.7.3_2.log


The error seems to be in a missing sys/filedesc.h include. This is a big  
guess of my side.
darwin_sigar.c:1968:27: error: no member named 'fd_lastfile' in 'struct  
filedesc'

procfd->total = filed.fd_lastfile;

I noticed the working build is in Jail OSVERSION: 1300101 and the broken  
one is in Jail OSVERSION: 1300101.
I'm wondering if it is possible to get a more fine grained version nr of  
the working/broken version. And while I'm typing this I see that the URLs  
contain s363088 and s363627. Is this the OS revision?



If somebody knows the fix please go ahead. I did not make a PR yet.  
Building and setting up proper jails/poudrieres on my home machine will  
take quite some time.


Regards,
Ronald.
___
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: devel/sigar breakage on 13-current (fd_lastfile)

[Ronald Klop]

On Sun, 02 Aug 2020 15:50:41 +0200, Ronald Klop   
wrote:



Hi,

I noticed cassandra3/4 is not build on 13-current. It does build on 11  
and 12.
The cause is breakage in the devel/sigar port on 13-current. It is a  
fairly recent breakage.


works:  
http://beefy18.nyi.freebsd.org/data/head-amd64-default/p541901_s363088/logs/sigar-1.7.3_2.log


broken:  
http://beefy18.nyi.freebsd.org/data/head-amd64-default/p543559_s363627/logs/errors/sigar-1.7.3_2.log


The error seems to be in a missing sys/filedesc.h include. This is a big  
guess of my side.
darwin_sigar.c:1968:27: error: no member named 'fd_lastfile' in 'struct  
filedesc'

 procfd->total = filed.fd_lastfile;

I noticed the working build is in Jail OSVERSION: 1300101 and the broken  
one is in Jail OSVERSION: 1300101.
I'm wondering if it is possible to get a more fine grained version nr of  
the working/broken version. And while I'm typing this I see that the  
URLs contain s363088 and s363627. Is this the OS revision?



If somebody knows the fix please go ahead. I did not make a PR yet.  
Building and setting up proper jails/poudrieres on my home machine will  
take quite some time.


Regards,
Ronald.



I found this commit to be to culprit.
https://svnweb.freebsd.org/base?view=revision&revision=363214

The code did "filed.fd_lastfile". This was retrieved by reading kvm.
Current code should do fdlastfile(&filed), but the linker can't find the  
method. I think because the method is defined in the kernel.

What is the best way to retrieve this value in userland?

Regards,
Ronald.
___
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: Chromium (& derivatives) and Python 2.7

[Ronald Klop]

On Tue, 04 Aug 2020 16:20:01 +0200, Lars Liedtke  wrote:


At least in Ubuntu the mongodb 3.6 package does not depend on python2.


Package: mongodb-server-core
Version: 1:3.6.9+really3.6.8+90~g8e540c0b6d-0ubuntu5
Priority: optional
Section: universe/database
Source: mongodb
Origin: Ubuntu
Maintainer: Ubuntu Developers 
Original-Maintainer: Debian MongoDB Maintainers



Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 77,8 MB
Depends: libboost-filesystem1.71.0, libboost-program-options1.71.0,

libc6 (>= 2.29), libgcc-s1 (>= 3.4), libgoogle-perftools4, libpcrecpp0v5
(>= 7.7), libsnappy1v5 (>= 1.1.8), libssl1.1 (>= 1.1.0), libstdc++6 (>=
9), libstemmer0d (>= 0+svn527), libyaml-cpp0.6 (>= 0.6.2), zlib1g (>=
1:1.2.0)

Breaks: mongodb-server (<< 1:3.4.14-3ubuntu1)
Replaces: mongodb-server (<< 1:3.4.14-3ubuntu1)
Homepage: https://www.mongodb.org
Download-Size: 21,6 MB
APT-Sources: http://de.archive.ubuntu.com/ubuntu focal/universe amd64

Packages
[...]

I don't know about build dependencies



It's a build dependency.

Regards,
Ronald.



Am 28.07.20 um 11:36 schrieb Ronald Klop:

The same problem is going to happen with mongodb36 I presume. It uses
python2 to build, but does not need it to run.
Would it be possible to remove python2 as a RUN_DEPENDS at the end of
2020, but keep it as a BUILD_DEPENDS in the ports framework?

This might save some usefull ports.

How are other projects (like Debian, etc.) solving this?

Regards,
Ronald.


Van: Adriaan de Groot 
Datum: maandag, 27 juli 2020 21:36
Aan: freebsd-ports@freebsd.org
Onderwerp: Chromium (& derivatives) and Python 2.7


The Chromium build system -- and as a consequence, also QtWebEngine
-- still
uses Python 2.7. This is going to be a real problem about six months
down the
line, and I have no idea how upstream is going to deal with it. I've
heard
there are patches buried deep within the chocolate factory, but not  
from

reliable sources.

QtWebEngine is an even specialer case, since it's an LTS and also the
last LTS
in the Qt5 series, and I have real doubts about upstream -- The Qt
Company --
being able or willing to deal with Python 2.7 deprecation there.

Has anyone in FreeBSD tried to port the stuff over? I got about an
hour or two
into the porting process (making configure accept Python 3 is easy, but
there's all these wretched code-generating scripts) and hit a brick
wall of
templating engines doing sensible Python 2.7 things.

[ade]





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

aarch64 pkg build ready but hangs

[Ronald Klop]

Hi,


http://thunderx1.nyi.freebsd.org/build.html?mastername=head-arm64-default&build=p542683_s363381



This build is finished, but stays in state parallel_build.
Some workers are in state cleanup instead of idle. Maybe that is part of the 
cause.


If I had the magic I would unblock it myself. 😀🔮


Regards,
Ronald.
___
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"

11.3/aarch64 pkg build seems broken/hanging

[Ronald Klop]

Hi,

See: 
http://thunderx1.nyi.freebsd.org/build.html?mastername=113arm64-quarterly&build=544320

All current builds are from 10 aug or earlier and seem stuck.

Does anybody know who to ping about this? Or what is going on?

Regards,
Ronald.

___
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: 11.3/aarch64 pkg build seems broken/hanging

[Ronald Klop]

On Tue, 11 Aug 2020 17:17:47 +0200, Ronald Klop   
wrote:



Hi,

See:  
http://thunderx1.nyi.freebsd.org/build.html?mastername=113arm64-quarterly&build=544320


All current builds are from 10 aug or earlier and seem stuck.


I saw that the build was restarted a few days ago. But now the URL gives a  
timeout.



Does anybody know who to ping about this? Or what is going on?


So, this question still stands.
NB: I would love invest some time into this and help running the build  
machines.




Regards,
Ronald.
 ___
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: Availability of samba 4.12.x

[Ronald Klop]

Van: Kurt Jaeger 
Datum: 19 september 2020 16:12
Aan: FreeBSD Ports 
Onderwerp: Re: Availability of samba 4.12.x



Hi!

> I was just wondering why the current stable version of samba -- samba
> 4.12.7 is not available in the post tree?

Because the maintainer did not yet got the time to create a port.

Maybe you want to try to create 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"





Interesting. Truenas 12 (Formerly Freenas) runs a samba-4.12.6_6 pkg. I don't 
see it in ports. Regards,Ronald
___
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"

committer for mongodb-tools

[Ronald Klop]

Hi,

Anybody interested in committing the latest mongodb-tools before the new 
Q-branch?

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

Regards,
Ronald.

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

committer for python3 fix for mongodb36

[Ronald Klop]

Hi,

This issue contains a patch for python3 support for building  
databases/mongodb36.

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

It is approved by the maintainer. Is anybody willing to commit it?

It will save net-mgmt/unifi[56] from removal at the end of the year also.

Regards,
Ronald.
___
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: DMA -- difference between base and port?

[Ronald Klop]

On Mon, 21 Dec 2020 12:12:02 +0100, Dan Mahoney (Gushi)  
 wrote:



Hey there,

At the day job we've been using mail/dma port for a number of years now,  
and the rollout and config of files in /usr/local/etc/dma is part of our  
deploy process.


It only recently occurred to us that there was a "dma" in base since  
probably 11.0 (whomever wrote the release notes missed that -- and the  
manpage doesn't mention when it was added to FreeBSD).


We notice that the "newaliases" function in /etc/mail/mailer.conf is  
missing from the port version -- which means if you're using ports dma,  
you probably want to set newaliases to something like /usr/bin/true (dma  
doesn't use an aliases db, so there's no need to rebuild one, as  
newaliases would).  Again. something we noticed in our deployment  
process with puppet.


I can't find a feature-by-feature comparison for what one would install  
the port for (other than inertia, like we have).


There's no "version" command that I can find in DMA. (tried -h, -?, -v  
--version, -V).


Does "our" DMA track the Dragonfly version (like the base sendmail or  
openssl track world) or is it completely forked and unlikely to  
incorporate changes?  This would be useful in feature comparison.


Is it worth mentioning this in the pkg-message for mail/dma?

-Dan



On 13-CURRENT I have:
# more /usr/src/contrib/dma/VERSION
v0.11

But the version nr doesn't tell the whole story. There are some code syncs  
after 0.11.

https://github.com/freebsd/freebsd/commits/master/contrib/dma

There is a PR to upgrade base to 0.13 already.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244630

Would love to see a sync with even newer code. I made a fix upstream  
myself.


Regards,
Ronald.
___
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"

committer for Cassandra4 aarch64 fix?

[Ronald Klop]

Hi,


Looking for a committer for 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=252068 ?
Small fix for compilation on aarch64. Would be nice to have it in the 2021Q1 
quarterly branch.


Regards,
Ronald
___
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: DMA -- difference between base and port?

[Ronald Klop]

Some questions below.

On Tue, 22 Dec 2020 01:56:04 +0100, Dan Mahoney (Gushi)  
 wrote:



On Mon, 21 Dec 2020, Ronald Klop wrote:

On Mon, 21 Dec 2020 12:12:02 +0100, Dan Mahoney (Gushi)  
 wrote:



Hey there,
 At the day job we've been using mail/dma port for a number of years  
now, and the rollout and config of files in /usr/local/etc/dma is part  
of our deploy process.
 It only recently occurred to us that there was a "dma" in base since  
probably 11.0 (whomever wrote the release notes missed that -- and the  
manpage doesn't mention when it was added to FreeBSD).
 We notice that the "newaliases" function in /etc/mail/mailer.conf is  
missing from the port version -- which means if you're using ports  
dma, you probably want to set newaliases to something like  
/usr/bin/true (dma doesn't use an aliases db, so there's no need to  
rebuild one, as newaliases would).  Again. something we noticed in our  
deployment process with puppet.



Why are you calling newaliases if dma does not use an aliases db?


 I can't find a feature-by-feature comparison for what one would  
install the port for (other than inertia, like we have).
 There's no "version" command that I can find in DMA. (tried -h, -?,  
-v --version, -V).
 Does "our" DMA track the Dragonfly version (like the base sendmail or  
openssl track world) or is it completely forked and unlikely to  
incorporate changes?  This would be useful in feature comparison.

 Is it worth mentioning this in the pkg-message for mail/dma?
 -Dan



On 13-CURRENT I have:
# more /usr/src/contrib/dma/VERSION
v0.11

But the version nr doesn't tell the whole story. There are some code  
syncs after 0.11.

https://github.com/freebsd/freebsd/commits/master/contrib/dma

There is a PR to upgrade base to 0.13 already.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244630

Would love to see a sync with even newer code. I made a fix upstream  
myself.


Yes, my issue with "newaliases" failing actually comes down to two open  
issues:


1) No released version will work with "newaliases" unless "newaliases"  
is called as a bareword (so calling /usr/bin/newaliases, as puppet does,  
causes you to get a "no recipients" error)  This is fixed in dma head,  
but not in either the current port version, or the freebsd base version.





I'm a bit confused. You say "this is fixed in dma head". I see no matching  
commit about this fix after 0.13 release in  
https://github.com/corecode/dma/commits/master .



We've tweaked it by telling our deploy tools (puppet) to call newaliases  
and handing it a path, but we prefer to hand exec's full paths to  
binaries.


2) DMA's still broken if you've got an alternate alias file defined, see  
https://github.com/corecode/dma/issues/90


(Given, this is the ports mailing list, but those should also be fixed  
in the ports version, with the latter perhaps being fixed one dma hits  
0.14 or whatever version number has that fix, rather than manually  
patching 0.13.)


-Dan




If I read it correctly I have the idea that your issue is in FreeBSD base,  
ports and the dma github code?

So it seems it needs to be solved upstream first.

I'm asking this, because I would like to have the 0.13 update in base and  
make sure that your issue is not a showstopper for this but a separate  
issue independend of the version of contrib/dma.


Regards,
Ronald.
___
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"

pkg building is hanging on arm64/12

[Ronald Klop]

Hi,

The last package is holding up the completion of the build.

(ipv6 only)
http://ampere1.nyi.freebsd.org/build.html?mastername=121arm64-quarterly&build=560365

Can somebody kick it? While keeping the already build packages preferably. ;-)

Regards,
Ronald.

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

help on port linux-vivaldi needed

[Ronald Klop]

Hi,

I created a port of the Vivaldi browser & e-mail client. (www.vivaldi.com)
It is still a work in progress.
The port is based on the linux-opera port.

It installs in /compat/linux/opt/vivaldi which needs to be improved yet.
It seems I have all the dependencies in place now.

But when I start it it complains that libffmpeg.so is not available while
ldd gives that it is perfectly available.
/opt/vivaldi/vivaldi-bin: error while loading shared libraries:
libffmpeg.so: cannot open shared object file: No such file or directory

$ ldd /opt/vivaldi/vivaldi-bin
linux_vdso.so.1 =>  (0x7000)
libffmpeg.so => /opt/vivaldi/lib/libffmpeg.so (0x00080bc0)
libdl.so.2 => /lib64/libdl.so.2 (0x00080c20)

My port can be found here:
https://www.klop.ws/linux-vivaldi.tar

Is anybody willing to help create this port?

Ronald.


PS: resend from my subscribed email address. Might be double. Sorry.
___
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"

help on port linux-vivaldi needed

[Ronald Klop]

Hi,

I created a port of the Vivaldi browser & e-mail client. (www.vivaldi.com)
It is still a work in progress.
The port is based on the linux-opera port.

It installs in /compat/linux/opt/vivaldi which needs to be improved yet.  
It seems I have all the dependencies in place now.


But when I start it it complains that libffmpeg.so is not available while  
ldd gives that it is perfectly available.
/opt/vivaldi/vivaldi-bin: error while loading shared libraries:  
libffmpeg.so: cannot open shared object file: No such file or directory


$ ldd /opt/vivaldi/vivaldi-bin
linux_vdso.so.1 =>  (0x7000)
libffmpeg.so => /opt/vivaldi/lib/libffmpeg.so (0x00080bc0)
libdl.so.2 => /lib64/libdl.so.2 (0x00080c20)

My port can be found here:
https://www.klop.ws/linux-vivaldi.tar

Is anybody willing to help create this port?

Ronald.
___
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: unifi6-6.0.45

[Ronald Klop]

Hi,


You can see here which pkg is already build by the pkg cluster.


https://www.freshports.org/net-mgmt/unifi6/


Pkg building was only recently enabled for unifi6, so things like quarterly do 
not have pkgs.


Regards,
Ronald.


Van: Juraj Lutter 
Datum: 5 maart 2021 15:46
Aan: j...@otterholm.se
CC: "" 
Onderwerp: Re: FreeBSD Port: unifi6-6.0.45




Hi,

net-mgmt/unifi6 (6.0.45) should be available for 12.2 (amd64) since 3.3.2021.

By "current” you mean 13.0 or 14-CURRENT?

hth,
otis


> On 5 Mar 2021, at 14:01,   wrote:
> 
> Hi.
>  
> Any reason why pkg for this port is not available for 12.2 and Current (only 11.2)?
>  
> Br

> Jon Otterholm

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

Illegal instruction on new port mongodb49 on arm64

[Ronald Klop]

Hi,

I created a new port for mongodb49: 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254631
It compiles fine: https://www.klop.ws/mongodb49-4.9.0.r0.log

When I run an application I get "Illegal Instruction" error.

==
[root@rpi4 /tmp]# lldb /usr/local/bin/mongo
(lldb) target create "/usr/local/bin/mongo"
Current executable set to '/usr/local/bin/mongo' (aarch64).
(lldb) run
Process 55420 launching
Process 55420 launched: '/usr/local/bin/mongo' (aarch64)
Process 55420 stopped
* thread #1, name = 'mongo', stop reason = signal SIGILL: illegal trap
   frame #0: 0x016a320c mongo`___lldb_unnamed_symbol32$$mongo + 1784
mongo`___lldb_unnamed_symbol32$$mongo:
->  0x16a320c <+1784>: ldaddal x9, x8, [x8]
   0x16a3210 <+1788>: ldrq0, [x11]
   0x16a3214 <+1792>: movw10, #0x20
   0x16a3218 <+1796>: strb   wzr, [sp, #0x68]
(lldb) bt
* thread #1, name = 'mongo', stop reason = signal SIGILL: illegal trap
 * frame #0: 0x016a320c mongo`___lldb_unnamed_symbol32$$mongo + 1784
   frame #1: 0x42b29b58
   frame #2: 0x42b289f8

==
[root@rpi4 /tmp]# /usr/local/bin/mongo
Illegal instruction (core dumped)

[root@rpi4 /tmp]# lldb /usr/local/bin/mongo -c /var/tmp/0.mongo.0.55421.core
(lldb) target create "/usr/local/bin/mongo" --core 
"/var/tmp/0.mongo.0.55421.core"
Core file '/var/tmp/0.mongo.0.55421.core' (aarch64) was loaded.

(lldb) bt
* thread #1, name = 'mongo', stop reason = signal SIGILL
 * frame #0: 0x016a320c mongo`___lldb_unnamed_symbol32$$mongo + 1784
   frame #1: 0x42b29b58 ld-elf.so.1`objlist_call_init(list=, 
lockstate=) at rtld.c:2855:7
   frame #2: 0x42b289f8 ld-elf.so.1`_rtld(sp=, 
exit_proc=, objp=) at rtld.c:828:5
   frame #3: 0x42b264d8 ld-elf.so.1`.rtld_start at rtld_start.S:41

==

NB: The default of the port uses LTO. I disabled it on my build system because 
of lack of memory.

Can anybody help me with this?

It would be interesting to know if this also happens on amd64.

Regards,
Ronald.

___
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: Illegal instruction on new port mongodb49 on arm64

[Ronald Klop]

Van: "Micha? Górny" 
Datum: donderdag, 1 april 2021 10:47
Aan: Ronald Klop , freebsd-ports@freebsd.org, 
freebsd-...@freebsd.org
Onderwerp: Re: Illegal instruction on new port mongodb49 on arm64


On Thu, 2021-04-01 at 10:37 +0200, Ronald Klop wrote:
> Hi,
>
> I created a new port for mongodb49: 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254631
> It compiles fine: https://www.klop.ws/mongodb49-4.9.0.r0.log
>
> When I run an application I get "Illegal Instruction" error.
>
> ==
> [root@rpi4 /tmp]# lldb /usr/local/bin/mongo
> (lldb) target create "/usr/local/bin/mongo"
> Current executable set to '/usr/local/bin/mongo' (aarch64).
> (lldb) run
> Process 55420 launching
> Process 55420 launched: '/usr/local/bin/mongo' (aarch64)
> Process 55420 stopped
> * thread #1, name = 'mongo', stop reason = signal SIGILL: illegal trap
> frame #0: 0x016a320c mongo`___lldb_unnamed_symbol32$$mongo + 1784
> mongo`___lldb_unnamed_symbol32$$mongo:
> ->  0x16a320c <+1784>: ldaddal x9, x8, [x8]

According to [1], this instruction requires ARMv8.1.  If I grep
correctly, rpi4 is ARMv8-A.  Yet you're compiling with -march=armv8.2-a,
so it's a case of wrong -march.

[1] 
https://developer.arm.com/documentation/100069/0608/A64-Data-Transfer-Instructions/LDADDA--LDADDAL--LDADD--LDADDL--LDADDAL--LDADD--LDADDL

--
Best regards,
Micha Górny

 







Hi,

Thank you for the quick insight.
Now I found this update upstream: https://jira.mongodb.org/browse/SERVER-55178 
and 
https://github.com/mongodb/mongo/commit/8f708f3b68c3c85108294a8f58d780b6ccf18194
 .
Not much info why this was necessary though. I hate it when a commit message 
describes *what* changed instead of *why* it changed. The what is already in 
the diff.

Anyways. Thanks for the reply. I think I'll need to try to contact somebody at 
MongoDB.

Regards,
Ronald.

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

git-tiny or git-lite - Re: No update for a day on ports?

[Ronald Klop]

Hi,

I like pkg install git-tiny or git-lite so much more. If I install git I 
don't see why I need to install subversion as a dependency. And 50+ other 
direct or indirect dependencies.

But gitup also helps for port users.

Regards,
Ronald.


Van: Mathieu Arnold 
Datum: donderdag, 1 april 2021 10:01
Aan: Milan Obuch 
CC: freebsd-ports@freebsd.org
Onderwerp: Re: No update for a day on ports?


On Thu, Apr 01, 2021 at 09:54:16AM +0200, Milan Obuch wrote:
> On Thu, 1 Apr 2021 09:47:04 +0200, Mathieu Arnold 
> wrote:
>
> > On Thu, Apr 01, 2021 at 09:16:15AM +0200, Milan Obuch wrote:
> > > Also, what about svn mirror, as is done for src repository, for 11
> > > and 12 branches at least? I did not tried it recently, but it used
> > > to work. For some boxes, adding git to the mix would be big PITA.  
> >

> > There will be no Git to Subversion conversion for ports, like for
> > docs. The only reason there is for the base system on 11 and 12 is
> > because Subversion was the source control software used when they
> > were released.
> >
>
> This is unpleasant move for me. This means git or equivalent (and
> dependencies) must be installed on any box where tracking ports tree is
> planned/needed... and no tool like svnlite could be expected in base
> system for some time.
>
> So I need some work on my local infrastructure to adjust to this move.
> C'est la vie...

If you actually need a repository, and not just the latest files, all
you need is run pkg install git on the machines you are actually using a
ports tree on, if you have more than one machine, you should probably be
using binary packages anyway, either the ones provided by FreeBSD, or
ones built yourself using ports-mgmt/poudriere.  If you only need the
latest files, you can probably use something like net/gitup.

--
Mathieu Arnold



 

___
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: gitup on two machines

[Ronald Klop]

Maybe the second machine is up to date.
Or do you mean that gitup does not exit but keeps waiting forever? 




Regards, 
Ronald 



Van: "@lbutlr" 
Datum: 5 april 2021 18:49
Aan: FreeBSD 
Onderwerp: gitup on two machines




I have tow machines, both on 12.2-RELEASE

Running `gitup ports` on one server updates the ports tree. Running the the 
same command with the same configuration (pointing at the GitHub mirror in both 
cases) just sits there with no feedback and does nothing, even if I run it with 
a -v 2 flag.

   "ports" : {
"host"   : "github.com",
"repository" : "/freebsd/freebsd-ports.git",
"branch" : "main",
"target" : "/usr/ports",
"ignores": [
"distfiles",
"packages",
],
},

Server1 is x86 and Server2 is amd64


--
"Are you pondering what I'm pondering?"
"Whuh... I think so, Brain, but... but if Charlton Heston doesn't eat
Soylent Green, what will he eat?"

___
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: poudriere: net/openldap24-server: stage/runaway , building forever

[Ronald Klop]

Hi,

The official pkg builders are also stuck for 14-CURRENT. Although at a 
different port sysutils/msktutil.

See main-amd64 at https://pkg-status.freebsd.org/builds?type=package

It is stuck in "stage/runaway" for 61 hours now. 
http://beefy18.nyi.freebsd.org/build.html?mastername=main-amd64-default&build=p569609_s5b3b19db73
 (ipv6 only)

NB: I'm not involved in the pkg building cluster.

Regards,
Ronald.


Van: "O. Hartmann" 
Datum: vrijdag, 9 april 2021 07:27
Aan: FreeBSD Ports 
Onderwerp: Re: poudriere: net/openldap24-server: stage/runaway , building 
forever


On Fri, 9 Apr 2021 06:17:03 +0200
"Hartmann, O."  wrote:

> Recent CURRENT host (FreeBSD 14.0-CURRENT #26 main-n245806-4d221f59b85: Sat
> Apr  3 06:43:44 CEST 2021 amd64), poudriere CURRENT jail at 14.0-CURRENT
> 147 amd64 from 2021-04-08 05:25:38. It seems that the recent CURRENT does
> have a serious problem when building net/openldap24-server. The build process
> gets stuck with staging and is marked "runaway":
>
> [head-amd64-head-default] [2021-04-08_13h56m41s] [parallel_build:] Queued:
> 1847 Built: 63 Failed: 17   Skipped: 1759 Ignored: 8Tobuild: 0 Time:
> 13:26:35 [01]: net/openldap24-server | openldap-sasl-server-2.4.58
> stage/runaway (06:28:32 / 08:41:16)
>
> Also, on jails (recent CURRENT) serving as OpenLDAP server (also recent taken
> from git /usr/ports, branch main), run into a serious problem starting slapd,
> when starting slapd and the process is reporting checking configuration, it
> freezes forever. Putting slapd into debug mode doesn't help, since the freeze
> is quite early.
>
> Does anybody know what the reason for this strange behaviour is on CURRENT?
> All CURRENT servers are affected (almost all the same revision as shown
> above)?
>
> Thanks in advance,
>
> O. Hartmann

Short update, another host is stuck at the very same point, host's CURRENT is at
 FreeBSD 14.0-CURRENT #2 main-n245870-86a52e262a6: Wed Apr  7 13:57:20 CEST
 2021 amd64, it's jails is taken from the same source.

The process is stuck at staging and took 34 hours ... never seen before:


[...]
[09:05:25] [03] [02:13:44] Finished net/openldap24-server |
openldap-sasl-server-2.4.58: Failed: stage/runaway load: 10.39  cmd: awk 24374
[running] 0.06r 0.00u 0.00s 0% 3420k [headamd64-head-default]
[2021-04-07_12h26m18s] [parallel_build:] Queued: 3298 Built: 2123 Failed: 7
Skipped: 1161 Ignored: 7Tobuild: 0 Time: 40:52:34 [03]:
net/openldap24-server | openldap-sasl-server-2.4.58 stage/runaway
(31:48:30 / 34:01:11) [40:52:52] Logs:
/pool/poudriere/data/logs/bulk/headamd64-head-default/2021-04-07_12h26m18s
___
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: Access to detailed status info on package build servers

[Ronald Klop]

Van: Kevin Oberman 
Datum: 14 april 2021 08:31
Aan: Simon Wright 
CC: FreeBSD Ports ML 
Onderwerp: Re: Access to detailed status info on package build servers




On Tue, Apr 13, 2021 at 11:02 PM Simon Wright  wrote:

> Hi all,
>
> As detailed in other threads, I have been tracking the latest complete
> build information on the package build servers (actually on
> beefy6.ny.freebsd.org) in order to synchronise my ports tree with the
> ports tree used by the build servers. This is so that the packages that
> I build locally are as far as possible in sync with the packages
> available from the freebsd mirrors.
>
> I use a script to pull down this file:
>
> http://beefy6.nyi.freebsd.org/data/122amd64-default/.data.json
>
> and extract the builds.latest field from it for the jail. Since the move
> to git I can no longer access this file. Curl fails with an error 7
> which is a permission denied error.
>
> This is the command line I have been using:
> /sbin/curl -so -
> http://beefy6.nyi.freebsd.org/data/122amd64-default/.data.json
>
> Can anyone suggest another source for this data? Does the pkg-status
> server have this info in a JSON file somewhere? It is on the status page
> for the build here:
>
>
> 
https://pkg-status.freebsd.org/builds/default:default:122amd64:4c2cc95952a6:beefy6
>
> Build 4c2cc95952a6
> Serverbeefy6
> Statusstopped:done:
> Jail  122amd64
> Set   default
> Ports Tree  default
> Build type  Package
> Start time  2021-04-10 01:01
> Elapsed   99:04:36
> SVN
>
> Or is it possible to return the access permissions for this
> server/directory/file to what they were last week?
>
> Thanks for any guidance.
>
> Simon Wright.
> ___
> 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"
>
This is likely not your problem, but Is it possible that you have an IPv6
issue? As of a few days ago, beefy6 is IPv6 only. For me, it means no
access unless I bring up a tunnel as Frontier does not support IPv6. Next
week I'll be moving to Comcast and that will fix the problem. Since it
appears that Frontier has no plans to ever support IPv6 on fiber, or at
least not for several years, I guess an HE tunnel is the only fix if I want
500 Mbps FIOS.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
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"










If it is because of ipv6 you can also wrap the url in a service like 
http://www.ipv6proxy.net/
I use that sometimes to access the pkg servers.


Regards,
Ronald
___
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"

lang/go coredumps on RPI4

[Ronald Klop]

Hi maintainer of lang/go and ports ML,

Latest go gives an Illegal Instruction on arm64.
I'm running FreeBSD-14/arm64 on RPI4. Compilation of lang/go goes well. But 
follow-up ports like grafana7 and mongodb42-tools coredump during compilation.

[00:01:12] ===>  Building mongodump from ./mongodump/main
[00:01:12] go tool compile: signal: illegal instruction (core dumped)
[00:01:12] *** Error code 1
[00:01:12]
[00:01:12] Stop.
[00:01:12] make: stopped in /usr/ports/databases/mongodb42-tools

I tried to get some debug info. I don't know if I got useful information here. 
I don't use gdb/lldb and go that often.

root@rpi4:/ # /usr/bin/lldb -c var/tmp/65534.compile.0.63376.core 
/usr/local/go/pkg/tool/freebsd_arm64/compile
(lldb) target create "/usr/local/go/pkg/tool/freebsd_arm64/compile" --core 
"var/tmp/65534.compile.0.63376.core"
Core file '/var/tmp/65534.compile.0.63376.core' (aarch64) was loaded.

Cannot read termcap database;
using dumb terminal settings.
(lldb) bt
This version of LLDB has no plugin for the go language. Inspection of frame 
variables will be limited.
* thread #1, name = 'compile', stop reason = signal SIGILL
  * frame #0: 0x00074880 compile`_rt0_arm64_freebsd at 
rt0_freebsd_arm64.s:9
    frame #1: 0x00074880 compile`runtime.asyncPreempt at 
preempt_arm64.s:148
(lldb) quit


NB: This compiles fine on the FreeBSD pkg builders. So it might have something 
todo with ARMv8.1 vs ARMv8.2 instruction set. I'm not familiar with this.
NB2: It also compiles fine in a FreeBSD-12 jail which uses an older clang 
version.

Regards,

Ronald.

___
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: security/luasec maintainer not responding

[Ronald Klop]

On 4/29/21 7:54 PM, Yasuhiro Kimura wrote:

From: Thomas Morper 
Subject: security/luasec maintainer not responding
Date: Thu, 29 Apr 2021 19:42:35 +0200 (CEST)


Second: how do you deal with this situation in general? I think I've asked
this question before, but the results were somewhat inconclusive. When is
a port considered unmaintained despite formally having a maintainer and
how do you either mark it as unmaintained or assign a new maintainer with
the least amount of work for anyone involved?


1. Submit patch to change MAINTAINER of the port in question.
2. Wait for timeout (for about a month).
3. Ask committers for commiting the patch.

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




There is documentation about this:
https://docs.freebsd.org/en_US.ISO8859-1/books/porters-handbook/makefile-maintainer.html

Regards,
Ronald.

___
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: lang/go coredumps on RPI4

[Ronald Klop]

On 4/29/21 5:03 PM, Ronald Klop wrote:

Hi maintainer of lang/go and ports ML,

Latest go gives an Illegal Instruction on arm64.
I'm running FreeBSD-14/arm64 on RPI4. Compilation of lang/go goes well. But 
follow-up ports like grafana7 and mongodb42-tools coredump during compilation.

[00:01:12] ===>  Building mongodump from ./mongodump/main
[00:01:12] go tool compile: signal: illegal instruction (core dumped)
[00:01:12] *** Error code 1
[00:01:12]
[00:01:12] Stop.
[00:01:12] make: stopped in /usr/ports/databases/mongodb42-tools

I tried to get some debug info. I don't know if I got useful information here. 
I don't use gdb/lldb and go that often.

root@rpi4:/ # /usr/bin/lldb -c var/tmp/65534.compile.0.63376.core 
/usr/local/go/pkg/tool/freebsd_arm64/compile
(lldb) target create "/usr/local/go/pkg/tool/freebsd_arm64/compile" --core 
"var/tmp/65534.compile.0.63376.core"
Core file '/var/tmp/65534.compile.0.63376.core' (aarch64) was loaded.

Cannot read termcap database;
using dumb terminal settings.
(lldb) bt
This version of LLDB has no plugin for the go language. Inspection of frame 
variables will be limited.
* thread #1, name = 'compile', stop reason = signal SIGILL
   * frame #0: 0x00074880 compile`_rt0_arm64_freebsd at 
rt0_freebsd_arm64.s:9
     frame #1: 0x00074880 compile`runtime.asyncPreempt at 
preempt_arm64.s:148
(lldb) quit


NB: This compiles fine on the FreeBSD pkg builders. So it might have something 
todo with ARMv8.1 vs ARMv8.2 instruction set. I'm not familiar with this.
NB2: It also compiles fine in a FreeBSD-12 jail which uses an older clang 
version.

Regards,

Ronald.

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



Gdb gives about the same output and I learned the "disass" command.
UDF instruction seems to be UNDefined so it might get into a codepath which it 
should not get into.


[root@rpi4 /var/tmp]# gdb /usr/local/go/pkg/tool/freebsd_arm64/compile 
./0.compile.0.84815.core
GNU gdb (GDB) 10.1 [GDB v10.1 for FreeBSD]
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "aarch64-portbld-freebsd14.0".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/local/go/pkg/tool/freebsd_arm64/compile...
[New LWP 298311]
Core was generated by `/usr/local/go/pkg/tool/freebsd_arm64/compile -V=full'.
Program terminated with signal SIGILL, Illegal instruction.
#0  _rt0_arm64_freebsd () at /usr/local/go/src/runtime/rt0_freebsd_arm64.s:9
9   ADD $8, R0, R1  // argv
warning: File "/usr/local/go/src/runtime/runtime-gdb.py" auto-loading has been declined 
by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load".
To enable execution of this file add
add-auto-load-safe-path /usr/local/go/src/runtime/runtime-gdb.py
line to your configuration file "/root/.gdbinit".
--Type  for more, q to quit, c to continue without paging--
To completely disable this security protection add
set auto-load safe-path /
line to your configuration file "/root/.gdbinit".
For more information about this security protection see the
"Auto-loading safe path" section in the GDB manual.  E.g., run from the shell:
info "(gdb)Auto-loading safe path"
(gdb) bt
#0  _rt0_arm64_freebsd () at /usr/local/go/src/runtime/rt0_freebsd_arm64.s:9
(gdb) disass
Dump of assembler code for function _rt0_arm64_freebsd:
=> 0x00074880 <+0>:udf #0
   0x00074884 <+4>:   udf #0
   0x00074888 <+8>:   udf #0
   0x0007488c <+12>:  udf #0
End of assembler dump.


I can reproduce it by running a simple "go run helloworld.go".

Any thoughts?

Regards,
Ronald.
___
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: I thought "pkg updating" would alert me about python...?

[Ronald Klop]

On 5/2/21 4:20 PM, David Wolfskill wrote:

I just re-verified the behavior, so -- even though I have already
started taking evasive action (updating python), I figured it may be of
use to show what I'm seeing; maybe I'm confused:

Local ports tree is updated; previous ports update was a week ago.  I
happen to know that there's an UPDATING entry:

lgld-dhw(12.2-S)[4] tail +16 /usr/ports/UPDATING | head -5
20210425:
   AFFECTS: users of python
   AUTHOR: k...@freebsd.org

   The default version of python3 and python was switched to 3.8.


And that this machine should be affected:

lgld-dhw(12.2-S)[5] pkg info -o python\*
python27-2.7.18_1  lang/python27
python36-3.6.13lang/python36
python38-3.8.9 lang/python38


[As noted above, I had already started evasive action.]

But "pkg updating" is not actually showing the above entry:

lgld-dhw(12.2-S)[6] pkg updating -d 20210424
lgld-dhw(12.2-S)[7] echo $?
0


Am I alone in expecting "pkg updating" to have displayed the 20210425
entry?

(There was an issue a while back, where "pkg updating" was not showing
"glob" entries, but that has since been addressed.)

This is on a machine running stable/12:

lgld-dhw(12.2-S)[8] uname -a
FreeBSD lgld-dhw.corp.example.com 12.2-STABLE FreeBSD 12.2-STABLE #21 
stable/12-n233048-23a3c3d97d72: Sun May  2 04:43:57 PDT 2021 
r...@lgld-dhw.corp.example.com:/common/S2/obj/common/S2/src/amd64.amd64/sys/GENERIC
  amd64
lgld-dhw(12.2-S)[9] pkg -v
1.16.3

Thanks.

Peace,
david




The UPDATING file says "users of python" while the pkg/port name is python37. 
So that does not match. It does match for humans but not for computers. :-)
The UPDATING entry should have said something like "users of lang/python*" to 
work.

Regards,
Ronald.
___
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: I thought "pkg updating" would alert me about python...?

[Ronald Klop]

Van: Tatsuki Makino 
Datum: 2 mei 2021 22:36
Aan: Ronald Klop , freebsd-ports@freebsd.org
Onderwerp: Re: I thought "pkg updating" would alert me about python...?




Ronald Klop wrote on 2021/05/03 05:14:
> The UPDATING entry should have said something like "users of lang/python*" to 
work.

The behavior of this is strange.
I have the following python* in my environment.
python, python27, python3, python37 and python38

AFFECTS: users of python : not match
AFFECTS: users of pytho? : match
AFFECTS: users of python3 : not match
AFFECTS: users of python* : match
AFFECTS: users of python3[7] : match

package names are also comparable.
Does it not pattern match if the pattern match symbol ?, [] or * is not 
included?

Regards.








If I read the pkg source correctly it uses regex with some glob-like 
preparation like converting * to 
.*.https://github.com/freebsd/pkg/blob/62302ab4b4d69528e155ea7b68f058a05d6dffdd/src/updating.c#L71And
 it indeed checks if the word contains regex characters. If not it compares 
with strcmp.
strpbrk(words[i],"^$*|?") == NULL



What is remarkable is that it compares to "origin". I think origin is the full portname 
"lang/python". The regex match also matches a substring of origin.


This would explain why pytho? matches, but python didn't.


NB: this is by  looking at the C code for a minute with my rusty C skills. I 
might have overlooked something. 😅

Regards,Ronald
___
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: Ports recompile for 13.0-RELEASE

[Ronald Klop]

On 5/4/21 4:10 PM, @lbutlr wrote:

With the move to FreeBSD 13.0 is there a simple (single step) way to reinstall 
all the current ports other than saving off a list of the ports and then 
stepping through that list to reinstall them? It was very inefficient when 
moving to 12.0 as many ports in the list, of course, were dependent on other 
ports, but then got recompiled, sometimes multiple times. I know I ended up in 
a make loop where came was compiled over and over again until I aborted, listed 
the current ports, differ on the previous ports, and picked a port I though 
would have a lot of reps to restart the compile. I then did this several more 
times to get back to where I had been on 11.x



I used "portmaster -fa" in the past.
(see ports-mgmt/portmaster)
 

And there's still no way to tell if a port was installed from pkg or from 
ports, correct? Since I use MariaDB instead of MySQLI have to be sure I don't 
try to use package for anything that will try to install MySQL instead.



I don't know.


And finally, the release of 13.0 ends the 12.x versions, right? There will not 
be a 12.3.


https://www.freebsd.org/security/#sup

12.x has support until 2024. So a 12.3 is in the pipeline. 12.4 probably also. 
11.4 was the latest 11.x release AFAIK.



(And yes, I've tried moving to poudrerie several times and we do not get on. At 
all.)




Might help to do another attempt. Especially if you are using custom port 
settings instead of pkgs.


Regards,
Ronald.
___
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"

looking for committer

[Ronald Klop]

Hi,

I'm looking for a committer for the following port issues.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255118 (mongodb40, maintainer 
gave +feedback instead of +approval)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255117 (monbodb40-tools, 
maintainer gave +feedback instead of +approval)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255255 (grafana7 depends on 
ca_root_nss, maintainer did not react for 2 weeks)

Thanks in advance.

Regards,
Ronald.

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

pkg builders order of jobs

[Ronald Klop]

Hi,

On the pkg builders the list of builds is ordered on git hash.
http://beefy18.nyi.freebsd.org/jail.html?mastername=main-amd64-default
(NB: ipv6 only)

This ordering is totally random to me. With svn the list was naturally  
ordered because of the incremental commit id.


Is it possible to add the commit count to the job-name like  
sys/conf/newvers.sh in base?

git_cnt=$($git_cmd rev-list --first-parent --count HEAD 2>/dev/null)

Regards,
Ronald.
___
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: pkg builders order of jobs

[Ronald Klop]

Van: Stefan Esser 
Datum: zondag, 9 mei 2021 12:40
Aan: po...@freebsd.org
Onderwerp: Re: pkg builders order of jobs


Am 09.05.21 um 12:22 schrieb Ronald Klop:
> Hi,
>
> On the pkg builders the list of builds is ordered on git hash.
> http://beefy18.nyi.freebsd.org/jail.html?mastername=main-amd64-default
> (NB: ipv6 only)
>
> This ordering is totally random to me. With svn the list was naturally ordered
> because of the incremental commit id.
>
> Is it possible to add the commit count to the job-name like 
sys/conf/newvers.sh
> in base?
> git_cnt=$($git_cmd rev-list --first-parent --count HEAD 2>/dev/null)

Adding the start-time of the build in ISO format would also be highly
appreciated, at least by me ;-)

The date should reflect the time of the last commit that has been
considered. Such a time stamp would let me see with little effort
whether a failure is due to a long running build job that did not
catch-up with the latest fixes to a port, or whether there still is
an issue with a port (especially for the "exotic" architectures that
I do not test on my system and that often need a lot longer to complete
a build job).

Regards, STefan
 




 



Hi,

Which method is used to create a sortable list for human readabiltiy does not 
really matter to me.
Commit count or unix timestamp or 20210510_1147 or some Poudriere internal 
build number or something I did not think of. Everything is better than 
pseudo-random hex strings to me. :-)

At home my Poudriere names the builds like "2021-05-09_20h49m55s". I don't 
remember configuring this by myself, so I think it is the default. But I can imagine 
people also want an exact reference to the git hash. Maybe the SVN property in the 
Poudriere page can be used for that. I don't know, somebody with more inside knowledge 
should decide.

Regards,
Ronald.

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

looking for ports committer (net/ldapbrowser)

[Ronald Klop]

Hi,

Somebody changed the LICENSE* stuff in my net/ldapbrowser port. It does not 
compile anymore.

This change fixes it.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255752

I mailed mat@ about his change breaking my port, but did not hear anything from 
him for about ten days. (no offense) So I'm trying the ML.

Ronald.

___
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: looking for ports committer (net/ldapbrowser)

[Ronald Klop]

On 5/20/21 10:48 AM, Ronald Klop wrote:

Hi,

Somebody changed the LICENSE* stuff in my net/ldapbrowser port. It does not 
compile anymore.

This change fixes it.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255752

I mailed mat@ about his change breaking my port, but did not hear anything from 
him for about ten days. (no offense) So I'm trying the ML.

Ronald.



Never mind, somebody else committed a fix in the meantime. (I got a conflict on 
git pull.)

https://cgit.freebsd.org/ports/commit/?id=a0c694d15d97dfefdda209823d47440fbfa02d3a

Ronald.
___
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: Large builds with poudriere

[Ronald Klop]

On 5/20/21 2:47 PM, Fernando Apesteguía wrote:

El jue., 20 may. 2021 14:45, Alexis Praga  escribió:



Hi guys,

I've recently been using poudriere to test news ports but this resulted in
building two large ports, namely:
- devel/llvm [1]
- lang/rust [2]

Now, lang/rust takes 2 hourse to compile. So testing for 13.0, 12.2 and
11.4 means around 6 hours in total, a lot of time for my desktop
computer. Especially if the dependencies are upgraded later on.

Do you have any tips to deal with such long build time ? Apart from
have a dedicated server :)



Patience :-)

Package seeding in poudriere is a long awaited feature.




You can manually put the rust/llvm package in the All packages directory and 
poudriere will use that. It is a manual repeating task though. So the package 
seeding is indeed a nice feature.

Ronald.




 

Thanks,


[1] For https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233010
[2] For https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255233

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



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

opera 12.11 libpng error

[Ronald Klop]

Hi,

I have the same libpng error when starting Opera 12.11 as already  
mentioned on this list. I happen to run KDE and ktrace shows me it crashes  
while reading icons like  
/usr/local/kde4/share/icons/oxygen/64x64/mimetypes/unknown.png.
After renaming these icons so Opera does not find them it still prints  
'libpng error: incorrect data check' but does not crash anymore.

If I start without KDE integration there is no error anymore.
You can do this by adding Dialog Toolkit=4 to the [File Selector] part of  
your opera*.ini.

http://de.opera.com/support/usingopera/operaini/#file_selector

Not an ideal solution, but at least I can read my e-mail again in Opera.

Cheers,
Ronald.

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: opera 12.11 libpng error

[Ronald Klop]

On Thu, 29 Nov 2012 00:21:33 +0100, ajtiM  wrote:


On Wednesday 28 November 2012 15:57:44 Ion-Mihai Tetcu wrote:

On Wed, 28 Nov 2012 21:28:30 +0100

"Ronald Klop"  wrote:
> Hi,
>
> I have the same libpng error when starting Opera 12.11 as already
> mentioned on this list. I happen to run KDE and ktrace shows me it
> crashes while reading icons like
> /usr/local/kde4/share/icons/oxygen/64x64/mimetypes/unknown.png.
> After renaming these icons so Opera does not find them it still
> prints 'libpng error: incorrect data check' but does not crash
> anymore. If I start without KDE integration there is no error anymore.
> You can do this by adding Dialog Toolkit=4 to the [File Selector]
> part of your opera*.ini.
> http://de.opera.com/support/usingopera/operaini/#file_selector
>
> Not an ideal solution, but at least I can read my e-mail again in
> Opera.

I've added a note in UPDATING for this, thank you!


Thank you very much for help...
It works now but Opera is not as before. It crashed on many sites (also  
at
work on my Mac), I cannot upload pictures on Redbubble (Xombrero or  
Konqueror

are much better). I hope Opera 12.12 would be better

Thank you to everyone for the help again...

Mitja


Please report a bug at opera.com about this.
https://bugs.opera.com/wizarddesktop/

Ronald.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: /archivers/ is missing after svn...

[Ronald Klop]

On Thu, 29 Nov 2012 05:28:51 +0100, Jeffrey Bouquet  
 wrote:





--- On Wed, 11/28/12, Jeffrey Bouquet  wrote:

From: Jeffrey Bouquet 
Subject: /archivers/ is missing after svn...
To: freebsd-ports@freebsd.org
Date: Wednesday, November 28, 2012, 8:20 PM

As in the subject.  Anyone else?
r 307953

UPDATE:

OTOH I can svn it independently to elsewhere than ports, any canonical  
way

to move that /tmp/archivers to /usr/ports/archivers ??

J. Bouquet


File permissions of /usr/ports? Or /usr/ports/archivers?
Any error messages while doing what you are doing?

Ronald.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: /archivers/ is missing after svn...

[Ronald Klop]

On Thu, 29 Nov 2012 13:45:23 +0100, Jeffrey Bouquet  
 wrote:





--- On Wed, 11/28/12, Jeffrey Bouquet  wrote:

From: Jeffrey Bouquet 
Subject: Re: /archivers/ is missing after svn...
To: freebsd-ports@freebsd.org
Date: Wednesday, November 28, 2012, 8:28 PM



--- On Wed, 11/28/12, Jeffrey Bouquet  wrote:

From: Jeffrey Bouquet 
Subject: /archivers/ is missing after svn...
To: freebsd-ports@freebsd.org
Date: Wednesday, November 28, 2012, 8:20 PM

As in the subject.  Anyone else?
r 307953

UPDATE:

OTOH I can svn it independently to elsewhere than ports, any canonical  
way

to move that /tmp/archivers to /usr/ports/archivers ?

DONE:
moved that /tmp/archivers to /usr/ports/archivers, strangely I did not  
find its

.svn after the move.
So a port sees /usr/ports/archivers, but still fails to configure.  I'll  
wait a while
to see if that changes...   Don't know enough about the port nor svn to  
figure

out much more about it.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"



Hi,

Since subversion (svn) 1.7 there is only one .svn directory in the root of  
your checkout. Not in every subdir anymore.


Ronald.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: /archivers/ is missing after svn...

[Ronald Klop]

On Thu, 29 Nov 2012 20:04:08 +0100, Jeffrey Bouquet  
 wrote:





--- On Thu, 11/29/12, Warren Block  wrote:

From: Warren Block 
Subject: Re: /archivers/ is missing after svn...
To: "Jeffrey Bouquet" 
Cc: freebsd-ports@freebsd.org
Date: Thursday, November 29, 2012, 7:00 AM

On Thu, 29 Nov 2012, Jeffrey Bouquet wrote:


UPDATE:

OTOH I can svn it independently to elsewhere than ports, any canonical  
way

to move that /tmp/archivers to /usr/ports/archivers ?

DONE:
moved that /tmp/archivers to /usr/ports/archivers, strangely I did not  
find its

.svn after the move.


Multiple partial checkouts is not the same as one big checkout.  The
.svn directory only exists in the base directory of the checkout.

Back up /usr/ports (for local changes), delete the entire directory,
then check out the entire directory.
___
Done.
Unfortunately I forgot to relocate /packages/ and /distfiles/ first, so
they have been restored from yesterday's backup.
Also there is an INDEX-9.move_distfiles  (zero length file) for the next
time, as a reminder, as I'd move INDEX* out of the way first.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"



Packages and distfiles are cache directories to save on network bandwidth.  
If your internet is not very slow or on a data limit then it is harmless  
to delete their content. The files will get downloaded when they are  
needed again.


You sound to me like you moved the content of /usr/ports to another place  
per file or per directory.

I hope you did something like this.
mv /usr/ports /usr/ports-old
svn checkout svn+ssh://svn.freebsd.org/ports/head /usr/ports

This will restore a complete and consistent ports directory. And you don't  
need the reminders, etc.


Regards,
Ronald.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [RFC/HEADSUP] portmaster default -w (preserve shared libraries)

[Ronald Klop]

On Tue, 11 Dec 2012 18:04:33 +0100, Chris Rees  wrote:


On 11 Dec 2012 16:44, "Alex Dupre"  wrote:


Jeremy Messenger ha scritto:

>> Absolutely yes from me. The -w option is real lifesaver and should be
>> on by default.
>
> I disagree. The -w is a temp fix and not a correct solution, so it
> shouldn't be default.

I agree with your disagreement :-)



I get what you're saying, but please consider which is easier to reverse-
deleting an accidentally saved library, or restoring an accidentally
deleted library?

Defaults should be safe.  I was bitten by this with pcre- sometimes we
can't update all our ports at one time.

How isn't it correct?  We still keep src libraries around until we make
delete-old-libs.  Why should ports be different?

Chris


Doesn't the ports framework itself also keep the old libraries around in  
/usr/local/lib/compat/pkg or something like that?


Ronald.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Problems with samba-* ports on arm

[Ronald Klop]

The bt from gdb is weird. It looks like the error handler of Samba crashes.

Ronald.


On Sat, 15 Dec 2012 14:12:11 +0100, Timur I. Bakeyev   
wrote:


File a PR. The problem is that I don't have ARM box around, so it's hard  
to

debug.

There is an attempt to address a problem with the ARM in the port:
.if ${ARCH} == "arm"
CONFIGURE_ARGS+=--disable-pie
.endif

But it never was tested live.




On Mon, Nov 5, 2012 at 1:09 PM, Łukasz  wrote:


Hello everyone,
 I'm not sure whether this is the correct list, but I would like to
report my efforts to build and run samba on ARM machine (sheevaplug) -
# uname -mopr
FreeBSD 8.3-STABLE arm arm

samba36-3.6.9
nmbd - works fine
smbd - core dump with bus error


 # smbd -V
Version 3.6.9

 # gdb smbd smbd.core
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for  
details.

This GDB was configured as "arm-marcel-freebsd"...
Core was generated by `smbd'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /lib/libcrypt.so.5...done.
Loaded symbols for /lib/libcrypt.so.5
Reading symbols from /usr/lib/libpam.so.5...done.
Loaded symbols for /usr/lib/libpam.so.5
Reading symbols from /usr/local/lib/libexecinfo.so.1...done.
Loaded symbols for /usr/local/lib/libexecinfo.so.1
Reading symbols from /lib/libmd.so.5...done.
Loaded symbols for /lib/libmd.so.5
Reading symbols from /usr/local/lib/libiconv.so.3...done.
Loaded symbols for /usr/local/lib/libiconv.so.3
Reading symbols from /usr/local/lib/libdmalloc.so.1...done.
Loaded symbols for /usr/local/lib/libdmalloc.so.1
Reading symbols from /usr/local/lib/libpopt.so.0...done.
Loaded symbols for /usr/local/lib/libpopt.so.0
Reading symbols from /usr/local/lib/libtalloc.so.2...done.
Loaded symbols for /usr/local/lib/libtalloc.so.2
Reading symbols from /usr/local/lib/libtdb.so.1...done.
Loaded symbols for /usr/local/lib/libtdb.so.1
Reading symbols from /lib/libz.so.5...done.
Loaded symbols for /lib/libz.so.5
Reading symbols from /lib/libc.so.7...done.
Loaded symbols for /lib/libc.so.7
Reading symbols from /lib/libm.so.5...done.
Loaded symbols for /lib/libm.so.5
Reading symbols from /usr/local/lib/libintl.so.9...done.
Loaded symbols for /usr/local/lib/libintl.so.9
Reading symbols from /usr/lib/librt.so.1...done.
Loaded symbols for /usr/lib/librt.so.1
Reading symbols from /libexec/ld-elf.so.1...done.
Loaded symbols for /libexec/ld-elf.so.1
#0  0x208d20b0 in getframeaddr () from /usr/local/lib/libexecinfo.so.1
(gdb) bt
#0  0x208d20b0 in getframeaddr () from /usr/local/lib/libexecinfo.so.1
#1  0x208d1c84 in backtrace () from /usr/local/lib/libexecinfo.so.1
#2  0x003df308 in log_stack_trace () at lib/util.c:1217
#3  0x003df4bc in smb_panic (why=0x7cce40 "internal error") at
lib/util.c:1118
#4  0x003cde8c in sig_fault (sig=8179264) at lib/fault.c:57
#5  0x003cde8c in sig_fault (sig=8179264) at lib/fault.c:57
(gdb)

Below are the options:
# Options for samba36-3.6.9
_OPTIONS_READ=samba36-3.6.9
_FILE_COMPLETE_OPTIONS_LIST= LDAP ADS CUPS WINBIND SWAT ACL_SUPPORT
AIO_SUPPORT FAM_SUPPORT SYSLOG QUOTAS UTMP PAM_SMBPASS DNSUPDATE AVAHI
PTHREADPOOL EXP_MODULES POPT IPV6 MAX_DEBUG SMBTORTURE
OPTIONS_FILE_UNSET+=LDAP
OPTIONS_FILE_UNSET+=ADS
OPTIONS_FILE_UNSET+=CUPS
OPTIONS_FILE_UNSET+=WINBIND
OPTIONS_FILE_UNSET+=SWAT
OPTIONS_FILE_SET+=ACL_SUPPORT
OPTIONS_FILE_UNSET+=AIO_SUPPORT
OPTIONS_FILE_UNSET+=FAM_SUPPORT
OPTIONS_FILE_SET+=SYSLOG
OPTIONS_FILE_UNSET+=QUOTAS
OPTIONS_FILE_UNSET+=UTMP
OPTIONS_FILE_UNSET+=PAM_SMBPASS
OPTIONS_FILE_UNSET+=DNSUPDATE
OPTIONS_FILE_UNSET+=AVAHI
OPTIONS_FILE_UNSET+=PTHREADPOOL
OPTIONS_FILE_UNSET+=EXP_MODULES
OPTIONS_FILE_SET+=POPT
OPTIONS_FILE_SET+=IPV6
OPTIONS_FILE_SET+=MAX_DEBUG
OPTIONS_FILE_UNSET+=SMBTORTURE

For samba35-3.5.18 there is completely the same problem.

samba34-3.4.17

===>  Building for samba34-3.4.17
cd /usr/ports/net/samba34/work/samba-3.4.17/source3 && make pch
rm -f
/usr/ports/net/samba34/work/samba-3.4.17/source3/include/includes.h.gch
make
/usr/ports/net/samba34/work/samba-3.4.17/source3/include/includes.h.gch
cc -O -pipe -g -g -Wall -Wshadow -Wpointer-arith -Wcast-align
-Wwrite-strings -DDEBUG_PASSWORD -DDEVELOPER
-Wdeclaration-after-statement -Werror-implicit-function-declaration
-Wstrict-prototypes -I.
-I/usr/ports/net/samba34/work/samba-3.4.17/source3
-I/usr/ports/net/samba34/work/samba-3.4.17/source3/iniparser/src
-Iinclude -I./include  -I. -I. -I./../lib/replace -I/usr/local/include
  -I./../lib/tevent -I./../lib/tdb/include -I./libaddns -I./librpc
-I./..  -DHAVE_CONFIG_H  -I/usr/local/include -g -Iinclude -I./include
-I. -I. -I./../lib/replace -I/usr/local/include -I./../lib/tevent
-I./../lib/tdb/include -I./libaddns -I./librpc -I./.. -I./../lib/popt
-I/usr/local/include
-I/usr/ports/net

Re: java/openjdk6 fails to build..

[Ronald Klop]

On Thu, 20 Dec 2012 22:58:48 +0100, David Demelier  
 wrote:



Hello,

I have no luck tonight, openjdk6 fails to build too :

c++ -m64 -Xlinker -O1 -m64 -export-dynamic -o ../generated/adfiles/adlc
../generated/adfiles/adlparse.o ../generated/adfiles/archDesc.o
../generated/adfiles/arena.o ../generated/adfiles/dfa.o
../generated/adfiles/dict2.o ../generated/adfiles/filebuff.o
../generated/adfiles/forms.o ../generated/adfiles/formsopt.o
../generated/adfiles/formssel.o ../generated/adfiles/main.o
../generated/adfiles/adlc-opcodes.o ../generated/adfiles/output_c.o
../generated/adfiles/output_h.o
gmake[6]: *** No rule to make target
`/usr/obj/usr/ports/java/openjdk6/work/hotspot/src/cpu/amd64/vm/x86_64.ad',
needed by `../generated/adfiles/bsd_x86_64.ad'.  Stop.
gmake[6]: Leaving directory
`/usr/obj/usr/ports/java/openjdk6/work/build/bsd-amd64/hotspot/outputdir/bsd_amd64_compiler2/product'
gmake[5]: *** [ad_stuff] Error 2
gmake[5]: Leaving directory
`/usr/obj/usr/ports/java/openjdk6/work/build/bsd-amd64/hotspot/outputdir/bsd_amd64_compiler2/product'
gmake[4]: *** [product] Error 2
gmake[4]: Leaving directory
`/usr/obj/usr/ports/java/openjdk6/work/build/bsd-amd64/hotspot/outputdir'
gmake[3]: *** [generic_build2] Error 2
gmake[3]: Leaving directory
`/usr/obj/usr/ports/java/openjdk6/work/hotspot/make'
gmake[2]: *** [product] Error 2
gmake[2]: Leaving directory
`/usr/obj/usr/ports/java/openjdk6/work/hotspot/make'
gmake[1]: *** [hotspot-build] Error 2
gmake[1]: Leaving directory `/usr/obj/usr/ports/java/openjdk6/work'
gmake: *** [build_product_image] Error 2
*** [do-build] Error code 1




Try to set the environment variable MAKE_JOBS_NUMBER=1 before building.

Ronald.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

amarok-kde4 needs googlemock

[Ronald Klop]

Hi,

After upgrading kde to 4.10 I rebuild amarok and configure failed.

-
-- The following REQUIRED packages could NOT be located on your system.
-- You must install these packages before continuing.
-
   * gmock (1.4 or higher)  
 Used in Amarok's tests.

-

CMake Error at  
/usr/local/kde4/share/apps/cmake/modules/MacroLogFeature.cmake:152  
(MESSAGE):

  Exiting: Missing Requirements
Call Stack (most recent call first):
  CMakeLists.txt:222 (macro_display_feature_log)


After installing the port devel/googlemock it now configured good. It is  
still building.

There maybe is a dependency missing.

Oh, just as I want to press send the build fails.
/usr/local/include/gmock/gmock-matchers.h:2649:33: warning:  
"GTEST_OS_CYGWIN" is

 not defined
/usr/local/include/gmock/gmock-matchers.h:2649:33: warning:  
"GTEST_OS_SOLARIS" i

s not defined
Linking CXX executable ../../../testproxycollectionmeta
CMakeFiles/testproxycollectionmeta.dir/TestProxyCollectionMeta.o: In  
function `T

estProxyCollectionMeta::testHasCapabilityOnSingleAlbum()':
TestProxyCollectionMeta.cpp:(.text+0x12aa): undefined reference to  
`Meta::ProxyA

lbum::ProxyAlbum(Collections::ProxyCollection*, KSharedPtr)'
TestProxyCollectionMeta.cpp:(.text+0x12d9): undefined reference to  
`Meta::ProxyA

lbum::hasCapabilityInterface(Capabilities::Capability::Type) const'
TestProxyCollectionMeta.cpp:(.text+0x1307): undefined reference to  
`Meta::ProxyA

lbum::hasCapabilityInterface(Capabilities::Capability::Type) const'

Any advice?


Regards,
Ronald.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: amarok-kde4 needs googlemock

[Ronald Klop]

On Sat, 30 Mar 2013 00:07:51 +0100, Alberto Villa   
wrote:



On Friday 29 March 2013 01:30:56 Alberto Villa wrote:

On Thursday 28 March 2013 14:35:10 Ronald Klop wrote:
> After upgrading kde to 4.10 I rebuild amarok and configure failed.

This is being analyzed; for some reason, a global CMake setting changed  
with

KDE SC 4.10.


Fix committed.



Thanks!
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: JVM panic when build openjdk7 on private FreeBSD 8.2

[Ronald Klop]

On Thu, 30 May 2013 02:53:01 +0200, Xu Zhe  wrote:


于 5/30/13 1:42 AM, Chris Rees 写道:

On 29 May 2013 09:28, Peter Xu  wrote:

Hi, all,

I got strange issue when trying to build opendjk7 using ports utility  
on a

private-built FreeBSD 8.2 system. Here is the output of make:




I'm going to suggest that you upgrade to FreeBSD 8.3-- it's not a big
jump, so it shouldn't break anything.

Unfortunately ports can't be tested on unsupported versions, and 8.3
has been out over a year now.

However, I've added java@ in case they have any suggestions.

Chris

Hi, Chris,

Thanks for the mail.

The problem is, the target FreeBSD 8.2 system has been heavily hacked  
(on both kernel and libc, as far as I know), and they have been doing  
system test for months. If we (or say they) do the swtich, the porting  
of the kernel part will be huge, and test results in the past months  
will be wasted. So I suppose that is not the working solution for my  
case. :(


BTW, I would appreciate if anyone can tell me why build java need java  
support?


I don't know the internals of building Java, but with compilers it is  
generally a chicken-and-egg-problem. How do you compile the compiler? The  
compiler javac is written in Java, so you need java to build it.

But you can build a pkg of java on another machine and copy it.
Or it might work to use a ports tree of FreeBSD 8.2.
http://svnweb.freebsd.org/ports/tags/RELEASE_8_2_0/

Didn't try, buy might be worth a try.

Ronald.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [CFT] SSP Package Repository available

[Ronald Klop]

On Wed, 20 Aug 2014 18:34:22 +0200, Bryan Drewery   
wrote:



On 9/21/2013 5:49 AM, Bryan Drewery wrote:

Ports now support enabling Stack Protector [1] support on FreeBSD 10
i386 and amd64, and older releases on amd64 only currently.

Support may be added for earlier i386 releases once all ports properly
respect LDFLAGS.

To enable, just add WITH_SSP=yes to your make.conf and rebuild all  
ports.


The default SSP_CLFAGS is -fstack-protector, but -fstack-protector-all
may optionally be set instead.

Please help test this on your system. We would like to eventually enable
this by default, but need to identify any major ports that have run-time
issues due to it.

[1] https://en.wikipedia.org/wiki/Buffer_overflow_protection



We have not had any feedback on this yet and want to get it enabled by
default for ports and packages.

We now have a repository that you can use rather than the default to
help test. We need your help to identify any issues before switching the
default.

This repository is available for:

head
10.0
9.1,9.2,9.3

It is not available for 8.4. If someone is willing to test on 8.4 I will
build a repository for it.

Place this in /usr/local/etc/pkgs/repos/FreeBSD_ssp.conf:

FreeBSD: { enabled: no }
FreeBSD_ssp: {
  url: "pkg+http://pkg.FreeBSD.org/${ABI}/ssp";,
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/share/keys/pkg",
  enabled: yes
}

Once that is done you should force reinstall packages from this  
repository:


  pkg update
  pkg upgrade -f

Thanks for your help!
Bryan Drewery
On behalf of portmgr.




Hi,

Is it necessary to upgrade all packages at once or can I just enable  
WITH_SSP and upgrade ports as they are updated in the ports tree?


Ronald.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: [CFT] SSP Package Repository available

[Ronald Klop]

On Thu, 21 Aug 2014 17:55:41 +0200, Bryan Drewery   
wrote:



On 8/21/2014 6:56 AM, Ronald Klop wrote:

On Wed, 20 Aug 2014 18:34:22 +0200, Bryan Drewery 
wrote:


On 9/21/2013 5:49 AM, Bryan Drewery wrote:

Ports now support enabling Stack Protector [1] support on FreeBSD 10
i386 and amd64, and older releases on amd64 only currently.

Support may be added for earlier i386 releases once all ports properly
respect LDFLAGS.

To enable, just add WITH_SSP=yes to your make.conf and rebuild all
ports.

The default SSP_CLFAGS is -fstack-protector, but -fstack-protector-all
may optionally be set instead.

Please help test this on your system. We would like to eventually  
enable
this by default, but need to identify any major ports that have  
run-time

issues due to it.

[1] https://en.wikipedia.org/wiki/Buffer_overflow_protection



We have not had any feedback on this yet and want to get it enabled by
default for ports and packages.

We now have a repository that you can use rather than the default to
help test. We need your help to identify any issues before switching  
the

default.

This repository is available for:

head
10.0
9.1,9.2,9.3

It is not available for 8.4. If someone is willing to test on 8.4 I  
will

build a repository for it.

Place this in /usr/local/etc/pkgs/repos/FreeBSD_ssp.conf:

FreeBSD: { enabled: no }
FreeBSD_ssp: {
  url: "pkg+http://pkg.FreeBSD.org/${ABI}/ssp";,
  mirror_type: "srv",
  signature_type: "fingerprints",
  fingerprints: "/usr/share/keys/pkg",
  enabled: yes
}

Once that is done you should force reinstall packages from this
repository:

  pkg update
  pkg upgrade -f

Thanks for your help!
Bryan Drewery
On behalf of portmgr.




Hi,

Is it necessary to upgrade all packages at once or can I just enable
WITH_SSP and upgrade ports as they are updated in the ports tree?



You can let them update on their own if you wish. Of course SSP won't be
in the binaries until they are rebuilt.



Hi,

As you wanted feedback. I run with WITH_SSP_PORTS=yes in /etc/make.conf  
for about a month now on a desktop machine.
A lot of ports have recompiled in the meantime. Things like Firefox,  
icewm, urxvt, virtualbox.

No problem so far.

Cheers,
Ronald.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

certificate error - (was: Re: CFT: Update to xf86-video-ati 7.5.0)

[Ronald Klop]

On Mon, 27 Oct 2014 10:26:32 +0100, Jean-Sébastien Pédron  
 wrote:



Hi!

Before updating xf86-video-ati to 7.5.0, we would like some people to
try it out. The reason is that 7.4.0 was crashing for several users, so
we want to be sure it's fixed in 7.5.0.

Here's patch:
https://people.freebsd.org/~dumbbell/graphics/ports-xf86-video-ati-7.5.0.patch

To apply it:
  cd /usr/ports
  patch -p1 < /path/to/ports-xf86-video-ati-7.5.0.patch

Then update x11-drivers/xf86-video-ati with your method of choice.

What we're especially looking for is report of successful or failed
startup of the X server. With 7.4.0, the server would crash during
startup. But with 7.5.0, none of us could reproduce the problem.

When you're finished, you may restore your vanilla ports tree:
  cd /usr/ports
  patch -p1 -R < /path/to/ports-xf86-video-ati-7.5.0.patch
  find x11-drivers/xf86-video-ati -name "*.orig" -delete

Thank you for your help!




fetch  
'https://people.freebsd.org/~dumbbell/graphics/ports-xf86-video-ati-7.5.0.

patch'
Certificate verification failed for /C=US/ST=UT/L=Salt Lake City/O=The  
USERTRUST

 Network/OU=http://www.usertrust.com/CN=UTN-USERFirst-Hardware
34380950936:error:14090086:SSL  
routines:SSL3_GET_SERVER_CERTIFICATE:certificate
verify  
failed:/usr/src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_clnt.c:1

180:
fetch:  
https://people.freebsd.org/~dumbbell/graphics/ports-xf86-video-ati-7.5.0.

patch: Authentication error

Using the option '--ca-cert=/usr/local/share/certs/ca-root-nss.crt' from  
port ca_root_nss for fetch helps.
Something wrong in my setup, that default certs of 10.1-STABLE are not  
enough?


Regards,
Ronald.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: pkg upgrade deletes firefox?

[Ronald Klop]

Interesting:

# 21:12:51 root@sjakie [~]
pkg install firefox
Updating FreeBSD repository catalogue...
FreeBSD repository is up-to-date.
All repositories are up-to-date.
pkg: No packages available to install matching 'firefox' have been found  
in the repositories


I guess this is a temporary hickup.

Ronald.



On Thu, 09 Feb 2017 21:12:28 +0100, Ronald Klop   
wrote:



Hi,

Today I get this...

# 21:08:42 root@sjakie [~]
pkg upgrade
Updating FreeBSD repository catalogue...
Fetching meta.txz: 100%944 B   0.9kB/s00:01
Fetching packagesite.txz: 100%6 MiB   3.0MB/s00:02
Processing entries: 100%
FreeBSD repository update completed. 25950 packages processed.
Checking for upgrades (13 candidates): 100%
Processing candidates (13 candidates): 100%
The following 13 package(s) will be affected (of 0 checked):

Installed packages to be REMOVED:
firefox-51.0.1,1

Installed packages to be UPGRADED:
xkeyboard-config: 2.19 -> 2.20
xconsole: 1.0.6_1 -> 1.0.7
xauth: 1.0.9_1 -> 1.0.10
vim-lite: 8.0.0252 -> 8.0.0301
tmux: 2.3 -> 2.3_1
opencollada: 1.6.25 -> 1.6.37
mplayer: 1.3.0.20161228_2 -> 1.3.0.20161228_3
libevent2: 2.0.22_1 -> 2.1.8
libass: 0.13.5 -> 0.13.6
gstreamer1: 1.8.0 -> 1.8.0_1
gstreamer: 0.10.36_5 -> 0.10.36_6
ffmpeg: 3.2.2_5,1 -> 3.2.2_6,1

Number of packages to be removed: 1
Number of packages to be upgraded: 12

The operation will free 124 MiB.
25 MiB to be downloaded.

Proceed with this action? [y/N]:


Why would upgrade want to remove firefox?

Regards,
Ronald.
___
freebsd-sta...@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-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: svn commit: r315662 - in head: contrib/bsnmp/snmp_mibII contrib/ipfilter/ipsend lib/libprocstat sys/netinet sys/sys usr.bin/netstat usr.bin/sockstat usr.bin/systat usr.sbin/tcpdrop usr.sbin/trpt

[Ronald Klop]

On Tue, 21 Mar 2017 10:19:24 +0100, Mathieu Arnold  wrote:


Le 21/03/2017 à 08:27, Gleb Smirnoff a écrit :

On Tue, Mar 21, 2017 at 08:22:19AM +0100, Baptiste Daroussin wrote:
B> On Mon, Mar 20, 2017 at 11:54:33PM -0700, Gleb Smirnoff wrote:
B> > On Tue, Mar 21, 2017 at 07:50:32AM +0100, Antoine Brodin wrote:
B> > A> >   This change is known to break a ton of ports. More than 100  
if
B> > A> > counting depends. I'm sorry for that and I already started to  
fix

B> > A> > them.
B> > A> >
B> > A> > Please send all new breakages to me.
B> > A>
B> > A> Hi,
B> > A>
B> > A> Exp-runs should happen before breakage happens, not after.
B> > A> If you already know that it breaks hundreds of ports, please  
revert

B> > A> and request an exp-run.
B> >
B> > The exp-run has already been made:
B> >
B> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210673
B> >
B> > Wasn't very helpful.
B> >
B>
B> I disagree it was useful it showed you some ports that were breaking  
given there
B> was some high level one you were expected to provide patches to fix  
them.


I'm working on them right now.


You should have worked on it *before* the patch breaking everything
landed, providing patches for the ports that were reported as broken,
and repeat until all the ports that were building before were building
again.

You should **not** have committed the patch to the src tree before all
those patches were created, and you should have committed all the
patches at once, preferably before committing the patch to the src tree.






People should...
No ports are broken on released version of FreeBSD. The broken ones are  
being fixed.
And a very good improvement of code has happened. Maybe a notice in  
UPDATING helps third-party people.

I don't see a real problem. Only progress.

Ronald.
___
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: libGL error: unable to load driver: swrast_dri.so

[Ronald Klop]

On Sat, 27 May 2017 18:44:37 +0200, bob prohaska   
wrote:



On an RPI2 www/epiphany finally compiled using portmaster. When started
it runs (somewhat)  but reports

libGL error: unable to load driver: swrast_dri.so

Web searches suggest it's something to do with an Nvidia driver, which
seems inapplicable to an RPI2.

Is there a workaround? /usr/ports are at 441746, /usr/src is at 318674.

Thanks for reading,

bob prohaska


AFAIK swrast is the Software Raster driver. So I don't think the link is  
with NVidia in your case.
I had the same error on my laptop with a Radeon driver (r600_dri.so) a  
while back, but don't see it anymore when I start a GL program. What I  
remember in my case the error was harmless. The driver was already loaded  
or something like that.
Do you experience actual errors or only the message, i.e. does the program  
run as expected?
I run the latest packages on amd64, but your ports tree is also quite  
up-to-date as far as I see.


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

port x11-wm/icewm does not have a pkg?

[Ronald Klop]

Hi,

I can't install a pkg of x11-wm/icewm. But I can't see in the port why. It  
seems to have a proper license GPLv2 and is distributable.


Any insights on this?

Regards,
Ronald.
___
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: reccomendation for a building architecture schematic diagram editor ?

[Ronald Klop]

On Thu, 03 May 2018 18:45:49 +0200, Miroslav Lachman <000.f...@quip.cz>  
wrote:



Julian H. Stacey wrote on 2018/05/03 14:54:

CC pruned, & 1 added as som thread commonality below ***
 Miroslav Lachman wrote:

The cad/freecad port has PORTNAME= FreeCAD in the Makefile, so the
package name is FreeCAD-0.17.13509.txz

Miroslav Lachman

 Thanks.
As these fail:
pkg search cad | grep -i free
pkg search CAD | grep -i free
pkg install FreeCAD-0.17.13509.txz
pkg install FreeCAD-0.17.13509
pkg install FreeCAD-0.17
pkg install FreeCAD-0
pkg install FreeCAD
& I am reaching the world with these 2 that produce the same
pkg search cad
pkg search CAD
&   pkg search exmh # exmh-2.8.0_1
pkg install exmh-2.8.0_1
ports/mail/exmh2/Makefile
PORTNAME=   exmh
PORTVERSION=2.8.0
PORTREVISION=   1
ports/cad/freecad/Makefile
PORTNAME=   FreeCAD
DISTVERSION=0.17.13509
 ***
Probably some packages are missing from the freebsd.org build system,  
as in

Subject: port x11-wm/icewm does not have a pkg?
These also fail
pkg search  icewm
pkg install icewm-1.3.8_3



What repository are you using?
Did you run pkg update -f?

The package is in official FreeBSD repo for 10 and 11:
http://pkg.freebsd.org/FreeBSD:10:amd64/latest/All/FreeCAD-0.17.13509.txz
http://pkg.freebsd.org/FreeBSD:11:amd64/latest/All/FreeCAD-0.17.13509.txz

Also in quaterly branch
http://pkg.freebsd.org/FreeBSD:10:amd64/quarterly/All/FreeCAD-0.17.12018_2.txz
http://pkg.freebsd.org/FreeBSD:11:amd64/quarterly/All/FreeCAD-0.17.12018_2.txz

pkg install FreeCAD shoul work. (I am not using official FreeBSD repo on  
any of our machines so I cannot test it now)


Miroslav Lachman



In the past we had portsmon which displayed if a port build or not.

http://portsmon.freebsd.org/portoverview.py?category=cad&portname=freecad

But is in maintenance for a while now. The maintainer mailed me (about a  
month ago) it will be back in Q2 probably.


I don't know of a similar site with the data of the current pkg build  
system.


Cheers,
Ronald.
___
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: port x11-wm/icewm does not have a pkg?

[Ronald Klop]

On Thu, 03 May 2018 17:16:16 +0200, Mateusz Piotrowski <0...@freebsd.org>  
wrote:



Hello,

On Thu, 03 May 2018 12:50:24 +0200
"Ronald Klop"  wrote:


I can't install a pkg of x11-wm/icewm. But I can't see in the port
why. It seems to have a proper license GPLv2 and is distributable.


It looks like it's simply broken because it does not compile probably
due to the switch to a C++11.

I've opened an issue on Bugzilla for this.[1]

It seems to require some minor fixes but I don't have time for this
unfortunatelly at the moment. You may look at those errors on your own.
Just download the ports[2] and then run

# cd /usr/ports/x11-wm/icewm
# make

If you would like to work on this issue and write some patches then I'm
ready to assist you.

Cheers,

Mateusz

[1]: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227951
[2]: https://www.freebsd.org/doc/handbook/ports-using.html



Thanks for your answer. I compiled in the meantime myself and saw the  
error.

I added a patch to the PR.

Regards,
Ronald.
___
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"