Bug#651992: cl-portable-aserve: diff for NMU version 1.2.42+cvs.2010.02.08-dfsg-1.1

tags 651992 + patch tags 651992 + pending thanks Dear maintainer, I've prepared an NMU for cl-portable-aserve (versioned as 1.2.42+cvs.2010.02.08-dfsg-1.1). I have not uploaded it since I am a DM. Regards. diff -u cl-portable-aserve-1.2.42+cvs.2010.02.08-dfsg/debian/control cl-portable-aserve-1

Bug#493869: octave3.0: gaminv and gamcdf crash for big values of parameter A

Package: octave3.0 Version: 1:3.0.1-6 Severity: normal gaminv and gamcdf function crash with the following parameters: octave> gaminv(0.5,600,1) ***MESSAGE FROM ROUTINE D9LGIT IN LIBRARY SLATEC. ***FATAL ERROR, PROG ABORTED, TRACEBACK REQUESTED * NO CONVERGENCE IN 200 TERMS OF CONTINUED FRACT

Bug#492959: dblatex: fails when a "linkend" attribute contains an underscore

Package: dblatex Version: 0.2.9-2 Severity: normal dblatex does not correctly handle underscores in "linkend" attributes. It doesn't escape the underscore with a backslash when outputting the LaTeX file, and this makes pdflatex fail. Consider the following example: http://www.oasis-open.org/

Bug#485920: octave-miscellaneous: calling waitbar() makes Octave crash when run within Emacs

Package: octave-miscellaneous Version: 1.0.6-2 Severity: normal When I run Octave as an Emacs inferior process (with M-x run-octave), any call to waitbar() will make Octave segfault: octave> waitbar(0) panic: Segmentation fault -- stopping myself... attempting to save variables to `octave-core'

Bug#336602: gksu: fails when wheel group trusted in /etc/pam.d/su

Package: gksu Version: 1.3.5-2 Severity: normal I have uncommented the following line in /etc/pam.d/su: auth sufficient pam_wheel.so trust so that members of group wheel can su without a password. This settings makes gksu exit after a few seconds without any output or display (or crash if

Bug#313227: bacula-director-pgsql: omits to set character encoding when creating database

Package: bacula-director-pgsql Version: 1.36.2-2sarge1 Severity: normal When it creates the postgresql database, the postinst script omits to specify a character encoding. Therefore, the system wide setting is used, which is unicode on my box. Because of this, when a backup job encounters a filen