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#63702 - bleachbit 2.2-2 /usr/share/bleachbit/*.pyc exists in filesystem
Attached to Project:
Community Packages
Opened by bill-auger (bill-auger) - Monday, 09 September 2019, 13:45 GMT
Last edited by Antonio Rojas (arojas) - Monday, 09 September 2019, 13:53 GMT
Opened by bill-auger (bill-auger) - Monday, 09 September 2019, 13:45 GMT
Last edited by Antonio Rojas (arojas) - Monday, 09 September 2019, 13:53 GMT
|
Detailsif the bleachbit 2.2-1 has ever been run as su, that creates several new un-owned .pyc files in /usr/share/bleachbit/ - those files all have owned counterparts in /usr/share/bleachbit/__pycache__ as: *.cpython-37.pyc
when upgrading to bleachbit 2.2-2, that will attempt to install those same previously un-owned files (now owned by bleachbit 2.2-2) and so install fails - bleachbit 2.2-2 does not install any files to /usr/share/bleachbit/__pycache__; but it installs corresponding *.pyo files that have no counterparts in bleachbit 2.2-1 special note that this is not reproducible unless that program has been run as su; but upgrade will be blocked for any user who has done so, unless they run: # sudo rm -rf /usr/share/bleachbit |
This task depends upon
Closed by Antonio Rojas (arojas)
Monday, 09 September 2019, 13:53 GMT
Reason for closing: Not a bug
Additional comments about closing: Nothing that can be fixed in packaging, affected users will have to overwrite the files
Monday, 09 September 2019, 13:53 GMT
Reason for closing: Not a bug
Additional comments about closing: Nothing that can be fixed in packaging, affected users will have to overwrite the files
bleachbit-2.2.1-tree