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#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#1056953: marked as pending in gdcm

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:

Bug#1054696: marked as pending in gdcm

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:

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#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#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#1042246: marked as pending in gdcm

Control: tag -1 pending Hello, Bug #1042246 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:

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#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#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#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#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#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#1025203: r-cran-glmmtmb: FTBFS on mipsel

On Fri, Dec 9, 2022 at 10:29 AM Andreas Tille wrote: > > Hi Mathieu, > > Am Tue, Dec 06, 2022 at 08:38:43AM +0100 schrieb Mathieu Malaterre: > > I do not have a clean answer to this, but in my experience it is > > getting more and more difficult to compile anything o

Bug#1025203: r-cran-glmmtmb: FTBFS on mipsel

I do not have a clean answer to this, but in my experience it is getting more and more difficult to compile anything on mipsel with g++-12. The default option `-g -O2` seems to imply `take as much memory as you want to get things to compile` so this end up crossing the 2GB hard-limit. For example

Bug#1021857: CMake Error at /usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake:1598 (message):

what I would do: $ cd obj-* $ DESTDIR=/tmp/sylvestre make install $ find /tmp/sylvestre -name mlir-tblgen output1 $ grep mlir-tblgen /tmp/sylvestre/usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake output2 -> verify output1 & output2 matches > > Le 28/11/2022 à 12:07, Mathieu Mal

Bug#1021857: CMake Error at /usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake:1598 (message):

Control: found 1021857 1:14.0.6-2 -- Found LibXml2: /usr/lib/x86_64-linux-gnux32/libxml2.so (found version "2.9.14") CMake Error at /usr/lib/llvm-14/lib/cmake/llvm/LLVMExports.cmake:1598 (message): The imported target "mlir-tblgen" references the file "/usr/lib/llvm-14/bin/mlir-tblgen"

Bug#1021117:

Control: fixed -1 1:15.0.2-2~exp4 Control: fixed -1 1:15.0.3-1 Ok nevermind I see that the issue is still in riscv64. But I do not understand why I see in llvm-14...

Bug#1021117: Fixed since 1:15.0.2-2~exp4

> Fixed since 1:15.0.2-2~exp4 Seems it came back: * https://buildd.debian.org/status/fetch.php?pkg=openvdb=riscv64=10.0.0-6=1669407006=0 CMake Error at /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake:1631 (message): The imported target "mlir-tblgen" references the file

Bug#1013156: gdcm: vtk[6,7] removal

On Wed, Oct 26, 2022 at 11:19 AM Andreas Tille wrote: > > Hi Mathieu, > > Am Wed, Oct 26, 2022 at 11:16:30AM +0200 schrieb Mathieu Malaterre: > > > > https://salsa.debian.org/med-team/gdcm/-/commits/debian/experimental/ > > > > > > Ups, sorry f

Bug#1013156: gdcm: vtk[6,7] removal

On Wed, Oct 26, 2022 at 10:35 AM Andreas Tille wrote: > > Hi Mathieu, > > Am Wed, Oct 26, 2022 at 08:10:42AM +0200 schrieb Mathieu Malaterre: > > On Wed, Oct 26, 2022 at 7:53 AM Andreas Tille wrote: > > > > > > Hi, > > > > > > in the bu

Bug#1013156: gdcm: vtk[6,7] removal

On Wed, Oct 26, 2022 at 7:53 AM Andreas Tille wrote: > > Hi, > > in the bug log there is some discussion to drop C# and Java VTK > bindings. This would mean to drop the packages libvtkgdcm-cil and > libvtkgdcm-java. I'm perfectly fine with this and I just pushed > a change in d/control where I

Bug#1021165: Gcc 13 requires some (older) glibc headers to be fixed up .

For reference: malat@amdahl /tmp % apt-cache policy libc6-dev libc6-dev: Installed: 2.35-1 Candidate: 2.35-1 Version table: *** 2.35-1 500 500 https://deb.debian.org/debian sid/main armhf Packages 100 /var/lib/dpkg/status

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

