Bug#1000320: RM: ginkgocadx -- ROM; FTBS; dead upstream

Package: ftp.debian.org Severity: normal The package has been abandoned by upstream, requires old versions of libraries (vtk6), and forward porting is not an option, beause it would either require a rewrite of the renderer, or need another package that is not in Debian, namely wxWidgests >= 3.1

Bug#994453: linux-image-5.14.0-trunk-amd64: Kernel hangs at loading initramfs Ryzon based laptop

With 'mem_encrypt=off' the kernel boots fine, thanks for the pointer.  @Bastian: I'm not sure I understand why you downgraded the bug to important (I could have understood serious, grave). When the package is installed as is, one can't boot from this kernel, so the package should not got into

Bug#994453: linux-image-5.14.0-trunk-amd64: Kernel hangs at loading initramfs Ryzon based laptop

Package: src:linux Version: 5.14.3-1~exp1 Severity: critical Justification: breaks the whole system Dear Maintainer, booting the kernel on the computer as given in the description below hangs at the message "loading initial ramdisk" (no change of display mode, just the two initial boot message

Bug#994449: linux-image-5.14.0-trunk-amd64: Please enable CONFIG_UDMABUF

package: src:linux Version: 5.14.3-1~exp1 Severity: wishlist Dear Maintainer, UDMABUF is useful qemu, and required to get blob support, which in turn is needed by mesa/virgl to get support for ARB_buffer_storage and OpenGL 4.4 in the guest, and Vulkan support in the guest. Many thanks, Gert

Bug#972909: insighttoolkit4 ftbfs with python3.9

Hi Matthias, shouldn't the severity be "important" if the FTBFS is really related to python 3.9 until this version becomes the default python version? AFAICS 3.8 is still the default, here [1] it is not yet listed for bullseye, and ITK is build only against the default python version

Bug#944683: FTBFS: missing file /usr/lib/nodejs/axios/dist/axios.min.js

Package: orthanc-dicomweb Version: orthanc-dicomweb_1.0+dfsg-1 Severity: serious Justification: 4 Dear Maintainer, While I was trying to rebuild the package to use libgdcm-dev instead of libgdcm2-dev (change already pushed to the repo) the package failed to build for another reason with the

Bug#941664: RM: vtk6-doc,vtk6-examples -- NBS;not built anymore

Control: -1 -moreinfo The dependency was fixed with gdcm-3.0.4-2 (just uploaded) Thanks, Gert

Bug#941664: vtk6: was the removal of vtk6-examples and vtk6-doc intentional?

Control: reassign -1 ftp.debian.org Control: retitle -1 RM: vtk6-doc,vtk6-examples -- NBS;not built anymore Yes, the removal was intentional, since vtk6 is EOL upstream and will get phased out slowly, Best, Gert

Bug#943677: please package insighttoolkit5 (5.0 and 5.1 beta 1 are out)

Since I'm no longer working on anything related to image processing that would require ITK (or its dependent packages) I'm not very dedicated to package this, especially since packaging ITK really needs a lot of work an time. Especially the python bindings are a nuisance, it is quite difficult

Bug#937480: pymia: Python2 removal in sid/bullseye

Hi Sandro, NMU is fine with me, as nearly all the packages in debian-med the package is lowNMU, so no delay is necessary. Maybe next time consider to send the diff as merge request on salsa, it makes it easier to apply ;) Best, Gert

Bug#933414: ginkgocadx: Please rebuild against wxWidgets GTK 3 package

Am Mittwoch, den 31.07.2019, 12:58 +0200 schrieb Andreas Tille: > Control: tags -1 help > > Hi Gert, > > As far as I can see /usr/bin/vtkParseOGLExt exists only in vtk6. > > Could you please take over from here? sure, Gert

Bug#930277: unblock: gdcm_2.8.8-9

, with C++ libraries this +just doesn't work well enough. + + -- Gert Wollny Tue, 26 Mar 2019 22:07:17 +0100 + +gdcm (2.8.8-8) unstable; urgency=medium + + * d/libvtkgdcm2.8a.symbols: Attempt to fix symbols on mips/mipsel + + -- Gert Wollny Tue, 26 Mar 2019 19:35:20 +0100 + +gdcm (2.8.8-7

Bug#930275: unblock: dcmtk/3.6.4-2.1

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package dcmtk Upstream hasn't ported the package to use charls-2.yet, and the port tried by me resulted in serious regressions (as reported in #923433). This upload

