Source: python-greenlet Version: 2.0.2-1 Severity: normal Tags: patch Hi!
I initially found this doing a rebuild in a derived distro, then debugged and worked out what's happening. The build-time tests may generate a core file, depending on the build environment. If that happens, the core file in included in the .deb output which is clearly not useful. It's just luck that the Debian buildds (etc.) don't run "ulimit -c unlimited" or similar to have triggered this already. Have an obvious patch to fix this... :-) -- System Information: Debian Release: 11.7 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'oldoldstable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-23-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
diff --git a/debian/rules b/debian/rules index 0a03f62..9be930e 100755 --- a/debian/rules +++ b/debian/rules @@ -25,6 +25,7 @@ override_dh_auto_install: mv $(CURDIR)/debian/tmp/usr/include/python3.7/ \ $(CURDIR)/debian/tmp/usr/include/python3.7m/ ; \ fi + find $(CURDIR)/debian/tmp/ -name core -type f -delete override_dh_auto_test: ifeq (,$(findstring nocheck,$(DEB_BUILD_OPTIONS)))