Re: FreeBSD Port: strongswan-5.9.2_1

Hi, Strongswan authors have no interest in supporting LibreSSL and patching it in the code #ifdef maze is really difficult since it checks OpenSSL version numbers which for LibreSSL looks like the most modern OpenSSL Release. Cheers, Franco > On 25. Apr 2021, at 20:41, Gena Gulchin wrote: >

LibreSSL 3.1.5 quarterly update vs. vuxml entry

Hello, https://svnweb.freebsd.org/ports?view=revision=557712 https://svnweb.freebsd.org/ports?view=revision=557716 vuxml only sets 3.2.3 but that still flags the fixed quarterly version 3.1.5 as vulnerable. It would be nice to have this fixed. Thanks, Franco

Re:

> On 7. Nov 2020, at 6:25 PM, Cy Schubert wrote: > > That's not needed. The proposal is to replace the syslog-ng port with the > contents of syslog-ng329 and deprecate the others. Those using > sysutils/syslog-ng will see no change. Those using older versions will need > to replace

Ready for commit PRs

Hi, ClamnAV build fix for latest version: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247792 Squid update to 4.12: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247397 Thanks, Franco ___ freebsd-ports@freebsd.org mailing list

Re: Portmaster failing

Hi Adam, > On 1. Jan 2020, at 10:18 PM, Adam Weinberger wrote: > > On Wed, Jan 1, 2020 at 1:51 PM @lbutlr wrote: >> >> On 01 Jan 2020, at 13:46, Franco Fichtner wrote: >>> >>> >>> >>>> On 1. Jan 2020, at 9:42 PM, @lbutlr wrote:

Re: Portmaster failing

> On 1. Jan 2020, at 9:42 PM, @lbutlr wrote: > > On 01 Jan 2020, at 13:40, Franco Fichtner wrote: >> security/openssl was removed before, now security/openssl111 has become >> security/openssl. > > Ugh. > >> A bit too eager for my taste, but that's why

Re: Portmaster failing

security/openssl was removed before, now security/openssl111 has become security/openssl. A bit too eager for my taste, but that's why we all have private trees, don't we. ;) Cheers, Franco > On 1. Jan 2020, at 9:37 PM, @lbutlr wrote: > > Portmaser -L errors out with > > make:

Re: XXX needs Python 3.4 at least, but 2.7 was specified

> On 25. Dec 2019, at 12:59 PM, D'Arcy Cain wrote: > > On 12/24/19 5:56 PM, w.schwarzenfeld wrote: >> At least a workaround (maybe the sollutiion): >> >> >> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209881=diff > > Another workaround if you don't want to modify files in the repo

Patches waiting for commits

Hi, Here are a few bug reports waiting for a kind committer: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233963 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239860 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241569 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242658

Re: PHP version retirement

> On 12. Aug 2019, at 16:29, Adam Weinberger wrote: > > On Mon, Aug 12, 2019 at 1:04 AM Martin Waschbüsch > wrote: >> Furthermore, the argument that it is more more work to maintain an >> abandoned version is silly because it’s more work to delete a port that >> to just keep it

Re: PHP version retirement

> On 12. Aug 2019, at 00:22, Adam Weinberger wrote: > >> On Sun, Aug 11, 2019 at 1:05 PM Franco Fichtner wrote: >> >> Quarterly is essentially useless if the decision is to immediately axe a >> deprecated release. 3 months are nothing in production environments

Re: PHP version retirement

Quarterly is essentially useless if the decision is to immediately axe a deprecated release. 3 months are nothing in production environments, if you get 3 months (1,5 months mean) at all and also all other updates and security relevant bug fixes in the same quarterly that you desperately need.

Re: Bind914 conficts with bind-tools

> On 1. May 2019, at 11:08 AM, Xavier wrote: > > Hello, > > I wanted to portupgrad bind914, ran into a conflict : > >> [root@numenor bind914]# make all >> ===> Staging for bind914-9.14.1 >> ===> bind914-9.14.1 depends on package: bind-tools>0 - not found >> ===> Installing for

