[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Uploaded fortify 1.2.6-2 (source i386 all) to nonus



-----BEGIN PGP SIGNED MESSAGE-----

Format: 1.5
Date: Sat, 12 Sep 1998 18:56:29 +0200
Source: fortify
Binary: fortify-unix-x86 fortify-linux-x86 fortify
Architecture: source i386 all
Version: 1.2.6-2
Distribution: unstable
Urgency: low
Maintainer: Roberto Lumbreras <rover@debian.org>
Description: 
 fortify    - World-wide strong cryptography for Netscape
 fortify-linux-x86 - Fortify stub files for linux-x86 architectures
 fortify-unix-x86 - Fortify stub files for unix-x86 (non-Linux) architectures
Changes: 
 fortify (1.2.6-2) unstable; urgency=low
 .
   * Postinst: update-alternatives needs to be run before trying to use
     fortify. (fixes: Bug #26628)
   * debian/rules: moved stub and index files to /usr/share/fortify
   * src/fortify.c: changed default Index file from ./Index to
     /usr/share/fortify/Index and morphs directory from . to /usr/share/fortify/
   * debian/rules: moved fortify binary to /usr/bin.
   * debian/postinst: changed the way fortifying is done; should fix: Bug #23564
   * moved linux/x86 stub files to a new package: fortify-linux-x86, Debian
     is not a x86-only OS.
   * Added dependency for fortify on one of the fortify-* packages.
Files: 
 20fb300baa08aed11b0428ca71a5621e 659 non-free optional fortify_1.2.6-2.dsc
 ad60501ed7488705620ffcea50243d03 5770 non-free optional fortify_1.2.6-2.diff.gz
 388008b6d9fc5dca00c2bd4c2c1a3250 30348 non-free optional fortify-linux-x86_1.2.6-2_all.deb
 440c7966cd722f8988e9c2b43c36232b 29358 non-free optional fortify-unix-x86_1.2.6-2_all.deb
 612da9e8f197973536b45f49861d058b 72422 non-free optional fortify_1.2.6-2_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: noconv

iQCVAwUBNfrKNDkbwlcUO+ORAQEJLAP9EY8uF3GaZ6081RIzT9LmI2AuEwWXt4hi
Gdlr2bvVdr34FZFzDSVvnsxAbJYGQpuyDaHPVpHVbhjvx0yIWWCsIjnsWArULijT
g/5okDhMcH34v3tSx7ywcolmAZ3QrqoUZm4eP5B8bdHeb/d7SlQVVMdai7aY4im9
jHXeQpbNu4Q=
=E9UA
-----END PGP SIGNATURE-----


Reply to: