From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: Graphical Corruption on Chromium Apps with Mesa 19.0.5
Date: Sun, 02 Jun 2019 06:11:02 +0200 [thread overview]
Message-ID: <20190602041102.de1xz6FyrUmX0XMLQkEFtYiVTAeIF_EygCLxqoRueIg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11907@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 505 bytes --]
New comment by HadetTheUndying on void-packages repository
https://github.com/void-linux/void-packages/issues/11907#issuecomment-497997462
Comment:
> I really think Void should roll this package back asap... Fedora has patched this already somehow, someone should make a pull request.
The problem is that no one is sure if after bisecting and removing these two commits if new bugs were introduced yet. You can manually rebuild 19.0.4 if you do not have it in your cache, which is my suggestion,.
next prev parent reply other threads:[~2019-06-02 4:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11907@inbox.vuxu.org>
2019-05-30 15:30 ` voidlinux-github
2019-05-30 22:15 ` voidlinux-github
2019-06-01 12:10 ` voidlinux-github
2019-06-01 18:56 ` voidlinux-github
2019-06-01 19:20 ` voidlinux-github
2019-06-01 22:00 ` voidlinux-github
2019-06-02 0:23 ` voidlinux-github
2019-06-02 0:26 ` voidlinux-github
2019-06-02 0:29 ` voidlinux-github
2019-06-02 4:11 ` voidlinux-github [this message]
2019-06-02 15:32 ` voidlinux-github
2019-06-02 20:55 ` voidlinux-github
2019-06-03 0:21 ` voidlinux-github
2019-06-03 1:36 ` voidlinux-github
2019-06-03 1:42 ` voidlinux-github
2019-06-03 1:44 ` voidlinux-github
2019-06-04 9:05 ` voidlinux-github
2019-06-04 9:11 ` voidlinux-github
2019-06-04 11:30 ` voidlinux-github
2019-06-04 22:10 ` voidlinux-github
2019-06-04 23:02 ` voidlinux-github
2019-06-06 11:06 ` [ISSUE] [CLOSED] " voidlinux-github
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=20190602041102.de1xz6FyrUmX0XMLQkEFtYiVTAeIF_EygCLxqoRueIg@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).