Authentic theme files are missing

Hi,

There is nothing to worry about. When you update part of the package manually (Authentic Theme), you would get such errors.

Please let me explain it once more.

In case you update Authentic Theme after RPM package was installed using theme update mechanism or some other way, you overwrite original package content. When you upgrade your RPM with newer version, installer lets you know, that previous package files were changes manually.

To avoid this error don't update the theme outside of package installer.

Ilia's explanation is correct but maybe worth expanding on.

It's always true that installing over something that was initially installed by the package manager can lead to mismatches between what the package manager thinks is on the filesystem and what is actually on the file system. But, it's also true that this particular set of changes is huge relatively speaking and hopefully won't happen often.

Authentic had a major overhaul recently, which re-organized and re-bundled a bunch of files...making a lot of old files go away. That sort of thing shouldn't happen frequently...and thus it's unlikely that there will be this kind of mismatch in the future, even if the system has had the installed theme replaced outside of a Webmin update.

In the past, when we first started shipping Authentic for Virtualmin users, I'd insisted that Authentic theme hide theme update options so this wouldn't happen (we insisted on updates only happening in packages), but people really wanted to be able to follow the updates, because Authentic is progressing so quickly, so Ilia added the update options back in.

So, the decision to include Authentic as the default them in Webmin, but also to make it easy to replace the Authentic theme outside of a Webmin package upgrade, has led us here. I'm not sure how to solve this without removing the ability for users to upgrade the theme (and requiring them updates wait until the next Webmin update to roll out). Separating it back out into a separate package wouldn't be popular with Jamie, as he likes Webmin to be one self-contained unit that someone can download and have working in seconds, so that would be the obvious but untenable answer.

We can't (AFAIK) suppress those complaints from the package manager (and probably wouldn't want to, as errors during package install may be valuable).

We can encourage Ilia to avoid changes that lead to files disappearing (maybe leaving behind a dummy file until after the next major Webmin release, if reorganizations have to happen again). I don't want to do anything that would slow Ilia down, however. The theme was massively improved, in terms of performance, by the most recent overhaul.

Thank you, Joe for making it clearer.

Those are warnings and should be treated as warnings. They are made to inform you, that the package was changed.

@yngens Please don't worry about those warnings, there is nothing bad happening.

After upgrading to Webmin 1.870 with Authentic 19.04, everything is working, right?

Depending on the system set-up, warnings could appear potentially anywhere.

Most of the time it's harmless. It's warning not error.

Sometimes warnings could be very useful, for instance, just recently, I was reinstalling my system and some node packages. I used to have this package installed separately, but in some time, it became the part of the main distro and no longer need.

Here is an example:

[root@toor ~]# npm install -g babel-plugin-remove-comments
npm WARN deprecated babel-plugin-remove-comments@2.0.0: [DEPRECATED] Use comments: false in your Babel config
+ babel-plugin-remove-comments@2.0.0
added 1 package in 0.643s
[root@toor ~]# npm remove -g babel-plugin-remove-comments
removed 1 package in 0.053s