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: Wed, 05 Oct 2022 23:50:27 +0200	[thread overview]
Message-ID: <20221005215027.3j0Qsb2KVS1--wTeczGlBqy7c4McPwdUDH32_J8P7Ok@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: 2593 bytes --]

New comment by bugcrazy on void-packages repository

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

Comment:
> > I will only use glib 2.74, when they release a glib version 2.74.1 or higher, which really fixes the problems
> 
> "the problems"? You refuse to test this with the official gtk package and none of your reports make sense. Which problems do you have that are not caused by your modifications?
> 
> > as there are no test tools on the glib if it had no bug in the gimp.
> 
> glib has a test suite, I am not sure what your point is here.
> 
> > Problems in other distros are similar.
> 
> Problems with which programs that we also have? Links? Can you reproduce the issues? If there are none that you are experiencing, we don't care.
> 
> > Already question of the thunar, would be a problem of stamp data/team, when copies android files to Void. Because user, it didn't open Issue in github, that's a matter of him.
> 
> I don't really understand the first sentence, but if there isn't an open issue, we will probably ignore it.
> 
> You are not trying to be helpful. You just decided that glib 2.74 is bad, you complain in 3 (1 unrelated) threads, ignore me when I ask you to test something and then continue with complaining. This is not Telegram, this is a bug tracker and you are expected to cooperate in order for us to figure out how to solve the issues if there are any.

I opened a issue here, as the problem was not reproduced, it was closed, so the problem was gimp, 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. I also opened glib's gitlab ticket, was closed and had poorly answered answers, I started accompanying gitlab glib tickets, has many problems related to glib 2.73, which has a 2.74 code and problems at 2.74, are simply closed and not fixed , they release a version with bugs and misplaced, the gimp is proof of this, because it is a brother project, they create patches later and is like this, just like Debian package full of patches.

If there really is glib testsuite, it does not work, as they would easily detect errors before, the problem with gimp would not exist.

The user who reported a problem with thunar knows how to create Issue here, because he didn't open it, I don't know.

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

  parent reply	other threads:[~2022-10-05 21:50 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 ` [ISSUE] [CLOSED] " biopsin
2022-09-29  8:56 ` 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
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 [this message]
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=20221005215027.3j0Qsb2KVS1--wTeczGlBqy7c4McPwdUDH32_J8P7Ok@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).