Bug#1041419: ca-certificates-java: workaround

[tomas]

Package: ca-certificates-java
Followup-For: Bug #1041419
X-Debbugs-Cc: foren...@wi.rr.com

There are actually 2 of each of these files, differing only
in 7+7 and 8+7

openjdk-17-jre_17.0.7+7-1~deb12u1_amd64.deb  
openjdk-17-jre_17.0.8+7-1~deb12u1_amd64.deb


openjdk-17-jre-headless_17.0.7+7-1~deb12u1_amd64.deb
openjdk-17-jre-headless_17.0.8+7-1~deb12u1_amd64.deb

So I purged the partially configured files, and downloaded them again 
with 
apt-get -d install 

I did updatedb and locate to find the full names, and used
dpkg -i --force-depends 

for both of the 8+7 versions, ran
apt-get -f install
dpkg --configure --pending

and there are no more errors. 

-- System Information:
Debian Release: 12.0
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-9-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_DIE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ca-certificates-java depends on:
ii  ca-certificates   20230311
ii  default-jre-headless [java8-runtime-headless] 2:1.17-74
ii  openjdk-17-jre-headless [java8-runtime-headless]  17.0.8+7-1~deb12u1

ca-certificates-java recommends no packages.

ca-certificates-java suggests no packages.

-- Configuration Files:
/etc/default/cacerts [Errno 13] Permission denied: '/etc/default/cacerts'

-- no debconf information

__
This is the maintainer address of Debian's Java team
.
 Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#1041282: Additional information

[Vladimir Petko]

Hi,

 The build.xml is not supported by the upstream, so I have updated the
patch to include rule changes to use the provided Makefile[1].

Changes:
  * Use Makefile to build jtreg (LP: #2031041).
- Use --release option in Makefile compile options.
- d/p/*: drop build.xml patches.
- d/control: add libguice-java, zip.

Thank you for considering the patch.

Best Regards,
 Vladimir.

[1] https://bugs.launchpad.net/ubuntu/+source/jtreg6/+bug/2031041


jtreg6_6.1+2-1_to_jtreg6_6.1+2-1ubuntu3.debdiff
Description: Binary data
__
This is the maintainer address of Debian's Java team
.
 Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#1040226: tomcat10: deployment-time Java EE to Jakarta EE migration fails

[Markus Koschany]

Hi,

Am Dienstag, dem 15.08.2023 um 14:52 +0200 schrieb J. Tóth Tamás:
> Hi,
> 
> > Please keep the bug report always in CC.
> 
> I thought my 8 August mail contains no new information, so it makes no 
> sense to spam the BTS with it. But okay, next time (and this time) I’ll 
> use Reply All regardless of the message content.

I'm not the only Debian developer who could help you. There may be other users
too who are interested in this topic and who could provide valuable insight or
suggestions. Hence why it's so important to have a public bug tracker with the
record of our conversation.

> 
> > > We’d like to gradually upgrade
> > > to Bookworm, but I don’t want to make sysops’ lives more complicated by
> > > giving them one WAR file to install on Bookworm and another one to
> > > install on Bullseye.
> > 
> > […] You can just manually run the tomcat-jakartaee-migration tool on
> > your existing war files. All it mainly does is to replace the old
> > occurrences of javax.* with jakarta.*.
> 
> That’s exactly what I meant by “making sysops’ lives more complicated by
> giving them one WAR file to install on Bookworm and another one to 
> install on Bullseye”, so it’s out of question for me in production.

Ok, I'm not familiar with your workflow. Though I would never trust a tool to
do the right thing on the fly. I would instruct my development team to port the
application to Tomcat 10 and test it thoroughly and then my production team
only would take care of the administration and deployment task as usual. 

> 
> > You could also send a patch with your proposed changes to Debian's tomcat10
> > > package and I take a look at it.
> 
> I created https://salsa.debian.org/java-team/tomcat10/-/merge_requests/1 
> – it’s quite likely wrong in its current form, but I hope it can be fixed.

Thank you! I have merged your request and also pushed a new upstream version to
our Git repository but I didn't upload the package yet. Patches should be added
to the debian/patches/series file as well, otherwise they won't be applied. The
rest looked good to me. However I still get a migration warning when I follow
your initial steps with the basic "test" app. There is a
DirectoryNotEmptyException. Initially tomcat migrates the test folder in
webapps-javaee to a newx.tmp folder and then tries to remove the latter,
which fails. What can we do to avoid this warning?

Regards,

Markus


signature.asc
Description: This is a digitally signed message part
__
This is the maintainer address of Debian's Java team
.
 Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#1040226: tomcat10: deployment-time Java EE to Jakarta EE migration fails

[J . Tóth Tamás]

Hi,


Please keep the bug report always in CC.


I thought my 8 August mail contains no new information, so it makes no 
sense to spam the BTS with it. But okay, next time (and this time) I’ll 
use Reply All regardless of the message content.



We’d like to gradually upgrade
to Bookworm, but I don’t want to make sysops’ lives more complicated by
giving them one WAR file to install on Bookworm and another one to
install on Bullseye.


[…] You can just manually run the tomcat-jakartaee-migration tool on
your existing war files. All it mainly does is to replace the old
occurrences of javax.* with jakarta.*.


That’s exactly what I meant by “making sysops’ lives more complicated by
giving them one WAR file to install on Bookworm and another one to 
install on Bullseye”, so it’s out of question for me in production.



You could also send a patch with your proposed changes to Debian's tomcat10 > 
package and I take a look at it.


I created https://salsa.debian.org/java-team/tomcat10/-/merge_requests/1 
– it’s quite likely wrong in its current form, but I hope it can be fixed.


Tamás

__
This is the maintainer address of Debian's Java team
.
 Please use
debian-j...@lists.debian.org for discussions and questions.

Processed: Fix committed to Salsa

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #1047196 [src:libjswingreader-java] libjswingreader-java: Fails to build 
source after successful build
Added tag(s) pending.

-- 
1047196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1047196
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

__
This is the maintainer address of Debian's Java team
.
 Please use
debian-j...@lists.debian.org for discussions and questions.

Processed: Fix committed to Salsa

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #1046349 [src:libjogl2-java] libjogl2-java: Fails to build source after 
successful build
Added tag(s) pending.

-- 
1046349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1046349
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

__
This is the maintainer address of Debian's Java team
.
 Please use
debian-j...@lists.debian.org for discussions and questions.