Source: libgc Version: 1:8.2.2-1 Severity: serious Tags: ftbfs Hi,
what happend to libgc? It ftbfs on all 32bit architectures and its symbol handling is essentially stripped of all the architecture-specific patterns that we have accumulated over the years. The general quality of the upload seems questionable as well: * A possibly breaking change for a core package is often done to experimental first to reduce disruption of development on unstable. Doing so would have prevented major pain here. * The debian/changelog entry contains duplicates. * Lots of symbols were dropped from the symbols file without bumping soname. Possibly, this may lead to incorrect dependencies on libgc in downstream builds. * debian/changelog says that you removed libatomic_ops handling, but for every new architecture libatomic_ops is still opted in leading to unnecessary porting work even though built-in atomics generally work well. I am also wondering whether this actually is a package hijack as there is no visible acknowledgement from any existing maintainers to adding Ian to uploaders. I am quite disappointed by this upload and the downstream pain it causes to QA. Helmut
