Re: quarterly 2024Q3 amd64 / 13.3 missing all vital packages for desktop

Hi Miroslav, Please see my email titled: "Quarterly backport for multimedia/x265 patch" sent to this list a few hours before yours. Shortly after sending it, the patch was committed to 2024Q3. Builders will have to catch up, but hopefully things can be resolved. I do feel like this could have

Quarterly backport for multimedia/x265 patch

Hi all, There's been a lot of packages that haven't been built in quarterly because of a checksum mismatch. I think this affected latest as well for a little while, but that's been resolved. Here's some information on the extent of the issue: https://forums.freebsd.org/threads/disappearance-of

Re: git: 0668752 Revert "Framework: Introduce bsd.sponsor.mk"

Jun 25, 2024, 07:39 by free...@omnilan.de: >> Revert "Framework: Introduce bsd.sponsor.mk" >> >> This reverts commit 274cd4df4dcce0a9aa78da47bb6e35ab3dbcbf8c >> > > > See also: > https://reviews.freebsd.org/D44487 > > >  In D44487#1014651, @mat wrote: > >>> >>> > >> but we want users to st

Taking over net/ndisc6, or adding it to src?

Hi everyone, I see that net/ndisc6 doesn't have a maintainer. As a long time user of the tool, I'd be happy to take it over. That said, I was wondering if this package might be a candidate for src? It's tiny and useful. You can do the same sort of thing as rdisc6 with ntsol -D, but I don't thi

2024Q2 branch

Hi Everyone, I'm wondering when 2024Q2 will be cut. I assumed it would have been already. Are there any blockers before it's cut? Thank you! -Henrich

No word from maintainer, but have patch to fix build

Hi everyone, I haven't heard back from the maintainer of net-p2p/qbittorrent. I opened the original issue 3 weeks ago and almost 2 weeks with a patch. Not sure what the traditional timeframe is to give. Would someone be able to review this? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=277

Merge access review + QT6 update best practices

Hi everyone, I have two requests for help. First one is that I updated one of my ports, but I don't have merge access. Would appreciate it if someone can review. Ideally would merge to main + backport to quarterly. If there's something missing in the report that should be there, please let me

Re: "py-" prefix shouldn't be needed for Python-based ports that are programs, not libraries

I agree with this. Some Python libraries are grey areas where they have helper programs and a library. Or a full on program and a library. But some make a very clear distinction and are not designed to be imported at all. Those would probably be fine to drop the py- prefix, and associate it with

Re: Latest and quarterly best practices

Hi Ronald and all, Sorry for the wait on this. I didn't mean to stir up any controversy. I think the general guidelines are good. I have requested many times that a particular package update be backported into quarterly. I was mainly just hoping to put this out in the open so more people migh

Latest and quarterly best practices

Hi, I'm not a committer so this shouldn't carry much weight. Just wanted to express my opinion. I think the latest and quarterly setup is a nice and clever one. Unfortunately, it seems fairly often that ports that should probably be cherrypicked into quarterly are not. Occasionally, some updat