Control: forcemerge -1 1076939 Hi!
On Wed, 2024-07-24 at 12:17:21 +0200, Santiago Vila wrote: > Package: dpkg > Version: 1.22.8 > While building some packages I get weird errors like this: > > dpkg-deb: building package 'aspell-nl' in '../aspell-nl_2.20.19-2_all.deb'. > dpkg-deb: building package 'idutch' in '../idutch_2.20.19-2_all.deb'. > dpkg-deb: error: parsing file 'debian/hunspell-nl/DEBIAN/control' near line 3 > package 'hunspell-nl': > 'Version' field value '2:': nothing after colon in version number > dh_builddeb: error: dpkg-deb --build debian/hunspell-nl .. returned exit code > 2 > > (the above is for package "dutch") > > This seems more a dpkg bug (maybe related with epoch handling) than a bug in > dutch, > but I'm not sure. Can you check? > On Wed, 2024-07-24 at 14:10:48 +0200, Jonas Smedegaard wrote: > Package: dpkg-dev > Version: 1.22.8 > Severity: important > It looks like recent changes to dpkg-dev affects a bunch of packages > that I maintain. > > Concretely, the package radicale now fails to build, as it passes an > empty version number to help2man. This was reported as bug#1076915. > Seemingly related bug#1076568 made me try downgrade dpkg-dev, and > indeed with dpkg-dev 1.22.6 the variable DEB_VERSION_UPSTREAM_REVISION > again resolves correctly. > > It looks like recent dpkg-dev offers variable expansion only inside > make rules, not for make code declares "at the core", outside of make > rules. > > Many of the packages I maintain rely on the ability to resolve variables > also at the core of the makefile. I am not furiously against changing my > packaging patterns, but I imagine I am not the only one, so I guess such > change needs more care and documentation (or perhaps just pointing me to > the elaborate documentation that I have totally missed). Both look like the same problem, which would be a regression from the recent rework of the Makefile fragments. I'm CCing Nicolas as a heads-up, and I'm looking into this to try to do a quick fix upload. Thanks, Guillem
