Your message dated Tue, 02 Dec 2025 17:48:45 +0000
with message-id <[email protected]>
and subject line Bug#1119716: fixed in blosxom 2.2.0-1
has caused the Debian Bug report #1119716,
regarding "ITS: blosxom"
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.)
--
1119716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1119716
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: blosxom
Version: 2.1.2-2.2
Severity: important
X-Debbugs-Cc: Rhonda D'Vine <[email protected]>, Axel Beckert
<[email protected]>, [email protected], Package Salvaging Team
<[email protected]>
Hi Rhonda,
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 Rhonda. 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 a new version
- There are QA issues with the package.
- Git repository mentioned in Vcs fields is not accessible
- Not on Salsa but it could profit from team maintenance
- No maintainer upload in the last 9 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/blosxom
[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)
Kernel taint flags: TAINT_WARN
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: blosxom
Source-Version: 2.2.0-1
Done: Emmanuel Arias <[email protected]>
We believe that the bug you reported is fixed in the latest version of
blosxom, 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.
Emmanuel Arias <[email protected]> (supplier of updated blosxom 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: Sun, 02 Nov 2025 11:07:51 -0300
Source: blosxom
Architecture: source
Version: 2.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Rhonda D'Vine <[email protected]>
Changed-By: Emmanuel Arias <[email protected]>
Closes: 1091770 1119716
Changes:
blosxom (2.2.0-1) unstable; urgency=medium
.
[ Andreas Tille ]
* Team upload.
* New upstream version
* Maintain package in Debian team
* Secure URI in Homepage
* d/watch: version=5
* d/copyright: DEP5
* Standards-Version: 4.7.2 (routine-update)
* debhelper-compat 13 (routine-update)
* Remove trailing whitespace in debian/control (routine-update)
* Build time test needs Build-Depends: libyaml-perl,
libtest-differences-perl,
libfile-dircompare-perl, libfile-remove-perl, libcgi-pm-perl
* Recommends: s/apache/apache2/
* Cleanup upstream source from ._* files via Files-Excluded
* Fix permissions of directories in /var/lib/blosxom
Closes: #1091770
.
[ Emmanuel Arias ]
* d/control: Add my self as uploaders (Closes: #1119716).
Checksums-Sha1:
67c4935a1a1166a8ecf96bc6d258c1d597998cba 2067 blosxom_2.2.0-1.dsc
a6cb18404d0e87b11608461a6cdee1818af68ca3 21132 blosxom_2.2.0.orig.tar.xz
e988b3ab2a72846b4d6e2b5be286de511f882095 12980 blosxom_2.2.0-1.debian.tar.xz
3f0b1b3f9ed799b78b8bba4a5f34088b682aadc0 5862 blosxom_2.2.0-1_amd64.buildinfo
Checksums-Sha256:
769b5aa3c90089f07aec28813435564676210417b7cb36c23fc4c0b5cf850504 2067
blosxom_2.2.0-1.dsc
3f5d44cb83970baa33084b8de23ef81aa97dd4b3736a8809ea9080aad9dc84d1 21132
blosxom_2.2.0.orig.tar.xz
e8b1e700f8c934baee6d09c5fca069ad627b008bb271817365090d974d5d58fb 12980
blosxom_2.2.0-1.debian.tar.xz
250e07e9bf9007c78217ed5fbfd5913f394fecac2b0f2327d7706df7ccfd3c66 5862
blosxom_2.2.0-1_amd64.buildinfo
Files:
c6d33896c442c2c0f0f142b62bcb0bfb 2067 web optional blosxom_2.2.0-1.dsc
87d4e8e9080bf15d4bb52272fbbd2974 21132 web optional blosxom_2.2.0.orig.tar.xz
19fcfebaf072ef42f08a7873ec3a95c9 12980 web optional
blosxom_2.2.0-1.debian.tar.xz
40e0b140495b1117445310df93f72bf4 5862 web optional
blosxom_2.2.0-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJGBAEBCgAwFiEEE3lnVbvHK7ir4q61+p3sXeEcY/EFAmkh7ewSHGVhbWFudUBk
ZWJpYW4ub3JnAAoJEPqd7F3hHGPxXNgP/i8GtwFmB3I8pxQToE6eT6HsjPWSRiTs
L3qtdopf8vG981ueoD7dEeuAd3NzQdj6h84o7rV0kfEkv2RNLLzDQPekudLfKVQf
UUpGchij9MWP8eD8hsFAKG+YvoRBHqKrplKlpl1nQM+rc6kEuaj2a0B9A18wkcet
hpQbXX6ES2FPMX0x8pSpEcoE7LBYFMR7tJwnHnV49ollaHHNkacLd4xbTp9u/IR0
KHR5+8iUOIWDNVMlGYucjO4Ms6e2mDmxVOv+2Zkb2KgDXbSkERB8k2kMvm0Giqy6
7NYoNG150aHCDrrm4vjqXx4d+mrtpyHO09e4UMnP1E4Snh1czN4+QuaG67z4pxx5
0A1KqwdGPGW0nR1ZGqu/KlARNu6z6mr0gQLrBKGXauzFgjKkjxpaCGW2yiZyTlwQ
qniT1NRQF7fwSvwYF/PBTt2jKevzzKgYbcoWm7RiCt8fjEOl0i0zxq2onei9logM
ZC0HJ7RHzhY+tbMRzlyHwkJGrFhyqsWNdckgI/Qi6cub64+72CzwUa/wiHzci/Nd
lr+n3O9mMerZtyaSqCOMIB8DvgHv1LRVOtyaVUNv+t6kzGLdgp9Zyrr+U0eGrlGQ
2CKOZhemkONOlbt+uP8vshHgcJb8IPQo4bBGm32MwUhVXoog5DyAqPa5nMwUYNPD
ktxYXRBGOB6W
=BHb4
-----END PGP SIGNATURE-----
pgp0eETB4mAke.pgp
Description: PGP signature
--- End Message ---
