Your message dated Wed, 8 Jul 2020 13:34:39 +0200 with message-id <CAM8zJQufxRs-ty3PqN84ULUsJUZ80PcPMRRRfMHR+e9ptHTung@mail.gmail.com> and subject line python-bayespy: FTBFS and Debci failure on several architectures has caused the Debian Bug report #884516, regarding python-bayespy: FTBFS and Debci failure on several architectures 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 owner@bugs.debian.org immediately.) -- 884516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884516 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: python-bayespy autopkg tests fail on several architectures
- From: Matthias Klose <doko@debian.org>
- Date: Sat, 16 Dec 2017 08:38:11 +0100
- Message-id: <0bde50ff-0e33-167a-bd67-5d67a5ba2ea9@debian.org>
Package: src:python-bayespy Version: 0.5.12-1 Severity: important Tags: sid buster (seen on the autopkg tests on Ubuntu) It looks like 0.5.12 is failing it's autopkg tests at least on arm64, armhf, ppc64el and s390x (all succeeding with 0.5.8). arm64, ppc64el, s390x: Test the message to parents of Concatenate node. ... Segmentation fault (core dumped) armhf: Test the message from SumMultiply node to its parents. ... Segmentation fault (core dumped) Succeeding targets are amd64 and i386. In a Debian test rebuild, the package seems to succeed on at least amd64.
--- End Message ---
--- Begin Message ---
- To: 884516-done@bugs.debian.org
- Subject: python-bayespy: FTBFS and Debci failure on several architectures
- From: Graham Inggs <ginggs@debian.org>
- Date: Wed, 8 Jul 2020 13:34:39 +0200
- Message-id: <CAM8zJQufxRs-ty3PqN84ULUsJUZ80PcPMRRRfMHR+e9ptHTung@mail.gmail.com>
This appears to have been resolved in another package in November / December 2019. Possibly the new version of numpy.
--- End Message ---