Hi, I’ve noticed that most of our packages both depend on dh-octave and dh- sequence-octave (with a version constraint for the former). When the version constraint on dh-octave corresponds to an old version (i.e. is satisfied in stable, or even in oldstable), then the whole build dependency on dh-octave is unnecessary and can be dropped. I’ve done that in octave-io and everything seems to work correctly. Also note that the dh_octave_make script systematically adds such a versioned build dependency, which looks superfluous to me. So is there any other reason to keep those build-dependencies on dh- octave, that I may be missing? By the way, I’ve also started to remove “Rules-Requires-Root: no” in my latest uploads, since that value is now the default (since dpkg-dev 1.22.13). Best, -- ⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot ⣾⠁⢠⠒⠀⣿⡁ Debian Developer ⢿⡄⠘⠷⠚⠋⠀ https://sebastien.villemot.name ⠈⠳⣄⠀⠀⠀⠀ https://www.debian.org
Attachment:
signature.asc
Description: This is a digitally signed message part