Bug#1061025: Additional information

2024-03-06 Thread Vladimir Petko
Dear Maintainers,

 I am wondering if the acceptable fix for this failure would be
disabling slf4j backend in commons-logging? This will break circular
dependency and allow projects that use commons-logging and slf4j to
build. I have created a MR with the patch[1].

Best Regards,
 Vladimir.

[1] 
https://salsa.debian.org/java-team/libcommons-logging-java/-/merge_requests/7



Bug#1061025: Additional information

2024-03-03 Thread Vladimir Petko
Dear Maintainers,

httpcomponents-client contains an implicit dependency on slf4j-java.

Last time it was build successfully against libcommons-log-java 1.2[1]

Support for slf4j was added after its release[2][3]

Debian and Ubuntu have slf4j 1.7.32-1 which calls
org.apache.commons.logging.LogFactory.getLog[4].

This causes exception in httpclient-cache tests[5]:

java.lang.IllegalStateException: Recursive update
 at 
java.base/java.util.concurrent.ConcurrentHashMap.computeIfAbsent(ConcurrentHashMap.java:1763)

Best Regards,
 Vladimir.

[1] 
https://buildd.debian.org/status/fetch.php?pkg=httpcomponents-client=all=4.5.14-1=1670330442=0
[2] https://github.com/apache/commons-logging/pull/177
[3] 
https://github.com/apache/commons-logging/commits/master/src/main/java/org/apache/commons/logging/impl/Slf4jLogFactory.java
[4] 
https://github.com/qos-ch/slf4j/blob/e9ee55cca93c2bf26f14482a9bdf961c750d2a56/slf4j-jcl/src/main/java/org/slf4j/impl/JCLLoggerFactory.java#L77
[5] 
https://launchpad.net/~vpa1977/+archive/ubuntu/october-21/+build/27798162/+files/buildlog_ubuntu-noble-amd64.httpcomponents-client_4.5.14-1_BUILDING.txt.gz