These forums are locked and archived, but all topics have been migrated to the new forum. You can search for this topic on the new forum: Search for Dovecot Update? on the new forum.
This website is deprecated, and remains online only for historic access to old issues and docs for historic versions of Virtualmin. It has been unmaintained for several years, and should not be relied on for up-to-date information. Please visit www.virtualmin.com instead.
[code:1]
yum list dovecot*
Error accessing file for config file://///etc/yum.repos.d/virtualmin.repo
Setting up repositories
Reading repository metadata in from local files
Installed Packages
dovecot.i386 1.0-1.3.rc15.el4.vm installed
Available Packages
dovecot.i386 0.99.11-8.EL4 base
[/code:1]
As i cant edit the post, The code above is not as root user. The next is:
[code:1]yum list dovecot*
Setting up repositories
Reading repository metadata in from local files
Installed Packages
dovecot.i386 1.0-1.3.rc15.el4.vm installed
[/code:1]
You're running the latest version, so no need to actually upgrade. I'm not sure why the Package Updates module would want to tell you about it in that way, though. ;-)
Sounds like maybe a bug in the Virtualmin Package Updates version detection code.
What do you get if you run:
yum list dovecot*
From the command line?
--
Check out the forum guidelines!
[code:1]
yum list dovecot*
Error accessing file for config file://///etc/yum.repos.d/virtualmin.repo
Setting up repositories
Reading repository metadata in from local files
Installed Packages
dovecot.i386 1.0-1.3.rc15.el4.vm installed
Available Packages
dovecot.i386 0.99.11-8.EL4 base
[/code:1]
As i cant edit the post, The code above is not as root user. The next is:
[code:1]yum list dovecot*
Setting up repositories
Reading repository metadata in from local files
Installed Packages
dovecot.i386 1.0-1.3.rc15.el4.vm installed
[/code:1]
You're running the latest version, so no need to actually upgrade. I'm not sure why the Package Updates module would want to tell you about it in that way, though. ;-)
I'll see if I can reproduce this problem here.
--
Check out the forum guidelines!