Your message dated Sat, 10 Jan 2026 21:51:05 +0000
with message-id <[email protected]>
and subject line Bug#1120624: fixed in sma 1.4-3.2
has caused the Debian Bug report #1120624,
regarding Intend to Orphan: sma
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.)
--
1120624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1120624
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: sma
Version: 1.4-3.1
Severity: important
X-Debbugs-Cc: [email protected], Andrew Pollock <[email protected]>,
Package Salvaging Team <[email protected]>
Hi Andrew,
I admit I'm not sure whether the ITS procedure is the best approach in
this case since as far as you know you are active - at least I've seen
uploads of slack in 2022. However, we have no better procedure when
trying to migrate some package to Salsa and so I choose this one. I'd
prefer to move the repository below moved to Debian/ team and be
maintained by you. If you agree with this and have no time I might
consider an NMU if you agree to this.
I would be interested in helping with sma, following the Package
Salvaging procedure outlined in the Developers Reference[1]. From what I
see, the package seems to meet the criteria for this process, and I'd
like to support keeping it maintained in Debian. As the Salvage process
suggests, here is a list of the criteria that I believe apply:
- NMU
- Bugs filed against the package do not have answers from the
maintainer.
- There are QA issues with the package.
I've set up a repository within the salvage-team space[2] to assist you
with this initial setup. If you decide not to accept the ITS, this
repository can easily be moved to another location, such as debian/, or
any place of your choosing. I hope this service helps make the
transition to using a Git repository on Salsa smoother and more
convenient for you.
END FIXME
This package was highlighted in the Bug of the Day[3] 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/salvage-team/sma
[3] 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: sma
Source-Version: 1.4-3.2
Done: Andreas Tille <[email protected]>
We believe that the bug you reported is fixed in the latest version of
sma, 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 sma 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: Wed, 31 Dec 2025 21:58:53 +0100
Source: sma
Architecture: source
Version: 1.4-3.2
Distribution: unstable
Urgency: medium
Maintainer: Andrew Pollock <[email protected]>
Changed-By: Andreas Tille <[email protected]>
Closes: 1119564 1120624
Changes:
sma (1.4-3.2) unstable; urgency=medium
.
* Non-maintainer upload.
Closes: #1120624
* Remove d/rules.old since the package is now in Git
* Add fake watch file since the download page seems to be broken
* d/rules:
- Remove invalid boilerplate
- Add hardening options
* Standards-Version: 4.7.2 (routine-update)
* debhelper-compat 13 (routine-update)
* Remove trailing whitespace in debian/control (routine-update)
* Trim trailing whitespace.
* d/copyright:
- DEP5
- Review
* Make sure build flags will be propagated
Closes: #1119564
Checksums-Sha1:
2ce744244d90d1b8dea7a398849bfa746dfa0588 1779 sma_1.4-3.2.dsc
5d1aa456957fa8fc5ad6ccf6d7fb07d72b6e07d4 4064 sma_1.4-3.2.debian.tar.xz
0f5e24f70c8f7653178b8fb7f3a9c281c7d11288 5843 sma_1.4-3.2_amd64.buildinfo
Checksums-Sha256:
0aa497d3d76b10e5ecee58abf469374695e90c3b1cc2ff69ecab08045079b7bb 1779
sma_1.4-3.2.dsc
a96f118c685570e1b6795182634dc994be4fca86d9ebe9f660f41ac1ee10a938 4064
sma_1.4-3.2.debian.tar.xz
366ffd5988c255d1df60e8c38135c0316e4818278b615a751356192e50b19c05 5843
sma_1.4-3.2_amd64.buildinfo
Files:
f0632ae88a7d04ae774d7a855d66114b 1779 mail optional sma_1.4-3.2.dsc
28d2b29dd6c73661007d23117b114645 4064 mail optional sma_1.4-3.2.debian.tar.xz
d164ef1ddd95930706552fb8541c6ca2 5843 mail optional sma_1.4-3.2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmlVj6sRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGVhw/8CNqwiFWUZiQRPgp6wyYjTzDN5kNl19nm
/bI9SissxsoyFxKFIIY5SsDuZNzP3HlBr4KVe6voQXI4xGH9nrjhfi9qoxetlDVm
ZzXZtbM85HSWzuGyOkeI97DzfwRoFhMoF9/uyNauWBFdzOOTQRTOMKCG9YaC+DMm
i1UvHdRv6yRSTgrLPBT50VJdWXiHYHojbT8KPLiqhPmnmiocXp6GQ/4ngmYM1V2z
EGGrzhZJXicehEzUazqvma7ky/0uwOH0I7hJUnMpOhWfOIcfeEglvoqEla7OjIVI
/zFabigEhHkSr6Fft6JRfCOdN6G8vTSsfKkw0kUqHiNP5uDN2CjbumB2N8ZKvDOd
nMJpjuK8Ov9aPO4YHwZeMq17hi2Ad4GSIZU62VM/pqx1xy2v4xveQ6/RdUWB4TKJ
/+DaUULL3Sanq3zq/pFCPbx+1XXZL3jedGTzwYXRdvphK8Zu8YlUJeVVJjqzJ33l
H6MDGm+d/1sZ8EqS43QO/ZMyDiDiWB9r56SpfkWTROlQx6xzLQ0BWpzdYbHArTmd
Qk2QYi+erfJlAzO+bbrGBmSOg53h0/AsFmTr3InzM33GJ6Sv0sSzDXKX575oMu4i
90rauYvyKlEZPmmniBKTk4bIFO0ChBnqtX/uB80NI4GrQ1ECJRl6oJCqB904+fz2
wKBEj42avP4=
=PLBJ
-----END PGP SIGNATURE-----
pgp0uejTA4Nc8.pgp
Description: PGP signature
--- End Message ---
