Your message dated Thu, 12 Nov 2026 14:16:20 +0800
with message-id <[email protected]>
and subject line Re: Bug#1147732: RFS: neofetch/7.1.0-3 [ITP] -- Shows Linux
System Information with Distribution Logo
has caused the Debian Bug report #1147732,
regarding RFS: neofetch/7.1.0-3 [ITP] -- Shows Linux System Information with
Distribution Logo
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.)
--
1147732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1147732
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "neofetch":
* Package name : neofetch
Version : 7.1.0-3
Upstream contact : Dylan Araps <[email protected]>
* URL : https://github.com/dylanaraps/neofetch
* License : Expat
* Vcs : https://salsa.debian.org/debian/neofetch
Section : utils
The source builds the following binary packages:
neofetch - Shows Linux System Information with Distribution Logo
To access further information about this package, please visit the
following URL:
https://mentors.debian.net/package/neofetch/
Alternatively, you can download the package with 'dget' using this
command:
dget -x
https://mentors.debian.net/debian/pool/main/n/neofetch/neofetch_7.1.0-3.dsc
Changes since the last upload:
neofetch (7.1.0-3) unstable; urgency=medium
.
* Reintroduce package (Closes: #1147637)
* Update Standards-Version to 4.7.4.1
* Switch to debhelper-compat level 13
* Update Maintainer to new maintainer
Regards,
--- End Message ---
--- Begin Message ---
On Sun, 2026-10-18 at 02:24 -0300, Joaquín Daniel wrote:
> Hi Simon,
>
> Here is the "really good reason" you asked for to re-introduce neofetch.
Your email appears to me to be based on content generated by an LLM,
which is not a good start.
> While it is true that fastfetch is the modern, actively maintained
> alternative, it does not cover the exact use case that a significant portion
> of our user base relies on. My argument for re-introduction is based on three
> pillars:
>
> 1. The "Legacy Migration" Factor:
> Many users migrating from older releases (like Debian 11 or Ubuntu 22.04) are
> accustomed to `neofetch`. More importantly, there are thousands of legacy
> scripts, dotfiles, and tutorials in the wild that explicitly call `neofetch`.
> Forcing them to switch to `fastfetch` breaks their workflows. Keeping
> neofetch allows for a seamless transition and backwards compatibility.
People having old scripts they don't want to update isn't an excuse to
keep an unmaintained, obsolete codebase in the archive. Either way,
neowofetch (hyfetch) is an active fork that can be aliased/symlinked to
neofetch, and this is in the Debian archive.
> 2. The "Emergency/Low-Level" Diagnostic Tool:
> Neofetch is a pure Bash script. Unlike compiled binaries (which can fail if a
> shared library is broken or if the graphical environment fails to load), a
> Bash script relies on basic system commands. If a user's system breaks, the
> network manager fails, or they lose their graphical interface, `neofetch` is
> a lifeline to quickly check kernel version, DE/WM, and hardware state without
> needing a browser or complex tools. It is a reliable, universal diagnostic
> tool.
neowofetch / hyfetch has the same benefits, being a fork of neofetch.
fastfetch only depends on a single library (yyjson).
> 3. My Commitment as a Maintainer:
> I am not asking Debian to adopt an orphaned package. I am taking full
> responsibility for it. As proof of my active maintenance, I am already
> building and maintaining this package successfully for the Fedora ecosystem
> (including Fedora 43, 44, and Rawhide) via COPR:
> https://copr.fedorainfracloud.org/coprs/daniopenhat/neofetch/
This does not show anything. It is an external rpm repo that has two
versions uploaded three months apart. The actual neofetch package in
Fedora is still orphaned.
> I am fully prepared to handle any downstream patches, fix compatibility
> issues, and ensure it meets Debian Quality Assurance standards, without
> adding technical debt to the archive.
It is unlikely that a Debian Developer will want to reintroduce this
package into the archive. If you still want to do this, consider hosting
an external deb repository.
> The community still wants it, and I am ready to do the work. I kindly ask you
> to reconsider this re-introduction.
--
Maytham
signature.asc
Description: This is a digitally signed message part
--- End Message ---