Debian Patches
Status for pydicom/3.0.2-4
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| import-metadata-version-string.patch | import metadata version string In Debian build environments the package is not installed at documentation build time, so package metadata is unavailable. Fallback to a static version to ensure Sphinx can import the module. |
Karsten Schöke <karsten.schoeke@geobasis-bb.de> | not-needed | 2026-05-04 | ||
| pytest.ini-insert-file-to-deaktivate-tests.patch | pytest.ini insert file to deaktivate tests | Karsten Schöke <karsten.schoeke@geobasis-bb.de> | not-needed | 2026-05-06 | ||
| doc-conf.py-sphinx-use-local-inventory-references-fo.patch | doc/conf.py sphinx use local inventory references for intersphin Note that we will not be making this conditional: we want the build to fail if intersphinx was to fetch inventory data from the internet. |
Karsten Schöke <karsten.schoeke@geobasis-bb.de> | not-needed | 2026-05-07 | ||
| doc-conf.py-deactivate-performance-datafooter-in-doc.patch | doc/conf.py deactivate performance datafooter in doc Make the build reproducible | Karsten Schöke <karsten.schoeke@geobasis-bb.de> | not-needed | 2026-05-12 | ||
| fix-example-for-reproducible-build.patch | fix example for reproducible build. Removal of the display of temporary files containing hashes in their names, thereby rendering the reproducible build impossible. |
Karsten Schöke <karsten.schoeke@geobasis-bb.de> | not-needed | 2026-05-12 | ||
| make-documentation-example-reproducible.patch | Make documentation example reproducibleThe DICOM writing example uses datetime.now() to generate ContentDate and ContentTime values. These values are printed by the example and end up in the generated Sphinx-Gallery HTML output, resulting in build-dependent documentation. . Use fixed timestamps instead to ensure reproducible builds. |
Karsten Schöke <karsten.schoeke@geobasis-bb.de> | not-needed | 2026-06-10 | ||
| fix-fileset-uid-property-annotation.patch | fix-fileset-uid-property-annotation with Python 3.14Python 3.14 may resolve the UID annotation of a property named UID to the property object itself. This causes Sphinx autodoc to include the property object's memory address in the generated documentation, resulting in architecture-dependent documentation and FTBR failures. Use an explicitly qualified UID type for the affected UID properties in FileSet and CoderBase to avoid the name collision. |
Karsten Schöke <karsten.schoeke@geobasis-bb.de> | yes | 2026-08-24 |