From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: 54252@debbugs.gnu.org, Maxime Devos <maximedevos@telenet.be>,
Jai Vetrivelan <jaivetrivelan@gmail.com>
Subject: [bug#54252] [PATCH] gnu: lemonbar: Update to 1.4.
Date: Fri, 11 Mar 2022 14:15:08 -0500 [thread overview]
Message-ID: <8735joti6b.fsf@gmail.com> (raw)
In-Reply-To: <87y21g3n6r.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Fri, 11 Mar 2022 09:31:24 +0100")
Hi Nicolas,
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Hello,
>
> Maxime Devos <maximedevos@telenet.be> writes:
>
>> Nicolas Goaziou schreef op vr 11-03-2022 om 01:47 [+0100]:
>>> Jai Vetrivelan <jaivetrivelan@gmail.com> writes:
>>>
>>> > From dedefb5d5f0389d1e6fb190c9d47a6f8ca398791 Mon Sep 17 00:00:00 2001
>>> > From: Jai Vetrivelan <jaivetrivelan@gmail.com>
>>> > Date: Sat, 5 Mar 2022 11:17:57 +0530
>>> > Subject: [PATCH] gnu: lemonbar: Update to 1.4.
>>>
>>> Applied. Thank you.
>>
>> I don't think the null pointer dereferences have been reported upstream
>> yet.
>
> It would probably be a nice thing to do, but I don't think we can
> request packagers to also take care of reporting bugs upstream (or
> fixing them!). It is a different task with a different required skill
> set.
I don't have the full context, but I'll chip in in case it is useful.
When problems in the packaging are discovered as part of our activities,
I think it is part of our duty to at least report them and
cross-reference them via a comment in the package source if possible.
The reason I find this important is that over time, upstream can fix the
problems reported, and we can get rid of substitutions and other
Guix-specific patches, which should help reduce maintenance burden.
I hope this makes sense,
Thank you!
Maxim
next prev parent reply other threads:[~2022-03-11 19:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-05 6:05 [bug#54252] [PATCH] gnu: lemonbar: Update to 1.4 Jai Vetrivelan
2022-03-05 9:59 ` Maxime Devos
[not found] ` <87h78c4knq.fsf@gmail.com>
2022-03-05 15:32 ` Maxime Devos
2022-03-11 12:32 ` Maxime Devos
2022-03-05 10:01 ` Maxime Devos
2022-03-11 0:47 ` bug#54252: " Nicolas Goaziou
2022-03-11 7:28 ` [bug#54252] " Maxime Devos
2022-03-11 8:31 ` Nicolas Goaziou
2022-03-11 19:15 ` Maxim Cournoyer [this message]
2022-03-11 22:09 ` Nicolas Goaziou
2022-03-11 22:30 ` Maxime Devos
2022-03-11 23:14 ` Nicolas Goaziou
2022-03-11 23:26 ` Maxime Devos
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=8735joti6b.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=54252@debbugs.gnu.org \
--cc=jaivetrivelan@gmail.com \
--cc=mail@nicolasgoaziou.fr \
--cc=maximedevos@telenet.be \
/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).