This isn't something you need to worry about. It's a misconfiguration on our
end - the bugtracker appears to be pointing at the old location of the
mailserver, and I haven't had a chance to debug why yet.
June 12, 2018 2:42 PM, "Christian Keil" <c.k...@tu-harburg.de> wrote:
> Am Dienstag, den 12.06.2018, 10:13 -0400 schrieb Eli Schwartz:
>> On 06/11/2018 03:55 PM, Christian Keil wrote:
>> I wanted to submit a bug report for whipper / accurateip-checksum but
>> trying to register for an account at bugs.archlinux32.org just results
>> in a timeout:
>> "Completely unexpected exception: Connection to 172.18.0.1:25 Timed Out
>> This should never happend, please inform Flyspray Developers"
>> The bug in short: accurateip-checksum has an error that causes a crash
>> on 32bit architectures: https://github.com/leo-bogert/accuraterip-check
>> sum/issues/2. whipper has its own version of accurateip-checksum with
>> the necessary fix in its repo, but this isn't built for Arch's version.
>> Did you try pinging upstream to see if a couple years later, they've
>> finally gotten around to merging this change upstream?
> Do you mean upstream on GitHub or upstream Archlinux?
> packages.archlinux32.org refers to both as upstream =).
> The issue on GitHub is still open and since there hasn't been any
> activity in the project since 2013, I don't expect the existing pull
> request to be accepted there. It was commented by leo-bogert in 2016
> but since then nothing happened. I just asked for progress on this.
> The Arch version of accuraterip-check declared itself to be arch x86_64
> but the Whipper version claims to be arch any so it might also be
> considered to be a bug there. There is no bug report there.
> How would you suggest to proceed?
> arch-ports mailing list
arch-ports mailing list