Your message dated Mon, 10 Feb 2014 13:25:22 -0800
with message-id <[email protected]>
and subject line Re: Bug#738364: krb5-sync FTBFS on armel armhf ia64mips
mipsel sparc
has caused the Debian Bug report #738364,
regarding krb5-sync FTBFS on armel armhf ia64mips mipsel sparc
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 [email protected]
immediately.)
--
738364: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738364
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
package: krb5-sync
version: 3.0-1
severity: serious
justification: FTBFS
I'm surprised this is not already filed, but it seems like it should be.
krb5-sync is failing tests (and thus builds) on the above listed
architectures.
--- End Message ---
--- Begin Message ---
Version: 3.0-3
Sam Hartman <[email protected]> writes:
> I'm surprised this is not already filed, but it seems like it should be.
> krb5-sync is failing tests (and thus builds) on the above listed
> architectures.
Thank you for the report! For some reason, I didn't get, or didn't see,
the automated FTBFS notifications from the buildds.
This was a timing problem with one of the test cases combined with a
coding error. I've relaxed the expected timing, and 3.0-3 appears to have
fixed the issue.
--
Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/>
--- End Message ---
