From: paper42 <paper42@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 10:03:16 +0200 [thread overview]
Message-ID: <20221005080316.jrfI7JwYG0m20fLibX-ATqNEa1qpFas0CDLVPcpf74M@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: 1405 bytes --]
New comment by paper42 on void-packages repository
https://github.com/void-linux/void-packages/issues/39523#issuecomment-1268081658
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.
next prev parent reply other threads:[~2022-10-05 8:03 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 [this message]
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=20221005080316.jrfI7JwYG0m20fLibX-ATqNEa1qpFas0CDLVPcpf74M@z \
--to=paper42@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).