Re: Open strongswan bugs

Hi, > On 9. Mar 2019, at 11:46 AM, Kurt Jaeger wrote: > >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212149 > > I'm unsure about closing this one. Right now strongswan does not > build with libressl, right ? It's tricky. LibreSSL is not supported and currently the only way to make it

Open strongswan bugs

Hi, strongswan port has 4 open tickets with maintainer feedback or approval, but no assignees. Here's the digest. Should be committed (maintainer approval +): https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234648 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236218 Should be closed

Re: Add conflicts to port

Hi Matthias, Explicit CONFLICTS only exist within the ports tree during builds. pkg detects conflicts simply when files are attempted to be installed in the same place -- i.e. a file already belongs to another installed package. Cheers, Franco > On 8. Jan 2019, at 3:52 PM, Matthias Fechner

Re: ssl=base

> On 25. Nov 2018, at 12:51 PM, Eugene Grosbein wrote: > > Why can't you use LibreSSL port for some ports and base libssl for other > ports? > That is, net/mpd5 links with base system libfetch that depends on base libssl, > so it is example of port that cannot be built with LibreSSL. FWIW,

Re: sed dollar sign substitution in Makefile

Hi, > On 6. Nov 2018, at 9:12 PM, Oliver Mahmoudi wrote: > > Therefore, in Makefile I set: ${REINPLACE_CMD} 's|print $1|print $4|g' > file_to_be_changed In make commands you need to escape $ as $$ to be able to pass it to the shell. Cheers, Franco

Concerns about external contribution handling, a case study

To whom this may concern, The following PR showed vividly what I've been seeing for a long time on this list and while working with FreeBSD ports. I'm attaching my last response here because it may be important for some to see, even if it's being brushed off. ===>

Re: net/ntopng: version jump by an order of magnitude

Hi Guido, > On 20. Sep 2018, at 9:02 AM, Guido Falsi wrote: > > Terribly sorry I did not catch the typo before committing! No worries, was just wondering about it to point out that going back to the proper date will not upgrade through package because the version number is smaller again. >

net/ntopng: version jump by an order of magnitude

Hi, Small question: https://github.com/freebsd/freebsd-ports/commit/0585180d ... has a typo in the version number which was an ISO date originally. Are we using this new date format now or is there going to be a PORTEPOCH amendment? Cheers, Franco

Re: LibreSSL CVE-2018-0732 correction

> On 23. Jul 2018, at 9:29 PM, Mathieu Arnold wrote: > > On Mon, Jul 23, 2018 at 09:14:48PM +0200, Franco Fichtner wrote: >> Hi, >> >> What's the policy for picking these up? Is there the same >> kind of maintainer timeout at play here? Feedback welcome

LibreSSL CVE-2018-0732 correction

Hi, What's the policy for picking these up? Is there the same kind of maintainer timeout at play here? Feedback welcome. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229037 Cheers, Franco ___ freebsd-ports@freebsd.org mailing list

Re: Should a package restart on upgrade itself

> On 26. Jun 2018, at 1:27 PM, Miroslav Lachman <000.f...@quip.cz> wrote: > > One example from today upgrade: > > [87/96] Extracting open-vm-tools-nox11-10.2.5,2: .. done > Stopping vmware_guestd. > Waiting for PIDS: 516. > Loading vmmemctl kernel module: already loaded. >

Re: Removing git dependencies on perl5 and python27

> On 15. Jun 2018, at 10:10 AM, Mahmoud Al-Qudsi wrote: > > On Fri, Jun 15, 2018 at 2:57 AM, Michael Gmelin wrote: >> Last time I checked, building git without Perl broke submodules (which is a >> core feature that should work with a default installation). > > I fully agree. Fortunately,

Fwd: www/phalcon PHP flavoring

