JP2 (JPEG 2000 Part 1) validator and properties extractor. Jpylyzer was specifically created to check that a JP2 file really conforms to the format's specifications. Additionally jpylyzer is able to extract technical characteristics.
Build process for Debian packages results in file "opf-jpylyzer_2.2.0~rc1_all.deb". However, after upload to Github release, Github changes the name to "opf-jpylyzer_2.2.0.rc1_all.deb" (note tilde is replaced by full stop). This in turn breaks the download links on the Jpylyzer website.
It's not entirely clear to me if the tilde in the file name is a Debian requirement.
Tried to comment out the lines that insert the tilde, but this results in other errors at the end of the build process.
As a workaround I've simply renamed the file manually to "opf-jpylyzer_2.2.0rc1_all.deb" before upload, but it would be nice if the packaging script would get this right directly.
Perhaps @carlwilson or @darrendignam you could have a look at some point?
Build process for Debian packages results in file "opf-jpylyzer_2.2.0~rc1_all.deb". However, after upload to Github release, Github changes the name to "opf-jpylyzer_2.2.0.rc1_all.deb" (note tilde is replaced by full stop). This in turn breaks the download links on the Jpylyzer website.
Tilde is inserted here by package script:
https://github.com/openpreserve/jpylyzer/blob/a7b410d735d7a057292bb7a2b773f7afab8b7ab2/docker-package.sh#L35
It's not entirely clear to me if the tilde in the file name is a Debian requirement.
Tried to comment out the lines that insert the tilde, but this results in other errors at the end of the build process.
As a workaround I've simply renamed the file manually to "opf-jpylyzer_2.2.0rc1_all.deb" before upload, but it would be nice if the packaging script would get this right directly.
Perhaps @carlwilson or @darrendignam you could have a look at some point?