Colin Percival wrote on 2023/05/04 15:42:
> A recent commit (be67c1c353ca) broke Portsnap's INDEX generation; somehow
I understood what was going on.
Thank you very much.
I will adopt a different approach for a while. pkg version -P ... , make -C
/usr/ports fetchindex , or others.
Regards.
* Colin Percival [20230503 23:42]:
> My guess is that this is due to the Portsnap builder using an out-of-date
> environment for running `make describe`; the ports commit in question
> probably relies on something which changed in make(1) in the past decade.
> I'm going to try to track this down a
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
On Wed, May 03, 2023 at 08:16:01PM -0700, Mark Millard wrote:
>
> I gather you are not building your own ports for
> this context.
I certainly didn't build the initial installation of git
for this host. IIRC, the sequence was
Set up disk
install git via pkg from public repository
clone /usr/src
tl;dr Removing feature patches in mail/mutt! Do you care?
A recent bug [1] has been created with a claim that one of the remote
patches QUOTE_PATCH [2] causes issues even without using the feature.
This patch was originally a vvv patch [3] left unmaintained then later
taken over by some capacity
On Fri, May 5, 2023 at 12:33 AM Derek Schrock wrote:
>
> tl;dr Removing feature patches in mail/mutt! Do you care?
> (..)
> So do any of the ports/pkg mutt users deeply depend on any feature
> patches from the port and would the world end if you didn't have them?
I mainly use mutt to quickly revi
On Thu, May 04, 2023 at 06:33:05PM -0400, Derek Schrock wrote:
> tl;dr Removing feature patches in mail/mutt! Do you care?
>
> A recent bug [1] has been created with a claim that one of the remote
> patches QUOTE_PATCH [2] causes issues even without using the feature.
> This patch was originally
On 5/4/23 02:09, Felix Palmen wrote:
* Colin Percival [20230503 23:42]:
My guess is that this is due to the Portsnap builder using an out-of-date
environment for running `make describe`; the ports commit in question
probably relies on something which changed in make(1) in the past decade.
I'm g
