From: Maxime Devos <maximedevos@telenet.be>
To: Jai Vetrivelan <jaivetrivelan@gmail.com>, 54252@debbugs.gnu.org
Subject: [bug#54252] [PATCH] gnu: lemonbar: Update to 1.4.
Date: Fri, 11 Mar 2022 13:32:33 +0100 [thread overview]
Message-ID: <470cfa86f37cfe82073d99af72276e25e45063e7.camel@telenet.be> (raw)
In-Reply-To: <b5e0e1fe2501f180b0b5fa825ded9c777fa7fc31.camel@telenet.be>
[-- Attachment #1: Type: text/plain, Size: 887 bytes --]
Maxime Devos schreef op za 05-03-2022 om 10:59 [+0100]:
> Jai Vetrivelan schreef op za 05-03-2022 om 11:35 [+0530]:
> > + (package
> > + (name "lemonbar")
> > + (version "1.4")
> > + (source (origin
> > + (method git-fetch)
> > + (uri (git-reference
> > + (url "https://github.com/LemonBoy/bar")
> > + (commit (string-append "v" version))))
> > + (file-name (git-file-name name version))
>
> At least in the 'master' branch (and presumably also in v1.4), there
> are a few bugs. At line 789, the return value of 'malloc' is not
> checked, potentially causing a null-pointer dereference (and hence, a
> segfault) at line 790 (in lemonbar.c).
Now reported upstream at <https://github.com/LemonBoy/bar/issues/240>.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-03-11 12:33 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 [this message]
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
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=470cfa86f37cfe82073d99af72276e25e45063e7.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=54252@debbugs.gnu.org \
--cc=jaivetrivelan@gmail.com \
/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).