Source: gcc-snapshot Version: 1:20220920-1 Severity: grave Per original reference: --- Comment #1 from Andrew Pinski --- Is this a packaging issue? > ignoring nonexistent directory > "/usr/lib/gcc-snapshot/lib/gcc/arm-linux-gnueabihf/13/include-fixed/arm-linux-gnueabihf" ignoring nonexistent

Bug#1017752: Do you see any chance to fix the "virtual memory exhausted" for nheko on mipsel VM

On Wed, Sep 28, 2022 at 10:06 PM Andreas Tille wrote: > > Hi mips porters, > > in bug #1017752 a > >FTBFS on mipsel: virtual memory exhausted: Cannot allocate memory > > is reported. This remains for the new upstream version I've just > uploaded to experimental[1]. Do you see any chance to

Bug#1017752: Do you see any chance to fix the "virtual memory exhausted" for nheko on mipsel VM

On Thu, Sep 29, 2022 at 9:14 AM Mathieu Malaterre wrote: > > On Wed, Sep 28, 2022 at 10:06 PM Andreas Tille wrote: > > > > Hi mips porters, > > > > in bug #1017752 a > > > >FTBFS on mipsel: virtual memory exhausted: Cannot allocate memory >

Bug#1020642: webkit2gtk: FTBFS on mipsel: virtual memory exhausted

On Sat, Sep 24, 2022 at 7:42 PM Simon McVittie wrote: > webkit2gtk repeatedly failed to compile on the mipsel buildds: Here is the trick I used on those arches for openvdb: [...] # Disable optimization on mipsel because the compiler is running out of memory # see #847752 / #879636 ifneq

Bug#997080: marked as pending in openvdb

Control: tag -1 pending Hello, Bug #997080 in openvdb 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:

Bug#997080: openvdb: FTBFS: help2man: can't get `--help' info from ./debian/tmp/usr/bin/vdb_view

Control: tags -1 - patch Control: block -1 by 1001457 [Written communication is hard] It should be noticed that I did communicate privately with Tobias and I mentioned multiple times both issues are linked. > I was debugging into this, and IMHO this is not a compiler issue, but a > packaging

Bug#1018015: src:ilmbase will be removed

Control: severity -1 normal I think this is acceptable as-is since imath does Provides: libilmbase-dev. Reducing severity. Sorry for the noise.

Bug#1018013: src:ilmbase will be removed

Control: severity -1 normal I think this is acceptable as-is since imath does Provides: libilmbase-dev. Reducing severity. Sorry for the noise.

Bug#1018015: src:ilmbase will be removed

Source: openimageio Version: 2.3.18.0+dfsg-3 Severity: serious I am planning to remove ilmbase now that openexr 3.1.5 has migrated to testing. Please replace dependency from libilmbase-dev into libimath-dev. There should not be any other difference.

Bug#1018013: src:ilmbase will be removed

Source: nvidia-texture-tools Version: 2.0.8-1+dfsg-8.2 Severity: serious I am planning to remove ilmbase now that openexr 3.1.5 has migrated to testing. Please replace dependency from libilmbase-dev into libimath-dev. There should not be any other difference.

Bug#997080: openvdb / clang

> This bug is blocking openimageio, which blocks blender. Can this be > fixed, is it still not reproducible? I naively thought I could switch to clang instead of gcc to workaround the issue. It turns out that the Debian tools do not handle object files generated by clang: [...] dh_fixperms

Bug#1017547: openexr-viewers FTBFS with openexr 3.1.5

Hi Pino ! Since openexr-viewers does not build anymore against openexr 3.x and it is dead upstream, do you want me to fill in a RM for you ? Thanks

Bug#1017512: freeimage FTBFS with openexr 3.1.5

Control: tags -1 patch See attached. Thanks From f40352706436a15d09767011ec9c9c0df33a57a1 Mon Sep 17 00:00:00 2001 From: Mathieu Malaterre Date: Wed, 17 Aug 2022 15:04:22 +0200 Subject: [PATCH] d/patches: Refresh patch to handle openexr 3.x split --- debian/patches/Disable-vendored