Hi, Maybe someone else will take this. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226552 <https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226552> Thanks, Franco > Begin forwarded message: > > From: Franco Fichtner <fra...@opnsense.org> > Subject: www/phal

Re: *** Error code 70

> On 5. Mar 2018, at 3:28 AM, Paul Beard wrote: > > This was supposedly fixed almost 2 years ago in r412608. Seeing it now and > just updated to revision 463615. Pkg 1.10.x "fixed" this and introduced this ports framework regression.

committer for snuffleupagus update

Hi all, See: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225593 Thank you, Franco ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to

Re: RESTRICTED in net/frr

Hi all, No response from the committer or portmgr. This is *bad*. So we all agree it's ok to use the FreeBSD ports tree to block open source projects for petty fights and favours? But we are offended by strong language? Can somebody with authority please clear this up beyond a reasonable

Re: RESTRICTED in net/frr

Hi Kurt, > On 12. Jan 2018, at 9:57 AM, Kurt Jaeger wrote: > > As far as I understand it (and I'm by no means authoritative on this)! > > [...] Thank you for this. Though I don't see a GPL violation reason here. GPLv2 is still the license, the code is in the open. In a

RESTRICTED in net/frr

Hi, Can somebody please explain: > Mark net/frr as RESTRICTED, it contains a possible GPL violation of some > of the Quagga software that it includes. > > Submitted by: Paul Jakma (author of Quagga) > With hat: portmgr > MFH: 2018Q1 If there is an open reason it should certainly

Re: Option vs. flavor?

Why not use a separate data package as optional dependency? Solves the conditional fetch. > On 16. Dec 2017, at 22:02, Yuri wrote: > >> On 12/16/17 12:42, Ben Woods wrote: >> Is there any reason why you want to avoid the download with the port “make >> fetch”? > > To not clog

Re: Patches for a slave port

Hi Kevin, > On 15. Dec 2017, at 5:53 AM, Kevin Oberman wrote: > > Why does "svn diff" not see the new files? How do I get the diffs? Or am I > going to have to manually generate the diff the old fashioned way. Use "svn add" on these files beforehand. Cheers, Franco

Re: make reinstall does not work

> On 11. Dec 2017, at 7:34 AM, Kurt Jaeger wrote: > > Hi! > >> On Sunday, 10 December 2017 at 20:32:38 +0100, Walter Schwarzenfeld wrote: >>> Look at the link in Shawn Webb's post: >>> >>> bapt (Baptisse Daroussin) wrote >>> >>> *bapt * replied

Re: make reinstall does not work

> On 10. Dec 2017, at 6:59 PM, Kevin Oberman wrote: > > On Sat, Dec 9, 2017 at 11:19 PM, Greg 'groggy' Lehey > wrote: > >> On Saturday, 9 December 2017 at 12:04:02 +0100, Walter Schwarzenfeld >> wrote: >>> Thanks, this explains and solved the problem.

Re: make reinstall does not work

> On 9. Dec 2017, at 12:29 AM, Shawn Webb wrote: > > This is due to this commit: > https://github.com/freebsd/pkg/commit/7991c49665419916210ad589d4a85fd2a7f58b37 > > The standard procedure for reinstall is to do a deinstall first. I > guess it's pretty common just

Re: [HEADSUP] Flavors, and specifically, Python flavors landing today

> On 1. Dec 2017, at 9:28 AM, Mathieu Arnold <m...@freebsd.org> wrote: > > Le 01/12/2017 à 07:20, Franco Fichtner a écrit : >> Hi, >> >>> On 30. Nov 2017, at 4:32 PM, Mathieu Arnold <m...@freebsd.org> wrote: >>> >>> | See Ports

Re: [HEADSUP] Flavors, and specifically, Python flavors landing today

Hi, > On 30. Nov 2017, at 4:32 PM, Mathieu Arnold wrote: > > | See Ports now have flavors enabled| > | Tool developers, see https://wiki.freebsd.org/Ports/FlavorsTools| > | All Python dependencies must have @${PY_FLAVOR} appended to them| Very nice work, a thank you to all

Re: committer wanted for maintainer timeouts

Hi Kurt, > On 22. Nov 2017, at 3:49 PM, Kurt Jaeger wrote: > > Done. Many thanks! :) Cheers, Franco ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail

committer wanted for maintainer timeouts

Hi, Looking for a kind committer for these two issues: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218487 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222988 Thanks, Franco ___ freebsd-ports@freebsd.org mailing list

Re: portmaster, portupgrade, etc

> On 5. Oct 2017, at 9:47 AM, Eugene Grosbein wrote: > > On 05.10.2017 08:14, Adam Weinberger wrote: > >> Poudriere wants to be everything to everybody > > First poudriere will have to learn how to run without noticeable overhead > compared to "just build from ports"

Re: pkg issue after FreeBSD 11 upgrade

Hi Baptiste, > On 30. Aug 2017, at 3:05 PM, Baptiste Daroussin wrote: > >> No. At OPNsense we use a patch to revert the behaviour. >> >> https://github.com/opnsense/ports/blob/master/ports-mgmt/pkg/files/patch-libpkg_scripts.c > > Why and what is your use case, there is a

Re: pkg issue after FreeBSD 11 upgrade

Hi Cassiano, > On 30. Aug 2017, at 2:55 PM, Cassiano Peixoto > wrote: > > Why it used to work on FreeBSD 10? It stopped worked on FreeBSD 11 only. It was a later 10.x change as far as I know. > Is there some flag to disable it? Or some hack that I could do? No.

Re: security/libressl: Add the possibility to build only libtls

> On 21. Aug 2017, at 4:55 PM, Mathieu Arnold wrote: > >> Unless you build your own packages with OpenSSL from ports >> you can just install LibreSSL and use it in your programs... >> >> # pkg install libressl >> >> OpenSSL lives in the base system, LibreSSL will be an

Re: security/libressl: Add the possibility to build only libtls

> On 21. Aug 2017, at 11:59 AM, David Wahlund wrote: > > I'd like to use the libtls library of LibreSSL on FreeBSD. Or the python > bindings to libtls specifically. I do NOT however want to replace openssl or > use the libssl library. > > From what I understand it would be

Re: Pkg does not upgrade if more than one repository is defined

> On 28. Jul 2017, at 1:13 PM, Matt Smith wrote: > > This might also be related to the CONSERVATIVE_UPGRADE setting of pkg.conf. > According to the man page: > > CONSERVATIVE_UPGRADE: boolean > Ensure in multi repository mode that the priority is > given as much as

StrongSwan CVE-2017-9023 vuln.xml entry correction

Hi, An OPNsense user writes that the vuln.xml entry for CVE-2017-9023 has the wrong bound, it is less or equal to 5.5.2, not 5.5.3, see: https://www.strongswan.org/blog/2017/05/30/strongswan-vulnerability-(cve-2017-9023).html Can somebody correct this please? Thanks, Franco

Re: How to get pkg to recognize local repository?

> On 17. Jul 2017, at 8:44 AM, Thomas Mueller wrote: > > What meta files? There is a metamail-2.7_11.txz, but I don't think that's > what you meant. The files digests.txz, meta.txz and packagesite.txz, like this... https://pkg.opnsense.org/FreeBSD:11:amd64/17.1/latest/

Re: How to get pkg to recognize local repository?

> On 17. Jul 2017, at 7:10 AM, Thomas Mueller wrote: > > pkg-static: Ignoring bad configuration entry in > /usr/local/etc/pkg/repos/mytemprepo.conf: "file:///mnt/usr/packages/All" > pkg-static: Warning: Major OS version upgrade detected. Running "pkg-static > install -f

Re: Should a package restart on upgrade itself

