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

Accepted r-cran-uuid 0.1.2-7 (source amd64) into unstable



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

Format: 1.8
Date: Tue, 25 Oct 2016 20:09:47 +0200
Source: r-cran-uuid
Binary: r-cran-uuid
Architecture: source amd64
Version: 0.1.2-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers <debian-science-maintainers@lists.alioth.debian.org>
Changed-By: Gordon Ball <gordon@chronitis.net>
Description:
 r-cran-uuid - Tools for generating and handling UUIDs
Changes:
 r-cran-uuid (0.1.2-7) unstable; urgency=medium
 .
   [ Gordon Ball ]
   * Update Standards-Version to 3.9.8
   * Convert to debhelper
 .
   [ Andreas Tille ]
   * Use the canonical CRAN URL for the homepage
Checksums-Sha1:
 72155b5b9235ccd6987cbb4a18e1ae1433a45835 2030 r-cran-uuid_0.1.2-7.dsc
 d0d49dba61da605efd76aac16c5793f77e7886d3 2728 r-cran-uuid_0.1.2-7.debian.tar.xz
 7fab7a131b297dc0d5ab9af6138b7b5b4d92aae7 17152 r-cran-uuid-dbgsym_0.1.2-7_amd64.deb
 7055c5b7bc2ab0fb8dfec0af2a957c48c87e396b 15158 r-cran-uuid_0.1.2-7_amd64.deb
Checksums-Sha256:
 f57b6c625cba05f2b978e2638c59b424d34c79c93ba19f5e88f639f2f5475858 2030 r-cran-uuid_0.1.2-7.dsc
 e7aa902e010d9d3c547eafc420e596b9f8abab5469644f02265f7d228a1ea30e 2728 r-cran-uuid_0.1.2-7.debian.tar.xz
 85e26e2dc732d2cd12973761e31978987a5c5ccfabc858f46cc6ba44c9f58e98 17152 r-cran-uuid-dbgsym_0.1.2-7_amd64.deb
 7eb08b0b14a38754a559172428f5a1920ad1584da7a197aebfd0eeff598f3091 15158 r-cran-uuid_0.1.2-7_amd64.deb
Files:
 7354c8a1a55af536f81348b1c0dc4936 2030 gnu-r optional r-cran-uuid_0.1.2-7.dsc
 99bfe8a36b7e57b9249879cc180eba95 2728 gnu-r optional r-cran-uuid_0.1.2-7.debian.tar.xz
 7ff862814ace2321cf24a6550490e6ed 17152 debug extra r-cran-uuid-dbgsym_0.1.2-7_amd64.deb
 617b694879d86ce205fb20f091d7545c 15158 gnu-r optional r-cran-uuid_0.1.2-7_amd64.deb

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

iQIcBAEBCAAGBQJYHGpMAAoJEFeKBJTRxkbRyekP/Rh6cGxnKQNPx7Fl8hdI0pKR
+wiLWEd9meUtCZJum8NpqbbIyjO2LL/ifT2tmVkbmLm+0DSGQl87BdTy5Ryl0Zyh
WhtGE+VO2yUKDLAx2fGgxcY+Nbwh3dbGh+sLIVJFWX1ZY+z2XrdpI9Im86HSL/3J
cieZzShPf+zeGTH2rXT2xHeIO0tl3hxebzE3gB9OmTuERbbu1J0QkJ10c8PILwhh
k1Y/SCGQEa7PIyyYi8DITSVBUbXrfgg2APzj21QmQQgRvWm7Srljh9LOt9NM/00k
BBnM5jO4PCl5kwHltoCTLNdhcRPkUOVl3FDaM0j4OkMtcAhau4b1YR6b2FOmSDGB
hy1SWj3qozed7cQOYWknvSYmgik57rYIQMeZ14bYj0yN+WDKHGcOQp8l2pxbasdX
hsWJHpKpBaR2KZPHsb+PgUKUSNw8ex9MNIbmuzqbviBai28gze39bYGO6DONP7uM
fEubAmjPJ9UpYMK41xEqqn4RF32Io6LwKt/HEAHUzPQZ2L+wukHWVDVXtpqI9MNU
4qoilSWodWzCi/AIGxZu+bGxQfoyTSoTFaFwsbcrf7HDT1HGVzbOgEN/+SgJB+bt
cGerFZs7wteUHBY0B9bhg3WWfIX0pshQ9P5t65dj72bosRGfk2+KIzWc7xV1ern3
mN9kYlGZY6biclIyi0FK
=IrUn
-----END PGP SIGNATURE-----


Reply to: