Re: [RFC] Why FreeBSD ports should have branches by OS version

2017-06-26 Thread Guido Falsi
On 06/26/17 00:32, Dave Hayes wrote: > On 06/23/2017 01:53, Guido Falsi wrote: >> If your model works fine I'm quite sure the FreeBSD community and >> project will be quite happy to embrace it. > ... >> I cannot think of a better way to show there actually is no manpower > problem than creating a w

Re: [RFC] Why FreeBSD ports should have branches by OS version

2017-06-26 Thread Guido Falsi
On 06/26/17 09:27, Guido Falsi wrote: > I'd say the difficult part in such a problem is not in the idea but in > the boring details of it's implementation and long term maintenance. > I forgot one important piece of information: Any project that requires full dedication from all committers to a

Re: [RFC] Why FreeBSD ports should have branches by OS version

2017-06-26 Thread Kurt Jaeger
Hi! > Thus, in some cases, people demand or insist because they want something > they either cannot accomplish themselves, or cannot accomplish in the > limited time they have. As far as I have observed, you can't even -pay- > the ports experts to do something you might want. You can discuss t

Re: [RFC] Why FreeBSD ports should have branches by OS version

2017-06-26 Thread Franco Fichtner
> On 26. Jun 2017, at 9:43 AM, Kurt Jaeger wrote: > >> Thus, in some cases, people demand or insist because they want something >> they either cannot accomplish themselves, or cannot accomplish in the >> limited time they have. As far as I have observed, you can't even -pay- >> the ports expe

Re: "clamav-unofficial-sigs" error message

2017-06-26 Thread Marko Njezic
On 2017-06-25 18:16, Carmel NY wrote: On Sun, 25 Jun 2017 17:17:44 +0200, Martin Waschbüsch stated: From what I can see, the clamav-unofficial-sigs port works. It determines if there are updates or whether you have checked recently, so that you do not inadvertently dos the signature servers. Wh

FreeBSD ports you maintain which are out of date

2017-06-26 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

Re: [RFC] Why FreeBSD ports should have branches by OS version

2017-06-26 Thread Torsten Zuehlsdorff
Aloha David, I think the current process of having rolling-releases packages makes unpredictable upgrades as we have to manually check if the upgrade will be fine or not. When a user installs FreeBSD 11.0 on its system, it probably expects that everything will work fine until a next major upgrad

Re: "clamav-unofficial-sigs" error message

2017-06-26 Thread Carmel NY
On Mon, 26 Jun 2017 11:37:29 +0200, Marko Njezic stated: >On 2017-06-25 18:16, Carmel NY wrote: >> On Sun, 25 Jun 2017 17:17:44 +0200, Martin Waschbüsch stated: >> >>> From what I can see, the clamav-unofficial-sigs port works. It >>> determines if there are updates or whether you have checked

Re: "clamav-unofficial-sigs" error message

2017-06-26 Thread Marko Njezic
On 2017-06-26 13:26, Carmel NY wrote: On Mon, 26 Jun 2017 11:37:29 +0200, Marko Njezic stated: On 2017-06-25 18:16, Carmel NY wrote: On Sun, 25 Jun 2017 17:17:44 +0200, Martin Waschbüsch stated: From what I can see, the clamav-unofficial-sigs port works. It determines if there are updates or

Re: sysutils/tmux - strange behaviour with new version 2.4 / 2.5

2017-06-26 Thread Miroslav Lachman
Vanilla Hsu wrote on 2017/05/16 01:37: I got the same problem too, but after update to 2.5-rc2, all issues gone. maybe you can try to update to 2.5-rc2 (2.5 not yet released) by yourself. Opening this again. I downgraded to 2.3 in the meantime but I had a hope that 2.5 will be fine - it is no

Re: lang/gcc* package builds vs. release/11.0.1/ and the future release/11.1.0 because of vm_ooffset_t and vm_pindex_t changes and how the lang/gcc* work

2017-06-26 Thread Patrick Powell
I have reported this problem - see email to freebsd-stable Re: GCC + FreeBSD 11.0 Stable - stat.h does not have vm_ooffset_t definition Here is part of the discussion: On Sat, 29 Apr 2017, Dimitry Andric wrote: This is because gcc's fixincludes process makes copies of certain system headers (i

Re: USE_GCC usage

2017-06-26 Thread Mathieu Arnold
Le 25/06/2017 à 19:09, Richard Gallamore a écrit : > When using USE_GCC= 5+, errors occur because this USE only sets > build and run time dependency, and not lib dependency. > > Error: /usr/local/bin/ann_in is linked to > /usr/local/lib/gcc5/libgfortran.so.3 from lang/gcc but it is not declared as

Re: NEW APR/APR-Utils

2017-06-26 Thread Andre Goree
On 2017/06/22 9:43 pm, Dewayne Geraghty wrote: Andre, I've been down this path a few times and Bernard (who looks after most/all? things related to libressl) does a great job in supporting people like us that build our own packages. Out of frustration of build failures, I applied the patch below

Re: lang/gcc* package builds vs. release/11.0.1/ and the future release/11.1.0 because of vm_ooffset_t and vm_pindex_t changes and how the lang/gcc* work

2017-06-26 Thread Mark Millard
Top post on one point. . . Patrick Powell papowell at astart.com wrote on Mon Jun 26 14:10:44 UTC 2017 (He was quoting Gerald. I was also part of some earlier discussions.) > (Luckily this only hits with most -CURRENT versions of FreeBSD and > older packages only.) > > Gerald Unfortunately this

Re: [RFC] Why FreeBSD ports should have branches by OS version

2017-06-26 Thread Grzegorz Junka
On 26/06/2017 07:24, Torsten Zuehlsdorff wrote: Aloha David, I think the current process of having rolling-releases packages makes unpredictable upgrades as we have to manually check if the upgrade will be fine or not. When a user installs FreeBSD 11.0 on its system, it probably expects that ev

Re: [RFC] Why FreeBSD ports should have branches by OS version

2017-06-26 Thread Dave Hayes
On 06/26/2017 00:27, Guido Falsi wrote: I only partly agree with what you say, but anyway insisting on the mailing lists with individual committers, and defending a general idea ignoring all the details, dismissing the actual problems in the detailed implementation that are raised by committers i

PRs in need of some TLC

2017-06-26 Thread Martin Waschbüsch
Hi all, could someone have a look at these PRs (they are linked) and provide some tender loving care? ;-) https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220177 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220190 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220191 Thanks!! Martin

Re: perl problem

2017-06-26 Thread Dave Cottlehuber
On Tue, 20 Jun 2017, at 14:21, Jeffrey Bouquet via freebsd-ports wrote: > Attachment probably not sent to the list. > > CD /usr/ports/devel/p5-List-Regexp [new june 20 ] > make build > ... > Encode.c: loadable library and perl binaries are mismatched ( got > handshake key 0x8900080,

Re: PRs in need of some TLC

2017-06-26 Thread Greg 'groggy' Lehey
On Monday, 26 June 2017 at 21:48:14 +0200, Martin Waschbüsch wrote: > Hi all, > > could someone have a look at these PRs (they are linked) and provide > some tender loving care? ;-) > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220177 > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=2201

Re: PRs in need of some TLC

2017-06-26 Thread Kurt Jaeger
Hi! > could someone have a look at these PRs (they are linked) and provide some > tender loving care? ;-) > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220177 This is missing a patch, isn't it ? > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220190 > https://bugs.freebsd.org/bugzi

E-mail account blacklisted

2017-06-26 Thread Technical Support via freebsd-ports
Your Account Has Been Blacklisted! Your account has been Blacklisted due to system error CODE: REF-6192-0417 . You will not be able to send or receive emails from certain IP locations or Email Service Providers. If you would like to continue using your email address, please re-validate y

Your Account Has Been Disabled

2017-06-26 Thread Apple
___ 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"