Hi Matthias, As far as I know, pkg package scripts' runaway processes are reaped since a few versions, so you can't restart from there anymore. Maybe there is a way to detach correctly, I don't know. Cheers, Franco > On 27. Jun 2017, at 6:29 PM, Matthias Fechner wrote: >

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

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

Re: FreeBSD Port: lang/php71-extensions - missing php71-mssql

> On 15. May 2017, at 3:01 PM, Torsten Zuehlsdorff wrote: > >>> We are using php56-mssql for connecting to some MSSQL servers and we are >>> planning to upgrade to PHP 7.1 now but unfortunately I cannot find >>> php71-mssql port. >>> Why is it missing? Are there any problems

Re: FreeBSD Port: lang/php71-extensions - missing php71-mssql

> On 15. May 2017, at 2:53 PM, Miroslav Lachman <000.f...@quip.cz> wrote: > > We are using php56-mssql for connecting to some MSSQL servers and we are > planning to upgrade to PHP 7.1 now but unfortunately I cannot find > php71-mssql port. > Why is it missing? Are there any problems to build

Re: diff and submissions

> 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

zabbix server LibreSSL BROKEN improvement

Hi, I know this didn't fully time out yet, but it is a blanket? change that allows to build Zabbix Server higher than version 3 "with" LibreSSL by selecting a different crypto option (GnuTLS/PolarSSL) instead of failing the hard way all the time:

Suricata / Hyperscan ports timeouts

Hi ports, I would like to kindly ask for assistance on these port updates. Suricata has been lagging behind for quite some time now and for quality reasons FreeBSD must be quicker in adapting these patches. Yes, they work fine. Suricata developers take good care of FreeBSD compatibility

Re: Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?!

> On 9 Feb 2017, at 6:03 PM, Steve Wills wrote: > > Just because you don't use any features of the newer version doesn't > mean it's safe to run binaries built for the newer version on the older > version, as far as I understand it. True. :) Yet the reports are for

Re: Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?!

> On 9 Feb 2017, at 5:53 PM, Steve Wills wrote: > > What would enforcement look like? Something like "Sorry, you can't pkg > update because this system isn't supported any more."? But how would > that be possible without also breaking things for those who build/ship > their

Re: Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?!

> On 9 Feb 2017, at 5:53 PM, Steve Wills wrote: > > What would enforcement look like? Something like "Sorry, you can't pkg > update because this system isn't supported any more."? But how would > that be possible without also breaking things for those who build/ship > their

Re: Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?!

> On 9 Feb 2017, at 5:21 PM, Steve Wills wrote: > > We provide backwards compatibility, not forwards compatibility. But don't you see that users won't know this? This is a good theory, yet it is difficult in practice because it is not being enforced. Cheers, Franco

Re: Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?!

> On 9 Feb 2017, at 5:21 PM, Steve Wills wrote: > > We provide backwards compatibility, not forwards compatibility. But don't you see that users won't know this? This is a good theory, yet it is difficult in practice because it is not being enforced. Cheers, Franco

Re: Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?!

> On 9 Feb 2017, at 5:12 PM, Konstantin Belousov <kostik...@gmail.com> wrote: > > On Thu, Feb 09, 2017 at 04:30:20PM +0100, Franco Fichtner wrote: >> FreeBSD package management makes an ABI promise in the form of >> "FreeBSD:10:amd64", but not even pkg code i

Re: Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?!

> On 9 Feb 2017, at 4:47 PM, Steve Wills wrote: > > They're supposed to upgrade to a supported version of FreeBSD. pkg won't refuse the upgrade. And at least if it upgraded, it should not break itself. Imagine a GUI-driven appliance being bricked. There is nobody who can

Re: Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?!

Hi Steve, > On 9 Feb 2017, at 4:09 PM, Steve Wills wrote: > > Ports and packages are maintained on the assumption that the user is > using a supported version of the OS. We didn't decide when to end > support for 10.1 or 10.2. How long after the end of life for 10.1 would >

