Re: Sebastiaan Couwenberg > No, we explicitly added the templating bits to support this use case.
Iirc the reason it was copied from pgxs_debian_control.mk to support "NEWEST_PGVERSION". > > Calling clean was already triggering the control generation: > > > > override_dh_auto_clean: debian/control > > While that also changed d/control outside the chroot, it didn't call > `pg_buildext checkcontrol` which fails due to those changes. That part is necessary to make builds fail if control would change. It doesn't matter if the change is triggered from clean/configure/build. > AFAIK only the clean target is suitable, as configure shouldn't modify > d/control. Every package that generates d/control has that file a > dependency of the clean target. > > Making `pg_buildext checkcontrol` optional may be a solution for stable > systems. If the spurious change on stable is not a problem, and you just want the build not to fail, you can set PG_UPDATECONTROL=yes. Christoph _______________________________________________ Pkg-grass-devel mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-grass-devel