Bug#1017495: Missing Breaks on libopenexr-dev ?

Dear imath maintainer; I believe there is something missing for a proper upgrade path of imath (*). Would it be possible to add a Breaks: libopenexr-dev (<= 2.5.7-2) % sudo apt install libimath-dev [...] (Reading database ... 189739 files and directories currently installed.) Preparing to

Bug#1017495: libopenexr-dev: trying to overwrite '/usr/include/OpenEXR/Iex.h', which is also in package libilmbase-dev

On Wed, Aug 17, 2022 at 2:24 AM Christian Marillat wrote: > > Package: libopenexr-dev > Version: 2.5.7-1 > Severity: serious > > Dear Maintainer, > > I can't upgrade this package. > > , > | Preconfiguring packages ... > | (Reading database ... 325236 files and directories currently

Bug#1009308:

Control: tags -1 wontfix Control: tags -1 - patch Control: severity -1 normal I am not sure I can integrate your patch since libimath-dev does Provide: libilmbase-dev. Also: % sudo apt install libimath-dev [...] The following packages will be REMOVED: libilmbase-dev The following NEW packages

Bug#1016331: marked as pending in gdcm

Control: tag -1 pending Hello, Bug #1016331 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:

Bug#964654: kcov: FTBFS: ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libbfd.a(plugin.o): undefined reference to symbol 'dlclose@@GLIBC_2.2.5'

Dear Alessandro, Any chance you could merge the suggested MR ? Thanks

Bug#1014091: armhf: gcc has wrong configuration

Hi Richard ! On Thu, Jun 30, 2022 at 4:45 PM Richard Earnshaw wrote: > > I think the problem is valgrind's Makefiles are passing -mcpu=cortex-a8 > to the compiler. Cortex-a8 has Neon and the compiler now makes use of that. > > On the subject of the configuration of GCC > >

Bug#928224: patch

valgrind should apply the following patch: sed -i -e 's/cortex-a8/generic-armv7-a+vfpv3-d16/g' Makefile.all.am

Bug#928224: Valgrind is broken on armhf

% gdb "/usr/libexec/valgrind/memcheck-arm-linux" GNU gdb (Debian 12.1-2) 12.1 Copyright (C) 2022 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

Bug#1013258: autoreconf: error: /usr/bin/autoconf failed with exit status: 1

Control: tags -1 wontfix On Mon, Jun 20, 2022 at 1:39 PM Andreas Tille wrote: > > Am Mon, Jun 20, 2022 at 10:38:12AM +0200 schrieb Mathieu Malaterre: > > Source: openslide > > Severity: important > > Tags: ftbfs > > > > Dear Maintainer, > > > >

Bug#1008798: gdcm: FTBFS on s390x

Control: fixed -1 3.0.12-1 Fixed in latest upload

Bug#1007234: Test suite fails on all but amd64 arches

Bryan, On Tue, Mar 29, 2022 at 1:45 PM Mathieu Malaterre wrote: > > Bryan, > > On Sat, Mar 26, 2022 at 2:00 AM Bryan Henderson > wrote: > > > > I don't know familiar you are with debuggers, C, or C arithmetic, so I'm > > attaching a diagnostic version of the pr

Bug#1007234: Test suite fails on all but amd64 arches

Bryan, On Sat, Mar 26, 2022 at 2:00 AM Bryan Henderson wrote: > > I don't know familiar you are with debuggers, C, or C arithmetic, so I'm > attaching a diagnostic version of the program and will also explain where I > think the problem lies in case you want to investigate on your own. > > If

Bug#1007234: Test suite fails on all but amd64 arches

For some reason I never got your answer. So I've subscribed to `1007...@bugs.debian.org` > I'm sure this is easy to diagnose for someone who can reproduce it. I've followed the instructions from: * https://wiki.debian.org/RISC-V#debootstrap I have now a RISCV-64 arch on my amd64 machine. Now:

