Your message dated Sat, 10 Jan 2026 21:47:05 +0000
with message-id <[email protected]>
and subject line Bug#1119076: fixed in ckb-next 0.6.2+dfsg-0.1+deb13u1
has caused the Debian Bug report #1119076,
regarding ckb-next: systemd service missing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1119076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1119076
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ckb-next
Version: 0.6.2+dfsg-0.1
Severity: important
X-Debbugs-Cc: [email protected]
Dear Maintainer,
I have received a bug report upstream [0] from a user who upgraded their
Debian-derivative system to the latest release and discovered that ckb-next
no longer runs out of the box.
After looking into it, I realised that the version of ckb-next in stable
lacks the systemd service for the daemon.
I am aware that this has been resolved in testing and unstable [1], however
I kindly urge you to resolve this in stable as it not only makes the
software unusable for non experienced users, but it also results in the
software itself being perceived as broken.
Users should not be expected to manually create or install services.
Thank you for your time.
[0] https://github.com/ckb-next/ckb-next/1226
[1] https://bugs.debian.org/1107406
-- System Information:
Debian Release: 13.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.48+deb13-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages ckb-next depends on:
ii libc6 2.41-12
ii libdbusmenu-qt5-2 0.9.3+16.04.20160218-3+b1
ii libgcc-s1 14.2.0-19
ii libpulse0 17.0+dfsg1-2+b1
ii libqt5core5t64 5.15.15+dfsg-6
ii libqt5dbus5t64 5.15.15+dfsg-6
ii libqt5gui5t64 5.15.15+dfsg-6
ii libqt5network5t64 5.15.15+dfsg-6
ii libqt5widgets5t64 5.15.15+dfsg-6
ii libqt5x11extras5 5.15.15-2
ii libquazip5-1t64 0.9.1-5
ii libstdc++6 14.2.0-19
ii libudev1 257.8-1~deb13u2
ii libxcb-ewmh2 0.4.2-1
ii libxcb-screensaver0 1.17.0-2+b1
ii libxcb1 1.17.0-2+b1
ckb-next recommends no packages.
ckb-next suggests no packages.
-- no debconf information
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ckb-next
Source-Version: 0.6.2+dfsg-0.1+deb13u1
Done: Lee Garrett <[email protected]>
We believe that the bug you reported is fixed in the latest version of
ckb-next, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Lee Garrett <[email protected]> (supplier of updated ckb-next package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Fri, 09 Jan 2026 19:08:27 +0100
Source: ckb-next
Architecture: source
Version: 0.6.2+dfsg-0.1+deb13u1
Distribution: trixie
Urgency: medium
Maintainer: Stewart Ferguson <[email protected]>
Changed-By: Lee Garrett <[email protected]>
Closes: 1119076
Changes:
ckb-next (0.6.2+dfsg-0.1+deb13u1) trixie; urgency=medium
.
* Non-maintainer upload.
* Fix typo causing init systems' config not to be installed (Closes:
#1119076)
* Add debian/gbp.conf to follow trixie release branch
* Correctly initialize sysv init scripts
* Ensure firmware updates are cryptographically verified
Checksums-Sha1:
bc20e6a8155cf46bbe49f58467df1ef6a8e38c89 2823
ckb-next_0.6.2+dfsg-0.1+deb13u1.dsc
bd9e0c93c75ab8762f3c6895f923b334d8648c49 7576
ckb-next_0.6.2+dfsg-0.1+deb13u1.debian.tar.xz
1819d79f52e94c946d6e5fdcb714edc59984e627 13535
ckb-next_0.6.2+dfsg-0.1+deb13u1_amd64.buildinfo
Checksums-Sha256:
0b2dcdb015ffae85c5975d64402c4db570c0a459b33d2a2c89f3199cc0682a0b 2823
ckb-next_0.6.2+dfsg-0.1+deb13u1.dsc
50e154d964fda61422f08e6c0c57a50003eeed708f5335b3b3510c0bbad820b9 7576
ckb-next_0.6.2+dfsg-0.1+deb13u1.debian.tar.xz
aa9b04c277cc4f81226a9db791842903255c796b74cf1813b876c6b8301760be 13535
ckb-next_0.6.2+dfsg-0.1+deb13u1_amd64.buildinfo
Files:
08942243be807d78ea151b3d516fe8ea 2823 electronics optional
ckb-next_0.6.2+dfsg-0.1+deb13u1.dsc
0e4b0106012e6ffa944866a0644dbab0 7576 electronics optional
ckb-next_0.6.2+dfsg-0.1+deb13u1.debian.tar.xz
0d305d49ba6f15943217203dc61b7520 13535 electronics optional
ckb-next_0.6.2+dfsg-0.1+deb13u1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQQzBAEBCgAdFiEE2EfGJRCpwv8kLOAs1gShxII+4PgFAmlhgnsACgkQ1gShxII+
4PiK6R//c5UddE0V9eibOOP9VA2Y14FNCXJfAuksAzb0PxNtunfedEhysQ+7CAkN
6tkgJPCUKlwan+/egS9+YRd9pUqnlfqtSszIMuU8khwQRwBghGE5Ovy31fiy1vbG
DjindKSce2dXms28l7S9BsrdRbfOkrmsu7dIydh1SEfmFykLxJTrA7sw1WdIoA8+
7IgTH1zq2g9UFE7xxDd3DzF/GsvM3VfbNUCvQlhm8oP6rYrciT1Mbb74d2M8D61y
Gc9XHlorIgjRvpBZTwiEodzcQwDKqsvL+BBc1Uj7Z/Hr/Hc8APwfupLpMJLLm8/Z
mfqNSOuanGFmV5WUcULQ+YHGCJjYrL6B7sOpMmyTpCQ6KchXOjx9T84J9bOJdAJE
vVYPrXX6e9Vq2IdlObZzJOv/PX1L3PNSaRBorKcTJ33R9gTylFepcmnmhb8qhnlx
RyR1PHL7zhcW7I7v5n16IiIVZ6CARGhjQUIrjuhmgxkXutSI8rjtpwHS8s06KI4J
xCgMY7VUqDiLNvilxxjxN0OLIKwy85D8xFGhHwN23PcM1SX7PoH5VPut50AXbK21
XMqQnXbSfXfac9j7JOw6Gi3O2g+cZs9F6wcDmwUfhFwcrad5v6Rmn6lMxNpT7fM+
xBBGlzrDQGdp9tlSkxZ1ZLSzSCiQfMO87jUeZlrtCh2ofG2vh/ueFlwb9Cz8KmSB
gnTnepC/miRDdC/xseUHkDvvJOy5VZkyCaS5nmFzgjXdrbu0KoMbjXk1azzOxck6
RCrXzhXwF3Wj7ZbNjnyfP5s28Inz2gF1+Ps8i9v+ryAF2B822wVTlA5fJLFZotuo
D5wvnBTlPx3RhfjlcpDX9VjJmrnGxm5Fzqo0jjVwhMEpTlv38O2xkafj3cecO1DW
RwemZprkwHA4WJIQCw9dActctsaPL9+w0NiG08zekPNC1r9jYwdrfvCpbmnClBn4
ctPUaqVS67YvYoETYWnwl8adTCLmLTP1TZH/1UsiRj5xIAh5oMQBObD/Bqt8Gd+v
T+zTytakOLDrJIKNt6wnf4te+AbvyykloYi5pFRWDNcseojTRPYo4eeaLli0R6og
UKeNgFPpjcZXPZOsXbY4rg5opSt9j1aR3E7wRtWKBm7J5MczEOBjOWg8HP442daD
LEnpUeN8P/yPSwXXWv9LS02BvmVf3vhSypRJI9jyzKG2VN3kWSt9iaYGaEEW7jKu
Uw7RNjd+LhEd8Tp82MGq1D5wBA9157lTzwjVIOzJq7WT1OeH9EHcYTsaRaKotDjQ
kyfSrG69bt8KaDrEAqC4o1T87o/2WUIkHq33sUHr3ZyrUAIiJW7Ajv9qw6Fdm3Ix
bw9bgsZEkaD4W7pg0XfapwlP2x81Dg==
=C9d+
-----END PGP SIGNATURE-----
pgpOook79lnSw.pgp
Description: PGP signature
--- End Message ---
