Accepted ruby-soap4r 2.0.5-3 (source all)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Mon, 06 Jan 2014 17:50:04 -0300
Source: ruby-soap4r
Binary: ruby-soap4r
Architecture: source all
Version: 2.0.5-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers <pkg-ruby-extras-maintainers@lists.alioth.debian.org>
Changed-By: Antonio Terceiro <terceiro@debian.org>
Description:
ruby-soap4r - SOAP library for the Ruby programming language
Closes: 725672 730912
Changes:
ruby-soap4r (2.0.5-3) unstable; urgency=medium
.
[ David Suárez ]
* Fix failing tests on ruby2.0 (Closes: #730912)
* debian/source/options: remove 'single-debian-patch' options and add
'unapply-patches' one
.
[ Antonio Terceiro ]
* Don't use ruby-libxml based parser
added debian/patches/dont-use-libxml-based-parser.patch.
The parser seems to be written for a old version of ruby-libxml and my
quick attempt at fixing it didn't work. My level of patience with
anything that involves XML is quite low, so it's possible that the
problem is still properly fixable. (Closes: #725672)
Checksums-Sha1:
1d9a93e26aca4428958c4847b6a107258d9a0bf4 2048 ruby-soap4r_2.0.5-3.dsc
b0d5e61fce9566837ec404e3984b4c7d63580607 4531 ruby-soap4r_2.0.5-3.debian.tar.gz
cc69e3d4a0a36110191114e01ec2326b2dad30f7 96272 ruby-soap4r_2.0.5-3_all.deb
Checksums-Sha256:
194c4396e54d280dbe2ef1fdba3f23f785feafa1cbed71ef50f9e526e6a93d74 2048 ruby-soap4r_2.0.5-3.dsc
b662b28eddc83d9c61f93c96b3e0e0c5b382e0227b18a3c1b8995cb9566f02c4 4531 ruby-soap4r_2.0.5-3.debian.tar.gz
2a5a46c6ae049257701912755202dd2210594ca9c4d50159831611861eb70fd3 96272 ruby-soap4r_2.0.5-3_all.deb
Files:
167a366d64c012978393a1728222389f 2048 ruby optional ruby-soap4r_2.0.5-3.dsc
a1e6c4b35552e958c38a03bddb560846 4531 ruby optional ruby-soap4r_2.0.5-3.debian.tar.gz
4e221e0e16c7da24b8d52d5574c6d23f 96272 ruby optional ruby-soap4r_2.0.5-3_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)
iQIcBAEBCAAGBQJSyxsmAAoJEPwNsbvNRgveFKQQALas9ry20kEQRa8O96owkk9M
435Xd03RACZSr6EGw65QbsvKYAR7JKRqDZ0pevTmySc/XbprYS1K0uWjgeLalJ1b
qEWhSwep4JT3VSF/j5dUx+S73JufWAt1anMA0TFfxZVAlOAcJ6/9bNnSqqCX1o36
fJYOEfFUyMsU/OtmSBQGUQXMTzh+UUa9ypwNVV+omqqIzVQY213Vo0AFp0qbK0v+
X0k7hgBkGajJgVZdT9rsi32dgOCokLDRmHGd9GCHKR61i6OYdqdMvFlg/GGe/d02
pkUhqSlZcmcGrW1k0sdmI0W3mFMtEQwNvbgyKb++XEaIyLsTHQz5wJLvsrpS+9QA
oQeShEwW5D+BFrC95iAUNWUz5muo/CJ/kE4HXNJuLzsJP6sb6i/1z+6+2ur+zTLq
fhpx0+fhdHJBMn8cxX84Vvzw1/YJY85zB5nYmflN+kWRr2ocv5pnluvDsjp7laqG
6LmXNihHRPGOcSR0oF+lF5UjnMBvLV6cB6FsX4PrW2jh7/GpfpcE8VxE1kT4sM95
7EkC0RpBdm0BPHQEMNyrZbRRDeeeFsKiD5bze3EBteXgFeLBL2q4ZXz/ma/n0klY
XFE6TznRwcMjdet8f7e9VAsMWd3Rrsp54zas+DFjKP9UKTNd9zPAfXXcESA2uOZm
o44c6QotSzBoMJXSOWRr
=H/yE
-----END PGP SIGNATURE-----
Reply to: