Debian navigation

Notes about issue random_order_in_java_jar_manifest_mf in unstable

Identifier: random_order_in_java_jar_manifest_mf
Suites: stretch / buster / unstable / experimental
Description: Java .jar files written by some tools have a random order in MANIFEST.MF.
Packages in 'unstable' known to be affected by this issue:
(the 1/4 most-popular ones (within this issue) are underlined)

reproducible icon 17 reproducible packages in unstable/amd64: apache-directory-jdbm assertj-core epubcheck hawtdispatch httpcomponents-client istack-commons jackson-core jackson-dataformat-xml jackson-jaxrs-providers jackson-module-jaxb-annotations jaxb-api libjdo-api-java libjdom1-java libjdom2-java libxalan2-java testng xmlstreambuffer

FTBFS icon 2 FTBFS packages in unstable/amd64: jackson-databind guacamole-client#

FTBR icon 1 unreproducible packages in unstable/amd64: r-cran-lambda.r

 

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.