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

Format: 1.7
Date: Tue, 28 Nov 2006 23:55:52 +0000
Source: mldonkey
Binary: mldonkey-gui mldonkey-server
Architecture: source i386
Version: 2.8.2-1
Distribution: unstable
Urgency: low
Maintainer: Debian OCaml Maintainers <debian-ocaml-maint@lists.debian.org>
Changed-By: Samuel Mimram <[EMAIL PROTECTED]>
Description: 
 mldonkey-gui - Graphical frontend for mldonkey based on GTK
 mldonkey-server - Door to the 'donkey' network
Closes: 395068 397497 400216
Changes: 
 mldonkey (2.8.2-1) unstable; urgency=low
 .
   * New upstream release.
   - Should fix the DNS resolution problem, closes: #395068.
   - Removed newdns.dpatch, mlguistarter.dpatch and search.dpatch, integrated
     upstream.
   * mldonkey_users now uses "users2" section, closes: #397497.
   * Depending on dpkg (>= 1.13.24) in mldonkey-server to be sure that the
     --umask option of start-stop-daemon exists, closes: #400216.
Files: 
 f8ffac7c57e66742e6c8228610a61a6a 1084 net optional mldonkey_2.8.2-1.dsc
 640a5bd31794854057086573c2772aee 3203346 net optional 
mldonkey_2.8.2.orig.tar.gz
 aeb60e0eebf37223db0d45616a83df14 130981 net optional mldonkey_2.8.2-1.diff.gz
 65898ff655b17baab0067b6e1cba168b 2829768 net optional 
mldonkey-server_2.8.2-1_i386.deb
 2e71633a43c834e73b48131b79d08824 3286156 net optional 
mldonkey-gui_2.8.2-1_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFbM+pIae1O4AJae8RAkbTAJ0TOmv3D5Wsu4RxujvpIBB1Luaz7wCfVBoZ
X32Q2K1issW/sSjppFaEZLg=
=7fO+
-----END PGP SIGNATURE-----


Accepted:
mldonkey-gui_2.8.2-1_i386.deb
  to pool/main/m/mldonkey/mldonkey-gui_2.8.2-1_i386.deb
mldonkey-server_2.8.2-1_i386.deb
  to pool/main/m/mldonkey/mldonkey-server_2.8.2-1_i386.deb
mldonkey_2.8.2-1.diff.gz
  to pool/main/m/mldonkey/mldonkey_2.8.2-1.diff.gz
mldonkey_2.8.2-1.dsc
  to pool/main/m/mldonkey/mldonkey_2.8.2-1.dsc
mldonkey_2.8.2.orig.tar.gz
  to pool/main/m/mldonkey/mldonkey_2.8.2.orig.tar.gz


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to