[wishlist] unembargo into arbitrary pockets

[Kees Cook]

When unembargoing security P3A packages, it would be nice to be able to specify the pocket. In certain situations (major version upgrades, etc) it is nice to be able to publish into -proposed before pocket-copying fully into -security. (The reason to build in the P3A is to avoid building against things in -updates, which happens if you upload directly to -proposed.)

As I understand it, this requires changing the hard-coded "-security" that is appended in the tool and allowing the caller to define which pocket to use.

[Julian Edwards (julian-edwards)]

Fixed in RF 7282.

unembargo-package.py now treats the -s arg as a suite name, so you need to specify -s intrepid-security, for example. If you mistakenly specify the release pocket it will print an error and fail.