Bug#936207: biosig4c++: Python2 removal in sid/bullseye

on the system, in which case one needs to do only pip install numpy pkgconfig pip install Biosig-1.9.1.tar.gz where Biosig-1.9.1.tar.gz is just built in python/dist with this command: cd python && make release I provide the sources also here https://pub.ist.ac.at/~schloegl/biosig/prerele

Bug#925643: ignore error in missing symbol

The severity of this bug should be changed to minor for the following reason(s): The symbol being lost is not from the API of biosig, and no application using libbiosig could have used it in a meanigful way. The missing symbol

Bug#910686: Pymol 2.2.0 sources available from github

Package: pymol    Version: 2.2.0 Severity: wishlist The open source version of Pymol 2.2.0 is available from here now:    https://github.com/schrodinger/pymol-open-source    https://github.com/schrodinger/pymol-open-source/releases It seems, debian/watch file is not aware of this new

Bug#783653: pymol: Segmentation fault immediately after loading pdb

I confirm that this bug occurs under some specific conditions. For testing I used this file http://www.pdb.org/pdb/files/1bl8.pdb which works fine on a local installation of pymol (Debian/Stretch). It works also when connecting to OSX (through xquartz 2.7.12 with "ssh -Y " to a Debian/Jessie

Bug#866115: [Pkg-monitoring-maintainers] Bug#866115: dist-upgrade to Stretch broke ganglia-web

On 2017-06-27 15:15, Daniel Pocock wrote: > > > On 27/06/17 14:58, Alois Schloegl wrote: >> Package: ganglia-web >> >> >> The following ganglia packages are installed: >> >> ganglia:~# dpkg -l|grep ganglia >> ii ganglia-modules-linux

Bug#866115: dist-upgrade to Stretch broke ganglia-web

Package: ganglia-web The following ganglia packages are installed: ganglia:~# dpkg -l|grep ganglia ii ganglia-modules-linux 1.3.6-2 amd64Ganglia extra modules for Linux (IO, filesystems, multicpu) ii ganglia-monitor 3.6.0-7+b1

Bug#857121: biosig4c++ FTBFS on architectures where char is unsigned

This bug was fixed upstream in commit 8e7c3d7e485e1d3af3f3094641282274424b7385 Attaches is the corresponding patch. Thanks for consideration, Alois commit 8e7c3d7e485e1d3af3f3094641282274424b7385 Author: Christoph Schmidt-Hieber Date: Sat Dec 10

Bug#847309: libthrust-dev: cub::DeviceReduce::Min causes segmentation fault

Package: libthrust-dev Version: 1.7.0 Severity: normal Dear Maintainer, I tried to compile and run relion 2 beta with cuda enable. nvidia-cuda-toolkit 7.5 from debian8/backports is installed on that machine. When testing the application, it crashed with a segmentation fault. The issue is also

Bug#831387: Files and directories with Umlaut do not get backed up through smb

8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= #### Test 0: preparation ## For testing

Bug#816283: NVRM: API mismatch on cuda/jessie-backports

On 2016-03-31 20:30, Luca Boccassi wrote: > On Thu, 2016-03-31 at 18:23 +0200, Alois Schloegl wrote: >> At the beginning, I used the .run installer, but thought to have cleaned >> this up. Obviously, this was not the case. The are a few more files >> installed on Sep 10 (

Bug#816283: NVRM: API mismatch on cuda/jessie-backports

On 03/31/2016 04:12 PM, Andreas Beckmann wrote: > On 2016-03-31 11:46, Alois Schloegl wrote: >> I'm trying to get Cuda working on debian/jessie. When running >> nvidia-smi, dmesg shows this message: >> >> [ 2355.945623] NVRM: API mismatch: the client has the

Bug#816283: nvidia-cuda-toolkit: cuda broken after upgrade (x86_64, Jessie, GTX980)

In order to fix the installation of glx-alternative-nvidia, and fix some other cuda related issues, I tried to update cuda to jessie-backports. The update did not work out of the box, e.g After uninstalling nvidia-cuda and reinstallung with apt-get -t jessie-backports install

Bug#816283: nvidia-cuda-toolkit: cuda broken after upgrade (x86_64, Jessie, GTX980)

I was able to revert to a working state of cuda 6.5, by using dpkg -i and the packges in /var/cache/apt/archives. Below are the output of nvidia-smi and the gpuinfo test program. The package list is attached in "pkglist.nvidia.working.txt". Configuration of glx-alternative-nvidia failed with this

Bug#816283: nvidia-cuda-toolkit: cuda broken after upgrade (x86_64, Jessie, GTX980)

On 2016-02-29 16:08, lumin wrote: > Hi, > > Thank you for reporting this bug. > > It seems like a GCC ABI issue, rather than that of CUDA > or nvidia-driver. > If the nvidia-driver package ships binary then they are > linked by GCC-5, which requires an different ABI to > the one of Jessie. Hence

Bug#816283: nvidia-cuda-toolkit: cuda broken after upgrade (x86_64, Jessie, GTX980)

Package: nvidia-cuda-toolkit Version: 7.0.28-4 Severity: important Dear Maintainer, I tried to upgrade the nvidia-drivers from 352.41-1 to the current version "352.79-3" and nvidia-cuda-toolkit to a matching version, cuda became unusable. Rebooting the machine did not help. I used the

Bug#807016: octave-plplot: toggle_plplot_use is broken on Jessie

Package: octave-plplot Version: 5.10.0+dfsg-1 Severity: normal Tags: patch I've tryied to use plplot from Octave on Jessie. Octave and octave-plplot are installed. Starting octave and running "toggle_plplot_use cases the following problem: octave:1> use_plplot This function is deprecated.

Bug#742503: [Pkg-octave-devel] Bug#742503: octave 3.8.1 requires java

On 2015-07-16 07:00, Mike Miller wrote: On Wed, Jul 15, 2015 at 08:59:32 -0400, Mike Miller wrote: On Wed, Jul 15, 2015 at 10:00:33 +0200, Alois Schloegl wrote: Octave should not have a strong dependency on openjdk. Any of the following solutions would do: 1) the dependency should be changed

