From: realcharmer <realcharmer@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] conky: update to 1.19.0
Date: Mon, 03 Apr 2023 17:04:38 +0200 [thread overview]
Message-ID: <20230403150438.frGMyHyesEwosq13KWFwCuwGd3QLS8RJE4qbtYDem38@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42879@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 405 bytes --]
New comment by realcharmer on void-packages repository
https://github.com/void-linux/void-packages/pull/42879#issuecomment-1494496199
Comment:
There is a new release `1.19.0` for conky, so I've updated the PR and commit. It turns out there are more test failures on 32bit systems. See more at https://github.com/brndnmtthws/conky/issues/1485.
Waiting for upstream fixes and a subsequent new release.
next prev parent reply other threads:[~2023-04-03 15:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 14:17 [PR PATCH] conky: update to 1.18.3 realcharmer
2023-03-20 15:47 ` realcharmer
2023-03-20 15:59 ` realcharmer
2023-03-20 16:00 ` realcharmer
2023-03-28 8:27 ` realcharmer
2023-04-03 14:37 ` [PR PATCH] [Updated] [WIP] " realcharmer
2023-04-03 15:04 ` [WIP] conky: update to 1.19.0 realcharmer
2023-04-03 15:04 ` realcharmer [this message]
2023-04-14 9:03 ` ncmprhnsbl
2023-04-25 7:41 ` realcharmer
2023-04-25 7:42 ` realcharmer
2023-04-25 7:46 ` [PR PATCH] [Updated] " realcharmer
2023-04-25 22:48 ` [WIP] conky: update to 1.19.1 ncmprhnsbl
2023-04-25 22:49 ` ncmprhnsbl
2023-04-25 22:49 ` ncmprhnsbl
2023-04-30 6:10 ` ncmprhnsbl
2023-05-02 7:16 ` [PR PATCH] [Updated] " realcharmer
2023-05-02 7:34 ` realcharmer
2023-05-02 7:44 ` realcharmer
2023-05-30 14:04 ` realcharmer
2023-05-30 14:04 ` [PR PATCH] [Closed]: " realcharmer
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230403150438.frGMyHyesEwosq13KWFwCuwGd3QLS8RJE4qbtYDem38@z \
--to=realcharmer@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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.
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 NNTP newsgroup(s).