2006
rhyme (0.9-6) unstable; urgency=low
* QA upload. * Package is orphaned (#363499); set maintainer to Debian QA Group. * Acknowledge NMU. Closes: #326303. * Switch to debhelper 5. * debian/rules: Pass CFLAGS to the Makefile for DEB_BUILD_OPTIONS=noopt. * debian/menu: Add. * debian/watch: Add. * Conforms to Standards version 3.7.2.
-- Matej Vela <vela@debian.org> Mon, 8 May 2006 09:58:33 -0500
2005
rhyme (0.9-5.1) unstable; urgency=low
* NMU * Rebuild against libreadline5-dev (Closes: #326303)
-- Don Armstrong <don@debian.org> Fri, 30 Dec 2005 23:30:14 -0800
2004
rhyme (0.9-5) unstable; urgency=low
* Conflict with surfraw: Many thanks to Ian Beckwith and Thomas Smith for
their work on the surfraw package. Since they moved all the surfraw
elvi to /usr/lib in version 2.0-1 back in November, the conflict is no
longer needed. I've made it versioned in case anyone has a previous
version on hold or something. My apologies for not having noticed this
sooner. (Closes: #201039)
-- Stephen Stafford <bagpuss@debian.org> Sun, 4 Apr 2004 10:41:33 +0000
rhyme (0.9-4) unstable; urgency=low
* Change where rhyme puts the GDBM files to /usr/lib/rhyme/
(Closes: #233436)
* Thanks to Steve McIntyre for poiting this out.
-- Stephen Stafford <bagpuss@debian.org> Wed, 18 Feb 2004 11:35:26 +0000
2003
rhyme (0.9-3) unstable; urgency=low
* fiddle with how we install the files to the build directory so my home
directory is no longer hardcoded into the binary. Sorry I missed this
one, a test on a different box would have caught it. Thanks to iain d
broadfoot <ibroadfo@cis.strath.ac.uk> for spotting this and suggesting a
fix. Your fix was pretty close Iain, except that the upstream Makefile
uses those variables as a place to install to as well as using them for
the produced binary. I'll have to find a better way to write that
Makefile one of these days. (Closes: #201217)
-- Stephen Stafford <bagpuss@debian.org> Mon, 14 Jul 2003 14:11:54 +0000
rhyme (0.9-2) unstable; urgency=low
* Conflict with surfraw. (Closes: #201039) Yes, this is a highly suboptimal solution. I'm not convinced that setting up something with alternatives is any better though. I could just rename the binary, but what to? Alternatively, surfraw looks effectively unmaintained. Which suggests either filing for its removal, or maintaining it myself. What to do, what to do.... Answers on a postcard please.
-- Stephen Stafford <bagpuss@debian.org> Mon, 14 Jul 2003 11:28:18 +0000
rhyme (0.9-1) unstable; urgency=low
* Initial Release. (Closes: #199881)
-- Stephen Stafford <bagpuss@debian.org> Thu, 3 Jul 2003 16:26:50 +0000