pdfsam won't run, has missing and conflicting dependencies
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libhibernate-validator-java (Debian) |
New
|
Unknown
|
|||
libhibernate-validator-java (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
New
|
Undecided
|
Unassigned | ||
libsejda-java (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned | ||
pdfsam (Debian) |
Fix Released
|
Unknown
|
|||
pdfsam (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
pdfsam fails to work due missing and conflicting dependencies.
On Focal and Groovy libhibernate-
The usual implementation of el-api on Maven projects is from Glassfish, but that has not yet been packaged. libtomcat9-
Also during build time pdfsam must create links of the jar files it needs for runtime: tomcat9-
Only on Focal:
* libsejda-java 3.2.84-1 depends on libgeronimo-
* libhibernate-
A Java application must has either 1.0 or 1.1 spec on its classpath, never both as they are incompatible. To fix this libsejda-java in Focal should be updated to 3.2.84-2 so everything depends on the 1.1 spec (ie. libgeronimo-
[Test Case]
1) On Focal and Groovy, install pdfsam and run it
$ sudo apt get install -y pdfsam
$ pdfsam
2) Split a PDF
Expected result:
For the action to execute correctly.
Actual result:
The console shows a java stacktrace such as
ERROR 15:56:04.873 org.pdfsam.
org.sejda.
...
[Regression Potential]
* libseja-java backport:
Moving from 1.0 to 1.1 spec might cause regressions on packages that depend on libsejda-java as now el-api (and its implementation) must be available on the classpath (default on Java EE). At this time the only package that depends on libsejda-java is pdfsam.
Ubuntu users consuming libsejda-java directly can regress if something else in their dependency chain currently relies on spec 1.0 - they would need to update these dependencies to also use spec 1.1.
* New dependency on libtomcat9-
The most common implementation of el-api is from Glassfish, so using tomcat9 to provide this might introduce problems if it deviates from the spec (unlikely, as tomcat is also a Java EE provider).
[Other Info]
[Original Report]
pdfsam does not produce an output file because of various java-exceptions.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pdfsam 4.0.4-1
ProcVersionSign
Uname: Linux 5.4.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckR
CurrentDesktop: XFCE
Date: Fri Jul 10 11:46:14 2020
InstallationDate: Installed on 2019-09-09 (304 days ago)
InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
PackageArchitec
SourcePackage: pdfsam
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in pdfsam (Debian): | |
status: | Unknown → Confirmed |
Changed in libhibernate-validator-java (Debian): | |
status: | Unknown → New |
summary: |
- pdfsam does not produce output + libhibernate-validator-java should be kept at 4.3.4-1 |
Changed in libspring-java (Debian): | |
status: | Unknown → Confirmed |
description: | updated |
tags: | added: groovy |
description: | updated |
summary: |
- libhibernate-validator-java should be kept at 4.3.4-1 + libhibernate-validator-java should be backported to 4.3.4-1~18.04.1 |
description: | updated |
description: | updated |
summary: |
- libhibernate-validator-java should be backported to 4.3.4-1~18.04.1 + pdfsam won't run, has missing and conflicting dependencies |
no longer affects: | libspring-java (Ubuntu) |
no longer affects: | libspring-java (Debian) |
Changed in libhibernate-validator-java (Ubuntu): | |
status: | Confirmed → Fix Released |
Changed in libsejda-java (Ubuntu): | |
status: | New → Fix Released |
Changed in pdfsam (Ubuntu Focal): | |
status: | New → Confirmed |
description: | updated |
description: | updated |
description: | updated |
tags: | added: fr-740 |
Changed in pdfsam (Debian): | |
status: | Confirmed → Fix Released |
Status changed to 'Confirmed' because the bug affects multiple users.