Notes about issue extended_attributes_in_jar_file_created_without_manifest in unstable
| Identifier: | extended_attributes_in_jar_file_created_without_manifest |
|---|---|
| Suites: | unstable / trixie / bookworm / bullseye / experimental |
| URL: | https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8286712 |
| Description: |
Creating a jar file with the -M flag causes jar(1) to add extended attributes to the last file added to the archive. As files are not added in a deterministic order (if, say, a directory is specified on the command-line), this means that even if the files are subsequently sorted, the extended attribute is moved around independently as well. First seen in src:threeb via https://salsa.debian.org/reproducible-builds/strip-nondeterminism/-/issues/19. Submitted to upstream - "We will review your report and have assigned it an internal review ID 9073223" |
|
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.