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

Accepted php-horde-imap-client 2.28.0-1 (source all) into unstable



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Mon, 04 May 2015 21:44:08 +0200
Source: php-horde-imap-client
Binary: php-horde-imap-client
Architecture: source all
Version: 2.28.0-1
Distribution: unstable
Urgency: medium
Maintainer: Horde Maintainers <pkg-horde-hackers@lists.alioth.debian.org>
Changed-By: Mathieu Parent <sathieu@debian.org>
Description:
 php-horde-imap-client - ${phppear:summary}
Changes:
 php-horde-imap-client (2.28.0-1) unstable; urgency=medium
 .
   * Update Standards-Version to 3.9.6, no change
   * New upstream version 2.28.0
Checksums-Sha1:
 8bbfdefefb7bd704b97acbc25030c8266f91fb5b 2096 php-horde-imap-client_2.28.0-1.dsc
 bd020a8de274be74d223f8c990afc3af4477c5b5 236045 php-horde-imap-client_2.28.0.orig.tar.gz
 25d648996fd8e88e70d7b03060801c5fef8d0d26 3068 php-horde-imap-client_2.28.0-1.debian.tar.xz
 fba37bfc6a12e5bd4dcf275094c7ea813df8e088 202424 php-horde-imap-client_2.28.0-1_all.deb
Checksums-Sha256:
 cf46e708092da8b21ccbd5ab16d318aa875dde5264df094b3d8dcb5053701737 2096 php-horde-imap-client_2.28.0-1.dsc
 8d826bfc8199ecf6d777d2b8766bb765660ccecc9f161985f6bcc21c9b9a0a77 236045 php-horde-imap-client_2.28.0.orig.tar.gz
 bca4df02162a1b8bde8d1174677fb96128e2e454e8595653cd5bdba4e40f5a05 3068 php-horde-imap-client_2.28.0-1.debian.tar.xz
 07dda1637ef7ec3d7e7ee6db71c6c294dd1393a5f4d07d665fa766058b5b36ad 202424 php-horde-imap-client_2.28.0-1_all.deb
Files:
 1bac3164fe16706cea41246d28ddd91f 2096 php extra php-horde-imap-client_2.28.0-1.dsc
 82572967032a86824ed561c185eef97d 236045 php extra php-horde-imap-client_2.28.0.orig.tar.gz
 7b22fce49dbc12975b510687aa414577 3068 php extra php-horde-imap-client_2.28.0-1.debian.tar.xz
 8e603b3034383a4503054571e165afcd 202424 php extra php-horde-imap-client_2.28.0-1_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJVR8zGAAoJEK4DmARmaB+l7PcQALfxyFA+BIzJsCDf9XJ3F3G+
5wwHKNuB1iIJbd4g24g2cmrfCnwnalMRkIn6+sf0/LcHMZupmKWLzWtUhN9lvhJn
y6qktK67yplV8292yWZo/eHljMmD8508J5lr7wV5P3Un5WStooDrCeOG1+d4kG4F
2OU7/mYtY6R/JYX0eGwZ+73pXkqugdoRBmMWaSBYHXqKgT1s38Mr49wZ2X2hIwo0
fJlHt1NHYL5OagLpTNA1pyuAU+dK7lIg0CigGG1H6YixE1hRRSa1shx0L1Z/tEgV
EZP06nsOliC2nIISHcipOu1j9Dx2RPzV/c09yoik5W+CnrimeReuxfblvAfXNIZD
k6DnBimgAIFKkhboURCgQKY2nmASRx3eHn3BV5wahFaMVMfO3NgmYAOpXS/O0YSs
xHqcQ/g6lIFLhGX8LbMaZGUbPqiyUoiQFep3js+woPmC8GRA6t9xdzbJoXEqcDzC
KL4QHnv1Lmk0+PUHzel1hDVhPpLk21ExbzDSVj4QA3EzbSLmWvI0HCzEeQWgXG6c
mmeUdubtCJg7qgL7JW7nQ42DUlh4ridaYJ7gXerprkhLYAS8mUSlcucTpZvpNaPi
fEwTC6jl5xV5kv4H3OpfFac+BXjXzHCEzlrfFZ/9vLR4JS63FVPzPABb3I4HQw/i
1YYZJ1cV1OSs4J9gGPs3
=XkAS
-----END PGP SIGNATURE-----


Reply to: