Bug#954393: please Breaks: libc6-dev-${DEB_HOST_ARCH}-cross (<< ${CURRENT_UPSTREAM_VERSION})

2020-03-23 Thread Aurelien Jarno 
On 2020-03-21 07:34, Helmut Grohne wrote:
> Package: libc6-dev
> Version: 2.30-2
> Severity: wishlist
> 
> Every time a new glibc upstream release gets uploaded,
> cross-toolchain-base breaks in difficult to diagnose ways. This seems to
> happen, because gcc uses the libc6-dev:somearch headers together with
> libc6-dev-somearch-cross libraries.
> 
> Would you agree to have libc6-dev declare
> 
> Breaks: libc6-dev-${DEB_HOST_ARCH}-cross (<< ${CURRENT_UPSTREAM_VERSION}~)
> 

On the principle yes. Now I have to find a way to do it in a not too
ugly way, as ${DEB_HOST_ARCH} is not something supported by dpkg-dev. I
guess it probably means writing directly to substvars.

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#954393: please Breaks: libc6-dev-${DEB_HOST_ARCH}-cross (<< ${CURRENT_UPSTREAM_VERSION})

2020-03-21 Thread Helmut Grohne 
Package: libc6-dev
Version: 2.30-2
Severity: wishlist

Every time a new glibc upstream release gets uploaded,
cross-toolchain-base breaks in difficult to diagnose ways. This seems to
happen, because gcc uses the libc6-dev:somearch headers together with
libc6-dev-somearch-cross libraries.

Would you agree to have libc6-dev declare

Breaks: libc6-dev-${DEB_HOST_ARCH}-cross (<< ${CURRENT_UPSTREAM_VERSION}~)

where CURRENT_UPSTREAM_VERSION would presently be 2.30? I think that'd
spare us from diagnosing these issues in general.

Helmut