Bug#1061627: jpeg-xl: 0.8 failing autopkgtest

2024-05-21 Thread Mathieu Malaterre
Control: tags -1 upstream patch fixed-upstream Control: forwarded -1 https://github.com/libjxl/libjxl/issues/2391 On Sat, Jan 27, 2024 at 4:51 PM Jeremy Bícha wrote: [...] > Test - Lossless Roundtrip > JPEG XL encoder v0.8.2 [AVX2,SSE4,SSSE3,SSE2] > ./lib/extras/dec/color_hints.cc:54: No

Bug#1061627: jpeg-xl: 0.8 failing autopkgtest

2024-05-21 Thread Mathieu Malaterre
Control: tags -1 upstream patch fixed-upstream Control: forwarded -1 https://github.com/libjxl/libjxl/issues/2391 On Sat, Jan 27, 2024 at 4:51 PM Jeremy Bícha wrote: [...] > Test - Lossless Roundtrip > JPEG XL encoder v0.8.2 [AVX2,SSE4,SSSE3,SSE2] > ./lib/extras/dec/color_hints.cc:54: No

Bug#1061627: jpeg-xl: 0.8 failing autopkgtest

2024-05-21 Thread Mathieu Malaterre
Control: tags -1 upstream patch fixed-upstream Control: forwarded -1 https://github.com/libjxl/libjxl/issues/2391 On Sat, Jan 27, 2024 at 4:51 PM Jeremy Bícha wrote: [...] > Test - Lossless Roundtrip > JPEG XL encoder v0.8.2 [AVX2,SSE4,SSSE3,SSE2] > ./lib/extras/dec/color_hints.cc:54: No

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

2024-03-19 Thread Mathieu Malaterre
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#1060104: dcmtk: FTBFS on armel: Error: bad immediate value for offset (4100)

2024-03-19 Thread Mathieu Malaterre
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,

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

2024-03-19 Thread Mathieu Malaterre
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

2024-01-31 Thread Mathieu Malaterre
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#1060704: transition: dcmtk

2024-01-31 Thread Mathieu Malaterre
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

2024-01-31 Thread Mathieu Malaterre
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#1062022: dcmtk: NMU diff for 64-bit time_t transition

2024-01-31 Thread Mathieu Malaterre
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)

2024-01-18 Thread Mathieu Malaterre
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)

2024-01-18 Thread Mathieu Malaterre
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)

2024-01-14 Thread Mathieu Malaterre
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#1060104: dcmtk: FTBFS on armel: Error: bad immediate value for offset (4100)

2024-01-14 Thread Mathieu Malaterre
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

2024-01-13 Thread Mathieu Malaterre
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#1053866: transition: jpeg-xl

2024-01-13 Thread Mathieu Malaterre
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

2024-01-13 Thread Mathieu Malaterre
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#1060704: transition: dcmtk

2024-01-13 Thread Mathieu Malaterre
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

[med-svn] [Git][med-team/dcmtk][debian/experimental] 2 commits: d/rules: Fix armel buildd

2024-01-12 Thread Mathieu Malaterre (@malat)
Mathieu Malaterre pushed to branch debian/experimental at Debian Med / dcmtk Commits: 42583dfe by Emanuele Rocca at 2024-01-12T17:08:37+01:00 d/rules: Fix armel buildd - - - - - f4c27faa by Mathieu Malaterre at 2024-01-12T17:09:28+01:00 d/changelog: Upload 3.6.8-3 to experimental

[med-svn] [Git][med-team/dcmtk] Pushed new tag debian/3.6.8-3

2024-01-12 Thread Mathieu Malaterre (@malat)
Mathieu Malaterre pushed new tag debian/3.6.8-3 at Debian Med / dcmtk -- View it on GitLab: https://salsa.debian.org/med-team/dcmtk/-/tree/debian/3.6.8-3 You're receiving this email because of your account on salsa.debian.org. ___ debian-med-commit

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

2024-01-12 Thread Mathieu Malaterre
forwarded -1 https://support.dcmtk.org/redmine/issues/1100

