[Pkg-shadow-devel] Bug#836653: shadow: please drop the build dependency on hardening-wrapper
Serge E. Hallyn
serge at hallyn.com
Thu Sep 8 17:43:48 UTC 2016
Quoting Mattia Rizzolo (mattia at debian.org):
> On Sun, Sep 04, 2016 at 01:16:54PM +0000, Matthias Klose wrote:
> > This package builds using the hardening-wrapper package, which
> > is now replaced by dpkg-dev's DEB_BUILD_MAINT_OPTIONS settings.
> > Please consider dropping the build dependency of hardening-wrapper
> > and use the DEB_BUILD_MAINT_OPTIONS settings.
> This is particularly annoying for shadow, as it is part of the essential
> set, and it is currently not buildable (hardening-wrapper can't atm be
> coinstalled with current binutils), breaking a set of QA jobs that
> builds the essential set, and messing with statistics.
> I don't think shadow really need hardening-wrapper at all. The build
> system is a regular autoconf/autotools which respects CFLAGS.
> The compat level is 6, so dh_auto_* won't export them, but you could
> instead set DPKG_EXPORT_BUILDFLAGS and include
> /usr/share/dpkg/buildflags.mk to get them (you need to do so *after* the
> already presetn 'export DEB_BUILD_MAINT_OPTIONS = hardening=+all').
> BTW, Serge: you have staged a bunch of stuff in git already, can we have
> them uploaded? If you lack a reactive sponsor feel free to email me (or
> contact me over IRC).
actually I think everyone was ok with what is staged now, the only
problem is that some extra changes got rolled in which need to be
undone or deal twith (debuild -b complains about upstream changes
mainly to tranlsations). I've simply not had the time to fix it.
If you have time, that would be great, else yes when I have time (and
network bandwidth - not until next week) to do it I'll need a sponsor,
> Otherwise, as people are grumpy for this bug, can I NMU it? (I'd post a
> proposed patch here, of course, etc).
Sure, I have no objection NMU.
More information about the Pkg-shadow-devel