Re: Bug in glib update 2.74.0 (part II)

[paper42 <paper42@users.noreply.github.com>]

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

New comment by paper42 on void-packages repository

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

Comment:
> I opened a issue here, as the problem was not reproduced, it was closed, so the problem was gimp

no, your issue was about all gtk programs not working, someone had a similar issue in this issue, figured out it's because of their custom gtk3 and even provided a link to a patch for you.

> I said on the gimp ticket, what a bug was on the glib, you said the problem was at gimp, that glib 2.74 had shown this bug in gimp, then you posted what problem was really glib and hid the posts on the gimp ticket because they were off-tropics.

You went to an unrelated issue about a gimp with glib 2.74 bug, posted your unrelated issue in the gnome repository which confused me because I thought it was about that issue. I am sorry about that, I shouln't have blindly trusted that you won't post random links, sorry about that. When I realised this discussion was irrelevant, I marked it off topic.


> I also opened glib's gitlab ticket, was closed and had poorly answered answers

If you are talking about the one about chromium not starting (probavly because of your custom gtk3), I found the answer understandable.
 
> If there really is glib testsuite, it does not work, as they would easily detect errors before, the problem with gimp would not exist.

I think you don't understand how tests work. They can not catch all issues.

> If my needs, they require specific things, glib 2.74 problems cannot be reproduced, how would this help Void?

You wouldn't spam irrelevant things and you would probably fix your system if you just updated your gtk3 like I suggested multiple times. This is not going anywhere, so let's lock this discussion.