Your message dated Fri, 24 Feb 2012 16:33:11 +0000
with message-id <e1s0y51-0004or...@franck.debian.org>
and subject line Bug#641358: fixed in sary-ruby 1.2.0-3.1
has caused the Debian Bug report #641358,
regarding sary-ruby FTBFS on Ubuntu
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
641358: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641358
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sary-ruby
Version: 1.2.0-3
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu oneiric ubuntu-patch



*** /tmp/tmpgerdwh
In Ubuntu, the attached patch was applied to achieve the following:

  * Add patch to fix FTBFS caused by non-explicit glib-2.0 dependency.
    (LP: #755960)

This does not cause FTBFS on Debian yet, but it will if/when glib-2.0 is moved
to a multi-arch setup. The patch builds and functions correctly on sid.

Thanks for considering the patch.


-- System Information:
Debian Release: wheezy/sid
  APT prefers oneiric-updates
  APT policy: (500, 'oneiric-updates'), (500, 'oneiric-security'), (500, 
'oneiric')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-9-generic (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
=== modified file 'debian/changelog'

=== added file 'debian/patches/00list'
--- debian/patches/00list       1970-01-01 00:00:00 +0000
+++ debian/patches/00list       2011-09-12 18:36:55 +0000
@@ -0,0 +1 @@
+50_fix_multiarch_ftbfs.dpatch

=== added file 'debian/patches/50_fix_multiarch_ftbfs.dpatch'
--- debian/patches/50_fix_multiarch_ftbfs.dpatch        1970-01-01 00:00:00 
+0000
+++ debian/patches/50_fix_multiarch_ftbfs.dpatch        2011-09-12 18:35:06 
+0000
@@ -0,0 +1,39 @@
+#!/bin/sh -e
+## 50_fix_multiarch_ftbfs.dpatch.dpatch by Clint Byrum <cl...@ubuntu.com>
+##
+## All lines beginning with `## DP:' are a description of the patch.
+## DP: Fails to build because it can't find glib-2.0
+
+if [ $# -ne 1 ]; then
+    echo >&2 "`basename $0`: script expects -patch|-unpatch as argument"
+    exit 1
+fi
+
+[ -f debian/patches/00patch-opts ] && . debian/patches/00patch-opts
+patch_opts="${patch_opts:--f --no-backup-if-mismatch}"
+
+case "$1" in
+       -patch) patch $patch_opts -p1 < $0;;
+       -unpatch) patch $patch_opts -p1 -R < $0;;
+        *)
+                echo >&2 "`basename $0`: script expects -patch|-unpatch as 
argument"
+                exit 1;;
+esac
+
+exit 0
+
+@DPATCH@
+=== modified file 'extconf.rb'
+--- a/extconf.rb       2004-01-08 20:13:07 +0000
++++ b/extconf.rb       2011-09-12 18:06:43 +0000
+@@ -15,7 +15,9 @@
+   ENV['PKG_CONFIG_PATH'] = '/usr/local/lib/pkgconfig/'
+ end
+ 
++$CFLAGS  += ' ' + `#{pkg_config} glib-2.0 --cflags`.chomp
+ $CFLAGS  += ' ' + `#{pkg_config} sary --cflags`.chomp
++$LDFLAGS += ' ' + `#{pkg_config} glib-2.0 --libs`.chomp
+ $LDFLAGS += ' ' + `#{pkg_config} sary --libs`.chomp
+ 
+ if have_header('sary.h') &&
+


--- End Message ---
--- Begin Message ---
Source: sary-ruby
Source-Version: 1.2.0-3.1

We believe that the bug you reported is fixed in the latest version of
sary-ruby, which is due to be installed in the Debian FTP archive:

libsary-ruby1.8_1.2.0-3.1_i386.deb
  to main/s/sary-ruby/libsary-ruby1.8_1.2.0-3.1_i386.deb
sary-ruby_1.2.0-3.1.diff.gz
  to main/s/sary-ruby/sary-ruby_1.2.0-3.1.diff.gz
sary-ruby_1.2.0-3.1.dsc
  to main/s/sary-ruby/sary-ruby_1.2.0-3.1.dsc



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 641...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ralf Treinen <trei...@debian.org> (supplier of updated sary-ruby package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Fri, 17 Feb 2012 16:30:23 +0100
Source: sary-ruby
Binary: libsary-ruby1.8
Architecture: source i386
Version: 1.2.0-3.1
Distribution: unstable
Urgency: low
Maintainer: Masahito Omote <om...@debian.org>
Changed-By: Ralf Treinen <trei...@debian.org>
Description: 
 libsary-ruby1.8 - A ruby binding of sary
Closes: 641358 652800
Changes: 
 sary-ruby (1.2.0-3.1) unstable; urgency=low
 .
   * Non-maintainer upload
   * add patch 50_fix_multiarch_ftbfs.dpatch to fix location of glib-2.0
     that changed in the multiarch transition. Thanks a lot to Clint Byrum
     <cl...@ubuntu.com> for the patch! (closes: #641358, #652800)
Checksums-Sha1: 
 839f9df2c80ec3ef5c4059c4fd0dfebeb90b079b 1093 sary-ruby_1.2.0-3.1.dsc
 7dca9b3279fc4efc9be845595d229a80b8066086 27261 sary-ruby_1.2.0-3.1.diff.gz
 7b65246f810e2bf5932cb7e2a787009021628e55 14844 
libsary-ruby1.8_1.2.0-3.1_i386.deb
Checksums-Sha256: 
 509dd5a504da4df7b155a483935c20fc34dc0fc56da7ad8b9c160cdcf966daf0 1093 
sary-ruby_1.2.0-3.1.dsc
 52db70d43d4fd8839063e610174b9a14f50d077c31dc275fc8bee8dd50f9e612 27261 
sary-ruby_1.2.0-3.1.diff.gz
 75fe59f82ace5bc7fdf9ccfa8b91bbfb0b0383127b558ac54377538e16178555 14844 
libsary-ruby1.8_1.2.0-3.1_i386.deb
Files: 
 76db63dd4629383c1b7e5dfe9a36a004 1093 ruby optional sary-ruby_1.2.0-3.1.dsc
 4fbeb1e3605ee4fdc12c18083b91d7c6 27261 ruby optional 
sary-ruby_1.2.0-3.1.diff.gz
 95ef558490c498c576ddcdf561b6bc57 14844 ruby optional 
libsary-ruby1.8_1.2.0-3.1_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk8+d4MACgkQtzWmSeC6BMEaZQCgjc5MWjHvD8HEFe/yU7fGi3iD
x+gAoJxh0Pc9vSDuXJxTxaRJ+q38NYjG
=uOOt
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to