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

Uploaded dhcp3 3.0+3.0.1rc9-2 (sparc) to ftp-master



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

Format: 1.7
Date: Thu,  9 May 2002 23:22:20 -0400
Source: dhcp3
Binary: dhcp3-relay dhcp3-client-udeb dhcp3-client dhcp3-server dhcp3-dev dhcp3-common
Architecture: sparc
Version: 3.0+3.0.1rc9-2
Distribution: unstable
Urgency: low
Maintainer: Debian/sparc Build Daemon <buildd@sparc.debian.org>
Changed-By: Eloy A. Paris <peloy@debian.org>
Description: 
 dhcp3-client - DHCP Client
 dhcp3-client-udeb - DHCP Client for debian-installer (udeb)
 dhcp3-common - Common files used by all the dhcp3* packages.
 dhcp3-dev  - API for accessing and modifying the DHCP server and client state
 dhcp3-relay - DHCP Relay
 dhcp3-server - DHCP server for automatic IP address assignment
Closes: 146450
Changes: 
 dhcp3 (3.0+3.0.1rc9-2) unstable; urgency=low
 .
   * Fix silly mistake in dhclient-script. This slipped in when I
     prepared 3.0.1rc9 in a hurry. (Closes: #146450)
Files: 
 4aa83b9e657235fb6281210f3f28e33d 465244 net optional dhcp3-server_3.0+3.0.1rc9-2_sparc.deb
 8c572f6fd6604ec1e23dc80e1e4ebb98 178184 net optional dhcp3-common_3.0+3.0.1rc9-2_sparc.deb
 05dfa0d2eedefd1495ddbc2f2e0c4d06 87150 devel optional dhcp3-dev_3.0+3.0.1rc9-2_sparc.deb
 e68111e2193c3438bca50ded7523bf28 375128 net optional dhcp3-client_3.0+3.0.1rc9-2_sparc.deb
 a7057be98eaedb9d39fe12724caa8bc5 270994 net optional dhcp3-relay_3.0+3.0.1rc9-2_sparc.deb
 dd193d0c9975b435260f7a769235aba4 154020 debian-installer optional dhcp3-client-udeb_3.0+3.0.1rc9-2_sparc.udeb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.6 <http://mailcrypt.sourceforge.net/>

iEYEARECAAYFAjzbujUACgkQgD/uEicUG7AcEwCgw7dePSskO8ZAj5gcEszBJMRI
DgUAoOIxJ9/8y0yUNNZV4U/JLA26kjs3
=RYk3
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to debian-devel-sparc-changes-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org



Reply to: