Fix possible generation of empty Build-Depends profile restriction

While implementing some non-upstreamable changes to the packaging to disable building some packages, I have managed to generated a control with Build-Depends-Arch: libtraceevent-dev (>= 1:1.5) [...] <>. This then broke the build because dpkg-source could not parse the field.

Check that the restriction list is not empty when printing the angle brackets to avoid generating this invalid restriction formula.


Here's the bad changes: hacks.patch. I had done these because mostly I want to build just the main flavour image for testing on actual hardware, and I keep forgetting to build with the profiles I want to exclude non-image stuff. Anyway, not very important, but the fix looks OK in general so wanted to let you know.

Merge request reports

Loading