Re: replacement for lang/phantomjs [deprecated]

[Steven Hartland]

Pretty sure chrome has a headless mode now, perhaps you could use that.

On 22/05/2019 12:39, dangerwillrobinsondan...@gmail.com wrote:





On May 22, 2019, at 19:33, Kurt Jaeger  wrote:

Hi!


The port lang/phantomjs is marked as deprecated / expired 2019-05-15. Is
there any alternative in the ports tree? I searched the net and found
https://slimerjs.org but it is not in the ports tree. (I don't have a
skill to port it and maintain it myself)

One of my clients is using phantomjs thru some webapplication so I need
to find some replacement.

I have a vague guess that selenium does something similar.

https://docs.seleniumhq.org/

Not really.
phantomjs is like a headless browser client.
Selenium is web automation API and now a W3C standard implemented by browsers 
to support it. Version 3+
Earlier versions worked with older browsers via plugins or extensions but no 
more, in part due to security issues and in part because W3C.

PhantomJS was often like a generic browser space you could test inside of and 
it did have Selenium bindings.


--
p...@opsec.eu+49 171 3101372One year 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: lang/go failes to build with poudriere, since 2018-04-05

[Steven Hartland]

Yes thanks, sorry its taken a while to get round to looking at this; I 
didn't get the ktrace output file, only the log file you sent attached 
on the 27th.


    Regards
    Steve

On 28/04/2018 06:57, Bjarne wrote:

Hi Steven

I trust you have recieved the logfiles.
let me know if you need more tests.



On 27-04-2018 10:32, Steven Hartland wrote:
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

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

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
https://lists

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

[Steven Hartland]

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


--- /dev/null   2017-03-24 16:44:00.0 +
+++ src/syscall/exec_bsd_debug.go   2017-03-15 16:28:55.0 +
@@ -0,0 +1,41 @@
+// +build darwin dragonfly freebsd netbsd openbsd
+
+package syscall
+
+func ForkOnlyBSDTest() (err error) {
+   var r1 uintptr
+   var pid int
+   var err1 Errno
+   var wstatus WaitStatus
+
+   ForkLock.Lock()
+   runtime_BeforeFork()
+
+   r1, _, err1 = RawSyscall(SYS_FORK, 0, 0, 0)
+   if err1 != 0 {
+   runtime_AfterFork()
+   ForkLock.Unlock()
+   return err1
+   }
+
+   if r1 == 0 {
+   // in child, die die die my darling
+   for {
+   RawSyscall(SYS_EXIT, 253, 0, 0)
+   }
+   }
+
+   runtime_AfterFork()
+   ForkLock.Unlock()
+
+   pid = int(r1)
+
+   // Prime directive, exterminate
+   // Whatever stands left
+   _, err = Wait4(pid, , 0, nil)
+   for err == EINTR {
+   _, err = Wait4(pid, , 0, nil)
+   }
+
+   return
+}
#!/bin/sh

rm -f test.log
while true; do 
echo " NEW RUN $(date) "
echo
#time sh -c 'export GOGC=5; export GODEBUG=gctrace=2,schedtrace=100; 
./test'
#time sh -c 'export GOGC=5; ./test'
#time sh -c 'export GOGC=5; export GODEBUG=gcstackbarrierall=

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

[Steven Hartland]

That will just slow things down, its not a fix.

If you want to try its just an environment variable that needs to set 
before you run the app

e.g.
setenv GOMAXPROCS 1
./my-go-app

If you could have a look at my other reply and answer the questions 
there that would be appreciated.


    Regards
    Steve

On 26/04/2018 17:08, Bjarne wrote:

Hi Derek

Thank you very much for replying. it seems you hit it right on target!

Unfortunately I dont know anything about go, but it is a requirement 
of sysutils/beats. 
<http://portsmon.freebsd.org/portoverview.py?category=sysutils=beats>


Googling around i can see GOMAXPROCS is something with max number of 
cpu's used.
Since i dont know where to set that parameter and the fact i am 
working with a virtual environment, I reduced the numbe of cpu's  from 
4 to 1  on the build machine.

Now go is building and all is well again.

Where would I set GOMAXPROCS=1?
I might want to go back to 4 cpu's again.



On 25-04-2018 23: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




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

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

[Steven Hartland]

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

build started at Thu Apr  5 03:04:07 UTC 2018
port directory: /usr/ports/lang/go
package name: go-1.10.1,1
building for: FreeBSD freebsd_11-1-HEAD-job-03 11.1-RELEASE-p9 
FreeBSD 11.1-RELEASE-p9 amd64

maintained by: jlaff...@freebsd.org
Makefile ident:  $FreeBSD: head/lang/go/Makefile 466249 
2018-04-02 18:58:11Z jlaffaye $

Poudriere version: 3.2.6
Host OSVERSION: 1101001
Jail OSVERSION: 1101001

actually  build fails both on freebsd 10.3 and 11.1

Running poudriere testport -j freebsd_11-1 -p HEAD -i -o lang/go :


===>
=== 


=>> Recording filesystem state for prebuild... done
===
===>   go-1.10.1,1 depends on package: go14>=1.4 - found
===>  Configuring for go-1.10.1,1
=== 


===
===>  Building for go-1.10.1,1
cd /wrkdirs/usr/ports/lang/go/work/go/src && 
GOROOT=/wrkdirs/usr/ports/lang/go/work/go GOROOT_FINAL=/usr/local/go 
GOROOT_BOOTSTRAP=/usr/local/go14 GOBIN= GOARCH=amd64 GOOS=freebsd 
GO386=  /bin/sh make.bash

-ap: not found
go: not found
Building Go cmd/dist using /usr/local/go14.
Building Go toolchain1 using /usr/local/go14.
Building Go bootstrap cmd/go (go_bootstrap) using Go toolchain1.
Building Go toolchain2 using go_bootstrap and Go toolchain1.
runtime: gp: gp=0xc420499380, goid=38, gp->atomicstatus=2
runtime:  g:  g=0xc42c00, goid=0,  g->atomicstatus=0
fatal error: bad g->status in ready

runtime stack:
runtime.throw(0x6f776b, 0x16)
    /usr/local/go/src/runtime/panic.go:616 +0x81
runtime.ready(0xc420499380, 0x5, 0xc420499201)
    /usr/local/go/src/runtime/proc.go:601 +0x27b
runtime.goready.func1()
    /usr/local/go/src/runtime/proc.go:302 +0x38
runtime.systemstack(0x0)
    /usr/local/go/src/runtime/asm_amd64.s:409 +0x79
runtime.mstart()
    /usr/local/go/src/runtime/proc.go:1175

goroutine 37 [running]:
runtime.systemstack_switch()
    /usr/local/go/src/runtime/asm_amd64.s:363 fp=0xc4204a06c0 
sp=0xc4204a06b8 pc=0x450c00

runtime.goready(0xc420499380, 0x5)
    /usr/local/go/src/runtime/proc.go:301 +0x4b fp=0xc4204a06f0 
sp=0xc4204a06c0 pc=0x42a74b

runtime.readyWithTime(0xc4201a4c00, 0x5)
    /usr/local/go/src/runtime/sema.go:83 +0x41 fp=0xc4204a0710 
sp=0xc4204a06f0 pc=0x43a071

runtime.semrelease1(0x8885e4, 0x0)
    /usr/local/go/src/runtime/sema.go:194 +0x12d fp=0xc4204a0768 
sp=0xc4204a0710 pc=0x43a54d

sync.runtime_Semrelease(0x8885e4, 0xc4204a0700)
    /usr/local/go/src/runtime/sema.go:66 +0x34 fp=0xc4204a0788 
sp=0xc4204a0768 pc=0x439f84

sync.(*Mutex).Unlock(0x8885e0)
    /usr/local/go/src/sync/mutex.go:201 +0x75 fp=0xc4204a07b0 
sp=0xc4204a0788 pc=0x4674d5

sync.(*RWMutex).Unlock(0x8885e0)
    /usr/local/go/src/sync/rw

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

[Steven Hartland]

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

build started at Thu Apr  5 03:04:07 UTC 2018
port directory: /usr/ports/lang/go
package name: go-1.10.1,1
building for: FreeBSD freebsd_11-1-HEAD-job-03 11.1-RELEASE-p9 FreeBSD 
11.1-RELEASE-p9 amd64

maintained by: jlaff...@freebsd.org
Makefile ident:  $FreeBSD: head/lang/go/Makefile 466249 2018-04-02 
18:58:11Z jlaffaye $

Poudriere version: 3.2.6
Host OSVERSION: 1101001
Jail OSVERSION: 1101001

actually  build fails both on freebsd 10.3 and 11.1

Running poudriere testport -j freebsd_11-1 -p HEAD -i -o lang/go :


===
=== 


=>> Recording filesystem state for prebuild... done
===
===>   go-1.10.1,1 depends on package: go14>=1.4 - found
===>  Configuring for go-1.10.1,1
=== 


===
===>  Building for go-1.10.1,1
cd /wrkdirs/usr/ports/lang/go/work/go/src && 
GOROOT=/wrkdirs/usr/ports/lang/go/work/go GOROOT_FINAL=/usr/local/go  
GOROOT_BOOTSTRAP=/usr/local/go14 GOBIN= GOARCH=amd64 GOOS=freebsd  
GO386=  /bin/sh make.bash

-ap: not found
go: not found
Building Go cmd/dist using /usr/local/go14.
Building Go toolchain1 using /usr/local/go14.
Building Go bootstrap cmd/go (go_bootstrap) using Go toolchain1.
Building Go toolchain2 using go_bootstrap and Go toolchain1.
runtime: gp: gp=0xc420499380, goid=38, gp->atomicstatus=2
runtime:  g:  g=0xc42c00, goid=0,  g->atomicstatus=0
fatal error: bad g->status in ready

runtime stack:
runtime.throw(0x6f776b, 0x16)
    /usr/local/go/src/runtime/panic.go:616 +0x81
runtime.ready(0xc420499380, 0x5, 0xc420499201)
    /usr/local/go/src/runtime/proc.go:601 +0x27b
runtime.goready.func1()
    /usr/local/go/src/runtime/proc.go:302 +0x38
runtime.systemstack(0x0)
    /usr/local/go/src/runtime/asm_amd64.s:409 +0x79
runtime.mstart()
    /usr/local/go/src/runtime/proc.go:1175

goroutine 37 [running]:
runtime.systemstack_switch()
    /usr/local/go/src/runtime/asm_amd64.s:363 fp=0xc4204a06c0 
sp=0xc4204a06b8 pc=0x450c00

runtime.goready(0xc420499380, 0x5)
    /usr/local/go/src/runtime/proc.go:301 +0x4b fp=0xc4204a06f0 
sp=0xc4204a06c0 pc=0x42a74b

runtime.readyWithTime(0xc4201a4c00, 0x5)
    /usr/local/go/src/runtime/sema.go:83 +0x41 fp=0xc4204a0710 
sp=0xc4204a06f0 pc=0x43a071

runtime.semrelease1(0x8885e4, 0x0)
    /usr/local/go/src/runtime/sema.go:194 +0x12d fp=0xc4204a0768 
sp=0xc4204a0710 pc=0x43a54d

sync.runtime_Semrelease(0x8885e4, 0xc4204a0700)
    /usr/local/go/src/runtime/sema.go:66 +0x34 fp=0xc4204a0788 
sp=0xc4204a0768 pc=0x439f84

sync.(*Mutex).Unlock(0x8885e0)
    /usr/local/go/src/sync/mutex.go:201 +0x75 fp=0xc4204a07b0 
sp=0xc4204a0788 pc=0x4674d5

sync.(*RWMutex).Unlock(0x8885e0)
    /usr/local/go/src/sync/rwmutex.go:132 +0x7e fp=0xc4204a07e0 
sp=0xc4204a07b0 pc=0x46824e
syscall.forkExec(0xc4202f0440, 0x3d, 0xc4202aa1e0, 0x2, 0x2, 
0xc4204a09d8, 0x20, 0x0, 0xc4200aa5a0)
    /usr/local/go/src/syscall/exec_unix.go:199 +0x3e1 
fp=0xc4204a0900 sp=0xc4204a07e0 pc=0x46c031
syscall.StartProcess(0xc4202f0440, 0x3d, 0xc4202aa1e0, 0x2, 0x2, 
0xc4204a09d8, 0x2, 0x4, 0x0, 0x0)
    /usr/local/go/src/syscall/exec_unix.go:241 +0x64 
fp=0xc4204a0958 sp=0xc4204a0900 pc=0x46c484
os.startProcess(0xc4202f0440, 0x3d, 0xc4202aa1e0, 0x2, 0x2, 
0xc4204a0b80, 0xc420403400, 0x3e, 0x3e)
    /usr/local/go/src/os/exec_posix.go:46 +0x1f1 fp=0xc4204a0a30 
sp=0xc4204a0958 pc=0x48ce21
os.StartProcess(0xc4202f0440, 0x3d, 0xc4202aa1e0, 0x2, 0x2, 
0xc4204a0b80, 0x0, 0x0, 0x1)
    /usr/local/go/src/os/exec.go:102 +0x7c fp=0xc4204a0a88 
sp=0xc4204a0a30 pc=0x48c93c

os/exec.(*Cmd).Start(0xc4201809a0, 

Re: Mono 5.2 patch and DotNet Core 2 update

[Steven Hartland]

You want make makesum not make checksum to rebuild the distinfo file

On Wed, 10 Jan 2018 at 19:43, Romain Tartière  wrote:

> On Wed, Jan 10, 2018 at 08:55:45AM -0800, Russell Haley wrote:
> > I'm getting size and checksum errors for the file
> > dotnet-roslyn-322bd5b_GH0.tar.gz. This shouldn't be an issue: I
> > changed the size of the file in distinfo from 22058493 to the actual
> > size I received of 22058637 in order to make it build. My expectation
> > is that I should then run make checksum to fix the distinfo file
> > correctly. I run sudo make checksum and the target goes into an
> > infinite loop downloading the file, deciding it doesn't match the
> > checksum and then downloading it again. WTH?
>
> Since there are checksums, the ports systems must be checking them when
> downloading…  and since the checksum does not match, the download is
> assumed to have failed…  I guess you can solve this chicken-and-egg
> problem, vy simply removing the existing distinfo file.
>
> The actual files checksums will then be written to distinfo. You can
> `svn diff` to confirm only the expected files have been touched ;-)
>
> Regards,
> Romain
>
> --
> Romain Tartière   http://people.FreeBSD.org/~romain/
> pgp: 8234 9A78 E7C0 B807 0B59  80FF BA4D 1D95 5112 336F (ID: 0x5112336F)
> (plain text =non-HTML= PGP/GPG encrypted/signed e-mail much appreciated)
>
___
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: Last flavorless revision?

[Steven Hartland]

On 05/12/2017 08:13, Mathieu Arnold wrote:

Le 04/12/2017 à 18:33, Steve Kargl a écrit :

On Mon, Dec 04, 2017 at 11:49:30AM +, Alan Hicks wrote:

On 02/12/2017 17:28, Steve Kargl wrote:

On Sat, Dec 02, 2017 at 02:06:32PM +0100, Christian Ullrich wrote:

* Steve Kargl wrote:


Given that I asked about a specific revision number, it stands
to reason that I had already spent too much time wandering around
svnweb.freebsd.org.  An entry needs to be added to ports/UPDATING
to state which revision turns on flavors and by extension neuters
all port management tools except poudriere.  Four months from now
when users update a system finding that information by crawling
through svnweb.freebsd.org will be a challenge.


Your friend is subversion log search
svn log --search FLAVORS svn://svn.FreeBSD.org

r455205 | mat | 2017-11-30 15:33:29 + (Thu, 30 Nov 2017) | 13 lines

Generic FLAVORS work.

This does not document the change in ports/UPDATING.  FreeBSD
users have been told to check {src/ports}/UPDATING for 20+
years.  A change that fundamentally changes the way users
interact with ports/ should document.


This did not change anything for the users, so there was nothing in
UPDATING.

That's not true, for example it meant there was a minimum version 
requirement for poudriere without which it would fail to build any 
python packages, so if nothing else that should have been mentioned.


    Regards
    Steve
___
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: Welcome flavors! portmaster now dead? synth?

[Steven Hartland]

On 05/12/2017 04:51, Michelle Sullivan wrote:

Steven Hartland wrote:
On Mon, 4 Dec 2017 at 03:02, Michelle Sullivan <miche...@sorbs.net> 
wrote:



You mean if you're not into security or part of a security company stay
on quarterly, but if you need to keep patched up because you are in the
top 100 of most attacked sites/companies in the world, deploy a team of
people to patch security issues and run your own ports tree because
breakage on HEAD is often and when you need it the least and quarterly
doesn't guarantee it'll even work/compile and nearly never gets 
security

patches.


Sorry, but that's the truth of it and the reason I no longer use 
FreeBSD

or the Ports tree, instead using a derivative of each which is a lot
more stable and patched against security issues within hours of them
being identified.


This has not been our experience here, we’ve run our own ports tree from
HEAD for many years and while we’ve had some internal patches that need
fixing on update, thats always been down to us not keeping them up to 
date

with changes.


We were using HEAD, not a local copy that we could put patches in 
(that was the issue - we'd submit patches up and find them not applied 
for months in some cases.)
That's really unfortunate and I don't think you're alone, bringing in 
more resources to ports something that needs to be worked on.


Sure we could have got lucky but it does mean that such a blanket 
statement

is not valid for everyone’s use case.


I think you'll find using HEAD (as in the raw HEAD) not just a local 
copy with local patches it probably does ring true a lot - that said, 
didn't really bite me badly until the decision to force user changes 
by breaking the existing system (for me that was pkg_* -> pkgng) for 
others.. well they can say if they dare to chip in.
pkg -> pkgng was a little bit bumpy at the start but the results have 
been very much worth it.




I’m not sure if it’s possible but if you’re already allocating 
resources to

help handle security patches could that not be something that the wider
user base could benefit from via helping the secteam, if its turnaround
time on security patches you’re highlighting as an issue here?



Not working on FreeBSD now, the team deals with all in house OSes, 
FreeBSD is not deployed here anymore except on legacy machines that 
are being replaced (and I'm surprised there are any left now.)



Sorry to hear that.

___
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: Welcome flavors! portmaster now dead? synth?

[Steven Hartland]

On Mon, 4 Dec 2017 at 03:02, Michelle Sullivan  wrote:

>
> You mean if you're not into security or part of a security company stay
> on quarterly, but if you need to keep patched up because you are in the
> top 100 of most attacked sites/companies in the world, deploy a team of
> people to patch security issues and run your own ports tree because
> breakage on HEAD is often and when you need it the least and quarterly
> doesn't guarantee it'll even work/compile and nearly never gets security
> patches.
>
>
> Sorry, but that's the truth of it and the reason I no longer use FreeBSD
> or the Ports tree, instead using a derivative of each which is a lot
> more stable and patched against security issues within hours of them
> being identified.


This has not been our experience here, we’ve run our own ports tree from
HEAD for many years and while we’ve had some internal patches that need
fixing on update, thats always been down to us not keeping them up to date
with changes.

Sure we could have got lucky but it does mean that such a blanket statement
is not valid for everyone’s use case.

I’m not sure if it’s possible but if you’re already allocating resources to
help handle security patches could that not be something that the wider
user base could benefit from via helping the secteam, if its turnaround
time on security patches you’re highlighting as an issue here?
___
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: Welcome flavors! portmaster now dead? synth?

[Steven Hartland]

Come on guys you can’t make an omelet without breaking a few eggs.

Yes I got caught out by flavours too, but it was quickly fixed and it adds
a much needed feature which will make ports and associated tools better at
the end of the day.

People really seem to miss the point that there are only finite resources
and as an open source project that depends on people volunteering their
time to add new features and maintain tools.

A number of the messages to this thread really don’t seem to appreciate
that and they come across very poorly.

Sure it would it be nice if everyone’s favourite tool was always maintained
in good time but that can’t always be the case, however if anyone really
wants something, they can chip in and make it happen, thats the beauty of
open source projects.

For those who are considering migrating to something else, would your time
not be better spent chipping in to help?

When we adopted poudriere at work, it really enabled us to make much
quicker progress than we had been able to do with portmaster, so for those
that havent tried it its well worth a shot if your previous favourite tool
hasn’t been updated yet.

  Regards
  Steve
___
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 issue after FreeBSD 11 upgrade

[Steven Hartland]

Try tracing the install with truss or ktrace.

I suspect you'll find there is an issue where a pipe being closed; 
stdin, stdout or stderr, which results in the daemon that was started 
being stopped again, or something similar.


On 30/08/2017 13:00, Cassiano Peixoto wrote:

Hi Matthew,

Sorry back to this subject. But I really need to restart services with a
port. I'm quite sure there is a bug with pkg and FreeBSD 11.

I made a simple port to restart cron service:

# $FreeBSD$
PORTNAME=   ze
PORTVERSION=1.0
CATEGORIES= custom
MASTER_SITES=   #
DISTFILES=  #
EXTRACT_ONLY=   # NONE

MAINTAINER= peixotocassi...@gmail.com
COMMENT=ze port

#NO_MTREE=  yes



SUB_FILES=  pkg-install



NO_BUILD=   yes

NO_WRKSUBDIR=   yes



do-install:

 mkdir -p ${STAGEDIR}${DATADIR}

 @${CP} -r ${FILESDIR}/versions ${STAGEDIR}${DATADIR}/



post-install:

 ${SH} ${PKGINSTALL} ${PKGNAME} POST-INSTALL


.include 

Here is my pkg-install to restart cron service:

#!/bin/sh

if [ $2 = "POST-INSTALL" ]; then

   service cron restart

fi

Here is the output when I install the port:

root@kkk:~ # service cron start
cron already running?  (pid=2287).

root@kkk:~ # pkg install ze
Updating Custom repository catalogue...
Fetching meta.txz: 100%560 B   0.6kB/s00:01
Fetching packagesite.txz: 100%  122 KiB  62.6kB/s00:02
Processing entries: 100%
Custom repository update completed. 427 packages processed.
All repositories are up to date.
The following 1 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
ze: 1.0

Number of packages to be installed: 1

672 B to be downloaded.
[1/1] Fetching ze-1.0.txz: 100%672 B   0.7kB/s00:01
Checking integrity... done (0 conflicting)
[1/1] Installing ze-1.0...
+ set -- ze-1.0 PRE-INSTALL
+ [ PRE-INSTALL '=' POST-INSTALL ]
Extracting ze-1.0: 100%
+ set -- ze-1.0 POST-INSTALL
+ [ POST-INSTALL '=' POST-INSTALL ]
+ service cron restart
Stopping cron.
Waiting for PIDS: 2287.
Starting cron.

root@kkk:~ # ps ax | grep cron
2320  1  S+ 0:00.00 grep cron

As you can see the cron has stopped but hasn't started.

But If I install the same port with traditional ports approach it works,
see:

root@kkk: /usr/ports/custom/ze/# ps ax | grep cron
  1280  -  Is   0:00.97 /usr/sbin/cron -s

root@kkk: /usr/ports/custom/ze# make install
===>   ze-1.1 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by ze-1.1 for building
===>  Extracting for ze-1.1
===>  Patching for ze-1.1
===>  Configuring for ze-1.1
===>  Staging for ze-1.1
===>   Generating temporary packing list
mkdir -p /usr/ports/custom/ze/work/stage/usr/local/share/ze
/bin/sh /usr/ports/custom/ze/work/pkg-install ze-1.1 POST-INSTALL
> Compressing man pages (compress-man)
===>  Installing for ze-1.1
===>  Checking if ze already installed
Stopping cron.
Waiting for PIDS: 1280.
Starting cron.
===>   Registering installation for ze-1.1
Installing ze-1.1...

root@kkk: /usr/ports/custom/ze# ps ax | grep cron
37527  -  Ss   0:00.00 /usr/sbin/cron -s

Thanks for your help.



On Fri, Aug 11, 2017 at 1:45 PM, Cassiano Peixoto 
wrote:


On 10/08/2017 22:05, Cassiano Peixoto wrote:

I ran into an issue after FreeBSD 11 upgrade. I have some meta ports

that

starts services like slapd.

Its has been working fine on 10-STABLE. But after FreeBSD
11-STABLE r321625M upgrade it stopped working.

Here is a simple example of my pkg-install.in script:

#!/bin/sh
/usr/local/etc/rc.d/slapd stop
/usr/local/etc/rc.d/slapd start

I can see its executing while upgrading a package:

Stopping slapd.
Waiting for PIDS: 13875.
Starting slapd.

But looking if the process is running, it's not:

# ps ax | grep slapd
14164  0  S+ 0:00.00 grep slapd

Then I manually run the rc.d script and the service starts:

# /usr/local/etc/rc.d/slapd restart
slapd not running? (check /var/run/openldap/slapd.pid).
Starting slapd.

So my question is: something has changed on FreeBSD 11 not allowing this
kind of execution?

BTW, I'm using pkg 1.10.1 and my ports collection is as same as I was

using

on FreeBSD 10.

Restarting daemons after upgrading is something the project has been
quite resistant to implementing.  Mostly because as soon as you start
looking into it in any depth the true complexity of doing that sort of
thing reliably for any conceivable system becomes apparent and you end
up muttering darkly about systemd and 

Re: Easytag crashes with SIGABRT - stack overflow

[Steven Hartland]

amd64 or i386?

On 24/06/2017 22:15, Bob Eager wrote:

Before I submit an actual bug report, I wanted advice as to whether I'm
doing something silly!

I've been using Easytag for about 3 years now. All has been fine.

I recently upgraded from 10.3-RELEASE to 11.0-STABLE. I also updated
the ports (built locally).

Easytag now crashes as soon as I try to look at an album. SIGABRT - and
a kernel message about stack overflow. I've tried increasing the stack
size (via sysctl and reboot) by 50%, and there is no change.

Am I missing something?



___
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: Packaging Go Libs

[Steven Hartland]

I saw that, hoping it goes well as all of the other tools we've tried have
fairly significant issues.

On Sat, 13 May 2017 at 12:55, Christian Schwarz  wrote:

> Side note: There is an ongoing effort to build a dependency manager
> that aims at becoming part of the official Golang toolchain:
>
> https://github.com/golang/dep
>
> Cheers,
>
>   Christian
>
___
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: diff and submissions

[Steven Hartland]

On 05/05/2017 11:27, Mathieu Arnold wrote:

Le 05/05/2017 à 12:20, Baptiste Daroussin a écrit :

On Fri, May 05, 2017 at 12:17:06PM +0200, Mathieu Arnold wrote:

Le 05/05/2017 à 08:16, Franco Fichtner a écrit :

On 4. May 2017, at 10:20 AM, Mathieu Arnold  wrote:

If you went as far as being able to create a pull request, you can do a
git show HEAD or git diff origin/trunk...HEAD and submit that in the
FreeBSD PR as well.

It's pretty easy to extract the diff from a PR on GitHub, just append
".diff", and ".patch" works too, but gives the full git commit history:

https://github.com/freebsd/freebsd-ports/pull/62.diff

Yes, I am aware of that, the problem with github pull requests is that
they are outside of the FreeBSD bug report process, they do not get
assigned to maintainers, nobody notices them, they just stay there, and
get obsolete.
There have been 61 before, yes, I closed a lot because they were
obsolete because it is outside of our process and nobody noticed them,
and for the rest either asked the submitter to open a PR on our
bugzilla, or opened one myself.


I made a script which is a few lines of shell that converts pull requests to
phabricator reviews automatically.

I have handed it to some of the phabricator admins, I hope it will be progress
soon.


Please, do not do that.

Phabricator is for code review, not bug reports.  It all ends up in our
repository, but Phabricator does not have any maintainer notification
like Bugzilla has.
robak@ has a script that does pull-request -> bugzilla, and it has been
waiting for months for someone with access to do something about it.

Pull requests are not bug reports, that would issues.

IMO PR -> phabricator would be best match.

Regards
Steve
___
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: Packaging Go Libs

[Steven Hartland]

You should use built in golang vendoring to ensure these dependencies, as
their is no guarantee that someone won't update the library port and your
app would break, so doing that is very fragile
On Tue, 18 Apr 2017 at 03:34, Christopher Hall <
christopherhall@gmail.com> wrote:

> Hello Steve,
>
> On Mon, 17 Apr 2017 10:20:20 -0400, Steve Wills  wrote:
>
> > Hi,
> >
> > I'd like to propose eliminating packaging of Go libs.
>
> For my own go application I use the ports mechanism to specify specific
> versions of dependencies and it would only have been tested with those;
> if forces to use an older version it would likely fail as the APIs on
> some libs have changed quite a lot.
>
> So I personally see no need to have any go dependencies in the ports
> tree. I currently like the idea of having all the go dependencies
> statically linked and only few external "C" libs as dynamic links as it
> makes packaging and deployment very quick.
>
> >
> > Almost every Go app is developed with a different version of any given
> > lib than what another Go app might use. Forcing a Go app to use a
> > different version than what upstream might have chosen is error prone
> > at best and likely to produce a build that's unsupported upstream. So
> > for the packaged libs to even be useful, we would have to have as many
> > versions of each lib as there are consumers, or nearly as many.
> >
> > Further, best practice in the Go community is for Go apps to vendor
> > all their dependencies and almost all apps do that. This is the
> > reason most Go apps use different versions of it's libs.
> >
> > So to me, packaging Go libs doesn't make sense and I think we should
> > remove the Go libs from ports.
> >
> > Existing ports which use the Go libs should be updated to not use the
> > Go lib ports by doing one of these, in priority order:
> >
> > * Converted to using vendored deps included with the package source if
> > possible (preferred)
> > * Fetching the versions of deps specified by upstream (in the case of
> > vendor.json)
> > * As a last resort (deps are not included nor versions specified
> > exactly) fetching versions of deps available at the time of upstream
> > development
> >
> > Further, documentation should be added to the Porters Handbook saying
> > that we don't package Go libs and portlint should be updated to check
> > for installing files in GO_SRCDIR and GO_LIBDIR (exceot lang/go*).
> >
> > For reference, here's the list of Go lib ports that I found at the
> > moment:
> >
> > archivers/go-compress
> > databases/gomdb
> > databases/gosqlite3
> > databases/levigo
> > databases/radix.v2
> > databases/redigo
> > devel/go-bayesian
> > devel/go-cobra
> > devel/go-codec
> > devel/go-cpuid
> > devel/go-crc32
> > devel/go-faker
> > devel/go-form
> > devel/go-go.uuid
> > devel/go-goregen
> > devel/go-hashicorp-logutils
> > devel/go-json-rest
> > devel/go-logrus
> > devel/go-metrics
> > devel/go-nuid
> > devel/go-pflag
> > devel/go-protobuf
> > devel/go-raw
> > devel/go-runewidth
> > devel/go-slices
> > devel/go-sql-driver
> > devel/go-uuid
> > devel/go-yaml
> > devel/goprotobuf
> > net/go-amqp
> > net/go-geoip
> > net/go-httppath
> > net/go-httptreemux
> > net/go-nats
> > net/go.net
> > security/go.crypto
> > security/goptlib
> > textproc/go.text
> > www/go-fasthttp
> > www/webgo
> >
> > Does anyone have any objection or reasoning why this doesn't make
> > sense?
> >
> > Thanks,
> > Steve
> >
>
>
> --
> Best Regards.
> Christopher Hall.
> ___
> 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: Packaging Go Libs

[Steven Hartland]

Agreed we shouldn't vendor go libraries

On Mon, 17 Apr 2017 at 15:20, Steve Wills  wrote:

> Hi,
>
> I'd like to propose eliminating packaging of Go libs.
>
> Almost every Go app is developed with a different version of any given
> lib than what another Go app might use. Forcing a Go app to use a
> different version than what upstream might have chosen is error prone at
> best and likely to produce a build that's unsupported upstream. So for
> the packaged libs to even be useful, we would have to have as many
> versions of each lib as there are consumers, or nearly as many.
>
> Further, best practice in the Go community is for Go apps to vendor all
> their dependencies and almost all apps do that. This is the reason most
> Go apps use different versions of it's libs.
>
> So to me, packaging Go libs doesn't make sense and I think we should
> remove the Go libs from ports.
>
> Existing ports which use the Go libs should be updated to not use the Go
> lib ports by doing one of these, in priority order:
>
> * Converted to using vendored deps included with the package source if
> possible (preferred)
> * Fetching the versions of deps specified by upstream (in the case of
> vendor.json)
> * As a last resort (deps are not included nor versions specified
> exactly) fetching versions of deps available at the time of upstream
> development
>
> Further, documentation should be added to the Porters Handbook saying
> that we don't package Go libs and portlint should be updated to check
> for installing files in GO_SRCDIR and GO_LIBDIR (exceot lang/go*).
>
> For reference, here's the list of Go lib ports that I found at the moment:
>
> archivers/go-compress
> databases/gomdb
> databases/gosqlite3
> databases/levigo
> databases/radix.v2
> databases/redigo
> devel/go-bayesian
> devel/go-cobra
> devel/go-codec
> devel/go-cpuid
> devel/go-crc32
> devel/go-faker
> devel/go-form
> devel/go-go.uuid
> devel/go-goregen
> devel/go-hashicorp-logutils
> devel/go-json-rest
> devel/go-logrus
> devel/go-metrics
> devel/go-nuid
> devel/go-pflag
> devel/go-protobuf
> devel/go-raw
> devel/go-runewidth
> devel/go-slices
> devel/go-sql-driver
> devel/go-uuid
> devel/go-yaml
> devel/goprotobuf
> net/go-amqp
> net/go-geoip
> net/go-httppath
> net/go-httptreemux
> net/go-nats
> net/go.net
> security/go.crypto
> security/goptlib
> textproc/go.text
> www/go-fasthttp
> www/webgo
>
> Does anyone have any objection or reasoning why this doesn't make sense?
>
> Thanks,
> Steve
>
>
___
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"

Check for unsupported system version is broken

[Steven Hartland]

The check added to check and output an unsupported system version is 
broken and instead of output the error, the error errors ;-)

[00:00:01] >> Calculating ports order and dependencies
make: "/usr/ports/Mk/bsd.port.mk" line 1164: warning: duplicate script 
for target "show-unsupported-system-error" ignored
make: "/usr/ports/Mk/bsd.port.mk" line 1170: warning: using previous 
script for "show-unsupported-system-error" defined here


The change was added here:
https://svnweb.freebsd.org/ports?view=revision=431746

It's nice to warn the user, but ATM it just looks like someone broke 
something.


Regards
Steve
___
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: recent change to vim defaults?

[Steven Hartland]

mouse=n ?

On 18/01/2017 18:01, Julian Elischer wrote:

On 18/01/2017 5:03 PM, Raimund Sacherer wrote:

I have to put mouse=v to get the behavior I am used to.

Best


doesn't really work for me.

vim is still taking mouse events


___
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: Hash changes in the freebsd-ports GitHub mirror

[Steven Hartland]

On 02/12/2016 15:12, Shawn Webb wrote:

On Fri, Dec 02, 2016 at 10:40:29AM +0100, Raphael Kubo da Costa wrote:

Hi all,

I tried running `git pull` a few minutes ago and had a ton of conflicts.

It turns out all hashes after c96fb0418e545a569b5975b4d878a30a948c29d5
("fix issues related with USES=fonts" from 2015-07-18, aka r392404) are
now different in all GitHub branches.

Is anyone else experiencing this? Was this change intentional?

We at HardenedBSD are affected as well. Well, time to spend my weekend
resolving merge conflicts.

Seems like any downstream project that relies on the GitHub mirror of
the ports tree will have issues. Major ouch.


Did someone do a force push?
___
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: really to pkg people

[Steven Hartland]

If the machines where installed using pkg you can always grab the 
installs out of the cache (/var/cache/pkg/) on the relevant machines to 
debug issues.


On 28/11/2016 17:21, Julian Elischer wrote:

Is it at all possible for the ports/pkg people to QUIT DELETING STUFF!

It's most disconcerting when a quarterly collection of packages 
disappears and one has nowhere to get new packages that match all the 
ones out in the field. Since 10.3 is the latest 10 release and the 
release_3 collection is gettign soemwhat dated, it would be nice to 
have a stable quarterly set to refer to  that is not going to 
disappear in 3 months!


machines get shipped.. they go to customers. They are frozen in time.  
If debugging requires a new package, we have to have copied the entire 
quarterly set  "just in case". because the originals from freebsd have 
done a runner.  Are they archived somewhere?


yours


grumpy

p.s get off my lawn!

___
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: bind910-9.10.4 crash

[Steven Hartland]

On 16/05/2016 16:45, Marko Cupać wrote:

On Mon, 16 May 2016 15:48:57 +0100
Steven Hartland <ste...@multiplay.co.uk> wrote:


PR raised: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209553

What is the reason why this is a new PR and not update on:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209282



Because when I searched for an existing bug I got no results ;-)
___
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: bind910-9.10.4 crash

[Steven Hartland]

PR raised: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209553

On 16/05/2016 14:53, Steven Hartland wrote:


Even though this is not mentioned on their download page (they now 
list 9.10.4 as deprecated) and I found the following:


https://lists.isc.org/pipermail/bind-users/2016-May/096851.html

So looks like 9.10.4 is a no go and we should downgrade ports back to 
9.10.3-P4 until the issue is fixed.


Regards
Steve

On 05/05/2016 12:59, Dmitry Luhtionov wrote:

FreeBSD 11.0-CURRENT #0 r297375: Wed Mar 30 12:20:40 EEST 2016 amd64

bind910-9.10.4, installed from package crashed with these lines:

05-May-2016 14:34:35.528 general: critical: rbt.c:2726: INSIST(sibling !=
((void *)0)) failed, back trace
05-May-2016 14:34:35.528 general: critical: #0 0x4189d8 in ??
05-May-2016 14:34:35.528 general: critical: #1 0x5b812a in ??
05-May-2016 14:34:35.528 general: critical: #2 0x4bc5c8 in ??
05-May-2016 14:34:35.528 general: critical: #3 0x4c94be in ??
05-May-2016 14:34:35.528 general: critical: #4 0x4c8b4b in ??
05-May-2016 14:34:35.528 general: critical: #5 0x4c8448 in ??
05-May-2016 14:34:35.528 general: critical: #6 0x4c39cc in ??
05-May-2016 14:34:35.528 general: critical: #7 0x52d561 in ??
05-May-2016 14:34:35.528 general: critical: #8 0x5d9305 in ??
05-May-2016 14:34:35.528 general: critical: #9 0x801a37814 in ??
05-May-2016 14:34:35.528 general: critical: #10 0x0 in ??
05-May-2016 14:34:35.528 general: critical: exiting (due to assertion
failure)
___
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: bind910-9.10.4 crash

[Steven Hartland]

Even though this is not mentioned on their download page (they now list 
9.10.4 as deprecated) and I found the following:


https://lists.isc.org/pipermail/bind-users/2016-May/096851.html

So looks like 9.10.4 is a no go and we should downgrade ports back to 
9.10.3-P4 until the issue is fixed.


Regards
Steve

On 05/05/2016 12:59, Dmitry Luhtionov wrote:

FreeBSD 11.0-CURRENT #0 r297375: Wed Mar 30 12:20:40 EEST 2016 amd64

bind910-9.10.4, installed from package crashed with these lines:

