Bug#1064950: AW: AW: Bug#1064950: apache2: (Legacy?) "Depends: apache2-data (= ${source:Version})," in debian/control breaks binNMU builds.

Sebastian Ramacher wrote: > Christof Warlich wrote: > > If this assumption is true, then why is the Debian build system (i.e. > > dpkg-buildpackage) not smart enough to simply ignore an existing +bX > > extension for Architecture: all binary packages? IMHO, this would simplify > > matters, as

Bug#1064950: AW: Bug#1064950: apache2: (Legacy?) "Depends: apache2-data (= ${source:Version})," in debian/control breaks binNMU builds.

Sebastian Ramacher wrote: > This is wrong. apache2-data is an Architecture: all package, > but apache2 is Architecture: any. So using ${source:Version} > here is correct. Note that Debian does not currently support > binNMUs for Architecture: all packages, so apache2-data will > never have a +bX

Bug#1064950: apache2: (Legacy?) "Depends: apache2-data (= ${source:Version})," in debian/control breaks binNMU builds.

Subject: apache2: (Legacy?) "Depends: apache2-data (= ${source:Version})," in debian/control breaks binNMU builds. Source: apache2 X-Debbugs-Cc: christof.warl...@siemens.com Version: 2.4.57-2 Severity: serious Justification: fails to build from source (but built successfully in the past) Tags:

Rebuilding apache2 Package as binNMU.

I've rebuilt apache2 as a binNMU, i.e. without patching the package itself, but only changing its build environment. Thus, I appended the string "+b1" to its version as described in https://wiki.debian.org/binNMU All resulting packages compile without any problem, but when I try to install