Bug#742503: [Pkg-octave-devel] Bug#742503: octave 3.8.1 requires java

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Recently, I tried to remove openjdk-[6-8] from a number of machines because of the large number of open security issues with openjdk (currently there are 23, 21 and 20 open security issues on openjdk-6, openjdk-7, and openjdk-8, resp.). I learned

Bug#698286: incorrect value for max vmem is reported : possible fix

The attached patch should address this issue. The patch is essentially this commit af73e397da01a4f70c01387f284e87262e42e7a3 Author: Dave Love d.l...@liverpool.ac.uk Date: Thu Apr 21 12:44:36 2011 + Introduce lUlong64 to fix wrong vmem reporting on 64-bit GNU/Linux (from Univa) from

Bug#701246: biosig4c++: ftbfs with GCC-4.8

The same bug has been already reported against liboctave-dev http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705485 This bug report can be merged. Alois -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact

Bug#701246: debian bugreport in biosig4c++: ftbfs with GCC-4.8

In file included from /usr/include/octave-3.6.2/octave/mexproto.h:52:0, from /usr/include/octave-3.6.2/octave/mex.h:77, from mexSLOAD.cpp:15: /usr/include/c++/4.8/cstdlib: In function 'long long int std::abs(long long int)':

Bug#703591: pdftk - support for AES encrypted pdf files missing

Package: pdftk Version: 1.44-7 Severity: Wishlist I got an pdf file that could not be opened with pdftk. pdftk /tmp/q.pdf data_dump Error: Failed to open PDF file: /tmp/q.pdf Done. Input errors, so no output created. Unfortunately, the file contains personal information, so I can not

Bug#698286: incorrect value for max vmem is reported

resulting in 4.8GB memory need. - the script for submission to the grid engine qsub memtest03.m The e.mail report contains this: Job 4709696 (MEMTEST02) Complete User = schloegl Queue= mai...@nick13.ista.local Host = nick13.ista.local Start Time = 01/16

Bug#631831: [Pkg-octave-devel] Bug#631831: Bug#631831: build octave with --enable-openmp

On 06/30/11 04:11, Jordi Gutiérrez Hermoso wrote: On 29 June 2011 18:54,schlo...@ist.ac.at wrote: On Tue, Jun 28, 2011 at 09:03:32AM +0200, Alois Schloegl wrote: adding -lgomp to mkoctfile call does not do it. And I've not found any another option to enable openmp at this stage. Did you

Bug#631831: [Pkg-octave-devel] Bug#631831: build octave with --enable-openmp

On Tue, Jun 28, 2011 at 09:03:32AM +0200, Alois Schloegl wrote: adding -lgomp to mkoctfile call does not do it. And I've not found any another option to enable openmp at this stage. Did you pass -fopenmp to the compiler? Thomas I tried, but mkoctfile does not accept -fopenmp

Bug#631831: [Pkg-octave-devel] Bug#631831: build octave with --enable-openmp

On 06/27/11 20:23, Thomas Weber wrote: Hi Alois, On Mon, Jun 27, 2011 at 05:30:18PM +0200, Alois Schloegl wrote: Package: octave3.2 Severity: wishlist Octave should be configured with --enable-openmp. This would enable the use of multiple cpus. https://mailman.cae.wisc.edu/pipermail/octave

Bug#611070: Package: installation-reports

Package: installation-reports Boot method: CD Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/ Date: Jan 25 2011 10:00-11:00 CET GMT+1 Machine: Asus EeePC 1008PGO Processor: Atom N450 Memory: 1 GB Partitions: df -Tl will do; the raw partition table

Bug#457502: xserver-xorg-video-mga: mouse pointer isn't visible on VGA2 (MGA G450)

Package: xserver-xorg-video-mga Version: 1.9.100.dfsg.1-1 Severity: normal Hi, After expanding the desktop to both screens by command line xrandr --output VGA2 --right-of VGA1 the mouse pointer isn't visible when the mouse is moved into VGA2. It's possible to move windows into VGA2, even

Bug#419556: [Pkg-octave-devel] Bug#419556: ambigous results in matrix multipliication

Original-Nachricht Datum: Mon, 16 Apr 2007 21:38:12 +0200 Von: Thomas Weber [EMAIL PROTECTED] An: Alois Schloegl [EMAIL PROTECTED], [EMAIL PROTECTED] Betreff: Re: [Pkg-octave-devel] Bug#419556: ambigous results in matrix multipliication Hi, Am Montag, 16. April 2007 17:32

Bug#419556: ambigous results in matrix multipliication

Package: Octave2.9 Status: install ok installed Priority: optional Section: math Installed-Size: 26220 Maintainer: Debian Octave Group [EMAIL PROTECTED] Architecture: i386 Version: 2.9.10-3 Severity: Important One expects that a matrix multiplication (A*B)' gives the same result than for