Bug#1060677: Rounding error in OFStandard::atof

2024-01-12 Thread Mathieu Malaterre
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

Error: bad immediate value for offset (4100)

2024-01-12 Thread Mathieu Malaterre
[CC me please] Dear ARM porters, Could someone please confirm what I see on the armel/buildd: * https://buildd.debian.org/status/fetch.php?pkg=dcmtk=armel=3.6.8-2=1705054390=0 Is this a 32bits/limited RAM issue ? Is there a way to fix the symptoms ? Thanks !

[med-svn] [Git][med-team/dcmtk] Pushed new tag debian/3.6.8-2

2024-01-12 Thread Mathieu Malaterre (@malat)
Mathieu Malaterre pushed new tag debian/3.6.8-2 at Debian Med / dcmtk -- View it on GitLab: https://salsa.debian.org/med-team/dcmtk/-/tree/debian/3.6.8-2 You're receiving this email because of your account on salsa.debian.org. ___ debian-med-commit

[med-svn] [Git][med-team/dcmtk][debian/experimental] 3 commits: d/rules: Fix test suite on x87 hardware

2024-01-12 Thread Mathieu Malaterre (@malat)
Mathieu Malaterre pushed to branch debian/experimental at Debian Med / dcmtk Commits: 55e72fc5 by Mathieu Malaterre at 2024-01-12T10:33:11+01:00 d/rules: Fix test suite on x87 hardware - - - - - 2dce6668 by Mathieu Malaterre at 2024-01-12T10:33:52+01:00 d/patches: Import bug fix from upstream

[med-svn] [Git][med-team/dcmtk] Pushed new tag upstream/3.6.8

2024-01-11 Thread Mathieu Malaterre (@malat)
Mathieu Malaterre pushed new tag upstream/3.6.8 at Debian Med / dcmtk -- View it on GitLab: https://salsa.debian.org/med-team/dcmtk/-/tree/upstream/3.6.8 You're receiving this email because of your account on salsa.debian.org. ___ debian-med-commit

[med-svn] [Git][med-team/dcmtk] Pushed new tag debian/3.6.8-1

2024-01-11 Thread Mathieu Malaterre (@malat)
Mathieu Malaterre pushed new tag debian/3.6.8-1 at Debian Med / dcmtk -- View it on GitLab: https://salsa.debian.org/med-team/dcmtk/-/tree/debian/3.6.8-1 You're receiving this email because of your account on salsa.debian.org. ___ debian-med-commit

[med-svn] [Git][med-team/dcmtk][debian/experimental] 4 commits: New upstream version 3.6.8

2024-01-11 Thread Mathieu Malaterre (@malat)
Mathieu Malaterre pushed to branch debian/experimental at Debian Med / dcmtk Commits: 2ffc893b by Mathieu Malaterre at 2024-01-11T15:40:43+01:00 New upstream version 3.6.8 - - - - - 67a6f7c4 by Mathieu Malaterre at 2024-01-11T15:40:43+01:00 Update upstream source from tag upstream/3.6.8

[med-svn] [Git][med-team/dcmtk][upstream] New upstream version 3.6.8

2024-01-11 Thread Mathieu Malaterre (@malat)
Mathieu Malaterre pushed to branch upstream at Debian Med / dcmtk Commits: 2ffc893b by Mathieu Malaterre at 2024-01-11T15:40:43+01:00 New upstream version 3.6.8 - - - - - 12 changed files: - ANNOUNCE - CMake/3rdparty.cmake - CMake/GenerateDCMTKConfigure.cmake - CMake/dcmtkPrepare.cmake

Bug#1060442: DCMTK Release 3.6.8 available

2024-01-11 Thread Mathieu Malaterre
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#1056953: marked as pending in gdcm

2023-12-07 Thread Mathieu Malaterre
Control: tag -1 pending Hello, Bug #1056953 in gdcm reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

[med-svn] [Git][med-team/gdcm][master] Update debian/series

2023-12-07 Thread Mathieu Malaterre (@malat)
Mathieu Malaterre pushed to branch master at Debian Med / gdcm Commits: ff202349 by Mathieu Malaterre at 2023-12-07T10:39:39+01:00 Update debian/series - - - - - 1 changed file: - debian/patches/series Changes: = debian/patches/series

[med-svn] [Git][med-team/gdcm] Pushed new tag debian/3.0.22-2

2023-12-07 Thread Mathieu Malaterre (@malat)
Mathieu Malaterre pushed new tag debian/3.0.22-2 at Debian Med / gdcm -- View it on GitLab: https://salsa.debian.org/med-team/gdcm/-/tree/debian/3.0.22-2 You're receiving this email because of your account on salsa.debian.org. ___ debian-med-commit

[med-svn] [Git][med-team/gdcm] Pushed new tag upstream/3.0.22

2023-12-07 Thread Mathieu Malaterre (@malat)
Mathieu Malaterre pushed new tag upstream/3.0.22 at Debian Med / gdcm -- View it on GitLab: https://salsa.debian.org/med-team/gdcm/-/tree/upstream/3.0.22 You're receiving this email because of your account on salsa.debian.org. ___ debian-med-commit

[med-svn] [Git][med-team/gdcm] Pushed new tag debian/3.0.22-1

2023-12-07 Thread Mathieu Malaterre (@malat)
Mathieu Malaterre pushed new tag debian/3.0.22-1 at Debian Med / gdcm -- View it on GitLab: https://salsa.debian.org/med-team/gdcm/-/tree/debian/3.0.22-1 You're receiving this email because of your account on salsa.debian.org. ___ debian-med-commit

[med-svn] [Git][med-team/gdcm][master] 2 commits: d/patches: Revert changes breaking binary ABI. Closes: #1056953

2023-12-07 Thread Mathieu Malaterre (@malat)
Mathieu Malaterre pushed to branch master at Debian Med / gdcm Commits: 263554ea by Mathieu Malaterre at 2023-12-07T10:37:06+01:00 d/patches: Revert changes breaking binary ABI. Closes: #1056953 - - - - - c297d79a by Mathieu Malaterre at 2023-12-07T10:37:33+01:00 d/changelog: Upload 3.0.22-2

Bug#1056048: Acknowledgement (Memory leak in dcm2json)

2023-11-20 Thread Mathieu Malaterre
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

2023-11-20 Thread Mathieu Malaterre
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

2023-11-16 Thread Mathieu Malaterre
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)

2023-11-13 Thread Mathieu Malaterre
Current work-around: % dcmconv +ti RTStruct_VRDSAsVRUN.dcm - | dcm2json - output.json

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

2023-11-13 Thread Mathieu Malaterre
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

2023-11-13 Thread Mathieu Malaterre
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"

2023-11-13 Thread Mathieu Malaterre
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

2023-11-07 Thread Mathieu Malaterre
Control: fixed -1 3.6-25 Control: tags -1 wontfix PEBKAC % echo -n 'ABC' > 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)

2023-11-07 Thread Mathieu Malaterre
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

2023-11-07 Thread Mathieu Malaterre
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.

2023-11-07 Thread Mathieu Malaterre
> 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 :)

[med-svn] [Git][med-team/dcmtk] Pushed new tag debian/3.6.8_git20231027.1549d8c-2

2023-11-06 Thread Mathieu Malaterre (@malat)
Mathieu Malaterre pushed new tag debian/3.6.8_git20231027.1549d8c-2 at Debian Med / dcmtk -- View it on GitLab: https://salsa.debian.org/med-team/dcmtk/-/tree/debian/3.6.8_git20231027.1549d8c-2 You're receiving this email because of your account on salsa.debian.org

[med-svn] [Git][med-team/dcmtk][debian/experimental] 2 commits: d/patches: Fix install path for docs

2023-11-06 Thread Mathieu Malaterre (@malat)
Mathieu Malaterre pushed to branch debian/experimental at Debian Med / dcmtk Commits: 2318cc44 by Mathieu Malaterre at 2023-11-06T12:04:04+01:00 d/patches: Fix install path for docs - - - - - 0ea5fd8d by Mathieu Malaterre at 2023-11-06T12:07:55+01:00 d/changelog: Upload 3.6.8

[med-svn] [Git][med-team/dcmtk] Pushed new tag upstream/3.6.8_git20231027.1549d8c

2023-11-06 Thread Mathieu Malaterre (@malat)
Mathieu Malaterre pushed new tag upstream/3.6.8_git20231027.1549d8c at Debian Med / dcmtk -- View it on GitLab: https://salsa.debian.org/med-team/dcmtk/-/tree/upstream/3.6.8_git20231027.1549d8c You're receiving this email because of your account on salsa.debian.org

[med-svn] [Git][med-team/dcmtk] Pushed new tag debian/3.6.8_git20231027.1549d8c-1

2023-11-06 Thread Mathieu Malaterre (@malat)
Mathieu Malaterre pushed new tag debian/3.6.8_git20231027.1549d8c-1 at Debian Med / dcmtk -- View it on GitLab: https://salsa.debian.org/med-team/dcmtk/-/tree/debian/3.6.8_git20231027.1549d8c-1 You're receiving this email because of your account on salsa.debian.org

[med-svn] [Git][med-team/dcmtk][upstream] New upstream version 3.6.8~git20231027.1549d8c

2023-11-06 Thread Mathieu Malaterre (@malat)
Mathieu Malaterre pushed to branch upstream at Debian Med / dcmtk Commits: 53c26ca1 by Mathieu Malaterre at 2023-11-06T09:21:23+01:00 New upstream version 3.6.8~git20231027.1549d8c - - - - - 30 changed files: - CMake/3rdparty.cmake - CMake/FindICU.cmake - CMake/GenerateDCMTKConfigure.cmake

[med-svn] [Git][med-team/dcmtk][debian/experimental] 5 commits: New upstream version 3.6.8~git20231027.1549d8c

2023-11-06 Thread Mathieu Malaterre (@malat)
Mathieu Malaterre pushed to branch debian/experimental at Debian Med / dcmtk Commits: 53c26ca1 by Mathieu Malaterre at 2023-11-06T09:21:23+01:00 New upstream version 3.6.8~git20231027.1549d8c - - - - - b516ac9b by Mathieu Malaterre at 2023-11-06T09:21:23+01:00 Update upstream source from tag

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

2023-11-03 Thread Mathieu Malaterre
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

2023-11-03 Thread Mathieu Malaterre
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

dpkg: error processing archive /var/cache/apt/archives/usr-is-merged_38_all.deb (--unpack):

2023-10-31 Thread Mathieu Malaterre
Hi folks, Would anyone know what to do with perotto.d.n ? Thanks Here is what I get today: % sessionid=$(schroot -b -c sid) % dd-schroot-cmd -c $sessionid apt-get update % dd-schroot-cmd -c $sessionid apt-get upgrade [..] Preparing to unpack .../usr-is-merged_38_all.deb ...

[med-svn] [Git][med-team/charls] Pushed new tag debian/2.4.2-2

2023-10-30 Thread Mathieu Malaterre (@malat)
Mathieu Malaterre pushed new tag debian/2.4.2-2 at Debian Med / charls -- View it on GitLab: https://salsa.debian.org/med-team/charls/-/tree/debian/2.4.2-2 You're receiving this email because of your account on salsa.debian.org. ___ debian-med

[med-svn] [Git][med-team/charls][master] 4 commits: d/maintscript: Remove leftover

2023-10-30 Thread Mathieu Malaterre (@malat)
Mathieu Malaterre pushed to branch master at Debian Med / charls Commits: 990d2728 by Mathieu Malaterre at 2023-10-30T15:54:38+01:00 d/maintscript: Remove leftover - - - - - 70e94213 by Mathieu Malaterre at 2023-10-30T15:56:10+01:00 d/rules: Migrate to ninja build - - - - - b6d8467a

[med-svn] [Git][med-team/charls] Pushed new tag debian/2.4.2-1

