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

To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: Bug#954393: please Breaks: libc6-dev-${DEB_HOST_ARCH}-cross (<< ${CURRENT_UPSTREAM_VERSION})
From: Helmut Grohne <helmut@subdivi.de>
Date: Sat, 21 Mar 2020 07:34:24 +0100
Message-id: <[🔎] 20200321063424.GA4821@alf.mars>
Reply-to: Helmut Grohne <helmut@subdivi.de>, 954393@bugs.debian.org

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

Reply to:

Follow-Ups:
- Bug#954393: please Breaks: libc6-dev-${DEB_HOST_ARCH}-cross (<< ${CURRENT_UPSTREAM_VERSION})
  - From: Aurelien Jarno <aurelien@aurel32.net>
- Processed: Bug#954393 marked as pending in glibc
  - From: "Debian Bug Tracking System" <owner@bugs.debian.org>
- Bug#954393: marked as done (please Breaks: libc6-dev-${DEB_HOST_ARCH}-cross (<< ${CURRENT_UPSTREAM_VERSION}))
  - From: "Debian Bug Tracking System" <owner@bugs.debian.org>

Prev by Date: Bug#954392: libc6-dev-armhf-cross is incompatible with current libc6-dev:armhf
Next by Date: Bug#954374: libc6: please make maintainerscript compatible with busybox
Previous by thread: Bug#954392: marked as done (libc6-dev-armhf-cross is incompatible with current libc6-dev:armhf)
Next by thread: Bug#954393: please Breaks: libc6-dev-${DEB_HOST_ARCH}-cross (<< ${CURRENT_UPSTREAM_VERSION})
Index(es):
- Date
- Thread