From: Maxime Devos <maximedevos@telenet.be>
To: Remco van 't Veer <remco@remworks.net>, 55891@debbugs.gnu.org
Subject: [bug#55891] [PATCH] gnu: Add iec16022
Date: Sun, 31 Jul 2022 01:48:58 +0200 [thread overview]
Message-ID: <3e39fece-f6b2-b3c1-da19-e1c78fee2112@telenet.be> (raw)
In-Reply-To: <87tu819v5v.fsf@remworks.net>
[-- Attachment #1.1.1: Type: text/plain, Size: 1388 bytes --]
On 01-07-2022 08:58, Remco van 't Veer wrote:
> Is there anything else I can do to keep this ticket moving? Bug about
> unchecked IO is reported and discussion about unchecked malloc has
> stalled.
You could search for an alternative solution that is acceptable to
upstream, or if upstream completely refuses bugfixes, add some patch to
the Guix package definition. Also, I have not yet seen a v2 for
resolving the other (non-upstream-code) issues I noted.
Another method would be to help out with reviewing and fixing things
(with other packages), this frees up time and is seen as a good act,
hence making other people more inclined to help out with any remaining
issues in your patches (including fixing issues such as those of the
kind I have mentioned before, but also actually applying the patch and
committing it).
You could also perform _all_ the checks in (guix)Submitting Patches
(e.g., the bundling check, actually building it for other systems as
well with QEMU, reproducibility check).
> Also note, this package is also being shipped by debian, archlinux,
> fedora, and others. Not that it matters but just to point out it's a
> widely spread utility.
I am not convinced by your implied method of persuasion by social
pressure / argumentum ad populum. If it doesn't matter, why use it as an
argument?
Greetings,
Maxime.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-07-30 23:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 15:04 [bug#55891] [PATCH] gnu: Add iec16022 Remco van 't Veer
2022-06-10 15:42 ` Maxime Devos
2022-06-10 17:36 ` Remco van 't Veer
2022-06-10 15:45 ` Maxime Devos
2022-06-10 17:37 ` Remco van 't Veer
2022-06-10 15:47 ` Maxime Devos
2022-06-10 17:38 ` Remco van 't Veer
2022-06-10 15:55 ` Maxime Devos
2022-06-10 17:39 ` Remco van 't Veer
2022-06-10 21:47 ` Maxime Devos
2022-06-11 7:09 ` Remco van 't Veer
2022-06-25 14:53 ` Remco van 't Veer
2022-07-01 6:58 ` Remco van 't Veer
2022-07-30 23:48 ` Maxime Devos [this message]
2022-08-14 7:57 ` Remco van 't Veer
2022-06-10 17:35 ` [bug#55891] [PATCH v2] " Remco van 't Veer
2022-06-10 17:45 ` [bug#55891] [PATCH v3] " Remco van 't Veer
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=3e39fece-f6b2-b3c1-da19-e1c78fee2112@telenet.be \
--to=maximedevos@telenet.be \
--cc=55891@debbugs.gnu.org \
--cc=remco@remworks.net \
/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).