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#63107 - [vsftpd] pam config not listed in backup array
Attached to Project:
Community Packages
Opened by Julian Brost (julian) - Friday, 05 July 2019, 15:41 GMT
Last edited by Balló György (City-busz) - Sunday, 01 September 2019, 08:21 GMT
Opened by Julian Brost (julian) - Friday, 05 July 2019, 15:41 GMT
Last edited by Balló György (City-busz) - Sunday, 01 September 2019, 08:21 GMT
|
DetailsDescription:
Version 3.0.3-5 of the vsftpd package added a PAM configuration file at /etc/pam.d/vsftpd which is not listed in the backup array in the PKGBUILD. Upgrading the package from earlier versions results in the following error message if one already had a PAM config there: error: failed to commit transaction (conflicting files) vsftpd: /etc/pam.d/vsftpd exists in filesystem Also, my custom config would now be overwritten by package upgrades. Additional info: * package version(s): 3.0.3-5 and later Steps to reproduce: * Create a custom PAM config for vsftpd at /etc/pam.d/vsftpd * Upgrade from a earlier version to 3.0.3-5 or later (this will break) * Reinstall the package (this will delete the custom config) |
This task depends upon

This is an automated comment as this bug is open for more then 2 years. Please reply if you still experience this bug otherwise this issue will be closed after 1 month.