Yeah, oddly enough this happened with 0.14.0-1 too then mysteriously resolved itself when retried on a different mips64el buildd while I was waiting for porterbox access.
Looking over here it seems to hate the mipsel-manda-* buildds: https://buildd.debian.org/status/logs.php?pkg=hiredis&arch=mips64el ... bit odd. Guess I should kick off the porterbox request again to get to the bottom of it. I'll figure that out with Tony. Thinking slightly longer term: if you and/or the folks maintaining the redis package would like to adopt hiredis that might make sense -- as a non-DD/DM it's likely I'll always be moving slower than you & redis is obviously a relatively "hot" package. Aside from these occasionally annoying cross-platform headaches, hiredis is very low maintenance in the scheme of things & I don't want to be holding you folks up any time vendored hiredis & released hiredis diverge. (Don't feel obliged & I'm happy to continue maintenance, it just seems like you folks might be able to operate more effectively if we get hiredis + redis maintenance under the same umbrella.) Cheers, Tom On Fri, Nov 2, 2018 at 1:58 AM Chris Lamb <la...@debian.org> wrote: > Chris Lamb wrote: > > > > will push the backport when 0.14.0-2 hits testing. > > > > Great, hopefully soon. > > Looks like there's a build issue on mips64el that is blocking this: > > https://qa.debian.org/excuses.php?package=hiredis > > > Best wishes, > > -- > ,''`. > : :' : Chris Lamb > `. `'` la...@debian.org / chris-lamb.co.uk > `- > -- *Tom Lee */ http://tomlee.co / @tglee <http://twitter.com/tglee>
