public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Simone Caronni <negativo17@gmail.com>
To: git-commits@fedoraproject.org
Subject: [rpms/xevd] rawhide: Convert to %autorelease and %autochangelog
Date: Mon, 10 Aug 2026 14:29:07 GMT [thread overview]
Message-ID: <178637214703.1.12585353998806513879.rpms-xevd-ab1a8de140b2@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/xevd
Branch : rawhide
Commit : ab1a8de140b21d84037bd52eb65b8e131a480716
Author : Simone Caronni <negativo17@gmail.com>
Date : 2026-08-10T16:26:39+02:00
Stats : +26/-25 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/xevd/c/ab1a8de140b21d84037bd52eb65b8e131a480716?branch=rawhide
Log:
Convert to %autorelease and %autochangelog
[skip changelog]
---
diff --git a/changelog b/changelog
new file mode 100644
index 0000000..d4d4785
--- /dev/null
+++ b/changelog
@@ -0,0 +1,24 @@
+* Fri Jul 17 2026 Fedora Release Engineering <releng@fedoraproject.org> - 0.5.0-7
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_45_Mass_Rebuild
+
+* Sat Jan 17 2026 Fedora Release Engineering <releng@fedoraproject.org> - 0.5.0-6
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_44_Mass_Rebuild
+
+* Sun Aug 24 2025 Neal Gompa <ngompa@fedoraproject.org> - 0.5.0-5
+- Add patch to link libm properly
+- Drop pc file definition patch
+
+* Sun Aug 24 2025 Neal Gompa <ngompa@fedoraproject.org> - 0.5.0-4
+- Add patch to fix pc file definition
+
+* Fri Jul 25 2025 Fedora Release Engineering <releng@fedoraproject.org> - 0.5.0-3
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_43_Mass_Rebuild
+
+* Sat May 10 2025 Dominik Mierzejewski <dominik@greysector.net> - 0.5.0-2
+- fix build on non-x86
+
+* Sun Sep 29 2024 Neal Gompa <ngompa@fedoraproject.org> - 0.5.0-1
+- Updated to 0.5.0
+
+* Wed Oct 18 2023 Neal Gompa <ngompa@fedoraproject.org> - 0.4.1-1
+- Initial package
diff --git a/xevd.spec b/xevd.spec
index 5b79f6f..be95a2c 100644
--- a/xevd.spec
+++ b/xevd.spec
@@ -1,6 +1,6 @@
Name: xevd
Version: 0.5.0
-Release: 7%{?dist}
+Release: %autorelease
Summary: Reference MPEG-5 Part 1 (EVC) decoder
License: BSD-3-Clause
@@ -94,27 +94,4 @@ rm -rfv %{buildroot}%{_libdir}/%{name}*
%changelog
-* Fri Jul 17 2026 Fedora Release Engineering <releng@fedoraproject.org> - 0.5.0-7
-- Rebuilt for https://fedoraproject.org/wiki/Fedora_45_Mass_Rebuild
-
-* Sat Jan 17 2026 Fedora Release Engineering <releng@fedoraproject.org> - 0.5.0-6
-- Rebuilt for https://fedoraproject.org/wiki/Fedora_44_Mass_Rebuild
-
-* Sun Aug 24 2025 Neal Gompa <ngompa@fedoraproject.org> - 0.5.0-5
-- Add patch to link libm properly
-- Drop pc file definition patch
-
-* Sun Aug 24 2025 Neal Gompa <ngompa@fedoraproject.org> - 0.5.0-4
-- Add patch to fix pc file definition
-
-* Fri Jul 25 2025 Fedora Release Engineering <releng@fedoraproject.org> - 0.5.0-3
-- Rebuilt for https://fedoraproject.org/wiki/Fedora_43_Mass_Rebuild
-
-* Sat May 10 2025 Dominik Mierzejewski <dominik@greysector.net> - 0.5.0-2
-- fix build on non-x86
-
-* Sun Sep 29 2024 Neal Gompa <ngompa@fedoraproject.org> - 0.5.0-1
-- Updated to 0.5.0
-
-* Wed Oct 18 2023 Neal Gompa <ngompa@fedoraproject.org> - 0.4.1-1
-- Initial package
+%autochangelog
reply other threads:[~2026-08-10 14:29 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=178637214703.1.12585353998806513879.rpms-xevd-ab1a8de140b2@fedoraproject.org \
--to=negativo17@gmail.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