Hello Jonas! On 2/9/21 5:46 PM, Jonas Smedegaard wrote:
I am puzzled as to what is the real cause, though: It seems to me that the CI infrastructure neglects to install python3-vobject despite it being declared as a dependency of python3-radicale
Oh, so actually I would add either python3-radicale, either radicale, to the Depends field in d/tests/control, in order to install it in the testbed, along with its dependencies (which include python3-vobject).
As far as I know (I might be wrong), it's not automatic. I think it's because autopkgtest does not know which binary packages you intend to test, so you have to make it explicit in the Depends field.
Alternatively there is the special dependency '@' , which installs all the build dependencies of the source package.
All the best, Arnaud
