Bug#742408: fixed in connman 1.32-0.1

On Mon, 02 May 2016 18:50:07 + =?utf-8?q?Mateusz_=C5=81ukasik?= wrote: > Source: connman > Source-Version: 1.32-0.1 > > We believe that the bug you reported is fixed in the latest version of > connman, which is due to be installed in the Debian FTP archive. Amazing,

Bug#790211: Bug#801281: switch to gtk3

On Fri, 09 Oct 2015 01:13:18 -0400 Sergio Durigan Junior wrote: > > On Thursday, October 08 2015, chr...@fsfe.org wrote: > > > please consider building future versions of midori using gtk3; most > > important feature for me is finger scrolling that comes with it on touch >

Bug#742408: connman: Please package latest release (= 1.22)

Package: connman Version: 1.21-1 Severity: normal Dear Maintainer, I'd very much appreciate if you could package the latest connman release (1.22), because I'd like to use the A USB gadget device can be used as Internet uplink feature that is newly available in 1.22. (See

Bug#659062: ofono: Please consider packaging a more recent oFono release

Package: ofono Version: 0.53-2 Severity: wishlist Dear Maintainer, Please could you consider packaging a more recent oFono release, = 1.3 ? = 1.3 has support for the Option modem in my GTA04 device, on which I'm running Debian, and so it would be nice if = 1.3 was in the official archive. Many

Bug#560653: guile-1.8: FTBFS: ERROR: file: libtest-asmobs, message: file not found

Neil Jerram n...@ossau.uklinux.net writes: I suspect what's needed here is a patch like http://git.savannah.gnu.org/gitweb/?p=guile.git;a=commitdiff;h=5b98517a652ea51cbb0fd03e87a50c0b3add9707. I will upgrade to libltdl 2.2.6b, check if I can reproduce the FTBFS, and then see if that patch

Bug#560653: guile-1.8: FTBFS: ERROR: file: libtest-asmobs, message: file not found

Lucas Nussbaum lu...@lucas-nussbaum.net writes: ERROR: In procedure dynamic-link: ERROR: file: libtest-asmobs, message: file not found FAIL: test-asmobs PASS: test-list PASS: test-unwind PASS: test-conversion PASS: test-fast-slot-ref PASS: test-use-srfi PASS: test-scm-c-read PASS:

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.

Neil Jerram n...@ossau.uklinux.net writes: For 1.8.x extensions have to go in /usr/lib ... Sorry, s/have to/usually/ (It's possible for Guile code to load a .so from anywhere if it specifies the full path.) Neil -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org

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.

l...@gnu.org (Ludovic Courtès) writes: As far as the GnuTLS Guile bindings arguments, libguile-gnutls was never meant to be used as a “normal C library”, so it should definitely go under something different from $libdir (I wasn’t clear on that when I worked on it back then.) So as time

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.

Andy Wingo wi...@pobox.com writes: In the alpha 1.9 series you can install them to extensiondir. From NEWS: ** Dynamically loadable extensions may be placed in a Guile-specific path Before, Guile only searched the system library paths for extensions (e.g. /usr/lib), which meant

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.

l...@gnu.org (Ludovic Courtès) writes: meant to be used as a “normal C library”, so it should definitely go under something different from $libdir (I wasn’t clear on that when I worked on it back then.) So as time permits, I’m planning to update GnuTLS so that it installs the .so under

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.

Ludo / Andy, Is it still the case that we recommend guile extensions to be installed as normal libraries in /usr/lib, as opposed to some guile-specific place? I think you were recently discussing this, and I'm afraid I didn't pay complete attention. (Historically this has cropped up several

Bug#551119: e17: Illume launcher shows the same GNU Emacs 23 icon twice

Package: e17 Version: 0.16.999.062-1 Severity: normal I just installed emacs 23 (on my Neo Freerunner) and noticed that the illume launcher shows two identical emacs icons, with name GNU Emacs 23. Looking at /usr/share/applications/emacs23.desktop, I guessed that this might be caused by the

Bug#530010: Please document that threads are disabled

r...@cs.hut.fi (Riku Saikkonen) writes: It appears that threads are disabled in the Debian package of guile-1.8. There are some references to this in /usr/share/doc/guile-1.8/changelog.Debian.gz, but otherwise this does not seem to be documented anywhere. I think it should be documented in a

Bug#506684: guile-1.8: includes own definition of jmp_buf type in public header

2008/11/29 Ben Hutchings [EMAIL PROTECTED]: Here's a patch that renames Guile's reimplementations of jmp_buf, longjmp and setjmp in the public headers. I have tested that guile-1.8 builds on i386 and ia64 with the addition of this patch. I have not tested building lilypond against the

Bug#501854: guile-1.8: GDS is not really usable without gds.el

On 11/10/2008, Jose Antonio Ortega Ruiz [EMAIL PROTECTED] wrote: It'd be nice to have and additional guile-gds-el package providing gds.el (unless it's already available somewhere else). Or it could just be included in the guile-1.8 package. Note that you'll need gds-scheme.el and

Bug#495609: [debian] Can't type with matchbox keyboard

2008/9/19 Joachim Breitner [EMAIL PROTECTED]: Am Freitag, den 19.09.2008, 00:59 +0200 schrieb Neil Jerram: It looks like the problem is in /usr/share/matchbox-keyboard/keyboard-extended.xml: at line 276, it has two key entries which both have default display=. / I would guess

Bug#494337: guile-1.8: FTBFS in lenny: stdout:1536: error: 'input' defined but not used

2008/8/8 Lucas Nussbaum [EMAIL PROTECTED]: Package: guile-1.8 Version: 1.8.4+1-2 Severity: serious User: [EMAIL PROTECTED] Usertags: qa-ftbfs-20080808 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in a lenny chroot, your package failed to build on i386.

Bug#481378: Guile-1.8 FTBFS on mips (and other architectures)

2008/5/31 Neil Jerram [EMAIL PROTECTED]: 2008/5/29 Thiemo Seufer [EMAIL PROTECTED]: Neil Jerram wrote: 2008/5/28 Thiemo Seufer [EMAIL PROTECTED]: After a closer look I believe the logic of the test is just plain wrong: aux (l) unsigned long l; { int x; exit (l = ((unsigned long)x

Bug#481378: Guile-1.8 FTBFS on mips (and other architectures)

2008/5/28 Thiemo Seufer [EMAIL PROTECTED]: After a closer look I believe the logic of the test is just plain wrong: aux (l) unsigned long l; { int x; exit (l = ((unsigned long)x)); } main () { int q; aux((unsigned long)q); }, The test returns true for a downward-growing stack, but that

Bug#481378: Guile-1.8 FTBFS on mips (and other architectures)

2008/5/15 Thiemo Seufer [EMAIL PROTECTED]: Package: guile-1.8 Version: 1.8.5+1-1 Severity: serious Tags: patch Guile-1.8 currently fails to build on ia64 The ia64 problem is one that we've fixed upstream since 1.8.5, and I've provided the patch for testing to Rob Browning (Debian

Bug#479588: guile-1.8-doc: guile-tut-1.8.info has several blank sections

that it is very out of date. I will of course also work on fixing this upstream. Neil Jerram (Guile maintainer) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#474786: Bug report logs - #474786

[EMAIL PROTECTED] writes: Solution: change #ifndef YY_NO_INPUT to #ifdef YY_NO_INPUT in guile-1.8.4/libguile/c-tokenize.c :656 and :1529 Should work on this error. But unfortunately it will not continue working in the future! I believe the correct upstream fix for this is to #define