Bug#1060104: dcmtk: FTBFS on armel: Error: bad immediate value for offset (4100)

On Tue, Mar 19, 2024 at 8:44 AM Emanuele Rocca wrote: > > Hi, > > On 2024-03-19 06:24, Sébastien Jodogne wrote: > > Because of bug #1060104, a large majority of the packages related to > > medical imaging have just disappeared from Debian Unstable. > > > > But, if I correctly understand #1060104,

Bug#1060704: transition: dcmtk

Sebastian, On Sun, Jan 21, 2024 at 4:55 PM Sebastian Ramacher wrote: > > Control: tags -1 moreinfo > > Hi Mathieu > > On 2024-01-13 11:47:40 +0100, Mathieu Malaterre wrote: > > Package: release.debian.org > > Severity: normal > > User: release.debian.

Bug#1062022: dcmtk: NMU diff for 64-bit time_t transition

Hi, On Wed, Jan 31, 2024 at 1:09 AM wrote: > If you have any concerns about this patch, please reach out ASAP. Although > this package will be uploaded to experimental immediately, there will be a Are you going to nuke my work on dcmtk 3.6.8 transition ?

Bug#1060104: dcmtk: FTBFS on armel: Error: bad immediate value for offset (4100)

Control: severity -1 important On Mon, Jan 15, 2024 at 1:49 PM Emanuele Rocca wrote: [...] > For this reason I would > suggest to disable stackclash on the armel build of dcmtk (just like you > did in experimental) to make sure the package builds properly again, but > keep #1060104 open at a

Bug#1060104: dcmtk: FTBFS on armel: Error: bad immediate value for offset (4100)

Control: fixed -1 3.6.8-3 On Sat, Jan 13, 2024 at 9:42 PM Emanuele Rocca wrote: > > Control: user -1 debian-...@lists.debian.org > Control: usertag -1 + 32bit-stackclash > > Hi, > > On Fri, Jan 05, 2024 at 11:45:28PM +0100, Sebastian Ramacher wrote: > > /tmp/ccm0eYhx.s: Assembler messages: > >

Bug#1053866: transition: jpeg-xl

On Tue, Oct 17, 2023 at 6:04 PM Sebastian Ramacher wrote: > > Hi Mathieu > > On 2023-10-13 16:42:34 +0200, Mathieu Malaterre wrote: > > On Fri, Oct 13, 2023 at 11:57 AM Sebastian Ramacher > > wrote: > > > > > > Control: tags -1 moreinf

Bug#1060704: transition: dcmtk

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition I'd like to migrate to dcmtk 3.6.8. This is a standard SONAME transition. Current status in exp: https://buildd.debian.org/status/package.php?p=dcmtk=experimental Thanks

Bug#1060677: Acknowledgement (Rounding error in OFStandard::atof)

forwarded -1 https://support.dcmtk.org/redmine/issues/1100

Bug#1060677: Rounding error in OFStandard::atof

Source: dcmtk Version: 3.6.7-8+b1 I believe I found an edge case in OFStandard::atof logic. Consider the following ASCII string float > 16 bytes (valid case for input such as XML or JSON). Here is what I see on my side Debian/stable (dcmtk 3.6.7): $ ./fd 0x1.dp+3

Bug#1060442: DCMTK Release 3.6.8 available

Source: dcmtk Dear DCMTK Package Maintainer, we noticed that you are one the package maintainers helping to distribute a DCMTK package for some Linux distribution, BSD unix or other package management system. We want to inform you that there is a a new DCMTK release 3.6.8 available. You can

Bug#1056048: Acknowledgement (Memory leak in dcm2json)

As pointed out by upstream, one must export the following: You should set the environment variable ICONV_MAX_REUSE to zero before running such tests: export ICONV_MAX_REUSE=0 valgrind --leak-check=full ... Which gives now the reduced set of leaks: % valgrind --leak-check=full

Bug#1056302: FreeBSD/iconv: ISO 2022 IR 13\ISO 2022 IR 87

Source: dcmtk Version: 3.6.8~git20231027.1549d8c-2 Somewhat related to #988644. Steps: % curl -O https://dclunie.com/images/charset/charsettests.20070405.tar.bz2 % tar xf charsettests.20070405.tar.bz2 % cp charsettests/SCSH32 new.dcm % dcmodify -i "0018,1020=123\456" new.dcm Gives % dcmdump

Bug#1056048: Memory leak in dcm2json

Source: dcmtk Version: 3.6.8~git20231027.1549d8c-2 Looks like there is a memory leak using the new citrus/oficonv lib: curl -O https://dclunie.com/images/charset/charsettests.20070405.tar.bz2 tar xf charsettests.20070405.tar.bz2 valgrind --leak-check=full --show-leak-kinds=all dcm2json