Re: Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?!

> On 9 Feb 2017, at 10:03 AM, Kirill Ponomarev <k...@krion.cc> wrote: > > On 02/09, Franco Fichtner wrote: >> >>> On 9 Feb 2017, at 9:49 AM, Kirill Ponomarev <k...@krion.cc> wrote: >>> >>> I don't understand all critics I see in this thread

Re: Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?!

> On 9 Feb 2017, at 9:49 AM, Kirill Ponomarev wrote: > > I don't understand all critics I see in this thread and in your mail, > the fate of this project is all in your hands - try to contribute more, I'm going to stop you right there. That's not entirely true. Too few

Re: Install of pkg fuse-ntfs fails because of undefined symbol in pkg!?!

> On 8 Feb 2017, at 12:29 PM, > wrote: > > I just tried to install the fuse-nfts pkg under 10.2 on my > server-of-all-work. But after requiring me to "upgrade" pkg, the > fuse-ntfs install failed, apparently because there's an undefined > symbol

pending PRs

Hi, Please have a look at either one of: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215313 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=215900 Thanks, Franco ___ freebsd-ports@freebsd.org mailing list

Re: Ports options in make.conf vs. GSSIAPI

> On 13 Jan 2017, at 1:40 PM, Stefan Bethke <s...@lassitu.de> wrote: > >> >> Am 13.01.2017 um 13:36 schrieb Franco Fichtner <fra...@lastsummer.de>: >> >> Hi Stefan, >> >>> On 13 Jan 2017, at 1:30 PM, Stefan Bethke <s...@lassitu.de>

Re: Ports options in make.conf vs. GSSIAPI

Hi Stefan, > On 13 Jan 2017, at 1:30 PM, Stefan Bethke wrote: > > For example, with dns/bind99, without options for that port in make.conf, I > can run make showconfig and other build commands without issue. As soon as I > add either of these: > #OPTIONS_UNSET+= GSSAPI_BASE

Re: openldap-client vs openldap-sasl-client

> On 9 Jan 2017, at 11:54 PM, Miroslav Lachman <000.f...@quip.cz> wrote: > > I don't need SASL for LDAP client, but somebody messed up ports tree with > WANT_OPENLDAP_SASL which is for users and not maintainers: > > # WANT_OPENLDAP_SASL > # - User-defined variable

Re: openldap-client vs openldap-sasl-client

> On 5 Jan 2017, at 11:44 AM, Julian Elischer wrote: > > On 5/01/2017 6:30 PM, Jan Bramkamp wrote: >> On 04/01/2017 18:32, Andriy Gapon wrote: >>> >>> Do you I understand correctly that it is impossible now to install both >>> samba44 >>> and libreoffice using the official

Re: OpenVPN 2.3.13+ and the subnet fix on FreeBSD 10.x

Hi, Turns out the issue could not be reproduced by the reporter anymore. Thanks to both mandree@ and OpenVPN for helping out so swiftly. The current 2.3.14 work as expected. Cheers, Franco > On 21 Dec 2016, at 11:47 AM, Franco Fichtner <fra...@lastsummer.de> wrote: > > Hi,

Re: HEADSUP: FLAVORS (initial version) and subpackages proposals

> On 23 Dec 2016, at 10:34 AM, Miroslav Lachman <000.f...@quip.cz> wrote: > > But we don't have that now. For example dns/py-dnspython can create > py27-dnspython, py33-dnspython, py34-dnspython, py35-dnspython - four > different packages from one origin, one Makefile. Noticed that too. This

OpenVPN 2.3.13+ and the subnet fix on FreeBSD 10.x

Hi, Looks like subnet fix has unfortunate consequences[1] in FreeBSD 10.x. Can we get this fixed before it hits quarterly? Cheers, Franco -- [1] https://github.com/opnsense/core/issues/1314 ___ freebsd-ports@freebsd.org mailing list

