Your message dated Mon, 05 Jan 2026 14:56:20 +0000
with message-id <[email protected]>
and subject line Bug#1120034: fixed in lx-gdb 1.03-16.1
has caused the Debian Bug report #1120034,
regarding lx-gdb: Intend to Orphan: lx-gdb
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.)
--
1120034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1120034
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: lx-gdb
Version: 1.03-16
Severity: important
X-Debbugs-Cc: Mark W. Eichin <[email protected]>, [email protected],
Package Salvaging Team <[email protected]>
Hi,
This is an attempt to introduce a new procedure, which I propose to call
Intend To Orphan. While we have an established process for making minimal,
fine-grained changes to a package, it does not cover broader
improvements such as migrating to Salsa, updating the Standards-Version,
or adjusting the debhelper compatibility level. However, some packages
could benefit from more extensive changes, and this procedure aims to
provide a structured way to implement them. Unlike the well-established
Package Salvage procedure[1] which requires an active Uploader, the goal
here is to allow collaborative work on a package on Salsa, even if no
active uploader expresses interest in maintaining it.
--> Maintainer set to Debian QA Group <[email protected]>
If you do not agree to large-scale changes to this package, including
maintaining it on Salsa, feel free to close this bug or tag it as
'wontfix' to inform others. There is no obligation to continue reading
if your stance is clear, and that decision will, of course, be
respected.
Otherwise, I will follow the well-established timing of the ITS
procedure, waiting 21 days before performing a QA Upload to delayed=10.
This procedure has not yet reached consensus--I am simply exploring
whether it could be accepted. It was disussed at DebConf25 but some
consensus is pending. Please keep in mind that the goal of this process
is to help ensure that packages remain up to date and well maintained.
If you have suggestions for improving it, your feedback is most welcome.
I'm interested in orphaning the package lx-gdb. It meets the following
criteria:
- Bugs filed against the package do not have answers from the
maintainer. (Admittedly bug #1119477 is very new so I intend
to extend the waiting period from 21 to 51 days)
- There are QA issues with the package.
- Not on Salsa but it could profit from team maintenance
- No maintainer upload in the last 11 years
- Standards-Version < 4
I have set up a repository within Debian/[2]. This team functions
similarly to the former collab-maint on Alioth, allowing any Debian
Developer to make team uploads[3]. I understand that some maintainers
may prefer not to transition to collaborative maintenance, and I want to
emphasize that this is not intended as a hostile action. My goal is to
make the transition to using a Git repository on Salsa smoother and more
convenient for you.
This package was highlighted in the Bug of the Day[4] initiative, which
aims to introduce newcomers to manageable tasks and guide them through
the workflow to solve them. The focus of this initiative is on migrating
packages to Salsa, as it's a great way to help newcomers become familiar
with a consistent Git-based workflow.
Kind regards
Andreas.
[1]
https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#package-salvaging
[2] https://salsa.debian.org/debian/lx-gdb
[3]
https://wiki.debian.org/Salsa/Doc#Collaborative_Maintenance:_.22Debian.22_group
[4] https://salsa.debian.org/qa/tiny_qa_tools/-/wikis/Tiny-QA-tasks
-- System Information:
Debian Release: forky/sid
APT prefers testing
APT policy: (501, 'testing'), (50, 'buildd-unstable'), (50, 'unstable'), (5,
'experimental'), (1, 'buildd-experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.38+deb13-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE:de
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: lx-gdb
Source-Version: 1.03-16.1
Done: Andreas Tille <[email protected]>
We believe that the bug you reported is fixed in the latest version of
lx-gdb, 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.
Andreas Tille <[email protected]> (supplier of updated lx-gdb 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, 26 Dec 2025 14:22:53 +0100
Source: lx-gdb
Architecture: source
Version: 1.03-16.1
Distribution: unstable
Urgency: medium
Maintainer: Mark W. Eichin <[email protected]>
Changed-By: Andreas Tille <[email protected]>
Closes: 1119477 1120034
Changes:
lx-gdb (1.03-16.1) unstable; urgency=medium
.
* Non-maintainer upload.
Closes: #1120034
* Set Homepage to packages.debian.org since there seems no other
place with this version of the code in the internet any more
* Maintain package in Debian team on Salsa
* d/watch: Fake watch file
* d/copyright: DEP5
* debhelper-compat 13 (routine-update)
* Remove trailing whitespace in debian/changelog (routine-update)
* Trim trailing whitespace.
* d/rules: Cleanup d/rules and add hardening options
Closes: #1119477
* Standards-Version: 4.7.3 (routine-update)
* Remove Priority field to comply with Debian Policy 4.7.3 (routine-
update)
Checksums-Sha1:
a9ba0163c930f4e53b663038200b4dd6d6258077 1830 lx-gdb_1.03-16.1.dsc
cbd05b6c01a273bab69f4a64e536de5919e23f97 5980 lx-gdb_1.03-16.1.debian.tar.xz
58b9cf72d0fa39d9b3fbe22daa8cda3dbf5d6ad2 5900 lx-gdb_1.03-16.1_amd64.buildinfo
Checksums-Sha256:
6da5d62c83beab34a992c5ab8b050a1ec9dbc15c3edf8a83cefb9f974c3d7d09 1830
lx-gdb_1.03-16.1.dsc
0a4afcb7abc807defc7199b49aa36974193a521127e6d7312b251b379bb3155b 5980
lx-gdb_1.03-16.1.debian.tar.xz
c1d86a3b9c3b4876078d6d72f7b8b651119803689a3e800d49da11323b6469df 5900
lx-gdb_1.03-16.1_amd64.buildinfo
Files:
45fcd076768d4d8345cbb31be9a24f59 1830 otherosfs optional lx-gdb_1.03-16.1.dsc
6387a46452e68e51fb2a4d7119390c45 5980 otherosfs optional
lx-gdb_1.03-16.1.debian.tar.xz
c7dcb8296b7991242b21148c3b26fc7a 5900 otherosfs optional
lx-gdb_1.03-16.1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmlOjRIRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtEmAxAAmt1ENVYDlsmFhkWclBJMcU4ta/ynhd20
SYOSZSnDAw+bEFHShnU5bWROjbIaZJwSIY8Wd7Cp0ogpjAIE1wYeZLdjiSm6yKWk
hmPFpYovazh6T6jdi8xA3cgX/jml84L8I3lyNvmw8MWMi2sA9ZUz8RIv2OzHRSwF
1jHrKdjlqduufy3oCPZRNOGI2FKaSW8gIoHIe2q7zCIHbPCr4S5o0BqCLxdBMIug
KzQLU6/mMCJFDWjet584NETtZ1aRuIm6XdVftKIHE8py/71UVOzdbJOFsb1C7TAV
4huOMprhHC5v+21cNC5n1Pui5qLTXm9mNflylOdC4CxNm/zMXvlBH6hgysLPubBF
pfIy+Z4b09/dNP4krJeKCu4mEwFgzDsBGz+wbe+f9gTaJDeGVO1Tn/ypKwT+t6Of
LUQAz7T7R2yDDMgMbK47Q/N90fPfu64STe7OVXBiEt83OQcSknZxFjgN5QTb+oBQ
UuUQNZ+ZEjdAI34Rh5S4CJ4hL/yH3BP0POJ1U7JjA62hgJiKjtDY5J1ohk6hUiMt
caDfXdfbef7FU3a6gmhbo9oDBpDH/MmqCZfL0x1a0gdeh+VE9dfAneoo8N/dxLhG
K0CqE0GEqd1h7OenJt0CM+g6O3a5mj4psAUm9T05xN7AHoZCFZObFz2HAas9L+Rg
WRPqJfYaIi8=
=kwZk
-----END PGP SIGNATURE-----
pgp5cF50nYsxz.pgp
Description: PGP signature
--- End Message ---
