Build sipXecs on FreeBSD

2016-09-05 Thread Grzegorz Junka
Has anybody tried to build sipXcom on FreeBSD recently? This document mentions that at some point it was in the ports but it looks like it has been removed: https://sipfoundry.atlassian.net/wiki/display/sipXecs/Building+on+FreeBSD And this is the GitHub repository: https://github.com/sipXcom/

Re: ec2-eu-west-1.portsnap.freebsd.org is not up to date

2016-09-05 Thread Christian Ullrich
* 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 so

Re: ec2-eu-west-1.portsnap.freebsd.org is not up to date

2016-09-05 Thread Walter Schwarzenfeld
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

2016-09-05 Thread Xin Li
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

Re: ec2-eu-west-1.portsnap.freebsd.org is not up to date

2016-09-05 Thread Henk van Oers
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

go14 fails stable/11

2016-09-05 Thread Russell L. Carter
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 &

ports: on the fly pkg-plist creation from git pull

2016-09-05 Thread CeDeROM
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

Re: ec2-eu-west-1.portsnap.freebsd.org is not up to date

2016-09-05 Thread Walter Schwarzenfeld
... 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

2016-09-05 Thread Martin Waschbüsch
> 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

Maintainership for print/lilypond-devel

2016-09-05 Thread Martin Neubauer
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

ec2-eu-west-1.portsnap.freebsd.org is not up to date

2016-09-05 Thread 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? -- Henk ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "

FreeBSD ports you maintain which are out of date

2016-09-05 Thread portscout
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you