Dear Maintainer,

Since upload of version 8.5.50-0+deb9u1, upgrades to Buster are broken:

Unpacking libel-api-java (3.0.0-2) ...
dpkg: error processing archive /tmp/apt-dpkg-install-pjjAYg/328-libel-api-java_3.0.0-2_all.deb (--unpack):
 trying to overwrite '/usr/share/maven-repo/javax/el/javax.el-api/3.0/javax.el-api-3.0.pom', which is also in package libservlet3.1-java 8.5.50-0+deb9u1
[…]
Unpacking libjsp-api-java (2.3.4-2) ...
dpkg: error processing archive /tmp/apt-dpkg-install-pjjAYg/362-libjsp-api-java_2.3.4-2_all.deb (--unpack):
 trying to overwrite '/usr/share/maven-repo/javax/servlet/jsp/javax.servlet.jsp-api/2.3/javax.servlet.jsp-api-2.3.pom', which is also in package libservlet3.1-java 8.5.50-0+deb9u1
[…]
Unpacking libwebsocket-api-java (1.1-1) ...
dpkg: error processing archive /tmp/apt-dpkg-install-pjjAYg/388-libwebsocket-api-java_1.1-1_all.deb (--unpack):
 trying to overwrite '/usr/share/maven-repo/javax/websocket/javax.websocket-api/1.0/javax.websocket-api-1.0.pom', which is also in package libservlet3.1-java 8.5.50-0+deb9u1

The reason seems to be that files from this package migrated to other
packages in Buster, but at an earlier version than 8.5.50-0+deb9u1
(looks like the move happenend in 8.5.35-3~, according to the Breaks
in the now-broken packages).

I am not sure how this can be solved short of splitting the packages
the same way as in Buster, or possibly providing a newer version in
Buster with updated version in Breaks fields, if that works also for
people updating from earlier versions.

Regards,
Colomban

Hello,

Am 31.12.19 um 16:33 schrieb Colomban Wendling:
[...]

thanks for reporting. I believe I have to update the Breaks relationship
in libel-api-java, libjsp-api-java, libservlet-api-java and
libwebsocket-api-java. Probably << 9 will save us from further trouble.
I could also add a Conflicts field to libservlet3.1-java in Stretch but
I don't know if apt will properly resolve the dependencies during the
upgrade. This is something for a buster-pu.

Regards,

Markus

Hello

I am also affected by this bug. Is there any fix on the way?

Thank you very much

I have also experinced the exact same bug. Upgrading from a fresh Debian
9 install. Any chance of getting this fixed ??

Am 28.03.20 um 17:53 schrieb Ronny Buelund:

I will upload new packages to stable-proposed tomorrow but it may take a
few days until they will be accepted.

Hi!

I just encountered this bug, too, when upgrading a machine.

I couldn't find a new package corresponding to this ticket in
the announcement "[SUA 179-1] Upcoming Debian 10 Update (10.4)"
for the upcoming point release.

Regards,

Thomas

* Thomas Arendsen Hein <thomas@intevation.de> [20200506 17:09]:
Running "apt-get install -f" seems to work to continue the upgrade.

Regards,

Thomas

Am 06.05.20 um 17:22 schrieb Thomas Arendsen Hein:

The fixed packages are currently in stable-proposed-updates only but
there will be a new point update for stable within a few days.

* Markus Koschany <apo@debian.org> [20200507 13:35]:

Ah, right. I didn't see the updated packagess in
buster-proposed-updates, because I was looking for an updated
packaghe for libservlet3.1-java (which isn't in bpu), but there are
indeed updated packages for libjsp-api-java, libel-api-java and
libwebsocket-api-java.

For me neither the source package names (el-api, jsp-api,
websocket-api) nor the description "Fix stretch to buster upgrades
that involve Tomcat 8" from the announcement mail looked relevant
since there was no mention of servlet-api, and the server I upgraded
doesn't have tomcat installed.

Thank you,
Thomas

The bug is still not fixed as I tried updating LMDE3 to LMDE4 based on
debian 9 to 10.

Am Freitag, den 29.01.2021, 14:25 +0200 schrieb Modestas:

The bug was fixed eight months ago. Without more information, nobody can
investigate your problem.

Regards,

Markus Koschany