public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
To: git-commits@fedoraproject.org
Subject: [rpms/glib2] cve-2026-58016-f44: Make sure all .py files have fixed timestamps
Date: Tue, 11 Aug 2026 10:36:45 GMT	[thread overview]
Message-ID: <178644460566.1.4020014233955089873.rpms-glib2-789d0acce00b@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/glib2
Branch : cve-2026-58016-f44
Commit : 789d0acce00b6332bdc9fc2f97b9e0b1e7311b10
Author : Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
Date   : 2019-03-06T13:33:00+01:00
Stats  : +8/-2 in 1 file(s)
URL    : https://src.fedoraproject.org/rpms/glib2/c/789d0acce00b6332bdc9fc2f97b9e0b1e7311b10?branch=cve-2026-58016-f44

Log:
Make sure all .py files have fixed timestamps

---
diff --git a/glib2.spec b/glib2.spec
index 9ca7f74..fb8ddda 100644
--- a/glib2.spec
+++ b/glib2.spec
@@ -9,7 +9,7 @@
 
 Name: glib2
 Version: 2.60.0
-Release: 1%{?dist}
+Release: 2%{?dist}
 Summary: A library of handy utility functions
 
 License: LGPLv2+
@@ -109,7 +109,9 @@ rm glib/pcre/*.[ch]
 # Since this is a generated .py file, set it to a known timestamp,
 # otherwise it will vary by build time, and thus break multilib -devel
 # installs.
-touch -r gio/gdbus-2.0/codegen/config.py.in $RPM_BUILD_ROOT/%{_datadir}/glib-2.0/codegen/config.py
+# Also copy the timestamp for other .py files, because meson doesn't do
+# this, see https://github.com/mesonbuild/meson/issues/5027.
+touch -r gio/gdbus-2.0/codegen/config.py.in $RPM_BUILD_ROOT/%{_datadir}/glib-2.0/codegen/*.py
 chrpath --delete $RPM_BUILD_ROOT%{_libdir}/*.so
 
 mv  $RPM_BUILD_ROOT%{_bindir}/gio-querymodules $RPM_BUILD_ROOT%{_bindir}/gio-querymodules-%{__isa_bits}
@@ -218,6 +220,10 @@ glib-compile-schemas %{_datadir}/glib-2.0/schemas &> /dev/null || :
 %{_datadir}/installed-tests
 
 %changelog
+* Wed Mar  6 2019 Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> - 2.60.0-2
+- Make sure all .py files have fixed timestamps (fixes issue with
+  parallel installability of i686 and amd64 -devel packages)
+
 * Mon Mar 04 2019 Kalev Lember <klember@redhat.com> - 2.60.0-1
 - Update to 2.60.0
 

                 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=178644460566.1.4020014233955089873.rpms-glib2-789d0acce00b@fedoraproject.org \
    --to=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