05-May-2016 14:34:35.528 general: critical: rbt.c:2726: INSIST(sibling !=
((void *)0)) failed, back trace
05-May-2016 14:34:35.528 general: critical: #0 0x4189d8 in ??
05-May-2016 14:34:35.528 general: critical: #1 0x5b812a in ??
05-May-2016 14:34:35.528 general: critical: #2 0x4bc5c8 in ??
05-May-2016 14:34:35.528 general: critical: #3 0x4c94be in ??
05-May-2016 14:34:35.528 general: critical: #4 0x4c8b4b in ??
05-May-2016 14:34:35.528 general: critical: #5 0x4c8448 in ??
05-May-2016 14:34:35.528 general: critical: #6 0x4c39cc in ??
05-May-2016 14:34:35.528 general: critical: #7 0x52d561 in ??
05-May-2016 14:34:35.528 general: critical: #8 0x5d9305 in ??
05-May-2016 14:34:35.528 general: critical: #9 0x801a37814 in ??
05-May-2016 14:34:35.528 general: critical: #10 0x0 in ??
05-May-2016 14:34:35.528 general: critical: exiting (due to assertion
failure)
___
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: bind910-9.10.4 crash

[Steven Hartland]

Seeing the same on 10.2 as well.


On 05/05/2016 12:59, Dmitry Luhtionov wrote:

FreeBSD 11.0-CURRENT #0 r297375: Wed Mar 30 12:20:40 EEST 2016 amd64

bind910-9.10.4, installed from package crashed with these lines:

05-May-2016 14:34:35.528 general: critical: rbt.c:2726: INSIST(sibling !=
((void *)0)) failed, back trace
05-May-2016 14:34:35.528 general: critical: #0 0x4189d8 in ??
05-May-2016 14:34:35.528 general: critical: #1 0x5b812a in ??
05-May-2016 14:34:35.528 general: critical: #2 0x4bc5c8 in ??
05-May-2016 14:34:35.528 general: critical: #3 0x4c94be in ??
05-May-2016 14:34:35.528 general: critical: #4 0x4c8b4b in ??
05-May-2016 14:34:35.528 general: critical: #5 0x4c8448 in ??
05-May-2016 14:34:35.528 general: critical: #6 0x4c39cc in ??
05-May-2016 14:34:35.528 general: critical: #7 0x52d561 in ??
05-May-2016 14:34:35.528 general: critical: #8 0x5d9305 in ??
05-May-2016 14:34:35.528 general: critical: #9 0x801a37814 in ??
05-May-2016 14:34:35.528 general: critical: #10 0x0 in ??
05-May-2016 14:34:35.528 general: critical: exiting (due to assertion
failure)
___
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: graphics/ImageMagick vulnerability status?

[Steven Hartland]

