public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
To: git-commits@fedoraproject.org
Subject: [rpms/glib2] cve-2026-58016-f44: Drop manual byte compilation and call to marshalparser
Date: Tue, 11 Aug 2026 10:38:17 GMT	[thread overview]
Message-ID: <178644469758.1.17327467089626271414.rpms-glib2-ddcd084633b7@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/glib2
            Branch : cve-2026-58016-f44
            Commit : ddcd084633b758e6e4699f46e8167eab6ae49542
            Author : Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
            Date   : 2024-06-18T14:09:21+02:00
            Stats  : +1/-16 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/glib2/c/ddcd084633b758e6e4699f46e8167eab6ae49542?branch=cve-2026-58016-f44

            Log:
            Drop manual byte compilation and call to marshalparser

Since https://fedoraproject.org/wiki/Changes/ReproducibleBuildsClampMtimes,
the issues with cache invalidation should be fixed and the timestamp
of a generated file set to $SOURCE_DATE_EPOCH.

Pyc files are processed automatically by add-determinism:
https://fedoraproject.org/wiki/Changes/ReproduciblePackageBuilds

---
diff --git a/glib2.spec b/glib2.spec
index aaafa60..1f90c4f 100644
--- a/glib2.spec
+++ b/glib2.spec
@@ -33,7 +33,6 @@ BuildRequires:  pkgconfig(sysprof-capture-4)
 BuildRequires:  pkgconfig(zlib)
 BuildRequires:  python3-devel
 BuildRequires:  /usr/bin/g-ir-scanner
-BuildRequires:  /usr/bin/marshalparser
 BuildRequires:  /usr/bin/rst2man
 
 # Dependencies for tests
@@ -119,21 +118,7 @@ the functionality of the installed glib2 package.
 %install
 %meson_install
 
-# We need reproducible .pyc files across architectures to support multilib installations
-# https://bugzilla.redhat.com/show_bug.cgi?id=2008912
-# https://docs.fedoraproject.org/en-US/packaging-guidelines/Python_Appendix/#_byte_compilation_reproducibility
-%global py_reproducible_pyc_path %{buildroot}%{_datadir}
-
-# Since this is a generated .py file, set it to a known timestamp
-# because the source timestamp is baked into the .pyc file
-# 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 %{buildroot}%{_datadir}/glib-2.0/codegen/*.py
-
-# Perform byte compilation manually to avoid issues with
-# irreproducibility of the default invalidation mode, see
-# https://www.python.org/dev/peps/pep-0552/ and
-# https://bugzilla.redhat.com/show_bug.cgi?id=1686078
+# Perform byte compilation manually on paths outside the usual locations
 %py_byte_compile %{python3} %{buildroot}%{_datadir}
 
 mv %{buildroot}%{_bindir}/gio-querymodules %{buildroot}%{_bindir}/gio-querymodules-%{__isa_bits}

                 reply	other threads:[~2026-08-11 10:38 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=178644469758.1.17327467089626271414.rpms-glib2-ddcd084633b7@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