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

Accepted liburcu 0.8.4-2 (source amd64)



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Thu, 03 Apr 2014 20:31:36 -0400
Source: liburcu
Binary: liburcu-dev liburcu2
Architecture: source amd64
Version: 0.8.4-2
Distribution: unstable
Urgency: low
Maintainer: Jon Bernard <jbernard@debian.org>
Changed-By: Jon Bernard <jbernard@debian.org>
Description: 
 liburcu-dev - userspace RCU (read-copy-update) library - development files
 liburcu2   - userspace RCU (read-copy-update) library
Closes: 743403
Changes: 
 liburcu (0.8.4-2) unstable; urgency=low
 .
   [ Michael Jeanson ]
   * [04cf85f] Fix FTBFS on amrel and armhf (Closes: #743403)
   * [b515ef6] Use dpkg-buildflags to build with hardened flags
Checksums-Sha1: 
 52e3593c14172ce98f8977232be00f83e0f6ee8e 1913 liburcu_0.8.4-2.dsc
 92040932cc52ebc27de1925de8d1d556ea53d03c 6184 liburcu_0.8.4-2.debian.tar.xz
 abe8d90fd1969534444e26e2e088191afd4dee22 478506 liburcu-dev_0.8.4-2_amd64.deb
 510f994f21cd2dd15a872139d024dfa4c97eb138 52224 liburcu2_0.8.4-2_amd64.deb
Checksums-Sha256: 
 4d65ca1c14adcfdf44eaf059e5dd0c188adcf48be07ef20fb2ce473791c24152 1913 liburcu_0.8.4-2.dsc
 bf01269f8a7048454edfe8d7e3410b1cf8b4bfa0dd986765df5220cba7880792 6184 liburcu_0.8.4-2.debian.tar.xz
 556c818a35ffeff1c41925e467cf40464f7dc8e51c3946bdae7cee21558937d0 478506 liburcu-dev_0.8.4-2_amd64.deb
 c531aef2d9e88f46b4629a71ce99511ff59b25a4f2c1de77bdeca14da2c92d0f 52224 liburcu2_0.8.4-2_amd64.deb
Files: 
 76e373808781ad14b0027e6827d16f96 1913 libs extra liburcu_0.8.4-2.dsc
 4f362f4995c8e27492c6c2a48030c956 6184 libs extra liburcu_0.8.4-2.debian.tar.xz
 7a80209655ebf4bb7d88461ac107a8ce 478506 libdevel extra liburcu-dev_0.8.4-2_amd64.deb
 ee9f1407e62d7e0fbc7f0872938a7dd9 52224 libs extra liburcu2_0.8.4-2_amd64.deb

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

iQIcBAEBCgAGBQJTPf3bAAoJEGl4Op6tU2EHclEP/ijeQ4ZHENjezgk4GsLN3SMA
2boLgNgG6tPEXUcNws2dLifM7rcifw5UtG5nbpBIdUKAKo5OULX4e492k6g4L+8p
DFgRwHFAIY5R/Blj0C53YaQ7gV7LaeS7gjLGOGN9Hws4ftt/u6S7tjfFLGk8gmtR
rE7VDAe6ygzZHI0RhflmzaNvqjeDJU0eC1YRkawjfQ4F+oMFRCgL+SXMj2xlSl/v
YZ3ZbHs0hgvzHX0UW6H3WurXQjYG/VbRMdqkJSoa1vbB9HDxdZqffBSO4A3VNlEt
veOXaA1aSWItQaDLh2wlYDNA2+L0FQMD2xOLT/ABLRX3MUe/S6+2rcaWJjdveYW5
oA5YVYm70I7Pq4Lq+vaC0NF+mv5ZpcaHrlgd42RWKihDq5bWHWudmFqk+yr6lsd2
J+PGArcEK9praLaFkwZpy+nq99aCaJ5As+GIEUZJLc9KrHptC+lyLOTLr9zXhZnV
rL29QWbBN08ZtSU/EJTcZ2OQsSOkybt82UXsFVdjjomTdAQ382YY4AINFbYf/ZM/
iQHj2x8UU3gyUKKOAA9WrjNhvhwyGtht10KuPgdOhd7M5QQZOW2F3VBH0aaHCq8C
UI0dG15QWZgTMGm1o0YvixnkhJlZsrpcLnug19B7In/a8XY6G7WjynYI33BU4PS9
Rt3A+hrjxJBzE+XCE0Ub
=m0Po
-----END PGP SIGNATURE-----


Reply to: