Your message dated Thu, 16 Oct 2025 16:34:07 +0000
with message-id <[email protected]>
and subject line Bug#1115071: fixed in mbw 2.0-1
has caused the Debian Bug report #1115071,
regarding mbw: Intend to Orphan: mbw
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.)
--
1115071: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1115071
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: mbw
Version: 1.2.2-1.2
Severity: important
X-Debbugs-Cc: [email protected], Emmanuel QUEMENER
<[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 mbw. It meets the following
criteria:
- NMUs (more than one NMU in a row).
- Bugs filed against the package do not have answers from the
maintainer.
- Upstream has released several versions, but despite there being
a bug entry asking for it, it has not been packaged.
- There are QA issues with the package.
- Not on Salsa but it could profit from team maintenance
- No maintainer upload in the last 13 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/mbw
[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 unstable
APT policy: (500, 'unstable'), (500, 'testing'), (50, 'buildd-unstable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.3.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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
--- End Message ---
--- Begin Message ---
Source: mbw
Source-Version: 2.0-1
Done: Andreas Tille <[email protected]>
We believe that the bug you reported is fixed in the latest version of
mbw, 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 mbw 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: Mon, 06 Oct 2025 17:47:54 +0200
Source: mbw
Architecture: source
Version: 2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <[email protected]>
Changed-By: Andreas Tille <[email protected]>
Closes: 1111382 1115071
Changes:
mbw (2.0-1) unstable; urgency=medium
.
* QA upload.
Closes: #1115071
* New upstream version
Closes: #1111382
* Fix Homepage
* Add watch file
* Standards-Version: 4.7.2 (routine-update)
* debhelper-compat 13 (routine-update)
* Remove old boilerplate from debian/rules (routine-update)
* Remove trailing whitespace in debian/control (routine-update)
* Remove trailing whitespace in debian/rules (routine-update)
* No tab in license text (routine-update)
* Trim trailing whitespace.
* d/rules: Short dh
* d/copyright:
- DEP5
- Review
Checksums-Sha1:
0d802211aad41511c41ac63ddede60ecc0d3aaca 1775 mbw_2.0-1.dsc
ce4003300b25622cebf13efef33d727b6dfeb458 17166 mbw_2.0.orig.tar.gz
4cb436d6c8359864f3a59da590a82b4542673075 2180 mbw_2.0-1.debian.tar.xz
d9cb6ffb485ec73b45a19478bff71d162a50d16f 5651 mbw_2.0-1_amd64.buildinfo
Checksums-Sha256:
7eb2ff97206d6af0536229a5ebe180977b78e18d68010fd0fa3654e8e429aa77 1775
mbw_2.0-1.dsc
557f670e13ff663086fe239e4184d8ca6154b004bd5fde2b0a748e5aa543c87f 17166
mbw_2.0.orig.tar.gz
e6056f401b1457ae506f3c1f904ba3314b7b85162a1edb1a6da1fde5d34e54e7 2180
mbw_2.0-1.debian.tar.xz
61257720482d17e885419ba3d21d7cff5abe94108ebb0222c7880b84fa50a3c9 5651
mbw_2.0-1_amd64.buildinfo
Files:
b87107c7e43f2518d9abbdb9482b4ec3 1775 utils optional mbw_2.0-1.dsc
46ca7401ae650734965e7a25453557d4 17166 utils optional mbw_2.0.orig.tar.gz
a87e15330208346a20a20bb8e331f68c 2180 utils optional mbw_2.0-1.debian.tar.xz
a29b8c847f5a4e13705a7370c6816713 5651 utils optional mbw_2.0-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmjj52ERHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtE6Ww/+N8J2BdYdtt0WQCYgA9RFim0BZmVwO5nR
OQ8L4sW2pLXSSjtxlQx82FeleWrPf1YRJO0+aov1keLN5dry/MoEjLWAkaevB0oH
kT+ASBOrlMNPikWQqekyFeae4vGlUrLRThgcwvBxPENQQFhmlccakz+3zsVxgyWe
1HXf4wD5/uobWYZ+8j50cEzQCGEgxZSM5vuNzGoUfC7tHSEUlNKXXmfWPKoybSlx
gsO6y54rq4xvkQDibiJrhrxLraH5M4QAWa9QuvDWeOzny3/9BYKZoMXNDBjj11ZG
/u5PdpKnO+6sgxpJ1Mr1DUbfvdshjzJCP+f87FOiInUv+AT9QHtQoaiDl0mvalsb
NTHK1Wqp3psaJac7VfctDwCkpaFcwLbf6dAMLeJg3REuuH+JBHQ4vJmyCyiT4UYt
gGI+ueyqeJIw5nkjuLDoevpmdoSqbJb5fbnamyLW0sl/Y3df3Baj5+AThJFqGArq
Rb755KvZ4JCGgKB1px0DjuRFHjr7M1MeX0U+gwilDbLA6C59PWO/jplOZ8S9joyl
9hF5ykKv0UW6YS8DMdDze1pjfgIuMraN1q90I1nuHKl3HIosYOsMUWez36q3XfEv
nPemEEzuC3FwoejUCgOkb6fyO232nlE4dobkcAKSiEx7gVuywpMGZqyhqtIpNFT2
hKdAMpTA2t4=
=I2gA
-----END PGP SIGNATURE-----
pgprGTQHKtNlk.pgp
Description: PGP signature
--- End Message ---
