https://bugzilla.redhat.com/show_bug.cgi?id=2378003
Bug ID: 2378003
Summary: python-polib: Stop using deprecated
%py3_build/%py3_install macros
Product: Fedora
Version: rawhide
Status: NEW
Component: python-polib
Assignee: petersen(a)redhat.com
Reporter: mhroncok(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: dchen(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, reallylongword(a)gmail.com,
sundeep_anand(a)yahoo.com
Blocks: 2376118
Target Milestone: ---
Classification: Fedora
Dear package maintainer,
this bugzilla is automated becasue the number of impacted packages it too high
to go trough manually.
It appears that your package uses the deprecated %py3_build and/or %py3_install
macro.
See https://fedoraproject.org/wiki/Changes/DeprecateSetuppyMacros for why the
macros are deprecated.
%py3_install expands to python setup.py install. This has been a deprecated
command for 5 years and will likely stop working in Fedora 45.
Please migrate to %pyproject_buildrequires + %pyproject_wheel +
%pyproject_install macros instead.
See
https://fedoraproject.org/wiki/Changes/DeprecateSetuppyMacros#Migrating_to_…
for migration guide.
See https://github.com/hroncok/pyprojectize/ for a tool that can help you
automate the migration.
Thank you. Let me know if you need help.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=2376118
[Bug 2376118] Deprecate RPM Macros for setup.py-based Python Builds
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2378003
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2434850
Bug ID: 2434850
Summary: gettext-1.0 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: gettext
Keywords: FutureFeature, Triaged
Assignee: matiwari(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org,
matiwari(a)redhat.com, nphilipp(a)redhat.com,
petersen(a)redhat.com, sundeep_anand(a)yahoo.com
Target Milestone: ---
Classification: Fedora
Releases retrieved: 1.0
Upstream release that is considered latest: 1.0
Current version/release in rawhide: 0.26-4.fc44
URL: https://gnu.org/s/gettext/
Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
More information about the service that created this bug can be found at:
https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_M…
Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.
Based on the information from Anitya:
https://release-monitoring.org/project/898/
To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/gettext
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2434850
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2420900
Bug ID: 2420900
Summary: gettext FTBFS in eln mass rebuild
Product: Fedora
Version: rawhide
OS: Linux
Status: NEW
Component: gettext
Severity: medium
Assignee: matiwari(a)redhat.com
Reporter: petersen(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: dueno(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org,
matiwari(a)redhat.com, nphilipp(a)redhat.com,
petersen(a)redhat.com, sundeep_anand(a)yahoo.com
Target Milestone: ---
Classification: Fedora
In the recent ELN mass rebuild, gettext failed to rebuild due to latest gcc
getting more strict:
https://koji.fedoraproject.org/koji/taskinfo?taskID=139870804https://kojipkgs.fedoraproject.org/work/tasks/804/139870804/build.log
Like this:
In file included from /usr/include/features.h:540,
from /usr/include/uchar.h:26,
from ./uchar.h:45,
from c32isalnum.c:21:
./wchar.h:856:23: error: expected identifier or '(' before '_Generic'
856 | _GL_EXTERN_C wchar_t *wmemchr (const wchar_t *__s, wchar_t __wc, size_t
__n)
| ^~~~~~~
and many similar errors: not sure if an #include can fix this or something?
Might be good to alert upstream too.
Reproducible: Always
Steps to Reproduce:
1. rebuild gettext in rawhide (I didn't try F43, though it has seem gcc)
Actual Results:
Fails
Expected Results:
Success
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2420900
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2417582
Bug ID: 2417582
Summary: [abrt] ibus-libpinyin: _check_offset():
ibus-engine-libpinyin killed by SIGABRT
Product: Fedora
Version: 43
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:4a46cf28b71b7bda85a0968e1bf6ade5d591a433;VAR
IANT_ID=workstation;
Component: ibus-libpinyin
Assignee: pwu(a)redhat.com
Reporter: rimacc2ev(a)outlook.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, pwu(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
When choosing parts of chinese characters,this issue may appear randomly.
Sorry for cannot provide the detailed reproduce steps.
Version-Release number of selected component:
ibus-libpinyin-1.16.5-2.fc43
Additional info:
reporter: libreport-2.17.15
type: CCpp
reason: ibus-engine-libpinyin killed by SIGABRT
journald_cursor:
s=bc9246776a724277b46330b2f1aee892;i=78307;b=6dd9b410261f4251bd0aa2d6b9fc6181;m=1b2bf92437;t=6448761901280;x=be24863ca019a1bd
executable: /usr/libexec/ibus-engine-libpinyin
cmdline: /usr/libexec/ibus-engine-libpinyin --ibus
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.freedesktop.IBus.session.GNOME.service
rootdir: /
uid: 1000
kernel: 6.17.8-300.fc43.x86_64
package: ibus-libpinyin-1.16.5-2.fc43
runlevel: /bin/sh: 行 1: runlevel: 未找到命令
backtrace_rating: 4
crash_function: _check_offset
Truncated backtrace:
Thread no. 1 (16 frames)
#5 _check_offset at
/usr/src/debug/libpinyin-2.10.2-2.fc43.x86_64/src/pinyin.cpp:2173
#6 pinyin_guess_candidates at
/usr/src/debug/libpinyin-2.10.2-2.fc43.x86_64/src/pinyin.cpp:2222
#7 PY::PhoneticEditor::update at
/usr/src/debug/ibus-libpinyin-1.16.5-2.fc43.x86_64/src/PYPPhoneticEditor.cc:355
#8 PY::PhoneticEditor::selectCandidate at
/usr/src/debug/ibus-libpinyin-1.16.5-2.fc43.x86_64/src/PYPPhoneticEditor.cc:529
#9 PY::PhoneticEditor::selectCandidateInPage at
/usr/src/debug/ibus-libpinyin-1.16.5-2.fc43.x86_64/src/PYPPhoneticEditor.cc:547
#10 PY::PinyinEditor::processNumber at
/usr/src/debug/ibus-libpinyin-1.16.5-2.fc43.x86_64/src/PYPPinyinEditor.cc:81
#11 PY::PinyinEditor::processKeyEvent at
/usr/src/debug/ibus-libpinyin-1.16.5-2.fc43.x86_64/src/PYPPinyinEditor.cc:204
#12 PY::PinyinEngine::processKeyEvent at
/usr/src/debug/ibus-libpinyin-1.16.5-2.fc43.x86_64/src/PYPPinyinEngine.cc:437
#13 _ibus_marshal_BOOLEAN__UINT_UINT_UINT at
/usr/src/debug/ibus-1.5.33-1.fc43.x86_64/src/ibusmarshalers.c:280
#17 signal_emit_valist_unlocked at ../gobject/gsignal.c:3548
#20 ibus_engine_service_method_call at
/usr/src/debug/ibus-1.5.33-1.fc43.x86_64/src/ibusengine.c:1323
#21 call_in_idle_cb at ../gio/gdbusconnection.c:5476
#24 g_main_context_dispatch_unlocked at ../glib/gmain.c:4425
#25 g_main_context_iterate_unlocked at ../glib/gmain.c:4490
#27 ibus_main at /usr/src/debug/ibus-1.5.33-1.fc43.x86_64/src/ibusshare.c:336
#28 start_component at
/usr/src/debug/ibus-libpinyin-1.16.5-2.fc43.x86_64/src/PYMain.cc:161
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2417582
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2406377
Bug ID: 2406377
Summary: [abrt] ibus-hangul: hangul_ic_set_keyboard():
ibus-engine-hangul killed by SIGSEGV
Product: Fedora
Version: 43
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:00a010ce93688f8b0a87936af84bbdfc10509f7b;VAR
IANT_ID=workstation;
Component: ibus-hangul
Assignee: pwu(a)redhat.com
Reporter: joshua-huh(a)naver.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, pwu(a)redhat.com,
tfujiwar(a)redhat.com
Target Milestone: ---
Classification: Fedora
Version-Release number of selected component:
ibus-hangul-1.5.5-11.fc43
Additional info:
reporter: libreport-2.17.15
type: CCpp
reason: ibus-engine-hangul killed by SIGSEGV
journald_cursor:
s=a02d5f36b9df4747ac192d7370f2fb7f;i=16803;b=ccb914fab1e54a16a64ea23168c5c797;m=203c01c4;t=641fd07e84e13;x=cefe355fd7c94942
executable: /usr/libexec/ibus-engine-hangul
cmdline: /usr/libexec/ibus-engine-hangul --ibus
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.freedesktop.IBus.session.GNOME.service
rootdir: /
uid: 1000
kernel: 6.17.4-300.fc43.x86_64
package: ibus-hangul-1.5.5-11.fc43
runlevel: /bin/sh: line 1: runlevel: command not found
backtrace_rating: 4
crash_function: hangul_ic_set_keyboard
Truncated backtrace:
Thread no. 1 (14 frames)
#0 hangul_ic_set_keyboard at
/usr/src/debug/libhangul-0.2.0-2.fc43.x86_64/hangul/hangulinputcontext.c:1433
#1 hangul_ic_select_keyboard at
/usr/src/debug/libhangul-0.2.0-2.fc43.x86_64/hangul/hangulinputcontext.c:1481
#2 settings_changed at
/usr/src/debug/ibus-hangul-1.5.5-11.fc43.x86_64/src/engine.c:1946
#5 signal_emit_valist_unlocked at ../gobject/gsignal.c:3535
#8 g_settings_real_change_event at ../gio/gsettings.c:477
#9 _g_cclosure_marshal_BOOLEAN__POINTER_INTv at ../gio/gmarshal-internal.c:428
#10 _g_closure_invoke_va at ../gobject/gclosure.c:980
#11 signal_emit_valist_unlocked at ../gobject/gsignal.c:3439
#14 settings_backend_path_changed at ../gio/gsettings.c:552
#16 g_settings_backend_invoke_closure at ../gio/gsettingsbackend.c:270
#19 g_main_context_dispatch_unlocked at ../glib/gmain.c:4425
#20 g_main_context_iterate_unlocked at ../glib/gmain.c:4490
#22 ibus_main at /usr/src/debug/ibus-1.5.33
#23 start_component at
/usr/src/debug/ibus-hangul-1.5.5-11.fc43.x86_64/src/main.c:116
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2406377
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2399888
Bug ID: 2399888
Summary: Cannot see Hangul keyboard layout, confusing
activation
Product: Fedora
Version: 43
Status: NEW
Component: ibus-hangul
Assignee: pwu(a)redhat.com
Reporter: beland(a)alum.mit.edu
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, pwu(a)redhat.com,
tfujiwar(a)redhat.com
Target Milestone: ---
Classification: Fedora
I have gone into Settings -> Keyboard -> Input Sources and added Korean ->
Korean (Hangul).
One usability problem is that it's unclear how to switch input methods. I think
doing a web search I discovered it's possible to switch to 한 with Super+Space,
but this appears to have no effect; typing still produces Latin letters. In
order to actually type Hangul, after switching with Super+Space, I have to
notice that "en" has changed to "EN" in the bar at the top of the screen and
that I need to click on it to get a menu and enable "Hangul mode".
A second usability problem is that I cannot see a Hangul keyboard layout, which
I need because I am physically typing on a QWERTY keyboard. Turning on Hangul
mode and going to 한 -> Show Keyboard Layout pulls up a keyboard map, I believe
in a program called tecla, which has two pages and is labelled at the top
"Keyboard Layout - Korean". The first page shows a lowercase qwerty keyboard,
and the other page shows an uppercase QWERTY keyboard. There is no page showing
which key corresponds to which jamo, so the only way to type words in Korean is
to just press all the buttons on my keyboard until I find the one I need,
iteratively. 8(
This is with ibus-hangul-1.5.5-11.fc43 and tecla-49.0-1.fc43.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2399888
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…
https://bugzilla.redhat.com/show_bug.cgi?id=2395836
Bug ID: 2395836
Summary: don't combine pinyin Chinese IME and bopomofo Chinese
IME into one single package
Product: Fedora
Version: 42
Hardware: x86_64
OS: Linux
Status: NEW
Component: ibus-libpinyin
Keywords: Desktop, RFE
Severity: medium
Assignee: pwu(a)redhat.com
Reporter: lutingrong(a)hotmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, pwu(a)redhat.com
Target Milestone: ---
Classification: Fedora
Hello the authors of ibus-libpinyin ,
I'm using ibus-libpinyin on fedora 42 . I found ibus-libpinyin provides both
pinyin Chinese IME and bopomofo Chinese IME . Could you please consider split
ibus-libpinyin into ibus-libpinyin and ibus-libbopomofo ? The reason is that
those who use pinyin IME doesn't know bopomofo IME at all , and vice verse
those who use bopomofo IME doesn't know pinyin IME neither . So I can install
only the package which I use . Why must combine pinyin IME and bopomofo IME
into one single package ? Most hope there is no unnecessary codes in their
computers . Hope ibus-libpinyin more modularized and more divided ! Thanks for
your time and consideration!
Best regards,
Tingrong
Reproducible: Always
Steps to Reproduce:
1. sudo dnf install ibus-libpinyin
2. ibus-setup
3. will see there are both pinyin Chinese IME and bopomofo Chinese IME
Actual Results:
one single package -- ibus-libpinyin provides more than one IME .
Expected Results:
one package provides only one IME .
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2395836
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…