zstd-1.5.2 is a bug-fix release. From
https://github.com/facebook/zstd/releases/tag/v1.5.2:
- As a side-effect of the inclusion of assembly code in our source tree,
binary artifacts were being marked as needing an executable stack on
non-amd64 architectures. This release corrects that issue. Mo
Generally only folks who can commit to CVS should be asking "ok?"
It signals to others that you are also an OpenBSD dev. One might think
that doing this may get you quicker reivew attention, except it may also
mean that you get an ok and your work never gets committed. Why? Because
we'll assume yo
On Thu, 20 Jan 2022 08:44:22 +
Stuart Henderson wrote:
> On 2022/01/19 08:27, Ed Ahlsen-Girard wrote:
> [...]
> [...]
> [...]
>
> If you run a base system build as root, it automatically drops to the
> "build" user. So either /usr/obj needs to be writable by "build", or
> don't run
https://docs.python.org/release/3.9.10/whatsnew/changelog.html
I don't see any security issues fixed here, but numerous bug fixes.
Test suite passes mostly equivalent on amd64. test_poplib is an additional
test failure. Which is their pop3 library test. Since I run PORTS_PRIVSEP
I'm not surprised
On Wed, Jan 19, 2022 at 04:15:51PM +0100, Antoine Jacoutot wrote:
> Hi.
>
> Is there any reason why x11/qt5/qtwebengine RUN_DEPENDS on x11/gtk+3,-cups?
> Should we remove it?
Anyone?
>
> Index: Makefile
> ===
> RCS file: /cvs/port
On Wed, Jan 19, 2022 at 12:51:49PM -0500, Ian Darwin wrote:
> Update to 4.6.7, which uses log4j 2.1.7. Use modern Java runtime. Drop
> some trivial sampled files. Use provided class files instead
> of compiling, to speed build. Take Maintainer in case I'm the only
> one still using it :-).
>
Jus
On Thu, Jan 20, 2022 at 05:34:42PM +0100, Omar Polo wrote:
> Tracey Emery writes:
>
> > How about this for the README?
>
> way better, thanks!
>
> Here's a revised diff with your tweaks to the README and
> FIX_EXTRACT_PERMISSIONS. I don't remember why, my user was in the
> _pbuild group... Th
Tracey Emery writes:
> How about this for the README?
way better, thanks!
Here's a revised diff with your tweaks to the README and
FIX_EXTRACT_PERMISSIONS. I don't remember why, my user was in the
_pbuild group... Thanks semarie for the help!
Index: Makefile
Hi,
Update for Axel to 2.17.11:
https://github.com/axel-download-accelerator/axel/releases/tag/v2.17.11
OK? Comments?
Cheers.-
--
%gonzalo
Index: Makefile
===
RCS file: /cvs/ports/net/axel/Makefile,v
retrieving r
Omar Polo writes:
> Aaron Bieber writes:
>
>> Hi!
>>
>> Here is a handy tool that can be used to find common issues in Go code.
>>
>> I recently used it on security/ogvt with great success!
>>
>> Information for inst:gosec-2.9.5
>>
>> Comment:
>> security checker for Go projects
>>
>> Descript
Aaron Bieber writes:
> Hi!
>
> Here is a handy tool that can be used to find common issues in Go code.
>
> I recently used it on security/ogvt with great success!
>
> Information for inst:gosec-2.9.5
>
> Comment:
> security checker for Go projects
>
> Description:
> Inspects source code for secur
How about this for the README?
Index: pkg/README
===
RCS file: /cvs/ports/net/gophernicus/pkg/README,v
retrieving revision 1.5
diff -u -p -u -r1.5 README
--- pkg/README 4 Sep 2018 12:46:17 - 1.5
+++ pkg/README 20 Jan 2022
Tracey Emery writes:
> On Thu, Jan 20, 2022 at 10:07:13AM +0100, Omar Polo wrote:
>> Hello ports,
>>
>> Please find attached a diff to update net/gophernicus to the latest
>> version.
>>
>> The changelog for 3.1.0 is quite interesting, as they added pledge(2)
>> and unveil(2) support and change
On Thu, Jan 20, 2022 at 10:07:13AM +0100, Omar Polo wrote:
> Hello ports,
>
> Please find attached a diff to update net/gophernicus to the latest
> version.
>
> The changelog for 3.1.0 is quite interesting, as they added pledge(2)
> and unveil(2) support and changed the build system (among other
On Thu, Jan 20, 2022 at 10:07:13AM +0100, Omar Polo wrote:
> Hello ports,
>
> Please find attached a diff to update net/gophernicus to the latest
> version.
>
> The changelog for 3.1.0 is quite interesting, as they added pledge(2)
> and unveil(2) support and changed the build system (among other
Hi!
Here is a handy tool that can be used to find common issues in Go code.
I recently used it on security/ogvt with great success!
Information for inst:gosec-2.9.5
Comment:
security checker for Go projects
Description:
Inspects source code for security problems by scanning the Go AST.
Mainta
Bump...
On 1/16/22 16:48, Volker Schlecht wrote:
Update after feedback from abieber@
Hello ports,
Please find attached a diff to update net/gophernicus to the latest
version.
The changelog for 3.1.0 is quite interesting, as they added pledge(2)
and unveil(2) support and changed the build system (among other things.)
3.1.1 is just some bugfixes on the build system.
Unfortunately
On 2022/01/20 10:07, Renaud Allard wrote:
>
>
>
> On 1/20/22 10:06, Renaud Allard wrote:
> > Hi Stuart,
> >
> > On 1/20/22 09:40, Stuart Henderson wrote:
> > > On 2022/01/20 09:23, Renaud Allard wrote:
> > > > - ./logs/tracker-server.log
> > > > -+ > > > key='logger.file'>/var/log/trac
On 2022/01/19 08:27, Ed Ahlsen-Girard wrote:
> On Wed, 19 Jan 2022 11:04:09 +
> Stuart Henderson wrote:
>
> > On 2022/01/18 19:23, Ed Ahlsen-Girard wrote:
> > [...]
> >
> > First thing to try is a self-built kernel to check if it's some
> > uncommitted diff being tested in snapshots.
> >
On 2022/01/20 09:23, Renaud Allard wrote:
> -./logs/tracker-server.log
> -+/var/log/traccar/tracker-server.log
> ++ key='logger.file'>${VARBASE}/log/traccar/tracker-server.log
I think this should just use /var/log
Also (not new), I noticed this in the patch, doesn't seem quite right?
21 matches
Mail list logo
