For vivid, it has built packages like libunity-scopes1.0_1.0.0+15.04.20150819-0ubuntu1_amd64.deb with the new soname.
It looks like the script was run on the system where the source package was built. Your gen-debian-files script has no output, so it is hard to see what might have been doing on from the jenkins log for the source package build:
Looking at the builds in the landing silo, this hasn't worked:
https:/ /launchpad. net/~ci- train-ppa- service/ +archive/ ubuntu/ landing- 010/+packages
For vivid, it has built packages like libunity- scopes1. 0_1.0.0+ 15.04.20150819- 0ubuntu1_ amd64.deb with the new soname.
It looks like the script was run on the system where the source package was built. Your gen-debian-files script has no output, so it is hard to see what might have been doing on from the jenkins log for the source package build:
https:/ /ci-train. ubuntu. com/job/ ubuntu- landing- 010-1-build/ 195/consoleText
Perhaps instrumenting it a bit and redoing the build would be the best way forward.