Bug#1055873: Acknowledgement (dcm2json is missing --convert-un for CP-1066 EVRLE)

Current work-around: % dcmconv +ti RTStruct_VRDSAsVRUN.dcm - | dcm2json - output.json

Bug#1055872: Acknowledgement (CP-2275: "NaN", "+Infinity" and "-Infinity")

Control: forwarded -1 https://support.dcmtk.org/redmine/issues/1086 Confirmed by upstream. On Mon, Nov 13, 2023 at 11:51 AM Debian Bug Tracking System wrote: > > Thank you for filing a new Bug report with Debian. > > You can follow progress on this Bug here: 1055872: >

Bug#1055873: dcm2json is missing --convert-un for CP-1066 EVRLE

Source: dcmtk Version: 3.6.7-9 In some cases, DICOM enforces the serialization of VR:UN instead of the actual correct Value Representation. dcm2json does not permit on the fly conversion to correct VR and hence generates VR:UN with InlineBinary.

Bug#1055872: CP-2275: "NaN", "+Infinity" and "-Infinity"

Source: dcmtk Version: 3.6.7-9 DICOM standard is about to clarify support for "NaN", "+Infinity" and "-Infinity" in DICOM/JSON. Currently dcm2json does not support it. It has been discussed with upstream.

Bug#1055490: Subscription to 1055...@bugs.debian.org successful

Control: fixed -1 3.6-25 Control: tags -1 wontfix PEBKAC % echo -n 'ＡＢＣ' > t.txt % recode -v UTF-8..JIS_X0208 t.txt Request: UTF-8..:libiconv:..JIS_X0208 Shrunk to: UTF-8..JIS_X0208 Recoding t.txt... done % recode -v JIS_X0208..UTF-8 t.txt Request: JIS_X0208..:libiconv:..UTF-8 Shrunk to:

Bug#1055490: Acknowledgement (ISO-IR-87 encoding seems to be broken)

For ref: % recode -l | grep IR-87 JIS_X0208 csISO87JISX0208 ISO-IR-87 JIS0208 JISX0208.1983-0 JISX0208.1990-0 JIS_X0208-1983 JIS_X0208-1990 X0208

Bug#1055490: ISO-IR-87 encoding seems to be broken

Package: recode Version: 3.6-25 For some reason I cannot get ISO-IR-87 to work on my Debian/stable system: % echo 'foobar' > t.txt % recode -v UTF-8..ISO-IR-87 t.txt Request: UTF-8..:libiconv:..JIS_X0208 Shrunk to: UTF-8..JIS_X0208 Recoding t.txt... failed: Invalid input in step

Bug#409283: recode: man page author name does not seams well coded.

> In man page author name is > Franc,ois > when, in an UTF-8 system (default in etch), it should be > François Quite funny when you realize that `recode` is exactly about encoding :)

Bug#1055276: Acknowledgement (Valgrind does not read properly DWARF5 as generated by Clang14)

Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=452758 Control: tags -1 upstream fixed-upstream Control: affects -1 clang-16 Seems to be fixed in 3.20

Bug#1055276: Valgrind does not read properly DWARF5 as generated by Clang14

Source: valgrind Version: 1:3.19.0-1 valgrind does not handle clang 14 and up. % valgrind ./works2 ==171243== Memcheck, a memory error detector ==171243== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al. ==171243== Using Valgrind-3.19.0 and LibVEX; rerun with -h for copyright info

Bug#1054149: manpages-dev: Bizarre rendering of pointers (restrict .n)

Package: manpages-dev Version: 6.03-2 Severity: normal Dear Maintainer, Consider the following: `man 3 memcpy` You'll be presented with the following signature: <...> SYNOPSIS #include void *memcpy(void dest[restrict .n], const void src[restrict .n], size_t

Bug#1053866: transition: jpeg-xl

On Fri, Oct 13, 2023 at 11:57 AM Sebastian Ramacher wrote: > > Control: tags -1 moreinfo > Control: forwarded -1 > https://release.debian.org/transitions/html/auto-jpeg-xl.html > > On 2023-10-13 10:44:31 +0200, Mathieu Malaterre wrote: > > Package: release.debian.

Bug#1053866: transition: jpeg-xl

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: transition This is a minor SONAME transiton. Two (unused anywhere) symbols were removed. Current status in exp: https://buildd.debian.org/status/package.php?p=jpeg-xl=experimental Thanks Ben

Bug#1051905: jpeg-xl: Please add support for Loongarch

Control: fixed -1 0.7.0-10.2 I see that it builds fine on loong64: https://buildd.debian.org/status/fetch.php?pkg=jpeg-xl=loong64=0.7.0-10.2=1696728916=0 Closing. Thanks

