public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core 128 => 129 - iptables not shipped?
Date: Mon, 09 Sep 2019 10:56:17 +0100	[thread overview]
Message-ID: <6FD7330C-0145-41F6-8155-8D3F63DD67D9@ipfire.org> (raw)
In-Reply-To: <24c70849-0bc9-e3ad-9ee2-d8d28a4f726d@ipfire.org>

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

Yeah, it looks like I forgot this one.

Unfortunately that happens very often because I am just stupid.

Arne will merge the next update and so users will received that one :)

Best,
-Michael

> On 8 Sep 2019, at 18:10, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
> 
> Hi,
> 
> In Core update 128 => Core 129 the 'iptables'-udpdate from 1.6.2 to
> 1.8.2 is missing:
> 
> https://git.ipfire.org/?p=ipfire-2.x.git;a=tree;f=config/rootfiles/core/129/filelists;h=eeb0842b426fcd48228a08cd1e3e808fff86a186;hb=refs/heads/core129
> 
> The former update from 1.4.21 (Core 122 => Core 123) to 1.6.2 was ok:
> 
> https://git.ipfire.org/?p=ipfire-2.x.git;a=tree;f=config/rootfiles/core/123/filelists;h=acaca6cf1f3c2218f72cb7e9bdbaf1d34035c23c;hb=refs/heads/core123
> 
> This would mean that machines, which were updated through Pakfire from
> Core 128 to Core 129 didn't get this update. So did mine. Found per
> chance today.
> 
> Can someone confirm?
> 
> Best,
> Matthias


      reply	other threads:[~2019-09-09  9:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-08 17:10 Matthias Fischer
2019-09-09  9:56 ` Michael Tremer [this message]

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=6FD7330C-0145-41F6-8155-8D3F63DD67D9@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.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