Bug#649459: workaround
The workaround is to add: const Shell = imports.gi.Shell; to the top of /usr/share/gnome-shell/js/ui/windowManager.js Sjoerd will have a new package out later today, hopefully. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#542285: debian packages of guile 1.9/2.0
Hi, On Sat 17 Jul 2010 14:50, l...@gnu.org (Ludovic Courtès) writes: > Andy Wingo writes: > >> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542285. Is there any >> chance you could prod those folks? Ludo, can we get libgc people to >> help? > > Yes, the Debian folks just need to report upstream, if that’s not > already done, and they’ll probably quickly get an answer. > > FWIW, people have been meaning to release libgc 7.2 for a while, which > may fix the problem (and optionally add other problems ;-)). Copying the Debian libgc maintainer, then. With a report upstream, hopefully the libgc people can handle the Debian FTBFS problem themselves :) Andy -- http://wingolog.org/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@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.
Hi, On Fri 30 Oct 2009 22:14, Neil Jerram writes: > 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. 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 that the names of Guile extensions had to be globally unique. Installing them to a Guile-specific extensions directory is cleaner. Use `pkg-config --variable=extensionsdir guile-2.0' to get the location of the extensions directory. > (Historically this has cropped up several times. Marius favoured > /usr/lib on the grounds that it could make sense for some application to > use a Guile extension library just like a normal C library > (i.e. application coded in C, linking at build time to the extension > library and to libguile). But on the other hand the advantage of > somewhere like /usr/lib/guile-1.8 is that it makes it easier to handle > parallel installation, and corresponding correct version numbering, > without having to have .so names that have both libguile and extension > version numbers in. I think the balance goes for parallel installation -- that is, installing in guile-specific directories. However we do support dynamically loaded extensions in $libdir as well, for backwards compatibility. Also I'm not sure it's portable to have a shared module and be able to link to it. Andy -- http://wingolog.org/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#421534: wordpress: New 2.0.10 release claims to fix security issues, should be in stable security updates
Package: wordpress Version: 2.0.9-1 Severity: grave Tags: security Justification: user security hole The upstream 2.0.10 release notes claim that it fixes security problems, especially with the XML-RPC module. The diff applies cleanly to the packaged files, and appears to run fine on my machine. Suggest update. The diff: svn diff http://svn.automattic.com/wordpress/tags/2.0.9/ http://svn.automattic.com/wordpress/tags/2.0.10/ -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.27-2-386 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages wordpress depends on: ii apache2-mpm-prefork [htt 2.2.3-4 Traditional model for Apache HTTPD ii libapache2-mod-php4 6:4.4.4-8+etch2 server-side, HTML-embedded scripti ii mysql-client-5.0 [virtua 5.0.32-7etch1 mysql database client binaries ii php4-mysql 6:4.4.4-8+etch2 MySQL module for php4 wordpress recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