Bug#1007234: Test suite fails on all but amd64 arches

Dear Bryan, Could you comment on the buildds failures at: * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007234 For example on ppc64el (little endian system): * https://buildd.debian.org/status/fetch.php?pkg=netpbm-free=ppc64el=2%3A10.97.00-1=1647179729=0 [...] == palm-roundtrip.test

Bug#1007167: Acknowledgement (_clock_system.h:34:27: error: using-declaration for non-member at class scope)

For reference: * https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/synfig.html

Bug#1007167: _clock_system.h:34:27: error: using-declaration for non-member at class scope

Source: synfix Version: 1.4.0+dfsg-2.1 Severity: grave I cannot compile synfig on sid/amd64. It fails with a cryptic c++ compilation error: libtool: compile: g++ -DHAVE_CONFIG_H -I../.. -I../../src -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include -I/usr/include/glibmm-2.4

Bug#1002061: libjxl-dev: ships files already in libhwy-dev

Control: fixed -1 0.6.1+ds-6 jpeg-xl (0.6.1+ds-6) experimental; urgency=medium [...] * d/rules: Start using the system installed hwy Thanks

Bug#999608: marked as pending in epubcheck

Control: tag -1 pending Hello, Bug #999608 in epubcheck 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:

Bug#999900: epubcheck: java.lang.StackOverflowError

Control: severity -1 important Since this bug affects a limited set of architecture, I do not believe severity can be set to `grave` (please correct if wrong). On amd64: ``` % epubcheck /usr/share/doc/debian-policy/policy.epub Validating using EPUB version 3.2 rules. ERROR(PKG-006):

Bug#1003933: w3c-sgml-lib: catalogs for MathML 2.0 are incomplete

Control: forwarded -1 https://github.com/w3c/markup-validator/issues/66 Control: tags -1 upstream As discussed in upstream bug tracker there is something wrong with the namespace "TR"...

Bug#1004067: closed by Debian FTP Masters (reply to Mathieu Malaterre ) (Bug#1004067: fixed in imath 3.1.3-10)

Hi all, On Sun, Jan 23, 2022 at 10:45 PM Matteo F. Vescovi wrote: > > Version: 3.1.3-10 > > On 2022-01-23 at 18:42 (+01), Matteo F. Vescovi wrote: > > The build still ftbfs. > > Gosh, at the time of writing was still using -9 revision and it failed. > Now, I've tested -10 revision of imath and

Bug#1002216: jpylyzer: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13

Control: fixed -1 2.0.1-1

Bug#1003218: Processed: your mail

Control: found -1 0.15.0-4 See: * https://buildd.debian.org/status/fetch.php?pkg=highway=armhf=0.15.0-4=1641752465=0

Bug#984276: opencolorio: ftbfs with GCC-11

Control: upstream confirmed fixed-upstream https://github.com/AcademySoftwareFoundation/OpenColorIO/commit/2f87cca2e129471f57df0c3a8a3adc0c73a4811c.patch

Bug#1001136: Possible miscompilation triggered by -fvisibility=hidden

See: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103629

Bug#997080: openvdb: FTBFS: help2man: can't get `--help' info from ./debian/tmp/usr/bin/vdb_view

Control: notfound -1 8.1.0-3 Control: tags -1 wontfix I cannot reproduce the issue: * On my local sid schroot, * On barriere.d.o * The exp. buildds are working as expected: ** https://buildd.debian.org/status/fetch.php?pkg=openvdb=amd64=9.0.0-2=1638489598=0

Bug#1000220: marked as pending in dcmtk

Control: tag -1 pending Hello, Bug #1000220 in dcmtk 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:

Bug#1000222: marked as pending in orthanc

Control: tag -1 pending Hello, Bug #1000222 in orthanc 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:

Bug#1000222: orthanc force gnuc++11 reason

Control: tags -1 patch Could someone confirm; this is an acceptable patch ? thanks donotforcec++11.patch Description: Binary data

