Your message dated Fri, 27 Mar 2020 16:04:29 -0700
with message-id <20200327230429.gt50...@kduck.mit.edu>
and subject line openafs armhf issues specific to buildd network configuration
has caused the Debian Bug report #953729,
regarding openafs: FTBFS on armhf
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.)
--
953729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953729
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: src:openafs
version: 1.8.5-1
severity: serious
tags: ftbfs
Hi,
The latest upload of openafs to unstable fails on armhf:
https://buildd.debian.org/status/package.php?p=openafs
Cheers,
Ivo
--- End Message ---
--- Begin Message ---
In openafs 1.8.6~pre1-3 I have disabled the test that has been failing on
the armhf buildd; it's apparently dependent on the network configuration of
the system it's running on, and the build (including tests) works fine on a
porterbox. I will work with upstream to try and find a solution for
avoiding this dependence on the network configuration, but there's no
reason for the buildd's network configuration to keep openafs from
migrating to testing.
-Ben
--- End Message ---
