public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Packit <hello@packit.dev>
To: git-commits@fedoraproject.org
Subject: [rpms/bootc] f44: Update to 1.16.11 upstream release
Date: Thu, 03 Sep 2026 18:55:13 GMT [thread overview]
Message-ID: <178846171382.1.10331011556309692021.rpms-bootc-3da9d1243ba3@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/bootc
Branch : f44
Commit : 3da9d1243ba339c9c851873cf6cc34be81a2ec27
Author : Packit <hello@packit.dev>
Date : 2026-09-03T13:30:25+00:00
Stats : +8/-3 in 3 file(s)
URL : https://src.fedoraproject.org/rpms/bootc/c/3da9d1243ba339c9c851873cf6cc34be81a2ec27?branch=f44
Log:
Update to 1.16.11 upstream release
Upstream tag: v1.16.11
Upstream commit: add7a909
Commit authored by Packit automation (https://packit.dev/)
---
diff --git a/.gitignore b/.gitignore
index 0a77566..40c435f 100644
--- a/.gitignore
+++ b/.gitignore
@@ -100,3 +100,5 @@
/bootc-1.16.9-vendor.tar.zstd
/bootc-1.16.10.tar.zstd
/bootc-1.16.10-vendor.tar.zstd
+/bootc-1.16.11.tar.zstd
+/bootc-1.16.11-vendor.tar.zstd
diff --git a/bootc.spec b/bootc.spec
index 4f3f98c..2209193 100644
--- a/bootc.spec
+++ b/bootc.spec
@@ -23,7 +23,7 @@
Name: bootc
# Ensure this local build overrides anything else.
-Version: 1.16.10
+Version: 1.16.11
Release: %{autorelease}
Summary: Bootable container system
@@ -44,6 +44,9 @@ Source1: %{url}/releases/download/v%{version}/bootc-%{version}-vendor.tar
ExcludeArch: %{ix86}
BuildRequires: libzstd-devel
+# selinux-sys generates libselinux bindings with bindgen at build time.
+# bindgen requires libclang.
+BuildRequires: clang-devel
BuildRequires: make
BuildRequires: ostree-devel
BuildRequires: openssl-devel
diff --git a/sources b/sources
index 42bc666..fff4e30 100644
--- a/sources
+++ b/sources
@@ -1,2 +1,2 @@
-SHA512 (bootc-1.16.10.tar.zstd) = 9ede03ec8d24d359a69a2522cf0658eefb4273a2b611558c5d672a235bce49cdadf9c0908fda79c756ccf6e6ef37dff9a758a03e75fdc8a9528120e437cbb522
-SHA512 (bootc-1.16.10-vendor.tar.zstd) = 6f89c84581d9332e2c407995e63ce561b626ed02d3507840b5272d4261277f634f81dd051a4f4c47e19d1f1e8cc90e1281600e9eb5c21523882970020ea14d46
+SHA512 (bootc-1.16.11.tar.zstd) = a775b1dad14c76d1d9a6bd01f27558f78717267aefe75eb333e7a6fc8e1ec00fd46f97cd216201313b436745459408c55bab6707d6a9ec7e002bba0d35aa0a33
+SHA512 (bootc-1.16.11-vendor.tar.zstd) = 64118f8939f5ca428189aec286b445e0b833949700ca7e378794d7c09fd179e4ff15a86184aca345ea32dcc96ddf1848efffa0aa878aa061ddde8f41aabb7bcd
reply other threads:[~2026-09-03 18:55 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=178846171382.1.10331011556309692021.rpms-bootc-3da9d1243ba3@fedoraproject.org \
--to=hello@packit.dev \
--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