Allow repack VO to be modified if there is no previous repack VO defined
As decided before, it should not be possible to modify the default repack VO if there are any ongoing repacks being processed.
However, there should be an exception:
- When no repack VO is defined, we should be able to set a new repack VO.
A possible solution is to allow the modification of the repack VO to proceed here if --isrepackvo true:
Adding a default repack VO is fine. We should only fail when we are trying to remove a repack VO (--isrepackvo false) while there are ongoing repacks.
Adding a default repack VO when there is another repack VO already defined is also fine, because this will already be thrown back to the user:
throw exception::UserError("There already exists a default VO for repacking");This needs to be fixed before the next code public release.
For more details, check: