Uploaded dutch 0.1e-4 (source i386 all) to erlangen
Trying again... I deleted the previous upload soon after uploading it
because I noticed a dumb mistake. (I'd forgotten to actually install
the new postrm).
Other architectures may not want to bother compiling this, because
idutch (the arch-dependent part) is not touched at all.
If you do compile it, be sure to work around bug#18369 in ispell by
setting TMPDIR explicitly.
-----BEGIN PGP SIGNED MESSAGE-----
Format: 1.5
Date: Fri, 20 Mar 1998 16:55:56 +0100
Source: dutch
Binary: wdutch idutch
Architecture: source i386 all
Version: 1:0.1e-4
Distribution: frozen unstable
Urgency: low
Maintainer: Richard Braakman <dark@xs4all.nl>
Description:
idutch - The dutch dictionary for ispell, in new (August 1996) spelling.
wdutch - List of Dutch words in new (August 1996) spelling.
Changes:
dutch (1:0.1e-4) frozen unstable; urgency=low
.
* Use Charles Briscoe-Smith's postinst, prerm, and postrm scripts
for wdutch. This partially deals with the excessive prompting
mentioned in #7454 and #19600. A proper solution requires changing
all wordlist packages to use update-alternatives, but that is best
left for Debian 2.1.
* debian/rules: changed to install postrm script too.
Files:
a448e57e2b6574c55318058efe3dce07 707 text extra dutch_0.1e-4.dsc
7fbb312ef047a9c43d3f02be3fad4943 4552 text extra dutch_0.1e-4.diff.gz
1258595a55cf131b0b9316ad98edd59b 703492 text extra wdutch_0.1e-4_all.deb
c077a44750d43af0c651567d20eb0f77 1160454 text extra idutch_0.1e-4_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: noconv
iQDVAwUBNSwDDDI43/W5dqdJAQGtBgX/etKjXO+c7/aIR0PUCc8T9WRtemqtuhf7
225K/g8HAinSZO+cf7eAo7ieO+VKWhbH+YdiFd8c2BZ3MBM4jmjv86jHiMR3U5q/
amUUMACDELrAaPJNX4OCtkqhvBctj8D5L3oTkJq7azfn4VCdVpOchRv8UPTdiswG
B/fnJZJLHzXHXItiV7uoUeC/n/g3Ylb7TGVZY/4/kYkGwpWTUm67jHN7QLYIlRT5
d2KnfHlP6L8fgLkQV3u0pbt+WdDVFkzy
=laB9
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to debian-devel-changes-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: