Re: INDEX-12 gotten by portsnap is not updated

2023-05-05 Thread Felix Palmen
* Colin Percival [20230505 08:12]: > Older bmake handles ${FOO:%=bar%} with an empty FOO by matching % to the > empty string. In 2020, NetBSD changed this to non-matching "for gmake > compatibility". That's indeed a weak reason, I would have expected the reason to be "do what original AT&T make

Re: INDEX-12 gotten by portsnap is not updated

2023-05-05 Thread Colin Percival
On 5/5/23 07:53, Felix Palmen wrote: * Colin Percival [20230505 07:46]: On 5/4/23 23:47, Colin Percival wrote: Indeed.  I think I've fixed it by copying a newer /usr/bin/make into the build environment -- I should be able to confirm whether it works soon. Confirmed, portsnap's INDEX is worki

Re: INDEX-12 gotten by portsnap is not updated

2023-05-05 Thread Felix Palmen
* Colin Percival [20230505 07:46]: > On 5/4/23 23:47, Colin Percival wrote: > > Indeed.  I think I've fixed it by copying a newer /usr/bin/make into the > > build environment -- I should be able to confirm whether it works soon. > > Confirmed, portsnap's INDEX is working again. :-) Thanks for le

Re: INDEX-12 gotten by portsnap is not updated

2023-05-05 Thread Colin Percival
On 5/4/23 23:47, Colin Percival wrote: On 5/4/23 02:09, Felix Palmen wrote: I have a possible update for this commit that avoids the part that *seems* to be problematic here. It's more verbose now, but probably also more readable, so, will put this up for review soon. But probably it still make

Re: INDEX-12 gotten by portsnap is not updated

2023-05-04 Thread Colin Percival
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

Re: INDEX-12 gotten by portsnap is not updated

2023-05-04 Thread Felix Palmen
* 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

Re: INDEX-12 gotten by portsnap is not updated

2023-05-04 Thread Tatsuki Makino
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.

Re: INDEX-12 gotten by portsnap is not updated

2023-05-03 Thread Colin Percival
On 5/3/23 21:11, Kyle Evans wrote: On Wed, May 3, 2023 at 10:50 PM Tatsuki Makino wrote: It appears that INDEX-12 (DESCRIBE.12) has not been updated by portsnap for several days. For example, gstreamer1 remains in the following version zgrep -e ^gstreamer1-1 /var/db/portsnap/files/e24b4779*a

Re: INDEX-12 gotten by portsnap is not updated

2023-05-03 Thread Kyle Evans
On Wed, May 3, 2023 at 10:50 PM Tatsuki Makino wrote: > > Hello. > > It appears that INDEX-12 (DESCRIBE.12) has not been updated by portsnap for > several days. > For example, gstreamer1 remains in the following version > > > zgrep -e ^gstreamer1-1 /var/db/portsnap/files/e24b4779*a78a1f31.gz | cu