Your message dated Sun, 24 Jun 2018 15:38:32 +0000
with message-id <e1fx760-0006qc...@fasolo.debian.org>
and subject line Bug#902209: fixed in ostree 2018.6-3
has caused the Debian Bug report #902209,
regarding ostree: FTBFS on 64-bit big-endian: test failures: g_str_has_prefix: 
assertion 'str != NULL' failed
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 ow...@bugs.debian.org
immediately.)


-- 
902209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902209
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ostree
Version: 2018.6-1
Severity: serious
Tags: ftbfs

ostree 2018.6 has test failures on s390x and some ports architectures.
s390x is a representative example:

----8<----
PASS: tests/test-repo-finder-config 1 /repo-finder-config/init
PASS: tests/test-repo-finder-config 2 /repo-finder-config/no-configs
ERROR: tests/test-repo-finder-config - Bail out! GLib-FATAL-CRITICAL: 
g_str_has_prefix: assertion 'str != NULL' failed

# OSTree-DEBUG: ostree_repo_finder_resolve_all_async: Resolving refs 
[(org.example.Collection0, exampleos/x86_64/ref0), (org.example.Collection0, 
exampleos/x86_64/ref1), (org.example.Collection1, exampleos/x86_64/ref1), 
(org.example.Collection1, exampleos/x86_64/ref2), (org.example.Collection2, 
exampleos/x86_64/ref3)] with finders [OstreeRepoFinderConfig]
# OSTree-DEBUG: ostree_repo_finder_config_resolve_async: Checking 21474836480 
remotes
# OSTree-DEBUG: Resolved ref (org.example.Collection0, exampleos/x86_64/ref0) 
to remote ?remote0?.
# OSTree-DEBUG: Resolved ref (org.example.Collection0, exampleos/x86_64/ref1) 
to remote ?remote0?.
# OSTree-DEBUG: Resolved ref (org.example.Collection0, exampleos/x86_64/ref0) 
to remote ?remote0-copy?.
# OSTree-DEBUG: Resolved ref (org.example.Collection0, exampleos/x86_64/ref1) 
to remote ?remote0-copy?.
# OSTree-DEBUG: Resolved ref (org.example.Collection1, exampleos/x86_64/ref2) 
to remote ?remote1?.
# OSTree-DEBUG: Ignoring remote ?remote1-bad-copy? due to it not advertising 
any of the requested refs.
# OSTree-DEBUG: Ignoring remote ?remote2? due to no valid collection ID being 
configured for it: Invalid collection ID (null)
Bail out! GLib-FATAL-CRITICAL: g_str_has_prefix: assertion 'str != NULL' failed
ERROR: tests/test-repo-finder-config - Bail out! GLib-FATAL-CRITICAL: 
g_str_has_prefix: assertion 'str != NULL' failed
----8<----

----8<----
ERROR: tests/test-find-remotes.sh - too few tests run (expected 1, got 0)
ERROR: tests/test-find-remotes.sh - exited with status 133 (terminated by 
signal 5?)

+ env LD_PRELOAD=/<<PKGBUILDDIR>>/tests/libreaddir-rand.so ostree --repo=local 
find-remotes --finders=config org.example.AppsCollection app1

(ostree find-remotes:20691): GLib-CRITICAL **: 23:37:14.198: g_str_has_prefix: 
assertion 'str != NULL' failed
/<<PKGBUILDDIR>>/tests/test-find-remotes.sh: line 89: 20691 Trace/breakpoint 
trap   ${CMD_PREFIX} ostree --repo=$repo find-remotes --finders=config 
org.example.AppsCollection app1 > find
----8<----

I've prepared an upload to fix #902194, which will give us a better
picture of which architectures have this test failure. Right now we have:


          little-endian                         big-endian

32-bit    armel armhf i386 mipsel               mips powerpc(spe) sparc64:
          sh4 x32:                              FTBFS: #902194
          FTBFS: #902194

64-bit    amd64 arm64 mips64el ppc64el          s390x hppa ppc64:
          alpha ia64 riscv64:                   FTBFS: this bug
          successful

which looks suspiciously like correlation with big-endian architectures.
If that theory is correct, arm* i386 mipsel sh4 and x32 will succeed
after #902194 is fixed, but mips powerpc(spe) and sparc64 will continue
to FTBFS due to this bug.

    smcv

