Uploaded mule2 2.3+19.34-7potato1 (m68k) to erlangen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.6
Date: Tue, 7 Mar 2000 04:31:55 +0900
Source: mule2
Binary: mule2-wnn mule2-plain mule2-support mule2-supportel mule2-bin mule2-canna-wnn mule2-canna
Architecture: m68k
Version: 2.3+19.34-7potato1
Distribution: frozen
Urgency: high
Maintainer: Debian/m68k Build Daemon <buildd@kullervo.informatik.uni-erlangen.de>
Description:
mule2-bin - MULtilingual Enhancement to GNU Emacs -- support binaries
mule2-canna - MULtilingual Enhancement to GNU Emacs. (canna supported)
mule2-canna-wnn - MULtilingual Enhancement to GNU Emacs. (canna wnn supported)
mule2-plain - MULtilingual Enhancement to GNU Emacs. (plain binary)
mule2-wnn - MULtilingual Enhancement to GNU Emacs. (wnn supported)
Closes: 51731
Changes:
mule2 (2.3+19.34-7potato1) frozen; urgency=high
.
* use dbs_make becase mule2 have many patches.
* orig.tar.gz was modified, built with -sa.
* source packages is same as woody's, but removed IPv6 patch cos that
is new feature patch after freeze. (removed changes of -8)
* added alternatives as emacs.
* Fixed build problem on sparc arch. (closes: Bug#51731)
* Build-Depends: patch, debhelper (>=2), libwnn6-dev, libcanna1g-dev,
liblockfile-dev, xlib6g-dev, libncurses5-dev
is this right?
Files:
646f91bdcabfa35ab0456f9214442255 1537544 editors optional mule2-canna_2.3+19.34-7potato1_m68k.deb
45c8c10bb1700f618482a3476fe950ff 1699644 editors optional mule2-wnn_2.3+19.34-7potato1_m68k.deb
d75c282847494b0118d773d47338caae 1740058 editors optional mule2-canna-wnn_2.3+19.34-7potato1_m68k.deb
e3fb8fc396d68e8e53b11a80739d8419 1507864 editors optional mule2-plain_2.3+19.34-7potato1_m68k.deb
b8b7af0e8720d6e1132542d92a34184b 119116 editors optional mule2-bin_2.3+19.34-7potato1_m68k.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.0 (SunOS)
Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard <http://www.gnupg.org/>
iEYEARECAAYFAjjIyJUACgkQcS3JWD3FdveCoACeKzB9AAQ/dhABcGlJ9yEDoJY7
PDIAniSMcJ3NqYweGXGUG33JNavM2kLT
=wGEW
-----END PGP SIGNATURE-----
Reply to: