From: Andreas Enge <andreas@enge.fr>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: gstreamer 2.22, webkitgtk 2.40.0, qt 5.15.8 and ffmpeg 6 on staging
Date: Wed, 29 Mar 2023 11:53:22 +0200 [thread overview]
Message-ID: <ZCQKkiMV9wLWpHGu@jurong> (raw)
In-Reply-To: <ZCQGXKQRr55Kzdyi@jurong>
Am Wed, Mar 29, 2023 at 11:35:24AM +0200 schrieb Andreas Enge:
> FAIL! : KUsAsciiTextCodecTest::testBrokenBuiltinEncoding() Compared values are not the same
> Actual (failConverterState.invalidChars): 1
> Expected (0) : 0
> Loc: [/tmp/guix-build-kcodecs-5.98.0.drv-0/kcodecs-5.98.0/autotests/kusasciitextcodectest.cpp(56)]
> 86% tests passed, 1 tests failed out of 7
Looking at the file, it is a workaround for this Qt bug:
https://bugreports.qt.io/browse/QTBUG-83081
which was fixed in 5.17.0.
The file was removed in commit
commit 2e7dc813c2b4672f34d135755e928c52c15a1c3a
Author: Volker Krause <vkrause@kde.org>
Date: Sun Feb 19 20:15:29 2023 +0100
Remove QTextCodec leftovers
This is all unused internal API now.
of kcodecs, together with lots of other changes (wc shows 944 lines).
It is not part of the latest kcodecs release 5.104.0, made after the commit.
I do not know whether it would be safe to just disable the test for the
time being.
Andreas
next prev parent reply other threads:[~2023-03-29 9:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 3:10 gstreamer 2.22, webkitgtk 2.40.0, qt 5.15.8 and ffmpeg 6 on staging Maxim Cournoyer
2023-03-29 9:17 ` Andreas Enge
2023-03-29 12:32 ` Maxim Cournoyer
2023-03-29 12:58 ` Andreas Enge
2023-03-29 9:35 ` Andreas Enge
2023-03-29 9:39 ` Andreas Enge
2023-03-29 9:53 ` Andreas Enge [this message]
2023-03-29 9:58 ` Andreas Enge
2023-04-03 11:45 ` Andreas Enge
2023-04-07 21:24 ` Maxim Cournoyer
2023-04-08 9:37 ` Andreas Enge
2023-04-08 10:22 ` Josselin Poiret
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZCQKkiMV9wLWpHGu@jurong \
--to=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=maxim.cournoyer@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).