Re: HEADSUP: FLAVORS (initial version) and subpackages proposals

> On 20 Dec 2016, at 9:42 AM, Franco Fichtner <fra...@lastsummer.de> wrote: > > To emphasise on this: And lastly... if we have the automatic "default" flavour that is defined by the OPTIONS_DEFAULT knobs, we could finally avoid pkg upgrading custom builds by kn

Re: HEADSUP: FLAVORS (initial version) and subpackages proposals

> On 20 Dec 2016, at 9:27 AM, Franco Fichtner <fra...@lastsummer.de> wrote: > > We shouldn't use "-" or "/" anyway, should we? Please no fancy things > like "~" or so. No arbitrary package names... To emphasise on this: A flavour should act

Re: HEADSUP: FLAVORS (initial version) and subpackages proposals

Hi, > On 19 Dec 2016, at 1:31 AM, Baptiste Daroussin wrote: > > For flavors I would like to propose a simple approach first which is more > like a > rework of the slave ports for now: This progression sure is nice to see! I like "category/portname/flavour" origin a lot, but

Re: net/haproxy 1.7.0 : libressl support

> On 9 Dec 2016, at 11:51 AM, Dmitry Sivachenko wrote: > > If they reject it and refuse to support libressl for some reason, we will not > add your patches too, because this is not something FreeBSD-specific. Strongswan developers said similar things. Unfortunately, we

Re: security/heimdal timeout, committer wanted

> On 31 Oct 2016, at 6:04 PM, Mathieu Arnold <m...@freebsd.org> wrote: > > Le 31/10/2016 à 13:25, Franco Fichtner a écrit : >> Hi, >> >> A simple packaging fix for security/heimdal port is required to >> include two header files which are provided in base

security/heimdal timeout, committer wanted

Hi, A simple packaging fix for security/heimdal port is required to include two header files which are provided in base and security/krb5 and currently make sysutils/msktutil fail with option gssapi:heimdal. Thanks, Franco ___

Re: www/subsonic-standalone license

> On 28 Oct 2016, at 6:30 PM, Joshua Ruehlig wrote: > > I don't believe the maintainer dropped the project. I was talking about www/subsonic, sorry for the confusion: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213298 > If a user wants to use a previous version

Re: www/subsonic-standalone license

> On 28 Oct 2016, at 5:53 PM, Joshua Ruehlig wrote: > > Franco, what do you mean a maintainer drop? > Also Madsonic, which is supposedly GPL based on their website is available. The maintainer resigned, but updated to 6.0 because there were no distfiles, and the code

Re: www/subsonic-standalone license

> On 28 Oct 2016, at 4:41 PM, Joshua Ruehlig wrote: > > sure I'll take a look. I assume all I need to do is find and set the > current license? I would like to take this opportunity to ask why we have a maintainer drop whilst doing the upgrade of a free 5.3 to a

Re: lighttpd does not pull OpenSSL dependency

> On 27 Oct 2016, at 11:00 AM, Mathieu Arnold wrote: > > Le 26/10/2016 à 15:44, David Demelier a écrit : >> 2016-10-26 10:46 GMT+02:00 Mathieu Arnold : >>> Le 26/10/2016 à 00:14, Don Lewis a écrit : Then the question is, if DEFAULT_VERSIONS+=ssl=openssl

Re: make makepatch

> On 27 Oct 2016, at 8:28 AM, Jochen Neumeister wrote: > > Is this now right, that i can only use the new patch in /files? With > "make clean" i delete the work folder and the old patches. If all the previous patches patch a single file, makepatch will generate the patch

Re: make makepatch

> On 27 Oct 2016, at 7:53 AM, Jochen Neumeister wrote: > > No, make makepatch delete the patches into /files and: If there are no patches in files/ maybe you have no patches applied in the work/ dir? Does running "make patch" before makepatch help? Cheers, Franco

Re: make makepatch

