Discussion:
Bug#1093470: python3-fastapi
Add Reply
Julian Gilbey
2025-01-19 07:40:01 UTC
Reply
Permalink
Package: python3-fastapi
Version: 0.115.5-3
Severity: serious
Tags: patch

python3-fastapi installs a spurious file (log.txt) in the top
directory of the python dist-packages tree. This needs to be
removed. (It would not be an issue, or only a minor one, if it were
under the fastapi subdirectory.)

Patch:

--- fastapi-0.115.5/debian/python3-fastapi.pyremove 1970-01-01 01:00:00.000000000 +0100
+++ fastapi-0.115.5/debian/python3-fastapi.pyremove 2025-01-14 20:46:24.000000000 +0000
@@ -0,0 +1 @@
+log.txt


I'll fix this with an NMU in about a week.

Best wishes,

Julian
Debian Bug Tracking System
2025-01-19 08:30:01 UTC
Reply
Permalink
tags -1 +moreinfo
Bug #1093470 [python3-fastapi] python3-fastapi: installs spurious log.txt file at top of python3/dist-packages tree
Added tag(s) moreinfo.
--
1093470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093470
Debian Bug Tracking System
Contact ***@bugs.debian.org with problems
Julian Gilbey
2025-01-19 19:00:01 UTC
Reply
Permalink
control: tags -1 +moreinfo
Post by Julian Gilbey
Package: python3-fastapi
Version: 0.115.5-3
Severity: serious
what is the policy violation that warranted this severity?
Policy is not (and was never) intended to be exhaustive, but rather to
codify practices that are required for packages to interoperate and to
work within the Debian ecosystem. There are many things that are
"obvious" that are not stated in policy; as an extreme example (which
would certainly fail on other criteria), there is no policy statement
"you must not include malware in your package". As a minor example
not mentioned, "you should ensure that the spelling of words in the
package synopsis and extended description is correct". As an
in-between example, under which this falls, "you must not include
build logs or artefacts of test runs in your binary package (unless
they are required for the package to function normally)". In this
case, with the artefact lying at the root of the Python dist-modules
tree, and therefore having the potential to cause issues for other
Python packages now or in the future, it seems that severity "serious"
is appropriate.

Best wishes,

Julian

Loading...