On 2019-02-05 16:27, Sophie Brun wrote: >> Please note that the problem itself is with the autopkgtest of the >> package, build is ok, you will only spot it if you enable such tests. >> That is: the package is not FTBFSing, but the autopkgtests are >> failing. > > I push a fix for the autopkgtest today
Looks good! (It's curious that pyrit creating a config in $HOME hasn't been an issue with past autopkgtest, which makes me wonder if/how autopkgtest deals with $HOME. I couldn't find anything in the docs. I'll ask the autopkgtest maintainers.) One thing I just remembered: there's also pyrit-opencl 0.4 [1], a separately maintained package which depends on pyrit. It's possible that pyrit 0.5 might breakt this package, in which case at least a Breaks will be necessary. It looks as if pyrit-opencl could be updated to 0.5, too, though: [2] [1] https://tracker.debian.org/pkg/pyrit-opencl [2] https://github.com/JPaulMora/Pyrit/tree/master/modules/cpyrit_opencl Regards, Christian
