Re: Quarterly branch policy question

[Mathieu Arnold]

On Fri, Apr 27, 2018 at 04:38:14PM +, Lev Serebryakov wrote:
> 
>  I have question about Quarterly branch commits.
> 
>  Committers Guide says at 19.6.2
> (https://www.freebsd.org/doc/en/articles/committers-guide/ports.html#ports-qa-blanket):
> 
> 
> The following blanket approvals are in effect:
> ...
> 
> * Fixing shebangs, stripping installed libraries and binaries, and plist
> fixes.
> ...
> 
> Important:
> 
> No unauthorized commits can ever be made without approval of either
> Ports Security Team  or Ports Management Team
> .
> 
> 
>  I see contradiction here. Are such changes are pre-approved ("blanket
> approvals") or approval must be requested & gained?

There is a list of authorized things to do, and as people are usually
stupid and guess that they can go around if they like, something that
says after that list of authorized things that outside of that list, you
must get authorization.

>  Other question, whom should I ask for approval? I was said, that
> "portmgr is not responsible for approving merges, or direct commits, to
> the quarterly branches." in private message.
> 
>  Must shebang fix be approved by ports-secteam@? Really?

shebang fixes are covered in the blanket.

-- 
Mathieu Arnold


signature.asc
Description: PGP signature

Quarterly branch policy question

[Lev Serebryakov]

 I have question about Quarterly branch commits.

 Committers Guide says at 19.6.2
(https://www.freebsd.org/doc/en/articles/committers-guide/ports.html#ports-qa-blanket):


The following blanket approvals are in effect:
...

* Fixing shebangs, stripping installed libraries and binaries, and plist
fixes.
...

Important:

No unauthorized commits can ever be made without approval of either
Ports Security Team  or Ports Management Team
.


 I see contradiction here. Are such changes are pre-approved ("blanket
approvals") or approval must be requested & gained?

 Other question, whom should I ask for approval? I was said, that
"portmgr is not responsible for approving merges, or direct commits, to
the quarterly branches." in private message.

 Must shebang fix be approved by ports-secteam@? Really?

-- 
// Lev Serebryakov
___
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"

Problem with py36 "opt-1.pyc" files

[Christer Edwards]

There is an issue in the current (2018.3.0_1) sysutils/py-salt, specific to
py36. The "cpython-36.opt-1.pyc" files included in the pkg seem to contain
pre-patched files.

Any more experienced porters want to offer advice on how to fix this in the
port?

reproduce:
1. install py36-salt (>=2018.3.0)
2. start master/minion
3. error (/var/log/salt/{master,minion}

fix:
1. rm
/usr/local/lib/python3.6/site-packages/salt/grains/__pycache__/marathon.cpython-36.opt-1.pyc
/usr/local/lib/python3.6/site-packages/salt/grains/__pycache__/fx2.cpython-36.opt-1.pyc

I've never seen this before.

Cheers,
Christer
___
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 failes to build with poudriere, since 2018-04-05

[Steven Hartland]

Thanks for that does seem like your machine can readily reproduce in 
just a few seconds which is good. Here it usually takes days to trigger, 
which is why its been so hard to make any progress on isolating the 
issue; which its not clear if its go or kernel related.


Can you see if you can trigger the failure with:
ktrace -tfw+ -i -f ktrace-test.out ./test

On 27/04/2018 08:57, Bjarne wrote:

Hello Steve

The host machine is homebuilt with:
motherboard:  ASRock Z97 Pro3 - Z97Pro3
cpu:  Intel(R) Core(TM) i5-4460  CPU @ 3.20GHz
Ram: 32GB

poudriere is running on zfs.


So this is what I did:

Previously on your suggestions, I lowered the number af of cpu's to 1 
and was able to build a go version, meaning I have a go package.

Installing that version:

go version go1.10.1 freebsd/amd64
Just to test how to test, I tried your suggetions before patching 
anything.


with 4 cpu's.
go build main.go
go build -o test main.go

# build crash , can't build, core dump

# reducing to  1 cpu

# go build -o test main.go
# command-line-arguments
./main.go:15:13: undefined: syscall.ForkOnlyBSDTest


ok, now  patching to insert debug syscalls.

And your test program produces the attached log

Hope that helps.



On 27-04-2018 01:04, Steven Hartland wrote:

Thanks for the information, next question is what it the host machine?

As your currently unable to build go we may have to get a binary dist 
on the machine to start debugging, I can provide that if needed.


Once you have a working go installs you can try building and running 
the following:


The attached golang patch can be used to add new debug syscall, if 
you can build go from ports (try outside of poudriere).


Then you can compile main.go from a directory named test using "go 
build" and then from the same directory run the test.sh and lets see 
what you get?


    Regards
    Steve


On 26/04/2018 19:23, Bjarne wrote:

Hi Steven

Thanks for getting back on this.

The os is 11.1-RELEASE-p9  and the ports tree is HEAD.
The build machine is a virtual server ,
5120 M RAM
4 cpu
on top of  xen :
release    : 4.4.104-39-default
version    : #1 SMP Thu Jan 4 08:11:03 UTC 2018 (7db1912)


It seems I have a reliable test environment. I have just 
reconfigured to 4 cpus and tested a rebuild and got same error as 
before.

Anything i can do to assist in debugging?

Bear in mind I dont know anything of lang/go and am still a beginner 
regading poudriere.
I have frozen the build machine so it wont download new versions of 
anything.




On 26-04-2018 01:31, Steven Hartland wrote:
That happens very rarely, so rarely its been really hard to make 
any progress debugging it.


If you believe you have reliable reproduction case I'd be very 
interested in it.


One thing I noticed when re-reading your original post is that you 
say you tested on 11.1 but then your output mentions HEAD, are you 
running 11.1-RELEASE or 11-STABLE, if so what revision?


Also of interest is the hardware and related configuration?

    Regards
    Steve

On 25/04/2018 22:09, Derek (freebsd lists) wrote:

Ah, you'll note: fork/exec implicated here.

Looks like this guy strikes again:
https://github.com/golang/go/issues/15658

It pains me to say but Go on FreeBSD is (and has always been) 
broken.  Should be fine if you don't exec. Something that might 
help, is setting GOMAXPROCS=1.


Derek

On 18-04-25 07:45 AM, Steven Hartland wrote:

Builds fine on 11.1-RELEASE-p6 here:

[00:04:02] Committing packages to repository
[00:04:02] Removing old packages
[00:04:02] Built ports: lang/go
[ports11-1-multiplay] [2018-04-25_11h37m16s] [committing:] 
Queued: 1 Built: 1  Failed: 0  Skipped: 0 Ignored: 0  Tobuild: 
0   Time: 00:04:01
[00:04:02] Logs: 
/usr/local/poudriere/data/logs/bulk/ports11-1-multiplay/2018-04-25_11h37m16s 


[00:04:02] Cleaning up

svn info
Path: .
Working Copy Root Path: /usr/local/poudriere/ports/multiplay
URL: https://svn.freebsd.org/ports/head
Relative URL: ^/head
Repository Root: https://svn.freebsd.org/ports
Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
Revision: 468275
Node Kind: directory
Schedule: normal
Last Changed Author: tobik
Last Changed Rev: 468275
Last Changed Date: 2018-04-25 11:08:41 + (Wed, 25 Apr 2018)


 Regards
 Steve

On 25/04/2018 12:07, Bjarne wrote:
I got a job to rebuild all packages every night, but since 
2018-04-05 building /usr/ports/lang/go is failing.


Apparently 2018-04-05  some major changed was introduced, since 
331 pakackes was rebuilt. Not sure what it was, I saw nothing in 
UPATING.


Top of logfile:


Building lang/go

:snip





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








--
mvh,
Bjarne




--
mvh,
Bjarne


___
freebsd-ports@freebsd.org mailing list

Re: lang/go failes to build with poudriere, since 2018-04-05

[Bjarne]

Hello Steve

The host machine is homebuilt with:
motherboard:  ASRock Z97 Pro3 - Z97Pro3
cpu:  Intel(R) Core(TM) i5-4460  CPU @ 3.20GHz
Ram: 32GB

poudriere is running on zfs.


So this is what I did:

Previously on your suggestions, I lowered the number af of cpu's to 1 and was able to build a go 
version, meaning I have a go package.

Installing that version:

go version go1.10.1 freebsd/amd64
Just to test how to test, I tried your suggetions before patching anything.

with 4 cpu's.
go build main.go
go build -o test main.go

# build crash , can't build, core dump

# reducing to  1 cpu

# go build -o test main.go
# command-line-arguments
./main.go:15:13: undefined: syscall.ForkOnlyBSDTest


ok, now  patching to insert debug syscalls.

And your test program produces the attached log

Hope that helps.



On 27-04-2018 01:04, Steven Hartland wrote:

Thanks for the information, next question is what it the host machine?

As your currently unable to build go we may have to get a binary dist on the machine to start 
debugging, I can provide that if needed.


Once you have a working go installs you can try building and running the 
following:

The attached golang patch can be used to add new debug syscall, if you can build go from ports 
(try outside of poudriere).


Then you can compile main.go from a directory named test using "go build" and then from the same 
directory run the test.sh and lets see what you get?


    Regards
    Steve


On 26/04/2018 19:23, Bjarne wrote:

Hi Steven

Thanks for getting back on this.

The os is 11.1-RELEASE-p9  and the ports tree is HEAD.
The build machine is a virtual server ,
5120 M RAM
4 cpu
on top of  xen :
release    : 4.4.104-39-default
version    : #1 SMP Thu Jan 4 08:11:03 UTC 2018 (7db1912)


It seems I have a reliable test environment. I have just reconfigured to 4 cpus and tested a 
rebuild and got same error as before.

Anything i can do to assist in debugging?

Bear in mind I dont know anything of lang/go and am still a beginner regading 
poudriere.
I have frozen the build machine so it wont download new versions of anything.



On 26-04-2018 01:31, Steven Hartland wrote:

That happens very rarely, so rarely its been really hard to make any progress 
debugging it.

If you believe you have reliable reproduction case I'd be very interested in it.

One thing I noticed when re-reading your original post is that you say you tested on 11.1 but 
then your output mentions HEAD, are you running 11.1-RELEASE or 11-STABLE, if so what revision?


Also of interest is the hardware and related configuration?

    Regards
    Steve

On 25/04/2018 22:09, Derek (freebsd lists) wrote:

Ah, you'll note: fork/exec implicated here.

Looks like this guy strikes again:
https://github.com/golang/go/issues/15658

It pains me to say but Go on FreeBSD is (and has always been) broken.  Should be fine if you 
don't exec.  Something that might help, is setting GOMAXPROCS=1.


Derek

On 18-04-25 07:45 AM, Steven Hartland wrote:

Builds fine on 11.1-RELEASE-p6 here:

[00:04:02] Committing packages to repository
[00:04:02] Removing old packages
[00:04:02] Built ports: lang/go
[ports11-1-multiplay] [2018-04-25_11h37m16s] [committing:] Queued: 1 Built: 1  Failed: 0  
Skipped: 0  Ignored: 0 Tobuild: 0   Time: 00:04:01

[00:04:02] Logs: 
/usr/local/poudriere/data/logs/bulk/ports11-1-multiplay/2018-04-25_11h37m16s
[00:04:02] Cleaning up

svn info
Path: .
Working Copy Root Path: /usr/local/poudriere/ports/multiplay
URL: https://svn.freebsd.org/ports/head
Relative URL: ^/head
Repository Root: https://svn.freebsd.org/ports
Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
Revision: 468275
Node Kind: directory
Schedule: normal
Last Changed Author: tobik
Last Changed Rev: 468275
Last Changed Date: 2018-04-25 11:08:41 + (Wed, 25 Apr 2018)


 Regards
 Steve

On 25/04/2018 12:07, Bjarne wrote:
I got a job to rebuild all packages every night, but since 2018-04-05 building 
/usr/ports/lang/go is failing.


Apparently 2018-04-05  some major changed was introduced, since 331 pakackes was rebuilt. Not 
sure what it was, I saw nothing in UPATING.


Top of logfile:


Building lang/go

:snip





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







--
mvh,
Bjarne




--
mvh,
Bjarne

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

FreeBSD ports you maintain which are out of date

[portscout]

Dear port maintainer,

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

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

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


Port| Current version | New version
+-+
databases/postgresql-plv8js | 1.4.8   | v2.3.3
+-+
lang/duktape| 2.2.0   | 2.2.1
+-+
sysutils/freefilesync   | 9.8 | 10.0
+-+


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

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

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