Your message dated Sun, 28 Jun 2026 16:38:38 +0200 with message-id <[email protected]> and subject line Re: [Pkg-clamav-devel] Bug#1120998: clamscan: thread '<unnamed>' panicked while scanning a TIFF file has caused the Debian Bug report #1120998, regarding clamscan: thread '<unnamed>' panicked while scanning a TIFF file 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.) -- 1120998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1120998 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: clamav Version: 1.4.3+dfsg-1 Scanning https://github.com/holoviz/datashader/raw/refs/heads/main/datashader/tests/data/world.rgb.tif (sha256: a89c9376a0023c7b76af4df5000639d0e32d976c4f9d8750b1825ed3fac2eb7b) with clamscan reproducibly results in the following warning: thread '<unnamed>' panicked at /build/reproducible-path/clamav-1.4.3+dfsg/.cargo/vendor/image/src/codecs/tiff.rs:269:21: copy_from_slice: source slice length (131072) does not match destination slice length (393216) clamscan then declares the file to be OK and continues normally.
--- End Message ---
--- Begin Message ---Version: 1.4.4+dfsg-1 On 2025-11-19 11:19:21 [+0000], Sergio Gelato wrote: > Scanning > https://github.com/holoviz/datashader/raw/refs/heads/main/datashader/tests/data/world.rgb.tif > (sha256: > a89c9376a0023c7b76af4df5000639d0e32d976c4f9d8750b1825ed3fac2eb7b) with > clamscan reproducibly results in the following warning: > > thread '<unnamed>' panicked at > /build/reproducible-path/clamav-1.4.3+dfsg/.cargo/vendor/image/src/codecs/tiff.rs:269:21: > copy_from_slice: source slice length (131072) does not match destination > slice length (393216) > > clamscan then declares the file to be OK and continues normally. Fixed in 1.4.4. Sebastian
--- End Message ---
