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

Accepted ostree 2017.12-2~bpo9+1 (source) into stretch-backports



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

Format: 1.8
Date: Fri, 27 Oct 2017 12:57:37 +0100
Source: ostree
Binary: gir1.2-ostree-1.0 libostree-1-1 libostree-dev libostree-doc ostree ostree-tests
Architecture: source
Version: 2017.12-2~bpo9+1
Distribution: stretch-backports
Urgency: medium
Maintainer: Utopia Maintenance Team <pkg-utopia-maintainers@lists.alioth.debian.org>
Changed-By: Simon McVittie <smcv@debian.org>
Description:
 gir1.2-ostree-1.0 - content-addressed filesystem for operating system binaries (intro
 libostree-1-1 - content-addressed filesystem for operating system binaries (libra
 libostree-dev - Development files for the libostree library
 libostree-doc - Development documentation for the libostree library
 ostree     - content-addressed filesystem for operating system binaries
 ostree-tests - content-addressed filesystem for operating system binaries - test
Changes:
 ostree (2017.12-2~bpo9+1) stretch-backports; urgency=medium
 .
   * Rebuild for stretch-backports
     - debian/gbp.conf: Adjust for this branch
 .
 ostree (2017.12-2) unstable; urgency=medium
 .
   * Disable gtk-doc if we are not going to build libostree-doc,
     in particular for architecture-specific builds. Note that it remains
     in Build-Depends (not Build-Depends-Indep) because it is also needed
     for gtkdocize during dh_autoreconf.
     - In particular this might fix FTBFS on sparc64, where highlight(1)
       fails.
   * d/p/2017.13/lib-core-Init-struct-stat-buffer.patch,
     d/p/2017.13/lib-sysroot-Fix-pointer-going-out-of-scope-in-unlock-code.patch,
     d/p/2017.13/lib-deploy-Ignore-FIFREEZE-FITHAW-errors-when-already-in-.patch,
     d/p/2017.13/lib-deploy-Use-_exit-for-FIFREEZE-watchdog.patch,
     d/p/2017.13/lib-deltas-Check-cancellable-during-processing.patch,
     d/p/2017.13/lib-utils-Check-for-invalid-UTF-8-in-filenames.patch,
     d/p/2017.13/Cope-with-xattr-syscalls-raising-EOPNOTSUPP.patch,
     d/p/2017.13/lib-sysroot-Fix-error-handling-when-mounting-overlayfs-fa.patch,
     d/p/2017.13/lib-repo-Properly-handle-NULL-homedir-when-signing-commit.patch,
     d/p/2017.13/fdio-allow-NULL-for-fstatat_allow_noent-stbuf.patch,
     d/p/2017.13/lib-repo-Fix-loading-commitstate-with-parent-repos.patch:
     Add various bugfix patches from upstream
     - In particular, dealing with the possibility that EOPNOTSUPP != ENOTSUP
       should fix test failures on hppa.
   * d/p/2017.13/tests-Add-test-pull-bareuseronly.patch:
     Add more test coverage from upstream
     - d/rules: Make the new test executable
   * d/test.sh: Clean up ostree-trivial-httpd processes
   * d/test.sh: Don't repeat build-time tests if they fail once. They seem
     to be somewhat reliable now.
Checksums-Sha1:
 57ccee34f366556249d61094cf03d83822c0ec8f 3025 ostree_2017.12-2~bpo9+1.dsc
 5eed5439e92cbb94d0a8117769b06641cb4b4985 26928 ostree_2017.12-2~bpo9+1.debian.tar.xz
 36e2de62dd0d9477d4b1f42e985830079d829b26 11418 ostree_2017.12-2~bpo9+1_source.buildinfo
Checksums-Sha256:
 7fb83875c405b2d2ccdd77ca1c7237f5512b63d38bae82abd36e0e407a9f208d 3025 ostree_2017.12-2~bpo9+1.dsc
 59ce4b23d3877f7b620d5935555c61f20d9421e27cbf7b3e2b4ac54aeefd0a88 26928 ostree_2017.12-2~bpo9+1.debian.tar.xz
 76a9cd099a9b543a7968b6be3ea53aab3276cc06058aa72c836cc05d3674d2bd 11418 ostree_2017.12-2~bpo9+1_source.buildinfo
Files:
 e1c11fb6aabaeca22652fd6d7386e5ef 3025 admin optional ostree_2017.12-2~bpo9+1.dsc
 ca939ddd74ee295fe5a19351c04d6123 26928 admin optional ostree_2017.12-2~bpo9+1.debian.tar.xz
 9cd04cbe37da75cb749c64031ce04eed 11418 admin optional ostree_2017.12-2~bpo9+1_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAln5vcgACgkQ4FrhR4+B
TE/6Pg/9GtefdI0sEAtUigZ3PLG4EaVHq5RuMo4IjGf60osSf9LE2fPeYzccaXPn
KvbOpKqofETGo9eB8ougVMjzxOUZb/8K+QXBnYrHsuGctn7VUCmochJHn5D7wRdZ
CuU+AcoQZ4grsNlmcfDU2rJXuBoEkEppNFmQsz6Ervt4P113CC9aE+hv6VRf0K5P
Grhq7wQt6gfGP8oJSiJ9qGG8ZynG2wkql634PxKT5KApw1iIjC5VX2EvDpl9RS/r
U+l2gmypM+9zfQDl01BylJR3TbCs1ar4ahbo8KIhSh+OWs+tqP+Q/sOyxGr7doFz
WeeU2wVz3miqkY0O40rBOIQpn3oUn4uzoRpa2u1fvR5wSRM8qGpP4rDo/qKFxsd2
FcqOdKV1NUmVIvsCUfR4norewMlcABQ+p8XKl2CRZQf/seGFhInk3G8JWSlqnoof
mEOSR4L1HMd8zVMTwrK1G0pEdrBg8qB26oqve2OlFtINHlEbpE3oRcVsZhVDzw4g
8kEoiD6YmfLkwnSS6+AvX92SnpZfKaC5/Cem6m8HG0T1osHWAd36yxEl5Ah40Crv
KRozk95ZsHOnEUYPjh/eHYAWR7Mnr1K7gP9m7hPK1feDiMrAQ5KU642iChuxYMH3
Ge5GRJ93OHK+I7XiHz6INKV+tqVz4An4hIhGcJ7A51wjEO9LG9E=
=JPri
-----END PGP SIGNATURE-----


Reply to: