Bug#553109: guile-gnutls: postinst-must-call-ldconfig /usr/lib/libguile-gnutls-v-1.so.0.0.0 by the dynamic library loader. Therefore, the package must call ldconfig in its postinst script.

2009-11-01 Thread Ludovic =?UTF-8?Q?Court=C3=A8s
Hi, Neil Jerram n...@ossau.uklinux.net writes: In that case, for the sake of consistency, shouldn't the answer be the same as what we will get in 1.9/2.0 from `pkg-config --value=extensionsdir guile-2.0` (per Andy's email)? Yes, good point. That would be ‘$libdir/guile/1.8/extensions’ then.

Bug#553109: guile-gnutls: postinst-must-call-ldconfig /usr/lib/libguile-gnutls-v-1.so.0.0.0 by the dynamic library loader. Therefore, the package must call ldconfig in its postinst script.

2009-10-31 Thread Ludovic =?UTF-8?Q?Court=C3=A8s
Hello, Neil Jerram n...@ossau.uklinux.net writes: My view on this is not very strong, but is that by sticking to /usr/lib we do seem to be sailing against the wind (cf. other scripting languages); and also that the normal C library argument feels unlikely in practice.) I agree. The “normal

Bug#553109: guile-gnutls: postinst-must-call-ldconfig /usr/lib/libguile-gnutls-v-1.so.0.0.0 by the dynamic library loader. Therefore, the package must call ldconfig in its postinst script.

2009-10-31 Thread Ludovic =?UTF-8?Q?Court=C3=A8s
Neil Jerram n...@ossau.uklinux.net writes: l...@gnu.org (Ludovic Courtès) writes: As far as the GnuTLS Guile bindings arguments, libguile-gnutls was never s/arguments/are concerned/ meant to be used as a “normal C library”, so it should definitely go under something different from $libdir

Bug#447916: libmailutils1: Guile module fails to load `libmailutils'

2007-10-31 Thread Ludovic =?UTF-8?Q?Court=C3=A8s
Hi, Jordi Mallach [EMAIL PROTECTED] writes: This is documented in README.Debian, but I'm not sure that's enough. Any other suggestion? The file reads: This package includes a few guile dynamic libraries, but they can't be used without their corresponding .la files. Why is it the case?

Bug#433782: libcap-bin: Manual page for `cap_from_text(3)' is missing

2007-10-14 Thread Ludovic =?UTF-8?Q?Court=C3=A8s
Hi, Ted Percival [EMAIL PROTECTED] writes: Ludovic Courtes wrote: In addition to bug #118186, the manual page for `cap_from_text(3)' (which is referred to by `getpcaps') isn't available. This makes it hard to use the tools. cap_from_text(3)'s manpage is in libcap-dev. Would this be solved

Bug#435452: emacs22: `set-keyboard-coding-system' fails in non-X11 mode]

2007-09-01 Thread Ludovic =?UTF-8?Q?Court=C3=A8s
Hi, Stefan Monnier [EMAIL PROTECTED] writes: Typing M-x yields the `ø' (o slash) character instead of running `execute-extended-command'. This is because your terminal sends the exact same byte sequence (in this case it's actually a single byte) when you type M-x as when you type ø, so

Bug#435452: emacs22: `set-keyboard-coding-system' fails in non-X11 mode]

2007-08-30 Thread Ludovic =?UTF-8?Q?Court=C3=A8s
Hi, Kenichi Handa [EMAIL PROTECTED] writes: In article [EMAIL PROTECTED], [EMAIL PROTECTED] (Ludovic Courtès) writes: Indeed, using C as my locale fixes the problem (I used to have LC_CTYPE=fr_FR). Strangely enough, Emacs 21.4.1 with LC_CTYPE=fr_FR doesn't have the problem (i.e., dead

Bug#435452: emacs22: `set-keyboard-coding-system' fails in non-X11 mode]

2007-08-29 Thread Ludovic =?UTF-8?Q?Court=C3=A8s
Hi, Sven Joachim [EMAIL PROTECTED] writes: Invoking `set-keyboard-coding-system' in an emacs -nw session fails. For instance, asking it `no-conversion' (which is needed so that dead keys work as expected) fails: Unsupported coding system in Encoded-kbd mode: no-conversion I don't

Bug#425716: tdb-dev: Fails to open previous databases

2007-07-18 Thread Ludovic =?UTF-8?Q?Court=C3=A8s
Hi, Pierre Habouzit [EMAIL PROTECTED] writes: The problem is because of the deactivated spinlock code. The following patch seems to fix the problem, but I'm unable to understand the consequences properly (e.g. on a system where things using the old tdb library could still exist, and

Bug#422108: closed by Daniel Baumann [EMAIL PROTECTED] (Bug#422108: fixed in linux-libertine 2.5.9-1)

2007-05-09 Thread Ludovic =?UTF-8?Q?Court=C3=A8s
Hi, [EMAIL PROTECTED] (Debian Bug Tracking System) writes: This is an automatic notification regarding your Bug report #422108: linux-libertine: Erroneous Defoma hints for Type 1 fonts, which was filed against the linux-libertine package. Thanks for applying the patch. Could you answer my

Bug#419618: Other crash-on-print example

2007-04-17 Thread Ludovic =?UTF-8?Q?Court=C3=A8s
Hi, FWIW, I have another example PDF file that reproducibly crashed Evince (0.4.0-5) and Xpdf (3.01-9) when clicking on print, or when directly running `pdftops' from `xpdf-utils' (3.01-9): http://www.cs.cmu.edu/~ntolia/files/pubs/fast03.pdf SHA1: 742aef21430186ebc2f46c222a1064df838ad80c

Bug#419618: Other crash-on-print example

2007-04-17 Thread Ludovic =?UTF-8?Q?Court=C3=A8s
Hi, Hamish Moffatt [EMAIL PROTECTED] writes: pdftops works for me on that file. I am out of date from unstable by a week or two. I wonder if one of the libraries that Xpdf uses has changed since the lenny flood gates opened, hence the sudden rush of bugs being reported. I haven't upgraded

Bug#305801: closed by Oleksandr Moskalenko [EMAIL PROTECTED] (close #305801)

2007-02-28 Thread Ludovic =?UTF-8?Q?Court=C3=A8s
Hi, [EMAIL PROTECTED] (Debian Bug Tracking System) writes: From: Oleksandr Moskalenko [EMAIL PROTECTED] Subject: close #305801 To: [EMAIL PROTECTED] Date: Tue, 27 Feb 2007 14:41:14 -0700 Reply-To: Oleksandr Moskalenko [EMAIL PROTECTED] User-Agent: Mutt/1.5.13 (2006-08-11) Tested, not