2023-10-30 Thread Mathieu Malaterre (@malat)
Mathieu Malaterre pushed new tag debian/2.4.2-1 at Debian Med / charls -- View it on GitLab: https://salsa.debian.org/med-team/charls/-/tree/debian/2.4.2-1 You're receiving this email because of your account on salsa.debian.org. ___ debian-med

Bug#1054696: marked as pending in gdcm

2023-10-30 Thread Mathieu Malaterre
Control: tag -1 pending Hello, Bug #1054696 in gdcm reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

[med-svn] [Git][med-team/gdcm][upstream] New upstream version 3.0.22

2023-10-30 Thread Mathieu Malaterre (@malat)
Mathieu Malaterre pushed to branch upstream at Debian Med / gdcm Commits: 5c264060 by Mathieu Malaterre at 2023-10-30T15:26:41+01:00 New upstream version 3.0.22 - - - - - 30 changed files: - + .clang-tidy - − .gitignore - − .gitmodules - Applications/Cxx/gdcmanon.cxx - Applications/Cxx

[med-svn] [Git][med-team/gdcm][master] 4 commits: New upstream version 3.0.22

2023-10-30 Thread Mathieu Malaterre (@malat)
Mathieu Malaterre pushed to branch master at Debian Med / gdcm Commits: 5c264060 by Mathieu Malaterre at 2023-10-30T15:26:41+01:00 New upstream version 3.0.22 - - - - - 6057456e by Mathieu Malaterre at 2023-10-30T15:26:41+01:00 Update upstream source from tag upstream/3.0.22 Update

Upload commands to debomatic-amd64

2023-10-30 Thread Mathieu Malaterre
Dear all, I am trying to follow documentation from: * http://debomatic-amd64.debian.net/ and: * https://deb-o-matic.readthedocs.io/en/stable/upload.html#prepare-command-files Which does not seems to be working for me today; % dcut -U debomatic jxl.commands usage: dcut [-h] [-d] [-f] [-c

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

2023-10-18 Thread Mathieu Malaterre
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

2023-10-13 Thread Mathieu Malaterre
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

2023-10-13 Thread Mathieu Malaterre
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

2023-10-13 Thread Mathieu Malaterre
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#1053866: transition: jpeg-xl

2023-10-13 Thread Mathieu Malaterre
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

[med-svn] [Git][med-team/charls] Pushed new tag upstream/2.4.2

2023-10-12 Thread Mathieu Malaterre (@malat)
Mathieu Malaterre pushed new tag upstream/2.4.2 at Debian Med / charls -- View it on GitLab: https://salsa.debian.org/med-team/charls/-/tree/upstream/2.4.2 You're receiving this email because of your account on salsa.debian.org. ___ debian-med

[med-svn] [Git][med-team/charls] Pushed new tag upstream/2.4.1

2023-10-12 Thread Mathieu Malaterre (@malat)
Mathieu Malaterre pushed new tag upstream/2.4.1 at Debian Med / charls -- View it on GitLab: https://salsa.debian.org/med-team/charls/-/tree/upstream/2.4.1 You're receiving this email because of your account on salsa.debian.org. ___ debian-med

[med-svn] [Git][med-team/charls] Pushed new tag debian/2.4.1-1

2023-10-12 Thread Mathieu Malaterre (@malat)
Mathieu Malaterre pushed new tag debian/2.4.1-1 at Debian Med / charls -- View it on GitLab: https://salsa.debian.org/med-team/charls/-/tree/debian/2.4.1-1 You're receiving this email because of your account on salsa.debian.org. ___ debian-med

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

2023-10-11 Thread Mathieu Malaterre
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#1051905: jpeg-xl: Please add support for Loongarch

2023-10-11 Thread Mathieu Malaterre
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

2023-10-10 Thread Mathieu Malaterre
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

2023-10-08 Thread Mathieu Malaterre
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#1053641: transition: libavif

2023-10-08 Thread Mathieu Malaterre
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:

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

Bug#1050933:

2023-10-05 Thread Mathieu Malaterre
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

2023-10-02 Thread Mathieu Malaterre
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#1052677: Fixed in 1.0.7-1

