Your message dated Wed, 27 Jan 2021 09:34:23 +0000
with message-id <[email protected]>
and subject line Bug#978462: fixed in libevtx 20181227-2
has caused the Debian Bug report #978462,
regarding libevtx: memory tests fundamentally broken, please disable them on 
riscv64
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
978462: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978462
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: libevtx
Version: 20181227-1.1
Severity: normal
Tags: ftbfs patch upstream
User: [email protected]
Usertags: riscv64

Hi,

libevtx fails to build on riscv64:
https://buildd.debian.org/status/fetch.php?pkg=libevtx&arch=riscv64&ver=20181227-1.1&stamp=1584612286&raw=0

This is due to fundamentally broken tests assuming that memcpy and
memset can fail returning NULL, and interposing these libc functions in
the tests with functions that sometimes return NULL. This tests should
be simply removed as they do not make sense. See bug #978433 for more
details as the same code is basically replicated in dozen of packages.

A simpler way to fix the issue for riscv64 is to disable all memory
tests on this architecture, as it is already done for a long list of
cases. This is what the patch below does:

--- libevtx-20181227/debian/patches/01-disable-memory-tests-on-riscv64.patch    
1970-01-01 01:00:00.000000000 +0100
+++ libevtx-20181227/debian/patches/01-disable-memory-tests-on-riscv64.patch    
2020-12-27 14:36:09.000000000 +0100
@@ -0,0 +1,11 @@
+--- libevtx-20181227.orig/tests/evtx_test_memory.h
++++ libevtx-20181227/tests/evtx_test_memory.h
+@@ -28,7 +28,7 @@
+ extern "C" {
+ #endif
+ 
+-#if defined( HAVE_GNU_DL_DLSYM ) && defined( __GNUC__ ) && !defined( 
LIBEVTX_DLL_IMPORT ) && !defined( __arm__ ) && !defined( __clang__ ) && 
!defined( __CYGWIN__ ) && !defined( __hppa__ ) && !defined( __mips__ ) && 
!defined( __sparc__ ) && !defined( HAVE_ASAN )
++#if defined( HAVE_GNU_DL_DLSYM ) && defined( __GNUC__ ) && !defined( 
LIBEVTX_DLL_IMPORT ) && !defined( __arm__ ) && !defined( __clang__ ) && 
!defined( __CYGWIN__ ) && !defined( __hppa__ ) && !defined( __mips__ ) && 
!defined( __sparc__ ) && !defined( __riscv ) && !defined( HAVE_ASAN )
+ #define HAVE_EVTX_TEST_MEMORY         1
+ #endif
+ 
--- libevtx-20181227/debian/patches/series      1970-01-01 01:00:00.000000000 
+0100
+++ libevtx-20181227/debian/patches/series      2020-12-27 14:36:09.000000000 
+0100
@@ -0,0 +1 @@
+01-disable-memory-tests-on-riscv64.patch

Regards,
Aurelien

--- End Message ---
--- Begin Message ---
Source: libevtx
Source-Version: 20181227-2
Done: Sebastien Delafond <[email protected]>

We believe that the bug you reported is fixed in the latest version of
libevtx, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastien Delafond <[email protected]> (supplier of updated libevtx package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 27 Jan 2021 09:59:40 +0100
Source: libevtx
Architecture: source
Version: 20181227-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools <[email protected]>
Changed-By: Sebastien Delafond <[email protected]>
Closes: 978462
Changes:
 libevtx (20181227-2) unstable; urgency=medium
 .
   [ Jelmer Vernooij ]
   * Use secure copyright file specification URI. Fixed-Lintian-Tags: 
insecure-copyright-format-uri
 .
   [ Samuel Henrique ]
   * Configure git-buildpackage for Debian
 .
   [ Debian Janitor ]
   * Set debhelper-compat version in Build-Depends.
   * Set upstream metadata fields: Bug-Database, Bug-Submit.
   * Update standards version to 4.5.0, no changes needed.
   * Remove Section on libevtx1 that duplicates source.
   * Apply multi-arch hints. + python3-libevtx: Add Multi-Arch: same.
   * Update watch file format version to 4.
   * Use cross-build compatible macro for finding pkg-config.
 .
   [ Sébastien Delafond ]
   * Disable memory tests on riscv-64 (Closes: #978462)
Checksums-Sha1:
 2c30558d23d34056b5affe7ee9c3cc76d469d66b 1814 libevtx_20181227-2.dsc
 8e5ab842d451455ce1ad9580245ed87d89167764 4708 libevtx_20181227-2.debian.tar.xz
 2b6d78fad54af9d8b380ee0b05c78c6e51e0a2c6 8218 
libevtx_20181227-2_amd64.buildinfo
Checksums-Sha256:
 af4c78d970e6b6355f54439e1b65b03f3b42b23d33ad9ec69d32abb270312024 1814 
libevtx_20181227-2.dsc
 6464bff497ac779db472397b3f2e8aa7344c2054b5e8583b48f5d46862c7307a 4708 
libevtx_20181227-2.debian.tar.xz
 f7ee85ad3615472c5a12322691a82a3137c885c9b7749c7c88dcefa4df05f778 8218 
libevtx_20181227-2_amd64.buildinfo
Files:
 7eed8e4050ad64b8949eeb4b7fcd1cb5 1814 libs optional libevtx_20181227-2.dsc
 6829284317617adf028ad449dd3e1006 4708 libs optional 
libevtx_20181227-2.debian.tar.xz
 abf4f33b93202ad6d430cfdb0f0a5a7d 8218 libs optional 
libevtx_20181227-2_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEAqSkbVtrXP4xJMh3EL6Jg/PVnWQFAmARLjQACgkQEL6Jg/PV
nWRggggAvpPyHpvMpO7llq6MS7AH2Eoryy+aZEJ6SO2/c2vDFMa5iGody3pTcG/+
pmsAHDYPJ0Qpm1fSgz7tSxcWAnbvzhv90Ej83PYmSl53/RrkbdxSykngPXTH5zLM
yX6l4OXUTz/8fDH8kfLD1D7T8QMx16d1VgaCz2NGHfQYTr0djgbCIT2ds9l+kT04
e6d1og7LqGzlIYEvQBYwt7hFNrnHWoMUG56IbC9pbvqqeASJA2akkFxKex5zB3Pz
I+DcLdj34NunuHfYMbZktCR9Dsi2FXclcIMi26zLmo9szIv9Vi7OoKkY7rPdAmZh
EsNXA6w+9EDm/xww3eC1FFebhz0plQ==
=OSTp
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to