** Changed in: pdfsam (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887142
Title:
pdfsam won't run, has missing and conflicting dependencies
To
** Bug watch removed: Debian Bug tracker #941685
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941685
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887142
Title:
pdfsam won't run, has
works fine for me on Groovy
corrado@corrado-x2-gg-1009:~$ apt policy pdfsam
pdfsam:
Installed: 4.0.4-1ubuntu2
Candidate: 4.0.4-1ubuntu2
Version table:
*** 4.0.4-1ubuntu2 500
500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages
500
** Tags added: fr-740
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887142
Title:
pdfsam won't run, has missing and conflicting dependencies
To manage notifications about this bug go to:
This bug was fixed in the package libsejda-java - 3.2.84-2~20.04
---
libsejda-java (3.2.84-2~20.04) focal; urgency=medium
* Backport from Groovy.
* Fix incompatibility with libhibernate-validator-java by also
building against libgeronimo-validation-1.1-spec-java. LP:
This bug was fixed in the package pdfsam - 4.0.4-1ubuntu2~20.04
---
pdfsam (4.0.4-1ubuntu2~20.04) focal; urgency=medium
* Backport from Groovy.
pdfsam (4.0.4-1ubuntu2) groovy; urgency=medium
* Add dependency on libtomcat9-embed-java and require newer
libsejda-java and
Verified pdfsam 4.0.4-1ubuntu2~20.04 and libsejda-java 3.2.84-2~20.04
from focal-proposed.
I confirm that PDFSam now works for splitting and merging PDF files.
pdfsam:
Installed: 4.0.4-1ubuntu2~20.04
Candidate: 4.0.4-1ubuntu2~20.04
Version table:
*** 4.0.4-1ubuntu2~20.04 400
400
> I don't know how I could/should evaluate how bad this is compared to
having a non-working package such as pdfsam, so I would appreciate any
feedback related to the SRU process on such decisions (maybe just having
the regressions described is good enough?).
Just whatever best effort you can
> Is it possible that any Ubuntu users consume libsejda-java directly,
and thus would be regressed by bumping it to to the 1.1 spec?
Thanks for catching this. I updated the regression to include:
Ubuntu users consuming libsejda-java directly can
regress if something else in their dependency
** Description changed:
[Impact]
pdfsam fails to work due missing and conflicting dependencies.
On Focal and Groovy libhibernate-validator-java has a runtime dependency
on libel-api-java and an implementation of el-api. Both are usually
provided when running under Java EE. On Java SE
> 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.
Is it possible that any Ubuntu
This bug was fixed in the package pdfsam - 4.0.4-1ubuntu1
---
pdfsam (4.0.4-1ubuntu1) groovy; urgency=medium
* Add dependency on el-api and libtomcat9-java, require newer
libsejda-java and libhibernate-validator-java. (LP: #1887142)
-- Tiago Stürmer Daitx Wed, 23 Sep 2020
** Description changed:
[Impact]
pdfsam fails to work due missing and conflicting dependencies.
On Focal and Groovy libhibernate-validator-java has a runtime dependency
on libel-api-java and an implementation of el-api. Both are usually
provided when running under Java EE. On Java SE
13 matches
Mail list logo
