On 2/26/19 7:55 AM, Herbert Fortes wrote: > On 2/26/19 6:07 AM, Steve Langasek wrote: >> On Mon, Feb 25, 2019 at 01:43:03PM -0300, Herbert Fortes wrote: >>> On Wed, 20 Feb 2019 17:37:35 -0300 Herbert Fortes <terb...@gmail.com> wrote: >>
>> It looks like this build has passed now: >> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pyparted.html >> >> Are you happy to close this bug? >> > > Honestly not yet. > > There are two patches that I have to remove. One I am > confidence to do so. > > > armhf failed, but I think it is not the problem we treat > here. > > arm64 and i386 still missing. > > kFreebsd and Hurd have problems. But it is ok. > > I will upload a revision without one patch and Debian CI > like debhelper does. > > Don't worry. At the end everything will be fine. > The last try is here: mips, mips64el and mipsel are important for release and they fail. https://buildd.debian.org/status/package.php?p=pyparted&suite=sid E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd /<<PKGBUILDDIR>>/.pybuild/cpython2_2.7_parted/build; python2.7 -m unittest discover -v exit code=1 They are similar error message that happens to amrhf in reproducible-builds: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/armhf/pyparted.html E: pybuild pybuild:338: test: plugin distutils failed with: exit code=134: cd /build/pyparted-3.11.2/2nd/.pybuild/cpython2_2.7_parted/build; python2.7 -m unittest discover -v exit code=134 For release, 4 architectures still in 'needs-build'. I was honestly confidence for this one, but I will put back the patch I removed ( skip_0gt0.patch file). Let's not make this a big thing. My wild-guess is that the env is not appropriated to parted. I will talk to upstream about the 'find' anyway.
