languages.conf file

[Glenn Steen]

On 05/12/06, Rodney Green <rgreen at trayerproducts.com> wrote:
> I don't know if there was a .rpmnew file for the languages file. I
> copied the backup languages.conf file that I manually copied before even
> running install.sh into /etc/MailScanner/reports/en. That is the file
> I'm currently using and is the only languages.conf file I have to use. I
> don't have a languages.old or languages.new.
>
> Glenn Steen wrote:
(snip)
> > (I'll have to confess that I haven't done the latest upgrade yet...
> > will do one tomorrow though:-)
> >
> > Did the update create a languages.conf.rpmnew? If not, what are you
> > doing running the upgrade script then? As mentioned by others (Ken was
> > it?), if you just cut'n'paste the commands.... you have the old one as
> > a .old file... and can just move it back into place.
> >
> > As said, will know more about this come morning.

Ok.

If you have the old MailScanenr and the new package... and a spare
box... You could just make a mock install of the old one, then perform
a mock upgrade... If that creates a .rpmnew file, then you can run the
upgrade script on that and copy it into the real server... should work
nicely:-).
Or just make a mock install of the new one (if you haven't changed
anything in languages.conf, this is what I'd do:-)... should give you
a file with the "missing strings/variables" set.

If that seems onerous, you could alwayslook at/add any missing string
definitions...
Close to the end of the file you should have something like:
# Used in SpamAssassin cache results headers
cached = cached
notcached = not cached

HtH
-- 
-- Glenn
email: glenn < dot > steen < at > gmail < dot > com
work: glenn < dot > steen < at > ap1 < dot > se