Sync xiphos 3.1.1-2 (universe) from Debian unstable (main).
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xiphos (Ubuntu) |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
affects ubuntu/xiphos
status new
importance wishlist
subscribe ubuntu-
done
Please sync xiphos 3.1.1-2 (universe) from Debian unstable (main). This will fix bug #418341.
Changelog since current karmic version 3.1.1-1:
xiphos (3.1.1-2) unstable; urgency=high
* debian/control:
- Re-add "Provides: sword-frontend"
- Add "Suggests: sword-text"
- Xiphos depends on source-version xiphos-data (thanks Matthew Talbert)
- Bumped debhelper version to >= 7.0.50~
- Bumped standards version to 3.8.3
* debian/
- New file. Describing standard quilt
-- Dmitrijs Ledkovs <email address hidden> Mon, 24 Aug 2009 23:32:53 +0000
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iQIcBAEBCgAGBQJ
W5DBDpcjoVdiFwm
5RMTukMvN94fsko
lYfn4hwv+
uDhsfi1AFy7r2PZ
9adcNi4VvshsBO5
YZ+Uy5rFABHm5ro
u8C9dwkKIeURPlj
wRSgZvk1PvTngmJ
7SOtke2EBn+
PNqlTaFcoFd0uxv
lZK3HRbON0f1lX4
=XP6x
-----END PGP SIGNATURE-----
Thanks =) I hope you did notice that I was both the reporter and the Debian Uploader =)
Very quick to spot the upload.
I'm just not sure that the #418341 is present and haven't been able yet to set-up PIUPARTS. Can you please confirm that it is present on Ubuntu when upgrading gnomesword from jaunty to the karmic (and hense to xiphos) that this problem exists?