Re: @sample surprises (dns/knot-resolver)

2021-04-12 Thread Baptiste Daroussin
On Mon, Apr 12, 2021 at 11:34:11AM +0200, Adriaan de Groot wrote:
> As prep-work for CMake updates I locally "exp-run" all the ports that use 
> CMake. I use poudriere for this, with the `-t` flag to test each port.
> 
> dns/knot-resolver fails to package like that, with this error:
> 
> ===
> ===>  Building package for knot-resolver-5.3.0
> @sample with 1 single argument expect ".sample" extension
> pkg-static: Fail to apply keyword 'sample'
> *** Error code 1
> 
> 
> The same failure occurs on the build cluster. I checked the porter's handbook 
> and it describes 1- and 2-argument forms of @sample, but neither seemed 
> applicable here without digging into the port itself to rename the installed 
> configuration file. What's the right approach here?
> 
> (CC'ed maintainer and last committer; I'm going to locally stop building this 
> one in preparation of a CMake update)


This makes me happy to have implemented this prepacking tests in pkg for
keywords.

The port is clearly buggy here, the right approach is to move the
%%ETCDIR%%/kresd.conf into %%ETCDIR%%/kresd.conf.sample in the post-install
And change the plist

Best regards,
Bapt
___
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: Portsnap restoration after Git migration

2021-04-12 Thread Bob Eager
On Mon, 12 Apr 2021 16:02:41 -0400
Ed Maste  wrote:

> Colin (cperciva) and I are making good progress on the portsnap build
> infrastructure Git migration. I'll follow up when it is back in
> operation.

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"


Portsnap restoration after Git migration

2021-04-12 Thread Ed Maste
Colin (cperciva) and I are making good progress on the portsnap build
infrastructure Git migration. I'll follow up when it is back in
operation.
___
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"


vim for FreeBSD11/libsysinfo

2021-04-12 Thread Akihiko HAYASHI

Hi, all

editors/vim fails to build on FreeBSD 11 that libsysinfo installed

memline.c(vim) uses macro HAVE_SYSINFO_UPTIME, then
HAVE_SYSINFO_UPTIME should be removed from ${WRKSRC}/src/auto/config.h

this patch is here: 
https://gist.github.com/a-rin/9454f9913d25ea03f54364384da47a7b

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


Re: @sample surprises (dns/knot-resolver)

2021-04-12 Thread Mathieu Arnold
On Mon, Apr 12, 2021 at 11:34:11AM +0200, Adriaan de Groot wrote:
> As prep-work for CMake updates I locally "exp-run" all the ports that use 
> CMake. I use poudriere for this, with the `-t` flag to test each port.
> 
> dns/knot-resolver fails to package like that, with this error:
> 
> ===
> ===>  Building package for knot-resolver-5.3.0
> @sample with 1 single argument expect ".sample" extension
> pkg-static: Fail to apply keyword 'sample'
> *** Error code 1
> 
> 
> The same failure occurs on the build cluster. I checked the porter's handbook 
> and it describes 1- and 2-argument forms of @sample, but neither seemed 
> applicable here without digging into the port itself to rename the installed 
> configuration file. What's the right approach here?
> 
> (CC'ed maintainer and last committer; I'm going to locally stop building this 
> one in preparation of a CMake update)

The best is probably to fix the plist and use two arguments.

-- 
Mathieu Arnold


signature.asc
Description: PGP signature


Re: chromium-89.0.4389.114_1 sign-in feature unavailable?

2021-04-12 Thread Dimitry Andric
On 12 Apr 2021, at 00:24, Jonathan Chen  wrote:
> 
> On Mon, 12 Apr 2021 at 09:51, Dimitry Andric  wrote:
>> 
>> On 11 Apr 2021, at 21:57, Jonathan Chen  wrote:
>>> 
>>> I recently updated to chromium-89.0.4389.114_1, and it now appears
>>> that the browser sync sign-in feature is not available anymore? Or did
>>> I miss something?
>> 
>> Yes, apparently you missed this:
>> 
>> https://blog.chromium.org/2021/01/limiting-private-api-availability-in.html
>> 
>> It was all over the news... :)
> 
> I must not have the right feeds...
> 
> Is the FreeBSD port of chrome considered a "third-party Chromium based
> browser"?

