Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#20823 - [dovecot]
Attached to Project:
Arch Linux
Opened by Dieter Plaetinck (Dieter_be) - Sunday, 12 September 2010, 10:53 GMT
Last edited by Andreas Radke (AndyRTR) - Sunday, 12 September 2010, 15:02 GMT
Opened by Dieter Plaetinck (Dieter_be) - Sunday, 12 September 2010, 10:53 GMT
Last edited by Andreas Radke (AndyRTR) - Sunday, 12 September 2010, 15:02 GMT
|
Details[root@dieter-p4sci-arch ~]# pacman -Qi dovecot | grep Version
Version : 1.2.13-1 [root@dieter-p4sci-arch ~]# pacman -Sy dovecot (...) Targets (1): dovecot-2.0.2-1 (...) (1/1) checking for file conflicts [#######################################################################################################] 100% error: failed to commit transaction (conflicting files) dovecot: /etc/dovecot/dovecot.conf exists in filesystem Errors occurred, no packages were upgraded. [root@dieter-p4sci-arch ~]# This isn't normal right? Why doesn't the usual pacnew file creation happen? |
This task depends upon
Closed by Andreas Radke (AndyRTR)
Sunday, 12 September 2010, 15:02 GMT
Reason for closing: Not a bug
Sunday, 12 September 2010, 15:02 GMT
Reason for closing: Not a bug
Comment by Andreas Radke (AndyRTR) -
Sunday, 12 September 2010, 15:02 GMT
The old dovecot.conf file was created by yourself. It's not under pacman control. New version now ships a default dovecot.conf file and will take it under pacman control. It's safe to -Sf dovecot.