Your message dated Fri, 21 Apr 2017 19:19:01 +0000
with message-id <[email protected]>
and subject line Bug#842606: fixed in ostree 2016.15-5
has caused the Debian Bug report #842606,
regarding ostree pull or pull-local intermittently does not terminate (e.g.
FTBFS with exit status 124)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
842606: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842606
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: ostree
Version: 2016.12-1
Severity: important
"ostree pull" and related commands sometimes lock up (deadlock?) and do
not terminate. This can sometimes also be seen in Flatpak, which uses
ostree behind the scenes.
When tests are run at build-time, we use timeout(1) to kill each test
after 30 minutes. This lockup manifests as exit status 124, for example
in these build logs:
https://buildd.debian.org/status/fetch.php?pkg=ostree&arch=amd64&ver=2016.12-1&stamp=1477511802
https://buildd.debian.org/status/fetch.php?pkg=ostree&arch=powerpcspe&ver=2016.12-1&stamp=1477523854
My speculation is that this might be another manifestation of the same
non-thread-safe communication (between the main thread and a libsoup
worker thread perhaps?) that is causing segfaults in "ostree pull"
(also visible in that amd64 log); but I have no evidence for this.
Unhelpfully, I cannot reproduce either the deadlocks or the segfaults
on-demand. If anyone can reproduce them reliably, backtraces and
debugging would be very useful.
ci.debian.net also appears to see timeouts in the tests reliably,
but I don't know how to retrieve useful debug information from there.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'),
(500, 'stable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ostree
Source-Version: 2016.15-5
We believe that the bug you reported is fixed in the latest version of
ostree, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Simon McVittie <[email protected]> (supplier of updated ostree package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Fri, 21 Apr 2017 18:03:13 +0100
Source: ostree
Binary: gir1.2-ostree-1.0 libostree-1-1 libostree-dev libostree-doc ostree
ostree-tests
Architecture: source
Version: 2016.15-5
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team
<[email protected]>
Changed-By: Simon McVittie <[email protected]>
Closes: 842606 860262
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 ostree library
libostree-doc - Development documentation for the ostree library
ostree - content-addressed filesystem for operating system binaries
ostree-tests - content-addressed filesystem for operating system binaries -
test
Changes:
ostree (2016.15-5) unstable; urgency=medium
.
* Tag all patches as having been applied upstream in 2017.1
* Backport an additional change from 2017.1 to put all libsoup use
in one thread, which seems to solve pulls getting stuck without
progress (Closes: #860262, hopefully also Closes: #842606)
Checksums-Sha1:
a202afb4d440d64d4c91e9dd7ceeb7f48022a9c5 2829 ostree_2016.15-5.dsc
6e28499b920c1e994a01c0a2332ffd23a8ff0b1d 19920 ostree_2016.15-5.debian.tar.xz
Checksums-Sha256:
6ebc779903fea685a8a3dec222d22f92d12c760f96243511ae1ac589191978f6 2829
ostree_2016.15-5.dsc
5bd45967e87b24919d2df9db79b188c32936d4cd938cdbcc4afe96ece115fc2a 19920
ostree_2016.15-5.debian.tar.xz
Files:
0b259bfc4b778269386ec8c37e3a9707 2829 admin optional ostree_2016.15-5.dsc
66e59285be7988ab9a9a3e2c1f877c7a 19920 admin optional
ostree_2016.15-5.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEE2pjyXAhxxJpZ6v8sTej/KmPHzJAFAlj6VSUACgkQTej/KmPH
zJB77w/+IcF/z2aFiHwLprjAO8/yKxUplv0MNg4O0GU7v7wI71mgKGlXE/WHMCp1
m0GxWhxNQk7cRJCAVmPvyqwJGWod7sq+ZsbN6pBYDSlcCLkgqHNqkUYKBcIICuzX
fLAL4Nuw1G6qlBek/vV2wGH0v33sarLDfYY4Hl9wNx6DBIy2i1EOfT88sK2Vmfly
j5uiNHKsFEUKN2qKtoqa+q6tbqCtA9xw+oO7ObzZms10Q3IYW9QW+GnP3f3IDLLw
qsh6aFWz/5FRrgmUdAEQWUDeLK273lPmuIbfW3MK6J81tsBDJWp2m91V1gtUTAD2
A9LzSMTPKbmgrKUCGW436KEtqL2kYkyREXk7bvMHGzqzs8mKNCqGVF7ugpTN/6L2
ZYJAROvqbT6DIaZIVXpL6TOcqZcWhPgUpgnDaHqiwIl+bMXB20f0s+nbUagKsrI/
pGW0vXao1wP4KRHKXZaZQUW58m9X2s+5gLGleDBc9C4G3+UxOPbv/Vissd/JOYor
Zusi2IHu6Gnf4GZm5IF8Xa6mUz8UNf4tsJ9cVEwM0cLKoUBKXi1+c3mCwjHbml8y
gsujaUD6ib64OygG8anAmoy9eYNZtlv0nMUjmAg1dmpExxK37Kq4rPkzVlrINz2S
jOH98N07eUbDXfmycBxZSw3FQJWJTd0jEn4qmvsrzn5cMIAreRA=
=ZjbQ
-----END PGP SIGNATURE-----
--- End Message ---
_______________________________________________
Pkg-utopia-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-utopia-maintainers
