Unarchive the following likely erroneously archived bugs

[Don Armstrong]

On Mon, 18 Dec 2017, Paul Gevers wrote:
> Well, it doesn't help that we are not aware that that is the reason.
> The bts doesn't tell us. All I see is an old bug that doesn't get
> archived.

The version graph is how I knew what was going on, and that's linked
from the bug pages:

https://bugs.debian.org/cgi-bin/version.cgi?info=1;found=brltty%2F5.3.1-1;package=brltty;absolute=0;collapse=1;fixed=brltty%2F5.3.1-2

You can also get more information if you ask for a bug to be archived
with debugging on.

> There is probably something wrong in the packaging of brltty that
> causes 4 non-release archs to FTBFS with a recent version. It would
> help more if a wishlist bug about that would be opened instead of an
> unrelated bug does not get archived.

Looks like something with the java API:

https://buildd.debian.org/status/fetch.php?pkg=brltty&arch=kfreebsd-amd64&ver=5.5-4&stamp=1512331748&raw=0

-- 
Don Armstrong                      https://www.donarmstrong.com

As nightfall does not come at once, neither does oppression. In both
instances, there is a twilight when everything remains seemingly
unchanged. And it is in such twilight that we all must be most aware
of change in the air -- however slight -- lest we become unwitting
victims of the darkness.
 -- William O. Douglas