Bug#1000222: orthanc force gnuc++11 reason

Control: tags -1 upstream confirmed Control: affects -1 dcmtk/3.6.6-2 For some reason orthanc forces the uses of gnuc++11 gcc compiler flag. Unless there is a good reason, I would simply suggest to remove this hard-coded value: % grep -r gnu++11 .

Bug#1000220: /usr/include/dcmtk/dcmsr/dsrtlist.h:303:30: error: cannot convert 'std::__cxx11::list >::iterator'

Control: tags -1 patch Here is one possible fix: https://github.com/DCMTK/dcmtk/pull/45 Thanks for consideration.

Bug#1000220: /usr/include/dcmtk/dcmsr/dsrtlist.h:303:30: error: cannot convert 'std::__cxx11::list >::iterator'

Control: tags -1 upstream Control: found -1 3.6.6-2 Dear DCMTK team, The DCMTK package 3.6.6-2 currently in Debian/sid fails to build because of (*). Could you please confirm that DCMTK_ENABLE_STL:BOOL=ON is an acceptable option for releasing DCMTK in Debian, and that the toolkit codebase should

Bug#1000221: wontfix

Control: tags -1 wontfix See bug#1000320 ... error: ‘STATUS_N_PRINT_BSB_Fail_PrintQueueFull’ was not declared in this scope; did you mean ‘STATUS_N_PRINT_BFB_Fail_PrintQueueFull’? ... For reference upstream refactored the whole DIMSE status codes at:

Bug#996820: marked as pending in gdcm

Control: tag -1 pending Hello, Bug #996820 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:

Bug#989296: [RFR] libgdcm-dev/3.0.8-2 (to close #989296)

Salut Étienne, On Fri, Jul 30, 2021 at 9:21 PM Étienne Mollier wrote: > > Hi Mathieu, > > Mathieu Malaterre, on 2021-07-30: > > Hi all, > > > > I've reviewed commit 92bee7344b774b45b66185ed17b040f12fe31c43. I've > > not verified it fixes the OP symp

Bug#989296: [RFR] libgdcm-dev/3.0.8-2 (to close #989296)

Hi all, I've reviewed commit 92bee7344b774b45b66185ed17b040f12fe31c43. I've not verified it fixes the OP symptoms, but this is the right fix IMHO. I've also reviewed cddfeab955f486fba72745b66130480dfec1a2b6 and this is not the right fix, sorry. See #711214 for more context. 2cts On Fri, Jul

Bug#976906: Possible lex issue for ppc64el (Was: Bug#976906: libpll: FTBFS on ppc64el: lex_utree.l:22:10: fatal error: parse_utree.h: No such file or directory)

"make -j160" that would be my guess :) remove parallel from the dh option, and try again (fixes symptoms) On Thu, Dec 10, 2020 at 10:49 AM Andreas Tille wrote: > > Control: tags -1 help > > Hi, > > I tried to investigate the situation below and my guess is that lex has > somehow problems to

Bug#973723:

Control: tags -1 fixed-upstream http://git.dcmtk.org/?p=dcmtk.git;a=commit;h=46b4b4c

Bug#974544: marked as pending in charls

Control: tag -1 pending Hello, Bug #974544 in charls 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:

Bug#974544: libcharls-dev needs Breaks+Replaces: libdcmtk-dev (<< 3.6.5-1~)

Control: retitle -1 libcharls-dev needs Breaks: libdcmtk-dev (<< 3.6.5-1~) On Thu, Nov 12, 2020 at 8:13 AM Adrian Bunk wrote: > > On Thu, Nov 12, 2020 at 08:09:11AM +0100, Mathieu Malaterre wrote: > > On Thu, Nov 12, 2020 at 8:06 AM Adrian Bunk wrote: > > &g

Bug#974544: libcharls-dev needs Breaks+Replaces: libdcmtk-dev (<< 3.6.5-1~)