Really doesn't help that they keep revising the fix, 3 releases in 6 
days, latest version actually being 6.9.4-1 :(


On 10/05/2016 15:09, Stefan Bethke wrote:

Hey,

according to 
https://www.imagemagick.org/discourse-server/viewtopic.php?f=4=29588, a 
release 6.9.4-0 should be out that improves the situation significantly.  It 
appears that graphics/ImageMagick is at 6.9.3.  It would be nice if people who 
follow ImageMagick more closely than me could speak to the security status of the 
current port, updates planned, and/or additional mitigation recommended.  Heise 
News is reporting that exploits have been posted and are seen in the wild.


Thanks,
Stefan



___
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: Removing documentation

[Steven Hartland]

On 14/02/2016 11:25, Michelle Sullivan wrote:

Kevin Oberman wrote:

My experience is that pkg(8) has been wonderfully robust since 1.3. before
1.3 it was a real pain in the neck, though I never had a need to rebuild
the DB, I did ave to do a bit of fix-up. I really, really wish Bapt had
listened and held up the default to pkg for a bit. Much as I like it, it
really was not ready for prime time when it became the default. The early
issues chased too many people away. E.g. you.
   

Nailed it!
The problem with that is its a chicken and egg situation, without it 
hitting prime time it likely wouldn't have got the needed use to 
identify and subsequently fix the issues you're referring to; at the 
very least it would have slowed that process down :(


Regards
Steve
___
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: mysql55 security fix, when?

[Steven Hartland]

In case I've missed something here, which  vulnerability specifically 
are you referring to?


On 23/11/2015 06:55, Gerhard Schmidt wrote:

Hi,

just ignore this one :-( my nigthly portsnap fetch didn't work as it
seams. manual portsnap fetch and it's there.

Regards
   Estartu

Am Montag, den 23.11.2015, 07:30 +0100 schrieb Gerhard Schmidt:

Hi,

there is a vulnerability report for mysql55 client and server out for
more than a week. What's the holdup from the update of the port to
the
fixed version?

Regards
Estartu
___
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: ZFS 9.2/9.3 oh so broken...

[Steven Hartland]

freebsd-ports@ is not really the right mailing list for this as there's 
no ports involved, unless I'm totally missing something, best place is 
freebsd-fs@.


You might want to consider triming your mail a little in the future as 
107Kb when the last zpool status below would had done is little 
excessive don't you think?


Its also a good idea to sumarise any issue in the subject, something 
like "zpool status still showing resilvering when complete"


With regards your problem, it seems like a display issue but have you tried:
1. zpool clear
2. reboot

Do either clear the problem?

9.x is really quite old I'd strongly advise you move to 10.2 as it 
includes a lot of fixes and enhancements to many areas including ZFS.


On 18/09/2015 23:36, Matthew Sullivan wrote:

Ok it's 9.2 so "unsupported" - but I believe the code is unchanged for
this one in 9.3 which *is* supported


Here's the last couple of days after the failure of a drive...  I
realised there was no point in swaping back in the new drive and I
should make the swap drive perm, and use the new drive as a hotspare
so followed: http://docs.oracle.com/cd/E19253-01/819-5461/gcvdi/index.html

... that was a mistake...

..online,spun_up   none 0x500062b200320021
   pool: storage
  state: ONLINE
status: One or more devices is currently being resilvered.  The pool will
 continue to function, possibly in a degraded state.
action: Wait for the resilver to complete.
   scan: resilver in progress since Thu Sep 17 00:20:00 2015
 14.1T scanned out of 27.1T at 1/s, (scan is slow, no estimated time)
 935G resilvered, 51.97% done
config:

 NAMESTATE READ WRITE CKSUM
 storage ONLINE   0 0 0
   raidz2-0  ONLINE   0 0 0
 mfid10  ONLINE   0 0 0
 mfid8   ONLINE   0 0 0
 mfid12  ONLINE   0 0 0
 mfid0   ONLINE   0 0 0
 mfid14  ONLINE   0 0 0
 mfid15  ONLINE   0 0 0
 mfid1   ONLINE   0 0 0
 mfid7   ONLINE   0 0 0
 mfid2   ONLINE   0 0 0
 mfid9   ONLINE   0 0 0
 mfid3   ONLINE   0 0 0
 mfid4   ONLINE   0 0 0
 mfid5   ONLINE   0 0 0
 mfid6   ONLINE   0 0 0
 mfid11  ONLINE   0 0 0
 spares
   mfid13AVAIL

errors: No known data errors
root@colossus:~ #


... so online (no errors) and still resilvering!!!

Michelle
___
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: [HEADS-UP] switching default Perl to 5.22

[Steven Hartland]

On 28/08/2015 16:44, Mathieu Arnold wrote:

+--On 28 août 2015 17:34:49 +0200 Mark Martinec
mark.martinec+free...@ijs.si wrote:
| 2015-08-28 17:16, Mathieu Arnold wrote:
| +--On 28 août 2015 17:13:34 +0200 Kurt Jaeger li...@opsec.eu wrote:
| | | In one or two weeks, I'll be switching the default Perl version
| to
| | | 5.22, and from now on, the new Perl will be added at the end of
| May
| | | when released, and switched to at the beginning of September.
| | |
| | | mod_perl is still broken with 5.22. Which is very sad. So maybe
| | | it's premature to switch the default ?
| |
| | But, it was building when I added Perl 5.22 in May, when did it
| break ?
| |
| | ohauer marked it broken on the 9th of June.
|
| Oh, maybe it did not work and I told myself never mind, mod_perl never
| works anyway
|
| The lang/perl5.20 will still be in ports, for anyone that needs it.
|
| Being heavy Perl users we have switched to 5.22 when it hit the ports,
| and I have no complaints about it.

Oh, yes, Perl 5.20 will still be until 2018-12-31, as will 5.18 until
2017-12-31 and 5.16 until 2016-12-31 :-)

But I'm talking about switching the default, it means people using packages
will not have mod_perl. (And you really can't use a non default Perl, and
binary packages for the rest.)


Yer that's not good :(

Regards
Steve
___
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: Another pkg showstopper-- more information

[Steven Hartland]

On 12/12/2014 19:22, Jeffrey Bouquet wrote:

On 12/12/14 10:25, Steven Hartland wrote:

Unless I'm missing something you don't actually provide any
information about the issue your actually seeing?

I personally have already updated 10 or so boxes with a wide range of
packages to pkg 1.4 and apart from a change with the handling of pkg
upgrade -f pkg, which was an intended fix, I didn't have any problems.

So not sure what your show stopper is or what you think could be
tested more thoroughly (don't forget the call for testing did go out
the other week, so looks like there was quite a bit of opportunity to
get involved.

 Regards
 Steve

On 12/12/2014 18:20, Jeffrey Bouquet via freebsd-ports wrote:

Reverted to pkg, by build, and FORCE PKG REGISTER.

pkgs still cannot be installed.

Still stuck with ports ( however portupgrade -- non-packages -- seems
to be
working with this pkg  pkg-devel downgrade )

(/ portmaster?  == no, cannot get
handle, lock on database)  only.

..###...##...

Should pkg and/or pkg-devel be more thoroughly tested before
release into the tree?   No other pkg usually hints at similar pkg
system(s) breakage without a proven recovery/rollback procedure
already documented...  similar to what portupgrade does with its
saving of shared libraries prior to upgrade of a port.
___
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org


Bringing the list back into this, as its not my area:


pkg install wants to install extra ports and abort traps
You'll want to post details about, OS version, pkg version, and the 
exact error with any stack trace

pkg add a pkg fetched file, cannot install it by package, wrong
architecture
(freebsd  FreeBSD or vice versa, setting somewhere, etc)
This doesn't make any sense to me, to others it may do but, always best 
to include proper steps and the output of the commands so people know 
exactly what your doing and the issue your seeing.

portupgrade works on some ports still, but machine  machine broken
because of pkg issues
and portupgrade -P broken similarly

portmaster cannot install,  convoluted error (lock on database and/or
already installed error(s))

So the /var/db/pkg build machine functionality also the portmaster  -P
portupgrade -P
are broken.  Here.  Maybe these could be tested on all architectures
before each new package
upgrade?  Another layer of machines, so to speak, just because NOT 
Again you don't provide any real details of the issues, you might of 
well have said its broken

  of SQlite..  ...  one

used to not have to post to the list or even subscribe to have  reliable
LAN build set.



___
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: Another pkg showstopper-- more information

[Steven Hartland]

On 15/12/2014 15:19, Jeffrey Bouquet wrote:

On 12/15/14 07:03, Steven Hartland wrote:

On 12/12/2014 19:22, Jeffrey Bouquet wrote:

On 12/12/14 10:25, Steven Hartland wrote:

Unless I'm missing something you don't actually provide any
information about the issue your actually seeing?

I personally have already updated 10 or so boxes with a wide range of
packages to pkg 1.4 and apart from a change with the handling of pkg
upgrade -f pkg, which was an intended fix, I didn't have any
problems.

So not sure what your show stopper is or what you think could be
tested more thoroughly (don't forget the call for testing did go out
the other week, so looks like there was quite a bit of opportunity to
get involved.

  Regards
  Steve

On 12/12/2014 18:20, Jeffrey Bouquet via freebsd-ports wrote:

Reverted to pkg, by build, and FORCE PKG REGISTER.

pkgs still cannot be installed.

Still stuck with ports ( however portupgrade -- non-packages -- seems
to be
working with this pkg  pkg-devel downgrade )

(/ portmaster?  == no, cannot get
handle, lock on database)  only.

..###...##...

Should pkg and/or pkg-devel be more thoroughly tested before
release into the tree?   No other pkg usually hints at similar pkg
system(s) breakage without a proven recovery/rollback procedure
already documented...  similar to what portupgrade does with its
saving of shared libraries prior to upgrade of a port.
___
To unsubscribe, send any mail to
freebsd-ports-unsubscr...@freebsd.org

Bringing the list back into this, as its not my area:


pkg install wants to install extra ports and abort traps

You'll want to post details about, OS version, pkg version, and the
exact error with any stack trace

pkg add a pkg fetched file, cannot install it by package, wrong
architecture
(freebsd  FreeBSD or vice versa, setting somewhere, etc)

This doesn't make any sense to me, to others it may do but, always
best to include proper steps and the output of the commands so people
know exactly what your doing and the issue your seeing.

portupgrade works on some ports still, but machine  machine broken
because of pkg issues
and portupgrade -P broken similarly

portmaster cannot install,  convoluted error (lock on database and/or
already installed error(s))

So the /var/db/pkg build machine functionality also the portmaster  -P
portupgrade -P
are broken.  Here.  Maybe these could be tested on all architectures
before each new package
upgrade?  Another layer of machines, so to speak, just because NOT 

Again you don't provide any real details of the issues, you might of
well have said its broken

   of SQlite..  ...  one

used to not have to post to the list or even subscribe to have  reliable
LAN build set.


I just updated 195471 bugzilla with a two week update.  Fixed
(temporarily?) the wrong
architecture error with a missing pkg.conf file or reversion of one of
them which was not
missing, and have a workaround for the errors that remain, but it is
tedious and
worrisome, to say the least.   Compared to how it could be with more SQL
coders on
board... maybe.


Cant say I've ever had any issues, its always just worked, so worth 
posting your customizations.


Made a post in a thread on the forums with the same information as the
update in
the PR above.

For what it is worth...
Just read the digest of Freebsd-STABLE that arrived today, others are also
disillusioned  with the priority given to pkg(ng) fixes for what was
once a not-exact but
very reliable packaging system across releases.



Thanks for forwarding to the list.  Unsure with each email sent
precisely the number of
recipients, but the fewer, the more likelihood the sometimes could not
be sent appears...

Mostly wishing for a procedure to fix it before needing to upgrade to
v10 !! Never had to
reinstall since v5.0x AFAIK...

Copying to the list again.

You might want to see if you have a reply to list or reply to all option 
in your mail client there Jeffrey, as I said this not my area but the 
pkgng are very good, so given the right information I'm sure someone 
will be able to help.


Regards
Steve
___
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: www/horde does not run on 10-STABLE - Fatal Error: Could not pack data

[Steven Hartland]

Have you made sure you have rebuilt all php libs?
- Original Message - 
From: Per olof Ljungmark p...@intersonic.se

To: po...@freebsd.org
Cc: questi...@freebsd.org
Sent: Monday, September 01, 2014 10:14 PM
Subject: www/horde does not run on 10-STABLE - Fatal Error: Could not 
pack data




Sorry for the cross-post but this is a bit out of the ordinary for me.

In short, no matter how I try varoius changes, I am unable to run
www/horde-base under latest 10-STABLE. The error is:

HORDE: Could not pack data. [pid 80949 on line 154 of
/usr/local/share/pear/Horde/Pack.php]

From what I gather, Pack.php deals with compressing data before cache,
maybe also before sending to browser. Problem occurs both through 
Apache

and with php cli.

Facts:
The same config ran on 10-STABLE mid-August
Stopped working after updating to latest 10-STABLE end last week 
(27th.)

Same config runs fine on 9-STABLE. Today I did a fresh 9-STABLE, got
Horde up and running fine. Updated the system to 10-STABLE. rebuilt 
all

ports and the error is back.

Please, if anyone has ANY idea what is going on? If I was fluent in 
PHP

I assume I could figure out myself...

Thank you!

//per
___
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




___
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: FreeBSD Port: rubygem-passenger-4.0.41_2

[Steven Hartland]

Yep after applying the latest patch + making sure the rename
is done I don't have any outstanding issues with the port.

   Regards
   Steve

- Original Message - 
From: David Keller david.kel...@litchis.fr

To: Steven Hartland kill...@multiplay.co.uk
Cc: FreeBSD Ports po...@freebsd.org; Scot Hetzel swhet...@gmail.com; Sergey A. 
Osokin o...@freebsd.org
Sent: Sunday, June 29, 2014 4:02 PM
Subject: Re: FreeBSD Port: rubygem-passenger-4.0.41_2



Hi,

This should correct the symlink creation error.

Regards,

David

On Wed, Apr 16, 2014 at 5:01 PM, Steven Hartland
kill...@multiplay.co.uk wrote:

Good catch on the WITH_APACHEPORT, thats old pre new options hang over,
switched to a straight else, as one or the other must be selected.

Looks like the svn diff didnt show the move, if you run the following:
svn mv files/pkg-message.in files/pkg-message-apache.in
before applying the attached patch with the WITH_APACHEPORT fix you
should be good.


   Regards
   Steve
- Original Message - From: Sergey A. Osokin o...@freebsd.org
To: Steven Hartland kill...@multiplay.co.uk
Cc: FreeBSD Ports po...@freebsd.org; Scot Hetzel swhet...@gmail.com;
David Keller david.kel...@litchis.fr
Sent: Wednesday, April 16, 2014 10:03 AM

Subject: Re: FreeBSD Port: rubygem-passenger-4.0.41_2



Hi Steven,

unfortunately your version is different, especially this part of the code:

SUB_LIST+= GEM_LIB_DIR=${GEM_LIB_DIR} RUBY=${RUBY}
-SUB_FILES= pkg-message
+.if ${PORT_OPTIONS:MNGINX}
+SUB_FILES+=pkg-message-nginx
+PKGMESSAGE=pkg-message-nginx
+.elif defined(WITH_APACHEPORT)
+SUB_FILES+=pkg-message-apache
+PKGMESSAGE=pkg-message-apache
+.endif

Please explain what's the WITH_APACHEPORT knob, also, what's the
pkg-message-apache file, missing from your original patch.

And anyway.  On the staging phase I have following error:

===  Staging for rubygem-passenger-4.0.41_3
===   rubygem-passenger-4.0.41_3 depends on package:
rubygem-fastthread=1.0.7 - found
===   rubygem-passenger-4.0.41_3 depends on package: rubygem-rack=1.4.5
- found
===   rubygem-passenger-4.0.41_3 depends on package:
rubygem-daemon_controller=1.2.0 - found
===   rubygem-passenger-4.0.41_3 depends on file: /usr/local/bin/gem19 -
found
===   rubygem-passenger-4.0.41_3 depends on file: /usr/local/bin/ruby19 -
found
===   rubygem-passenger-4.0.41_3 depends on file: /usr/local/sbin/apxs -
found
===   Generating temporary packing list
Building native extensions.  This could take a while...
Successfully installed passenger-4.0.41
1 gem installed
Installing RDoc documentation for passenger-4.0.41...
(CC=clang CXX=clang++
/usr/home/osa/ports/www/rubygem-passenger/work/stage/usr/local/bin/passenger-install-apache2-module
--auto)
/usr/local/lib/ruby/site_ruby/1.9/rubygems/dependency.rb:247:in
`to_specs': Could not find passenger (= 0) amongst
[daemon_controller-1.2.0, fastthread-1.0.7, rack-1.4.5, rake-10.2.2]
(Gem::LoadError)
   from
/usr/local/lib/ruby/site_ruby/1.9/rubygems/dependency.rb:256:in `to_spec'
   from /usr/local/lib/ruby/site_ruby/1.9/rubygems.rb:1231:in `gem'
   from
/usr/home/osa/ports/www/rubygem-passenger/work/stage/usr/local/bin/passenger-install-apache2-module:22:in
`main'
*** Error code 1

Any idea?

--
Sergey A. Osokin
o...@freebsd.org.

On Tue, Apr 15, 2014 at 12:59:14AM +0100, Steven Hartland wrote:


Hi Sergey, could you clarify which parts you believe are features?

I know there are a number of changes but all of them I'd class as fixes
and not really features.

For reference here's a description of the changes:-

* Added missing license
* Display the correct install message for both nginx and apache
* Fix staging build of nginx, apache and link components
* Ensure download_cache is included in the package which prevents warning
 on removal due to failure to delete directory.
* Updated LIB_DEPENDS to latest recommended format

Just to be sure we're both talking about the same changes I've attached
the latest version for reference.

   Regards
   Steve
- Original Message - From: Sergey A. Osokin o...@freebsd.org
To: Steven Hartland kill...@multiplay.co.uk
Cc: FreeBSD Ports po...@freebsd.org; Scot Hetzel
swhet...@gmail.com; David Keller david.kel...@litchis.fr
Sent: Tuesday, April 15, 2014 12:00 AM
Subject: Re: FreeBSD Port: rubygem-passenger-4.0.41_2


Hi Steven,

unfortunately, your patch is wrong and this is why I can't commit your
 changes.

What's wrong in your patch?  You have mixed features and bugfixes in one
 patch.
Please provide bugfix only patch.

-- ozz

On Sun, Apr 13, 2014 at 12:28:41PM +0100, Steven Hartland wrote:
- Original Message - From: David Keller
 david.kel...@litchis.fr


Hi Sergey,

It's not related to gem dependency error but the symlink creation
might be incorrect:
${LN} -s ${GEM_LIB_DIR} ${STAGEDIR}${PREFIX}/${GEMS_DIR}/${PORTNAME}

Will create the following symlink:
/usr/local/lib/ruby/gems/1.9/gems/passenger -
lib/ruby/gems/1.9/gems/passenger-4.0.41

Rather than

Re: Unable to use ports on 8.3 or earlier since r352986

[Steven Hartland]

For the record bmake doesn't work is fails to build qmake4 without even
giving an error :(

Where as copying make from 10 to the 8.3 box worked fine.

   Regards
   steve
- Original Message - 
From: l...@lena.kiev.ua

To: freebsd-ports@freebsd.org
Sent: Sunday, May 11, 2014 12:11 AM
Subject: Re: Unable to use ports on 8.3 or earlier since r352986



 As a work-around it may be possible to install the devel/bmake port and
 use it for port management.



Yes this should work. Install devel/bmake, then use 'bmake' instead of
'make' when interacting with the ports tree. Or install devel/fmake and
use 'fmake'. Either works.


Or download 8.4 sources:

rm -rf /usr/src
svn export svn://svn0.us-east.FreeBSD.org/base/releng/8.4 /usr/src

and upgrade the `make` binary only:

cd /usr/src/usr.bin/make
make
make install

Or (untested) copy the file /usr/bin/make from 8.4 CD or its image,
an example for i386:

fetch 
ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-i386/8.4/FreeBSD-8.4-RELEASE-i386-livefs.iso
mdconfig -f FreeBSD-8.4-RELEASE-i386-livefs.iso
mount_cd9660 /dev/md0 /mnt
cp -p /usr/bin/make /usr/bin/make.bak
cp /mnt/usr/bin/make /usr/bin/make
umount /mnt
mdconfig -d -u 0

Or if i386 then you can use the binary from my 8.4:

fetch http://lena.kiev.ua/make84.bin
cp -p /usr/bin/make /usr/bin/make.bak
cp make84.bin /usr/bin/make
___
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


___
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: Unable to use ports on 8.3 or earlier since r352986

[Steven Hartland]

I take it back this fails for qt4-rcc which fails to detect endian
and other issues :(

So far Lena's suggestion of an 8.4 make is working :)

- Original Message - 
From: Steven Hartland




For the record bmake doesn't work is fails to build qmake4 without even
giving an error :(

Where as copying make from 10 to the 8.3 box worked fine.
- Original Message - 
From: l...@lena.kiev.ua

To: freebsd-ports@freebsd.org
Sent: Sunday, May 11, 2014 12:11 AM
Subject: Re: Unable to use ports on 8.3 or earlier since r352986



 As a work-around it may be possible to install the devel/bmake port and
 use it for port management.



Yes this should work. Install devel/bmake, then use 'bmake' instead of
'make' when interacting with the ports tree. Or install devel/fmake and
use 'fmake'. Either works.


Or download 8.4 sources:

rm -rf /usr/src
svn export svn://svn0.us-east.FreeBSD.org/base/releng/8.4 /usr/src

and upgrade the `make` binary only:

cd /usr/src/usr.bin/make
make
make install

Or (untested) copy the file /usr/bin/make from 8.4 CD or its image,
an example for i386:

fetch 
ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-i386/8.4/FreeBSD-8.4-RELEASE-i386-livefs.iso
mdconfig -f FreeBSD-8.4-RELEASE-i386-livefs.iso
mount_cd9660 /dev/md0 /mnt
cp -p /usr/bin/make /usr/bin/make.bak
cp /mnt/usr/bin/make /usr/bin/make
umount /mnt
mdconfig -d -u 0

Or if i386 then you can use the binary from my 8.4:

fetch http://lena.kiev.ua/make84.bin
cp -p /usr/bin/make /usr/bin/make.bak
cp make84.bin /usr/bin/make

___
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: Global options ordering bug?

[Steven Hartland]

Its a single option so you need:
OPTIONS_UNSET=X11 JAVA

- Original Message - 
From: Dave Duchscher da...@nostrum.com

To: po...@freebsd.org
Sent: Sunday, June 08, 2014 3:36 AM
Subject: Global options ordering bug?


I was updating make.conf on a build machine today and noticed that OPTIONS_UNSET=X11 was not working.  Digging around, I found 
that if OPTIONS_UNSET=X11 was set before OPTIONS_UNSET=JAVA, OPTIONS_UNSET=X11 didn't happen.  WITHOUT_X11=YES worked in all 
cases.  Is this expected behavior or a bug?


--
DaveD

___
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



___
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: FreeBSD Port: rubygem-passenger-4.0.41_2

[Steven Hartland]

Good catch on the WITH_APACHEPORT, thats old pre new options hang over,
switched to a straight else, as one or the other must be selected.

Looks like the svn diff didnt show the move, if you run the following:
svn mv files/pkg-message.in files/pkg-message-apache.in
before applying the attached patch with the WITH_APACHEPORT fix you
should be good.

   Regards
   Steve
- Original Message - 
From: Sergey A. Osokin o...@freebsd.org

To: Steven Hartland kill...@multiplay.co.uk
Cc: FreeBSD Ports po...@freebsd.org; Scot Hetzel swhet...@gmail.com; David 
Keller david.kel...@litchis.fr
Sent: Wednesday, April 16, 2014 10:03 AM
Subject: Re: FreeBSD Port: rubygem-passenger-4.0.41_2



Hi Steven,

unfortunately your version is different, especially this part of the code:

SUB_LIST+= GEM_LIB_DIR=${GEM_LIB_DIR} RUBY=${RUBY}
-SUB_FILES= pkg-message
+.if ${PORT_OPTIONS:MNGINX}
+SUB_FILES+=pkg-message-nginx
+PKGMESSAGE=pkg-message-nginx
+.elif defined(WITH_APACHEPORT)
+SUB_FILES+=pkg-message-apache
+PKGMESSAGE=pkg-message-apache
+.endif

Please explain what's the WITH_APACHEPORT knob, also, what's the
pkg-message-apache file, missing from your original patch.

And anyway.  On the staging phase I have following error:

===  Staging for rubygem-passenger-4.0.41_3
===   rubygem-passenger-4.0.41_3 depends on package: rubygem-fastthread=1.0.7 
- found
===   rubygem-passenger-4.0.41_3 depends on package: rubygem-rack=1.4.5 - 
found
===   rubygem-passenger-4.0.41_3 depends on package: 
rubygem-daemon_controller=1.2.0 - found
===   rubygem-passenger-4.0.41_3 depends on file: /usr/local/bin/gem19 - found
===   rubygem-passenger-4.0.41_3 depends on file: /usr/local/bin/ruby19 - found
===   rubygem-passenger-4.0.41_3 depends on file: /usr/local/sbin/apxs - found
===   Generating temporary packing list
Building native extensions.  This could take a while...
Successfully installed passenger-4.0.41
1 gem installed
Installing RDoc documentation for passenger-4.0.41...
(CC=clang CXX=clang++ 
/usr/home/osa/ports/www/rubygem-passenger/work/stage/usr/local/bin/passenger-install-apache2-module --auto)
/usr/local/lib/ruby/site_ruby/1.9/rubygems/dependency.rb:247:in `to_specs': Could not find passenger (= 0) amongst 
[daemon_controller-1.2.0, fastthread-1.0.7, rack-1.4.5, rake-10.2.2] (Gem::LoadError)

   from /usr/local/lib/ruby/site_ruby/1.9/rubygems/dependency.rb:256:in 
`to_spec'
   from /usr/local/lib/ruby/site_ruby/1.9/rubygems.rb:1231:in `gem'
   from 
/usr/home/osa/ports/www/rubygem-passenger/work/stage/usr/local/bin/passenger-install-apache2-module:22:in
 `main'
*** Error code 1

Any idea?

--
Sergey A. Osokin
o...@freebsd.org.

On Tue, Apr 15, 2014 at 12:59:14AM +0100, Steven Hartland wrote:

Hi Sergey, could you clarify which parts you believe are features?

I know there are a number of changes but all of them I'd class as fixes
and not really features.

For reference here's a description of the changes:-

* Added missing license
* Display the correct install message for both nginx and apache
* Fix staging build of nginx, apache and link components
* Ensure download_cache is included in the package which prevents warning
 on removal due to failure to delete directory.
* Updated LIB_DEPENDS to latest recommended format

Just to be sure we're both talking about the same changes I've attached
the latest version for reference.

   Regards
   Steve
- Original Message - From: Sergey A. Osokin o...@freebsd.org
To: Steven Hartland kill...@multiplay.co.uk
Cc: FreeBSD Ports po...@freebsd.org; Scot Hetzel swhet...@gmail.com; David 
Keller david.kel...@litchis.fr
Sent: Tuesday, April 15, 2014 12:00 AM
Subject: Re: FreeBSD Port: rubygem-passenger-4.0.41_2


Hi Steven,

unfortunately, your patch is wrong and this is why I can't commit your changes.

What's wrong in your patch?  You have mixed features and bugfixes in one patch.
Please provide bugfix only patch.

-- 
ozz


On Sun, Apr 13, 2014 at 12:28:41PM +0100, Steven Hartland wrote:
- Original Message - From: David Keller david.kel...@litchis.fr


Hi Sergey,

It's not related to gem dependency error but the symlink creation
might be incorrect:
${LN} -s ${GEM_LIB_DIR} ${STAGEDIR}${PREFIX}/${GEMS_DIR}/${PORTNAME}

Will create the following symlink:
/usr/local/lib/ruby/gems/1.9/gems/passenger -
lib/ruby/gems/1.9/gems/passenger-4.0.41

Rather than:
/usr/local/lib/ruby/gems/1.9/gems/passenger -
/usr/local/lib/ruby/gems/1.9/gems/passenger-4.0.41

Or:
/usr/local/lib/ruby/gems/1.9/gems/passenger - passenger-4.0.41


You might prefer using:
${LN} -s ${STAGEDIR}${PREFIX}/${GEMS_DIR}/${GEM_NAME}
${STAGEDIR}${PREFIX}/${GEMS_DIR}/${PORTNAME}

Or even:
${LN} -s ${GEM_NAME} ${STAGEDIR}${PREFIX}/${GEMS_DIR}/${PORTNAME}

My current version has:
(cd ${STAGEDIR}${PREFIX}/${GEMS_DIR}  ${LN} -s ${GEM_NAME} ${PORTNAME})

Which I will create:
/usr/local/lib/ruby/gems/1.9/gems/passenger - passenger-4.0.41

@Sergey: For your apache module problem try

Re: FreeBSD Port: rubygem-passenger-4.0.41_2

[Steven Hartland]

Hi Sergey, could you clarify which parts you believe are features?

I know there are a number of changes but all of them I'd class as fixes
and not really features.

For reference here's a description of the changes:-

* Added missing license
* Display the correct install message for both nginx and apache
* Fix staging build of nginx, apache and link components
* Ensure download_cache is included in the package which prevents warning
 on removal due to failure to delete directory.
* Updated LIB_DEPENDS to latest recommended format

Just to be sure we're both talking about the same changes I've attached
the latest version for reference.

   Regards
   Steve
- Original Message - 
From: Sergey A. Osokin o...@freebsd.org

To: Steven Hartland kill...@multiplay.co.uk
Cc: FreeBSD Ports po...@freebsd.org; Scot Hetzel swhet...@gmail.com; David 
Keller david.kel...@litchis.fr
Sent: Tuesday, April 15, 2014 12:00 AM
Subject: Re: FreeBSD Port: rubygem-passenger-4.0.41_2



Hi Steven,

unfortunately, your patch is wrong and this is why I can't commit your changes.

What's wrong in your patch?  You have mixed features and bugfixes in one patch.
Please provide bugfix only patch.

--
ozz

On Sun, Apr 13, 2014 at 12:28:41PM +0100, Steven Hartland wrote:

- Original Message - From: David Keller david.kel...@litchis.fr


Hi Sergey,

It's not related to gem dependency error but the symlink creation
might be incorrect:
${LN} -s ${GEM_LIB_DIR} ${STAGEDIR}${PREFIX}/${GEMS_DIR}/${PORTNAME}

Will create the following symlink:
/usr/local/lib/ruby/gems/1.9/gems/passenger -
lib/ruby/gems/1.9/gems/passenger-4.0.41

Rather than:
/usr/local/lib/ruby/gems/1.9/gems/passenger -
/usr/local/lib/ruby/gems/1.9/gems/passenger-4.0.41

Or:
/usr/local/lib/ruby/gems/1.9/gems/passenger - passenger-4.0.41


You might prefer using:
${LN} -s ${STAGEDIR}${PREFIX}/${GEMS_DIR}/${GEM_NAME}
${STAGEDIR}${PREFIX}/${GEMS_DIR}/${PORTNAME}

Or even:
${LN} -s ${GEM_NAME} ${STAGEDIR}${PREFIX}/${GEMS_DIR}/${PORTNAME}

My current version has:
(cd ${STAGEDIR}${PREFIX}/${GEMS_DIR}  ${LN} -s ${GEM_NAME} ${PORTNAME})

Which I will create:
/usr/local/lib/ruby/gems/1.9/gems/passenger - passenger-4.0.41

@Sergey: For your apache module problem try the attached patch / full
version which fixes that for me.

I'd previously only ever built the nginx version and looks like the
apache2 module build was broken when stage support was added.

I've confirmed it builds but I don't have an apache2 install to test
fully with here so if you could let me know if it works and I'll get all
the changes checked in.

   Regards
   Steve




___
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


rubygem-passenger.patch
Description: Binary data
___
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: FreeBSD Port: rubygem-passenger-4.0.41_2

[Steven Hartland]

- Original Message - 
From: David Keller david.kel...@litchis.fr




Hi Sergey,

It's not related to gem dependency error but the symlink creation
might be incorrect:
${LN} -s ${GEM_LIB_DIR} ${STAGEDIR}${PREFIX}/${GEMS_DIR}/${PORTNAME}

Will create the following symlink:
/usr/local/lib/ruby/gems/1.9/gems/passenger -
lib/ruby/gems/1.9/gems/passenger-4.0.41

Rather than:
/usr/local/lib/ruby/gems/1.9/gems/passenger -
/usr/local/lib/ruby/gems/1.9/gems/passenger-4.0.41

Or:
/usr/local/lib/ruby/gems/1.9/gems/passenger - passenger-4.0.41


You might prefer using:
${LN} -s ${STAGEDIR}${PREFIX}/${GEMS_DIR}/${GEM_NAME}
${STAGEDIR}${PREFIX}/${GEMS_DIR}/${PORTNAME}

Or even:
${LN} -s ${GEM_NAME} ${STAGEDIR}${PREFIX}/${GEMS_DIR}/${PORTNAME}


My current version has:
(cd ${STAGEDIR}${PREFIX}/${GEMS_DIR}  ${LN} -s ${GEM_NAME} ${PORTNAME})

Which I will create:
/usr/local/lib/ruby/gems/1.9/gems/passenger - passenger-4.0.41

@Sergey: For your apache module problem try the attached patch / full
version which fixes that for me.

I'd previously only ever built the nginx version and looks like the
apache2 module build was broken when stage support was added.

I've confirmed it builds but I don't have an apache2 install to test
fully with here so if you could let me know if it works and I'll get all
the changes checked in.

   Regards
   Steve

Makefile
Description: Binary data


Makefile.patch
Description: Binary data
___
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: FreeBSD Port: rubygem-passenger-4.0.41_2

[Steven Hartland]

I've been playing with this and other issues with that port, try the attached 
patch.

   Regards
   Steve
- Original Message - 
From: David Keller david.kel...@litchis.fr

To: o...@freebsd.org
Cc: po...@freebsd.org
Sent: Friday, April 11, 2014 10:29 AM
Subject: FreeBSD Port: rubygem-passenger-4.0.41_2



Hello,

Since

rev *350664* (Wed Apr 9 02:36:08 2014 UTC)


After *#make install *from */usr/ports/www/rubygem-passenger*

/usr/local/lib/ruby/gems/1.9/gems/passenger-4.0.41/*buildout*


is no longer populated with passenger binaries, hence nginx complains that
passenger is not installed.

Mannualy copying *buildout* directory from
*/usr/ports/www/rubygem-passenger/work/**passenger-4.0.41/* resolves the
issue.

Regards.
___
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


rubygem-passenger-stage-fix.patch
Description: Binary data
___
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: FreeBSD Port: rubygem-passenger-4.0.41_2

[Steven Hartland]

- Original Message - 
From: David Keller david.kel...@litchis.fr




It's working :-)

But the symlink seems incorrect:
* passenger - lib/ruby/gems/1.9/gems/passenger-4.0.41

I might be better like this:
* passenger - passenger-4.0.41


Sorry David I've never used the link option, I just corrected
the syntax to work with stage, could you give me some context
on that please?

   Regards
   Steve
___
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: FreeBSD Port: rubygem-passenger-4.0.41_2

[Steven Hartland]

- Original Message - 
From: Steven Hartland kill...@multiplay.co.uk

To: David Keller david.kel...@litchis.fr
Cc: po...@freebsd.org; o...@freebsd.org
Sent: Friday, April 11, 2014 12:04 PM
Subject: Re: FreeBSD Port: rubygem-passenger-4.0.41_2


- Original Message - 
From: David Keller david.kel...@litchis.fr




It's working :-)

But the symlink seems incorrect:
* passenger - lib/ruby/gems/1.9/gems/passenger-4.0.41

I might be better like this:
* passenger - passenger-4.0.41


Sorry David I've never used the link option, I just corrected
the syntax to work with stage, could you give me some context
on that please?


Actually I think I know what you might mean try changing the LN cmd
to:
(cd ${STAGEDIR}${PREFIX}/${GEMS_DIR}  ${LN} -s ${GEM_LIB_DIR} ${PORTNAME})

   Regards
   Steve
___
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: pkgng multi-repository support description

[Steven Hartland]

- Original Message - 
From: Andriy Gapon a...@freebsd.org



Is there a document that describes how pkgng multi-repository support works?
I am trying to understand what pkgng does when different versions of the same
package are present in different repositories.

Practically, I want to achieve the following.
One repository is designated as primary.  If a package is present in the primary
repository, then its presence in other repositories is completely ignored.

Alternatively, the following could also work for me.
A package remembers from what repository it was originally installed and all
future upgrades are taken from the same repository.

What I want to avoid is a package flip-flopping between being installed from
different repositories depending on their update pace.  This is useful e.g. when
I have my local repository for some packages that I want to build with special
options but I also want to install all other packages from some other repository
which is not under my control.  So I fear that the other repository gets a newer
version of a package than what my repository has, then pkg upgrade would upgrade
the package and thus it won't have any customizations until my repository
catches up.

Thank you very much.

P.S. https://github.com/freebsd/pkg#multirepos seems to be outdated?


Did you ever figure this one out?

In our case we want to tell pkg to only use repro XYZ from the ones availble,
for example without having to delete /etc/pkg/FreeBSD.conf.

   Regards
   Steve
___
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: FreeBSD Port: rubygem-passenger-4.0.41_2

[Steven Hartland]

The change is from :N - :M
.if ${PORT_OPTIONS:MDEBUG}

Which occurs 220 in the port tree and:

.if ${PORT_OPTIONS:NDEBUG}

Which only occurs twice, so TBH I assumed it was a typo given every other
option uses PORTOPTIONS:M${option}

Unfortunately the docs don't seem to provide any clarification
http://www.freebsd.org/doc/en/books/porters-handbook/makefile-options.html
so if anyone could chime in with some details on the exact meanings that
would be most appreciated.

   Regards
   Steve

- Original Message - 
From: Sergey A. Osokin o...@freebsd.org

To: Steven Hartland kill...@multiplay.co.uk
Cc: David Keller david.kel...@litchis.fr; po...@freebsd.org
Sent: Friday, April 11, 2014 11:27 PM
Subject: Re: FreeBSD Port: rubygem-passenger-4.0.41_2



Hi Steven,

looks good, except one thing:

-.if ${PORT_OPTIONS:NDEBUG}
+.if ${PORT_OPTIONS:MDEBUG}

Could you explain what's the actual change here.

Also, please bump PORTREVISION for final patch.

--
Sergey A. Osokin
o...@freebsd.org


   Regards
   Steve
- Original Message - From: David Keller david.kel...@litchis.fr
To: o...@freebsd.org
Cc: po...@freebsd.org
Sent: Friday, April 11, 2014 10:29 AM
Subject: FreeBSD Port: rubygem-passenger-4.0.41_2


Hello,

Since

rev *350664* (Wed Apr 9 02:36:08 2014 UTC)


After *#make install *from */usr/ports/www/rubygem-passenger*

/usr/local/lib/ruby/gems/1.9/gems/passenger-4.0.41/*buildout*


is no longer populated with passenger binaries, hence nginx complains that
passenger is not installed.

Mannualy copying *buildout* directory from
*/usr/ports/www/rubygem-passenger/work/**passenger-4.0.41/* resolves the
issue.

Regards.
___
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






___
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: pkgng multi-repository support description

[Steven Hartland]

- Original Message - 
From: Matthew Seaman matt...@freebsd.org

On 11/04/2014 17:21, Steven Hartland wrote:

In our case we want to tell pkg to only use repro XYZ from the ones
availble, for example without having to delete /etc/pkg/FreeBSD.conf.


For individual ports:

pkg-repository(8), the section titled WORKING WITH MULTIPLE REPOSITORIES

To disable eg. the default FreeBSD repo:

cat EOF  /usr/local/etc/pkg/repos/FreeBSD.conf
FreeBSD: {
 enabled: no
}
EOF


Thanks Matthew, I'd reviewed pkg.conf where I got all the base info from
but never saw any mention of this setting or even a reference to that
man page. Seems like it would definitely be worth while adding a reference
or two in there?

Actually I dont have any pkg-repository(8) I have a pkg-repository(5) but
no mention of an enabled flag?

Am I totally missing something?

   Regards
   Steve
___
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: Quickly cleanroom building and installing software from ports

[Steven Hartland]

You can pop a web server in front of its output directory, configure your
repository to point to it and then let pkg install do the yes.

Simply answer yes it can :)

- Original Message - 
From: Chris Rees cr...@bayofrum.net




I'd be delighted if out of the box it could *install* just built packages.  Can 
it do that?

Chris

On 8 April 2014 22:12:19 BST, Steven Hartland kill...@multiplay.co.uk wrote:

Look at poudriere its really good for exactly this, can even cross
build
different versions.


___
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: Quickly cleanroom building and installing software from ports

[Steven Hartland]

Look at poudriere its really good for exactly this, can even cross build
different versions.

   Regards
   Steve

- Original Message - 
From: Chris Rees cr...@physics.org

To: po...@freebsd.org
Sent: Tuesday, April 08, 2014 9:45 PM
Subject: Quickly cleanroom building and installing software from ports



Hi all,

I really enjoy using pkgng, and I love that all my packages are build on a 
clean system without any possible quirks.

I found that installing from ports is a bit of a pain on these machines however, because I don't have any of the development 
packages installed (gcc47 etc).  I found I ended up installing these, but didn't like the 'pollution'.


I chucked together two scripts, buildthis and upgradethis and figured people 
might find them useful.

All you need do is install it and Tinderbox and either:

# buildthis category/port [category2/port2 ]

or

# cd /usr/ports/category/port  buildthis

A build will be created for Tinderbox if necessary and the port will have a 
package built and installed.

Requires Tinderbox, if people want it around poudriere then please let me know.

Caveat emptor: I just wanted this to work for me... the code quality isn't 
anything special

http://www.bayofrum.net/cgi-bin/fossil/buildthis/tarball/buildthis-d503b895e8cc3883.tar.gz?uuid=d503b895e8cc3883dc5c6f2ed006b22ed10547ff

Chris

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
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



___
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: [FreeBSD-Ports-Announce] Time to bid farewell to the old pkg_ tools

[Steven Hartland]

- Original Message - 
From: Julian H. Stacey j...@berklix.com

Immediately personal criticism is a poor way to start convincing.

ports/ is not just for package addicts.  I never install packages,
but only build  install from ports/.  sqlite junk obstructs
/var/db/pkg being accessed by find  grep to debug breaking ports builds.


We also maintain all our machines from in house built ports but I
must say in the 10 years I've never used find / grep on /var/db/pkg
to debug breaking port builds.

Everyone works differently, so we may be unique here, but surely if
the tools still exist to determine the issue e.g. sqlite queries,
along side the clear advantages the new storage brings, I'm not
sure what the issue is?

   Regards
   Steve


This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.

___
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

Possible fix for all p5-* port installs being broken on FreeBSD

[Steven Hartland]

Hi Sunpoet seems your the most active maintainer
of perl ports system on FreeBSD so please excuse
the email if your not the correct person but 
here goes.


Currently make install for all p5-* ports fail
because they cant find the installed files.

This seems to be because the site_perl directory
struction now uses PERL_VERSION instead of PERL_VER
e.g 5.14.4 not 5.14

The attached patch fixes this for me by changing
the package vars to use PERL_VERISON but its not
clear if its the install which is incorrect or
the vars.

cc'ed ports@ just in case.

   Regards
   Steve

p5-ports-fix.patch
Description: Binary data
___
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: Possible fix for all p5-* port installs being broken on FreeBSD

[Steven Hartland]

- Original Message - 
From: Sunpoet Po-Chuan Hsieh sunp...@freebsd.org



On Fri, Oct 25, 2013 at 8:26 PM, Steven Hartland s...@freebsd.org wrote:


Hi Sunpoet seems your the most active maintainer
of perl ports system on FreeBSD so please excuse
the email if your not the correct person but here goes.

Currently make install for all p5-* ports fail
because they cant find the installed files.

This seems to be because the site_perl directory
struction now uses PERL_VERSION instead of PERL_VER
e.g 5.14.4 not 5.14

The attached patch fixes this for me by changing
the package vars to use PERL_VERISON but its not
clear if its the install which is incorrect or
the vars.

cc'ed ports@ just in case.

   Regards
   Steve



Hi Steven,

The perl infrastructure change was made by az@.
It helps to make minor version update easier (e.g. 5.14.2 - 5.14.4).
Please see UPDATING 20130612 entry for further information.
Thanks.


Thanks Sunpoet :)

@az given UPDATING 20130612 I guess the attached patch is
required. As its currently its not possible to install any
p5-* port think we should get it commited ASAP assuming its
the correct fix.

   Regards
   Steve


This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.

p5-ports-fix.patch
Description: Binary data
___
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: Possible fix for all p5-* port installs being broken on FreeBSD

[Steven Hartland]

An example would be:-

make install
===  Installing for p5-Encode-Locale-1.03
===   p5-Encode-Locale-1.03 depends on file: /usr/local/bin/perl5.14.2 - found
===  Checking if converters/p5-Encode-Locale already installed
===   Registering installation for p5-Encode-Locale-1.03 #1
/data/portbuild/usr/ports/converters/p5-Encode-Locale/work/.PLIST.mktmp
pkg-static: lstat(/usr/local/lib/perl5/5.14/man/man3/Encode::Locale.3.gz): No 
such file or directory
*** Error code 74

Stop.
make: stopped in /usr/ports/converters/p5-Encode-Locale

- Original Message - 
From: Andrej Zverev a...@freebsd.org

To: Steven Hartland kill...@multiplay.co.uk
Cc: Sunpoet Po-Chuan Hsieh sunp...@freebsd.org; ports po...@freebsd.org
Sent: Friday, October 25, 2013 3:45 PM
Subject: Re: Possible fix for all p5-* port installs being broken on FreeBSD



I'm sorry, but can you for start provide build log where I can see
error(s) ? I'm sure it's just your local issues.


On Fri, Oct 25, 2013 at 5:27 PM, Steven Hartland
kill...@multiplay.co.uk wrote:

- Original Message - From: Sunpoet Po-Chuan Hsieh
sunp...@freebsd.org


On Fri, Oct 25, 2013 at 8:26 PM, Steven Hartland s...@freebsd.org wrote:


Hi Sunpoet seems your the most active maintainer
of perl ports system on FreeBSD so please excuse
the email if your not the correct person but here goes.

Currently make install for all p5-* ports fail
because they cant find the installed files.

This seems to be because the site_perl directory
struction now uses PERL_VERSION instead of PERL_VER
e.g 5.14.4 not 5.14

The attached patch fixes this for me by changing
the package vars to use PERL_VERISON but its not
clear if its the install which is incorrect or
the vars.

cc'ed ports@ just in case.

   Regards
   Steve




Hi Steven,

The perl infrastructure change was made by az@.
It helps to make minor version update easier (e.g. 5.14.2 - 5.14.4).
Please see UPDATING 20130612 entry for further information.
Thanks.



Thanks Sunpoet :)

@az given UPDATING 20130612 I guess the attached patch is
required. As its currently its not possible to install any
p5-* port think we should get it commited ASAP assuming its
the correct fix.

   Regards
   Steve


This e.mail is private and confidential between Multiplay (UK) Ltd. and the
person or entity to whom it is addressed. In the event of misdirection, the
recipient is prohibited from using, copying, printing or otherwise
disseminating it or any information contained in it.
In the event of misdirection, illegible or incomplete transmission please
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.





This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.

___
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

pkgng ports failing to process make install correctly

[Steven Hartland]

Sorry for the cross post but not sure where the exact
issues lies.

Today I came to install git so as per normal
cd /usr/ports/devel/git
make install

This failed first due to a problem with p5-* ports
failing to install, which is being discussed on ports@
Possible fix for all p5-* port installs being broken
on FreeBSD

So with that fixed the next issue was a failure to
process the docs for git. The errors for this was:-
install -d -m 755 /usr/local/libexec/git-core
install -m 755 git-subtree /usr/local/libexec/git-core
asciidoc -b docbook -d manpage -f ../../Documentation/asciidoc.conf \
   -agit_version=1.8.4.1 git-subtree.txt
asciidoc: FAILED: configuration file asciidoc.conf missing
gmake[2]: *** [git-subtree.xml] Error 1
gmake[2]: Leaving directory 
`/data/portbuild/usr/ports/devel/git/work/git-1.8.4.1/contrib/subtree'

As you can see its moaning about asciidoc.conf being
missing. This should have been installed with asciidoc
so I started digging there.

The problem seems to be related to how the new stage
system interacts with pkgng. The asciidoc port has
a post-install target which copies XXX.conf.sample
files to XXX.conf if the target file doesn't exists.

It does this to STAGEDIR which seems to work correctly
but install from the staging area to the live area
doesn't reflect this.

I've checked pkg-plist and it has the relavent @exec
lines so the port itself seems ok.

Next I tried:
* make package
* make deinstall
* pkg add asciidoc-8.6.8_1.txz

This works fine and all the expected .conf files are
installed.

Next I tried a port install without pkgng by using:
make WITHOUT_PKGNG=1 install

While this moans about the fact the system is using
pkgng the expected .conf files are installed.

So it looks like there is an issue between ports and
pkgng, possibly around the processing of pkg-plist
@exec commands when staging is active.

Any ideas?

   Regards
   Steve


This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.

___
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: Possible fix for all p5-* port installs being broken on FreeBSD

[Steven Hartland]

- Original Message - 
From: Andrej Zverev a...@freebsd.org



Can you please show output (you can pastebin it somewhere)
1. make -C /usr/ports/converters/p5-Encode-Locale/ -VPERL_VERSION
-VPERL_VER -VMAN3PREFIX -VSITE_PERL -VSITE_PERL_REL

make -C /usr/ports/converters/p5-Encode-Locale/ -VPERL_VERSION -VPERL_VER 
-VMAN3PREFIX -VSITE_PERL -VSITE_PERL_REL
5.14.2
5.14
/usr/local/lib/perl5/5.14.2
/usr/local/lib/perl5/site_perl/5.14.2
lib/perl5/site_perl/5.14.2


2. perl -V

perl -V
Summary of my perl5 (revision 5 version 14 subversion 2) configuration:

 Platform:
   osname=freebsd, osvers=10.0-current, archname=amd64-freebsd
   uname='freebsd head.labs.multiplay.co.uk 10.0-current freebsd 10.0-current #0: fri apr 19 20:51:53 utc 2013 
r...@head.labs.multiplay.co.uk:usrobjusrhomesmhfreebsdbaseheadsysgeneric amd64 '
   config_args='-sde -Dprefix=/usr/local -Darchlib=/usr/local/lib/perl5/5.14.2/mach -Dprivlib=/usr/local/lib/perl5/5.14.2 -Dman3dir=/usr/local/lib/perl5/5.14.2/perl/man/man3 
-Dman1dir=/usr/local/man/man1 -Dsitearch=/usr/local/lib/perl5/site_perl/5.14.2/mach -Dsitelib=/usr/local/lib/perl5/site_perl/5.14.2 
-Dscriptdir=/usr/local/bin -Dsiteman3dir=/usr/local/lib/perl5/5.14.2/man/man3 -Dsiteman1dir=/usr/local/man/man1 -Ui_malloc -Ui_iconv 
-Uinstallusrbinperl -Dcc=cc -Duseshrplib -Dinc_version_list=none -Dccflags=-DAPPLLIB_EXP=/usr/local/lib/perl5/5.14.2/BSDPAN -Doptimize=-O2 
-pipe -fno-strict-aliasing -Ui_gdbm -Dusethreads=n -Dusemymalloc=n -Duse64bitint'

   hint=recommended, useposix=true, d_sigaction=define
   useithreads=undef, usemultiplicity=undef
   useperlio=define, d_sfio=undef, uselargefiles=define, usesocks=undef
   use64bitint=define, use64bitall=define, uselongdouble=undef
   usemymalloc=n, bincompat5005=undef
 Compiler:
   cc='cc', ccflags 
='-DAPPLLIB_EXP=/usr/local/lib/perl5/5.14.2/BSDPAN -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -fstack-protector 
-I/usr/local/include',

   optimize='-O2 -pipe -fno-strict-aliasing',
   cppflags='-DAPPLLIB_EXP=/usr/local/lib/perl5/5.14.2/BSDPAN -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe  
-fstack-protector -I/usr/local/include'

   ccversion='', gccversion='4.2.1 Compatible FreeBSD Clang 3.3 (trunk 
178860)', gccosandvers=''
   intsize=4, longsize=8, ptrsize=8, doublesize=8, byteorder=12345678
   d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=16
   ivtype='long', ivsize=8, nvtype='double', nvsize=8, Off_t='off_t', 
lseeksize=8
   alignbytes=8, prototype=define
 Linker and Libraries:
   ld='cc', ldflags ='-pthread -Wl,-E  -fstack-protector -L/usr/local/lib'
   libpth=/usr/lib /usr/local/lib
   libs=-lm -lcrypt -lutil
   perllibs=-lm -lcrypt -lutil
   libc=, so=so, useshrplib=true, libperl=libperl.so
   gnulibc_version=''
 Dynamic Linking:
   dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='  
-Wl,-R/usr/local/lib/perl5/5.14.2/mach/CORE'
   cccdlflags='-DPIC -fPIC', lddlflags='-shared  -L/usr/local/lib 
-fstack-protector'


Characteristics of this binary (from libperl):
 Compile-time options: PERL_DONT_CREATE_GVSV PERL_MALLOC_WRAP
   PERL_PRESERVE_IVUV USE_64_BIT_ALL USE_64_BIT_INT
   USE_LARGE_FILES USE_PERLIO USE_PERL_ATOF
 Built under freebsd
 Compiled at Apr 19 2013 22:39:40
 @INC:
   /usr/local/lib/perl5/5.14.2/BSDPAN
   /usr/local/lib/perl5/site_perl/5.14.2/mach
   /usr/local/lib/perl5/site_perl/5.14.2
   /usr/local/lib/perl5/5.14.2/mach
   /usr/local/lib/perl5/5.14.2


3. cat /etc/make.conf


cat /etc/make.conf
# Ports
WRKDIRPREFIX?=/data/portbuild
PACKAGES=/data/packages
WITHOUT_X11=1
WITHOUT_DOCS=1
WITHOUT_EXAMPLES=1
# added by use.perl 2013-04-19 22:42:57
PERL_VERSION=5.14.2

Another piece of info which may well be relavent:-
uname -a
FreeBSD  11.0-CURRENT FreeBSD 11.0-CURRENT #98 r256886:256889M:

The system is hence using pkgng by default.

   Regards
   Steve 




This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.

___
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: Possible fix for all p5-* port installs being broken on FreeBSD

[Steven Hartland]

Just to be clear that was with the patch applied, without it I get:-

make -C /usr/ports/converters/p5-Encode-Locale/ -VPERL_VERSION -VPERL_VER 
-VMAN3PREFIX -VSITE_PERL -VSITE_PERL_REL
5.14.2
5.14
/usr/local/lib/perl5/5.14
/usr/local/lib/perl5/site_perl/5.14
lib/perl5/site_perl/5.14

   Regards
   Steve

- Original Message - 
From: Steven Hartland kill...@multiplay.co.uk

To: Andrej Zverev a...@freebsd.org
Cc: Sunpoet Po-Chuan Hsieh sunp...@freebsd.org; ports po...@freebsd.org
Sent: Friday, October 25, 2013 5:17 PM
Subject: Re: Possible fix for all p5-* port installs being broken on FreeBSD




- Original Message - 
From: Andrej Zverev a...@freebsd.org



Can you please show output (you can pastebin it somewhere)
1. make -C /usr/ports/converters/p5-Encode-Locale/ -VPERL_VERSION
-VPERL_VER -VMAN3PREFIX -VSITE_PERL -VSITE_PERL_REL

make -C /usr/ports/converters/p5-Encode-Locale/ -VPERL_VERSION -VPERL_VER 
-VMAN3PREFIX -VSITE_PERL -VSITE_PERL_REL
5.14.2
5.14
/usr/local/lib/perl5/5.14.2
/usr/local/lib/perl5/site_perl/5.14.2
lib/perl5/site_perl/5.14.2


2. perl -V

perl -V
Summary of my perl5 (revision 5 version 14 subversion 2) configuration:

 Platform:
   osname=freebsd, osvers=10.0-current, archname=amd64-freebsd
   uname='freebsd head.labs.multiplay.co.uk 10.0-current freebsd 10.0-current #0: fri apr 19 20:51:53 utc 2013 
r...@head.labs.multiplay.co.uk:usrobjusrhomesmhfreebsdbaseheadsysgeneric amd64 '
   config_args='-sde -Dprefix=/usr/local -Darchlib=/usr/local/lib/perl5/5.14.2/mach -Dprivlib=/usr/local/lib/perl5/5.14.2 -Dman3dir=/usr/local/lib/perl5/5.14.2/perl/man/man3 
 -Dman1dir=/usr/local/man/man1 -Dsitearch=/usr/local/lib/perl5/site_perl/5.14.2/mach -Dsitelib=/usr/local/lib/perl5/site_perl/5.14.2 
 -Dscriptdir=/usr/local/bin -Dsiteman3dir=/usr/local/lib/perl5/5.14.2/man/man3 -Dsiteman1dir=/usr/local/man/man1 -Ui_malloc -Ui_iconv 
 -Uinstallusrbinperl -Dcc=cc -Duseshrplib -Dinc_version_list=none -Dccflags=-DAPPLLIB_EXP=/usr/local/lib/perl5/5.14.2/BSDPAN -Doptimize=-O2 
 -pipe -fno-strict-aliasing -Ui_gdbm -Dusethreads=n -Dusemymalloc=n -Duse64bitint'

   hint=recommended, useposix=true, d_sigaction=define
   useithreads=undef, usemultiplicity=undef
   useperlio=define, d_sfio=undef, uselargefiles=define, usesocks=undef
   use64bitint=define, use64bitall=define, uselongdouble=undef
   usemymalloc=n, bincompat5005=undef
 Compiler:
   cc='cc', ccflags 
='-DAPPLLIB_EXP=/usr/local/lib/perl5/5.14.2/BSDPAN -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -fstack-protector 
 -I/usr/local/include',

   optimize='-O2 -pipe -fno-strict-aliasing',

  cppflags='-DAPPLLIB_EXP=/usr/local/lib/perl5/5.14.2/BSDPAN -DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe  
 -fstack-protector -I/usr/local/include'

   ccversion='', gccversion='4.2.1 Compatible FreeBSD Clang 3.3 (trunk 
178860)', gccosandvers=''
   intsize=4, longsize=8, ptrsize=8, doublesize=8, byteorder=12345678
   d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=16
   ivtype='long', ivsize=8, nvtype='double', nvsize=8, Off_t='off_t', 
lseeksize=8
   alignbytes=8, prototype=define
 Linker and Libraries:
   ld='cc', ldflags ='-pthread -Wl,-E  -fstack-protector -L/usr/local/lib'
   libpth=/usr/lib /usr/local/lib
   libs=-lm -lcrypt -lutil
   perllibs=-lm -lcrypt -lutil
   libc=, so=so, useshrplib=true, libperl=libperl.so
   gnulibc_version=''
 Dynamic Linking:
   dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='  
-Wl,-R/usr/local/lib/perl5/5.14.2/mach/CORE'
   cccdlflags='-DPIC -fPIC', lddlflags='-shared  -L/usr/local/lib 
-fstack-protector'


Characteristics of this binary (from libperl):
 Compile-time options: PERL_DONT_CREATE_GVSV PERL_MALLOC_WRAP
   PERL_PRESERVE_IVUV USE_64_BIT_ALL USE_64_BIT_INT
   USE_LARGE_FILES USE_PERLIO USE_PERL_ATOF
 Built under freebsd
 Compiled at Apr 19 2013 22:39:40
 @INC:
   /usr/local/lib/perl5/5.14.2/BSDPAN
   /usr/local/lib/perl5/site_perl/5.14.2/mach
   /usr/local/lib/perl5/site_perl/5.14.2
   /usr/local/lib/perl5/5.14.2/mach
   /usr/local/lib/perl5/5.14.2


3. cat /etc/make.conf


cat /etc/make.conf
# Ports
WRKDIRPREFIX?=/data/portbuild
PACKAGES=/data/packages
WITHOUT_X11=1
WITHOUT_DOCS=1
WITHOUT_EXAMPLES=1
# added by use.perl 2013-04-19 22:42:57
PERL_VERSION=5.14.2

Another piece of info which may well be relavent:-
uname -a
FreeBSD  11.0-CURRENT FreeBSD 11.0-CURRENT #98 r256886:256889M:

The system is hence using pkgng by default.

   Regards
   Steve


This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the 
event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any 
information contained in it.

In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to postmas

Re: Possible fix for all p5-* port installs being broken on FreeBSD

[Steven Hartland]

Ahh I see, sorry totally read that the wrong way round :(

I never expected it to go from MAJOR.MINOR.REV - MAJOR.MINOR
as we've had issues in the past with REV changes so would
definitely need to keep the old structure.

We'll maintain this patch locally instead.

Thanks for info, sorry again for the noise.

   Regards
   Steve

- Original Message - 
From: Andrej Zverev a...@freebsd.org




Well,  your perl -V output show what you have old structures.

Can you follow this entry in ports/UPDATING also before rebuild remove
all your home patches. This is your issue.

20130612:
 AFFECTS: users of lang/perl* and any port that depends on it
 AUTHOR: a...@freebsd.org

 The directory structure where Perl is installed has also been modified:
 major.minor is now used instead of major.minor.patchlevel.
 The perl-after-upgrade script has been removed.
 Please rebuild all Perl ports and all ports that depend on it:
 # portmaster -r perl
   or
 # portupgrade -rf perl
   or
 # pkg install -fR perl



On Fri, Oct 25, 2013 at 8:25 PM, Steven Hartland
kill...@multiplay.co.uk wrote:

Just to be clear that was with the patch applied, without it I get:-


make -C /usr/ports/converters/p5-Encode-Locale/ -VPERL_VERSION -VPERL_VER
-VMAN3PREFIX -VSITE_PERL -VSITE_PERL_REL
5.14.2
5.14
/usr/local/lib/perl5/5.14
/usr/local/lib/perl5/site_perl/5.14
lib/perl5/site_perl/5.14

   Regards
   Steve

- Original Message - From: Steven Hartland
kill...@multiplay.co.uk
To: Andrej Zverev a...@freebsd.org

Cc: Sunpoet Po-Chuan Hsieh sunp...@freebsd.org; ports
po...@freebsd.org
Sent: Friday, October 25, 2013 5:17 PM

Subject: Re: Possible fix for all p5-* port installs being broken on FreeBSD




- Original Message - From: Andrej Zverev a...@freebsd.org


Can you please show output (you can pastebin it somewhere)
1. make -C /usr/ports/converters/p5-Encode-Locale/ -VPERL_VERSION
-VPERL_VER -VMAN3PREFIX -VSITE_PERL -VSITE_PERL_REL


make -C /usr/ports/converters/p5-Encode-Locale/ -VPERL_VERSION -VPERL_VER
-VMAN3PREFIX -VSITE_PERL -VSITE_PERL_REL
5.14.2
5.14
/usr/local/lib/perl5/5.14.2
/usr/local/lib/perl5/site_perl/5.14.2
lib/perl5/site_perl/5.14.2


2. perl -V


perl -V
Summary of my perl5 (revision 5 version 14 subversion 2) configuration:

 Platform:
   osname=freebsd, osvers=10.0-current, archname=amd64-freebsd
   uname='freebsd head.labs.multiplay.co.uk 10.0-current freebsd
10.0-current #0: fri apr 19 20:51:53 utc 2013
r...@head.labs.multiplay.co.uk:usrobjusrhomesmhfreebsdbaseheadsysgeneric
amd64 '
   config_args='-sde -Dprefix=/usr/local
-Darchlib=/usr/local/lib/perl5/5.14.2/mach
-Dprivlib=/usr/local/lib/perl5/5.14.2
-Dman3dir=/usr/local/lib/perl5/5.14.2/perl/man/man3
-Dman1dir=/usr/local/man/man1
-Dsitearch=/usr/local/lib/perl5/site_perl/5.14.2/mach
-Dsitelib=/usr/local/lib/perl5/site_perl/5.14.2  -Dscriptdir=/usr/local/bin
-Dsiteman3dir=/usr/local/lib/perl5/5.14.2/man/man3
-Dsiteman1dir=/usr/local/man/man1 -Ui_malloc -Ui_iconv  -Uinstallusrbinperl
-Dcc=cc -Duseshrplib -Dinc_version_list=none
-Dccflags=-DAPPLLIB_EXP=/usr/local/lib/perl5/5.14.2/BSDPAN -Doptimize=-O2
-pipe -fno-strict-aliasing -Ui_gdbm -Dusethreads=n -Dusemymalloc=n
-Duse64bitint'
   hint=recommended, useposix=true, d_sigaction=define
   useithreads=undef, usemultiplicity=undef
   useperlio=define, d_sfio=undef, uselargefiles=define, usesocks=undef
   use64bitint=define, use64bitall=define, uselongdouble=undef
   usemymalloc=n, bincompat5005=undef
 Compiler:
   cc='cc', ccflags ='-DAPPLLIB_EXP=/usr/local/lib/perl5/5.14.2/BSDPAN
-DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe
-fstack-protector  -I/usr/local/include',
   optimize='-O2 -pipe -fno-strict-aliasing',

  cppflags='-DAPPLLIB_EXP=/usr/local/lib/perl5/5.14.2/BSDPAN
-DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe
-fstack-protector -I/usr/local/include'
   ccversion='', gccversion='4.2.1 Compatible FreeBSD Clang 3.3 (trunk
178860)', gccosandvers=''
   intsize=4, longsize=8, ptrsize=8, doublesize=8, byteorder=12345678
   d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=16
   ivtype='long', ivsize=8, nvtype='double', nvsize=8, Off_t='off_t',
lseeksize=8
   alignbytes=8, prototype=define
 Linker and Libraries:
   ld='cc', ldflags ='-pthread -Wl,-E  -fstack-protector -L/usr/local/lib'
   libpth=/usr/lib /usr/local/lib
   libs=-lm -lcrypt -lutil
   perllibs=-lm -lcrypt -lutil
   libc=, so=so, useshrplib=true, libperl=libperl.so
   gnulibc_version=''
 Dynamic Linking:
   dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='
-Wl,-R/usr/local/lib/perl5/5.14.2/mach/CORE'
   cccdlflags='-DPIC -fPIC', lddlflags='-shared  -L/usr/local/lib
-fstack-protector'


Characteristics of this binary (from libperl):
 Compile-time options: PERL_DONT_CREATE_GVSV PERL_MALLOC_WRAP
   PERL_PRESERVE_IVUV USE_64_BIT_ALL USE_64_BIT_INT
   USE_LARGE_FILES USE_PERLIO USE_PERL_ATOF
 Built under freebsd
 Compiled at Apr 19 2013 22:39

Re: Possible fix for all p5-* port installs being broken on FreeBSD

[Steven Hartland]

I think it would a good idea to check it out again yes, but TBH
we would never update perl without reinstalling all ports anyway.

In our currently situation, having to reinstall basically every
port on all the machines just to add a simple perl module is
something we'd also rather avoid ;-)

   Regards
   Steve
- Original Message - 
From: Andrej Zverev a...@freebsd.org




You are welcome.
With your patch after every Perl update you will have to rebuild or
move at least all the p5 ports (since SITE_PERL x.y.z where z is
moving).

I can only recommed to look at the situation again. Maybe the old
problems have been solved and you just need to try again (with 5.14.4
or 5.16 which is now the default).

On Fri, Oct 25, 2013 at 9:35 PM, Steven Hartland

Ahh I see, sorry totally read that the wrong way round :(

I never expected it to go from MAJOR.MINOR.REV - MAJOR.MINOR
as we've had issues in the past with REV changes so would
definitely need to keep the old structure.

We'll maintain this patch locally instead.

Thanks for info, sorry again for the noise.




This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.

___
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: accidently removed /usr/ports/.svn/pristine

[Steven Hartland]

Delete you ports directory and redownload it.
- Original Message - 
From: Marco Beishuizen mb...@xs4all.nl

To: freebsd-ports@freebsd.org
Sent: Sunday, October 13, 2013 5:14 PM
Subject: accidently removed /usr/ports/.svn/pristine



Hi,

I thought that I could safely remove the /usr/ports/.svn/pristine 
directory. But that wasn't the case so now updating the ports tree with 
svn doesn't work anymore.


Is there a way to repair the damage? I reinstalled subversion but that 
wasn't enough.


Thanks,

Marco

--
Eat, drink, and be merry!  Tomorrow you may be in Utah.
___
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




This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.

___
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

No valid mirrors for mysql56?

[Steven Hartland]

Seems there are currently no valid mirrors for the mysql56 port:-


=== Fetching all distfiles required by mysql-server-5.6.12 for building
===  Extracting for mysql-server-5.6.12
= SHA256 Checksum mismatch for mysql-5.6.12.tar.gz.
===  Refetch for 1 more times files: mysql-5.6.12.tar.gz
= mysql-5.6.12.tar.gz doesn't seem to exist in /usr/ports/distfiles/.
= Attempting to fetch 
ftp://ftp.fi.muni.cz/pub/mysql/Downloads/MySQL-5.6/mysql-5.6.12.tar.gz
fetch: ftp://ftp.fi.muni.cz/pub/mysql/Downloads/MySQL-5.6/mysql-5.6.12.tar.gz: 
Unknown FTP error
= Attempting to fetch 
http://mysql.mirrors.cybercity.dk/Downloads/MySQL-5.6/mysql-5.6.12.tar.gz
fetch: 
http://mysql.mirrors.cybercity.dk/Downloads/MySQL-5.6/mysql-5.6.12.tar.gz: No 
route to host
= Attempting to fetch 
ftp://ftp.fh-wolfenbuettel.de/pub/database/mysql/Downloads/MySQL-5.6/mysql-5.6.12.tar.gz
fetch: 
ftp://ftp.fh-wolfenbuettel.de/pub/database/mysql/Downloads/MySQL-5.6/mysql-5.6.12.tar.gz:
 Unknown FTP error
= Attempting to fetch 
ftp://ftp.gwdg.de/pub/misc/mysql/Downloads/MySQL-5.6/mysql-5.6.12.tar.gz
fetch: mysql-5.6.12.tar.gz: local file (35876046 bytes) is longer than remote 
file (35853760 bytes)
= Attempting to fetch 
http://netmirror.org/mirror/mysql.com/Downloads/MySQL-5.6/mysql-5.6.12.tar.gz
fetch: 
http://netmirror.org/mirror/mysql.com/Downloads/MySQL-5.6/mysql-5.6.12.tar.gz: 
Not Found
= Attempting to fetch 
ftp://netmirror.org/mysql.com/Downloads/MySQL-5.6/mysql-5.6.12.tar.gz
fetch: ftp://netmirror.org/mysql.com/Downloads/MySQL-5.6/mysql-5.6.12.tar.gz: 
Protocol error
= Attempting to fetch 
http://mirrors.ntua.gr/MySQL/Downloads/MySQL-5.6/mysql-5.6.12.tar.gz
fetch: http://mirrors.ntua.gr/MySQL/Downloads/MySQL-5.6/mysql-5.6.12.tar.gz: 
Requested Range Not Satisfiable
= Attempting to fetch 
ftp://ftp.ntua.gr/pub/databases/mysql/Downloads/MySQL-5.6/mysql-5.6.12.tar.gz
fetch: mysql-5.6.12.tar.gz: local file (35876046 bytes) is longer than remote 
file (35853760 bytes)
= Attempting to fetch 
http://mysql.sote.hu/Downloads/MySQL-5.6/mysql-5.6.12.tar.gz
fetch: http://mysql.sote.hu/Downloads/MySQL-5.6/mysql-5.6.12.tar.gz: No address 
record
= Attempting to fetch 
ftp://ftp.rhnet.is/pub/mysql/Downloads/MySQL-5.6/mysql-5.6.12.tar.gz
fetch: ftp://ftp.rhnet.is/pub/mysql/Downloads/MySQL-5.6/mysql-5.6.12.tar.gz: 
File unavailable (e.g., file not found, no access)
= Attempting to fetch 
ftp://mirror.widexs.nl/pub/mysql/Downloads/MySQL-5.6/mysql-5.6.12.tar.gz
fetch: ftp://mirror.widexs.nl/pub/mysql/Downloads/MySQL-5.6/mysql-5.6.12.tar.gz: File unavailable (e.g., file not found, no 
access)

= Attempting to fetch 
ftp://mirror.switch.ch/mirror/mysql/Downloads/MySQL-5.6/mysql-5.6.12.tar.gz
fetch: mysql-5.6.12.tar.gz: local file (35876046 bytes) is longer than remote 
file (35853760 bytes)
= Attempting to fetch 
http://mysql.dp.ua/Downloads/MySQL-5.6/mysql-5.6.12.tar.gz
fetch: http://mysql.dp.ua/Downloads/MySQL-5.6/mysql-5.6.12.tar.gz: Not Found
= Attempting to fetch 
http://mysql.mirrored.ca/Downloads/MySQL-5.6/mysql-5.6.12.tar.gz
fetch: http://mysql.mirrored.ca/Downloads/MySQL-5.6/mysql-5.6.12.tar.gz: size 
mismatch: expected 35853760, actual 51
= Attempting to fetch 
ftp://mirror.services.wisc.edu/mirrors/mysql/Downloads/MySQL-5.6/mysql-5.6.12.tar.gz
fetch: 
ftp://mirror.services.wisc.edu/mirrors/mysql/Downloads/MySQL-5.6/mysql-5.6.12.tar.gz:
 No address record
= Attempting to fetch 
http://mysql.mirrors.pair.com/Downloads/MySQL-5.6/mysql-5.6.12.tar.gz
fetch: http://mysql.mirrors.pair.com/Downloads/MySQL-5.6/mysql-5.6.12.tar.gz: 
Requested Range Not Satisfiable
= Attempting to fetch 
ftp://ftp.linorg.usp.br/mysql/Downloads/MySQL-5.6/mysql-5.6.12.tar.gz
fetch: ftp://ftp.linorg.usp.br/mysql/Downloads/MySQL-5.6/mysql-5.6.12.tar.gz: 
No address record
= Attempting to fetch 
ftp://ftp.cbn.net.id/mirror/mysql/Downloads/MySQL-5.6/mysql-5.6.12.tar.gz
fetch: ftp://ftp.cbn.net.id/mirror/mysql/Downloads/MySQL-5.6/mysql-5.6.12.tar.gz: File unavailable (e.g., file not found, no 
access)

= Attempting to fetch 
ftp://ftp.easynet.be/mysql/Downloads/MySQL-5.6/mysql-5.6.12.tar.gz
fetch: ftp://ftp.easynet.be/mysql/Downloads/MySQL-5.6/mysql-5.6.12.tar.gz: 
Unknown FTP error
= Attempting to fetch 
http://download.softagency.net/MySQL/Downloads/MySQL-5.6/mysql-5.6.12.tar.gz
fetch: mysql-5.6.12.tar.gz: local file (35876046 bytes) is longer than remote 
file (35853760 bytes)
= Attempting to fetch 
ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/mysql-5.6.12.tar.gz
fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/mysql-5.6.12.tar.gz: 
size mismatch: expected 35853760, actual 35876046
= Couldn't fetch it - please try to retrieve this
= port manually into /usr/ports/distfiles/ and try again.
*** Error code 1

Stop in /usr/ports/databases/mysql56-server.
*** Error code 1

Stop in /usr/ports/databases/mysql56-server.

   Regards
   Steve 


___
freebsd-ports@freebsd.org mailing list

Re: No valid mirrors for mysql56?

[Steven Hartland]

- Original Message - 
From: John Marshall john.marsh...@riverwillow.com.au

..

= Couldn't fetch it - please try to retrieve this
= port manually into /usr/ports/distfiles/ and try again.
*** Error code 1


So the problem is not that it isn't available, the problem is that the
software you're using won't fetch it.

Delete (or rename) the existing copy from /usr/ports/distfiles and try
again.


Good catch, I spotted the file size difference error but assumed this
was moaning about the new copy it was downloading and not an
existing copy.

Seems for some reason mysql-5.6.12.tar.gz has changed sizes
and checksums since I last downloaded and after updating ports
from svn it was expecting a new version of the file without a change
in filename, hence the issue.

Seems odd that the ports system wouldn't catch this and delete
the bad original before trying to re-download or forcing an overwrite
on download.

   Regards
   Steve


This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.

___
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

New Port Options infrastructure bug

[Steven Hartland]

I've just been looking at devel/rubygem-multi_json and was
perplexed by how it wasn't saving my options.

It seems that how the new port options infrastructure determines
where to load and store its configured options from is quite
flaky and breaks with anything that amends PKGNAMEPREFIX within
a sub Makefile such as python, ruby etc.

Having searched long for the issue it seems lots of ports
are having to work-around this problem as indicated by
comments such as:-

# bypass infrastructure bug (taken from www/py-django)
OPTIONSFILE=${PORT_DBDIR}/py-${PORTNAME}/options

Is this a know issue which has someone is working on it or are
port creators being left deal with this on a case by case
basis?

Obviously its extremely frustrating from a user perspective
to find out that the options chosen aren't actually being
applied as they are failing to save / load :(

   Regards
   Steve


This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.

___
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: [HEADS-UP] Announcing the end of port CVS

[Steven Hartland]

- Original Message - 
From: Erich Dollansky erichfreebsdl...@ovitrap.com



 What if neither is close to me (there are other countries in the
 world, not only USA, some are even on the other side of the planet,
 btw, did you know?) ?

Yes, I am quite aware of it, but I am merely the messenger. Until
other subversion mirrors are made available in other parts of the
world, only the two in the US are available. I'm sure that will change
in time, but for the moment, only the two US mirrors have been
announced.


why stop a system then when the replacement is not up and running? Do
you want to kill the infrastructure to distribute FreeBSD?


Looking at it from the practical side if the replacement architecture
isn't ready yet then it sounds like this needs to be delayed until
such a time that it is.

Only having two mirrors and both in the US is not really practical,
many of us, in other parts of the globe, will suffer from stupidly
long update times; BDP would really have a bad effect on updates,
and that's assuming the two servers don't just die under the load of
everyone using them.

So again please consider delaying the switch over until a decent mirror
set is available, in order to prevent serious amounts of frustration
from your user base.

   Regards
   Steve


This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.

___
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: [FreeBSD-Announce] Announcing the end of port CVS

[Steven Hartland]

Moved discussion to freebsd-ports...

- Original Message - 
From: Beat Gaetzi b...@freebsd.org

portsnap also doesn't appear to provide feature compatibility
with csup, specifically it states in the man page that it
deletes unknown files and restore modified files to their
unmodified state.

This makes maintaining custom patches very hard. Is there an
option to disable this behaviour?


You can blacklist custom ports with a REFUSE line in portsnap.conf or
use a Subversion checkout to maintain your local modifications.


Is there no way to tell it not to delete unknown files so we
don't have to add addional steps to the workflow flow of adding
additional patches to local port builds?

I appreciate things must move forward but this seems like a step
backwards in terms of functionality :(


Also where is the local mirrors list for portsnap as I can't
find anything like the mirrors list for cvsup e.g.
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html#CVSUP-MIRRORS


Mirrors for portsnap are selected using geolocation:
http://www.daemonology.net/blog/2012-05-20-portsnap-geolocation.html


Not wishing to be a pain but its often the case that simple
geolocation fails to be optimal due to load network paths etc,
is there a list of the available sites so we can test and use
the best mirror for us?

   Regards
   Steve




This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.

___
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

php5 broken by commit from yesterday?

[Steven Hartland]

Seems the following commit broke php5
http://www.freebsd.org/cgi/cvsweb.cgi/ports/lang/php5/files/patch-sapi_fpm_Makefile.frag.diff?r1=1.1;r2=1.2;f=h

The port now fails to build with:-
libtool: link: `sapi/fpm/fpm/fastcgi.lo' is not a valid libtool object

I suspect the change meant to add this additional fix to the Makefile
patch but instead replaced it.

   Regards
   Steve


This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.

___
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: Cannot install PEAR (again)

[Steven Hartland]

You most likely have php built without threaded support, which will cause
random crashes when used with extensions that are linked against threaded
libs.

Rebuilding php and all extensions with LINKTHR selected will likely fix your 
issue.

   Regards
   Steve
- Original Message - 
From: Andrea Venturoli m...@netfence.it

To: m...@freebsd.org; a...@freebsd.org; freebsd-ports@FreeBSD.org
Sent: Thursday, January 12, 2012 9:14 AM
Subject: Cannot install PEAR (again)



Hello.

I've had this problem in the past, but eventually always got out of it.
I also see many other people reporting this, usually with some hint on how to work around it, but no real solution. I've tried 
all the suggestion I found, but still it doesn't work and I would appreciate if I could sort this out once and for all.


 #uname -a
FreeBSD x..xx 7.3-RELEASE-p9 FreeBSD 7.3-RELEASE-p9 #3: Tue Jan  3 09:33:25 CET 2012 
r...@x..xx:/usr/obj/usr/src/sys/X  amd64

# pkg_info|grep php
php5-5.3.8  PHP Scripting Language
php5-ctype-5.3.8The ctype shared extension for php
php5-dom-5.3.8  The dom shared extension for php
php5-filter-5.3.8   The filter shared extension for php
php5-gd-5.3.8   The gd shared extension for php
php5-gettext-5.3.8  The gettext shared extension for php
php5-hash-5.3.8 The hash shared extension for php
php5-iconv-5.3.8The iconv shared extension for php
php5-imap-5.3.8 The imap shared extension for php
php5-json-5.3.8 The json shared extension for php
php5-mbstring-5.3.8 The mbstring shared extension for php
php5-mysql-5.3.8The mysql shared extension for php
php5-openssl-5.3.8  The openssl shared extension for php
php5-pdo-5.3.8  The pdo shared extension for php
php5-pdo_pgsql-5.3.8 The pdo_pgsql shared extension for php
php5-session-5.3.8  The session shared extension for php
php5-simplexml-5.3.8 The simplexml shared extension for php
php5-xml-5.3.8  The xml shared extension for php
php5-zip-5.3.8  The zip shared extension for php
php5-zlib-5.3.8 The zlib shared extension for php
# cd /usr/ports/devel/pear/
# make install
===  License check disabled, port has not defined LICENSE
===  Extracting for pear-1.9.4_1
= SHA256 Checksum OK for pear-1.9.4.tar.bz2.
===  Patching for pear-1.9.4_1
===  Applying FreeBSD patches for pear-1.9.4_1
===  Configuring for pear-1.9.4_1
===  Installing for pear-1.9.4_1
===   pear-1.9.4_1 depends on file: /usr/local/include/php/main/php.h - found
===   pear-1.9.4_1 depends on file: /usr/local/lib/php/20090626-debug/xml.so - 
found
===   Generating temporary packing list
===  Checking if devel/pear already installed

Bootstrapping Installer...
Using previously install ... ok

Extracting installer..
PHP Deprecated:  Function set_magic_quotes_runtime() is deprecated in 
/usr/local/share/pear/PEAR/DependencyDB.php on line 554
PHP Deprecated:  Function set_magic_quotes_runtime() is deprecated in 
/usr/local/share/pear/PEAR/DependencyDB.php on line 558
Using previously installed installer ... ok

Preparing installer..
PHP Deprecated:  Assigning the return value of new by reference is deprecated in /usr/local/share/pear/PEAR/Command.php on line 
137
PHP Deprecated:  Assigning the return value of new by reference is deprecated in /usr/local/share/pear/PEAR/Command.php on line 
154
PHP Deprecated:  Assigning the return value of new by reference is deprecated in /usr/local/share/pear/PEAR/Frontend.php on 
line 91

PHP Deprecated:  Function set_magic_quotes_runtime() is deprecated in 
/usr/local/share/pear/PEAR/Config.php on line 1026
PHP Deprecated:  Function set_magic_quotes_runtime() is deprecated in 
/usr/local/share/pear/PEAR/Config.php on line 1033
PHP Deprecated:  Function set_magic_quotes_runtime() is deprecated in 
/usr/local/share/pear/PEAR/Registry.php on line 1179
PHP Deprecated:  Function set_magic_quotes_runtime() is deprecated in 
/usr/local/share/pear/PEAR/Registry.php on line 1183
PHP Deprecated:  Assigning the return value of new by reference is deprecated in /usr/local/share/pear/PEAR/ChannelFile.php on 
line 199
PHP Deprecated:  Assigning the return value of new by reference is deprecated in /usr/local/share/pear/PEAR/ChannelFile.php on 
line 1504
PHP Deprecated:  Assigning the return value of new by reference is deprecated in /usr/local/share/pear/PEAR/ChannelFile.php on 
line 1516
PHP Deprecated:  Assigning the return value of new by reference is deprecated in /usr/local/share/pear/PEAR/ChannelFile.php on 
line 1524
PHP Deprecated:  Assigning the return value of new by reference is deprecated in /usr/local/share/pear/PEAR/ChannelFile.php on 
line 1527
PHP Deprecated:  Assigning the return value of new by reference is deprecated in /usr/local/share/pear/PEAR/Common.php on line 
492
PHP Deprecated:  Assigning the return value of new by reference is deprecated in /usr/local/share/pear/PEAR/Common.php on line 
511
PHP Deprecated:  Assigning the 

Re: php5-5.3.6_1 with Segmentation fault (amd64)

[Steven Hartland]

- Original Message - 
From: Alex Dupre a...@freebsd.org


The issue is very complex, it depends on many factors (FreeBSD version, 
calling program, extensions loaded, ports options, etc.). In short 
words, dlopening and dlclosing libthr is bad. The final and definitive 
solution would be a libc including libthr (if I'm not wrong there was a 
plan to do it). A less drastic solution would be to link to libthr every 
program that dlopen() uncontrolled libraries (i.e. apache, php, etc.). 
I've already proposed this change, but was considered too risky at that 
time. So, for now, you have to live with the LINKTHR php option that 
does its best to make all happy.


We'll I've not managed to get a working php from the default settings
for a while now. Even core php requires libxml which is using libthr
so I would suggest LINKTHR needs to be set by default. 


   Regards
   Steve


This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.

___
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: php5-5.3.6_1 with Segmentation fault (amd64)

[Steven Hartland]

- Original Message - 
From: Alex Dupre a...@freebsd.org




Steven Hartland ha scritto:

Even core php requires libxml which is using libthr
so I would suggest LINKTHR needs to be set by default.


That's false. I can assure you that I have all my php installations 
without LINKTHR, and I use complex php applications like roundcube.


Segv's on restart very regularly here and generally a php -m is also
enough to cause it too.

php + apache + php-extensions (standard selection) produces this
here, that's on 8.2-RELEASE

I agree you can run applications seemingly without issue, but apache
does have unexplained handler crashes and a restart really seem to
cause it problems recently.

   Regards
   Steve


This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.

___
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: php5-5.3.6_1 with Segmentation fault (amd64)

[Steven Hartland]

Rebuild with threads enabled, will likely fix all your problems.

Why the default is off I don't know but it conflicts with a
number of the main libs used e.g. libxml hence causing segvs
just as you described.

   Regards
   Steve
- Original Message - 
From: Luiz Gustavo S. Costa luizgust...@luizgustavo.pro.br

To: freebsd-ports@freebsd.org
Sent: Tuesday, June 28, 2011 5:53 PM
Subject: php5-5.3.6_1 with Segmentation fault (amd64)


Hey list !

exist some trouble with php and amd64 ? (last php from ports)


[root@gringo] ~# pkg_info | grep php5-5
php5-5.3.6_1PHP Scripting Language
[root@gringo] ~# php -v
Segmentation fault
[root@gringo] ~# php-fpm -h
Segmentation fault
[root@gringo] ~# which php-fpm
/usr/local/sbin/php-fpm
[root@gringo] ~# file /usr/local/sbin/php-fpm
/usr/local/sbin/php-fpm: ELF 64-bit LSB executable, x86-64, version 1
(FreeBSD), dynamically linked (uses shared libs), for FreeBSD 8.2, not
stripped
[root@gringo] ~# uname -a
FreeBSD gringo.mundounix.com.br 8.2-RELEASE FreeBSD 8.2-RELEASE #0:
Thu Feb 17 02:41:51 UTC 2011
r...@mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64


--
/\ Luiz Gustavo S. Costa
/ \ Programmer at BSD Perimeter
/ \ /\/\/\ Visit the pfSense Project
/ \ \ \ http://www.pfsense.org
-
BSD da serra carioca, Teresopolis (visite: http://miud.in/Inv)
Contatos: luizgust...@luizgustavo.pro.br / lgco...@pfsense.org
Blog: http://www.luizgustavo.pro.br
___
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



This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.

___
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

php Segmentation fault (core dumped) in xmlFreeMutex (how to fix)

[Steven Hartland]

Just wanted to share the follow so others can avoid the issues:-

Having just rebuilt a clean install of php 5.3.6 it was crashing
left right and center even a php -m caused it.

The stack looks like the following under gdb

#0 0x000103db8600 in ?? ()
#1 0x000100ce1a95 in xmlFreeMutex () from /usr/local/lib/libxml2.so.5
#2 0x000100ce14d5 in xmlCleanupGlobals () from /usr/local/lib/libxml2.so.5
#3 0x000100c79f4a in xmlCleanupParser () from /usr/local/lib/libxml2.so.5
#4 0x0044daa8 in php_libxml_shutdown ()
#5 0x0044dad9 in zm_shutdown_libxml ()
#6 0x0055289f in module_destructor ()
#7 0x00559be4 in zend_hash_apply_deleter ()
#8 0x00559e58 in zend_hash_graceful_reverse_destroy ()
#9 0x0054dfc8 in zend_shutdown ()
#10 0x004fbb9a in php_module_shutdown ()
#11 0x005d55e2 in main ()
#12 0x00417125 in _start ()

The problem is being caused by libxml2 under FreeBSD being compiled
as threaded by default where as php isn't.

The fix is simple select the LINKTHR option from make config and
recompile php and its modules to be safe.

Would suggest that the php port is updated to reflect this change
to avoid issues in the future.

   Regards
   Steve


This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.

___
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: databases/mysql55-server, Error: shared library mysqlclient.18 does not exist

[Steven Hartland]

- Original Message - 
From: L Campbell lcampb...@ironclad.mobi

To: a...@freebsd.org; po...@freebsd.org
Sent: Thursday, June 09, 2011 7:32 PM
Subject: databases/mysql55-server, Error: shared library mysqlclient.18 does 
not exist



For some reason, I can't compile databases/mysql55-server on a fresh
install; it errors out with

...

Works fine for me here Campbell, are you sure your ports are up to date 
properly?

locate libmysql |grep -v ports
/usr/local/lib/mysql/libmysqlclient.a
/usr/local/lib/mysql/libmysqlclient.so
/usr/local/lib/mysql/libmysqlclient.so.18
/usr/local/lib/mysql/libmysqlclient_r.a
/usr/local/lib/mysql/libmysqlclient_r.so
/usr/local/lib/mysql/libmysqlclient_r.so.18
/usr/local/lib/mysql/libmysqld.a
/usr/local/lib/mysql/libmysqlservices.a

   Regards
   Steve



This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.

___
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: mysql-client-5.5.10 fails to install properly, breaking all dependant ports

[Steven Hartland]

- Original Message - 
From: Patrick Powell papow...@astart.com
Try running mysql_update and mysql_install_db.  The last version of 
these died with error messages indicating they could not find 
executables.   The problem appeared to be that the scripts were 
generated with either null paths for the executable directories or the 
path was ./ (./data was one).   I suspect that the original script 
values did not

have entries for the paths.


I just updated here and no problems with mysql_upgrade there is
no mysql_update, I assume that was just a typo?

   Regards
   Steve


This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.

___
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: mysql-client-5.5.10 fails to install properly, breaking all dependant ports

[Steven Hartland]

- Original Message - 
From: Patrick Powell papow...@astart.com
My bad.  That was mysql_upgrade.  Sorry for the confusion.  How about 
mysql_install_db?


Can't test that I'm afraid as the machine is now in production. Might want
to make sure the old mysql pkg was removed correctly before the new
version was installed.

If you want to compare your version with the one we have I've uploaded
to: http://www.multiplaygameservers.com/dropzone/mysql_install_db.gz

Hope that helps.

   Regards
   Steve


This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.

___
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: lighttpd/1.4.28 + lighttpd-mod_h264_streaming won't start

[Steven Hartland]

Not really an answer to your problem but we've found nginx works very well
with this. Tried lighttpd and had no end of problems with it nginx just
works. If you switch to nginx I'd advise going with the dev version which
has quite a few new features and fixes and again never had any issues with.
/usr/ports/www/nginx-dev

   Regards
   Steve
- Original Message - 
From: Paul Macdonald p...@ifdnrg.com
After an update to lighttpd today, the server won't start with the 
mod_h264_streaming module (it does otherwise).


This was also the same on a fresh build on 8.1 release, (with the new 
lighttpd config format)


There's nothing in the error logs (other than reporting the server started!)

Anyone else seeing anything similar?




This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.

___
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: Fwd: Tomcat6 port keeps locking up??

[Steven Hartland]

- Original Message - 
From: Jeremy Chadwick

On Fri, Sep 17, 2010 at 12:19:00PM +0300, Andriy Gapon wrote:

on 17/09/2010 11:56 Jeremy Chadwick said the following:
 I don't think you understand how Solaris's VM behaves with ZFS.  It
 behaves very differently than FreeBSD.  On Solaris/OpenSolaris with ZFS,
 you'll see the ARC taking up as much memory as possible -- but unlike
 FreeBSD (AFAIK), when a userland or kernel application requires more
^
 memory, the Solaris kernel dynamically releases portions of the ARC.

Can you please explain that unlike part?


When ZFS was first introduced to FreeBSD, I was given the impression
from continual posts on the mailing lists that memory which was
allocated to the ARC was never released in the situation that a userland
program wanted memory.

An example scenario.  These numbers are in no way accurate given many
other things (network mbufs, UFS and VFS cache, etc.):

- amd64 system has 2GB physical RAM (assume ~1920MB usable)
- vm.kmem_size=1536M + vfs.zfs.arc_max=1400M
- Heavy ZFS I/O results in ARC maxing out at ~1400MB
- Userland application runs, requests malloc() of 1024MB
- Userland gets 384MB from physical RAM, remaining 640MB from swap
- ARC remains at 1400MB

Is this no longer the case?


My experience is no this is no longer the case at least on stable + patches
mentioned on thread:-
zfs very poor performance compared to ufs due to lack of cache?

   Regards
   Steve


This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.

___
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: Wordpress outputs an empty page after ports upgrade

[Steven Hartland]

- Original Message - 
From: Yuri y...@rawbw.com
No, look at ports-mgmt/portupgrade, it is capable of upgrading ports 
in-place quite happily in most cases. With the caveat that there might 
be some special steps that need to be taken not covered by port itself. 
This usually happens when dependencies split or being renamed or some 
other wild change that isn't covered by the standard process. But in the 
case of wordpress no special record has been placed into 
/usr/ports/UPDATING, which means that portupgrade should be sufficient.


I'm sorry but your wrong, as you can clearly see from the port Makefile.

Yes /usr/ports/UPDATING can be helpful but in this case the warning is
presented by the pre-everything target which you will likely miss if your
using portupgrade.

All portupgrade does is manage the process of uninstalling the old version
and installing the new version. So its generally fine for binary only
packages but for those that include data which needs special handling on
upgrade such as wordpress, perl, mysql etc you still need to do those
processes manually.

I'd suggest restoring you pre-upgrade backup of both files and db and 
perform a

manual upgrade as per the wordpress guide.
http://codex.wordpress.org/Upgrading_WordPress



This is quite unpractical with many packages installed on the system. 
Also WP has an embedded DB update process that is activated 
automatically when you first run after system upgrade. This makes manual 
upgrade redundant (at least theoretically).


Absolutely not, ALWAYS backup your data before each upgrade, its the only
way to be sure you don't loose things if something goes wrong.

In addition be especially careful with major version upgrades like 2.9 -
3.0 as they often have additional caveats.

   Regards
   Steve


This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.

___
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: Wordpress outputs an empty page after ports upgrade

[Steven Hartland]

- Original Message - 
From: Yuri y...@rawbw.com


No, no BUS or SEGFAULT.
My quick debugging didn't produce much results. This must be some 
robustness issue. It looks most likely like an issue in WP itself. So I 
filed the PR: http://core.trac.wordpress.org/ticket/14367


Sounds like an upgrade issue, possibly a broken theme or missing dependency.

We're running WP 3 on FreeBSD here without problem, although we don't use
the port as I don't really see the need for WP tbh as its so easy to install
anyway.

First things to check, apache etc error logs, revert to the standard theme
and go from there.

Saying it doesn't work doesn't help anyone help you ;-) You need to detail
what you have an haven't tried.

   Regards
   Steve


This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.

___
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: Wordpress outputs an empty page after ports upgrade

[Steven Hartland]

- Original Message - 
From: Yuri y...@rawbw.com

To: Steven Hartland kill...@multiplay.co.uk
Cc: Remko Lodder re...@elvandar.org; po...@freebsd.org
Sent: Tuesday, July 20, 2010 11:33 PM
Subject: Re: Wordpress outputs an empty page after ports upgrade



On 07/20/2010 15:15, Steven Hartland wrote:
Sounds like an upgrade issue, possibly a broken theme or missing 
dependency.


We're running WP 3 on FreeBSD here without problem, although we don't use
the port as I don't really see the need for WP tbh as its so easy to 
install

anyway.


port upgrades to the latest version automatically, this is the main benefit


I think you may have got the wrong end of the stick there. Ports can be used
to uninstall the old and install the new version yes, but I don't believe it
automates any of the upgrade process required for something like wordpress
for you.

I've had peek at the workpress Makefile and it has the following in it which
also indicates this is the case:-
If you want to upgrade, you must read upgrade document.

So if you've just used the port to upgade, then this is likely your your 
problem.

I'd suggest restoring you pre-upgrade backup of both files and db and perform a
manual upgrade as per the wordpress guide.
http://codex.wordpress.org/Upgrading_WordPress

   Regards
   Steve



This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.

___
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: Early CONFLICTS detection is POLA viloation?

[Steven Hartland]

Had the same here when trying to upgrade things, I don't want to
have to uninstall the current version before I can build the new
one only to find out there is some issue and have to roll back.

I've ended up commenting out the conflicts and ignoring them,
which I'm sure is not the desired behaviour :(

   Regards
   Steve


This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.

___
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: Help update audio/mumble to 1.2.0

[Steven Hartland]

It anyone's interested in a murmur12 port, the server component of mumble,
you can grab it from here:
http://gameservers.multiplay.co.uk/dropzone/freebsd-ports/murmur12.tar.gz

   Regards
   Steve

- Original Message - 
From: Marius Nünnerich mar...@nuenneri.ch

To: freebsd-ports@freebsd.org
Sent: Wednesday, December 23, 2009 6:12 PM
Subject: Help update audio/mumble to 1.2.0



Hi all,

I could use some help updating audio/mumble to version 1.2.0. The
current 1.1.8 worked for a while but after upgrading some other ports
(Qt related I guess) others can't here me anymore. Upgrading the port
to 1.2.0 doesn't help with this problem. I can't even hear others with
this version. With the following patch it builds, installs and
deinstalls fine.
http://nuenneri.ch/freebsd/mumble-1.2.0.patch

Anyone has an idea what to try? Anyone can test this against the
8.0-RELEASE set of the ports?
Thanks
Marius
___
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





This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.

___
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: Lighttpd 1.4.22/PHP 5.2.9 hardlocking the system

[Steven Hartland]

We had issues when running lighttpd which indicated an issue with kqueue.

Disabling lightttpd's use of kqueue using the following prevented this.
server.event-handler = poll

In the logger term we have moved to nginx.

   Regards
   Steve

- Original Message - 
From: Jacob Myers s...@whotookspaz.org

To: freebsd-ports@freebsd.org
Sent: Monday, June 01, 2009 12:18 PM
Subject: Lighttpd 1.4.22/PHP 5.2.9 hardlocking the system



-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello,

I'm running lighttpd 1.4.22 and PHP 5.2.9 on FreeBSD 7.2-RELEASE. When
uploading files  1 MB in size or so via PHP, the box then hard locks.
SSH and HTTP become unavailable, and apparently console logins don't
work; however, the box can still be pinged. So far I've been able to
reproduce this issue on FreeBSD/i386 and FreeBSD/amd64.

I have no clue how to debug this, but I'm willing to help :). Sadly, I
don't have physical access to a FreeBSD machine atm to help debug this
with, but I'm working on that.

- -- Jacob
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkojuPUACgkQnokOSaNFCAYVmgCg4CtC68Wo9Aa7jWHXjnvzs5oa
V2cAnRzXhMXucY0G7hY0wyTSmE/QpfCQ
=s2Id
-END PGP SIGNATURE-
___
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




This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.

___
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

emulators/linux_base-f10 = Fedora 8?

[Steven Hartland]

Why does emulators/linux_base-f10 contain a Fedora 8 port
most confusing!

   Regards
   Steve


This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to postmas...@multiplay.co.uk.

___
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: devel/gio-fam-backend build faild

[Steven Hartland]

You need to upgrade all your ports as gnome has been updated, caught us
out too. See:
http://www.freebsd.org/gnome/docs/faq222.html

   Regards
   Steve

- Original Message - 
From: Jyun-Yi Liou [EMAIL PROTECTED]

To: freebsd-ports@freebsd.org
Cc: [EMAIL PROTECTED]
Sent: Wednesday, June 04, 2008 1:18 PM
Subject: devel/gio-fam-backend build faild



Hi list!

I cant build devel/gio-fam-backend while I wana upgrade irc/bitlbee from
1.0.2 to 1.2
the compile error message below:

===  Building for gio-fam-backend-2.16.3
/bin/sh ../../libtool --tag=CC   --mode=link cc -DG_LOG_DOMAIN=\GLib-GIO\
-I../.. -I../../glib -I../../gmodule -I../../gio -DG_DISABLE_CAST_CHECKS
-DGIO_MODULE_DIR=\/usr/local/lib/gio/modules\ -DGIO_COMPILATION
-DG_DISABLE_DEPRECATED -O2 -fno-strict-aliasing -pipe -march=pentium3 -Wall
-export_dynamic -avoid-version -module -no-undefined -export-symbols-regex
'^g_io_module_(load|unload)' -L/usr/local/lib -lintl -o libgiofam.la -rpath
/usr/local/lib/gio/modules libgiofam_la-fam-helper.lo
libgiofam_la-fam-module.lo libgiofam_la-gfamdirectorymonitor.lo
libgiofam_la-gfamfilemonitor.lo  -lgio-2.0 -lgobject-2.0 -lglib-2.0  -lfam
rm -fr  .libs/libgiofam.exp
generating symbol list for `libgiofam.la'
/usr/bin/nm -B  .libs/libgiofam_la-fam-helper.o
.libs/libgiofam_la-fam-module.o .libs/libgiofam_la-gfamdirectorymonitor.o
.libs/libgiofam_la-gfamfilemonitor.o  | sed -n -e 's/^.*[
]\([ABCDGIRSTW][ABCDGIRSTW]*\)[ ][
]*\([_A-Za-z][_A-Za-z0-9]*\)$/\1 \2 \2/p' | /usr/bin/sed 's/.* //' | sort |
uniq  .libs/libgiofam.exp
/usr/bin/grep -E -e ^g_io_module_(load|unload) .libs/libgiofam.exp 
.libs/libgiofam.expT
mv -f .libs/libgiofam.expT .libs/libgiofam.exp
cc -shared  .libs/libgiofam_la-fam-helper.o .libs/libgiofam_la-fam-module.o
.libs/libgiofam_la-gfamdirectorymonitor.o
.libs/libgiofam_la-gfamfilemonitor.o  -Wl,--rpath -Wl,/usr/local/lib
-Wl,--rpath -Wl,/usr/local/lib -L/usr/local/lib /usr/local/lib/libintl.so
-lgio-2.0 /usr/local/lib/libgobject-2.0.so
/usr/local/lib/libglib-2.0.so/usr/local/lib/libfam.so  -march=pentium3
-Wl,-soname -Wl,libgiofam.so
-Wl,-retain-symbols-file -Wl,.libs/libgiofam.exp -o .libs/libgiofam.so
*/usr/bin/ld: cannot find -lgio-2.0
gmake: *** [libgiofam.la] Error 1
*** Error code 2*

Stop in /usr/ports/devel/gio-fam-backend.

ports tree has already updated

best regards,
jyuny1
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]




This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to [EMAIL PROTECTED]

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: devel/gio-fam-backend build faild

[Steven Hartland]

Correct, tbh it really should detect the updated requirement better than it 
does.

   Regards
   Steve

- Original Message - 
From: Jyun-Yi Liou [EMAIL PROTECTED]




Thanks for this hint, Steve!
but I am confused why bitlbee depends on devel/gio-fam-backend
I can install bitlbee from source tarbal without gio-fam-backend (juust
./configure, gmake, gmake install)

because of USE_GNOME= glib20 in irc/bitlbee/Makefile?




This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to [EMAIL PROTECTED]

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: devel/gio-fam-backend build faild

[Steven Hartland]

- Original Message - 
From: Henrik Brix Andersen [EMAIL PROTECTED]

On Wed, Jun 04, 2008 at 04:20:40PM +0100, Steven Hartland wrote:

Correct, tbh it really should detect the updated requirement
better than it does.


Meaning what?


Meaning if it depends on a specific version of another package
it should ensure that version is built and installed. This is
one of the key benefits features of ports tree IMO.

The current error is hard to track down, where as if there was
a failure installing version XYZ of a package e.g. due to a
conflict, it would be much more obvious to the EU as to what
the actual issue was.

Ideally a make clean followed by a make should never fail
with such none descript error when its a dependency issue.

PS: Nothing wrong with top posting as long as maintains the
thread context, its often much easier to follow IMO. Also has
the benefit that: people who have been following the thread
and already know the context, don't have to look through old
information to find the new :)


This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to [EMAIL PROTECTED]

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

portupgrade, recommended by 7 release notes, breaks perl

[Steven Hartland]

Seems portupgrade can easily break the perl install.

How? Well there are various modules which can be updated
but are also part of the base perl and are hence required.

A good example of this is ExtUtils::MakeMaker. If you
uninstall any version of this port your done for, as
trying to build it requires ExtUtils::Command which in
turn requires ExtUtils::MakeMaker which was just deleted.

This circular dependency would not be an issue if the
uninstall somehow knew that the files where required
by perl, and hence didn't break the base port ( perl )
by removing them.

I found this by following the 7.0-RELEASE upgrade
guide which recommends: portupgrade -faP

This ended up with a totally broken install which
took quite some time to fix so I thought it best to
highlight the issue so it can be addressed.

I'm not 100% sure but I think I also spotted portupgrade
reinstalling the same port over and over during this
process. Could this be the case and if so is there
an option to prevent it?

   Regards
   Steve


This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to [EMAIL PROTECTED]

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Ion3 removal (Re: Ion3 license violation)

[Steven Hartland]

- Original Message - 
From: Mark Linimon [EMAIL PROTECTED]




On Wed, Dec 12, 2007 at 08:12:17PM -0600, Mark Linimon wrote:

http://mail-index.netbsd.org/tech-pkg/2007/10/28/.html

Anyone interested in this thread needs to go read that one first.


As well as http://www.archlinux.org/pipermail/tur-users/2007-April/004634.html,
which contains the history of the author's legal threat against ArchLinux.


http://en.wikipedia.org/wiki/Ion_%28window_manager%29#Controversy

   Regards
   Steve


This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to [EMAIL PROTECTED]

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Moving to a more recent linux base, when?

[Steven Hartland]

FYI: The current thinking from iD about the reason ET:QW doesn't work
on 5.4 is problems with TLS so this could also be the case here.

   Regards
   Steve

- Original Message - 
From: Michal Varga [EMAIL PROTECTED]

Well, just for the record, Enemy Territory stopped working with 2.6 for
me, but I can live with that (Doom 3 runs still fine, for example). On
my -CURRENT desktop, I have 2.6 support enabled from the first day of
commit and never plan to go back, not just for one game or even Java.

From the perspective of a common everyday desktop user, I'd call current

2.6 support fine enough, and we are talking about 7.0 that's not even
out yet. Anyway, good job, Roman and the rest of the team.




This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to [EMAIL PROTECTED]

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: FreeBSD Port: mysql-server-5.1.18

[Steven Hartland]

Should be able to just roll your ports tree back to when it included 5.1.X or manually update the couple of files required and 
then rebuild. That said it may not be that which is causing your issue check to see if you enhancing the memory sizes using the 
following, N.B. adjust sizes to be appropriate on your machine.


kern.maxdsiz=4G
kern.dfldsiz=4G
kern.maxssiz=512M

   Regards
   Steve

- Original Message - 
From: Paul Laudanski [EMAIL PROTECTED]

It appears there is a problem with this port.  In the meantime, can you
guide me on how to downgrade to 5.1.17?  www.castlecops.com is entirely
offline. 




This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to [EMAIL PROTECTED]

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Packages not respecting DESTDIR ( perl5.8 )

[Steven Hartland]

http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/porting-prefix.html

- Original Message - 
From: [LoN]Kamikaze [EMAIL PROTECTED]

To: Steven Hartland [EMAIL PROTECTED]
Cc: freebsd-ports@freebsd.org
Sent: Wednesday, May 02, 2007 7:54 AM
Subject: Re: Packages not respecting DESTDIR ( perl5.8 )



Steven Hartland wrote:

I'm trying to install ports into a jail but even some
key ports like don't seen to support this option
even to the extent they appear to break the host OS
deleting files.

I'm assuming this shouldn't be the case?


I don't see DESTIR mentioned in ports(7) or in the Porters' Handbook, how did 
you acquire this assumption?




This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to [EMAIL PROTECTED]

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Packages not respecting DESTDIR ( perl5.8 )

[Steven Hartland]

I'm trying to install ports into a jail but even some
key ports like don't seen to support this option
even to the extent they appear to break the host OS
deleting files.

I'm assuming this shouldn't be the case?

Repro steps:
cd /usr/ports/lang/perl5.8
make install
ls -l /usr/local/bin/perl*
-rwxr-xr-x  2 root  wheel   9424 May  1 23:30 /usr/local/bin/perl
-r-xr-xr-x  1 root  wheel  15101 May  1 23:30 /usr/local/bin/perl-after-upgrade
lrwxr-xr-x  1 root  wheel 24 May  1 23:30 /usr/local/bin/perl5 - 
/usr/local/bin/perl5.8.8
-rwxr-xr-x  2 root  wheel   9424 May  1 23:30 /usr/local/bin/perl5.8.8
-rwxr-xr-x  1 root  wheel  37307 May  1 23:30 /usr/local/bin/perlbug
-rwxr-xr-x  1 root  wheel  17965 May  1 23:30 /usr/local/bin/perlcc
-rwxr-xr-x  1 root  wheel236 May  1 23:30 /usr/local/bin/perldoc
-rwxr-xr-x  1 root  wheel  11949 May  1 23:30 /usr/local/bin/perlivp

All good so far.
make DESTDIR=/usr/local/jails/jail1 install
Does nothing, a quirk of the port system for a while now where it
seems to attempt to remember the state but gets it wrong in this
type of case.
make DESTDIR=/usr/local/jails/jail1 reinstall
which goes well until:
/usr/bin/strip: '/usr/local/bin/perl5.8.8': No such file
/usr/bin/strip: '/usr/local/bin/perl': No such file
/usr/local/bin/pod2man: not found
*** Error code 127

Make is not my strong point but looking at the makefile it seems
the post and pre install steps are broken and not using DESTDIR.

ls -l /usr/local/bin/perl*
-r-xr-xr-x  1 root  wheel  15101 May  1 23:30 /usr/local/bin/perl-after-upgrade
lrwxr-xr-x  1 root  wheel 24 May  1 23:30 /usr/local/bin/perl5 - 
/usr/local/bin/perl5.8.8
-rwxr-xr-x  1 root  wheel  37307 May  1 23:30 /usr/local/bin/perlbug
-rwxr-xr-x  1 root  wheel  17965 May  1 23:30 /usr/local/bin/perlcc
-rwxr-xr-x  1 root  wheel236 May  1 23:30 /usr/local/bin/perldoc
-rwxr-xr-x  1 root  wheel  11949 May  1 23:30 /usr/local/bin/perlivp

This has now trashed the base perl which was installed first and it
shouldnt have gone any where near it.

The following diff fixes most of the issues but use.perl, pkg-install
and pkg-deinstall and or their invocation still need fixing up.

[patch]
--- Makefile.orig   Tue May  1 23:46:35 2007
+++ MakefileWed May  2 00:40:38 2007
@@ -178,19 +178,19 @@

post-install:
-   @${STRIP_CMD} ${PREFIX}/bin/perl${PERL_VER}
-   @${STRIP_CMD} ${PREFIX}/bin/perl
-   @${PREFIX}/bin/pod2man ${WRKDIR}/perl-after-upgrade 
${WRKDIR}/perl-after-upgrade.1
-   @${INSTALL_SCRIPT} ${WRKDIR}/perl-after-upgrade 
${PREFIX}/bin/perl-after-upgrade
+   @${STRIP_CMD} ${DESTDIR}${PREFIX}/bin/perl${PERL_VER}
+   @${STRIP_CMD} ${DESTDIR}${PREFIX}/bin/perl
+   @${DESTDIR}/${PREFIX}/bin/perl ${DESTDIR}${PREFIX}/bin/pod2man ${WRKDIR}/perl-after-upgrade 
${WRKDIR}/perl-after-upgrade.1

+   @${INSTALL_SCRIPT} ${WRKDIR}/perl-after-upgrade 
${DESTDIR}${PREFIX}/bin/perl-after-upgrade
   @${INSTALL_MAN} ${WRKDIR}/perl-after-upgrade.1 
${MAN1PREFIX}/man/man1/perl-after-upgrade.1
-   @${LN} -sf ${PREFIX}/bin/perl${PERL_VER} ${PREFIX}/bin/perl5
+   @${CHROOT} ${DESTDIR} ${LN} -sf ${PREFIX}/bin/perl${PERL_VER} 
${PREFIX}/bin/perl5
.for files in ${BSDPAN_FILES}
-   ${MKDIR} ${BSDPAN_DEST}/${files:H}
+   ${MKDIR} ${DESTDIR}${BSDPAN_DEST}/${files:H}
   ${INSTALL} ${COPY} -o ${BINOWN} -g ${BINGRP} -m ${NOBINMODE} \
-   ${BSDPAN_WRKSRC}/${files} ${BSDPAN_DEST}/${files}
+   ${BSDPAN_WRKSRC}/${files} ${DESTDIR}${BSDPAN_DEST}/${files}
.endfor
.ifndef WITHOUT_USE_PERL
   PKG_PREFIX=${PREFIX} ${SH} ${PKGINSTALL} ${PKGNAME} POST-INSTALL
.if ${OSVERSION}  500036
-   ${INSTALL_SCRIPT} ${WRKDIR}/use.perl ${PREFIX}/bin/use.perl
+   ${INSTALL_SCRIPT} ${WRKDIR}/use.perl ${DESTDIR}${PREFIX}/bin/use.perl
   @fmt ${PKGMESSAGE}
.endif
[/patch]



This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to [EMAIL PROTECTED]

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: PHP 5.2.1

[Steven Hartland]

emmi wrote:

Hello, I just updated my ports this morning and the PHP was updated to
5.2.1. I am having major issues with my website, specially my forums.
The designers (vBulletin) say this is a problem in the latest FreeBSD
ports update. Does anyone know about this?


Some info on the issues your seeing might be helpful.

   Steve



This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to [EMAIL PROTECTED]

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

proftpd port missing dependency on autoconf

[Steven Hartland]

The current version download via cvsup as of this evening is
broken due to a missing dependency on autoconf producing the
following error on a clean machine:

[log]
cd .  autoconf
autoconf: not found
gmake: *** [configure] Error 127
*** Error code 2
[/log]

Installing autoconf-2.61 followed by make clean; make fixed
the error.

The makefile however does state so maybe something more
seriously wrong with the current port base?
USE=AUTOTOOLS=  autoconf:259

   Steve



This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 


In the event of misdirection, illegible or incomplete transmission please 
telephone +44 845 868 1337
or return the E.mail to [EMAIL PROTECTED]

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]