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#29764 - [ranger] *.pyo file conflicts on update
Attached to Project:
Community Packages
Opened by Michishige Kaito (mkaito) - Saturday, 05 May 2012, 15:08 GMT
Last edited by Jakob Gruber (schuay) - Sunday, 06 May 2012, 12:24 GMT
Opened by Michishige Kaito (mkaito) - Saturday, 05 May 2012, 15:08 GMT
Last edited by Jakob Gruber (schuay) - Sunday, 06 May 2012, 12:24 GMT
|
DetailsDescription:
The package upgrade doesn't account for generated *.pyo files, and complains about conflicts: Steps to reproduce: Have an older version of ranger installed. Attempt to upgrade with pacman. |
This task depends upon
Comment by Jakob Gruber (schuay) -
Sunday, 06 May 2012, 12:22 GMT
The previous .pyo files were generated by running ranger as root. It is safe to --force this upgrade: 'pacman -Sf ranger'
ranger_conflicts.txt