djgpp packages could be dropped severely outdated

[Jon Turney]

On 28/08/2025 17:53, ASSI via Cygwin-apps wrote:
> Brian Inglis via Cygwin-apps writes:
>> Only messages I got from issuing vault commands were:
>>
>> vault: package 'djgpp-binutils' version '2.25-2' marked as expirable
>> vault: package 'djgpp-gcc' version '5.3.0-1' marked as expirable
>> vault: package 'djgpp-gcc' version '5.4.0-1' marked as expirable
>> vault: package 'djgpp-runtime' version '2.05-1' marked as expirable
>>
>> but none of the usual vault emails and they still appear in the setup
>> master and git:

Hmm.. yeah, the person who requested the vaulting is supposed to be 
included in the interest list to get emailed the results, but that 
doesn't seem to be working currently.

Not sure if that's something I've broken, or if it never worked properly 
:( .

> The actual vaulting will not happen if there's another package still
> requiring it as a dependency.  You'd have to drop in a newer package
> satisfying the same dependency first and/or update all other packages to
> not depend on the old version anymore.  I don't know how circular
> dependencies among packages marked for vaulting are handled (at all or
> in this particular case).That secnario should be handled correctly if all the vaultings are 
requested simultaneously.