DFSG NEW Queue

DFSG, Licensing & New Packages Team

pysavitar 5.3.0-1

Package Information

Description3MF file handling library (Python bindings)

Savitar is a C++ library with Python 3 bindings for reading and writing 3MF files.

3MF is an interchange format for sharing 3D models and other 3D printing data between related software and 3D printers. It is XML based and standardised by the 3MF consortium.

This package contains the Python 3 bindings.

MaintainerDebian 3-D Printing Packages <3dprinter-general@lists.alioth.debian.org>
Changed ByChristoph Berg <myon@debian.org>
Sponsormyon@debian.org
Distributionexperimental
Architectureany
VCSgit: https://salsa.debian.org/3dprinting-team/pysavitar.git (browse)
Trackerhttps://tracker.debian.org/pkg/pysavitar
Uploaded2 hours ago

Takes Over Existing Binary Packages

This upload builds binary packages that a different source package currently builds in unstable. Check that the takeover is intended and explained, for example in the changelog.

BinaryCurrently built by
python3-savitarlibsavitar

New Package Report

.changes◂
Changed-ByChristoph Berg <myon@debian.org>
Architecturesource amd64
Distributionexperimental
DateWed, 04 Nov 2026 12:00:00 +0100
Sourcepysavitar
Version5.3.0-1
Changelog◂
pysavitar (5.3.0-1) experimental; urgency=medium
 .
   * Initial release.  This is the Python bindings split out of libSavitar
     5.2.0 into a separate upstream project.
.dsc◂
Sectionpython
Priorityoptional
Componentmain
Package-Listpython3-savitar deb python optional arch=any
debian/copyright◂
Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: pySavitar
Source: https://github.com/Ultimaker/pySavitar

Files: *
Copyright: 2022 Ultimaker B.V.
License: LGPL-3+

Files: debian/*
Copyright:
 2016-2017 Gregor Riepl <onitake@gmail.com>
 2017 Petter Reinholdtsen <pere@debian.org>
 2020-2026 Christoph Berg <myon@debian.org>
License: BSD-3-clause

License: BSD-3-clause
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions
 are met:
 .
 1. Redistributions of source code must retain the copyright
    notice, this list of conditions and the following disclaimer.
 2. Redistributions in binary form must reproduce the copyright
    notice, this list of conditions and the following disclaimer in the
    documentation and/or other materials provided with the distribution.
 3. The name of the author may not be used to endorse or promote products
    derived from this software without specific prior written permission.
 .
 THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
 IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
 OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
 IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
 INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
 NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
 DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
 THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
 (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
 THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

License: Expat
 Permission is hereby granted, free of charge, to any person
 obtaining a copy of this software and associated documentation
 files (the "Software"), to deal in the Software without
 restriction, including without limitation the rights to use,
 copy, modify, merge, publish, distribute, sublicense, and/or sell
 copies of the Software, and to permit persons to whom the
 Software is furnished to do so, subject to the following
 conditions:
 .
 The above copyright notice and this permission notice shall be
 included in all copies or substantial portions of the Software.
 .
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
 EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
 OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
 NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
 HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
 WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
 FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
 OTHER DEALINGS IN THE SOFTWARE.

License: LGPL-3+
 [/usr/share/common-licenses/LGPL-3]
 GNU LESSER GENERAL PUBLIC LICENSE
                        Version 3, 29 June 2007
 .
  Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
  Everyone is permitted to copy and distribute verbatim copies
  of this license document, but changing it is not allowed.
 .
 .
   This version of the GNU Lesser General Public License incorporates
 the terms and conditions of version 3 of the GNU General Public
 License, supplemented by the additional permissions listed below.
 .
   0. Additional Definitions.
 .
   As used herein, "this License" refers to version 3 of the GNU Lesser
 General Public License, and the "GNU GPL" refers to version 3 of the GNU
 General Public License.
 .
   "The Library" refers to a covered work governed by this License,
 other than an Application or a Combined Work as defined below.
 .
   An "Application" is any work that makes use of an interface provided
 by the Library, but which is not otherwise based on the Library.
 Defining a subclass of a class defined by the Library is deemed a mode
 of using an interface provided by the Library.
 .
   A "Combined Work" is a work produced by combining or linking an
 Application with the Library.  The particular version of the Library
 with which the Combined Work was made is also called the "Linked
 Version".
 .
   The "Minimal Corresponding Source" for a Combined Work means the
 Corresponding Source for the Combined Work, excluding any source code
 for portions of the Combined Work that, considered in isolation, are
 based on the Application, and not on the Linked Version.
 .
   The "Corresponding Application Code" for a Combined Work means the
 object code and/or source code for the Application, including any data
 and utility programs needed for reproducing the Combined Work from the
 Application, but excluding the System Libraries of the Combined Work.
 .
   1. Exception to Section 3 of the GNU GPL.
 .
   You may convey a covered work under sections 3 and 4 of this License
 without being bound by section 3 of the GNU GPL.
 .
   2. Conveying Modified Versions.
 .
   If you modify a copy of the Library, and, in your modifications, a
 facility refers to a function or data to be supplied by an Application
 that uses the facility (other than as an argument passed when the
 facility is invoked), then you may convey a copy of the modified
 version:
 .
    a) under this License, provided that you make a good faith effort to
    ensure that, in the event an Application does not supply the
    function or data, the facility still operates, and performs
    whatever part of its purpose remains meaningful, or
 .
    b) under the GNU GPL, with none of the additional permissions of
    this License applicable to that copy.
 .
   3. Object Code Incorporating Material from Library Header Files.
 .
   The object code form of an Application may incorporate material from
 a header file that is part of the Library.  You may convey such object
 code under terms of your choice, provided that, if the incorporated
 material is not limited to numerical parameters, data structure
 layouts and accessors, or small macros, inline functions and templates
 (ten or fewer lines in length), you do both of the following:
 .
    a) Give prominent notice with each copy of the object code that the
    Library is used in it and that the Library and its use are
    covered by this License.
 .
    b) Accompany the object code with a copy of the GNU GPL and this license
    document.
 .
   4. Combined Works.
 .
   You may convey a Combined Work under terms of your choice that,
 taken together, effectively do not restrict modification of the
 portions of the Library contained in the Combined Work and reverse
 engineering for debugging such modifications, if you also do each of
 the following:
 .
    a) Give prominent notice with each copy of the Combined Work that
    the Library is used in it and that the Library and its use are
    covered by this License.
 .
    b) Accompany the Combined Work with a copy of the GNU GPL and this license
    document.
 .
    c) For a Combined Work that displays copyright notices during
    execution, include the copyright notice for the Library among
    these notices, as well as a reference directing the user to the
    copies of the GNU GPL and this license document.
 .
    d) Do one of the following:
 .
        0) Convey the Minimal Corresponding Source under the terms of this
        License, and the Corresponding Application Code in a form
        suitable for, and under terms that permit, the user to
        recombine or relink the Application with a modified version of
        the Linked Version to produce a modified Combined Work, in the
        manner specified by section 6 of the GNU GPL for conveying
        Corresponding Source.
 .
        1) Use a suitable shared library mechanism for linking with the
        Library.  A suitable mechanism is one that (a) uses at run time
        a copy of the Library already present on the user's computer
        system, and (b) will operate properly with a modified version
        of the Library that is interface-compatible with the Linked
        Version.
 .
    e) Provide Installation Information, but only if you would otherwise
    be required to provide such information under section 6 of the
    GNU GPL, and only to the extent that such information is
    necessary to install and execute a modified version of the
    Combined Work produced by recombining or relinking the
    Application with a modified version of the Linked Version. (If
    you use option 4d0, the Installation Information must accompany
    the Minimal Corresponding Source and Corresponding Application
    Code. If you use option 4d1, you must provide the Installation
    Information in the manner specified by section 6 of the GNU GPL
    for conveying Corresponding Source.)
 .
   5. Combined Libraries.
 .
   You may place library facilities that are a work based on the
 Library side by side in a single library together with other library
 facilities that are not Applications and are not covered by this
 License, and convey such a combined library under terms of your
 choice, if you do both of the following:
 .
    a) Accompany the combined library with a copy of the same work based
    on the Library, uncombined with any other library facilities,
    conveyed under the terms of this License.
 .
    b) Give prominent notice with the combined library that part of it
    is a work based on the Library, and explaining where to find the
    accompanying uncombined form of the same work.
 .
   6. Revised Versions of the GNU Lesser General Public License.
 .
   The Free Software Foundation may publish revised and/or new versions
 of the GNU Lesser General Public License from time to time. Such new
 versions will be similar in spirit to the present version, but may
 differ in detail to address new problems or concerns.
 .
   Each version is given a distinguishing version number. If the
 Library as you received it specifies that a certain numbered version
 of the GNU Lesser General Public License "or any later version"
 applies to it, you have the option of following the terms and
 conditions either of that published version or of any later version
 published by the Free Software Foundation. If the Library as you
 received it does not specify a version number of the GNU Lesser
 General Public License, you may choose any version of the GNU Lesser
 General Public License ever published by the Free Software Foundation.
 .
   If the Library as you received it specifies that a proxy can decide
 whether future versions of the GNU Lesser General Public License shall
 apply, that proxy's public statement of acceptance of any version is
 permanent authorization for you to choose that version for the
 Library.

DFSG Assistant LLM REVIEW 0 blocker, 0 important, 2 minor

This is an LLM based review using a Debian Inference based workflow. It was not written by a member of the DFSG team and has not been checked by one. It is not a decision on the package: it may be wrong, and it may have missed things.

Reviewed 1 hour ago.

Report◂

DFSG NEW review for pysavitar version 5.3.0-1

Summary

  • Licensing is DFSG-compliant and debian/copyright is accurate: Yes
  • Packaging is of good quality: Yes
  • Issues: 0 blocker, 0 important, 2 minor
  • debian/watch: version 5
  • debian/copyright: machine-readable
  • Scan before the review: nothing found

Licensing

Upstream is LGPL-3+ and DFSG-free: all six python/*.sip files carry // Copyright (c) 2022 Ultimaker B.V. and // pySavitar is released under the terms of the LGPLv3 or higher., the top-level LICENSE is the full LGPL-3 text, and README.md names LGPLv3. debian/copyright is DEP-5 with a Files: * stanza (2022 Ultimaker B.V., LGPL-3+) and a later debian/* stanza (BSD-3-clause, three Debian holders), and reproduces the BSD-3-clause notice plus an LGPL-3+ paragraph pointing at /usr/share/common-licenses/LGPL-3. No non-free wording, no built or minified files, no vendored third-party code, and nothing has an unclear licence. The prescan's only hit is a false positive (the SIP header line matched as a holder name).

Packaging

Standard modern packaging for a SIP binding: debhelper-compat 13, pybuild with the PEP 517 pyproject build system, dh-python, hardening enabled, Rules-Requires-Root: no, Standards-Version 4.7.4, DEP-5 copyright, 3.0 (quilt), a gbp.conf, salsa CI and an autopkgtest that imports the module for every supported Python. Two minor points: the versioned build dependency on libsavitar 5.3.0 is not yet satisfiable from the archive, and the single Debian-only patch has no DEP-3 header.

Issues

minor packaging 1. Build-Depends libsavitar-dev (>= 5.3.0) cannot be satisfied from the archive, and python3-savitar is still built by source libsavitar ◂
  • Files: debian/control:13, debian/changelog
  • Basis: checked, in the package or with a reference tool
  • Evidence: debian/control: libsavitar-dev (>= 5.3.0),; apt-cache on this system: Package: libsavitar-dev / Source: libsavitar (5.0.0-4.1) / Version: 5.0.0-4.1+b9, and Package: python3-savitar / Source: libsavitar (5.0.0-4.1).
  • Problem: The only libsavitar-dev in unstable/experimental is 5.0.0-4.1, so an sbuild in a clean sid chroot cannot satisfy the versioned Build-Depends, and the binary name python3-savitar is still produced by the libsavitar source package, so dak would reject a second source shipping it. The upload therefore depends on a libsavitar 5.3.0 that drops the Python bindings binary and that is not in the archive (nor in NEW) yet; the target experimental in changelog is consistent with that, but nothing in the package records the dependency on that upload.
  • Fix: Upload libsavitar 5.3.0 (with the Python bindings binary removed from it) before or together with this package, or state the requirement in the changelog if 5.3.0 is only about to be uploaded; keep the versioned dependency since the .sip files use the 5.3.0 API.
minor packaging 2. The only patch, which creates pyproject.toml, has no DEP-3 header (no Description, Author or Forwarded) ◂
  • Files: debian/patches/0001-add-pyproject-toml.patch:1
  • Basis: checked, in the package or with a reference tool
  • Evidence: The patch starts directly with --- a/pyproject.toml 1970-01-01 01:00:00.000000000 +0100; the only statement of its purpose is the comment in debian/rules: # The source tree still carries upstream's Conan-oriented CMakeLists.txt; build # the SIP module through its PEP 517 backend instead.
  • Problem: The patch adds a whole build file with a hardcoded version = "5.3.0" and libraries = ["Savitar"], and upstream's .gitignore lists pyproject.toml, i.e. this is Debian-only glue that upstream should carry. Without a Description/Forwarded header neither its purpose nor its upstream status is recorded, which DEP-3 asks for and which Policy 4.3 supports for changes worth sending upstream.
  • Fix: Add a DEP-3 header (Description, Origin/Author, Forwarded: not-needed or a bug URL) to debian/patches/0001-add-pyproject-toml.patch and, ideally, offer the pyproject.toml upstream.
Verified ◂
  • debian/copyright read in full: DEP-5, two Files stanzas (* then debian/*, which overrides it for debian/ files) and stand-alone License paragraphs for BSD-3-clause, Expat and LGPL-3+ (the last pointing at /usr/share/common-licenses/LGPL-3 with the full text). The Expat paragraph is unused but harmless.
  • Prescan item python/{MeshData,MetadataEntry,Scene,SceneNode,Types,pySavitar}.sip: each begins with // Copyright (c) 2022 Ultimaker B.V. and // pySavitar is released under the terms of the LGPLv3 or higher. The scan's Ultimaker B.V. pySavitar is released is that second header line, not a separate holder: the holder is already named in Files: *, and LGPL-3+ matches the or higher wording.
  • Whole tree inspected except .pc/: LICENSE (unmodified LGPL-3), README.md, CMakeLists.txt, conanfile.py, pyproject.toml (created by the quilt patch), python/*.sip, test_package/conanfile.py, test_package/test.py, .clang-format, .clang-tidy, .gitignore and .github/workflows/{conan-package.yml,process-pull-request.yml,requirements-conan-package.txt}. None carries a second licence or holder; the workflows only call ultimaker/cura reusable workflows, no copied code.
  • No built artefacts (no .so, .pyc, minified code, archives, PDFs, images or fonts) in the tree; no vendored library -- the Savitar C++ library itself is not shipped, the module links the system libSavitar (libsavitar-dev). The applied .pc/ copy was ignored as instructed.
  • README.md's You need to share the source of any pySavitar modifications is a lay summary of LGPL-3 under a 'boils down to' heading pointing at LICENSE; it adds no term.
  • debian/rules works as written: /usr/share/dh-python/dhpython/build/plugin_pyproject.py registers the pyproject plugin, whose configure step only needs python3-build and python3-installer (both in Build-Depends); dh-python 7 provides dh-sequence-python3, so --with python3 at compat 13 is fine; pybuild's default test runner is unittest discover with ignore_no_tests, so no python3-pytest is needed (and no upstream tests are run at build time).
  • debian/tests/control (Tests: import, Depends: python3-all, @,), tests/import, gbp.conf, source/format (3.0 quilt), salsa-ci.yml, changelog date (2026-11-04 is a Wednesday) and Standards-Version 4.7.4 (current 4.7.x) checked.
  • uscan found the packaged version as the newest upstream release (upstream 5.3.0, packaged 5.3.0).
  • Every pointer of debian/copyright to /usr/share/common-licenses names a file that is there (LGPL-3).
Not confirmed ◂
  • The Savitar headers and signatures the .sip files use (Savitar/ThreeMFParser.h, Savitar/Scene.h, ThreeMFParser::parse, Scene::getAllSceneNodes) could not be checked against libsavitar 5.3.0, which is not available on this system; a build would show a compile error if the API does not match.
  • The existence of the salsa repositories named in Vcs-Git/Vcs-Browser could not be checked (no network).
Proposed changes ◂

None.

Uploader's response to the LLM review

libsavitar 5.3 which does not build python3-savitar anymore has already been uploaded to experimental (and this is upload is for experimental as well.)

— Christoph Berg (myon), 1 hour ago

Back to Dashboard | View all reviews for this package