On Thu, Nov 12, 2020 at 8:06 AM Adrian Bunk wrote: > > Control: reopen -1 > > On Thu, Nov 12, 2020 at 08:02:07AM +0100, Mathieu Malaterre wrote: > > Control: fixed -1 2.1.0+dfsg-7 > > > > https://salsa.debian.org/med-team/charls/-/blob/debian/2.1.0+dfsg-7/debian/c

Bug#974544: libcharls-dev needs Breaks+Replaces: libdcmtk-dev (<< 3.6.5-1~)

Control: fixed -1 2.1.0+dfsg-7 https://salsa.debian.org/med-team/charls/-/blob/debian/2.1.0+dfsg-7/debian/control#L22 dcmtk 3.6.5 ships a convenient copy of CharLS with SOVERSION=1, while libcharls-dev is SOVERSION=2, so I'll not add the Replaces.

Bug#973723: libcharls-dev ships libcharls.so which is also in libdcmtk-dev

Hi Gert, On Wed, Nov 4, 2020 at 10:06 AM Mathieu Malaterre wrote: > > Control: tags -1 patch upstream confirmed > > On Wed, Nov 4, 2020 at 9:13 AM Mathieu Malaterre wrote: > > > > Control: reassign -1 src:dcmtk > > > > > trying to overwrite '/usr/li

Bug#972867: marked as pending in charls

Control: tag -1 pending Hello, Bug #972867 in charls 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:

Bug#973723: libcharls-dev ships libcharls.so which is also in libdcmtk-dev

Control: tags -1 patch upstream confirmed On Wed, Nov 4, 2020 at 9:13 AM Mathieu Malaterre wrote: > > Control: reassign -1 src:dcmtk > > > trying to overwrite '/usr/lib/x86_64-linux-gnu/libcharls.so', which is also > > in package libdcmtk-dev 3.6.4-2.1+b1 > > Dear

Bug#973723: libcharls-dev ships libcharls.so which is also in libdcmtk-dev

Control: reassign -1 src:dcmtk > trying to overwrite '/usr/lib/x86_64-linux-gnu/libcharls.so', which is also > in package libdcmtk-dev 3.6.4-2.1+b1 Dear dcmtk maintainer, Would it make sense to rename the customized charls included as a convenient copy in dcmtk as 'libdcmcharls.so' instead of

Bug#972867: Patch

Case sensitive systems are affected by 2.1.0 release. diff --git a/CMake/FindCharLS.cmake b/CMake/FindCharLS.cmake index 8f6bf19..b253a61 100644 --- a/CMake/FindCharLS.cmake +++ b/CMake/FindCharLS.cmake @@ -6,7 +6,7 @@ # For details see the accompanying COPYING-CMAKE-SCRIPTS file. #

Bug#972430: nvidia-legacy-340xx-driver 340.108-6~bpo10+1

Control: found -1 340.108-6~bpo10+1 Would be nice to have a bpo of -8 at some point. Thanks very much ! This is my only option as nouveau is unstable on this system.

Bug#972867: CharLS should have changed its SOVERSION

Control: tags -1 upstream For details: https://github.com/team-charls/charls/issues/81

Bug#970271: marked as pending in blender

Control: tag -1 pending Hello, Bug #970271 in blender 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:

Bug#966670: marked as pending in pixelmed

Control: tag -1 pending Hello, Bug #966670 in pixelmed 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:

Bug#963444: update Google Guava dependency to v24.0

Control: tags -1 fixed-upstream patch confirmed See: https://github.com/w3c/epubcheck/pull/833#issuecomment-367052775

Bug#951829: don't explicitly request python 3.7 for the build

Control: severity -1 normal On Fri, Mar 27, 2020 at 12:57 PM Emilio Pozuelo Monfort wrote: > > Control: reopen -1 7.0.0-1 > Control: retitle -1 python3-openvdb: build against the default python3 version > > On Mon, 24 Feb 2020 11:10:49 +0100 Mathieu Malaterre wrote: > > Con

  1   2   3   4   5   6   7   >