Re: ec2-eu-west-1.portsnap.freebsd.org is not up to date
* Walter Schwarzenfeld wrote: ... and none of them work. ... since early Sunday; six of the seven are working and returning a "latest" timestamp of 2016-09-04T05:17:49Z. So no updates for ~35 hours. The "snapshot" timestamp is just after midnight UTC on Sunday, but that is probably just something that happens once per day. Is cperciva@ still in charge of portsnap? The latest information I can find is years old. -- 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: ec2-eu-west-1.portsnap.freebsd.org is not up to date
Thanks, you are right. Works now again as expected. ___ 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: ec2-eu-west-1.portsnap.freebsd.org is not up to date
On 9/5/16 13:19, Henk van Oers wrote: > > On Mon, 5 Sep 2016, Martin Waschb?sch wrote: >>> Am 05.09.2016 um 09:44 schrieb Henk van Oers: >>> >>> >>> The portsnap.FreeBSD.org on IP-nr 46.137.83.240 >>> is not serving updates anymore. >>> >>> What other server can I use? >> >> The list of mirrors is updated by portsnap and stored in >> /var/db/portsnap/serverlist > > Ah, thanks for the pointer. > >> You can try any of them to see if they respond... > > Mmmm: ""Latest snapshot on server matches what we already have."" > > Maybe the feed to portsnap.FreeBSD.org is down. > I'll wait an other day. Please try again, this should have been fixed now (the outage was related to the monthly update, which is unknown to the builder itself and makes it to refrain from doing further update and required a manual intervention). Cheers, signature.asc Description: OpenPGP digital signature
Re: ec2-eu-west-1.portsnap.freebsd.org is not up to date
On Mon, 5 Sep 2016, Martin Waschb?sch wrote: Am 05.09.2016 um 09:44 schrieb Henk van Oers: The portsnap.FreeBSD.org on IP-nr 46.137.83.240 is not serving updates anymore. What other server can I use? The list of mirrors is updated by portsnap and stored in /var/db/portsnap/serverlist Ah, thanks for the pointer. You can try any of them to see if they respond... Mmmm: ""Latest snapshot on server matches what we already have."" Maybe the feed to portsnap.FreeBSD.org is down. I'll wait an other day. -- Henk ___ 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"
go14 fails stable/11
Greetings, With an up-to-date ports tree and 73076d5 stable/11 I get the appended errors trying to build lang/go14. Possibly there is something wrong with my environment, any ideas? If not I'll file a bug report. Best, Russell ===> Building for go14-1.4.3 cd /usr/ports/lang/go14/work/go/src && CC=/usr/bin/cc GOROOT=/usr/ports/lang/go14/work/go GOROOT_FINAL=/usr/local/go14 GOBIN= GOARCH=amd64 GOOS=freebsd CGO_ENABLED=0 /bin/sh make.bash # Building C bootstrap tool. cmd/dist -t: not found gcc: not found -t: not found # Building compilers and Go bootstrap tool for host, freebsd/amd64. lib9 libbio liblink cmd/cc cmd/gc cmd/6l cmd/6a cmd/6c /usr/ports/lang/go14/work/go/src/cmd/6c/txt.c:995:28: warning: shifting a negative signed value is undefined [-Wshift-negative-value] f->vconst |= (vlong)~0 << 32; ~ ^ /usr/ports/lang/go14/work/go/src/cmd/6c/txt.c:1045:28: warning: shifting a negative signed value is undefined [-Wshift-negative-value] f->vconst |= (vlong)~0 << 32; ~ ^ 2 warnings generated. cmd/6g runtime errors sync/atomic sync io unicode unicode/utf8 unicode/utf16 bytes math strings strconv bufio sort container/heap encoding/base64 syscall time os reflect fmt encoding encoding/json flag path/filepath path io/ioutil log regexp/syntax regexp go/token go/scanner go/ast go/parser os/exec os/signal net/url text/template/parse text/template go/doc path/filepath path io/ioutil log regexp/syntax regexp go/token go/scanner go/ast go/parser os/exec os/signal net/url text/template/parse text/template go/doc go/build cmd/go Bus error (core dumped) *** Error code 138 Stop. make: stopped in /usr/ports/lang/go14 --More--(END) ___ 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"
ports: on the fly pkg-plist creation from git pull
Hello, I am creating a port from a GIT repository. I would like to keep the GIT file structure to user can update the project with GIT tools. I know this is not the best and not even the valid way to update, but in this particular case there is no other choice yet.. and the project changes really fast so updates from GIT are reasonable and desired. Hopefully it will change in a next major release and we can simply create a package. I did the simple automation of project clone, submodiles clone, initial configuration, etc, inside port Makefile. The problem is with the pkg-plist. I can create one with `make plist` based on the staged filesystem and it works until update. I would like make to create a plist file after fetch and build as a part of automation. How can I call `make makeplis` on each build? Any hints appreciated :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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: ec2-eu-west-1.portsnap.freebsd.org is not up to date
... and none of them work. ___ 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: ec2-eu-west-1.portsnap.freebsd.org is not up to date
> Am 05.09.2016 um 09:44 schrieb Henk van Oers: > > > The portsnap.FreeBSD.org on IP-nr 46.137.83.240 > is not serving updates anymore. > > What other server can I use? The list of mirrors is updated by portsnap and stored in /var/db/portsnap/serverlist You can try any of them to see if they respond... Martin ___ 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"
Maintainership for print/lilypond-devel
Hi everyone, I would like to offer maintaining the print/lilypond-devel port. Attached you'll find a patch bringing the port to the current version 2.19.47. A few more tests might still be necessary, but as the port is already marked for deletion I wanted to put the work I've done into the open as soon as possible. A short summary of the patch: - Update to version 2.19.47 - Import fix for pkgconfig detection in configure script from print/lilypond - Use gcc for building as newer versions (2.19.42+) don't build with clang anymore - Re-generate the patches with `make makepatch` to make portlint happy and bring the patches back in sync with the patched files. Best regards, Martin -- Press the # key for more options. diff -Nur lilypond-devel.orig/distinfo lilypond-devel/distinfo --- lilypond-devel.orig/distinfo2016-09-01 22:42:51.129658000 +0200 +++ lilypond-devel/distinfo 2016-09-05 14:25:54.362645000 +0200 @@ -1,2 +1,3 @@ -SHA256 (lilypond-2.19.11.tar.gz) = 5245aba230ccc0a217d25079eca44cea637c6897d99ff094f4145cacef70bbb0 -SIZE (lilypond-2.19.11.tar.gz) = 16304635 +TIMESTAMP = 1472857204 +SHA256 (lilypond-2.19.47.tar.gz) = 842312813a9144b6b54a33f13fb19addbfc779d7bbfe3b2075be1235287de08c +SIZE (lilypond-2.19.47.tar.gz) = 16926783 diff -Nur lilypond-devel.orig/files/patch-config.make.in lilypond-devel/files/patch-config.make.in --- lilypond-devel.orig/files/patch-config.make.in 2016-09-01 22:40:20.018546000 +0200 +++ lilypond-devel/files/patch-config.make.in 2016-09-05 14:25:54.363283000 +0200 @@ -1,8 +1,8 @@ config.make.in.origSun Apr 11 10:26:32 2004 -+++ config.make.in Sun Apr 11 10:26:46 2004 -@@ -41,7 +41,7 @@ +--- config.make.in.orig2016-08-30 10:23:53 UTC config.make.in +@@ -67,7 +67,7 @@ sharedstatedir = @sharedstatedir@ + stepmake = @stepmake@ - # move out of config.make.in? package_datadir = $(datadir)/$(package) -package_infodir = $(infodir)/$(package) +package_infodir = $(infodir) diff -Nur lilypond-devel.orig/files/patch-configure lilypond-devel/files/patch-configure --- lilypond-devel.orig/files/patch-configure 1970-01-01 01:00:00.0 +0100 +++ lilypond-devel/files/patch-configure2016-09-05 14:25:54.36350 +0200 @@ -0,0 +1,78 @@ +--- configure.orig 2016-08-30 10:23:53 UTC configure +@@ -11412,74 +11412,7 @@ test -n "$PKG_CONFIG" || PKG_CONFIG="no" + + if test $? -eq 0 -a -n "0.9.0"; then + +-r="`eval echo '$'"PKG_CONFIG"`" +-{ $as_echo "$as_me:$LINENO: checking $r version" >&5 +-$as_echo_n "checking $r version... " >&6; } +-exe=` +-## which doesn't work in ash, if /usr/bin/which isn't installed +-## type -p doesn't work in ash +-## command -v doesn't work in zsh +-## command -v "$r" 2>&1 +-## this test should work in ash, bash, pdksh (ksh), zsh +-type -p $r 2>/dev/null | tail -n 1 | awk '{print $NF}' +-` +-if test -n ""; then +-ver="" +-else +-ver=` +-## "$exe" --version 2>&1 | grep -v '^$' | head -n 1 | awk '{print $NF}' +-## +-## ARG. +-## Workaround for broken Debian gcc version string: +-## gcc (GCC) 3.1.1 20020606 (Debian prerelease) +-## +-## -V: Workaround for python +- +-#dnl +- +-## Assume and hunt for dotted version multiplet. +-## use eval trickery, because we cannot use multi-level $() instead of `` +-## for compatibility reasons. +- +-## grab the first version number in --version output. +-eval _ver=\"\`("$exe" --version || "$exe" -V) 2>&1 | +- grep -E '(^| )[0-9][0-9]*\.[0-9]' | +- head -n 1 | +- tr ' ' '\n' | +- sed 's/\([0-9][0-9]*\.[0-9][0-9.]*\).*/\1/g' | +- grep -E '(^| )[0-9][0-9]*\.[0-9]' | +- head -n 1\`\" +- +-if test -z "$_ver"; then +-## If empty, try date [fontforge] +-eval _ver=\"\`("$exe" --version || "$exe" -V) 2>&1 \ +- | grep '\(^\|[^0-9a-f]\)[0-9]\{6,8\}\([^0-9a-f]\|$\)' \ +- | head -n 1 \ +- | sed -e 's/^[^.0-9]*//' -e 's/[^.0-9]*$//'\`\" +-fi +-echo "$_ver" +-#dnl +-` +-fi +-num=` +-echo "$ver" | awk -F. ' +-{ +- if ($3) {three = $3} +- else {three = 0} +-} +-{printf "%.0f\n", $1*100 + $2*1000 + three}' +-` +-req=` +-echo "0.9.0" | awk -F. ' +-{ +- if ($3) {three = $3} +- else {three = 0} +-} +-{printf "%.0f\n", $1*100 + $2*1000 + three}' +-` +-{ $as_echo "$as_me:$LINENO: result: $ver" >&5 +-$as_echo "$ver" >&6; } +-if test "$num" -lt "$req"; then ++if $exe --atleast-pkgconfig-version 0.9.0; then + + eval "REQUIRED"=\"`eval echo \"'$'REQUIRED\" \""$r >= 0.9.0 (installed: $ver)"\"`\" + diff -Nur lilypond-devel.orig/files/patch-Documentation_GNUmakefile lilypond-devel/files/patch-Documentation_GNUmakefile --- lilypond-devel.orig/files/patch-Documentation_GNUmakefile 2016-09-01 22:39:37.625401000 +0200 +++
ec2-eu-west-1.portsnap.freebsd.org is not up to date
The portsnap.FreeBSD.org on IP-nr 46.137.83.240 is not serving updates anymore. What other server can I use? -- Henk ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ lang/jimtcl | 0.76| 0.77 +-+ math/rpy2 | 2.7.8 | 2.8.3 +-+ multimedia/gtk-youtube-viewer | 3.2.3 | 3.2.4 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"