I just ran into https://sourceforge.net/p/traceroute/bugs/8/ (august 2014!) Suggestion: stabilize traceroute-2.0.22
why not 2.1.0?
(In reply to Pacho Ramos from comment #1) > why not 2.1.0? No particular reason.. gotta keep something in ~ though right? ;)
we can try the latest to not need to repeat the whole stabilization progress and involving all the arch teams again soon
amd64 stable
sparc done.
ia64 stable
arm64 stable
x86 stable
Stable on alpha.
hppa stable
ppc/ppc64 stable
arm stable
s390 stable
SuperH port disbanded.
m68k dropped stable keywords Last arch. Closing.