2023-10-02 Thread Mathieu Malaterre
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#1052677: Fixed in 1.0.7-1

2023-10-02 Thread Mathieu Malaterre
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

2023-09-27 Thread Mathieu Malaterre
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#1051384: bookworm-pu: package highway/1.0.3-3

2023-09-27 Thread Mathieu Malaterre
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)

2023-09-21 Thread Mathieu Malaterre
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#1033656: closed by Debian FTP Masters (reply to Mathieu Malaterre ) (Bug#1033656: fixed in highway 1.0.7-1)

2023-09-21 Thread Mathieu Malaterre
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

[valgrind] [Bug 461074] valgrind: m_debuginfo/readdwarf.c:2396 (copy_convert_CfiExpr_tree): Assertion 'srcix >= 0 && srcix < VG_(sizeXA)(srcxa)' failed.

2023-09-20 Thread Mathieu Malaterre
https://bugs.kde.org/show_bug.cgi?id=461074 --- Comment #7 from Mathieu Malaterre --- (In reply to Mark Wielaard from comment #4) > Thanks, so that is in libhwy_contrib.so.1.0.7 which is > https://packages.debian.org/sid/libhwy1 and can be downloaded through > http://ftp.debian.org/de

[valgrind] [Bug 461074] valgrind: m_debuginfo/readdwarf.c:2396 (copy_convert_CfiExpr_tree): Assertion 'srcix >= 0 && srcix < VG_(sizeXA)(srcxa)' failed.

2023-09-20 Thread Mathieu Malaterre
https://bugs.kde.org/show_bug.cgi?id=461074 --- Comment #6 from Mathieu Malaterre --- Created attachment 161747 --> https://bugs.kde.org/attachment.cgi?id=161747=edit % valgrind --debug-dump=frames ./fails >& /tmp/frames.txt -- You are receiving this mail because: You are watchi

[valgrind] [Bug 461074] valgrind: m_debuginfo/readdwarf.c:2396 (copy_convert_CfiExpr_tree): Assertion 'srcix >= 0 && srcix < VG_(sizeXA)(srcxa)' failed.

2023-09-20 Thread Mathieu Malaterre
https://bugs.kde.org/show_bug.cgi?id=461074 --- Comment #3 from Mathieu Malaterre --- (In reply to Mark Wielaard from comment #2) > The first issue seems to be because we cannot handle the CFI from this > libamath.so library. > For the second it isn't clear which library causes the iss

[valgrind] [Bug 461074] valgrind: m_debuginfo/readdwarf.c:2396 (copy_convert_CfiExpr_tree): Assertion 'srcix >= 0 && srcix < VG_(sizeXA)(srcxa)' failed.

2023-09-20 Thread Mathieu Malaterre
https://bugs.kde.org/show_bug.cgi?id=461074 Mathieu Malaterre changed: What|Removed |Added CC||ma...@debian.org --- Comment #1 from

Bug#1052141: Simplified

2023-09-20 Thread Mathieu Malaterre
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.)

2023-09-18 Thread Mathieu Malaterre
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.

2023-09-18 Thread Mathieu Malaterre
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)

2023-09-15 Thread Mathieu Malaterre
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#1051126: armhf: Miscompilation at O2 level (O1 is working)

2023-09-15 Thread Mathieu Malaterre
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() =

LTO status on ia64 ?

2023-09-14 Thread Mathieu Malaterre
[Cc me please] Hi gurus ! Could someone please double check what I did at: * https://buildd.debian.org/status/fetch.php?pkg=highway=ia64=1.0.7-4=1694591500=0 For some reason LTO produces a FTBFS. Some more details at: * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051772 Thanks,

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

2023-09-12 Thread Mathieu Malaterre
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#1051772: Fwd: ia64 generates wrong-code with LTO

2023-09-12 Thread Mathieu Malaterre
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

2023-09-12 Thread Mathieu Malaterre
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#1051769: ia64 generates wrong-code with LTO

2023-09-12 Thread Mathieu Malaterre
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

2023-09-12 Thread Mathieu Malaterre
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.

  1   2   3   4   5   6   7   8   9   10   >