Re: wifi-firmware-kmod-release-20241017 is not a unique package name; wifi-firmware-kmod-20241017 also is not

From: Mark Millard <marklmi_at_yahoo.com>
Date: Wed, 18 Dec 2024 20:05:50 UTC
On Wed, 18 Dec 2024, Mark Millard wrote:

> On Dec 18, 2024, at 10:55, Bjoern A. Zeeb <bz@freebsd.org> wrote:. . .
> . . .
> No!  Makefile.inc != Makefile

Yep: I looked in the wrong file, for sure. Sorry for the horrible noise.

And, so, what survives in my reporting is the @8000's destroyed content of 
its log file for the Ignore port when @22000 was processed for the same
package and origin: the release flavor of wifi-firmware-kmod . That would
be a poudriere problem with preserving log file information.

In more detail . . .

1623 wifi-firmware-kmod-release-20241017 net/wifi-firmware-kmod@release 0 Dependent port net/wifi-firmware-iwlwifi-kmod@8000 | wifi-firmware-iwlwifi-kmod-8000-20241017.1500029_1 ignored

had its log file content in:

. . ./main-armv7-default/peb87cb7f3aa2_s48d92db080/logs/wifi-firmware-kmod-release-20241017.log

but that content was later replaced by the content for:

1629 wifi-firmware-kmod-release-20241017 net/wifi-firmware-kmod@release 0 Dependent port net/wifi-firmware-iwlwifi-kmod@22000 | wifi-firmware-iwlwifi-kmod-22000-20241017.1500029_1 ignored

because both used the name:

. . ./main-armv7-default/peb87cb7f3aa2_s48d92db080/logs/wifi-firmware-kmod-release-20241017.log

and it was not an appending of log information --the content ended up only
being present for the second (1629 a.k.a. @22000 in the example).

So this note is now to Bryan D. for that issue for future reference.

===
Mark Millard
marklmi at yahoo.com