Re: pkg/59626 (compat80-* distfiles missing from all repositories)

The following reply was made to PR pkg/59626; it has been noted by GNATS.

From: Havard Eidnes <[email protected]>
To: [email protected], [email protected]
Cc: [email protected], [email protected], [email protected],
 [email protected], [email protected]
Subject: Re: pkg/59626 (compat80-* distfiles missing from all repositories)
Date: Thu, 12 Feb 2026 11:23:19 +0100 (CET)

 > he@: you originally created this package [...]
 
 Well, yes and no.
 
 I may very well have been the one who last updated the package.
 
 However, I cannot claim to be the original author of the package.
 
 > [...], could you please take a look?
 
 When I fiddled with it the last time I found it a little
 difficult to figure out how to align the various bits to make it
 possible to perform the update.  Sadly, I did not improve that
 particular aspect by creating a suitable README.updating file or
 anything like that.
 
 I also see in the CVS log that the package is accused of being
 cursed, and that bad things can happen if it's un-installed after
 having been installed.  I vaguely recall that was something I
 thought about when I did the previous update, e.g. when creating
 revision 1.3 of
 
   emulators/compat_netbsd/INSTALL.ELF
 
 However, in hindsight, whether that actually cured the curse (it
 would certainly not cure it for already-installed instances) I
 cannot now claim with any amount of certainty.  Possibly it
 didn't.
 
 It is evident to me that this package and documentation of "how
 to update" and the overall "an overview of this is what the
 update procedure does" needs to be tackled first, and we can then
 hopefully both make it easier for others to perform the update,
 and make it easier to properly fix the "curse" as well.
 
 That said, I have found my local copy of the computed distfiles
 which used to live in the 20191014/ subdirectory (the checksums
 seem to match with what's in the existing distinfo), and I'm able
 to upload them again to "un-break" the immediate breakage of this
 package.  That may be the shortest path to fixing the immediate
 problem, and then we can tackle the ones which require more
 scrutiny and discussion as a separate thing.
 
 Regards,
 
 - H=E5vard