--- End Message ---
--- Begin Message ---
Source: ostree
Source-Version: 2018.6-3

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 902...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Simon McVittie <s...@debian.org> (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 ftpmas...@ftp-master.debian.org)


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

Format: 1.8
Date: Sun, 24 Jun 2018 13:04:09 +0100
Source: ostree
Binary: gir1.2-ostree-1.0 libostree-1-1 libostree-dev libostree-doc ostree 
ostree-tests
Architecture: source
Version: 2018.6-3
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 
<pkg-utopia-maintain...@lists.alioth.debian.org>
Changed-By: Simon McVittie <s...@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
Closes: 902209
Changes:
 ostree (2018.6-3) unstable; urgency=medium
 .
   * d/p/avahi-Fail-immediately-if-we-can-t-talk-to-D-Bus-or-Avahi.patch:
     Mark as applied upstream
   * d/p/OstreeRepoFinderConfig-Fix-guint-gsize-confusion.patch:
     Add patch to fix incorrect type aliasing that caused assertion
     failures on 64-bit big-endian platforms (Closes: #902209)
Checksums-Sha1:
 6db4a1b7e290d101b55f88382b48883008ce434c 3043 ostree_2018.6-3.dsc
 ace4582c5a24def85be17aa6db322a3626a85770 20128 ostree_2018.6-3.debian.tar.xz
 2572ca8e5ff060c40d81c7ca108afef4aa8bcece 11020 ostree_2018.6-3_source.buildinfo
Checksums-Sha256:
 744608fd70148371f4931d190c6003861c22c9e740146892f87f34b1912aedc9 3043 
ostree_2018.6-3.dsc
 8cad232e19838f5b5b24077bce6d80a8cb33fe2a90c3945f91760063f1a744f6 20128 
ostree_2018.6-3.debian.tar.xz
 b79941db1356705c1022298fe11875dbe87f87c4c517c3e9df64f80e2568fff1 11020 
ostree_2018.6-3_source.buildinfo
Files:
 a57e32da65324dece960e604cf3c77fb 3043 admin optional ostree_2018.6-3.dsc
 7f9bad12e79f93b117f1c8aa06e2e899 20128 admin optional 
ostree_2018.6-3.debian.tar.xz
 c60b94ffe02aee7b9611371559661bfd 11020 admin optional 
ostree_2018.6-3_source.buildinfo

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

iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAlsvsdgACgkQ4FrhR4+B
TE8KVxAAtfbAiVKqj8fXYg4h3XUizJMEMMh6OGzcDZZ1L3wAwj3GmOmqSHXhEfqa
aISUpoB9CfgCAClizerBR6Z0+pHnpQgrHMtYkJpfRj9poRFT5ibhIQtRFsqNiYbm
MOogkwO76Z7RsVConCqe/WanhiP6Vcw1jWEY3YOLCoyPNvV7+TyNfJ+UGHf02Q/P
LYMfpCLekN5iH9/KBZlcZrI4rdxhc0u6cUbeJQsTveHvEUi/EwosOsVqOwle0Pv5
I2Fo0W3/qVRWZrpTmYwHPDXbjh4CPRTqoOGI/HHsrFvufFiQ9NelLXRajkjrcSbR
TgwOjXBuuPLQO6/du3JKpmOw2L5Wfsc1huBdqiapznc9NChfWi3IHSLTy785idDu
otGlrxGRFHjv9/lN9duLAnUC9ICLp4HJsddTgJjoLr55k4GAQc5VAfDRcmxF9dOi
O3PUgrcJFU9N0Ly42Lfix902e/GYrFANfa/b67+MjmY/j+6sxuD5wA3kLn/40Hfb
8al3wppuiYi8+bn5el48y9n39w8qsdNkBvAjfmphdKx2hVqVVWpHKl5VhNFpNEXT
M3yb0uwKbuEH1idkj+55XCZf/7LzewOb582Ts+2c6ZtX4fhIclQZIPFm/QYP6Jbg
lHsNEvnbekW6V6+tLB34xWx6ttVwSCC5ikhnInBO2kCwWrj5BTU=
=DiUx
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to