Stefan - that sounds like a good plan to me. Looking at the crashes from 2015-08-03 we can see the following:
$ grep "^ " 20150803-iproute2-crashes.txt | awk -F, {'print $3'} | sort | uniq -c
22 Linux 3.13.0-59-generic x86_64
1 Linux 3.13.0-61-generic x86_64
1 Linux 3.19.0-25-generic x86_64
1 Linux 3.19.0-26-generic x86_64
Looking at the -61- crash it is actually a package installation failure so not a concern. The two 3.19 crashes are a package installation failure and a good, complete, iproute2 crash. So I think things are looking better.
I've attached the crashes I reviewed from 2015-08-03.
Stefan - that sounds like a good plan to me. Looking at the crashes from 2015-08-03 we can see the following:
$ grep "^ " 20150803- iproute2- crashes. txt | awk -F, {'print $3'} | sort | uniq -c
22 Linux 3.13.0-59-generic x86_64
1 Linux 3.13.0-61-generic x86_64
1 Linux 3.19.0-25-generic x86_64
1 Linux 3.19.0-26-generic x86_64
Looking at the -61- crash it is actually a package installation failure so not a concern. The two 3.19 crashes are a package installation failure and a good, complete, iproute2 crash. So I think things are looking better.
I've attached the crashes I reviewed from 2015-08-03.