Processing commands for cont...@bugs.debian.org:
> block 1034824 with 1036798
Bug #1034824 [src:tomcat9] tomcat9 should not be released with Bookworm
1034824 was blocked by: 1031816 1034855 1033366 1036250
1034824 was not blocking any bugs.
Added blocking bug(s) of 1034824: 1036798
> thanks
Am Freitag, dem 26.05.2023 um 21:44 +0200 schrieb Emmanuel Bourg:
>
> The changes to jetty9 have to be reverted too, the package is broken
> (#1036798).
>
> Sadly we can't do without tomcat9. The path forward implies packaging
> Jetty 11 or 12 first and migrating all the reverse dependencies,
Hi,
On 26-05-2023 21:34, Markus Koschany wrote:
Do I understand you correctly, that we only ship libtomcat9-java in Bookworm
now? Shall I upload a new revision of tomcat9 too?
Yes and yes.
Paul
OpenPGP_signature
Description: OpenPGP digital signature
__
This is the maintainer address of
Le 2023-05-26 21:14, Paul Gevers a écrit :
I have just added removal hints for tomcatjss and dogtag-pki. As
mentioned in my previous message, I want the changes in logback
reverted. You can do the reduced upload of tomcat9.
Markus, can you please revert you logback change by tomorrow at the
Hi,
> Markus, can you please revert you logback change by tomorrow at the latest?
Sure. I will take care if it.
Do I understand you correctly, that we only ship libtomcat9-java in Bookworm
now? Shall I upload a new revision of tomcat9 too?
Regards,
Markus
signature.asc
Description: This is
Hi,
On 26-05-2023 10:58, Moritz Muehlenhoff wrote:
Can't we just do the pragmatic fix of updating src:tomcat9 to only ship
libtomcat9-java and libtomcat9-embed-java? The maintenance burden for
security updates lies within the server stack, the percentage of issues
affecting the libtomcat9-java
Package: jetty9
Version: 9.4.50-3
Severity: grave
Justification: renders package unusable
The jetty9 package can no longer run web applications after switching
to libtomcat10-java for the JSP compiler. The following error appears
in the log:
java.util.ServiceConfigurationError:
hey all,
I was involved with a discussion on site here in Hamburg with Paul
about it.
On Fri, May 26, 2023 at 10:58:48AM +0200, Moritz Muehlenhoff wrote:
> On Fri, May 26, 2023 at 12:10:18AM +0200, Markus Koschany wrote:
> > First of all trapperkeeper-webserver-jetty9-clojure should add a build-
Le 26/05/2023 à 10:58, Moritz Muehlenhoff a écrit :
Can't we just do the pragmatic fix of updating src:tomcat9 to only ship
libtomcat9-java and libtomcat9-embed-java? The maintenance burden for
security updates lies within the server stack, the percentage of issues
affecting the libtomcat9-java
On Fri, May 26, 2023 at 12:10:18AM +0200, Markus Koschany wrote:
> First of all trapperkeeper-webserver-jetty9-clojure should add a build-
> dependency on logback to detect such regressions in advance.
>
> #1036250 is mainly a logback problem, not a tomcat problem. I still would like
> to hear
Processing control commands:
> clone -1 -2 -3
Bug #1034824 [src:tomcat9] tomcat9 should not be released with Bookworm
Bug 1034824 cloned as bugs 1036790-1036791
1036790 was blocked by: 1031816 1034855 1033366 1036250
1036790 was not blocking any bugs.
Ignoring request to alter blocking bugs of
Control: clone -1 -2 -3
Control: reassign -2 release-notes
Control: reassign -3 debian-security-support
Control: tag -1 bookworm-ignore
Hi,
On 26-05-2023 00:10, Markus Koschany wrote:
#1036250 is mainly a logback problem, not a tomcat problem. I still would like
to hear Emmanuel's opinion. We
12 matches
Mail list logo
