Re: Go ports fail with fs violation: Error: Filesystem touched during build:,extra: root/.cache

2018-02-28 Thread Yuri 

On 02/28/18 13:15, Antoine Brodin wrote:

Both examples do not use MAKE_ENV.



Maybe all of them should be changed to use MAKE_ENV, and if it will also 
include XDG_DATA_HOME, the problem wil be gone?



Yuri


___
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: Go ports fail with fs violation: Error: Filesystem touched during build:,extra: root/.cache

2018-02-28 Thread Antoine Brodin 
On Wed, Feb 28, 2018 at 10:10 PM, Yuri  wrote:
> On 02/28/18 13:07, Antoine Brodin wrote:
>>
>> No,  HOME is already enough to fix the violation.  The problem is that
>> those ports/go.mk do fancy things and do not respect BUILD_ENV.
>
>
>
> Both examples don't use go.mk and still fail.

Both examples do not use MAKE_ENV.

Antoine
___
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: Go ports fail with fs violation: Error: Filesystem touched during build:,extra: root/.cache

2018-02-28 Thread Yuri 

On 02/28/18 13:07, Antoine Brodin wrote:

No,  HOME is already enough to fix the violation.  The problem is that
those ports/go.mk do fancy things and do not respect BUILD_ENV.



Both examples don't use go.mk and still fail.


Yuri

___
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: Go ports fail with fs violation: Error: Filesystem touched during build:,extra: root/.cache

2018-02-28 Thread Antoine Brodin 
On Wed, Feb 28, 2018 at 9:57 PM, Yuri  wrote:
> On 02/28/18 00:35, Antoine Brodin wrote:
>>
>> Ports that use CONFIGURE_ENV / MAKE_ENV have this violation issue with
>> HOME=${WRKDIR}.
>> Maybe this should be added to GO_ENV and go ports should respect more
>> this environment.
>
>
>
> PGo also tries "XDG_CACHE_HOME" when "GOCACHE" isn't defined.
>
> Mk/ does define "XDG_DATA_HOME" in MAKE_ENV.
>
> Maybe the right solution is to just add "XDG_CACHE_HOME" there?

No,  HOME is already enough to fix the violation.  The problem is that
those ports/go.mk do fancy things and do not respect BUILD_ENV.

Antoine
___
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: Go ports fail with fs violation: Error: Filesystem touched during build:,extra: root/.cache

2018-02-28 Thread Yuri 

On 02/28/18 00:35, Antoine Brodin wrote:

Ports that use CONFIGURE_ENV / MAKE_ENV have this violation issue with
HOME=${WRKDIR}.
Maybe this should be added to GO_ENV and go ports should respect more
this environment.



PGo also tries "XDG_CACHE_HOME" when "GOCACHE" isn't defined.

Mk/ does define "XDG_DATA_HOME" in MAKE_ENV.

Maybe the right solution is to just add "XDG_CACHE_HOME" there?


Yuri

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

www/waterfox: Why is it deprecated?

2018-02-28 Thread Naram Qashat 

Hi Jan,

I was wondering why www/waterfox currently has a deprecation notice for 
2018-03-20 of "Temporary experiment". Are there no plans to keep 
Waterfox in the ports tree as an alternative to Firefox? The project 
appears to be an active fork of Firefox.


Thanks,
Naram Qashat
___
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: Problem with old files in freebsd-update/files

2018-02-28 Thread Kurt Jaeger 
Hi!

> > And if I want to clean them up, I do:
> > 
> > cd /var/db
> > mv freebsd-update fbsd-up-old
> > mkdir freebsd-update
> > chmod 700 freebsd-update
> > rm -rf fbsd-up-old
> 
>   Out of curiosity, why not just:
> 
> ~ # rm -rf /var/db/freebsd-update/*
> 
>   Is there a reason you're moving the directory and creating a new, empty
> one?

Sometimes, depending on the storage media below, it takes time
to remove the old directory. So it's faster that way and both
the removal and the -update can be done in parallel.

-- 
p...@opsec.eu+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"

Re: Problem with old files in freebsd-update/files

2018-02-28 Thread Mathieu Arnold 
On Tue, Feb 27, 2018 at 11:48:31PM +, Janky Jay, III wrote:
> Hello,
> 
> On 02/27/2018 01:31 PM, Kurt Jaeger wrote:
> > Hi!
> > 
> >> FreeBSD 10.4-RELEASE-p3 (GENERIC) #0: Tue Nov 14 09:06:09 UTC 2017
> >>
> >> I wrote about this before, and was told to use "pkg clean" to clean up old 
> >> files which I now do every week, but...
> > 
> > I have those files in /var/db/freebsd-update/
> > 
> > And if I want to clean them up, I do:
> > 
> > cd /var/db
> > mv freebsd-update fbsd-up-old
> > mkdir freebsd-update
> > chmod 700 freebsd-update
> > rm -rf fbsd-up-old
> 
>   Out of curiosity, why not just:
> 
> ~ # rm -rf /var/db/freebsd-update/*
> 
>   Is there a reason you're moving the directory and creating a new, empty
> one?

From time to time, there are tens of thousands of files directly in
this directory, and using * ends up saying that the argument list is too
long.


-- 
Mathieu Arnold


signature.asc
Description: PGP signature

FreeBSD ports you maintain which are out of date

2018-02-28 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
+-+
editors/cooledit| 3.17.17 | 3.17.20
+-+
emulators/mame  | 0.166   | mame0195
+-+
emulators/mess  | 0.166   | mame0195
+-+
graphics/opencv | 2.4.13.1| 3.4.1
+-+
graphics/opencv-core| 2.4.13.1| 3.4.1
+-+
graphics/opencv-java| 2.4.13.1| 3.4.1
+-+
graphics/py-opencv  | 2.4.13.1| 3.4.1
+-+


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

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

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

Re: Go ports fail with fs violation: Error: Filesystem touched during build:,extra: root/.cache

2018-02-28 Thread Antoine Brodin 
On Wed, Feb 28, 2018 at 8:35 AM, Antoine Brodin  wrote:
> On Wed, Feb 28, 2018 at 12:12 AM, Yuri  wrote:
>> For example:
>>
>> http://package21.nyi.freebsd.org/data/111amd64-default-qat/462883/logs/errors/gogs-0.11.34_2.log
>>
>> http://package21.nyi.freebsd.org/data/111amd64-default-qat/462883/logs/errors/cryptoballot-g20170928.log
>
> Ports that use CONFIGURE_ENV / MAKE_ENV have this violation issue with
^^ fixed
> HOME=${WRKDIR}.
> Maybe this should be added to GO_ENV and go ports should respect more
> this environment.
>
> Antoine
___
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: Go ports fail with fs violation: Error: Filesystem touched during build:,extra: root/.cache

2018-02-28 Thread Antoine Brodin 
On Wed, Feb 28, 2018 at 12:12 AM, Yuri  wrote:
> For example:
>
> http://package21.nyi.freebsd.org/data/111amd64-default-qat/462883/logs/errors/gogs-0.11.34_2.log
>
> http://package21.nyi.freebsd.org/data/111amd64-default-qat/462883/logs/errors/cryptoballot-g20170928.log

Ports that use CONFIGURE_ENV / MAKE_ENV have this violation issue with
HOME=${WRKDIR}.
Maybe this should be added to GO_ENV and go ports should respect more
this environment.

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