Your message dated Thu, 5 Mar 2020 18:59:57 -0700
with message-id 
<cabrvrihuuqm6pwwnapbsyp5mu8txdo_vdrnxxvapqhmroen...@mail.gmail.com>
and subject line Bug#951702: not subvertpy's bug; build fine on s390x and ppc64 
now
has caused the Debian Bug report #951702,
regarding subvertpy ftbfs on 64bit big endian targets
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.)


-- 
951702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951702
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:subvertpy
Version: 0.11.0~git20191228+2423bf1-1
Severity: serious
Tags: sid bullseye

seen on ppc64 and s390x at least:

[...]
Generating objects inventory at apidocs/objects.inv
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
   dh_auto_test -a -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py test
running test
running build
running build_py
running build_ext
running build_scripts
Running unittest without install.
Segmentation fault
E: pybuild pybuild:341: test: plugin distutils failed with: exit code=139:
python2.7 setup.py test
dh_auto_test: error: pybuild --test -i python{version} -p 2.7 returned exit 
code 13

--- End Message ---
--- Begin Message ---
Source: subvertpy
Source-Version: 0.11.0~git20191228+2423bf1-1

Two weeks have passed since the FTBFS happened, and after visiting
https://buildd.debian.org/status/package.php?p=subvertpy and giving
back the builds on s390x and ppc64 in sid, I am happy to report that
that subvertpy built fine on both architectures on first try.

The FTBFS appears to be a temporary glitch with the rest of the system
and not a problem with subvertpy itself, and since the problem seems
to be solved, I am hereby closing this bug report.

Cheers,
Anthony Fok

--- End Message ---

Reply via email to