Bug#1011935: (no subject)

2022-05-27 Thread tsteven4 
Why do many qt6 packages have a dependency on qtchooser if you are not 
supporting Qt6 with qtchooser?


  qt6-webengine-dev-tools
  qt6-l10n-tools
  qt6-documentation-tools
  qt6-declarative-dev-tools
  qt6-base-dev-tools
  qmlscene-qt6
  qml-qt6
  assistant-qt6
  linguist-qt6
  designer-qt6

Bug#1013610: (no subject)

2022-06-26 Thread tsteven4 
The underlying issue here is likely 
https://bugreports.qt.io/browse/QTBUG-91558

Bug#1022197: fix correction

2022-10-21 Thread tsteven4 

The original report dropped the final double quote in the fix.  Here is the 
corrected fix.

   $ diff /usr/bin/fop fop
   46c46
   < . $HOME/.foprc
   ---
   > . "$HOME/.foprc"

Bug#1068931: libdom4j-java version numbering

2024-04-13 Thread tsteven4 

Package: libdom4j-java

Version: 2.1.4-1

The package uses the source for 2.1.4, but the project/version element 
has value 2.1.1 in debian/pom.xml.

Bug#1068931: pom.xml version impact

2024-04-16 Thread tsteven4 
Having the wrong version in pom.xml results in the deb having the 
following files incorrectly named:


root@d19edf0ef10b:/app# diff before after
9c9
< -rw-r--r-- root/root    323778 2024-01-05 16:32 
./usr/share/java/dom4j-2.1.1.jar

---
> -rw-r--r-- root/root    323778 2024-01-05 16:32 
./usr/share/java/dom4j-2.1.4.jar

18,19c18,19
< drwxr-xr-x root/root 0 2024-01-05 16:32 
./usr/share/maven-repo/org/dom4j/dom4j/2.1.1/
< -rw-r--r-- root/root  2230 2024-01-05 16:32 
./usr/share/maven-repo/org/dom4j/dom4j/2.1.1/dom4j-2.1.1.pom

---
> drwxr-xr-x root/root 0 2024-01-05 16:32 
./usr/share/maven-repo/org/dom4j/dom4j/2.1.4/
> -rw-r--r-- root/root  2230 2024-01-05 16:32 
./usr/share/maven-repo/org/dom4j/dom4j/2.1.4/dom4j-2.1.4.pom

22,24c22,24
< lrwxrwxrwx root/root 0 2024-01-05 16:32 
./usr/share/java/dom4j.jar -> dom4j-2.1.1.jar
< lrwxrwxrwx root/root 0 2024-01-05 16:32 
./usr/share/maven-repo/org/dom4j/dom4j/2.1.1/dom4j-2.1.1.jar -> 
../../../../../java/dom4j-2.1.1.jar
< lrwxrwxrwx root/root 0 2024-01-05 16:32 
./usr/share/maven-repo/org/dom4j/dom4j/debian/dom4j-debian.jar -> 
../../../../../java/dom4j-2.1.1.jar

---
> lrwxrwxrwx root/root 0 2024-01-05 16:32 
./usr/share/java/dom4j.jar -> dom4j-2.1.4.jar
> lrwxrwxrwx root/root 0 2024-01-05 16:32 
./usr/share/maven-repo/org/dom4j/dom4j/2.1.4/dom4j-2.1.4.jar -> 
../../../../../java/dom4j-2.1.4.jar
> lrwxrwxrwx root/root 0 2024-01-05 16:32 
./usr/share/maven-repo/org/dom4j/dom4j/debian/dom4j-debian.jar -> 
../../../../../java/dom4j-2.1.4.jar


That may be responsible for at least one tool flagging a security 
vulnerability that was fixed in 2.1.3.  Docker scout reports:


CRITICAL    CVE-2020-10683
pkg:maven/org.dom4j/dom4j@2.1.1

9.8

1 image
Yes

2.1.3