From: ram02z <ram02z@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: pango: update to 1.50.2
Date: Thu, 30 Dec 2021 22:20:51 +0100 [thread overview]
Message-ID: <20211230212051.ueJ2rDBQNHBpl8bsrDYSsKP8pvQrl4uG3nLsmwQxdGs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34422@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 503 bytes --]
New comment by ram02z on void-packages repository
https://github.com/void-linux/void-packages/pull/34422#issuecomment-1003184825
Comment:
> @ram02z can you please open an issue and share screenshots?
>
> I don't think this has been reported to sway upstream yet :/
Sorry, it was i3status-rs, not swaybar.
Seems to be this https://github.com/greshake/i3status-rust/issues/1367
> @ram02z Also, could you check if the update in #34725 fixes your problem?
Yeah, pango 1.50.3 fixes the bug.
prev parent reply other threads:[~2021-12-30 21:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 20:24 [PR PATCH] pango: update to 1.50.0 cinerea0
2021-12-08 1:07 ` [PR PATCH] [Updated] " cinerea0
2021-12-08 22:01 ` ericonr
2021-12-08 22:03 ` ericonr
2021-12-08 22:13 ` ericonr
2021-12-08 23:40 ` ericonr
2021-12-11 1:32 ` [PR PATCH] [Updated] " cinerea0
2021-12-11 2:25 ` [PR REVIEW] " ericonr
2021-12-12 0:12 ` [PR PATCH] [Updated] " cinerea0
2021-12-16 21:46 ` [PR PATCH] [Updated] pango: update to 1.50.1 cinerea0
2021-12-16 21:48 ` pango: update to 1.50.2 cinerea0
2021-12-16 22:31 ` cinerea0
2021-12-17 8:36 ` ericonr
2021-12-21 3:26 ` ericonr
2021-12-21 3:27 ` [PR PATCH] [Merged]: " ericonr
2021-12-30 12:11 ` ram02z
2021-12-30 16:26 ` ericonr
2021-12-30 17:12 ` cinerea0
2021-12-30 21:20 ` ram02z [this message]
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=20211230212051.ueJ2rDBQNHBpl8bsrDYSsKP8pvQrl4uG3nLsmwQxdGs@z \
--to=ram02z@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).