public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Kalev Lember <klember@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/glib2] cve-2026-58016-f44: Own /usr/share/gdb and /usr/share/systemtap directories
Date: Tue, 11 Aug 2026 10:36:09 GMT [thread overview]
Message-ID: <178644456919.1.2106477963695046065.rpms-glib2-720a3c04d333@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/glib2
Branch : cve-2026-58016-f44
Commit : 720a3c04d333b0baff643c7f76953f23d61b55cb
Author : Kalev Lember <klember@redhat.com>
Date : 2016-08-18T08:42:40+02:00
Stats : +3/-5 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/glib2/c/720a3c04d333b0baff643c7f76953f23d61b55cb?branch=cve-2026-58016-f44
Log:
Own /usr/share/gdb and /usr/share/systemtap directories
... to avoid leaving behind empty directories after uninstalling
glib2-devel.
---
diff --git a/glib2.spec b/glib2.spec
index 98115a3..1211dc7 100644
--- a/glib2.spec
+++ b/glib2.spec
@@ -210,12 +210,9 @@ chmod 644 $RPM_BUILD_ROOT%{_datadir}/bash-completion/completions/*
%{_mandir}/man1/gdbus-codegen.1*
%{_mandir}/man1/glib-compile-resources.1*
%{_mandir}/man1/gresource.1*
-%{_datadir}/gdb/auto-load%{_libdir}/libglib-2.0.so.*-gdb.py
-%{_datadir}/gdb/auto-load%{_libdir}/libgobject-2.0.so.*-gdb.py
-# Let's own the directory, as it was not there
-%{_datadir}/gdb/auto-load%{_libdir}/__pycache__
+%{_datadir}/gdb/
%{_datadir}/gettext/
-%{_datadir}/systemtap/tapset/*.stp
+%{_datadir}/systemtap/
%files doc
%doc %{_datadir}/gtk-doc/html/*
@@ -237,6 +234,7 @@ chmod 644 $RPM_BUILD_ROOT%{_datadir}/bash-completion/completions/*
%changelog
* Thu Aug 18 2016 Kalev Lember <klember@redhat.com> - 2.49.5-1
- Update to 2.49.5
+- Own /usr/share/gdb and /usr/share/systemtap directories
* Tue Aug 16 2016 Miro Hrončok <mhroncok@redhat.com> - 2.49.4-3
- Use Python 3 for the RPM Python byte compilation
reply other threads:[~2026-08-11 10:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178644456919.1.2106477963695046065.rpms-glib2-720a3c04d333@fedoraproject.org \
--to=klember@redhat.com \
--cc=git-commits@fedoraproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox