Unmaintained FreeBSD ports which are out of date

2024-01-12 Thread portscout
Dear port maintainers, The portscout new distfile checker has detected that one or more unmaintained 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. Please consider also adopting this po

Re: Latest and quarterly best practices

2024-01-12 Thread Tomoaki AOKI
On Sat, 13 Jan 2024 02:52:18 +0100 Jan Beich wrote: > Jose Quinteiro writes: > > > Maybe there are some ports that should not exist in the quarterly > > branch? Looks like some of these are under such heavy development that > > they really don't have a stable version. > > Hyprland release cade

Re: Latest and quarterly best practices

2024-01-12 Thread Jan Beich
Jose Quinteiro writes: > Maybe there are some ports that should not exist in the quarterly > branch? Looks like some of these are under such heavy development that > they really don't have a stable version. Hyprland release cadence is similar to Chromium and Firefox.

Re: FreeBSD ports disabled for bsdforge

2024-01-12 Thread Jamie Landeg-Jones
Alexey Dokuchaev wrote: > It was very rash, but for endangered ports, they'll use any possibility. Fair enough. > Muhammad seldom responds to email these days; for both of them I believe > this situation (Chris' domain renewal and him coming back online) is > uncomfortable as they both want for

Re: FreeBSD ports disabled for bsdforge

2024-01-12 Thread Jamie Landeg-Jones
Daniel Engberg wrote: > I'd also like to remind people much work related to ports is not paid > and what that all entails. I don't know anthing about the history behind the scenes, and I wasn't making a personal attack on your work with ports. I know it's unpaid, but I'll also remind you that wh

Re: FreeBSD ports disabled for bsdforge

2024-01-12 Thread Jamie Landeg-Jones
Gleb Popov wrote: > > But I didn't realise it was only 6 days! Jeeze, I have many PR's that > > haven't > > been looked at it months! > > There is a misconception that portmgr@ is in charge of going through > open unassigned PRs and committing them. But this is actually ports > committers' job.

Re: Latest and quarterly best practices

2024-01-12 Thread Rene Ladan
On Fri, Jan 12, 2024 at 09:51:06AM -0800, Jose Quinteiro wrote: > > > On 1/4/24 12:19, Jan Beich wrote: > > henrichhart...@tuta.io writes: > > > >> I propose that as a rule of thumb, if a package uses Semantic > >> Versioning (semver) and the changes are non-breaking, it should be > >> cherry pi

Re: FreeBSD ports disabled for bsdforge

2024-01-12 Thread Daniel Engberg
Hi, There multiple reasons why we took action on this such as: * Security, it's not uncommon for expired domains to turn into rouge ones * Several days of downtime is general not considered a small hiccup and since there was no communication about it action was taken based on the information tha

Re: Latest and quarterly best practices

2024-01-12 Thread Jose Quinteiro
On 1/4/24 12:19, Jan Beich wrote: > henrichhart...@tuta.io writes: > >> I propose that as a rule of thumb, if a package uses Semantic >> Versioning (semver) and the changes are non-breaking, it should be >> cherry picked into quarterly. Especially if this is only a patch level >> change and not

Re: FreeBSD ports disabled for bsdforge

2024-01-12 Thread Chris
On 2024-01-12 07:04, Gleb Popov wrote: On Fri, Jan 12, 2024 at 5:00 PM Jamie Landeg-Jones wrote: I thought it was a bit rash of them to do all that so soon (it was obvious that the domain hadn't expired completely, as I could see that you renewed it before it was returned to being "unused".)

Re: FreeBSD ports disabled for bsdforge

2024-01-12 Thread Chris
On 2024-01-12 06:44, Alexey Dokuchaev wrote: On Fri, Jan 12, 2024 at 02:00:04PM +, Jamie Landeg-Jones wrote: Chris wrote: ... > NO! I missed the domain renewal by 5 days. So domain went unavailable. > I fixed it on the 6th day. I thought it was a bit rash of them to do all that so soon (it

editor/linux-wps-office; stop-errors

2024-01-12 Thread J.
Hello everyone, I'm new to the ports mailing list, and indeed rather new to UNIX/FreeBSD. I like working with WPS Office (the Writer application) due to it being rather compatible with Amazon KDP, which is Amazon's self-publishing platform. I'm used to running WPS Office on Windows and tried to

games port update to commit

2024-01-12 Thread Pavel Timofeev
Hello Can any ports committer take a look at this please? games/jaggedalliance2: update to 0.21.0 -- https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275379 Thank you!

Re: FreeBSD ports disabled for bsdforge

2024-01-12 Thread Gleb Popov
On Fri, Jan 12, 2024 at 5:00 PM Jamie Landeg-Jones wrote: > > I thought it was a bit rash of them to do all that so soon (it was obvious > that the domain hadn't expired completely, as I could see that you renewed > it before it was returned to being "unused".) > > But I didn't realise it was only

Re: FreeBSD ports disabled for bsdforge

2024-01-12 Thread Alexey Dokuchaev
On Fri, Jan 12, 2024 at 02:00:04PM +, Jamie Landeg-Jones wrote: > Chris wrote: > ... > > NO! I missed the domain renewal by 5 days. So domain went unavailable. > > I fixed it on the 6th day. > > I thought it was a bit rash of them to do all that so soon (it was obvious > that the domain hadn'

Re: FreeBSD ports disabled for bsdforge

2024-01-12 Thread Tomoaki AOKI
On Thu, 11 Jan 2024 15:17:55 -0800 Chris wrote: > On 2024-01-11 03:26, Jamie Landeg-Jones wrote: > > Hi, have you seen this? > > > > https://cgit.freebsd.org/ports/commit/?id=82b56c14531faee93344e59d3ec30dcc3cf5c2e0 > > > > Cheers, Jamie > > NO! I missed the domain renewal by 5 days. So domain

Re: FreeBSD ports disabled for bsdforge

2024-01-12 Thread Jamie Landeg-Jones
Chris wrote: > NO! I missed the domain renewal by 5 days. So domain went unavailable. I > fixed it on > the 6th day. I thought it was a bit rash of them to do all that so soon (it was obvious that the domain hadn't expired completely, as I could see that you renewed it before it was returned to