Bug#1053753: libpng1.6 shlibs contains debian revision

Source: libpng1.6 Version: 1.6.40-1 Just like symbols file (symbols-file-contains-current-version-with-debian-revision), shlibs should not contain debian revision, please remove it. For reference: % cat libpng16-16.shlibs libpng16 16 libpng16-16 (>= 1.6.2-1) udeb: libpng16 16 libpng16-16-udeb

Bug#1053641: transition: libavif

Hi, On Sat, Oct 7, 2023 at 9:36 PM Boyuan Yang wrote: > > X-Debbugs-CC: ma...@debian.org > > 在 2023-10-07星期六的 20:32 +0200，Sebastian Ramacher写道： > > Control: tags -1 confirmed > > > > On 2023-10-07 14:06:44 -0400, Boyuan Yang wrote: > > > I am looking at starting the transition for package

Bug#1050933:

Control: tags -1 wontfix GCC-13 works as expected. Turns out to be a UB case in highway source code. Closing

Bug#1052677: Fixed in 1.0.7-1

Version: 1.0.7-1 > Looks like this was already fixed in 1.0.7-1 a couple of weeks ago. I > updated and the problem went away. Sorry for the dupe. Sorry for the mess. Just for reference, this is also fixed on 1.0.3-3+deb12u1

Bug#1051384: bookworm-pu: package highway/1.0.3-3

On Thu, Sep 7, 2023 at 1:23 PM Adam D. Barratt wrote: > > Control: tags -1 + moreinfo > > On Thu, 2023-09-07 at 09:11 +0200, Mathieu Malaterre wrote: > > I'd like to fix highway on armhf (neon-less) system. > > > > [ Reason ] > > See #1033656 > > > &

Bug#1033656: closed by Debian FTP Masters (reply to Mathieu Malaterre ) (Bug#1033656: fixed in highway 1.0.7-1)

gt; > > > #1033656: illegal hardware instruction cjxl > > > > It has been closed by Debian FTP Masters > > (reply to Mathieu Malaterre ). > > > > Their explanation is attached below along with your original report. > > If this explanation is unsatis

Bug#1052141: Simplified

Steps: % clang++-16 -o fails math_test4.cc -lhwy_contrib % cat math_test4.cc int main() {} % clang++-16 -o fails math_test4.cc -lhwy_contrib % valgrind ./fails ==3733364== Memcheck, a memory error detector ==3733364== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al. ==3733364==

Bug#1052141: Acknowledgement (valgrind: m_debuginfo/readdwarf.c:2761 (copy_convert_CfiExpr_tree): Assertion 'srcix >= 0 && srcix < VG_(sizeXA)(srcxa)' failed.)

Reproducer % clang++-16 -std=c++17 -Wfatal-errors -Wall -Wextra -Werror -O1 -o fails '-DHWY_DISABLED_TARGETS=(HWY_NEON|HWY_SVE|HWY_SVE2|HWY_SVE_256|HWY_SVE2_128)' math_test4.cc -lhwy -lhwy_contrib -lhwy_test % valgrind ./fails // Copyright 2020 Google LLC // SPDX-License-Identifier: Apache-2.0

Bug#1052141: valgrind: m_debuginfo/readdwarf.c:2761 (copy_convert_CfiExpr_tree): Assertion 'srcix >= 0 && srcix < VG_(sizeXA)(srcxa)' failed.

Source: valgrind Version: 1:3.19.0-1 On amdhal.d.o: % valgrind ./fails ==3527834== Memcheck, a memory error detector ==3527834== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al. ==3527834== Using Valgrind-3.19.0 and LibVEX; rerun with -h for copyright info ==3527834== Command:

Bug#1051126: armhf: Miscompilation at O2 level (O1 is working)

Total Test time (real) = 26.65 sec The following tests FAILED: 446 - HwyWidenMulTestGroup/HwyWidenMulTest.TestAllSatWidenMulPairwiseAdd/EMU128 # GetParam() = 2305843009213693952 (Subprocess aborted) 452 - HwyWidenMulTestGroup/HwyWidenMulTest.TestAllSumOfMulQuadAccumulate/EMU128 # GetParam() =

Bug#1051772: Fwd: ia64 generates wrong-code with LTO

