public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Nicolas Chauvet <kwizart@gmail.com>
To: git-commits@fedoraproject.org
Subject: [rpms/nv-codec-headers] epel10: Merge remote-tracking branch 'origin/f44' into epel10
Date: Wed, 22 Jul 2026 19:02:55 GMT [thread overview]
Message-ID: <178474697507.1.1294509717152516686.rpms-nv-codec-headers-f83ffa700013@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/nv-codec-headers
Branch : epel10
Commit : f83ffa700013dab4c3d0a9b23b8910feb875a1dc
Author : Nicolas Chauvet <kwizart@gmail.com>
Date : 2026-07-22T21:02:29+02:00
Stats : +17/-2 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/nv-codec-headers/c/f83ffa700013dab4c3d0a9b23b8910feb875a1dc?branch=epel10
Log:
Merge remote-tracking branch 'origin/f44' into epel10
---
diff --git a/nv-codec-headers.spec b/nv-codec-headers.spec
index 3a066c7..c6259af 100644
--- a/nv-codec-headers.spec
+++ b/nv-codec-headers.spec
@@ -1,5 +1,5 @@
Name: nv-codec-headers
-Version: 12.2.72.0
+Version: 13.0.19.1
Release: 1%{?dist}
Summary: FFmpeg version of Nvidia Codec SDK headers
License: MIT
@@ -38,6 +38,21 @@ sed -i '1,22s/^.\{,3\}//' LICENSE
%changelog
+* Wed Jul 22 2026 Nicolas Chauvet <kwizart@gmail.com> - 13.0.19.1-1
+- Update to 13.0.19.1
+
+* Fri Jan 16 2026 Fedora Release Engineering <releng@fedoraproject.org> - 13.0.19.0-3
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_44_Mass_Rebuild
+
+* Thu Jul 24 2025 Fedora Release Engineering <releng@fedoraproject.org> - 13.0.19.0-2
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_43_Mass_Rebuild
+
+* Tue Mar 18 2025 Leigh Scott <leigh123linux@gmail.com> - 13.0.19.0-1
+- Update to 13.0.19.0
+
+* Fri Jan 17 2025 Fedora Release Engineering <releng@fedoraproject.org> - 12.2.72.0-2
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_42_Mass_Rebuild
+
* Fri Sep 20 2024 Nicolas Chauvet <kwizart@gmail.com> - 12.2.72.0-1
- Update to 12.2.72.0
diff --git a/sources b/sources
index 19b7781..3736bb8 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (nv-codec-headers-n12.2.72.0.tar.gz) = dd2f1c7ff54890016ab17500449620cdf3690aa1d34dec78f1b27bdc0d51ec1335a66fda5942ddb43e1a1310de95874aef5232a1e676c21882fae08472d17808
+SHA512 (nv-codec-headers-n13.0.19.1.tar.gz) = df307c6e5b96b77c5bd0d0f6e3a1a85513d2b728e3060084a3ff205d36617e00b0fa1b60ee6568be62e811cfa45cbbbda369f0873be7d6d2d73d41e89f24c5b4
reply other threads:[~2026-07-22 19:02 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=178474697507.1.1294509717152516686.rpms-nv-codec-headers-f83ffa700013@fedoraproject.org \
--to=kwizart@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