----------------------------------------------------------------------------------
@MSGID: <op.1815w4laa3w0dxdave@hodgins.homeip.net>
cc773f50
@REPLY: 1@dont-email.me> 5aa0a91a
@REPLYADDR David W. Hodgins
<dwhodgins@nomail.afraid.org>
@REPLYTO 2:5075/128 David W. Hodgins
@CHRS: CP866 2
@RFC: 1 0
@RFC-Message-ID:
<op.1815w4laa3w0dxdave@hodgins.homeip.net>
@RFC-References: 1@dont-email.me>
1@dont-email.me> 1@dont-email.me> 1@dont-email.me>
1@dont-email.me>
@TZUTC: -0400
@PID: Opera Mail/12.16 (Linux)
@TID: FIDOGATE-5.12-ge4e8b94
On Wed, 02 Aug 2023 05:15:40 -0400, Markus Robert Kessler
<
no_reply@dipl-ing-kessler.de> wrote:
> nice to know.
I`m expecting it to be before the end of the month at the latest. I`m the
leader of the qa team.
> Well, whenever a security-related bug is found, I go and get the source
> of the new, bugfixed version. But as said, doing so, including building
> all packages which this one is depending on, is very time consuming and
> the effort goes through the roof. Sooner or later this won`t work anymore.
That`s a lot of work. :-)
> So, what about installing MGA9 Cauldron now, and use it as MGA9 stable
> when it is released?
> At least the repo definitions have to be updated, since during
> development in Cauldron there is no `update` repo. Right?
> All stuff seems to be in one place.
> Someone already tried this with MGA9 / Cauldron, or any former version?
It should work. Once m9 is released, existing cauldron installs should
automatically become m9 installs through an update, though I`ve forgotten
the details of how that works. I don`t remember if the repos must be manually
removed/re-added or if that`s automatic. Pretty sure it`s automatic, and
packagers must alter their configurations to continue with using cauldron
when a new cauldron repo is forked.
There will be very few changes between now and when m9 is released unless
something major and unexpected happens.
Regards, Dave Hodgins
--- Opera Mail/12.16 (Linux)
* Origin: A noiseless patient Spider (2:5075/128)
SEEN-BY: 5001/100 5005/49 5015/255 5019/40 5020/715
848 1042 4441 12000
SEEN-BY: 5030/49 1081 5075/128
@PATH: 5075/128 5020/1042 4441