On 2025-05-01 12:45, Kurt Jaeger wrote:
Hi!
It looks as though the maintainer has approved this patch which is to
remedy PowerDNS Security Advisory 2025-01 (CVE-2025-30195) and some minor
fixes. Can any committer give this a little love please? :)
Just a little, yes 8-}
Many thanks Kurt!
On 2023-05-08 12:40, Mark Millard wrote:
Simon Wright wrote on
Date: Mon, 08 May 2023 01:36:45 UTC :
I am using poudriere to build a small selection of posts with
non-default options. This is working fine, however for the daily
security run on the VM that runs poudriere, I am seeing this
Hi all,
I am using poudriere to build a small selection of posts with
non-default options. This is working fine, however for the daily
security run on the VM that runs poudriere, I am seeing this warning:
===
Checking for security vulnerabilities in base (userland & kernel):
On 2022-12-12 14:50, Kevin Oberman wrote:
On Sun, Dec 11, 2022 at 7:35 PM Simon Wright wrote:
On 2022-12-12 10:36, Mark Millard wrote:
Simon Wright wrote on
Date: Mon, 12 Dec 2022 00:13:20 UTC :
If I look at the report on:
https://pkg-status.freebsd.org/builds?jailname=131amd64&
On 2022-12-12 10:36, Mark Millard wrote:
Simon Wright wrote on
Date: Mon, 12 Dec 2022 00:13:20 UTC :
If I look at the report on:
https://pkg-status.freebsd.org/builds?jailname=131amd64&type=package&all=1
the status on 131amd64 default (on beefy16) is: parallel_build, started
10
Hi all,
I hope that someone can shed light on why I am seeing differing status
messages from the package build cluster.
If I look at the report on:
https://pkg-status.freebsd.org/builds?jailname=131amd64&type=package&all=1
the status on 131amd64 default (on beefy16) is: parallel_build, started
On 2022-11-11 01:58, Chris wrote:
On 2022-11-09 17:46, Simon Wright wrote:
I don't want to buy a proxy just to access one small file once or twice
a day and free ones seem to be very very thin on the ground. Can anyone
recommend a free IPv4 to IPv6 proxy service?
Hurricane Electric:
On 2022-11-10 11:27, Simon Wright wrote:
On 2022-11-10 10:58, Jan Beich wrote:
Simon Wright writes:
My issue is that since the build servers are IPv6-only and my provider
in Philippines does not offer any IPv6 service at all, I need to use a
proxy to use curl to access this file:
http
On 2022-11-10 10:58, Jan Beich wrote:
Simon Wright writes:
My issue is that since the build servers are IPv6-only and my provider
in Philippines does not offer any IPv6 service at all, I need to use a
proxy to use curl to access this file:
http://beefy16.nyi.freebsd.org/data/131amd64-default
Hi all!
I have a script to update my local ports tree to the same version being
used to build the Freebsd packages, then poudriere to build my own
packages where I want or need different options from default. I do this
to minimise issues with mixing package version since I don't want to
build *al
r than it used to
be, though I still need to look up usage if I need to do anything manually!
Just my two cents worth . . . .
--
Simon Wright
simon.wri...@gmx.net
smime.p7s
Description: S/MIME Cryptographic Signature
On 17/03/2022 08:01, Mark Millard wrote:
The armv7 style build failed with:
===> Building package for llvm14-14.0.0.r2
pkg-static: Unable to access file
/wrkdirs/usr/ports/devel/llvm14/work/stage/usr/local/llvm14/lib/clang/14.0.0/include/riscv_vector.h:No
such file or directory
pkg-static
Thanks for the update Moin and good luck with progress!
On 04/03/2022 13:08, Muhammad Moinur Rahman wrote:
It’s under process.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261523
Kind Regards,
Moin (bofh)
On 4 Mar 2022, at 05:09, Simon Wright wrote:
I've seen the notice about EO
Hi all,
I've seen the notice about EOL for this port and that it will expire at
the end of June this year. No problem there but I notice that the
default version in Mk/bsd.default-versions.mk is still set to 5.
Shouldn't this be updated to 18 before the next quarterly release and a
note added to
r, roll changes back to remove the faulty package?
Regards,
Simon.
On 21/06/2021 2:56 pm, Mathieu Arnold wrote:
On Mon, Jun 21, 2021 at 07:46:50AM +0800, Simon Wright wrote:
Hi Mat and all,
ISC released a warning not to upgrade to versions 9.16.17 or 9.17.14
which Xavier Humbert forwarded to po
poudriere has built bind-9.16.17
and bind-tools-9.16.17 for distribution which is the version warned about.
This bug has been corrected in 9.16.18
https://bind9.readthedocs.io/en/v9_16/notes.html#notes-for-bind-9-16-18.
Shouldn't 9.16.17 have been skipped and these ports moved straight to
9.16.18?
Hi all,
Looking for a committer for this drupal7 security patch please,
maintainer timeout.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255417
--
Thanks,
Simon.
On 23/05/2021 10:14 am, Charlie Li wrote:
Simon Wright wrote:
OK, I can do that though it will take a day or two to rebuild
everything. These are my ssl settings in the two active make.conf for
poudriere. What would you advise to set there in order to only use
openssl from base? Or conversely
On 23/05/2021 8:17 am, Tatsuki Makino wrote:
I haven't followed everything, but have you tried to rebuild libressl?
poudriere bulk -j FreeBSD:13:amd64 -p default -C security/libressl
And, here's a check for complete synchronization of port tree.
git -C ${BASEFS}/ports/default status
I haven't
On 23/05/2021 8:29 am, Charlie Li wrote:
Simon Wright wrote:
Thanks for this. My ports tree is synched to the package server for
amd64-default, ie. b093791110
I'm not mixing SSL's, here again are my make.conf files:
make.conf
There is no jail-specific make.conf or -z o
rs),
if it succeeds I'll update all my boxes with the new ports using base
openssl instead of libressl then update the ports tree and start another
build with libressl to see how it goes with your commit.
--
Regards,
Simon.
On 23/05/2021 1:05 am, Charlie Li wrote:
Simon Wright wrote:
Hi all,
21 matches
Mail list logo
