public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Tom spot Callaway <spotaws@amazon.com>
To: git-commits@fedoraproject.org
Subject: [rpms/libvpx] f45: 1.17.0
Date: Thu, 27 Aug 2026 14:00:05 GMT [thread overview]
Message-ID: <178783920534.1.6326472548117773962.rpms-libvpx-fb9233329b40@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/libvpx
Branch : f45
Commit : fb9233329b40649626d24713e2eab6ef50926429
Author : Tom spot Callaway <spotaws@amazon.com>
Date : 2026-08-27T09:59:16-04:00
Stats : +5/-17 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/libvpx/c/fb9233329b40649626d24713e2eab6ef50926429?branch=f45
Log:
1.17.0
---
diff --git a/libvpx-1.7.0-leave-fortify-source-on.patch b/libvpx-1.7.0-leave-fortify-source-on.patch
deleted file mode 100644
index 23099da..0000000
--- a/libvpx-1.7.0-leave-fortify-source-on.patch
+++ /dev/null
@@ -1,12 +0,0 @@
-diff -up libvpx-1.7.0/build/make/configure.sh.leave-fs-on libvpx-1.7.0/build/make/configure.sh
---- libvpx-1.7.0/build/make/configure.sh.leave-fs-on 2018-01-26 15:02:18.767645332 -0500
-+++ libvpx-1.7.0/build/make/configure.sh 2018-01-26 15:02:28.594420775 -0500
-@@ -1440,7 +1440,7 @@ EOF
-
- # Work around longjmp interception on glibc >= 2.11, to improve binary
- # compatibility. See http://code.google.com/p/webm/issues/detail?id=166
-- enabled linux && check_add_cflags -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=0
-+ # enabled linux && check_add_cflags -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=0
-
- # Check for strip utility variant
- ${STRIP} -V 2>/dev/null | grep GNU >/dev/null && enable_feature gnu_strip
diff --git a/libvpx.spec b/libvpx.spec
index 85265a3..65151d3 100644
--- a/libvpx.spec
+++ b/libvpx.spec
@@ -5,16 +5,14 @@
Name: libvpx
Summary: VP8/VP9 Video Codec SDK
-Version: 1.16.0
-Release: 3%{?dist}
+Version: 1.17.0
+Release: 1%{?dist}
License: BSD-3-Clause
URL: http://www.webmproject.org/code/
Source0: https://github.com/webmproject/libvpx/archive/v%{version}.tar.gz
Source1: vpx_config.h
# Thanks to debian.
Source2: libvpx.ver
-# Do not disable FORTIFY_SOURCE=2
-Patch0: libvpx-1.7.0-leave-fortify-source-on.patch
BuildRequires: gcc
BuildRequires: gcc-c++
BuildRequires: make
@@ -46,7 +44,6 @@ and decoder.
%prep
%setup -q -n libvpx-%{version}
-%patch -P0 -p1 -b .fortify-source-on
%build
@@ -202,6 +199,9 @@ rm -rf %{buildroot}%{_prefix}/src
%{_bindir}/*
%changelog
+* Thu Aug 27 2026 Tom Callaway <spot@fedoraproject.org> - 1.17.0-1
+- update to 1.17.0
+
* Thu Jul 16 2026 Fedora Release Engineering <releng@fedoraproject.org> - 1.16.0-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_45_Mass_Rebuild
next reply other threads:[~2026-08-27 14:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 14:00 Tom spot Callaway [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-08-27 14:00 [rpms/libvpx] f45: 1.17.0 Tom spot Callaway
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=178783920534.1.6326472548117773962.rpms-libvpx-fb9233329b40@fedoraproject.org \
--to=spotaws@amazon.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