FS#60827 - [scantailor] New version contains several regressions and is not backwards compatible
Attached to Project:
Community Packages
Opened by alexander raban (alraban) - Friday, 16 November 2018, 17:03 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 29 November 2018, 09:38 GMT
Opened by alexander raban (alraban) - Friday, 16 November 2018, 17:03 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 29 November 2018, 09:38 GMT
|
Details
Description:
The scantailor package was recently updated to 0.9.12.2-3 from 0.9.12.2-1. The new version no longer correctly reads the project files created by the prior version of scantailor (i.e. content selections and margins are broken, among other things). This is a breaking change, which was unexpected in a pkgver bump. I have close to a thousand scantailor project files. The new version also no longer appears to support graphical acceleration or multithreaded processing, which is not breaking, but significantly reduces the usability of the program (jobs now take more than eight times longer to process). Additional info: Package version 0.9.12.2-3 introduced this issue and rolling back solves it (the prior version works fine). There appears to be no upstream activity that would have caused this at the repo listed in the PKGBUILD (git://github.com/Tulon/scantailor.git), so it seems like these issues may be related to the new build patches included with the new version? Steps to reproduce: Create a project file in scantailor 0.9.12.2-1, then attempt to process it in 0.9.12.2-3 |
This task depends upon
It looks like Fedora is using the original repo which is mostly unmaintained: https://github.com/scantailor/scantailor
The Arch package had been using the experimental builds forked from the original scantailor by the original author (Tulon), found here: git://github.com/Tulon/scantailor.git. He did a lot of feature work in 2016, including some of the features that are now missing from the new build (like openCL acceleration), and changing the margins from mm to %, etc.
Did the new build change upstreams, or inadvertently revert to an older release/commit on Tulon's repo? That would explain the sudden loss of features and project file compatibility.
Thank you very much for your time and attention to the issue!