Bug#870428: libverto1: Upstream has moved

2019-02-27 Thread Sam Hartman
> "Robbie" == Robbie Harwood writes: Robbie> Sam Hartman writes: >> I apologize for dropping the ball on this so long. It looks like >> there is a 0.3.0 release of verto, which was folded into krb5. >> However, It looks like there's not an upstream tarball on github >>

Bug#870428: libverto1: Upstream has moved

2019-02-26 Thread Robbie Harwood
Sam Hartman writes: > I apologize for dropping the ball on this so long. > It looks like there is a 0.3.0 release of verto, which was folded into > krb5. > However, It looks like there's not an upstream tarball on github for > anything past 0.2.6. I'm confused by this comment. I've definitely

Bug#870428: Info received (Bug#870428: libverto1: Upstream has moved)

2019-02-26 Thread Sam Hartman
Sigh. I'm just confused. Got the 0.3.0 tar ball fine.

Bug#870428: libverto1: Upstream has moved

2019-02-26 Thread Sam Hartman
I apologize for dropping the ball on this so long. It looks like there is a 0.3.0 release of verto, which was folded into krb5. However, It looks like there's not an upstream tarball on github for anything past 0.2.6. Because I dropped the ball so much I'm under tight time pressure to get an

Bug#870428: libverto1: Upstream has moved

2017-08-01 Thread Robbie Harwood
Package: libverto1 Version: 0.2.4-2.1 Severity: normal Dear Maintainer, Since Fedorahosted isn't around anymore, we've moved the libverto upstream to https://github.com/latchset/libverto . I also notice that the Debian package is 0.2.4 while we have released 0.2.6 upstream. I am happy to help