Package: gcc-13 Version: 13.2.0-3 highway does not seem to work on ia64 with LTO (see #1051769). On yttrium with gcc-13: % /usr/bin/g++-13 -g -O2 -ffile-prefix-map=/home/malat/highway-1.0.7=. -flto=auto -ffat-lto-objects -specs=/usr/share/dpkg/pie-compile.specs -Wformat -Werror=format-security

Bug#1051769: ia64 generates wrong-code with LTO

Package: gcc-12 Version: 12.2.0-12 highway does not seems to work on ia64 with LTO: https://buildd.debian.org/status/fetch.php?pkg=highway=ia64=1.0.7-3=1694507301=0 The fun part is that even gdb crash on the generated exe: % gdb tests/copy_test GNU gdb (Debian 10.1-2) 10.1.90.20210103-git

Bug#1051764: Missing TARGET_OPTION_SAVE/RESTORE on riscv

Package: gcc-13 Version: 13.2.0-3 Forwarded: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110812 Affects: src:highway src:highway fails to compile on riscv64 with LTO. Confirmed upstream.

Bug#1051384: bookworm-pu: package highway/1.0.3-3

-3+deb11u1) bullseye; urgency=medium + + * d/rules: Fix armhf neon-less system. Closes: #1033656 + + -- Mathieu Malaterre Thu, 07 Sep 2023 09:04:55 +0200 + highway (1.0.3-3) unstable; urgency=medium [ Helmut Grohne ] diff -Nru highway-1.0.3/debian/rules highway-1.0.3/debian/rules

Bug#1016903: really closing for real

Version: 12.2.0-18 malat@barriere ~ % apt-cache policy gcc-12 gcc-12: Installed: 12.2.0-18 Candidate: 12.2.0-18 Version table: *** 12.2.0-18 100 1 https://deb.debian.org/debian experimental/main i386 Packages 100 /var/lib/dpkg/status 12.2.0-14 500 500

Bug#1050933: aarch64: Miscompilation at O1 level (O0 is working)

On Sun, Sep 3, 2023 at 9:23 AM Mathieu Malaterre wrote: > > On Sat, Sep 2, 2023 at 1:31 PM Matthias Klose wrote: > > upstream asks for a self-contained test case. Not sure if that's something > > you > > tried in https://bugs.debian.org/1050415 > > Currently

Bug#1051131: RM: jpeg-xl/experimental -- ROM; Newer version upstream

Package: ftp.debian.org Severity: normal Upstream has messed up the releases. 0.9.0snapshot was released *before* 0.8.0. https://github.com/libjxl/libjxl/tags I'd like to upload 0.8.0 to unstable, but since there is a SONAME transition I am required to upload to experimental first. So please

Bug#1050933: aarch64: Miscompilation at O1 level (O0 is working)

On Sat, Sep 2, 2023 at 1:31 PM Matthias Klose wrote: > upstream asks for a self-contained test case. Not sure if that's something you > tried in https://bugs.debian.org/1050415 Currently working on PR/111231. cresult is difficult to work with as it default to aggressive renaming. I've switch to

Bug#1051126: armhf: Miscompilation at O2 level (O1 is working)

Package: g++-13 Version: 13.2.0-2 Forwarded: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111231 Affects: src:highway I am getting some odd behavior for unit test of highway. I believe there is some wrong-code generation using g++ + -O2 on armhf. I also believe this is different from Debian bug

Bug#1050992: hwcap default search paths changed

