https://bugzilla.redhat.com/show_bug.cgi?id=2290513
Bug ID: 2290513
Summary: dahdi-tools-2.11.1-31.fc41 FTBFS: %setup0 does not
expand with rpm-build-4.19.91
Product: Fedora
Version: rawhide
URL: https://ppisar.fedorapeople.org/perl_rebuild/scratch/l
atest/packages/dahdi-tools/build.log
Status: NEW
Component: dahdi-tools
Assignee: jsmith.fedora(a)gmail.com
Reporter: ppisar(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: epel-packagers-sig(a)lists.fedoraproject.org,
jsmith.fedora(a)gmail.com
Blocks: 2260875 (F41FTBFS,RAWHIDEFTBFS)
Target Milestone: ---
Classification: Fedora
dahdi-tools-2.11.1-31.fc41 fails to build from sources in Fedora 41:
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.ee9Znl
+ umask 022
+ cd /home/test/fedora/dahdi-tools/dahdi-tools-2.11.1-build
+ %setup0 -q -n dahdi-tools-2.11.1 -a 2
/var/tmp/rpm-tmp.ee9Znl: line 34: fg: no job control
error: Bad exit status from /var/tmp/rpm-tmp.ee9Znl (%prep)
It seems that %setup0 macro does not expand with
rpm-build-4.19.91-7.fc41.x86_64. I believe that rpm intentionally stopped
supporting "macros" with a variadic digit suffix (%path0, %setup0 etc.).
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=2260875
[Bug 2260875] Fedora 41 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=2290513
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=2210415
Bug ID: 2210415
Summary: gajim-1.8.0 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: gajim
Keywords: FutureFeature, Triaged
Assignee: mschmidt(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
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
Releases retrieved: 1.8.0
Upstream release that is considered latest: 1.8.0
Current version/release in rawhide: 1.7.3-2.fc39
URL: https://gajim.org/
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/870/
To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/gajim
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2210415
https://bugzilla.redhat.com/show_bug.cgi?id=2210464
Bug ID: 2210464
Summary: python-nbxmpp-4.3.0 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: python-nbxmpp
Keywords: FutureFeature, Triaged
Assignee: mschmidt(a)redhat.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: epel-packagers-sig(a)lists.fedoraproject.org,
mschmidt(a)redhat.com, suraia(a)ikkoku.de
Target Milestone: ---
Classification: Fedora
Releases retrieved: 4.3.0
Upstream release that is considered latest: 4.3.0
Current version/release in rawhide: 4.2.2-1.fc39
URL: https://dev.gajim.org/gajim/python-nbxmpp/
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/12980/
To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/python-nbxmpp
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2210464
https://bugzilla.redhat.com/show_bug.cgi?id=2292430
Bug ID: 2292430
Summary: [abrt] blender: dri2_wl_visual_idx_from_pipe_format():
blender killed by SIGSEGV
Product: Fedora
Version: 40
Hardware: x86_64
Status: NEW
Whiteboard: abrt_hash:ffa9aa927839f14bde192bbf474ca5766cfd12d6;VAR
IANT_ID=workstation;
Component: blender
Assignee: luya_tfz(a)thefinalzone.net
Reporter: wanderingwolf8(a)protonmail.com
QA Contact: extras-qa(a)fedoraproject.org
CC: code(a)musicinmybrain.net,
design-devel(a)lists.fedoraproject.org,
epel-packagers-sig(a)lists.fedoraproject.org,
kwizart(a)gmail.com, luya_tfz(a)thefinalzone.net,
negativo17(a)gmail.com
Target Milestone: ---
Classification: Fedora
Description of problem:
I launched the app from the gnome launcher by clicking on the icon.
Version-Release number of selected component:
blender-1:4.1.1-3.fc40
Additional info:
reporter: libreport-2.17.15
type: CCpp
reason: blender killed by SIGSEGV
journald_cursor:
s=479ded9d89844ec3a0048da77395113f;i=157de2;b=b355d1677ab84dbb9a0bf58c0969c133;m=1b9c187c6;t=61adccd373f7c;x=7cb51c50f70b628c
executable: /usr/bin/blender
cmdline: /usr/bin/blender
cgroup:
0::/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-blender-20363.scope
rootdir: /
uid: 1000
kernel: 6.8.11-300.fc40.x86_64
package: blender-1:4.1.1-3.fc40
runlevel: N 5
backtrace_rating: 4
crash_function: dri2_wl_visual_idx_from_pipe_format
comment: I launched the app from the gnome launcher by clicking on the
icon.
Truncated backtrace:
Thread no. 1 (19 frames)
#0 dri2_wl_visual_idx_from_pipe_format at ../src/util/format/u_format.h:563
#1 server_supports_pipe_format at
../src/egl/drivers/dri2/platform_wayland.c:260
#2 dri2_wl_add_configs_for_visuals at
../src/egl/drivers/dri2/platform_wayland.c:1992
#3 dri2_initialize_wayland_drm at
../src/egl/drivers/dri2/platform_wayland.c:2178
#4 dri2_initialize_wayland at ../src/egl/drivers/dri2/platform_wayland.c:2869
#5 dri2_initialize at ../src/egl/drivers/dri2/egl_dri2.c:1080
#6 eglInitialize at ../src/egl/main/eglapi.c:698
#7 GHOST_ContextEGL::initializeDrawingContext at
/usr/src/debug/blender-4.1.1-3.fc40.x86_64/intern/ghost/intern/GHOST_ContextEGL.cc:356
#8 GHOST_WindowWayland::newDrawingContext at
/usr/src/debug/blender-4.1.1-3.fc40.x86_64/intern/ghost/intern/GHOST_WindowWayland.cc:2260
#9 GHOST_Window::setDrawingContextType at
/usr/src/debug/blender-4.1.1-3.fc40.x86_64/intern/ghost/intern/GHOST_Window.cc:65
#11 GHOST_WindowWayland::GHOST_WindowWayland at
/usr/src/debug/blender-4.1.1-3.fc40.x86_64/intern/ghost/intern/GHOST_WindowWayland.cc:1824
#12 GHOST_SystemWayland::createWindow at
/usr/src/debug/blender-4.1.1-3.fc40.x86_64/intern/ghost/intern/GHOST_SystemWayland.cc:7801
#13 GHOST_CreateWindow at
/usr/src/debug/blender-4.1.1-3.fc40.x86_64/intern/ghost/intern/GHOST_C-api.cc:173
#14 wm_window_ghostwindow_add at
/usr/src/debug/blender-4.1.1-3.fc40.x86_64/source/blender/windowmanager/intern/wm_window.cc:738
#15 wm_window_ghostwindow_ensure at
/usr/src/debug/blender-4.1.1-3.fc40.x86_64/source/blender/windowmanager/intern/wm_window.cc:831
#16 wm_window_ghostwindows_ensure at
/usr/src/debug/blender-4.1.1-3.fc40.x86_64/source/blender/windowmanager/intern/wm_window.cc:888
#17 WM_check at
/usr/src/debug/blender-4.1.1-3.fc40.x86_64/source/blender/windowmanager/intern/wm.cc:501
#18 wm_homefile_read_ex at
/usr/src/debug/blender-4.1.1-3.fc40.x86_64/source/blender/windowmanager/intern/wm_files.cc:1481
#19 WM_init at
/usr/src/debug/blender-4.1.1-3.fc40.x86_64/source/blender/windowmanager/intern/wm_init_exit.cc:287
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2292430
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=2283800
Bug ID: 2283800
Summary: Integrate Valkey with SELinux
Product: Fedora
Version: 39
Hardware: x86_64
OS: Linux
Status: NEW
Component: valkey
Keywords: SELinux
Severity: high
Assignee: jonathan(a)almalinux.org
Reporter: fedora(a)joshuanoeske.de
CC: epel-packagers-sig(a)lists.fedoraproject.org,
fedora(a)famillecollet.com, jonathan(a)almalinux.org,
nathans(a)redhat.com, ngompa13(a)gmail.com
Target Milestone: ---
Classification: Fedora
Currently, valkey runs with security context 'unconfined_service_t'. Moreover,
the file context of the standard directory for unix sockets (/var/run/valkey)
is 'var_run_t'. In comparison, redis runs with context 'redis_t', its socket
directory (/var/run/redis) uses 'redis_var_run_t'.
This has several implications for using unix sockets. Firstly, httpd/php-fpm is
not allowed to access the unix socket in /var/run/valkey as is has the wrong
file context. See the following SELinux message:
type=AVC msg=audit(1716984122.216:1041): avc: denied { write } for pid=7316
comm="php-fpm" name="valkey.sock" dev="tmpfs" ino=2973
scontext=system_u:system_r:httpd_t:s0 tcontext=system_u:object_r:var_run_t:s0
tclass=sock_file permissive=0
/var/run/redis automatically has the file context redis_var_run_t. However, if
you managed to make valkey use /var/run/redis, which is a problem in itself
(see https://bugzilla.redhat.com/show_bug.cgi?id=2283798) it still does not
work because the socket was created by a process running unconfined. See the
following error message (it is from valkey's socket, I renamed the socket to
redis-server.sock to try if that makes a difference):
type=AVC msg=audit(1716985343.79:1314): avc: denied { connectto } for pid=7315
comm="php-fpm" path="/run/redis/redis-server.sock"
scontext=system_u:system_r:httpd_t:s0
tcontext=system_u:system_r:unconfined_service_t:s0 tclass=unix_stream_socket
permissive=0
This makes valkey for me completely unusable at the moment. I will maybe try to
generate my own SELinux policy with audit2allow, eventually, but for now, I
will switch back to redis.
Maybe the existing contexts from redis can be reused? Or can new ones be
created with valkey in their name instead of redis, but which basically
function exactly like the redis contexts?
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=2283800
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=2292885
Bug ID: 2292885
Summary: python-tenacity-8.4.1 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: python-tenacity
Keywords: FutureFeature, Triaged
Assignee: aekoroglu(a)linux.intel.com
Reporter: upstream-release-monitoring(a)fedoraproject.org
QA Contact: extras-qa(a)fedoraproject.org
CC: aekoroglu(a)linux.intel.com, daltonminer(a)gmail.com,
davide(a)cavalca.name,
epel-packagers-sig(a)lists.fedoraproject.org,
michel(a)michel-slm.name, mrunge(a)redhat.com,
ngompa13(a)gmail.com
Target Milestone: ---
Classification: Fedora
Releases retrieved: 8.4.0, 8.4.1
Upstream release that is considered latest: 8.4.1
Current version/release in rawhide: 8.2.3-4.fc41
URL: https://github.com/jd/tenacity
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/12218/
To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/python-tenacity
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2292885
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-sp…