public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Adrian Reber <adrian@lisas.de>
To: git-commits@fedoraproject.org
Subject: [rpms/criu] f44: Always use nftables network locking backend
Date: Mon, 06 Jul 2026 05:55:06 GMT	[thread overview]
Message-ID: <178331730679.1.18271937910008553746.rpms-criu-259ac6c8e7e4@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/criu
Branch : f44
Commit : 259ac6c8e7e4f4862eaeeb1d768078b1b3b23adf
Author : Adrian Reber <adrian@lisas.de>
Date   : 2026-03-26T09:55:07+01:00
Stats  : +5/-2 in 1 file(s)
URL    : https://src.fedoraproject.org/rpms/criu/c/259ac6c8e7e4f4862eaeeb1d768078b1b3b23adf?branch=f44

Log:
Always use nftables network locking backend

---
diff --git a/criu.spec b/criu.spec
index ab8647c..7b770b1 100644
--- a/criu.spec
+++ b/criu.spec
@@ -13,7 +13,7 @@
 
 Name: criu
 Version: 4.2
-Release: 16%{?dist}
+Release: 17%{?dist}
 Summary: Tool for Checkpoint/Restore in User-space
 License: GPL-2.0-only AND LGPL-2.1-only AND MIT
 URL: http://criu.org/
@@ -42,11 +42,11 @@ BuildRequires: libselinux-devel
 BuildRequires: gnutls-devel
 BuildRequires: libdrm-devel
 BuildRequires: libuuid-devel
+BuildRequires: nftables-devel
 # Checkpointing containers with a tmpfs requires tar
 Recommends: tar
 %if 0%{?fedora}
 BuildRequires: libbsd-devel
-BuildRequires: nftables-devel
 %endif
 BuildRequires: make
 
@@ -206,6 +206,9 @@ rm -f $RPM_BUILD_ROOT%{_libdir}/libcriu.a
 %tmpfiles_create %{name}.conf
 
 %changelog
+* Thu Mar 26 2026 Adrian Reber <areber@redhat.com> - 4.2-17
+- Always use nftables network locking backend
+
 * Tue Mar 03 2026 Adrian Reber <areber@redhat.com> - 4.2-16
 - Fix tty compiler error (const qualifier warning)
 

                 reply	other threads:[~2026-07-06  5: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=178331730679.1.18271937910008553746.rpms-criu-259ac6c8e7e4@fedoraproject.org \
    --to=adrian@lisas.de \
    --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