Notes about issue build_path_used_to_determine_version_or_package_name in experimental
| Identifier: | build_path_used_to_determine_version_or_package_name |
|---|---|
| Suites: | unstable / trixie / bookworm / bullseye / experimental |
| Description: |
The package assumes to be build in a PACKAGE-VERSION directory to parse version and/or package name information. . For packages using python-param, see nondeterministic_version_generated_by_python_param. |
|
Packages in 'experimental' 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.