Bonjour LaLibreParole,
What would be the best solution to move from a 2.6.4 version
on an Ubuntu server deb package to a newer version (2.8 or
2.7.1 at worst) with the least risk for a production server
(and with the least downtime) ?
There's normally no risk of a "downtime" during the migration from 2.6.4
to 2.7.1 or 2.8.0 (at least in today's version). The news server should
be ready to use again after the installation of the new binaries. It
will just be stopped during the installation.
Have a look at "Upgrading from 2.6 to 2.7" in <
https://www.eyrie.org/~eagle/software/inn/docs/news.html> to see what
you need taking care of. Most of the changes are handled by the script
called during an upgrade (innupgrade).
You will probably want to set up Cancel-Lock in inn-secrets.conf; you
can do this after the upgrade (it is not necessary for the upgrade). A
mere restart of the news server is enough to take into account new
admin/user keys, once configured.
If you want to use the new ovsqlite overview method based on SQLite, a
downtime of a few minutes will be necessary during the overview rebuild.
It can also be done after the upgrade.
I see that Ubuntu currently has 2.7.1~20230131-1build1 packaged, which
is fine to use. You could upgrade to this version.
I am not aware of a ready-to-use package of 2.8.0. If you really want
it, you'll have to build INN from sources. (Using the same configure
flags as the ones of the Ubuntu package will facilitate the migration.)
--
Julien ÉLIE
« – Par Thor !
– Par Odin !
– Par exemple ! » (Astérix)
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)