https://bugzilla.redhat.com/show_bug.cgi?id=2209413
Bug ID: 2209413
Summary: Prepare for DNF 5, don't depend on `dnf`
Product: Fedora
Version: rawhide
Hardware: All
OS: Linux
Status: NEW
Component: system-config-language
Severity: high
Assignee: pnemade(a)redhat.com
Reporter: egoode(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, pnemade(a)redhat.com
Target Milestone: ---
Classification: Fedora
(I'm filing issues with all the packages that currently depend on `dnf`.)
DNF 5 is a new package manager that will replace DNF 4 in Fedora 39+: Starting
in Fedora 39, the `dnf` command will be provided by the `dnf5` package rather
than the `dnf` package, and `dnf5` will obsolete `dnf`. Since
system-config-language currently depends on DNF 4, it should choose one of the
following strategies to avoid breaking the Fedora upgrade:
- Add support for DNF 5, and depend on the `dnf5` package in Fedora 39+ instead
of `dnf`. Builds of DNF 5 are available in this COPR repository:
https://copr.fedorainfracloud.org/coprs/rpmsoftwaremanagement/dnf-nightly/, and
documentation is available here: https://dnf5.readthedocs.io/en/latest/.
- Alternatively, or in the meantime, change the system-config-language package
to depend on `python3-dnf` instead of `dnf`, and call the `dnf-3` binary
instead of `dnf`. The old DNF 4 command will still be available in the
distribution, but only as `dnf-3` (the binary is called `dnf-3` rather than
`dnf4` for historical reasons; it is the "Python 3 version" of DNF). The first
option is preferred to this one; it is not recommended to modify installed
software using both DNF 4 and DNF 5 on the same system.
- Or, if this package is no longer being maintained, consider removing it from
Fedora.
At some point, this project should adopt DNF 5, but the immediate issue is
removing the dependency on `dnf`. We are planning to replace DNF with DNF5 in
Fedora Rawhide very soon, by 2023-06-01, and the system-config-language package
will break as long as it still depends on the `dnf` package.
For more information about the switch to DNF 5, see
https://fedoraproject.org/wiki/Changes/ReplaceDnfWithDnf5.
Reproducible: Always
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2209413
https://bugzilla.redhat.com/show_bug.cgi?id=2335055
Bug ID: 2335055
Summary: gettext-0.23.1 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: 0.23.1
Upstream release that is considered latest: 0.23.1
Current version/release in rawhide: 0.23-1.fc42
URL: https://www.gnu.org/software/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=2335055
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=2241601
Bug ID: 2241601
Summary: Fedora input broke the fr(oss) French layout (default
Fedora French layout)
Product: Fedora
Version: rawhide
OS: Linux
Status: NEW
Component: xkeyboard-config
Severity: medium
Assignee: peter.hutterer(a)redhat.com
Reporter: nicolas.mailhot(a)laposte.net
QA Contact: extras-qa(a)fedoraproject.org
CC: ajax(a)redhat.com, i18n-bugs(a)lists.fedoraproject.org,
negativo17(a)gmail.com, peter.hutterer(a)redhat.com,
rhughes(a)redhat.com, rstrode(a)redhat.com
Target Milestone: ---
Classification: Fedora
fr(oss) is supposed to emit French upper case accented letters in caps locks
mode ÉÈÇÀ
Something changed in the past months and it emits lower case instead. So you
get very annoying mixed-case éLéGANT runs of text in caps locks.
Explicit level 4 capital selection still works but this change breaks existing
user habits and is very inconvenient for new users.
To be honest I’ve noticed the breakage for some time but was hoping it was a
stupid mistake that would go away with time.
Reproducible: Always
Steps to Reproduce:
1. switch to fr(oss)
2. set cap locks
3. tap the first (number) row → letters with diacritics should be emitted in
upper case, for example É, not lower case é
It is not a bug that cap locks produces symbols and accented letters. In
azerty, unlike qwerty, access to the diacritics necessary to type proper French
is prioritized over access to numbers
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2241601
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=2002446
Bug ID: 2002446
Summary: zinnia-0.07 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: zinnia
Keywords: FutureFeature, Triaged
Assignee: liangsuilong(a)gmail.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org,
liangsuilong(a)gmail.com, petersen(a)redhat.com,
pwu(a)redhat.com
Target Milestone: ---
Classification: Fedora
Latest upstream release: 0.07
Current version/release in rawhide: 0.06-55.fc35
URL: https://github.com/silverhikari/zinnia/
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://fedoraproject.org/wiki/Upstream_release_monitoring
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/5302/
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1974076
Bug ID: 1974076
Summary: Chinese input methods use previously enabled layout
Product: Fedora
Version: 34
Hardware: All
OS: Linux
Status: NEW
Component: ibus-libpinyin
Severity: medium
Assignee: pwu(a)redhat.com
Reporter: nickolay.ilyushin(a)gmail.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:
ibus-libpinyin (and most probably several other input methods) uses `default`
keyboard layout instead of `us` or whatever fits best. This effectively means
that the last keyboard layout (non-IME) will be used for the pinyin input. For
users which use non-Latin keyboard layouts, such as Russian or Ukrainian, this
makes pinyin input unusable.
Version-Release number of selected component (if applicable): 1.12.0
How reproducible: easily.
Steps to Reproduce:
1. Enable pinyin input method in your settings.
2. Switch to e.g. Russian layout.
3. Switch to pinyin IME.
4. You will type Russian letters and pinyin IME will not trigger.
Actual results:
`4. You will type Russian letters and pinyin IME will not trigger.`
Expected results:
`4. You will type *Latin* letters and pinyin IME *will* trigger.`
Additional info:
There are two workarounds:
1. Manually patch `/usr/share/ibus/component/libpinyin.xml` and change `layout`
to `us` from `default`. I don't know how this will work with non-QWERTY
keyboards though.
2. Switch to a Latin layout before switching to pinyin.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2354144
Bug ID: 2354144
Summary: translate-toolkit FTBFS due to missing tox
configuration
Product: Fedora
Version: rawhide
Status: NEW
Component: translate-toolkit
Assignee: petersen(a)redhat.com
Reporter: mhroncok(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com,
petersen(a)redhat.com, sshil(a)redhat.com,
sundeep_anand(a)yahoo.com
Blocks: 2322407 (PYTHON3.14), 2339432 (F43FTBFS,RAWHIDEFTBFS)
Target Milestone: ---
Classification: Fedora
Hello.
translate-toolkit fails to build from source becasue it uses one or both of:
- %pyproject_buildrequires -t/-e (generate dependencies via tox)
- %tox (run tox)
without tox configuration (e.g. tox.ini or tox section of
pyproject.toml/setup.cfg).
This was always supposed to fail, but regressed with tox 4.
Now it fails again.
https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproj…https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedorapr…
If this package uses tox upstream, make sure to use a source tarball that
includes the tox configuration (e.g. an archive from GitHub instead of sdist
from PyPI).
If this package does not use tox upstream, you cannot use the tox options.
If your package uses %pyproject_buildrequires -t/-e but does not use %tox, just
drop the -t/-e option.
If your package uses %tox, replace the call with a more suitable way for
running tests (e.g. %pytest).
Let me know if you need assistance. Thanks.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=2322407
[Bug 2322407] Python 3.14
https://bugzilla.redhat.com/show_bug.cgi?id=2339432
[Bug 2339432] Fedora 43 FTBFS Tracker
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2354144
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=2338091
Bug ID: 2338091
Summary: [abrt] ibus-typing-booster: g_list_last(): python3.13
killed by SIGSEGV
Product: Fedora
Version: 41
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:5853aa3fb62e2c51aeeab7a86c31a15bc64d7945;VAR
IANT_ID=workstation;
Component: ibus-typing-booster
Assignee: mfabian(a)redhat.com
Reporter: baltazar.diaz(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: i18n-bugs(a)lists.fedoraproject.org, mfabian(a)redhat.com
Target Milestone: ---
Classification: Fedora
Version-Release number of selected component:
ibus-typing-booster-2.27.7-1.fc41
Additional info:
reporter: libreport-2.17.15
type: CCpp
reason: python3.13 killed by SIGSEGV
journald_cursor:
s=0bc8e123142841989333a15b6ade2cb9;i=2191f;b=0e83ab47da9e41349e57477282f58f90;m=408949ed;t=62b9fed710848;x=426df6de097d5361
executable: /usr/bin/python3.13
cmdline: /usr/bin/python3 /usr/share/ibus-typing-booster/engine/main.py
--ibus
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/session.slice/org.freedesktop.IBus.session.GNOME.service
rootdir: /
uid: 1000
kernel: 6.12.8-200.fc41.x86_64
package: ibus-typing-booster-2.27.7-1.fc41
runlevel: N 5
dso_list: /usr/bin/python3.13 python3-3.13.1-2.fc41.x86_64 (Fedora
Project) 1736523791
backtrace_rating: 4
crash_function: g_list_last
Truncated backtrace:
Thread no. 1 (32 frames)
#0 g_list_last at ../glib/glist.c:925
#1 g_list_append at ../glib/glist.c:209
#2 g_queue_push_tail at ../glib/gqueue.c:418
#3 defer_message.isra.0 at ../atspi/atspi-misc.c:995
#4 atspi_dbus_filter at ../atspi/atspi-misc.c:1021
#7 message_queue_dispatch at ../atspi/atspi-gmain.c:89
#9 g_main_context_dispatch_unlocked at ../glib/gmain.c:4208
#10 g_main_context_iterate_unlocked.isra.0 at ../glib/gmain.c:4273
#12 ffi_call_unix64 at ../src/x86/unix64.S:104
#13 ffi_call_int at ../src/x86/ffi64.c:673
#14 ffi_call at ../src/x86/ffi64.c:710
#15 pygi_invoke_c_callable at ../gi/pygi-invoke.c:684
#16 pygi_function_cache_invoke at ../gi/pygi-cache.c:862
#17 pygi_callable_info_invoke at ../gi/pygi-invoke.c:727
#18 _wrap_g_callable_info_invoke at ../gi/pygi-invoke.c:764
#19 _callable_info_call at ../gi/pygi-info.c:548
#21 _PyObject_MakeTpCall at
/usr/src/debug/python3.13-3.13.1-2.fc41.x86_64/Objects/call.c:242
#22 _PyEval_EvalFrameDefault at
/usr/src/debug/python3.13-3.13.1-2.fc41.x86_64/Python/generated_cases.c.h:813
#23 PyEval_EvalCode at
/usr/src/debug/python3.13-3.13.1-2.fc41.x86_64/Python/ceval.c:601
#24 run_eval_code_obj at
/usr/src/debug/python3.13-3.13.1-2.fc41.x86_64/Python/pythonrun.c:1337
#25 run_mod at
/usr/src/debug/python3.13-3.13.1-2.fc41.x86_64/Python/pythonrun.c:1422
#26 pyrun_file at
/usr/src/debug/python3.13-3.13.1-2.fc41.x86_64/Python/pythonrun.c:1255
#27 _PyRun_SimpleFileObject at
/usr/src/debug/python3.13-3.13.1-2.fc41.x86_64/Python/pythonrun.c:490
#28 _PyRun_AnyFileObject at
/usr/src/debug/python3.13-3.13.1-2.fc41.x86_64/Python/pythonrun.c:77
#29 pymain_run_file_obj at
/usr/src/debug/python3.13-3.13.1-2.fc41.x86_64/Modules/main.c:409
#30 pymain_run_file at
/usr/src/debug/python3.13-3.13.1-2.fc41.x86_64/Modules/main.c:428
#31 pymain_run_python at
/usr/src/debug/python3.13-3.13.1-2.fc41.x86_64/Modules/main.c:696
#32 Py_RunMain at
/usr/src/debug/python3.13-3.13.1-2.fc41.x86_64/Modules/main.c:775
#33 Py_BytesMain at
/usr/src/debug/python3.13-3.13.1-2.fc41.x86_64/Modules/main.c:829
#34 __libc_start_call_main at ../sysdeps/nptl/libc_start_call_main.h:58
#35 __libc_start_main_impl at ../csu/libc-start.c:360
#36 _start
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2338091
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…