public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Davide Cavalca <dcavalca@fedoraproject.org>
To: git-commits@fedoraproject.org
Subject: [rpms/pipewire-epel] epel10: Bump releaes to avoid issues on upgrades
Date: Thu, 17 Sep 2026 17:12:43 GMT [thread overview]
Message-ID: <178966516349.1.6210139238335239628.rpms-pipewire-epel-668f8bc42330@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/pipewire-epel
Branch : epel10
Commit : 668f8bc42330c0ed9065df8c73d3b01beee877a8
Author : Davide Cavalca <dcavalca@fedoraproject.org>
Date : 2026-09-17T10:12:26-07:00
Stats : +5/-2 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/pipewire-epel/c/668f8bc42330c0ed9065df8c73d3b01beee877a8?branch=epel10
Log:
Bump releaes to avoid issues on upgrades
---
diff --git a/pipewire-epel.spec b/pipewire-epel.spec
index c1c23c8..6a57b06 100644
--- a/pipewire-epel.spec
+++ b/pipewire-epel.spec
@@ -12,7 +12,7 @@
%global ms_version 0.4.2
# For rpmdev-bumpspec and releng automation
-%global baserelease 2
+%global baserelease 3
#global snapdate 20210107
#global gitcommit b17db2cebc1a5ab2c01851d29c05f79cd2f262bb
@@ -70,7 +70,7 @@
Name: %{srcname}-epel
Summary: Media Sharing Server
Version: %{majorversion}.%{minorversion}.%{microversion}
-Release: %{baserelease}%{?snapdate:.%{snapdate}git%{shortcommit}}.1.1%{?dist}
+Release: %{baserelease}%{?snapdate:.%{snapdate}git%{shortcommit}}%{?dist}
License: MIT
URL: https://pipewire.org/
%if 0%{?snapdate}
@@ -940,6 +940,9 @@ systemctl --no-reload preset --global pipewire.socket >/dev/null 2>&1 || :
%endif
%changelog
+* Thu Sep 17 2026 Davide Cavalca <dcavalca@fedoraproject.org> - 1.4.11-3
+- Bump release to avoid issues on upgrades
+
* Wed Sep 16 2026 Davide Cavalca <dcavalca@fedoraproject.org> - 1.4.11-2.1.1
- Merge upstream changes for pipewire-epel
reply other threads:[~2026-09-17 17:12 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=178966516349.1.6210139238335239628.rpms-pipewire-epel-668f8bc42330@fedoraproject.org \
--to=dcavalca@fedoraproject.org \
--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