Re: understanding 2025Q2 in aarch64

[Greg Troxel <gdt%lexort.com@localhost>]

Jonathan Perkin <jperkin%pkgsrc.org@localhost> writes:

> * On 2025-08-13 at 13:08 BST, Greg Troxel wrote:
>
>>I would definitely listen to jperkin.  I would think that changing the
>>URL back, pkgin up, pkgin fug, would return you to the previous step,
>>and if not it's a bug.   But then you get to keep both halves, figure it
>>out, and submit changes to fix the bug.
>
> I'd be very wary of classing it as a bug.  You can't reasonably handle
> going backwards with a SUPERSEDES as the previous repository will have
> no knowledge of it as we cannot predict the future.  The only way to
> do that would be to go back and retrospectively update all pkg_summary
> files in EOL repositories to add some new metadata that records a
> reverse SUPERSEDES entry somehow, and that's pretty impractical.

I see; I wasn't thinking clearly about SUPERSEDES.  But still, pkgin
could keep a log of having done such an operation.

I wonder how guix handles this.