Re: testing security blockers
Steve Langasek <email@example.com> writes:
> In fact, though, I don't see any issues that would leave m68k any worse
> off than it is now if we push the update in on the other archs, so I'm
> going to go ahead and do this.
> Once it's in, the next step would have to be an upload to unstable that
> fixes the m68k build (or a fix for the m68k toolchain, if that happens
> sooner). Whether that should be followed by an upload to t-p-u probably
> depends on just how long it takes to get glibc sorted.
Okay, shortly after I see krb5 go into testing, I'll try to get an upload
in that attempts to work around the build failure.
Russ Allbery (firstname.lastname@example.org) <http://www.eyrie.org/~eagle/>