Bug 2241148
Summary: | rxvt-unicode does not show non-ascii charactrers correctly anymore and one cannot enter them. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Mike FABIAN <mfabian> |
Component: | rxvt-unicode | Assignee: | David Cantrell <dcantrell> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | 39 | CC: | amurdaca, andreas.bierfert, dbrendel, dcantrell, mfabian |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2023-10-06 06:25:54 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Mike FABIAN
2023-09-28 09:06:52 UTC
If I do this change to the rxvt-unicode.spec file: ``` $ git diff diff --git a/rxvt-unicode.spec b/rxvt-unicode.spec index 2222a32..81fd1e7 100644 --- a/rxvt-unicode.spec +++ b/rxvt-unicode.spec @@ -87,7 +87,7 @@ ln -s %{_datadir}/libev-source libev --enable-rxvt-scroll \ --enable-next-scroll \ --enable-xterm-scroll \ - --enable-perl \ + --disable-perl \ --enable-mousewheel \ --enable-xim \ --with-codesets=all \ ``` and then try to build with `fedpkg --release f39 mockbuild --no-cleanup-after` the build doesn’t finish because the file list wants to pack some files which are only generated on a build with perl: RPM build errors: File not found: /builddir/build/BUILDROOT/rxvt-unicode-9.31-5.fc39.x86_64/usr/share/man/man1/urxvt-background.1* But the binary /var/lib/mock/fedora-39-x86_64/root/builddir/build/BUILD/rxvt-unicode-9.31/src/rxvt has already been built and this binary works, it can display non-ascii characters jsut fine. So the upgrade to perl 5.38 seems to ahve broken something. That's a duplicate of #2240458. Upgrading to perl-5.38.0-501 fixes this issue. *** This bug has been marked as a duplicate of bug 2240458 *** |