Delete requests can wrongly end up in adi stagings
We just had a case of a delete request ending up in an adi staging instead of a letter staging. We managed to reproduce what happens.
- PKG A has a regular submit request which has been added to an adi staging (as per regular workflow)
- PKG A receives a delete request
osc staging list --supersede will 'see' the 2nd submission to be against the same package and have it 'take its place' in the current staging project - the adi project