Accepted afbackup 3.5-1 (source all i386)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Thu, 14 Dec 2006 23:01:40 +0100
Source: afbackup
Binary: afbackup afbackup-client afbackup-common
Architecture: source all i386
Version: 3.5-1
Distribution: experimental
Urgency: low
Maintainer: Torsten Werner <twerner@debian.org>
Changed-By: Torsten Werner <twerner@debian.org>
Description:
afbackup - Client-Server Backup System (Server side)
afbackup-client - Client-Server Backup System (Client side)
afbackup-common - Client-Server Backup System (common files)
Changes:
afbackup (3.5-1) experimental; urgency=low
.
* New upstream release.
* Move patches directory into debian directory.
* Add XS-X-Vcs-Svn header.
* Refreshed FreeBSD patch.
* Upstream has removed its own debian/ directory because I have requested
that.
* Add patch no_trigraph.diff which removes invalid trigraphs.
* Document all patches.
Files:
beb434d79c4cf0d00cded44e95f876ce 733 utils optional afbackup_3.5-1.dsc
f32f9a4798682001d48f68c407249dff 996262 utils optional afbackup_3.5.orig.tar.gz
e7e462fca74905593b5833444d07a71b 12242 utils optional afbackup_3.5-1.diff.gz
9364cd0efc2d1a43113d0d12060690e3 316908 utils optional afbackup-common_3.5-1_all.deb
37b021617a11b0cefe76438630833740 419332 utils optional afbackup_3.5-1_i386.deb
11885b36135c4d8fbf5ae64b26e8164b 513556 utils optional afbackup-client_3.5-1_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFFgczZfY3dicTPjsMRAmvWAKCWP19bBXJrlyvJBbnWppCRPKI27ACeI8j6
7eiDFhtaVpx1aU6iy+ilvbQ=
=lDLb
-----END PGP SIGNATURE-----
Accepted:
afbackup-client_3.5-1_i386.deb
to pool/main/a/afbackup/afbackup-client_3.5-1_i386.deb
afbackup-common_3.5-1_all.deb
to pool/main/a/afbackup/afbackup-common_3.5-1_all.deb
afbackup_3.5-1.diff.gz
to pool/main/a/afbackup/afbackup_3.5-1.diff.gz
afbackup_3.5-1.dsc
to pool/main/a/afbackup/afbackup_3.5-1.dsc
afbackup_3.5-1_i386.deb
to pool/main/a/afbackup/afbackup_3.5-1_i386.deb
afbackup_3.5.orig.tar.gz
to pool/main/a/afbackup/afbackup_3.5.orig.tar.gz
Reply to: