Detecting Package Transitions
Larger transitions in Debian are usually announced on e.g. debian-devel, but it’s harder to track the current status of all transitions. Having done a lot of QA uploads recently, I have on occasion uploaded packages involved in a transition. This can be unhelpful for the people handling the transition, but there’s also often not much point in uploading if your uploads are going to get stuck.
Talking to one of the release managers at a recent BSP, it was great to find out that the release team actually publish a data dump with which packages are involved in which transitions.
Here’s the script I use to find out about the transitions the package in my current working directory is involved in:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 | #!/usr/bin/python3 from urllib.request import urlopen import sys from debian.deb822 import Deb822 import yaml with open('debian/control', 'r') as f: package = Deb822(f)['Source'] with urlopen("https://release.debian.org/transitions/export/packages.yaml") as f: data = yaml.safe_load(f) def find_transitions(data, package): for entry in data: if entry['name'] != package: continue return dict(entry['list']) return {} transitions = find_transitions(data, package) print(transitions) sys.exit(1 if 'ongoing' in transitions.values() else 0) |
In practice, the output looks something like this:
$ debcheckout bctoolbox
git clone https://salsa.debian.org/pkg-voip-team/linphone-stack/bctoolbox.git bctoolbox ...
Cloning into 'bctoolbox'...
...
$ cd bctoolbox
$ in-transition.py
{'auto-upperlimit-libbctoolbox1': 'ongoing'}
