netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Sowden <jeremy@azazel.net>
To: Arturo Borrero Gonzalez <arturo@debian.org>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
	netfilter-devel@vger.kernel.org, fw@strlen.de, phil@nwl.cc
Subject: Re: [RFC] nftables 1.0.6 -stable backports
Date: Mon, 9 Oct 2023 12:44:49 +0100	[thread overview]
Message-ID: <20231009114449.GA1135389@celephais.dreamlands> (raw)
In-Reply-To: <e11f0179-6738-4b6f-8238-585fffad9a57@debian.org>

[-- Attachment #1: Type: text/plain, Size: 761 bytes --]

On 2023-10-09, at 13:05:32 +0200, Arturo Borrero Gonzalez wrote:
> On 10/9/23 12:44, Pablo Neira Ayuso wrote:
> > - Another possibility is to make a nftables 1.0.6.1 or 1.0.6a -stable
> > release from netfilter.org. netfilter.org did not follow this procedure
> > very often (a few cases in the past in iptables IIRC).
> 
> Given the amount of patches, this would be the preferred method from the
> Debian point of view.

Agreed.

J.

> 1.0.6.1 as version should be fine.
> 
> Please note the Debian Stable (1.0.6) package already includes some patches
> [0], so I strongly suggest this new 1.0.6.1 contains them as well.
> 
> regards.
> 
> [0] https://salsa.debian.org/pkg-netfilter-team/pkg-nftables/-/tree/debian/bookworm/debian/patches

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2023-10-09 11:44 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-09 10:44 [RFC] nftables 1.0.6 -stable backports Pablo Neira Ayuso
2023-10-09 10:50 ` Florian Westphal
2023-10-09 11:05 ` Arturo Borrero Gonzalez
2023-10-09 11:15   ` Florian Westphal
2023-10-09 11:41     ` Pablo Neira Ayuso
2023-10-10  8:39       ` Phil Sutter
2023-10-10 10:37         ` Pablo Neira Ayuso
2023-10-10 13:30           ` Phil Sutter
2023-10-10 11:53         ` Jan Engelhardt
2023-10-10 15:24         ` Arturo Borrero Gonzalez
2023-10-09 11:44   ` Jeremy Sowden [this message]
2023-10-09 11:36 ` [RFC] nftables 0.9.8 " Pablo Neira Ayuso
2023-10-09 11:50   ` Jeremy Sowden
2023-10-10  8:54   ` Pablo Neira Ayuso
2023-10-10 20:08     ` Jeremy Sowden
2023-10-10 22:21       ` Pablo Neira Ayuso
2023-10-11  9:46         ` Jeremy Sowden
2023-10-11 10:01           ` Pablo Neira Ayuso
2024-02-17 20:11   ` Jeremy Sowden
2024-02-18 13:56     ` Jeremy Sowden
2023-10-11  8:01 ` [RFC] nftables 1.0.6 " Pablo Neira Ayuso
2023-10-11 15:25   ` Phil Sutter
2023-10-11 15:49     ` Pablo Neira Ayuso
2023-10-19 14:27       ` Pablo Neira Ayuso
2023-10-19 15:23         ` Phil Sutter
2023-11-02 11:34           ` Pablo Neira Ayuso
2023-11-02 12:27             ` Phil Sutter
2023-11-02 21:23               ` Pablo Neira Ayuso
2023-11-03  9:59                 ` Phil Sutter
2023-11-03 10:44                   ` Phil Sutter
2023-11-03 10:49                     ` Pablo Neira Ayuso
2023-11-03 10:56                       ` Phil Sutter
2023-11-03 11:29                         ` Pablo Neira Ayuso
2023-11-03 12:11                           ` Pablo Neira Ayuso
2023-11-03 15:02                           ` Phil Sutter
2023-11-03 15:15                             ` Pablo Neira Ayuso

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=20231009114449.GA1135389@celephais.dreamlands \
    --to=jeremy@azazel.net \
    --cc=arturo@debian.org \
    --cc=fw@strlen.de \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=pablo@netfilter.org \
    --cc=phil@nwl.cc \
    /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;
as well as URLs for NNTP newsgroup(s).