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

Uploaded logtrend-linuxagent 0.82.2-1 (m68k) to ftp-master



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Wed, 24 Jul 2002 14:41:53 +1000
Source: logtrend-linuxagent
Binary: liblogtrend-agent-perl liblogtrend-action-perl logtrend-agentdescr liblogtrend-crypto-perl logtrend-linuxagent
Architecture: m68k
Version: 0.82.2-1
Distribution: unstable
Urgency: low
Maintainer: buildd m68k user account <buildd@ax.westfalen.de>
Changed-By: Jean-Francois Dive <jef@debian.org>
Description: 
 liblogtrend-action-perl - Perl module for logtrend agents
 liblogtrend-agent-perl - Perl modules for logtrend agents
 liblogtrend-crypto-perl - Crypto perl module for logtrend agent
 logtrend-agentdescr - Perl utils for logtrend agents
 logtrend-linuxagent - Perl daemon for linux box monitoring
Closes: 140775
Changes: 
 logtrend-linuxagent (0.82.2-1) unstable; urgency=low
 .
   * New upstream version.
   * Fixed some dependencies problems.
   * Added new perl library package: liblogtrend-crypto-perl for crypto
     supports.
   * Fixed return value problem in generic agent code (Agent.pm::New).
   * Fixed init return value handeling.
   * Fixed documentation path.
   * Fixed spelling in agentdescr (closes: #140775).
   * Fixed access right for /etc/logtrend/keys
Files: 
 13687d0e54e3819e0ecb389667a78756 20844 net optional logtrend-linuxagent_0.82.2-1_m68k.deb
 5c30e5eccc9d7b2609a879163cf1d4ff 13122 net optional liblogtrend-action-perl_0.82.2-1_m68k.deb
 5939e9178dbf13a6f4d72fc2d12ac17c 30262 net optional liblogtrend-agent-perl_0.82.2-1_m68k.deb
 df9c99c8bfa79fdaba6c0ed89035f947 8522 net optional liblogtrend-crypto-perl_0.82.2-1_m68k.deb
 aaa43398d678c02ed44131924a1a912d 4980 net optional logtrend-agentdescr_0.82.2-1_m68k.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Made with pgp4pine 1.75-6

iD8DBQE9TEeGWgZ1HEtaPf0RApfkAJ9Ho6KpqPE7ACFcTQbpxAu5PhJq4ACeLbMm
HJXkc3CGObkd98kOYMUsHWI=
=ieGG
-----END PGP SIGNATURE-----






Reply to: