INNUPGRADE(8)

πŸ’… INNUPGRADE(8) β€” the glow-up page for your config files ✨

okay so this is innupgrade, straight out of the InterNetNews docs, and honestly bestie it's the little cleanup fairy of your INN install 🧚


✨ NAME ✨

innupgrade β€” upgrades your INN configuration files so they don't live in the past πŸ’–


🌸 SYNOPSIS 🌸

innupgrade directory

innupgrade [-t type] -f file

πŸ¦‹ DESCRIPTION πŸ¦‹

So innupgrade is literally designed to be run during a major upgrade of INN, and its whole job is to fix your configuration files with whatever changes the new version needs. Think of it as your config's personal stylist πŸ’…

If you hand it a directory, it scans that directory for any files it has update rules defined for, tries to apply those updates, and then replaces the files with the updated versions β€” but only if applying the updates actually resulted in changes. And because it's not reckless, the old versions get saved with a .OLD extension πŸŽ€

If you use the -f flag instead, only that one file gets updated. And if the file name doesn't match the standard file name of an INN configuration file, you can pass the optional -t flag to tell it the type. There's an example of this down in EXAMPLES, iykyk πŸ‘‘

Currently (as in, right now, today), innupgrade knows how to apply the following updates:

πŸ“₯ incoming.conf

  • Rename nolist and noresendid to respectively list and resendid. Invert the related boolean values (since INN 2.7).
  • Comment out the removed comment and email parameters (since INN 2.7).

βš™οΈ inn.conf

  • Quote values that contain whitespace and comment out keys with no values β€” this is required for the change in configuration parsers introduced in INN 2.4. Heads up tho: the new format is not backward compatible with the previous parser, because the previous parser will include the double-quotes in the value of the parameter 😭
  • Add the hismethod parameter if it's not found (introduced in INN 2.4, with the default value hisv6).
  • Rename nntpactsync to incominglogfrequency (since INN 2.5). Rename addnntppostingdate and addnntppostinghost to respectively addinjectiondate and addinjectionpostinghost (since INN 2.6).
  • Remove the refusecybercancels and verifycancels parameters (since INN 2.7).
  • If the overview.fmt file exists, its content is merged into the extraoverviewadvertised and extraoverviewhidden parameters introduced in INN 2.5. The file is then renamed to overview.fmt.OLD.
  • If the sasl.conf file exists, its content is merged into the tlscapath, tlscafile, tlscertfile and tlskeyfile parameters introduced in INN 2.5. The file is then renamed to sasl.conf.OLD.

πŸ” inn-secrets.conf

  • Create a non-world-readable inn-secrets.conf file in pathetc, if it's not already existing (new in INN 2.7).

πŸ“° newsfeeds

  • Replace the use of startinnfeed with the appropriate direct invocation of innfeed or imapfeed (startinnfeed was removed in INN 2.5).
  • Replace the use of filechan with buffchan in unbuffered mode (filechan was removed in INN 2.7).

πŸ‘€ readers.conf

  • Rename require_ssl to require_encryption (since INN 2.7).

A few obsolete programs or configuration files get renamed with a .OLD extension by innupgrade. Obsolete man pages are directly removed β€” no .OLD for those, they just go πŸ’€

Normally, innupgrade should be run at least on the pathetc directory after any upgrade of INN other than a patch release (so: any upgrade that changes the first or second version numbers). And fr fr, this may occur automatically during the upgrade process, so don't be shocked if it already ran without asking 🌈


πŸŽ€ OPTIONS πŸŽ€

  • -f file β€” only act on file instead of working on an entire directory. One file, one mission 🫢
  • -t type β€” for a file specified with -f, parse it and upgrade it as if it were named type. Used for upgrading files with the same syntax as normal INN configuration files but with different names. Only makes sense in combination with -f β€” like, it's not a solo act, it needs its bestie ✨

🌟 EXAMPLES 🌟

Upgrade any configuration files found in pathetc and append a .OLD extension to obsolete files in pathetc:

innupgrade <pathetc in inn.conf>

Upgrade only /news/etc/inn.conf:

innupgrade -f /news/etc/inn.conf

Upgrade a file named inn-special.conf that should have the same syntax as inn.conf:

innupgrade -t inn.conf -f inn-special.conf

And just so we're clear: any upgrade rules that apply to inn.conf will be applied to the alternate file. Same rules, different name, iconic behavior πŸ‘‘


πŸ“œ HISTORY πŸ“œ

Written by Russ Allbery <eagle@eyrie.org> for InterNetNews. We stan a legend πŸ’œ


πŸ”— SEE ALSO πŸ”—

incoming.conf(5), inn.conf(5), inn-secrets.conf(5), newsfeeds(5), readers.conf(5).


okay that's the whole page!! πŸ“ this edition is INN 2.7.4, dated 2022-07-10, and it's the INNUPGRADE(8) page β€” go forth and let the tool handle the config drama, bestie, you've got this πŸ’–βœ¨

πŸ“¦ where this page comes from
  • arch rolling: inn 2.7.4-4 Β· ISC
  • epel 10: inn 2.7.4-5.el10_3 Β· ISC AND BSD-3-Clause AND BSD-4-Clause AND FSFAP AND (GPL-1.0-or-later OR Artistic-1.0-Perl) AND GPL-3.0-or-later WITH Bison-exception-2.2 AND LicenseRef-Fedora-Public-Domain AND MIT AND NTP
  • πŸ’– girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms