public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Jan Grulich <jgrulich@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/glib2] cve-2026-58016-f44: Onboard to Packit for stable Fedora branches
Date: Tue, 11 Aug 2026 10:38:39 GMT [thread overview]
Message-ID: <178644471953.1.3740356057829598326.rpms-glib2-9fddadf057c5@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/glib2
Branch : cve-2026-58016-f44
Commit : 9fddadf057c501aa904a91ae31a24ed4b47128ba
Author : Jan Grulich <jgrulich@redhat.com>
Date : 2026-02-24T08:36:09+01:00
Stats : +59/-0 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/glib2/c/9fddadf057c501aa904a91ae31a24ed4b47128ba?branch=cve-2026-58016-f44
Log:
Onboard to Packit for stable Fedora branches
---
diff --git a/.packit.yaml b/.packit.yaml
new file mode 100644
index 0000000..b8fe31c
--- /dev/null
+++ b/.packit.yaml
@@ -0,0 +1,59 @@
+# Minimal Packit Configuration for GNOME Packages
+# Copy this to your dist-git repository as .packit.yaml
+#
+# Prerequisites:
+# - Package is monitored by release-monitoring.org
+# - Monitoring status set to "Monitoring" in dist-git
+
+# Required for tag filtering (release-monitoring also tracks alpha/beta)
+upstream_project_url: https://gitlab.gnome.org/GNOME/glib
+
+jobs:
+ # Automated updates for stable branches
+ - job: pull_from_upstream
+ trigger: release
+ # Packit does the full update (spec, changelog) on the latest stable branch.
+ # The exact same commit is reused to open PRs for all other stable branches,
+ # which can be merged with fast-forward only (git merge --ff-only),
+ # keeping a linear, non-divergent history across branches.
+ dist_git_branches:
+ fedora-latest-stable:
+ fast_forward_merge_into:
+ - fedora-stable
+
+ # ========================================================================
+ # VERSIONING: Choose ONE option based on your package's versioning scheme
+ # ========================================================================
+
+ # OPTION A: Major version only - allows minor and patch updates
+ # For 2-digit: 50.0 -> 50.1 ✅, 50.x -> 51.0 ❌
+ # For 3-digit: 1.2.3 -> 1.3.0 ✅, 1.x.x -> 2.0.0 ❌
+ # Use for: GNOME apps/libs with 2-digit versions, or libraries following semver
+ # version_update_mask: '^\d+\.'
+
+ # OPTION B: Major.minor version - patch updates only
+ # Examples: 1.2.3 -> 1.2.4 ✅, 1.2.x -> 1.3.0 ❌
+ # Use for: Libraries with ABI concerns, even/odd development scheme
+ version_update_mask: '^\d+\.\d+\.'
+
+ # ========================================================================
+ # TAG FILTERING - Filter out pre-releases from release-monitoring
+ # ========================================================================
+ # Required because release-monitoring.org also tracks alpha/beta/rc
+ upstream_tag_exclude: '.*(alpha|beta|rc).*'
+
+ # Optional - only include stable release tags:
+ # upstream_tag_include: '^\d+\.\d+$' # For 2-digit versions
+ # upstream_tag_include: '^\d+\.\d+\.\d+$' # For 3-digit versions
+
+ # Build in Koji after merge
+ - job: koji_build
+ trigger: commit
+ dist_git_branches:
+ - fedora-stable
+
+ # Submit Bodhi update
+ - job: bodhi_update
+ trigger: commit
+ dist_git_branches:
+ - fedora-stable
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=178644471953.1.3740356057829598326.rpms-glib2-9fddadf057c5@fedoraproject.org \
--to=jgrulich@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