> you need python3-dev in the build-dependencies instead of python3 > (as-is, the package doesn’t build in a clean build chroot) This give me the following lintian warning: build-depends-on-python-dev-with-no-arch-any
However I don't really get what the difference between python3-dev and python3 is, the lintian tag entry doesn't really help. > the ratbagd dependency should be (>= 0.10-1), greater than rather > than equal, otherwise the piper package ends up too closely tied to > libratbag (0.10-2 would break the dependency, as would the > forthcoming 0.11-1); in fact switching to >= means you can even drop > the package revision, and write (>= 0.10) What I tried to do with my initial (=0.10) was to let every 0.10 version work, so 0.10-1 and 0.10-2, however this doesn't work. I tried to bind piper to a specific ratbagd version because the Wiki states that ratbagd API is not stable. I uploaded a new version with the right debian version and your suggestions. I know I have to update the git workflow, will do that in the future. Regards, Stephan
