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,
On Thu, Jan 02, 2020 at 02:50:04PM +0100, Jan Beich wrote:
> "Thomas Mueller" writes:
>
> >> This is why we practically beg people to use poudriere. There seems to
> >> be a pervasive misconception that poudriere is "advanced" and
> >> portmaster is simple or straightforward. That notion is
> Unequally, actually. portmaster still has some developers putting in
> the hard work to keep it running. portupgrade hasn't had much focused
> development in many years and should probably be removed from the
> tree. There are some problems with building on a live system that
> portmaster
Hi!
> What would be a secure alternative if one is needed?
> #) security/racoon2
> #) security/strongswan
This is also ipsec based.
> #) something else?
openvpn or wireguard
--
p...@opsec.eu+49 171 3101372Now what ?
[X-posted, please chose the relevant ML for such a thread]
Hi,
I am running ipsec-tools to implement a VPN tunnel (esp) between two hosts for
years now.
But this statement on http://ipsec-tools.sourceforge.net makes me think about
an alternative:
The development of ipsec-tools has
Kurt Jaeger wrote:
>> the recent renaming of security/openssl111 to security/openssl breaks
>> security/ipsec-tools.
>>
>> Have a look at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232169 for
>> details.
>
> Any reason you attach a patch to a closed/fix bug from Feb. 2019 ?
I am not
Hi!
> the recent renaming of security/openssl111 to security/openssl breaks
> security/ipsec-tools.
>
> Have a look at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232169 for
> details.
Any reason you attach a patch to a closed/fix bug from Feb. 2019 ?
This is a sure way to loose track
FYI,
the recent renaming of security/openssl111 to security/openssl breaks
security/ipsec-tools.
Have a look at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=232169 for
details.
Regards,
Michael
___
freebsd-ports@freebsd.org mailing list
Not sure if the top part of this is relevant:
-- => REST support is ON
CMake Warning at storage/connect/CMakeLists.txt:326 (FIND_PACKAGE):
By not providing "Findcpprestsdk.cmake" in CMAKE_MODULE_PATH this project
has asked CMake to find a package configuration file provided by
On Thu, Jan 02, 2020 at 12:22:20PM +0100, Stefan Eßer wrote:
> Am 01.01.20 um 22:04 schrieb Steve Kargl:
> > For users of mail/junkfilter, it now will filter all emails claiming
> > a "Bad Date line". The following patch seems to fix the problem for
> > the next decade.
>
> Hi Steve,
>
> thank
On Wed, Jan 1, 2020 at 7:56 PM Thomas Mueller wrote:
>
>
> > This is why we practically beg people to use poudriere. There seems to
> > be a pervasive misconception that poudriere is "advanced" and
> > portmaster is simple or straightforward. That notion is completely and
> > totally backwards.
"Thomas Mueller" writes:
>> This is why we practically beg people to use poudriere. There seems to
>> be a pervasive misconception that poudriere is "advanced" and
>> portmaster is simple or straightforward. That notion is completely and
>> totally backwards. Poudriere makes managing ports as
Am 01.01.20 um 22:04 schrieb Steve Kargl:
> For users of mail/junkfilter, it now will filter all emails claiming
> a "Bad Date line". The following patch seems to fix the problem for
> the next decade.
Hi Steve,
thank you for providing a patch. Since the maintainer (gsutter) has
not been active
On Wed, 1 Jan 2020 23:28:30 +0100
Kurt Jaeger wrote:
>
> For example: FreeBSD uses mailman2 for lists.freebsd.org, which needs
> python 2.7, which, as far as the python community is involved,
> is no longer supported.
>
py27-backports-1
14 matches
Mail list logo
