From: Skyler Ferris via Guix-patches via <guix-patches@gnu.org>
To: "Wiktor Żelazny" <wz@freeshell.de>, 69251@debbugs.gnu.org
Cc: Ricardo Wurmus <rekado@elephly.net>
Subject: [bug#69251] [PATCH] gnu: Add r-abbreviate.
Date: Sun, 18 Feb 2024 23:06:44 +0000 [thread overview]
Message-ID: <ae1c630c-0be8-40a2-b71f-c74846077f46@protonmail.com> (raw)
In-Reply-To: <ce6d33884c81110d3fe99ece4d3d32c443248875.1708281031.git.wz@freeshell.de>
Each section includes a checklist based on (and expands upon) the items
listed in the manual (22.7 "Submitting Patches"). Each checklist item
may have one of the following statuses:
C: Commitable. This item looks as expected for a final commit.
CC: Commitable with Context. Like commitable, but some notes have been
added providing context about anything notable or unusual. These notes
are provided for transparency and should not be interpreted as meaning
that I object to the patch.
MR: Minor Repair. There is something about the patch which I think
should ideally be changed, but I do not think that the patch should be
refused on this basis alone.
A: Attention. Something in the patch needs attention from the author,
the committer, or both. Resolving the matter may or may not require a
change to the patch.
XX: This item is not relevant to the patch.
Blank: I did not review this aspect of the patch.
[C ] Applies cleanly (commit fdbf4192f5eaa7fdb5e6e2e98ada0726c8104824)
[C ] Commit message looks correct & complete
[CC] Cryptographic hash
[A ] Project is maintained
[C ] Synopsis & Description
[C ] Package license matches source license
[C ] No compiler warnings (guix project, not package build)
[CC] `guix lint` output
[C ] `guix style` output
[C ] Package builds (my host is an x86_64 Xen guest)
[ ] Builds for other architectures
[C ] No bundled software
[CC] Works in container with minimal inputs
[C ] `guix size` output
[XX] Dependent packages (`guix refresh --list-dependent PACKAGE`)
[C ] `guix build --rounds=2`
[C ] Gender-neutral wording
[C ] One set of related changes
[CC] Simulated guix pull
# Cryptographic Hash
I was not able to locate a cryptographic hash for this package.
# Project is Maintained
All of the commits are from the end of 2021 and the version remains at
"0.1". However, the package is doing something relatively simple and
there are no open issues on the GitHub page (to be fair, there is only
one closed issue and it was handled ~2 months after the project was
uploaded).
There were about 1000 downloads within the past month at time of writing
(https://cranlogs.r-pkg.org/badges/last-month/abbreviate), implying that
some number of people are using the package. Combined with the lack of
issue reports, this gives some confidence that the lack of new commits
is "this doesn't need any changes" rather than "this is unmaintained".
# guix lint
There is a note that the source is not archived on Software Heritage or
Disarchive database. The 'archival' section in the "Invoking 'guix
lint'" chapter (9.8) indicates that the Software Heritage will pick up
the source at some point in the future.
# Works in container with minimal inputs
I used the following environment:
$ ./pre-inst-env guix shell -C r-abbreviate r
> library(abbreviate)
Then I entered some of the example commands from the README. The calls
were successful and produced reasonable-looking output.
# Simulated Guix Pull
I committed the diff locally and used `--disable-authentication`, which
I think is fine because the signature on the commit is unrelated to the
contents of the commit in this context.
next prev parent reply other threads:[~2024-02-18 23:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-18 18:31 [bug#69251] [PATCH] gnu: Add r-abbreviate Wiktor Żelazny
2024-02-18 23:05 ` Skyler Ferris via Guix-patches via
2024-02-18 23:06 ` Skyler Ferris via Guix-patches via [this message]
2024-02-19 12:57 ` bug#69251: " Ricardo Wurmus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ae1c630c-0be8-40a2-b71f-c74846077f46@protonmail.com \
--to=guix-patches@gnu.org \
--cc=69251@debbugs.gnu.org \
--cc=rekado@elephly.net \
--cc=skyvine@protonmail.com \
--cc=wz@freeshell.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).