public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <56F9A491.80904@ipfire.org> (raw)

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

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

                 reply	other threads:[~2016-03-28 21:39 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=56F9A491.80904@ipfire.org \
    --to=matthias.fischer@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