Hi Jochen, > On 27 Oct 2016, at 7:47 AM, Jochen Neumeister wrote: > > what am i doing wrong? Doesn't makepatch already place the new patches in files/? Cheers, Franco ___ freebsd-ports@freebsd.org mailing list

Re: Alternatives to rsync

> On 14 Oct 2016, at 7:54 AM, Eduardo Morras via freebsd-ports > wrote: > > > Sorry for commenting on this reply to Greg to answer Shane Ambler, I > joined maillist today. > > On Fri, 14 Oct 2016 09:26:03 +1100 > Greg 'groggy' Lehey wrote: > >>

Re: Alternatives to rsync

> On 13 Oct 2016, at 6:39 AM, reko.turja--- via freebsd-ports > wrote: > > The software should be relatively lightweight - no fullblown mirroring/backup > is needed. Also hints how to achieve similar ends using maybe tar/ssh might > do. Try cpdup(1). Cheers,

pending security/suricata updates

Hi list, There are two pending updates for Suricata in bugzilla, would anybody willing to take these? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210490 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212815 Thank you, Franco ___

Re: Pkg doesn't care about conflict

> On 27 Sep 2016, at 5:05 PM, Miroslav Lachman <000.f...@quip.cz> wrote: > > Margaret wrote on 09/27/2016 14:55: > > [...] > >>> Did you stop pkg in the middle or did you let it go? I think it will >>> show you conflict message and ask you if you would like to deinstall PHP >>> 7.0 and install

net/samplicator: fix fetch and bump to 1.3.8rc1

Hi there, This moves port fetch to GitHub and (unfortunately) bumps to a newer version since there is no tag for the former version. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212811 The new version was already tested in a production environment and works as expected. Can provide a

sysutils/msktutil: fix fetch

Hi there, The msktutil home moved to SF. There is also a new version 1.0 that came out two days ago so it's active... but first things first. :) https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212810 Thanks, Franco ___ freebsd-ports@freebsd.org

Re: FreeBSD Port: devel/libsysinfo

Hi Kurt, > On 22 Sep 2016, at 1:37 PM, Kurt Jaeger wrote: > > Only if you provide one -- and a patch for the port. Within this Google Code fallout, is there a policy for how the submitted patches are committed? E.g. do they require maintainer approval? Are they priority

Re: Checking port option descriptions

> On 19 Sep 2016, at 12:59 PM, Miroslav Lachman <000.f...@quip.cz> wrote: > > In the end of this story - we are no longer using ports versions for any PHP > web applications. We are using them directly because ports were more > problematic. We use various PHP packages from ports for a larger

Re: OpenSSL port ASM removal

> On 19 Sep 2016, at 11:35 AM, Franco Fichtner <fra...@lastsummer.de> wrote: > > 3. Is AESNI support considered a must-have feature for the > OpenSSL port in FreeBSD or not? How about base OpenSSL? And > how does this affect the plans to switch to OpenSSL from ports &g

Re: OpenSSL port ASM removal

Hi Dirk, > On 19 Sep 2016, at 11:22 AM, Dirk Meyer wrote: > >> ASM support for OpenSSL is missing from the port now, >> which is kind of unfortunate for two reasons: >> (a) FreeBSD base (at least for i386 and amd64) has it. >> (b) ASM is required for AESNI to work

OpenSSL port ASM removal

Hi all, ASM support for OpenSSL is missing from the port now, which is kind of unfortunate for two reasons: (a) FreeBSD base (at least for i386 and amd64) has it. (b) ASM is required for AESNI to work last time I checked. Why was it removed? It's not clear from the commit message. LibreSSL

Re: Maintainership Status for PHP 5.6

Hi Kurt, > On 26 Aug 2016, at 9:08 PM, Kurt Jaeger wrote: > > I'm testbuilding 5.6.25 right now. Please please make sure to reset all the php56-* module's port revisions to zero if you do commit. This was missed in the php70 bump. Cheers, Franco

  1   2   >