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#71375 - [certbot]
Attached to Project:
Community Packages
Opened by Randy Fin (oversla) - Sunday, 27 June 2021, 21:38 GMT
Last edited by Eli Schwartz (eschwartz) - Monday, 28 June 2021, 21:33 GMT
Opened by Randy Fin (oversla) - Sunday, 27 June 2021, 21:38 GMT
Last edited by Eli Schwartz (eschwartz) - Monday, 28 June 2021, 21:33 GMT
|
DetailsBecause /etc/letsencrypt is listed in the package contents, you can't install certbot when the files already exist, such as when you're using files you backed up earlier. You get an error "failed to commit transaction (conflicting files)". It should be possible to back up /etc/letsencrypt, copy it to a new computer, then install certbot and have it use those files. There's no good reason for it to fail installation just because files exist. certbot is perfectly capable of using an existing /etc/letsencrypt directory.
|
This task depends upon
This is completely false and the bug report makes no sense. The only "file" in the package within /etc is a directory. Directories are not checked for file conflicts, and if they were then Arch would be in major trouble due to conflicts on e.g. /usr/bin /usr/lib in 99% of packages.