It is odd, these all fail with the same error all the time.
But affected architectures changed - what seems like over time.
original
=> armhf fails
d/xen-utils-common.dirs: prep dir that is used for bash-completion
=> both arm builds fail
d/xen-utils-common.install: add leading/trailing slashes following the dh-exec examples
=> both arm builds fail
back to the original
=> Failing both arm builds now
Might there be something else that landed on armhf first and then arm64 later?
With that in mind I rechecked logs and found this:
All working arm builds have:
- dh-exec 0.23.4build2
All failing arm builds have
- dh-exec - 0.26
I do not know yet why this lands at so different times in the different
architectures.
In addition sadly it isn't so easy - as the working amd64 has dh-exec 0.26 as well.
It is odd, these all fail with the same error all the time.
But affected architectures changed - what seems like over time.
original common. dirs: prep dir that is used for bash-completion common. install: add leading/trailing slashes following the dh-exec examples
=> armhf fails
d/xen-utils-
=> both arm builds fail
d/xen-utils-
=> both arm builds fail
back to the original
=> Failing both arm builds now
Might there be something else that landed on armhf first and then arm64 later?
With that in mind I rechecked logs and found this:
All working arm builds have:
- dh-exec 0.23.4build2
All failing arm builds have
- dh-exec - 0.26
I do not know yet why this lands at so different times in the different
architectures.
In addition sadly it isn't so easy - as the working amd64 has dh-exec 0.26 as well.