Github messages for voidlinux
 help / color / mirror / Atom feed
From: bugcrazy <bugcrazy@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Bug in glib update 2.74.0 (part II)
Date: Mon, 03 Oct 2022 22:56:40 +0200	[thread overview]
Message-ID: <20221003205640.zyCH_n-6vzKlCwOv8VRBccopP3ojTlem8BzTSQ8sso4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39523@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 526 bytes --]

New comment by bugcrazy on void-packages repository

https://github.com/void-linux/void-packages/issues/39523#issuecomment-1266038091

Comment:
> And if there are any bugs in a normal void setup, not a highly customized one, they should be reported and fixed. So far only the gimp text tool bug was reported and fixed.

There was another user who told me, who had problems with glib 2.74 in thunar with android-tools. There are problems with glib update in distro:

https://forum.endeavouros.com/t/timeshift-issue/10391/9

  parent reply	other threads:[~2022-10-03 20:56 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-29  8:14 [ISSUE] " biopsin
2022-09-29  8:56 ` biopsin
2022-09-29  8:56 ` [ISSUE] [CLOSED] " biopsin
2022-09-29 18:18 ` paper42
2022-09-29 18:19 ` paper42
2022-09-29 18:19 ` [ISSUE] [CLOSED] " paper42
2022-09-29 18:24 ` paper42
2022-10-01 22:51 ` bugcrazy
2022-10-01 23:38 ` paper42
2022-10-01 23:40 ` paper42
2022-10-03  1:21 ` bugcrazy
2022-10-03  7:16 ` paper42
2022-10-03  8:27 ` paper42
2022-10-03  9:08 ` q66
2022-10-03 19:55 ` bugcrazy
2022-10-03 20:23 ` paper42
2022-10-03 20:56 ` bugcrazy [this message]
2022-10-03 20:58 ` bugcrazy
2022-10-03 21:16 ` bugcrazy
2022-10-03 21:24 ` paper42
2022-10-03 21:28 ` paper42
2022-10-05  4:43 ` bugcrazy
2022-10-05  8:03 ` paper42
2022-10-05 21:50 ` bugcrazy
2022-10-05 22:42 ` paper42
2022-10-05 22:44 ` paper42

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=20221003205640.zyCH_n-6vzKlCwOv8VRBccopP3ojTlem8BzTSQ8sso4@z \
    --to=bugcrazy@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).