Uploaded xinetd 2.1.8.8pre6-1 (alpha) to master
-----BEGIN PGP SIGNED MESSAGE-----
Format: 1.6
Date: Tue, 4 Jan 2000 23:54:08 +0100
Source: xinetd
Binary: xinetd
Architecture: alpha
Version: 1:2.1.8.8pre6-1
Distribution: unstable
Urgency: low
Maintainer: AlphaBuildd/John Goerzen <buildd@complete.org>
Description:
xinetd - replacement for inetd with many enhancements
Closes: 53865
Changes:
xinetd (1:2.1.8.8pre6-1) unstable; urgency=low
.
* New upstream version, packaged only to fix the Y2K glitch in the
log file, closes: #53865.
* Adopted/tookover the package :) I hear Norbert is around, but he
hasn't contacted anyone regarding the package yet.
* Introducing debconf support, to ask about converting the config file,
and to warn about update-inetd malfunctioning. However, I didn't remove
the old method of asking the questions yet, just in case debconf
doesn't exist. Only Recommends: debconf. Plus, I had to re-route all
the messages to &2, because of debconf.
* Added the missing `k' in `syslogd' recommendation (doh!). Added
Build-Depends: libwrap0-dev.
* Moved the whole contents of preinst to postinst (that is, stopping of
inetd and portmap, and creating the diversion of inetd init file),
no need to abuse preinst for that.
* Use --background option for start-stop-daemon, to speed up loading,
thus having to depend on dpkg >= 1.4.1.17.
* Fixed some details in postinst, init.d, config, and copyright files.
Files:
1ccc2f6a02cedbfff48809d0c61be529 121910 net optional xinetd_2.1.8.8pre6-1_alpha.deb
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3a
Charset: noconv
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface
iQEVAwUBOICgt9YJEdzpssC9AQFQWgf/WxZrnFCydhKZPwjMQffABhfJOADq6AQn
Jd8/hsspczLSMgPk48/rIHwyLNFbH3i+jP+8KWAEIcpj24v3avtBRYN4tbP8tN5b
Vq1frygacH5I/7oTN94Az0Zp91Dpplv5GV+jKKP0enQLSIe2Ea2jU93xGay0fRsV
x7NOPsadTvxaCJO07jr0dUUr0pxhRE2QmhYSrpQeAjImSmrX2tfYugwqSa0YcDta
RTaRIuECzaM85NCZx2pFzjOLD0jYXYss0zPtT7XoY+tAbXEoEas1Gi48p4nHo387
YsoqrnlwqZqNn3klb58k4iHI266RLgI1xWSfUKcAbX3P5FpbWZ7ktA==
=JgYR
-----END PGP SIGNATURE-----
Reply to: