pyarcus 5.3.0-1
Package Information
| Description | message queue for Cura based on protobuf (Python bindings) This library contains C++ code and Python3 bindings for creating a socket in a thread and using this socket to send and receive messages based on the Protocol Buffers library. It is designed to facilitate the communication between Cura and its backend and similar code. This package contains the Python 3 bindings. |
|---|---|
| Maintainer | Debian 3-D Printing Packages <3dprinter-general@lists.alioth.debian.org> |
| Changed By | Christoph Berg <myon@debian.org> |
| Sponsor | myon@debian.org |
| Distribution | experimental |
| Architecture | any |
| VCS | git: https://salsa.debian.org/3dprinting-team/pyarcus.git (browse) |
| Tracker | https://tracker.debian.org/pkg/pyarcus |
| Uploaded | 3 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.
| Binary | Currently built by |
|---|---|
python3-arcus | libarcus |
New Package Report
.changes
| Version | 5.3.0-1 |
|---|---|
| Changed-By | Christoph Berg <myon@debian.org> |
| Architecture | source amd64 |
| Distribution | experimental |
| Date | Wed, 04 Nov 2026 12:00:00 +0100 |
| Source | pyarcus |
Changelog
pyarcus (5.3.0-1) experimental; urgency=medium
.
* Initial release. This is the Python bindings split out of libArcus 5.2.0
into a separate upstream project..dsc
| Component | main |
|---|---|
| Package-List | python3-arcus deb python optional arch=any |
| Section | python |
| Priority | optional |
debian/copyright
Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Upstream-Name: pyArcus
Source: https://github.com/Ultimaker/pyArcus
Files: *
Copyright: 2015-2022 Ultimaker B.V.
License: LGPL-3+
Files: debian/*
Copyright: 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: 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 pyarcus version 5.3.0-1
Summary
- Licensing is DFSG-compliant and
debian/copyrightis 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
All upstream files are Ultimaker B.V. work under LGPL-3 or later (each C/C++/sip file says 'pyArcus is released under the terms of the LGPLv3 or higher', and the top-level LICENSE is LGPL-3), debian/ is BSD-3-clause, and debian/copyright is DEP-5 with the correct short names, full BSD text and a pointer to /usr/share/common-licenses/LGPL-3. No non-free terms, no unlicensed file, no generated or binary-only file: the sip binding's C++ is generated from the shipped python/*.sip. The only inaccuracy is that the top-level pyproject.toml, which the Debian patch creates, is claimed in the Files: * stanza as Ultimaker's LGPL-3+ work.
Packaging
Modern and sound: debhelper compat 13, dh with pybuild and PYBUILD_SYSTEM=pyproject building the SIP module through its PEP 517 backend, all substvars present, autopkgtest 'import' present and consistent with python3-all-dev, DEP-5 copyright, Vcs-* and a sane changelog. The only quality faults are minor: the patch that adds pyproject.toml has no DEP-3 header, and the pyproject.toml it adds is misattributed in debian/copyright.
Issues
minor licensing 1. Files: * attributes the Debian-added pyproject.toml to Ultimaker B.V. under LGPL-3+ ◂
- Files:
debian/copyright:5-7,pyproject.toml,debian/patches/0001-add-pyproject-toml.patch - Basis: checked, in the package or with a reference tool
- Evidence:
Files: */Copyright: 2015-2022 Ultimaker B.V./License: LGPL-3+; the patch starts with--- a/pyproject.toml 1970-01-01 01:00:00.000000000 +0100, and.gitignore:74listspyproject.toml, so the file is not in the upstream tarball. - Problem: copyright-format 6.3 requires each file's actual copyright holders and licence. The top-level pyproject.toml exists only because of the Debian patch (upstream generates it with its Conan toolchain and does not ship it), so neither Ultimaker's copyright nor LGPL-3+ is an accurate statement for that file; the comment in debian/rules makes clear it is the packager's build wiring.
- Fix: Add a
Files: pyproject.tomlstanza (Copyright: 2026 Christoph Berg myon@debian.org, License: BSD-3-clause), or drop the patch and generate the file from debian/rules, in which case it is covered by debian/*.
minor packaging 2. Patch 0001-add-pyproject-toml.patch has no DEP-3 header (no Description, Origin or Forwarded) ◂
- Files:
debian/patches/0001-add-pyproject-toml.patch:1,debian/patches/series:1 - Basis: checked, in the package or with a reference tool
- Evidence: The file begins directly with
--- a/pyproject.toml 1970-01-01 01:00:00.000000000 +0100, with noDescription:/Forwarded:fields;.gitignoreshows upstream generates this file from its Conanpyprojecttoolchain. - Problem: The only patch in the package adds a build file, and neither its purpose nor whether it was offered upstream is recorded. DEP-3 headers are the established way to make a patch self-documenting for the next maintainer and for the upstream release that will make it unnecessary.
- Fix: Add a DEP-3 header with a one-line Description and a Forwarded field (forwarding the file to Ultimaker, since upstream's Conan build generates the same content), so the patch can be dropped when 5.4.0 ships with it.
Verified ◂
- Read all of debian/ except debian/watch (out of scope): changelog, control, copyright, rules, source/format, gbp.conf, salsa-ci.yml, patches/series, patches/0001-add-pyproject-toml.patch, tests/control, tests/import.
- Upstream inventory (21 files, .pc/ excluded): LICENSE, README.md, CMakeLists.txt, conanfile.py, .clang-format, .clang-tidy, .gitignore, .github/workflows/{conan-package.yml,process-pull-request.yml,requirements-conan-package.txt}, include/pyArcus/PythonMessage.h, python/{pyArcus,Types,SocketListener,PythonMessage,Error}.sip, src/PythonMessage.cpp, test_package/{conanfile.py,test.proto,test.py}, pyproject.toml.
- Every C/C++/sip file carries
// Copyright (c) 2022 Ultimaker B.V.and// pyArcus is released under the terms of the LGPLv3 or higher.; README and conanfile.py name Ultimaker and LGPL-3 (conanfilelicense = "LGPL-3.0"); the remaining files carry no separate notices and are covered by the top-level LICENSE, which is the LGPL-3 text. - Prescan holder: the flagged 'Ultimaker B.V. pyArcus is released' matches the header of include/pyArcus/PythonMessage.h, src/PythonMessage.cpp and the five python/*.sip files, and
Files: *namesUltimaker B.V., so no holder is missing from debian/copyright. - No non-free wording in the tree (no non-commercial/ND clauses, no 'Good, not Evil'), no file without a licence path, and no built binaries, minified files, archives or PDFs: the SIP module's C++ is generated at build time from the shipped python/*.sip, so the preferred form for modification is present.
- test_package/{conanfile.py,test.proto,test.py} are upstream's Conan test recipe and data, not built or installed by the Debian package; .github/workflows/* is upstream CI configuration referencing external actions; no vendored third-party code is embedded.
- pyproject.toml is not upstream content:
.gitignore:74listspyproject.toml, and debian/patches/0001-add-pyproject-toml.patch creates it. - Build wiring checked against /usr/share/dh-python/dhpython/build/plugin_pyproject.py: the pyproject build system is part of dh-python and needs python3-build, python3-installer and the sipbuild backend; Build-Depends has the first two and python3-sipbuild (which Depends python3-setuptools), so the absent python3-setuptools/python3-wheel entries are not a fault, and pybuild runs
python3 -m build --no-isolation --wheel. - Autopkgtest: tests/import is
Restrictions: superficial, Depends python3-all, and imports pyArcus with everypy3versions -sinterpreter, consistent with building for python3-all-dev. - Standards-Version 4.7.4: its first two components match the reviewing system's Policy 4.7.x, so it is not an issue.
- python3-arcus is currently also built by libarcus 5.0.0-6 (apt-cache); pyarcus's python3-arcus 5.3.0-1 is the higher version, so the upgrade path is ordinary, but libarcus must stop building that binary to avoid a later conflict.
- uscan found the packaged version as the newest upstream release (upstream
5.3.0, packaged5.3.0). - Every pointer of
debian/copyrightto /usr/share/common-licenses names a file that is there (LGPL-3).
Not confirmed ◂
- libarcus-dev (>= 5.3.0) in Build-Depends: apt-cache shows only 5.0.0-6+b4 in unstable/experimental, so the versioned dependency cannot be satisfied from the package lists; if libarcus 5.3.0 is waiting in NEW this is only sequencing, which I could not see, and a build would otherwise fail dependency resolution.
- Nothing was built or run: sip code generation, the build and the autopkgtest could not be exercised in this read-only review.
Proposed changes ◂
None.
Uploader's response to the LLM review
The uploader was emailed about the review 1 hour ago.