From mboxrd@z Thu Jan  1 00:00:00 1970
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Some delicate updates - how to do it the best way?
Date: Mon, 28 Mar 2016 23:39:29 +0200
Message-ID: <56F9A491.80904@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0480835002139802521=="
List-Id: <development.lists.ipfire.org>

--===============0480835002139802521==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit

Hi,

being curious, I prepared five updates for the following components
('iptables 1.6.0' came to my view and I just couldn't resist ;-) ):

iptables 1.6.0
ipset 6.29
conntrack-tools 1.4.3
libnetfilter_conntrack 1.05
xtables-addons 2.10

The question that bugs me:
What would be the best way to test whether these updates run together
well under the current 'Core 100' environment? And: is anything
important component missing!?

In the first, I created five "update"-packs (using the hint Michael once
gave me) by creating five tar.gz-archives, each one containing the
corresponding files for each version from '.../common/rootfiles/..."

The plan is to extract each package from root-directory on my
(online-)testmachine, run 'ldconfig' and reboot - I think this will be
necessary.

But although the whole compiling and build process (based on 'next',
Core 100) ran through without any serious errors, I'm not really sure if
this is the right way to test this.

Has anyone any hints how to test this the best way? I don't want to push
these updates and run into some nasty errors...

Best,
Matthias

--===============0480835002139802521==--