From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Upgrading custom personal builds of ipfire
Date: Wed, 16 Mar 2022 10:21:11 +0000 [thread overview]
Message-ID: <F2182CCA-630B-46F6-A0F8-D6A2BFE3936D@ipfire.org> (raw)
In-Reply-To: <CAEUhsb5hmnBPBMG5pXh_VpcBh6vKBS02=wmqWgqwjf_YbqkMDw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]
Hello Ed,
And welcome to the list.
> On 15 Mar 2022, at 23:11, Ed Sweetman <cellsafemode(a)gmail.com> wrote:
>
> I've been looking for any kind of documentation on the ability to upgrade / test personal builds of ipfire and couldn't find any.
>
> I build a customized version of ipfire for personal use and obviously can't use the normal network upgrade but i dont see an option to point to a usb drive for a new build or anywhere other than the official servers. What is the preferred way to do this? Is there a way to upgrade offline without clean installing over or some way to set a personal build on a machine as a local repo mirror?
>
> Figure there's got to be a way to test the upgrade process locally..
>
> thanks for any help.
I am not entirely sure if I am getting it right what you are saying. If you:
a) Have a custom version with custom changes, installing any updates from our package repositories might overwrite those changes; or
b) You just want to upgrade to the latest testing version after having already installed a test version from the unstable or testing repository?
In case of a), the only way is to build your own updates that you host somewhere and you make sure you have all your own changes in your updates.
Does this help?
-Michael
parent reply other threads:[~2022-03-16 10:21 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAEUhsb5hmnBPBMG5pXh_VpcBh6vKBS02=wmqWgqwjf_YbqkMDw@mail.gmail.com>]
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=F2182CCA-630B-46F6-A0F8-D6A2BFE3936D@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