[Bug 2237693] New: rocksdb should not BuildRequire /usr/bin/python3
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2237693
Bug ID: 2237693
Summary: rocksdb should not BuildRequire /usr/bin/python3
Product: Fedora EPEL
Version: epel8
Status: NEW
Component: rocksdb
Assignee: epel-packagers-sig(a)lists.fedoraproject.org
Reporter: lbalhar(a)redhat.com
CC: davide(a)cavalca.name,
epel-packagers-sig(a)lists.fedoraproject.org,
hegjon(a)gmail.com, mmuzila(a)redhat.com
Target Milestone: ---
Classification: Fedora
Packages in RHEL 8 should not use, Require or BuildRequire `/usr/bin/python3`
because that file is provided by all the Python stacks - 3.6 (the main one),
3.8, 3.9, and 3.11. The particular version `/usr/bin/python3` points to depends
on the system of alternatives and is determined either by the priority of the
individual options or by manual setting by the system administrator. Python 3.6
has the highest priority, so if it is installed, `/usr/bin/python3` means
Python 3.6 by default. However, when Python 3.6 is not installed,
`/usr/bin/python3` can mean almost anything.
Python 3.6 is the only Python in RHEL 8 with a full 10+ years of support and
all system packages should depend on it. All other Python stacks have a shorter
support period. If you wish to use an alternate Python version becasue the life
cycle of your package allows you to do it, always choose that version
explicitly rather than allowing dnf to pull in any Python version.
Packages that Require `/usr/bin/python3` used to install Python 3.6 as a
dependency by default, so for majority of use cases this problem never
surfaced. However, python3.11 sort alphabetically sooner than python36, so
users of RHEL 8.8 will get Python 3.11 by default when a package requires
`/usr/bin/python3`.
Please, switch the BuildRequires to `python3-devel` and make sure to always use
%{python3} during the build when invoking Python rather than invoking
`/usr/bin/python3`. If your need to, you can change shebangs by the
%py3_shebang_fix macro. Shebangs of installed files are automatically mangled
by `/usr/lib/rpm/redhat/brp-mangle-shebangs`.
It is absolutely essential that no RHEL 8 package Requires `/usr/bin/python3`
on runtime. Even if you are confident that your code will work on any Python
future version, it is not a good idea to support this for our customers.
And also do not hesitate to let me know if you need any assistance or more
information.
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2237693
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...
4 months, 2 weeks
[Bug 2179598] New: Icons not showing in themes
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2179598
Bug ID: 2179598
Summary: Icons not showing in themes
Product: Fedora
Version: 37
Hardware: x86_64
Status: NEW
Component: gnome-icon-theme
Assignee: klember(a)redhat.com
Reporter: jkopcak+fedoraproject(a)zohomail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: caolanm(a)redhat.com,
epel-packagers-sig(a)lists.fedoraproject.org,
gnome-sig(a)lists.fedoraproject.org, klember(a)redhat.com,
rhughes(a)redhat.com, rstrode(a)redhat.com,
sandmann(a)redhat.com, stefano(a)karapetsas.com
Target Milestone: ---
Classification: Fedora
Description of problem:
Gnome icons do not appear in Themes.
Version-Release number of selected component (if applicable):
gnome-icon-theme-3.12.0-18.fc37.noarch
How reproducible:
Always, Fedora Cinnamon 37 and up.
Steps to Reproduce:
1. Menu
2. System Settings
3. Themes
4. Click the active "Icons" set
Actual results:
"gnome" icon set does not appear as an option.
Expected results:
Appear as an option in the list.
Additional info:
Fedora 36 system with gnome icons selected in Themes, then upgraded to 37,
"gnome" is shown as the selected option for Icons after upgrade. Though shown
as the active icon theme, it does not appear in the list and cannot be selected
again once changed.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2179598
4 months, 2 weeks
[Bug 2177329] New: fedpkg import srpm doesn't work with rpmautospec
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2177329
Bug ID: 2177329
Summary: fedpkg import srpm doesn't work with rpmautospec
Product: Fedora
Version: 37
Hardware: All
OS: All
Status: NEW
Component: python-rpmautospec
Severity: urgent
Assignee: asaleh(a)redhat.com
Reporter: gbcox(a)bzb.us
QA Contact: extras-qa(a)fedoraproject.org
CC: asaleh(a)redhat.com,
epel-packagers-sig(a)lists.fedoraproject.org,
infra-sig(a)lists.fedoraproject.org,
michel(a)michel-slm.name, nphilipp(a)redhat.com,
sgallagh(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
My workflow for uploading packages is:
$ git add -u
$ fedpkg clog
$ git commit -F clog
$ fedpkg import updated.srpm
$ git commit --am
~~~
fedpkg push
fedpkg build
When trying this with a package that has been converted to use rpmautospec, it
brakes the import srpm functionality.
I receive the following message:
Could not execute import_srpm: SRPM was processed by rpmautospec (specfile
msmtp.spec" was analyzed)
fedpkg import is a key function so this needs to be corrected
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2177329
4 months, 2 weeks
[Bug 2176799] New: [abrt] gajim: _sub_I_65535_0.0(): python3.11 killed by SIGTRAP
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2176799
Bug ID: 2176799
Summary: [abrt] gajim: _sub_I_65535_0.0(): python3.11 killed by
SIGTRAP
Product: Fedora
Version: 37
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:ca9065f5a474149cb513b6f56f6b71a12a570d50;VAR
IANT_ID=workstation;
Component: gajim
Assignee: mschmidt(a)redhat.com
Reporter: jan.public(a)famvlug.nl
QA Contact: extras-qa(a)fedoraproject.org
CC: epel-packagers-sig(a)lists.fedoraproject.org,
lemenkov(a)gmail.com, mschmidt(a)redhat.com,
redhat-bugzilla(a)linuxnetz.de, suraia(a)ikkoku.de
Target Milestone: ---
Classification: Fedora
Description of problem:
Happened when receiving an incoming audio call.
Version-Release number of selected component:
gajim-1.6.1-1.fc37
Additional info:
reporter: libreport-2.17.4
backtrace_rating: 3
cmdline: /usr/bin/python3 -sP /usr/bin/gajim
crash_function: _sub_I_65535_0.0
executable: /usr/bin/python3.11
journald_cursor:
s=35a57af056274a84bdea3fe35819825f;i=1d3e72;b=dacc0ddebaa7479896acf66bfeb7548d;m=24917d7326;t=5f59ca6e581a4;x=933d387ba9e74ade
kernel: 6.1.13-200.fc37.x86_64
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2176799
4 months, 2 weeks
[Bug 2176185] New: [abrt] gnome-calendar: _gtk_widget_is_sensitive(): gnome-calendar killed by SIGSEGV
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2176185
Bug ID: 2176185
Summary: [abrt] gnome-calendar: _gtk_widget_is_sensitive():
gnome-calendar killed by SIGSEGV
Product: Fedora
Version: 37
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:a5a4a621fe947a1a3c2837111fa5d4fd6f4c165d;VAR
IANT_ID=workstation;
Component: gnome-calendar
Assignee: gnome-sig(a)lists.fedoraproject.org
Reporter: youplamb(a)hotmail.nl
QA Contact: extras-qa(a)fedoraproject.org
CC: epel-packagers-sig(a)lists.fedoraproject.org,
gnome-sig(a)lists.fedoraproject.org,
igor.raits(a)gmail.com, klember(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
adding a location to a calendar entry
Version-Release number of selected component:
gnome-calendar-43.1-3.fc37
Additional info:
reporter: libreport-2.17.4
backtrace_rating: 3
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/app.slice/dbus-:1.2-org.gnome.Calendar@0.service
cmdline: /usr/bin/gnome-calendar --gapplication-service
crash_function: _gtk_widget_is_sensitive
executable: /usr/bin/gnome-calendar
journald_cursor:
s=8b593f4d013b441aa2224344ad125a83;i=1d7186;b=9ef4199959dd46e394d85341b0cbff5f;m=1e833045d;t=5f650ba8ba4bf;x=7948b4ef321892b2
kernel: 6.1.14-200.fc37.x86_64
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (10 frames)
#0 _gtk_widget_is_sensitive at ../gtk/gtkwidgetprivate.h:491
#1 gtk_propagate_event_internal.isra.0 at ../gtk/gtkmain.c:1895
#2 gtk_main_do_event at ../gtk/gtkmain.c:1680
#3 surface_event at ../gtk/gtkwindow.c:4735
#4 _gdk_marshal_BOOLEAN__POINTERv at gdk/gdkmarshalers.c:302
#5 gdk_surface_event_marshallerv at ../gdk/gdksurface.c:463
#6 g_signal_group__target_weak_notify at ../gobject/gsignalgroup.c:163
#7 g_list_insert_before at ../glib/glist.c:478
#8 ??
#9 ??
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2176185
4 months, 2 weeks
[Bug 2175907] New: [abrt] cinnamon: set_timezone(): cs_calendar.py:262:set_timezone:ValueError: not enough values to unpack (expected 2, got 1)
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2175907
Bug ID: 2175907
Summary: [abrt] cinnamon: set_timezone():
cs_calendar.py:262:set_timezone:ValueError: not enough
values to unpack (expected 2, got 1)
Product: Fedora
Version: 37
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:b5a1c49ef40e957ee878506e03d89171ad346dfd;VAR
IANT_ID=cinnamon;
Component: cinnamon
Assignee: leigh123linux(a)googlemail.com
Reporter: paulo.peixoto(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: epel-packagers-sig(a)lists.fedoraproject.org,
leigh123linux(a)googlemail.com, miketwebster(a)gmail.com,
riehecky(a)fnal.gov
Target Milestone: ---
Classification: Fedora
Description of problem:
Opening the date and time settings and enabling Network Time
Version-Release number of selected component:
cinnamon-5.6.7-1.fc37
Additional info:
reporter: libreport-2.17.4
cgroup: 0::/user.slice/user-1000.slice/session-3.scope
cmdline: cinnamon-settings '' '' '' '' '' '' '' '' '' '' '' '' '' '' ''
'' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' ''
'' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' '' ''
crash_function: set_timezone
exception_type: ValueError
executable: /usr/share/cinnamon/cinnamon-settings/cinnamon-settings.py
interpreter: cinnamon-5.6.7-1.fc37.x86_64
kernel: 6.1.14-200.fc37.x86_64
runlevel: N 5
type: Python3
uid: 1000
Truncated backtrace:
cs_calendar.py:262:set_timezone:ValueError: not enough values to unpack
(expected 2, got 1)
Traceback (most recent call last):
File "/usr/share/cinnamon/cinnamon-settings/modules/cs_calendar.py", line
194, in _on_proxy_ready
self.proxy_ready_callback()
File "/usr/share/cinnamon/cinnamon-settings/modules/cs_calendar.py", line 77,
in _on_proxy_ready
self.tz_selector.set_timezone(self.zone)
File "/usr/share/cinnamon/cinnamon-settings/modules/cs_calendar.py", line
262, in set_timezone
region, city = timezone.split('/', maxsplit=1)
^^^^^^^^^^^^
ValueError: not enough values to unpack (expected 2, got 1)
Local variables in innermost frame:
self: <cs_calendar.TimeZoneSelector object at 0x7f047b0f3840
(cs_calendar+TimeZoneSelector at 0x55f098800570)>
timezone: 'Portugal'
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2175907
4 months, 2 weeks
[Bug 2173204] New: [abrt] gnome-calendar: g_type_check_instance_cast(): gnome-calendar killed by SIGSEGV
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2173204
Bug ID: 2173204
Summary: [abrt] gnome-calendar: g_type_check_instance_cast():
gnome-calendar killed by SIGSEGV
Product: Fedora
Version: 37
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:097a7df52881ab113babff5506fdfdc0bb63e8d1;VAR
IANT_ID=workstation;
Component: gnome-calendar
Assignee: gnome-sig(a)lists.fedoraproject.org
Reporter: mohamed.b.baig(a)gmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: epel-packagers-sig(a)lists.fedoraproject.org,
gnome-sig(a)lists.fedoraproject.org,
igor.raits(a)gmail.com, klember(a)redhat.com
Target Milestone: ---
Classification: Fedora
Description of problem:
Clicked to future day from the left nav then clicked back on today's date
Version-Release number of selected component:
gnome-calendar-43.1-3.fc37
Additional info:
reporter: libreport-2.17.4
backtrace_rating: 4
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/app.slice/dbus-:1.2-org.gnome.Calendar@0.service
cmdline: /usr/bin/gnome-calendar --gapplication-service
crash_function: g_type_check_instance_cast
executable: /usr/bin/gnome-calendar
journald_cursor:
s=829bd94ca3fa4b64af263b98ea52b01f;i=da28c;b=5b2b156c38514bbe8228dc075ef7c8fa;m=2747c93f6;t=5f575d1e7b057;x=8f8db0b61ac96f1c
kernel: 6.1.13-200.fc37.x86_64
rootdir: /
runlevel: N 5
type: CCpp
uid: 1000
Truncated backtrace:
Thread no. 1 (7 frames)
#0 g_type_check_instance_cast at ../gobject/gtype.c:4122
#1 gcal_agenda_view_remove_event at ../src/gui/views/gcal-agenda-view.c:586
#2 remove_event_from_subscriber at ../src/core/gcal-timeline.c:228
#3 timeline_source_dispatch at ../src/core/gcal-timeline.c:717
#6 g_main_context_iterate.constprop.0 at ../glib/gmain.c:4238
#7 g_main_context_iteration at ../glib/gmain.c:4303
#8 g_application_run at ../gio/gapplication.c:2571
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2173204
4 months, 2 weeks