Hi! On Fri, 2017-08-18 at 23:09:08 +0200, Adam Borowski wrote: > Package: dpkg-dev > Version: 1.18.24 > Severity: wishlist
> Stretch's versions of all apt frontends other than cupt already support > "Important: yes" packages, thus it'd be reasonable to allow them in Buster. We are actually not very happy with the name and were already thinking about using something else. We've also written down our thoughts on the matter, as there are still some undecided/undesirable semantics: <https://wiki.debian.org/Teams/Dpkg/Spec/ImportantField> but as we were on the freeze didn't bring it into a wider audience. We'll be probably doing that in the coming days. > However, dpkg-gencontrol currently fails to copy the field into a generated > package. If I post-process it with a hack like: > .---- > override_dh_gencontrol: > dh_gencontrol > sed -e '2i Important: yes' -i debian/${PACKAGE}/DEBIAN/control > `---- > all is ok. Just for reference, the proper way to tell dpkg-gencontrol how to export unknown fields into various outputs is to use the export markers such as SBC as in «XB-Important: yes», as described in deb-src-control(5). > It is not documented in the Policy, I've filed #872587 asking for their > opinion. I don't think it makes sense to file this kind of bug on policy as long as there's no support in dpkg, nor a clear plan yet on how to proceed. :) Thanks, Guillem
