@neluser that does seem like a packaging bug. Are you able to contact us on support@ so I can debug this? I have revoked the 1.7.0-1 version in the meantime.
1.7.0-1 fixed some bugs in 1.7.0 but i guess i probably introduced some other issue. 1.6 used ruby 2.5 and 1.7 uses ruby 2.7. the package automatically rebuilds the gems but clearly something did not work out.