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
