Bug#1075793: plastimatch FTBFS with DCMTK 3.6.8
Thank you Adrian, Yes this is the correct patch. I'm inclined to make a new upstream release instead of patching, but let me know. Greg Sharp gregsh...@geocities.com
Bug#1075793: plastimatch FTBFS with DCMTK 3.6.8
Hi Mathieu, Thank you for the report. This was fixed long ago upstream, but I did not deploy a new version. Sorry for the FTBFS, that is my bad. Greg Sharp gregsh...@geocities.com
Bug#771094: nmu: plastimatch_1.5.16+dfsg-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu plastimatch_1.5.16+dfsg-2 . ALL -amd64 -arm64 -hurd-i386 -i386 -ppc64el . -m "Rebuild against new libinsighttoolkit3-dev" This is needed to resolve #769975. Thank you, Greg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#771092: insighttoolkit: Build failure on sparc
Package: insighttoolkit Version: 3.20.1+git20120521-5+b1 Severity: normal The sparc build continuously fails with the following message: Preparing to unpack .../libuuid1_2.25.2-3_sparc.deb ... Unpacking libuuid1:sparc (2.25.2-3) over (2.25.2-2) ... Setting up libuuid1:sparc (2.25.2-3) ... /var/lib/dpkg/info/libuuid1:sparc.postinst: 15: /var/lib/dpkg/info/libuuid1:sparc.postinst: groupmod: not found dpkg: error processing package libuuid1:sparc (--configure): subprocess installed post-installation script returned error exit status 127 Errors were encountered while processing: libuuid1:sparc E: Sub-process /usr/bin/dpkg returned an error code (1) apt-get failed. See for example: https://buildd.debian.org/status/fetch.php?pkg=insighttoolkit&arch=sparc&ver=3.20.1%2Bgit20120521-5%2Bb1&stamp=1416898633 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#770837: nmu: insighttoolkit_3.20.1+git20120521-5
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu insighttoolkit_3.20.1+git20120521-5 . !ppc64el . -m "Rebuild against multi-arch gdcm library" The binNMU is needed to resolve #768769, and eventually #769975. Thank you, Greg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#768769: plastimatch: FTBFS in jessie: Tests failures
Thank you for the report. This is a bug in upstream, where the regression test is missing a dependency. -- Greg Sharp gregsh...@geocities.com - Original Message - > From: Lucas Nussbaum > To: sub...@bugs.debian.org > Cc: > Sent: Sunday, November 9, 2014 2:26 AM > Subject: Bug#768769: plastimatch: FTBFS in jessie: Tests failures > > Source: plastimatch > Version: 1.5.16+dfsg-1 > Severity: serious > Tags: jessie sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20141108 qa-ftbfs > Justification: FTBFS in jessie on amd64 > > Hi, > > During a rebuild of all packages in jessie (in a jessie chroot, not a > sid chroot), your package failed to build on amd64. > > Relevant part (hopefully): >> Start 286: plm-sift-a-check-1 >> Start 287: plm-sift-a-check-2 >> 351/352 Test #286: plm-sift-a-check-1 Passed0.02 > sec >> 352/352 Test #287: plm-sift-a-check-2 Passed0.02 > sec >> >> 99% tests passed, 3 tests failed out of 352 >> >> Total Test time (real) = 41.57 sec >> >> The following tests FAILED: >> 297 - plm-union (Failed) >> 298 - plm-union-stats (Failed) >> 299 - plm-union-check (Failed) >> Errors while running CTest >> make[2]: *** [test] Error 8 >> Makefile:140: recipe for target 'test' failed > > The full build log is available from: > > http://aws-logs.debian.net/ftbfs-logs/2014/11/08/plastimatch_1.5.16+dfsg-1_jessie.log > > A list of current common problems and possible solutions is available at > http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! > > About the archive rebuild: The rebuild was done on EC2 VM instances from > Amazon Web Services, using a clean, minimal and up-to-date chroot. Every > failed build was retried once to eliminate random failures. > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#748155: (no subject)
Thank you Jakub, the problem is confirmed. It looks like that library went away when libinsighttoolkit4.5 was upgraded. The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Partners Compliance HelpLine at http://www.partners.org/complianceline . If the e-mail was sent to you in error but does not contain patient information, please contact the sender and properly dispose of the e-mail. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#730423: qtchooser: could not find a Qt installation of
> On Sunday, November 24, 2013 7:36 PM, Lisandro Damián Nicanor Pérez Meyer > wrote: > > On Sunday 24 November 2013 17:46:35 Greg Sharp wrote: > >> Package: qtchooser >> Version: 31-g980c64c-4 >> Severity: normal >> >> Dear Maintainer, >> >> I suffer from the seemingly common problem of qtchooser not finding >> its configuration directories. (cf #710773, #726989). >> >> For example, with qt4-default installed, the following occurs: >> >> $ qtchooser -list-versions >> $ qtchooser -print-env >> qtchooser: could not find a Qt installation of '' >> >> Unsetting XDG_CONFIG_DIRS does solve the problem, but my expectation >> would be a working package as default. >> >> Is this an issue with qtchooser, or is it xfce shouldn't set >> XDG_CONFIG_DIRS, or somewhere else? > > Upstream considers that if XDG_CONFIG_DIRS is set, qtchooser's config should > > be found using it, ignoring everything else, including the default we provide. > > On the other hand we the Qt/KDE team consider that the normal place for which > XDG_CONFIG_DIRS points, /etc/xdg/, is not a place to store qtchooser's > configs. > > So if you set XDG_CONFIG_DIR, you need to set provide qtchooser's config. > You > can do that by symlinking /usr/share/qtchooser > > -- > > Lisandro Damián Nicanor Pérez Meyer > http://perezmeyer.com.ar/ > http://perezmeyer.blogspot.com/ Thank you Lisandro for the very clear explanation. I search a little, it seems xfce4 which sets XDG_CONFIG_DIRS in the script /usr/bin/startxfce4. Do you think it is an incorrect choice by xfce to set this variable, or maybe they should also append your qtchooser directories? It is a problem that qmake and other executables aren't working. Nevertheless, it is difficult for me to suggest how to resolve. -- Greg Sharp gregsh...@geocities.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#631116: Additional information on bug 631116
I have this bug too, and I found a pattern. By typing two keys in rapid succession, the second keystroke usually (~90%) makes it through to gnome-terminal. Initially I had the idea it might be SCIM-related, but removing SCIM did not seem to clear the problem. Greg Sharp gregsh...@geocities.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#525572: pulseaudio: volume muted after every boot
OK, this bug is still open, so I'll bite. (1) Is the corresponding Ubuntu bug log (0090_fix_sw_mute_desync.patch) relevant? https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/352732 (2) Output from pulseaudio - (after fresh boot & login from gdm) D: main.c: Started as real root: no, suid root: yes I: main.c: PolicyKit refuses acquire-high-priority privilege. I: main.c: Called SUID root and real-time and/or high-priority scheduling was requested in the configuration. However, we lack the necessary privileges: I: main.c: We are not in group 'pulse-rt', PolicyKit refuse to grant us the requested privileges and we have no increase RLIMIT_NICE/RLIMIT_RTPRIO resource limits. I: main.c: For enabling real-time/high-priority scheduling please acquire the appropriate PolicyKit privileges, or become a member of 'pulse-rt', or increase the RLIMIT_NICE/RLIMIT_RTPRIO resource limits for this user. I: main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted I: main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not permitted D: main.c: Can realtime: no, can high-priority: no D: main.c: Can realtime: no, can high-priority: no I: main.c: This is PulseAudio 0.9.15 D: main.c: Compilation host: i486-pc-linux-gnu D: main.c: Compilation CFLAGS: -g -O2 -g -Wall -O2 -Wall -W -Wextra -pipe -Wno-long-long -Winline -Wvla -Wno-overlength-strings -Wunsafe-loop-optimizations -Wundef -Wformat=2 -Wlogical-op -Wsign-compare -Wformat-security -Wmissing-include-dirs -Wformat-nonliteral -Wold-style-definition -Wpointer-arith -Winit-self -Wdeclaration-after-statement -Wfloat-equal -Wmissing-prototypes -Wstrict-prototypes -Wredundant-decls -Wmissing-declarations -Wmissing-noreturn -Wshadow -Wendif-labels -Wcast-align -Wstrict-aliasing=2 -Wwrite-strings -Wno-unused-parameter -ffas t-math -Wp,-D_FORTIFY_SOURCE=2 -fno-common -fdiagnostics-show-option D: main.c: Running on host: Linux i686 2.6.26-2-686 #1 SMP Thu Mar 26 01:08:11 UTC 2009 D: main.c: Found 1 CPUs. I: main.c: Page size is 4096 bytes D: main.c: Compiled with Valgrind support: no D: main.c: Running in valgrind mode: no D: main.c: Optimized build: yes D: main.c: All asserts enabled. I: main.c: Machine ID is a2cd218d3c2fda097b5d9c00478c3229. I: main.c: Session ID is a2cd218d3c2fda097b5d9c00478c3229-1245385113.576938-1633355518. I: main.c: Using runtime directory /home/gsharp/.pulse/a2cd218d3c2fda097b5d9c00478c3229:runtime. I: main.c: Using state directory /home/gsharp/.pulse. I: main.c: Running in system mode: no E: pid.c: Daemon already running. E: main.c: pa_pid_file_create() failed. -- Greg Sharp gregsh...@geocities.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#519724: [Debian-med-packaging] Bug#519724: libinsighttoolkit3-dev: User program link error - libuuid
--- On Sat, 3/14/09, Nelson A. de Oliveira wrote: > From: Nelson A. de Oliveira > Subject: Re: [Debian-med-packaging] Bug#519724: libinsighttoolkit3-dev: User > program link error - libuuid > To: gregsharp@yahoo.com, 519...@bugs.debian.org > Date: Saturday, March 14, 2009, 10:40 AM > Hi Gregory! > > On Sat, Mar 14, 2009 at 2:30 PM, Gregory Sharp > wrote: > > User programs which try to link to debian ITK using > the usual > > CMake method of FIND_PACKAGE(ITK) cannot link. The > path specified > > in ITKLibraryDepends.cmake is /usr/lib/libuuid.so, but > debian > > installs in /lib/libuuid.so. > > libuuid.so (from uuid-dev) is installed as > /usr/lib/libuuid.so > (See: > http://packages.debian.org/sid/i386/uuid-dev/filelist) > > If I understood it correctly, I can't see where > it's wrong. Hi Nelson, That is interesting. I don't have uuid-dev installed. Now I look at the dependencies it seems that uuid-dev is not a dependency. Instead, libuuid1 is the dependency. gsh...@stonesmith:~$ dpkg -S /lib/libuuid.so.1 libuuid1: /lib/libuuid.so.1 I don't understand why one in /lib, and another in /usr/lib. But anyway, that does explain the problem. Greg -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#519724: libinsighttoolkit3-dev: User program link error - libuuid
Subject: libinsighttoolkit3-dev: User program link error - libuuid Package: libinsighttoolkit3-dev Version: 3.10.1-1 Severity: normal *** Please type your report below this line *** Hi, I reported this already once, but didn't get feedback email, nor did I find in the web database. Sorry if it is duplicated. User programs which try to link to debian ITK using the usual CMake method of FIND_PACKAGE(ITK) cannot link. The path specified in ITKLibraryDepends.cmake is /usr/lib/libuuid.so, but debian installs in /lib/libuuid.so. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libinsighttoolkit3-dev depends on: ii libfftw3-dev 3.1.2-3.1 library for computing Fast Fourier ii libinsighttoolkit3.10 3.10.1-1 Image processing toolkit for regis libinsighttoolkit3-dev recommends no packages. Versions of packages libinsighttoolkit3-dev suggests: pn insighttoolkit3-examples (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#331669: issue in streamripper 1.61.14
--- Michael Ablassmeier <[EMAIL PROTECTED]> wrote: > hi Greg, > > On Tue, Oct 04, 2005 at 06:22:01AM -0700, Gregory Sharp wrote: > > Just wanted to warn you of a new bug in the latest > > streamripper (1.61.14). The symptom is that they > > will get an error of "SR_ERROR_BUFFER_EMPTY", and then > > streamripper will exit. This only happens with certain > > streams, and/or with certain splitpoint settings. > > okey, do you rate this bug as release critical? If so, then i > could file > a bugreport against the package, so that it doesnt enter the > testing > distribution and stays in unstable (testing contains 1.61.11 > at the > moment). > Yes, that is a good idea. From 1.61.11 to 1.61.14 contains the new buffering code, and it may have other bugs. Greg Greg Sharp [EMAIL PROTECTED] __ Yahoo! for Good Donate to the Hurricane Katrina relief effort. http://store.yahoo.com/redcross-donate3/
Bug#331669: issue in streamripper 1.61.14
Hi Michael, Just wanted to warn you of a new bug in the latest streamripper (1.61.14). The symptom is that they will get an error of "SR_ERROR_BUFFER_EMPTY", and then streamripper will exit. This only happens with certain streams, and/or with certain splitpoint settings. The only known fix is to downgrade back to 1.61.11. I will fix this in the next release (about 2-4 week time frame). Thanks, Greg Greg Sharp [EMAIL PROTECTED] __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com