I don't think Google ever officially released a FreeBSD build of the
proprietary Chrome application. They do have official Linux builds, of
course, and it might just be possible to run these under the
Linuxulator, but your mileage may very, as they say.

But yeah, Google has again made a lot of people very unhappy with this
decision. Please draw your own conclusions. :)

-Dimitry



signature.asc
Description: Message signed with OpenPGP


Re: Deprecation of portsnap (was: Proposed ports git transition schedule)

2021-04-12 Thread Michael Gmelin


> On 12. Apr 2021, at 13:12, Peter Jeremy via freebsd-ports 
>  wrote:
> 
> On 2021-Apr-11 14:27:27 +0200, Helge Oldach  wrote:
>> Peter Jeremy via freebsd-ports wrote on Sun, 11 Apr 2021 00:52:11 +0200 
>> (CEST):
>>> Following the SVN to GIT migration, portsnap is now the only practical
>>> way to use ports on a low-memory system.  I've done some experiments
>>> and standard git has a 2GB working set to checkout a ports tree.
>> 
>> However checking out is a one-time action with ports as there is only
>> one branch (switching frequently between main and quarterly is probably
>> not very sensible on a limited machine). git pull is significantly more
>> lightweight, I've just seen some 200M RSS. That should work well even on
>> a 512M machine. Probably much better than gitup in constrained memory?
> 
> Except that git will arbitrarily and randomly decide that it needs to
> run "gc" -

See https://git-scm.com/docs/git-gc for an explanation of how git decides when 
to run gc and how you can control it (e.g., by setting gc.auto to 0).

-m

> which is similarly extravagant in memory usage.  Last time
> I found one running, it thrashed that poor VM for 3 days.
> 
> Ignoring that, a "git up -ff" on a ports tree peaks with 2×1GB processes,
> though it looks like the working set size might only be ~350MB.
> 
> -- 
> Peter Jeremy
___
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: Deprecation of portsnap (was: Proposed ports git transition schedule)

2021-04-12 Thread Peter Jeremy via freebsd-ports
On 2021-Apr-11 14:27:27 +0200, Helge Oldach  wrote:
>Peter Jeremy via freebsd-ports wrote on Sun, 11 Apr 2021 00:52:11 +0200 (CEST):
>> Following the SVN to GIT migration, portsnap is now the only practical
>> way to use ports on a low-memory system.  I've done some experiments
>> and standard git has a 2GB working set to checkout a ports tree.
>
>However checking out is a one-time action with ports as there is only
>one branch (switching frequently between main and quarterly is probably
>not very sensible on a limited machine). git pull is significantly more
>lightweight, I've just seen some 200M RSS. That should work well even on
>a 512M machine. Probably much better than gitup in constrained memory?

Except that git will arbitrarily and randomly decide that it needs to
run "gc" - which is similarly extravagant in memory usage.  Last time
I found one running, it thrashed that poor VM for 3 days.

Ignoring that, a "git up -ff" on a ports tree peaks with 2×1GB processes,
though it looks like the working set size might only be ~350MB.

-- 
Peter Jeremy


signature.asc
Description: PGP signature


fs_violations for ports that build using python tools

2021-04-12 Thread Adriaan de Groot
I build many ports in poudriere with the `-t` (test port) flag. Ports that use 
Python-based tools tend to fail with a fs_violation. For instance, FreeCAD:

=>> Checking for filesystem violations... done
=>> Error: Filesystem touched during build:
extra: usr/local/lib/python3.7/site-packages/shiboken2/__pycache__
extra: usr/local/lib/python3.7/site-packages/shiboken2/files.dir/
shibokensupport/__pycache__
extra: usr/local/lib/python3.7/site-packages/shiboken2/files.dir/
shibokensupport/signature/lib/__pycache__

