Control: reopen -1 Control: reassign -1 libgcc-s1 On Sun, 2024-07-28 at 15:30:09 +0000, Debian Bug Tracking System wrote: > Version: 9.5.0-6+rm > > Dear submitter, > > as the package gcc-9 has just been removed from the Debian archive > unstable we hereby close the associated bug reports. We are sorry > that we couldn't deal with your issue properly. > > For details on the removal, please see https://bugs.debian.org/1076502
Bug still relevant, reopening and reassigning. Keeping the original bug report below for context. > Date: Wed, 15 Jan 2014 20:49:30 +0100 > From: Guillem Jover <guil...@debian.org> > To: sub...@bugs.debian.org > Subject: libgcc1: Can switch to use new Ignore-Blacklist-Groups for aeabi > symbols > Message-ID: <20140115194930.ga25...@gaara.hadrons.org> > User-Agent: Mutt/1.5.21 (2010-09-15) > X-Spam-Status: No, score=-12.0 required=4.0 tests=BAYES_00,FROMDEVELOPER, > HAS_PACKAGE,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham > version=3.3.2-bugs.debian.org_2005_01_02 > > Package: libgcc1 > Version: 1:4.8.2-13 > Severity: wishlist > > With dpkg-dev 1.17.6, there's a new symbols file field named > Ignore-Blacklist-Groups that can be used by the toolchain packages to > ignore the entire blacklist group for the aeabi symbols, which are now > blacklisted by regex instead of by an explicit list. This means that > dpkg-dev will automatically blacklist new introduced symbols w/o > having them leak into other package symbol files or having them FTBFS, > and needing to add them manually to dpkg-dev and libgcc1.symbols.aeabi. > > But to make gcc unconditionally include unknown aeabi symbols the > ignore-blacklist tag is not enough, instead the new field can be used > which disables the entire regex for that group. Adding something like: > > ,--- > * Ignore-Blacklist-Groups: aeabi > `--- > > at the top of libgcc1.symbols.aeabi should do the trick. You can then > remove the ignore-blacklist tag if you want, or I guess you could keep > it to avoid having to Build-Depend on a newer dpkg-dev. Thanks, Guillem
