--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: unblock: linuxcnc/1:2.9.4-2
- From: Petter Reinholdtsen <pere@hungry.com>
- Date: Mon, 19 May 2025 12:50:54 +0200
- Message-id: <[🔎] sa6iklwg9gx.fsf@hjemme.reinholdtsen.name>
- In-reply-to: <trinity-8a80c29c-dfff-4a54-98b6-520557ec91d7-1747646014606@trinity-msg-rest-gmx-gmx-live-f4858f84-bnbqv>
- References: <trinity-441140b0-21e8-4b78-89a1-8c00b58c21d3-1747604211776@trinity-msg-rest-gmx-gmx-live-74d694d854-h6tdt> <sa6wmadi2pg.fsf@hjemme.reinholdtsen.name> <trinity-8a80c29c-dfff-4a54-98b6-520557ec91d7-1747646014606@trinity-msg-rest-gmx-gmx-live-f4858f84-bnbqv>
Package: release.debian.org
Control: affects -1 + src:linuxcnc
X-Debbugs-Cc: linuxcnc@packages.debian.org, Steffen Möller <steffen_moeller@gmx.de>
User: release.debian.org@packages.debian.org
Usertags: unblock
Severity: normal
Please unblock package linuxcnc
Yesterday it was drawn to my attention that the LinuxCNC package, which
us a machine and motor control software system for CNCs, plasma cutters,
robot arms etc, due to a cockup by the most active maintainer, fell out
of testing and the upload upload 35 days ago never migrated to testing.
Please allow it to enter testing, to provide those using the stable
edition today with a good upgrade path.
[ Reason ]
The package was supposed to make it to testing, but the maintainers ran
into a problem with epoc and confusion on which git repository to build
from, and failed to meet the deadline.
[ Impact ]
The major impact is that those currently using linuxcnc from Debian
Stable will not get an updated version with stability and security fixes
when upgrading to Trixie. We all want them to upgrade to a Debian
version with proper security maintenance and support. Another likely
result will be that they refuse to upgrade, and a slightly less likely
result is that they will start using LinuxCNC packages directly from the
upstream project instead of packages provided by Debian.
[ Tests ]
The build run several tests validating the behaviour of the program,
including cutter path planning verification and addon module behaviour.
There is also a more simple autopkgtest check verifying that LinuxCNC
tell motors to move the expected way.
[ Risks ]
There is no alternative to LinuxCNC in Debian today. It is a leaf
package with a small and dedicated user base, and the program was
available in testing until 2025-03-11 when a RC issue since fixed pulled
it out. I believe the risk with intrudicng the package back into
testing is non-existent, and the downsides of not doing so is fairly
small (0.03% of the popcon population ran it last week) but real.
[ Checklist ]
[x] all changes are documented in the d/changelog
[ ] I reviewed all changes and I approve them
[ ] attach debdiff against the package in testing
(I do not know what to compare against? The version previously in
testing or the one in stable, so did not check the last two in the
checklist.)
[ Other info ]
I am a member of the upstream LinuxCNC team, but not very active in the
Debian maintenance of it. I was asked by the upstream team to see if I
could help get the package back into testing, hence this email. Note, I
agree with those contacting me from the upstream team that it would be a
very good thing to have LinuxCNC in Trixie, as it was in Bookworm.
unblock linuxcnc/1:2.9.4-2
--
Happy hacking
Petter Reinholdtsen
--- End Message ---