or nextpnr:

=>> Checking for filesystem violations... done
=>> Error: Filesystem touched during build:
extra: usr/local/share/trellis/util/common/__pycache__
extra: usr/local/share/trellis/timing/util/__pycache__

On the build cluster, these don't seem to cause problems. Note that these 
pycache files are **not** from the port being built, but from other, python-
based, tools that are run as part of the build: trellis is a BUILD_DEPENDS for 
nextpnr.

What can I do to resolve this kind of build failure? I'd like to avoid false-
failures because they mask and confuse local exp-runs for (say) CMake updates.

[ade]

signature.asc
Description: This is a digitally signed message part.


@sample surprises (dns/knot-resolver)

2021-04-12 Thread Adriaan de Groot
As prep-work for CMake updates I locally "exp-run" all the ports that use 
CMake. I use poudriere for this, with the `-t` flag to test each port.

dns/knot-resolver fails to package like that, with this error:

===
===>  Building package for knot-resolver-5.3.0
@sample with 1 single argument expect ".sample" extension
pkg-static: Fail to apply keyword 'sample'
*** Error code 1


The same failure occurs on the build cluster. I checked the porter's handbook 
and it describes 1- and 2-argument forms of @sample, but neither seemed 
applicable here without digging into the port itself to rename the installed 
configuration file. What's the right approach here?

(CC'ed maintainer and last committer; I'm going to locally stop building this 
one in preparation of a CMake update)

signature.asc
Description: This is a digitally signed message part.


INDEX now builds successfully on 11.x

2021-04-12 Thread Ports Index build


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


FreeBSD ports you maintain which are out of date

2021-04-12 Thread portscout
Dear port maintainer,

The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
deskutils/copyq | 3.13.0  | v4.0.0
+-+
math/wxmaxima   | 20.04.0 | 
version-21.04.0
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

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


INDEX build failed for 11.x

2021-04-12 Thread Ports Index build
INDEX build failed with errors:
Generating INDEX-11 - please wait..--- describe.accessibility ---
--- describe.arabic ---
--- describe.archivers ---
--- describe.astro ---
--- describe.audio ---
--- describe.benchmarks ---
--- describe.biology ---
--- describe.cad ---
--- describe.chinese ---
--- describe.comms ---
--- describe.converters ---
--- describe.databases ---
--- describe.deskutils ---
--- describe.devel ---
--- describe.dns ---
--- describe.editors ---
--- describe.emulators ---
--- describe.finance ---
--- describe.french ---
--- describe.ftp ---
[...]
--- describe.print ---
--- describe.russian ---
--- describe.science ---
--- describe.security ---
--- describe.shells ---
--- describe.sysutils ---
--- describe.textproc ---
--- describe.ukrainian ---
--- describe.vietnamese ---
--- describe.www ---
--- describe.x11 ---
--- describe.x11-clocks ---
--- describe.x11-drivers ---
--- describe.x11-fm ---
--- describe.x11-fonts ---
--- describe.x11-servers ---
--- describe.x11-themes ---
--- describe.x11-toolkits ---
--- describe.x11-wm ---
 Done.
make_index: /home/indexbuild/tindex/ports/games/pink-pony: no entry for 
/home/indexbuild/tindex/ports/graphics/ilmbase

Committers on the hook:
mand...@freebsd.org swi...@freebsd.org w...@freebsd.org 

Most recent Git update was:
astro/p5-Astro-satpass/Makefile
astro/p5-Astro-satpass/distinfo
deskutils/syncthingtray/Makefile
deskutils/syncthingtray/distinfo
devel/liblouis/Makefile
devel/liblouis/distinfo
devel/liblouis/pkg-plist
games/wesnoth/Makefile
games/wesnoth/distinfo
games/wesnoth/pkg-plist
___
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"