All,
I've been experimenting with updating PCNS with support for FreeBSD
and at this point it's looking like this can be done entirely by
patching installation files. I'm curious if others on the list would
have any appetite for this becoming a port. The only catch is the
software is not redistrib
If no one else is interested, I'm happy to take on maintaining
comms/hidapi as I already have to track upstream releases for an
unrelated project. Is there a process beyond submitting a patch to
Bugzilla (I've had spotty luck in the past getting patches seen)?
Cheers,
Steve
On Mon, Jan 9, 2023 at
t; Basically I use a Jain running Poudriere to test the changes in a their
> own git branch, the make sure the main branch is up to date and my
> branch is rebased before using "arc diff --create" to upload the patch
> to reviews.freebsd.org
>
> On Mon, 9 Jan 2023 15:07:02
Thanks!
On Tue, Jan 10, 2023 at 10:25 AM Nuno Teixeira wrote:
>
> Done,
>
> Cheers
>
> Steven Stallion escreveu no dia terça, 10/01/2023 à(s)
> 14:34:
>>
>> Thanks for the info! I've submitted a patch to Bugzilla here:
>> https://bugs.freebsd.org/
All,
After updating to the quarterly branch my rdiff-backup jobs began
failing. It looks like rdiff-backup snuck in a dependency on
devel/py-yaml. I've filed a bug with a patch to address this issue and
to update the port to version 2.2.2.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=268863
All,
After 13.0-RELEASE was made public, I set about updating my systems to
take advantage of /var/run/motd and began generating dynamic content
on demand rather than rely on update_motd. This has worked so well I
created a new project on GitHub and I submitted a new port back in
October: https://
On Tue, Oct 18, 2022 at 7:42 PM Steven Stallion wrote:
> I've been experimenting with updating PCNS with support for FreeBSD
> and at this point it's looking like this can be done entirely by
> patching installation files. I'm curious if others on the list would
>
All,
I submitted https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267107 6
months ago in October. It's been picked up, however there's been no
movement. Could someone take a look when they have a moment?
Thanks in advance,
Steve
On Mon, Apr 17, 2023 at 2:32 AM Matthew Seaman wrote:
> I'll certainly do that. Give me a little while to run some tests:
> should be able to get this into the ports today. This bug report wasn't
> actually picked up by anyone with any agency to commit anything: the
> auto assignment to freebsd-
All,
Are there any plans to fix vulnerabilities in py311-Jinja2-3.1.3 on
the quarterly branch?
Cheers,
Steve
10 matches
Mail list logo