severity 643737 serious thanks Hi!
The GNOME 3 transition is now starting and very soon libgucharmap7 will not be available, making this package FTBFS. I plan to upload bluefish with the attached diff applied during the week, so the gucharmap plugin isn't built anymore. Thanks, Jordi -- Jordi Mallach Pérez -- Debian developer http://www.debian.org/ jo...@sindominio.net jo...@debian.org http://www.sindominio.net/ GnuPG public key information available at http://oskuro.net/
diff -u bluefish-2.0.3/debian/control bluefish-2.0.3/debian/control --- bluefish-2.0.3/debian/control +++ bluefish-2.0.3/debian/control @@ -4,8 +4,8 @@ Priority: optional Build-Depends: debhelper (>> 5.0.51~), autotools-dev, gettext, intltool (>= 0.40), libtool, libenchant-dev, libglib2.0-dev (>= 2.16), libgtk2.0-dev (>= 2.12), - libgucharmap2-dev (>= 2.20) | libgucharmap-dev (>= 2.20), libpango1.0-dev, - libxml2-utils, libxml2-dev, python-dev, zlib1g-dev + libpango1.0-dev, libxml2-utils, libxml2-dev, python-dev, zlib1g-dev +Build-Conflicts: libgucharmap2-dev Standards-Version: 3.9.1 Homepage: http://bluefish.openoffice.nl Vcs-Browser: http://bluefish.svn.sourceforge.net/viewvc/bluefish/packages/debian/bluefish/trunk/ diff -u bluefish-2.0.3/debian/changelog bluefish-2.0.3/debian/changelog --- bluefish-2.0.3/debian/changelog +++ bluefish-2.0.3/debian/changelog @@ -1,3 +1,14 @@ +bluefish (2.0.3-1.1) unstable; urgency=low + + * Non-maintainer upload, for the GNOME 3 transition. + * Disable charmap plugin, as the GTK+ 2.0 version of libgucharmap7 is + going away and loading GTK+ 2.0 and 3.0 in the same process is not + allowed (closes: #643737). + * Move Build-Depends on libgucharmap2-dev to Build-Conflicts as there + isn't a configure switch to disable the plugin. + + -- Jordi Mallach <jo...@debian.org> Thu, 13 Oct 2011 12:19:57 +0200 + bluefish (2.0.3-1) unstable; urgency=low * New upstream release.