Source: glibc Version: 2.37-1 Previously defined hwcap search paths have been changed. Those specified in `man 8 ld.so` are no longer accurate (bug #1050930). Typical output on sid/i386: % LD_DEBUG=libs LD_LIBRARY_PATH=. /bin/true 3611433: find library=libc.so.6 [0]; searching

Bug#1050933: aarch64: Miscompilation at O1 level (O0 is working)

Package: g++-13 Version: 13.2.0-2 Forwarded: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110643 Affects: src:highway I am getting some odd behavior for unit test of highway. I believe there is some wrong-code generation using g++ + -O1.

Bug#1050930: Obsolete hwcap section

Package: manpages-dev Version: 6.03-2 Currently `ld.so` man page describes location hwcap libraries. This appears to be obsolete in glibc 2.37. My Debian system reports: % LD_DEBUG=libs LD_LIBRARY_PATH=. /bin/true 3624017: find library=libc.so.6 [0]; searching 3624017: search

Bug#1050849: creduce upstream homepage

Source: creduce Version: 2.11.0~20230819-1 Could someone please document where creduce homepage is located nowadays. http://embed.cs.utah.edu/creduce/ seems to be gone. I am not clear what to do with reports such as: ===< pass_clang_binsrch :: replace-function-def-with-decl >=== Segmentation

Bug#1050506: [Pkg-cmake-team] Bug#1050506: Could NOT find EXPAT (missing: EXPAT_LIBRARY) (found version "2.5.0")

On Fri, Aug 25, 2023 at 4:06 PM Timo Röhling wrote: > > Control: severity -1 normal This caused a FTBFS in the original bug report. > Also, why do you think this is a CMake issue and not a VTK issue? As explained in my original report, this is a change of behavior in current cmake 3.27. If you

Bug#1042246: gdcm: FTBFS: make[1]: *** [debian/rules:107: override_dh_auto_configure] Error 2

Forwarded as #1050506

Bug#1050506: Could NOT find EXPAT (missing: EXPAT_LIBRARY) (found version "2.5.0")

Source: cmake Version: 3.27.3-1 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Affects: src:gdcm Original bug report is #1042246 Here is a minimal reproduce: % cat ../CMakeLists.txt cmake_minimum_required(VERSION 3.9.2)

Bug#1050415: PermissionError: [Errno 13] Permission denied

On Thu, Aug 24, 2023 at 7:03 PM Matthias Klose wrote: > > Control: tags -1 - moreinfo > > On 24.08.23 15:15, Mathieu Malaterre wrote: > > On Thu, Aug 24, 2023 at 2:21 PM Matthias Klose wrote: > >> > >> Control: tags -1 + moreinfo > >> &g

Bug#1050415: PermissionError: [Errno 13] Permission denied

On Thu, Aug 24, 2023 at 2:21 PM Matthias Klose wrote: > > Control: tags -1 + moreinfo > > On 24.08.23 11:54, Mathieu Malaterre wrote: > > Package: cvise > > Version: 2.8.0-1 > > > > I cannot run cvise in Debian/sid: > > [...] > > > with: > &g

Bug#1042246: gdcm: FTBFS: make[1]: *** [debian/rules:107: override_dh_auto_configure] Error 2

Control: tags -1 patch On Wed, Jul 26, 2023 at 10:30 PM Lucas Nussbaum wrote: [...] > > CMake Error at > > /usr/share/cmake-3.27/Modules/FindPackageHandleStandardArgs.cmake:230 > > (message): > > Could NOT find EXPAT (missing: EXPAT_LIBRARY) (found version "2.5.0") > > Call Stack (most

Bug#1050415: Acknowledgement (PermissionError: [Errno 13] Permission denied)

For reference, creduce seems to be happy with the exact same settings: % creduce check.sh testcase.i ===< 150190 >=== running 3 interestingness tests in parallel ===< pass_unifdef :: 0 >=== ===< pass_comments :: 0 >=== ===< pass_ifs :: 0 >=== ===< pass_includes :: 0 >=== ===< pass_line_markers

Bug#1050415: PermissionError: [Errno 13] Permission denied

Package: cvise Version: 2.8.0-1 I cannot run cvise in Debian/sid: % cvise check.sh testcase.i 00:00:07 INFO ===< 150150 >=== 00:00:07 INFO running 4 interestingness tests in parallel 00:00:07 INFO INITIAL PASSES 00:00:07 INFO ===< IncludesPass >=== Traceback (most recent call last): File

Bug#1049960: ITP: half -- C++ library for half precision floating point arithmetics

On Thu, Aug 17, 2023 at 1:27 PM Christian Kastner wrote: > > Package: wnpp > Severity: wishlist > Owner: Christian Kastner > X-Debbugs-Cc: debian-de...@lists.debian.org, debian...@lists.debian.org > > * Package name: half > Version : 2.2.0 > Upstream Author : Christian Rau > *

Bug#1050005: ITP: pdftopng -- Convert PDF to PNG

On Fri, Aug 18, 2023 at 1:19 PM Marvin Renich wrote: > > * Elena Grandi [230818 05:27]: > > Package: wnpp > > Severity: wishlist > > Owner: Elena Grandi > > > > * Package name: pdftopng > > Description : Convert PDF to PNG > > > > A command line tool and python library to convert PDFs

Bug#1040935: Please provide a version-less package for libboost-json1.81-dev

Source: boost1.81 Version: 1.81.0-5.2 As per title. For example I can Depends: on libboost-program-options-dev and have a nice transition. I cannot do the equivalent with libboost-json1.81-dev Thanks !

Bug#1040823: PR target/110560: internal compiler error: in extract_constrain_insn_cached, at recog.cc:2704

Package: g++-13 Version: 13.1.0-7 Forwarded: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110560 Affects: src:highway src:highway fails to compile on riscv64. Confirmed upstream. Already fixed in GCC14, backported to GCC13: * https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110560#c2

Bug#1040751: ITP: nanosvg -- simple svg parsing library

On Mon, Jul 10, 2023 at 10:08 AM Chow Loong Jin wrote: > > On Mon, Jul 10, 2023 at 07:50:21AM +0200, Mathieu Malaterre wrote: > > On Mon, Jul 10, 2023 at 6:03 AM Chow Loong Jin wrote: > > > * Package name: nanosvg > > > Version : 0~git20221204.1.9d

Bug#1040751: ITP: nanosvg -- simple svg parsing library

On Mon, Jul 10, 2023 at 6:03 AM Chow Loong Jin wrote: > * Package name: nanosvg > Version : 0~git20221204.1.9da543e > Upstream Contact: https://github.com/memononen/nanosvg/issues > * URL : https://github.com/memonenen/nanosvg https://github.com/memononen/nanosvg > *

Bug#1040394: Fwd: [someth2say/xmlformat] Submit to debian (Issue #23)

Source: xmlformat -- Forwarded message - From: Jordi Sola Oh, I didn't know debian was packaging XMLFormat. They are using the original script from Kitebird (www.kitebird.com), not this fork. I wonder if they would be interested in bumping to this updated version! link: *

Bug#635765: /bin/dd: dd if=/dev/zero of=testfile_4G bs=4G count=1 produces a 2G file

Control: tags -1 wontfix On Tue, Jul 4, 2023 at 5:02 PM Jakub Wilk wrote: > > * Mathieu Malaterre , 2011-07-28 17:49: > >For some reason the following command: > > > >dd if=/dev/zero of=testfile_4G bs=4G count=1 > > > >produces a 2G file: > > > &g

Bug#1039465: DICOM/JSON: (0018,1411) DS [-3. ] # 4,1 Exposure Index

Source: dcmtk Version: 3.6.7-8+b1 Forwarded: https://support.dcmtk.org/redmine/issues/1079 Tags: upstream dcm2json uses the method DcmJsonFormat::normalizeDecimalString() to normalize DICOM DS values before writing them as JSON. However, the method currently does not catch all cases where a legal

Bug#1038774: PR110264: internal compiler error: riscv_vector::vector_insn_info::get_avl_reg_rtx

Package: g++-13 Version: 13.1.0-6 Forwarded: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110264 Affects: src:highway src:highway fails to compile on riscv64. Confirmed upstream. Fixed in GCC14

Bug#1038768: PR110280: internal compiler error: in const_unop, at fold-const.cc:1884

Package: g++-13 Version: 13.1.0-6 Forwarded: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110280 Affects: src:highway src:highway fails to compile on arm64. Confirmed upstream

Bug#1038702: libjpeg6b: Should provide libjpeg62-turbo (>= 1.3.1)

Source: libjpeg6b Version: 1:6b2-3.1 As odd as it sounds it seems that libjpeg62 should now provides: libjpeg62-turbo (>= 1.3.1) Otherwise it cannot be installed on typical sid system, it would remove jre for instance: [...] % apt-cache show openjdk-17-jre-headless | grep jpeg Depends: [...]

Bug#298721: add lossless and 12/16 bit support to jpeg library

Control: tags -1 wontfix This has been recently implemented in -turbo: * https://github.com/libjpeg-turbo/libjpeg-turbo/issues/402 Thus closing. Thanks all.

Bug#1037981: Stop installing the header file jpegint.h

Package: libjpeg62-turbo-dev Version: 1:2.0.6-4 We should not be distributing jpegint.h header, it gives a false sense of API. Here is the full verbatim quote from upstream about this: ``` jpegint.h is only included by jpeglib.h if JPEG_INTERNALS is defined. jpegint.h is a project-private

Bug#1001786: jpeg-xl: Please build plugins

Control: tags -1 - wontfix On Fri, Jun 9, 2023 at 1:39 PM Julian Wollrath wrote: > > Hi, > > > it seems, like upstream is moving the plugin to use lcms2 [1] which is > > available in debian. > > I tried building a package with a new snapshot and enabled the building > of the gdk-pixbuf plugin

Bug#1036042: build-depends on libgmock-dev

Control: tags -1 invalid wontfix > it succeded once I installed the package libgmock-dev. My crystal ball tells me the compilation error arises somewhere in the *.cmake ot GTest package. Since no debuidd machines are failing, closing as invalid. Thanks

Bug#566801: jeuclid-cli does not work on simple example

Control: fixed -1 3.1.9-5 On Sun, May 28, 2023 at 5:39 PM Mathieu Malaterre wrote: > > On Sun, May 28, 2023 at 3:21 PM Pierre Gruet wrote: > > > > Control: tags -1 moreinfo unreproducible > > > > Hi Matthieu, > > > > Doing some bug triaging... > >

Bug#1036584: libopenjpip-viewer: broken symlink: /usr/bin/opj_jpip_viewer -> ../share/opj_jpip_viewer/opj_jpip_viewer.jar

Le jeu. 25 mai 2023, 19:15, Andreas Metzler a écrit : > Hello, > > if you have not got time for an upload I can look into it. > Yes please ! Thanks very much > cu Andreas > >

Bug#1036584: libopenjpip-viewer: broken symlink: /usr/bin/opj_jpip_viewer -> ../share/opj_jpip_viewer/opj_jpip_viewer.jar

Control: tags -1 - patch On Wed, May 24, 2023 at 6:21 PM Andreas Metzler wrote: > > Control: retitle -1 libopenjpip-viewer is basically empty > > On 2023-05-23 Mathieu Malaterre wrote: > > On Tue, May 23, 2023 at 10:46 AM Mathieu Malaterre wrote: > > > > &

Bug#1036584: libopenjpip-viewer: broken symlink: /usr/bin/opj_jpip_viewer -> ../share/opj_jpip_viewer/opj_jpip_viewer.jar

Control: tags -1 patch On Tue, May 23, 2023 at 10:46 AM Mathieu Malaterre wrote: > > Control: retitle -1 No java compiler found. Won't be able to build java viewer > > openjpeg2/java compilation appears to be broken: > > -- Could NOT find Java (missing: Ja

Bug#1036584: libopenjpip-viewer: broken symlink: /usr/bin/opj_jpip_viewer -> ../share/opj_jpip_viewer/opj_jpip_viewer.jar

Control: retitle -1 No java compiler found. Won't be able to build java viewer openjpeg2/java compilation appears to be broken: -- Could NOT find Java (missing: Java_JAVA_EXECUTABLE Java_JAVAC_EXECUTABLE Java_JAR_EXECUTABLE Java_JAVADOC_EXECUTABLE Java_JAVAH_EXECUTABLE Development) (Required is

Bug#1016903: closing for real

Version: 12.2.0-8 malat@barriere ~ % apt-cache policy gcc-12 gcc-12: Installed: 12.2.0-18 Candidate: 12.2.0-18 Version table: *** 12.2.0-18 100 1 https://deb.debian.org/debian experimental/main i386 Packages 100 /var/lib/dpkg/status 12.2.0-14 500 500

Bug#1034554: internal compiler error: in finalize_new_accesses, at rtl-ssa/changes.cc:471

Source: gcc-13 Version: 13-20230411-1 I cannot compile highway on riscv/rv64gcv1p0 with gcc-13. Compilation fais with: % /usr/bin/g++-13 -freport-bug -DHWY_SHARED_DEFINE -I"/home/malat/highway-1.0.4~git20230317.8681eb8" -g -O2 -ffile-prefix-map=/home/malat/highway-1.0.4~git20230317.8681eb8=.

Bug#1034353: mime-type: image/jpeg instead of image/jls

Source: file Version: 1:5.44-3 Steps: % wget -O filelogo.jls "https://bugs.astron.com/file_download.php?file_id=214=bug; % file --mime-type filelogo.jls filelogo.jls: image/jpeg However upstream claims this is fixed since 5.41, some kind of regression ? *

Bug#1033931: UB: memcmp is not atomic in C11 either

The bugzilla thread is rather long. But I took the liberty to report the issue as grave following the comment: https://sourceware.org/bugzilla/show_bug.cgi?id=29863#c11 Feel free to downgrade severity if my understanding is incorrect. Thanks

Bug#1033931: Fwd: Novice needs help submitting a bug report

Package: libc-bin Version: 2.36-8 Severity: grave Justification: renders package unusable Dear Maintainer, There is a bug in glibc 2.36 that has been fixed in 2.37. The two links below detail the original bug report and the fix. - Upstream bug report -

Bug#1033656: bt full with dbgsym

% gdb cjxl GNU gdb (Debian 13.1-2) 13.1 Copyright (C) 2023 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type

Bug#1033656: HWY_CMAKE_ARM7:BOOL=ON vs Dynamic Dispatch

Control: forwarded -1 https://github.com/google/highway/issues/1271 Technically we could just do a source upload with HWY_CMAKE_ARM7:BOOL=OFF. HWY_CMAKE_ARM7:BOOL=ON is a hack for an old clang version, if I understand correctly.

Bug#1033656: illegal hardware instruction cjxl

Package: libjxl-tools Version: 0.7.0-10 Severity: important cjxl/djxl cannot be used on armhf neon-less system. They fails with: % djxl zsh: illegal hardware instruction djxl Full ref: % gdb /usr/bin/cjxl GNU gdb (Debian 13.1-2) 13.1 Copyright (C) 2023 Free Software Foundation, Inc. License

Bug#1016903: git-updates.diff not applied ?

Control: reopen -1 > the upstream fix went into 12.2.0-2. Would be so kind as to demonstrate how ? Here is what I see on my side: % ssh barriere.debian.org % sessionid=$(schroot -b -c sid_i386-dchroot) % dd-schroot-cmd -c $sessionid apt-get update % dd-schroot-cmd -c $sessionid apt-get upgrade

Bug#1016903: vect: Don't allow vect_emulated_vector_p type in vectorizable_call [PR106322]

Control: severity -1 grave By default packages on Debian are build with -O2 since I see that it affects release arches: * armel * i386 * mips64el * mipsel Would it be possible to include fix: https://gcc.gnu.org/g:9f532fec01d6651cc3cc136073f044a7953d8560 Thanks,

Bug#1032118: riscv64: error: too few arguments to function 'long unsigned int __riscv_vsetvlmax_e8mf8(void)'

Control: forwarded -1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108927 Control: tags -1 confirmed upstream patch [PATCH] RISC-V: Remove void_type_node of void_args for vsetvlmax intrinsic https://gcc.gnu.org/pipermail/gcc-patches/2023-February/612858.html

Bug#1032118: riscv64: error: too few arguments to function 'long unsigned int __riscv_vsetvlmax_e8mf8(void)'

Source: gcc-snapshot riscv64 intrisincs are currently broken. % cat t.c #include int main() { size_t vl = __riscv_vsetvlmax_e8mf8(); return vl; } Gives: g++ -march=rv64gcv1p0 t.c t.c: In function 'int main()': t.c:5:39: error: too few arguments to function 'long unsigned int

Bug#1021165: floatn-common.h:214:9: error: multiple types in one declaration

Control: reassign -1 libc6.1-dev 2.36-5 Looks like the issue is not fixed on ia64 / sparc64. Steps: % cat p.cxx #include int main() { return 0; } Lead to: malat@yttrium ~ % /usr/lib/gcc-snapshot/bin/g++ -v p.cxx Using built-in specs. COLLECT_GCC=/usr/lib/gcc-snapshot/bin/g++

Bug#1031866: /usr/bin/ld: cannot find -lgcc_s: No such file or directory

Package: gcc-snapshot Version: 1:20230108-1 on riscv64, here is what I see: $ cat /tmp/bla.c int main() {} $ /usr/lib/gcc-snapshot/bin/gcc /tmp/bla.c /usr/bin/ld: cannot find -lgcc_s: No such file or directory collect2: error: ld returned 1 exit status Thanks

Bug#1024141: gtest: Normal execution is halted

On Tue, Nov 15, 2022 at 3:05 PM Steven Robbins wrote: > > On Tuesday, November 15, 2022 7:44:13 A.M. CST Mathieu Malaterre wrote: > > > jpeg-xl unit tests cannot be run on GNU/Hurd. It seems to be stuck for > > infinite time. > > That is curious. It would help g

Bug#1029698: ColorManagementTestInstantiation/ColorManagementTest.VerifyAllProfiles/ColorEncoding/RGB_D65_SRG_Per_709 (Failed)

Source: jpeg-xl Version: 0.8.0~git20230118.bcacd51-1 Seems like there is a regression in the testsuite since 0.7.0 See: https://github.com/libjxl/libjxl/issues/1910

Bug#1027965: Add libvtk6-qt-dev to dependencies

Control: tags -1 patch Since 2016 it seems that a hack has been put in place in vtk package consumer to always include vtk-qt package: https://salsa.debian.org/med-team/vtk-dicom/-/commit/0d3fde678cd86459a485df7492307b94a5afc97e I suspect it would be better done in vtk9 package itself. Typical

Bug#1027965: gdcm: FTBFS everywhere

Control: reassign -1 vtk9 9.1.0+really9.1.0+dfsg2-4 On Thu, Jan 5, 2023 at 11:03 AM Sebastian Ramacher wrote: [...] > CMake Error at > /usr/lib/x86_64-linux-gnu/cmake/vtk-9.1/VTK-vtk-module-find-packages.cmake:115 > (find_package): > By not providing "FindQt5.cmake" in CMAKE_MODULE_PATH this

Bug#1026559: fop: FTBFS: [javadoc] /<>/fop-core/src/main/java/org/apache/fop/servlet/FopServlet.java:29: error: package javax.servlet does not exist

Control: fixed -1 1:2.8-2 Seems to build fine now: https://buildd.debian.org/status/fetch.php?pkg=fop=all=1%3A2.8-2=1672905531=0 Closing.

Bug#1023746: Improve 'custom' codec in benchmark.

Control: found 1023746 0.7.0-7 Looks like I am missing a commit from main branch: https://github.com/libjxl/libjxl/commit/de08116d14db785431f3efb651dcf2af15bbb682.patch

Bug#1018954: Can't open perl script "/usr/share/vtk9/doxygen//doc_header2doxygen.pl": No such file or directory

On Thu, Dec 29, 2022 at 5:10 PM Paul Gevers wrote: > > Hi, > > On Fri, 2 Sep 2022 15:15:50 +0200 Mathieu Malaterre > wrote: > > Source: vtk9 > > Version: 9.1.0+really9.1.0+dfsg2-4 > > > > This is yet the same issue again, gdcm will need the file &g

  1   2   3   4   5   6   7   8   9   10   >