Your message dated Mon, 16 Mar 2026 14:49:29 +0000
with message-id <[email protected]>
and subject line Bug#1125294: fixed in gforth 0.7.3+dfsg-10
has caused the Debian Bug report #1125294,
regarding gforth: Should gforth be removed from unstable?
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.)
--
1125294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1125294
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: gforth
Version: 0.7.3+dfsg-9
Severity: serious
Justification: Grabbing attention of developers and users involved
X-Debbugs-Cc: [email protected], Peter Pentchev <[email protected]>, juno
adler <[email protected]>, "Ph. Marek"
<[email protected]>, Scott Mebust <[email protected]>, Anton Ertl
<[email protected]>, "T. Kurt Bond" <[email protected]>,
[email protected], "David N. Welton" <[email protected]>, Stéphane
Fillion <[email protected]>
Dear Peter and potential users of gforth,
I intentionally added all people who reported bugs against gforth since
this will reach potentially interested users. I want to make pretty
sure that my estimation of the status of gforth is correct and I'm not
missing an important point. If you think I'm wrong please decrease the
severity of this bug and set tag it `wontfix` if you disagree with the
removal. I explicitly would like to see gforth in Debian (used FORTH
myself 30 years ago and would be happy if there would be a chance to
serve Debian users properly)
I suggest removing gforth from Debian for the following reasons:
* It accumulated one RC-bug:
#1067376 gforth: FTBFS: make[1]: *** [Makefile:655: build-libcc-named]
Error 1
* Another bug report claims
#935487 gforth: Packaged gforth version is very old.
which makes me wonder whether our package is helpful for gforth users
* It is not part of trixie and is not a key package (no rdepends or
build-depends
* Admittedly there is some usage recorded per popcon
https://qa.debian.org/popcon-graph.php?packages=gforth&show_installed=on&show_vote=on&want_legend=on&want_ticks=on&from_date=&to_date=&hlght_date=&date_fmt=%25Y-%25m&beenhere=1
* The maintainer asked for adoption 2.5 years ago with no success
#1039051 RFA: gforth -- GNU Forth Language Environment
This bug serves as a pre-removal warning. Usually such warnings will be
reassigned to ftp.debian.org to actually request removal of the package
after one month. However, I'd like to give at least two months since it
would be a shame to see it go and I'd like to extent this discussion
period.
In case the package should be kept in unstable, please evaluate the
RC-bug listed above.
* If the bug no longer applies, please close it. If it is closed, check
whether the fixed version is correct and adjust if necessary.
* Is the bug really release-critical? If not, please downgrade.
* If the bug still applies, please send a status update at least once a year.
Once all of the mentioned RC bugs have been acted upon in one way or another,
please close this bug.
In case the package should be removed from unstable, you may reassign this
bug report:
Control: severity -1 normal
Control: retitle -1 RM: gforth -- RoM; rc-buggy
Control: reassign -1 ftp.debian.org
Control: affects -1 + src:gforth
Alternatively, you may wait two months and have it reassigned.
In case you disagree with the above, please add a wontfix tag to this bug.
Control: tags -1 + wontfix
Doing so will also prevent reassignment.
This package was highlighted in the Bug of the Day[1] 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://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: gforth
Source-Version: 0.7.3+dfsg-10
Done: Bernd Paysan <[email protected]>
We believe that the bug you reported is fixed in the latest version of
gforth, 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.
Bernd Paysan <[email protected]> (supplier of updated gforth 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, 16 Mar 2026 15:16:29 +0100
Source: gforth
Architecture: source
Version: 0.7.3+dfsg-10
Distribution: unstable
Urgency: medium
Maintainer: Bernd Paysan <[email protected]>
Changed-By: Bernd Paysan <[email protected]>
Closes: 1039051 1067376 1125294
Changes:
gforth (0.7.3+dfsg-10) unstable; urgency=medium
.
[ Bernd Paysan ]
* Add myself as Maintainer
Closes: #1039051
* Add patch for gcc-15
* Ignore failure on open-lib with libcc build stuff
Closes: #1067376, #1125294
.
[ Peter Pentchev ]
* Add a trivial git-buildpackage config file.
* Add two more Lintian overrides for the GForth plugins.
* Drop the version in the emacsen-common dependency.
* Declare compliance with Debian Policy 4.5.0 with no changes.
* Add the year 2020 to my debian/* copyright notice.
* Drop the adequate autopkgtest.
* Drop the Name and Contact upstream metadata fields.
* Only make commands conditional, not a whole target.
* Update to debhelper compat level 13: `dh_missing --fail-missing` is
now the default.
* Make the watch file options line more readable.
* Drop the "pasv" option for an HTTPS watchfile line.
* Add two watchfile lines for the snapshots directory.
.
[ Andreas Tille ]
* Maintain package in Debian team on Salsa
* Standards-Version: 4.7.3
Checksums-Sha1:
58c636690d64a9d1f504c7393af7c0e49a7a43cd 2087 gforth_0.7.3+dfsg-10.dsc
0ecbb91a4949f34ff65c510e3fd46aec437aad1a 44036
gforth_0.7.3+dfsg-10.debian.tar.xz
5a373935b4704aa43a09c66995c7ba0eb881f03e 6957
gforth_0.7.3+dfsg-10_amd64.buildinfo
Checksums-Sha256:
b8594920be427e7dc0b0e7a7fa4e32b45d9da2b902ce538bfb8b99683c8adfce 2087
gforth_0.7.3+dfsg-10.dsc
5cfca77e704bf30c8bb4240f8a6c0f0e825800709e4de9fe8a7936ec284a9523 44036
gforth_0.7.3+dfsg-10.debian.tar.xz
f91a13a1940318e7a2ee14004b2f17d12f0c90ae93b80059533cb637b3d0aa4e 6957
gforth_0.7.3+dfsg-10_amd64.buildinfo
Files:
529b5ddee726b6045bdb69743f37b97f 2087 interpreters optional
gforth_0.7.3+dfsg-10.dsc
214150904e611ee0eedf9832e17a1035 44036 interpreters optional
gforth_0.7.3+dfsg-10.debian.tar.xz
1a3d895490f1c8ca6fa8fe9030ac5a26 6957 interpreters optional
gforth_0.7.3+dfsg-10_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmm4FUMRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtGLOA//fVxTTK0VP7kQhg+krkLEs2EXl5EfU89v
28UvXznVQpi7PTrKKWowfezPrswgMvFUHGaPr/dkz40R5gMpiwkX6vva/r6+Frtf
uWgeAvRii39XT8MKSp/gNZzVdm7SyBsKsCVboQDXK6M9YyA1FhcdsJyatHMO9WTS
sdM+dfHkCpjUfQN6N1+HE/r5O+QIuoUXIr0ziRYGYO9yzvri47HrsyYD36dRqqL8
WO149gvem4nMTbpJxppHCumsEA1uXRm9rEFtjjghlDrf197eipO+O1mytJB9Nte6
84XJX+GpvULRlm4my0OQZ7Aa6exFgz4ycbTog1PNlZgXxg4l9XBaIk85yq/3LwCX
F6wPaiyc5NfL686KD6BZSGIgNaZd7sH5epn1DIJCCuEqNbU04sguzBGVZmZ4P+yk
Z3fqGTLf1VrpEJd/+k3aReHjQ/vlfAO0MM6ZcmgyHbeayvMhW4LUY1VnuvQdDCQU
stLS2TYs0aV7SqlyywTz/v40j0BcU2Xdync4rPWaQ+1GVYSystzpQvj2uPJKFHru
3WQffAMBKOdu4DKTYrw1nduXM6KETr4vzVEFwDQZDBlt3a5QhSdqhKWDarf5EGta
VE9j8t03c7aI/NR6rfEiMqn5873pznLuMkb7Lst2x1wbAqcrXKzZK6LvOFJ7h3d/
i+3PJuStPJo=
=8c5t
-----END PGP SIGNATURE-----
pgp10Fjkg_SJL.pgp
Description: PGP signature
--- End Message ---