Bug#923750: gdcm: FTBFS in buster/sid

I can't reproduce this in current sid. I've did a new upload with a minior unrelated fix incorporated by Gianfranco. If this passed on the build servers, I'm going to close the bug, best, Gert

Bug#919193: orthanc: FTBFS with dcmtk-3.6.4

Source: orthanc Version: 1.5.1+dfgs-1 Severity: serious Justification: 4 FTBFS but build before Dear Maintainer, The package FTBFS with dcmtk-3.6.4. The main issues: - unlock() now needs to be replaced by rdunlock() or wrunlock() depending on which *lock() method was called - Various

Bug#914817: [Debian-med-packaging] Bug#914817: camitk: FTBFS on i386

Am Sonntag, den 02.12.2018, 15:45 +0100 schrieb Mattia Rizzolo: > > Guess having this bug reassigned to vtk7, and Gert uploading a fixed > vtk7. Then camitk can be finally rebuilt on i386 as well. > I made an upload of vtk7 to exprimental, there mostly because I want to see whether QT can

Bug#911793: Bug#914483: Control: reassign -1 src:gdcm 2.8.7-2

Am Freitag, den 23.11.2018, 20:14 +0100 schrieb Mattia Rizzolo: > Hi, > > so, if you don't particularly mind, I'm happy to just take the least > and fix all the involved packages here, so src:vtk7 I just uploaded vtk7, I knew where to look because I did the changes that made the libraries go

Bug#911793: Control: reassign -1 src:gdcm 2.8.7-2

Hello, Am Freitag, den 23.11.2018, 16:30 +0100 schrieb Emmanuel Promayon: > Dear all > > Thank to Paul for your answers about the autoremoval and explanation > about the ABI problem. It seems that Adrian Bunk's triage message in > 909120 (added blocking bug(s) of 909120: 911793) did push the

Bug#906535: [Debian-med-packaging] Bug#906535: src:gdcm: Please support Python3

Hello Andreas, the python3 version is already in experimental, so you should be able to upload the new version of invesalius there and test it. I'll take care of the upload of the python3 supporting version of gdcm to sid when I'm back from my vacations. Best, Gert

Bug#897756: 897775 & 897756 *: ftbfs with GCC-8 (because of an error in insighttooklit4)

Hello Andreas, you marked these two bugs as found in insighttoolkit4/4.12.2-dfsg1-2, but they should actually have been merged with #897899 (maybe I did something wrong theer), a bug that was closed by exactly this version. Could you ellaborate why do you tagged these bugs like this? I just

Bug#902766: python3.7 causing python3-twisted failure?

Am Samstag, den 30.06.2018, 18:38 +0100 schrieb Neil Williams: > Do you have python3.7 installed? A similar error was reported against > python3-pexpect with python3.7: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902646 > > 'async' is a reserved keyword in Python 3.7. > Yes, because

Bug#902766: python3-twisted fails in the post-installation script when doing a first-time install

Package: python3-twisted Version: 18.4.0-1 Severity: serious Justification: Policy 5.2 (package remains in unconfigured state) Dear Maintainer, When doing a fresh install the post-installation script fails with Setting up python3-twisted (18.4.0-1) ... File

Bug#901635: itksnap: Crashes when opening example file

* > ITK-SNAP: Segmentation fault > BACKTRACE: > /usr/lib/snap-3.6.0/ITK- > SNAP(_Z24SegmentationFaultHandleri+0x144)[0xc5627d14] > /lib/x86_64-linux-gnu/libc.so.6(+0x34f00)[0x7f02a322ff00] >

Bug#895246: gconf: Intent to Adopt

Am Sonntag, den 13.05.2018, 15:18 -0400 schrieb Jeremy Bicha: > Respectfully, you are the only one complaining about gconf's > removal. I might not have been complaining here, but I'm also not that happy about some removals, and I don't understand the resistance to let someone adopt the package.

Bug#897775: itksnap: ftbfs with GCC-8

Control: reassign -1 src:insighttoolkit4 Control: merge -1 897899 more of the same

Bug#894371: gdcm FTBFS with openjdk-9

>As a workaround to let the poppler transition complete in raspbian I >whipped up a version of the package that forces openjdk-8. I intend to do the same, best Gert

Bug#896598: [Debian-med-packaging] Bug#896598: libglademm2.4: Intent to Adopt

Hi Adrian, while I generally agree that dropping all the gnome2 related libraries from Debian is not a good idea, in this case, where aeskulap is the only reverse dependency I'm aware of, I wonder whether is is really a good idea to put effort into providing this library package? Best, Gert

Bug#654839: retitle this to bring it up to date

Control: retitle -1 Paraview should use system VTK libraries Unfortunately, upstream comented on this that it would be difficult to use a seperate version of VTK because their development process just doesn't take care of this. See, e.g. this recent thread:

Bug#893770: libgnomecanvas will be adopted

Control: severity -1 important In light of #895249 I downgrade the bug severity. Autoremove will still happen since src:libgnomecanvas still has a few RC bugs. Best, Gert

Bug#895900: invesalius: Please port to python3

Package: invesalius Version: 3.1.1-3 Severity: important Dear Maintainer, Invesalius is the only package that depends on python-*gdcm, and gdcm is currently going to a transition to provide python3-*gdcm instead. This change is also imposed by moving forward with VTK for which we now also

Bug#895247: libgnomecanvas: Intent to Adopt

Am Donnerstag, den 12.04.2018, 23:32 +0300 schrieb Adrian Bunk: > On Thu, Apr 12, 2018 at 06:09:32PM +0100, Simon McVittie wrote: > > On Thu, 12 Apr 2018 at 15:03:11 +0200, Gert Wollny wrote: > > > Hi Adrian, > > > > (Adrian won't have seen this unless he's subscr

Bug#895247: libgnomecanvas: Intent to Adopt

Hi Adrian, as the maintainer of amide[1], a package that depends on libgnomecanvas I was also already thinking about adopting this package and libart- lgpl. In other words I'd happily join to co-maintain these two packages. Best, Gert

Bug#894371: gdcm FTBFS with openjdk-9

Control: forwarded -1 https://bugs.openjdk.java.net/browse/JDK-8200610 The bug is now visible upstream. but they closed it immediately. Unfortunately I can't comment on the bug, because I am unable to figure out how to open an account, but the suspected output path is definitely writeable (after

Bug#894371: gdcm FTBFS with openjdk-9

Control: reassign -1 src:openjdk-9 Control: affects -1 gdcm Control: tags -1 upstream The error message states: An exception has occurred in the compiler (9.0.4). Please file a bug against the Java compiler ... Hence, I reported the bug upstream and will update this report here when I

Bug#894462: paraview: edges are blotted [regression]

Am Freitag, den 30.03.2018, 18:01 +0200 schrieb Francesco Poli (wintermute): > Package: paraview > Version: 5.4.1+dfsg4-2 > Severity: grave > Justification: renders package unusable > > Hello paraview Debian package maintainers, > thanks for uploading a Debian revision that uses Qt5 rather than

Bug#893770: amide: Don't depend on libgnomecanvas

Am Donnerstag, den 22.03.2018, 00:40 -0400 schrieb Jeremy Bicha: > Source: amide > Version: 1.0.5-10 > Severity: serious > User: pkg-gnome-maintain...@lists.alioth.debian.org > Usertags: libgnomecanvas oldlibs > > As announced [1], we do not intend to release Debian 10 "Buster" with >

Bug#890891: systemd: PID1 getting stuck printing "systemd[1]: Time has been changed" continuously

Am Dienstag, den 20.02.2018, 15:31 +0100 schrieb Michael Biebl: > > > Kernel: Linux 4.15.1-cm-fx6-my (SMP w/4 CPU cores; PREEMPT) > > > Does this also happen with a Debian provided kernel? If so, which > kernel version is that? I haven't tried this so far, for that reason I was initially also

Bug#890891: systemd: PID1 getting stuck printing "systemd[1]: Time has been changed" continuously

Am Dienstag, den 20.02.2018, 14:09 +0100 schrieb Michael Biebl: > > As for the other cases, those are all hypothetical at this point, > right? > Yes, and that's why I did set this bug to severity normal and not higher. In the original bug report I just wanted to point out that there might be

Bug#890891: systemd: PID1 getting stuck printing "systemd[1]: Time has been changed" continuously

Am Dienstag, den 20.02.2018, 13:33 +0100 schrieb Michael Biebl: > Am > > > make it lock up in this loop, but if someone can spoof this kind of > > message and the system locks up because of this, wouldn't this be a > > typical DoS attack? > > How could an unprivileged user spoof such messages?

Bug#890891: systemd: PID1 getting stuck printing "systemd[1]: Time has been changed" continuously

Am Dienstag, den 20.02.2018, 12:56 +0100 schrieb Michael Biebl: > Am 20.02.2018 um 12:40 schrieb Gert Wollny: > > However, while upstream is certainly correct that a kernel bug is > > the trigger of the lockup, systemd should not hang on this, > > because if sending message

Bug#890891: systemd: PID1 getting stuck printing "systemd[1]: Time has been changed" continuously

Package: systemd Version: 236-3 Severity: normal Tags: upstream Dear Maintainer, on an 32 bit arm system when the RTC is set to a wrong time booting the system might fail because systemd gets stuck in a loop printing "systemd[1]: Time has been changed". The problem is known upstream and

Bug#888925: [Debian-med-packaging] Bug#888925: libminc FTBFS with netcdf 1:4.6.0-2: NetCDF: Attempt to use feature that was not turned on when netCDF was built

I'm on it Am Donnerstag, den 08.02.2018, 07:52 +0100 schrieb Sebastiaan Couwenberg: > On 02/08/2018 07:41 AM, Andreas Tille wrote: > > > libminc needs to fix their test or their usage of libnetcdf. > > > > Could you be more verbose what exactly needs to be changed? > > You can skip the test

Bug#885045: amide: Depends on old GNOME libraries

Hello Andreas Henriksson, thanks for digging into the code to see what's going on. I'll give the porting it a shot as soon as  can. Regarding gnome-canvas: are there already plans to drop that too, and what is actually the suggested replacement for it (The Gnome porting guide doesn't mention

Bug#885035: aeskulap: Please don't (build)-depend on gconfmm2.6

On 23.12.2017 13:55, Simon McVittie wrote: > On Sat, 23 Dec 2017 at 07:10:49 +0100, Andreas Tille wrote: >> When droping libgconfmm-2.6-dev from Build-Depends I get >> >> configure.ac:43: error: possibly undefined macro: AM_GCONF_SOURCE_2 >> >> What package provides this macro? > >

Bug#845032: valgrind: unusable on amd64: false-positive Illegal opcode at address ..

Hi, Trying the packaged version of darktable in unstable with the packaged version of valgrind (3.13.0-1) was not able to reproduce the error. However, I have seen a similar error with another program compiled with the usual Debian flags. With a self compiled version you probably have

Bug#873865: relion: Please add arm64

Hi Roland, You restricted the archs of that package? Was there any specific problem? Otherwise I'd enable all arch, upload, and see what sticks. Best, Gert

Bug#879194: [xfce4-session] Please add mate-screensaver to xflock4

Package: xfce4-session Version: 4.12.1-5 Severity: wishlist Tags: patch Dear maintainers, mate-screensaver is another alternative for a screensaver that would be a nice-have within the list that xflock4 can use. Please find a patch attached that updates d/patches/03 accordingly to add this

Bug#868383: amide: Please drop the (build-)dependency against gnome-vfs

amide pulls in gnome-vfs via libgnomeui and calls gnome-vfs also directly. Unless upstream is changing this I don't see that there is a good chance to remove this dependency. Best, Gert

Bug#853568: Nanopolish: gcc-7 issue solved, but immintrin.h missing on most architectures

Am Montag, den 18.09.2017, 13:54 +0200 schrieb Andreas Tille: > control: tags -1 help > > Hi, > > the gcc-7 issue of nanopolish described in latest upstream (0.8.1) > which is now in unstable but according to the build logs[1] on most > architecture the build fails with > > ... > cc -o

Bug#779655: [Debian-med-packaging] Bug#866434: invesalius: depends on obsolete python-imaging (replace with python3-pil or python-pil)

Patch pushed to packaging git, but someone should test it on real data. Best, Gert

Bug#874715: mesa: Games like Counter-Strike Global Offensive dont start after upgrading mesa to 17.2.0-2

Since you are using radeonsi you may have a conflict between the system libstdc++ and the one shipped with the steam runtime (Although this usually meant Steam doesn't start at all). cf: https://github.com/ValveSoftware/steam-for-linux/issues/3273

Bug#731433: dcmtk: iteration 9396u invokes undefined behavior [-Waggressive-loop-optimizations]

Control: tags -1 wontfix This warning is only relevant for 16 bit Jpegs and the comment in the source code states:  dcmjpeg/libijg16/jccolor.c 16-bit per pixel is used with lossless JPEG only, and we don't convert RGB to YCC in lossless mode. hence the code should never be run in this case.

Bug#853568: [Debian-med-packaging] Bug#853568: No idea how to fix abs arguments in nanopolish

Am Donnerstag, den 31.08.2017, 21:00 -0700 schrieb Walter Landry: > Andreas Tille wrote: > > Hi, > > > > to fix bug #853568 I tried a patch (gcc-7.patch) to fix abs() > > arguments > > in nanopolish[1] but I have no idea how to deal with this: > > > > ... > > g++ -o

Bug#873024: [Debian-med-packaging] Bug#873024: orthanc-wsi FTBFS with dcmtk 3.6.2

Control: tags -1 pending I've pushed the needed changes to the packaging git. Will check and upload tomorrow. Best, Gert

Bug#872542: qtwebkit-opensource-src: FTBFS on various release archs (i386, armel, armhf)

Source: qtwebkit-opensource-src Version: 5.9.1+dfsg-3 Severity: serious Justification: FTBFS but build before Dear Maintainer, As can be seen from the build status, the package fails to build on these release archs as well as some non-release archs.

Bug#871573: Castxml: error: invalid operands to binary expression

Control: severity -1 important Control: retitle -1 Invalid operands to binary expression with float128 Downgrading because the bug only affects source code that uses __float128, and there are packages that use castxml that are not affected by this problem. Best,  Gert 

Bug#872353: itksnap: FTBFS on i386: unconditionally expects SSE support

Package: itksnap Version: 3.6.0-1+b1 Severity: serious Tags: upstream Justification: FTBFS The package expects SSE but this is not enabled in the build environment. -- System Information: Debian Release: 9.1 APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable'),

Bug#872319: insightoolkit4: Re-enable python bindings

Package: insightoolkit4 Version: 4.12.0-dfsg1-2 Severity: normal Python bindings were (temporary) disabled because of a bug with Castxml #871573. This bug is here to track re-enabling these bindings -- Gert -- System Information: Debian Release: buster/sid APT prefers unstable-debug

Bug#871677: unblock regarding errors from castxml

Control: unblock -1 by 871573 Control: unblock 871282 by 871573  Will do an upload without Python bindings to avoid that the reverse dependencies get removed from testing. Another bug will be opened to track re-enabling the Python bindings, -- Gert

Bug#871282: libinsighttoolkit4.10: requires rebuild against GCC 7 and symbols/shlibs bump

Control: tags -1 -wontfix Control: block -1 by 871573 Control: block 871677 by 871573 I was getting to that, first I had to check #871573. Well, before that I thought I had it uploaded after gcc-7 became the default (I'm quite positive that I built it with an older version of gcc-7) and

Bug#724711: [Debian-med-packaging] Bug#724711: Bug#724711: insighttoolkit4: Drops architecture support

Am Donnerstag, den 10.08.2017, 08:33 +0100 schrieb Edmund Grimley Evans: > > As far as I can see all tests are disabled, failing tests means > > that > > the software has bugs, and I'm not sure whether we want to allow > > software with known bugs into the archives. > > Yes, but if the bug is in

Bug#724711: [Debian-med-packaging] Bug#724711: insighttoolkit4: Drops architecture support

> Ubuntu built 4.9.0, 4.10.0 and 4.10.1 on arm64: > > http://ports.ubuntu.com/ubuntu-ports/pool/universe/i/insighttoolkit4/ > > Though it looks like they may have ignored a few test failures to get > there: > > https://launchpad.net/ubuntu/+source/insighttoolkit4/+changelog As far as I can

Bug#871282: insighttoolkit4.10: requires rebuild against GCC 7 and symbols/shlibs bump

Control: tags -1 wontfix Version 4.12 is in unstable, was already build using gcc-7, and will soon transition to testing thereby removing v4.10 from the archives. Best, Gert

Bug#870806: Also fails with 2.1.22

Control: forwarded -1 https://dev.gnupg.org/T3331 The problem persists with 2.1.22 (This I only tested on the host system). There is also a related Gentoo bug: https://bugs.gentoo.org/show_bug.cgi?id=616096 I didn't try the workarounds described there though. Best, Gert

Bug#870806: gpg: Address family not supported by protocol if kernel doesn't support ipv6

Control: tags -1 + upstream This is definitely an upstream problem. In my normal maintenance of my Gentoo system I updated to gnupg 2.1.20, and it now also fails on the host system unless I load the ipv6 kernel module, so the problem was introduced somewhere between 2.1.15 and 2.1.20. I'll now

Bug#870806: gpg: Address family not supported by protocol if kernel doesn't support ipv6

pg: DBG: chan_3 -> [ 44 20 99 ...(982 byte(s) skipped) ] gpg: DBG: chan_3 -> [ 44 20 3d ...(982 byte(s) skipped) ] ... gpg: DBG: chan_3 -> END gpg: DBG: chan_3 <- INQUIRE KEYBLOCK_INFO gpg: DBG: chan_3 -> D pub::4096:1:02541A371530B71F:1395591437:1595083809::%0Auid

Bug#865781: orthanc-wsi FTBFS with libdcmtk-dev 3.6.1~20170228-2

Hi, I've pushed a patch that fixes this bug to the packaging repo. I didn't upload it though, because I saw that there was already a new version started for packaging. Best, Gert

Bug#834493: Bogus value for vtkWrappingJava_RUNTIME_LIBRARY_DIRS

Control: tags -1 wontfix Hello Mathieu, It is true that vtk originally installs the vtk6.jar files into the system library path that is indicated by vtkWrappingJava_RUNTIME_LIBRARY_DIRS, but since this does not conform to Debian policy, vtk6.jar is installed in /usr/share/java/ via

Bug#858260: Help needed for pandas bug: Could anybody verify the suspicion that tzdata might have some influence?

At second thought it might not be a bug in python-tz, but some undefined behavior that results from the pandas use of tz._utcoffset: >   tz = pytz.timezone('Asia/Tokyo') >   dt = datetime.datetime(2011,1,1) >   >   In[76]:  tz.utcoffset(dt) >   Out[76]: datetime.timedelta(0, 32400) > >   In

Bug#858260: Help needed for pandas bug: Could anybody verify the suspicion that tzdata might have some influence?

Hello, I did some digging: > Maybe it's a bug in python-tz? Most likely: Pandas uses this code to get the time offset for the local time in tslib.pyx: cpdef _get_utcoffset(tzinfo, obj): try: return tzinfo._utcoffset except AttributeError: return

Bug#853419: All fail because ITK/vcl doesn't know gcc7

reassign 853419 insighttoolkit4 reassign 853460 insighttoolkit4 reassign 853386 insighttoolkit4 merge 853454 853386 853460 853419 affects 853454 ginkgocadx itksnap elastix thanks

Bug#740296: SimpleITK

Am Samstag, den 28.01.2017, 15:48 + schrieb Ghislain Vaillant: > What is the status of your packaging effort for simpleitk? I never got past early tests to compile it. At that time I had a certain interest in the package but that veined. > > This bug was switched back to RFP in 2014.

Bug#838704: NMU: gnustep-dl2-postgresql-adaptor: fails to upgrade on a long grown system

and a tif file +that don't appear to be arch dependent. + + -- Gert Wollny <g...@debian.org> Sun, 08 Jan 2017 21:29:41 + + gnustep-dl2 (0.12.0-15) unstable; urgency=medium * debian/control: build depends on latest libgnustep-gui-dev diff -ruN gnustep-dl2-0.12.0/debian/files gnust

Bug#838704: gnustep-dl2-postgresql-adaptor: fails to upgrade on a long grown system

Hello,  in    d/gnustep-dl2-postgresql-adaptor.maintscript the first link uses "Current" which is already a symlink. When one replaces this with "0" the upgrade works fine. (I tested this with -9+nmu build on sid upgrading to the patched -15 which also failed here for the unpatched version.  I

Bug#845851: NMU: gnustep-sqlclient: switch to build depend on the metapackage default-libmysqlclient-dev

/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +gnustep-sqlclient (1.7.3-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Build depend on default-libmysqlclient-dev, Closes: #845851 + + -- Gert Wollny <g...@debian.org> Wed, 04 Jan 2017 09:27:59 + + gnustep-sqlclient (1

Bug#848590: llvm-toolchain-3.9: libclang-3.9-dev is missing cmake files

Source: llvm-toolchain-3.9 Version: 3.9.1-1 Severity: normal Dear Maintainers, For someone who is compiling using libclang-3.9-dev the current way to detect the installation location by using cmake is to use FIND_PACKAGE(LLVM), since here the required infomation about the root include directory

Bug#818505: sortmerna FTBFS on !x86

I think the best would be to restrict the package to amd64/i386/x32 and add a preinst script that checks for sse2 support (see below).  The only thing I wonder is whether there are legitimate cases wheer one should be able to install the package non-functional. Best,  Gert  #/bin/sh  set

Bug#846372: vtk6: FTBFS: /< ...

Hello Iain,  thanks for the patch and please go ahead with the upload. I will take care of adding it to the packaging git.  There is no use in forwarding this to upstream, because for them vtk-6 is EOL, they are now at vtk-7 which will only be packaged after stretch is released. Best, Gert 

Bug#844835: orthanc: FTBFS: build-dependency not installable: libssl-dev

Hi,  orthnac build depends on libdcmtk-dev, and this pulls in libssl1.0-dev (since dcmtk (a) does not yet support openssl-1.1 and (b) it is used by programs that require QT which conflicts with openssl-1.1).  libssl1.0-dev conflicts with libssl-dev, and hence the build failure.  The solution is

Bug#796246: libc recently more aggressive about pthread locks in stable ?

Am Dienstag, den 15.11.2016, 18:06 +0200 schrieb Adrian Bunk: >  > > Unfortunately, in current unstable with thread sanitizer one might > > get #796246 (at least I had this). > > Does "-fsanitize=thread -no-pie" work for you? Indeed, that fixed the problem with g++-6.2 (g++-5.4 doesn't has this

Bug#844140: mia: FTBFS: lxml.etree.XMLSyntaxError: None

I don't think that the bug is related to threading/locking failures within mia, i.e. compiling the package by using g++-5* and  -fsanitize=thread doesn't show any locking problems (specifically no double un-locking of a mutex).  Specifically, the error hints at     ./mia-3dmaskseeded

Bug#796246: RES: FATAL: ThreadSanitizer: ... (confirmed with g++-6.2 but doesn't show up with g++-5.4)

I've can confirm the bug with g++-6 on Debian (unstable as of 2016/11/14).  libtsan0: 6.2.0-13 g++-6: 6.2.0-13 When I compile the same software with g++-5 (5.4.1-3) in Debian or on Gentoo using g++-5.4.0 the error does not occur. In all cases the tsan library is libtsan.so.0.0.0.  I've

Bug#842796: libc recently more aggressive about pthread locks in stable ?

Am Sonntag, den 06.11.2016, 01:12 -0200 schrieb Henrique de Moraes Holschuh: >  >  >  > Unfortunately, when hardware lock elision support was added to glibc > upstream, libpthreads was *not* changed to properly assert() this > forbidden condition on the non-hardware-elision codepaths.  Such an >

Bug#828308: downgrade severity, because the bug is not RC anymore

Control: severity important Hello Mathieu, thanks for the patch, but since itksnap uses gdcm, and also QT5, and the latter uses dlload to pull in openssl-1.0 dynamically (and this will not change for stretch), gdcm will also be build against the older version of openssl. Hence I will not apply

Bug#828529: r-cran-openssl: FTBFS with openssl 1.1.0

Hello,  Am Donnerstag, den 27.10.2016, 08:56 +0200 schrieb Andreas Tille: > Hi, > > I can confirm this problem when trying to build against openssl 1.1: > > ... > gcc -std=gnu99 -I/usr/share/R/include -DNDEBUG  -fpic  -g -O2 > -fdebug-prefix-map=/build/r-base-3.3.1.20161024=.

Bug#838808: gtkglextmm: FTBFS: thread.h:140:18: error: variable or field 'thread_init' declared void

Control: tags -1 pending Hello Adrian, thanks for the patch but it is actually easier (because less intrusive) to add -DGLIBMM_DISABLE_DEPRECATED in debian/rules. I will adopt the package and prepare an upload shortly. Best, Gert signature.asc Description: OpenPGP digital signature

Bug#821731: ctk: FTBFS: ctkDICOMUtil.cpp:33:3: error: 'log4cplus' has not been declared

Hi, Some time ago there was some activity with an upstream issue [1] about making the package ready for proper inclusion into Debian. Unfortunately upstream doesn't properly document dependencies and seems to have the habit to use locally patched versions of these dependencies if they feel like

Bug#811818: crrcsim: FTBFS with GCC 6: no match for

that a newline was the intended output after the according message. Author: Gert Wollny <gw.foss...@gmail.com> Forwarded:no Debian-Bug: https://bugs.debian.org/811818 --- a/src/mod_video/crrc_animation.cpp +++ b/src/mod_video/crrc_animation.cpp @@ -84,7 +84,7 @@ else {

Bug#836592: jessie-pu: package gdcm/2.4.4-3

As far as I can tell, the problem isn't the documentation, it's: make[3]: *** No rule to make target '/usr/lib/jvm/default-java/jre/lib/ppc64/libjawt.so', needed by 'bin/libvtkgdcmJava.so'. Stop. Agreed, I didn't see this because I was scanning for "error:". The compilation failure is

Bug#836592: jessie-pu: package gdcm/2.4.4-3

On 09.09.2016 03:03, Adam D. Barratt wrote: On Mon, 2016-09-05 at 22:32 +0100, Adam D. Barratt wrote: Unfortunately it FTBFS on ppc64el; see https://buildd.debian.org/status/fetch.php?pkg=gdcm=ppc64el=2.4.4-3%2Bdeb8u1=1473373168 Hmm, this bug seem to be completely unrelated to the patch,

Bug#836592: jessie-pu: package gdcm/2.4.4-3

+0100 @@ -1,3 +1,11 @@ +gdcm (2.4.4-3+deb8u1) jessie-proposed-updates; urgency=medium + + * add patches: +- d/p/CVE-2015-8396.patch: fix according security vunerability +- d/p/CVE-2015-8397.patch: fix according security vunerability + + -- Gert Wollny <gw.foss...@gmail.com> Sat,

Bug#835761: insighttoolkit4: FTBFS: itkTriangleHelperPython.cpp:5836:65: error: no matching function for call ...

Control: tags -1 pending  Upstream provided all the required patches, test building now before uploading. 

Bug#835761: insighttoolkit4: FTBFS: itkTriangleHelperPython.cpp:5836:65: error: no matching function for call to

Control: forwarded -1 https://issues.itk.org/jira/browse/ITK-3466 This specific compilation error is fixed in the svn, however, other problems with the Python bindings result in other FTBFS, i.e. various tests are failing.  Best,  Gert   

Bug#832556: RFS: wvstreams/4.6.1-10 [QA, RC]

Package: sponsorship-requests Severity: important Dear mentors,   I am looking for a sponsor for the package "wvstreams"  * Package name: wvstreams    Version : 4.6.1-10    Upstream Author : Net Integration Technologies Inc. et al.   * URL :

Bug#832138: librostlab-blast: The package should compile without forcing the older -std=c++03

Source: librostlab-blast Version: 1.0.1-7 Severity: wishlist The package should either be refactored to work around #829604 in g++, or we have to wait thill that bug is fixed. Best, Gert -- System Information: Debian Release: stretch/sid APT prefers unstable-debug APT policy: (500,

Bug#829604: Bug reported upstream

forwarded 829604 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71975

Bug#831809: g++-5: exceptions thrown from callback with va_list not caugth on at least armhf and powerpc

Package: g++-5 Version: 5.4.0-6 Severity: important Tags: upstream Dear Maintainer, in the attached program the exception is not caught on armhf and powerpc. The compilation command line is g++ test_tiff_throw.cc -o test-tiff-throw -ltiff I've tested the compilers: powerpc: g++ (Debian

Bug#830827: RFS: wvstreams/4.6.1-9 [QA, RC]

Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for the package "wvstreams"  * Package name: wvstreams    Version : 4.6.1-9    Upstream Author : Net Integration Technologies Inc. et al.   * URL :

Bug#830595: closed by Gianfranco Costamagna <locutusofb...@debian.org> (Re: Bug#830595: RFS: fracplanet/0.4.0-4 [QA, RC])

Hello Gianfranco,  thanks for sponsoring.  > you also bumped std-version, I added the entry in changelog,  Well, since "cme fix dpkg-control" always bumps to the latest version, I didn't add this explicitly ...  Best,  Gert 

Bug#830595: RFS: fracplanet/0.4.0-4 [QA, RC]

Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for the package "fracplanet"  * Package name: fracplanet    Version : 0.4.0-4    Upstream Author : Tim Day  * URL : 

  1   2   3   >