Arch Linux

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!
Tasklist

FS#38086 - [gcc] Leaves zombie files/dirs on upgrade

Attached to Project: Arch Linux
Opened by Doug Newgard (Scimmia) - Monday, 09 December 2013, 22:34 GMT
Last edited by Allan McRae (Allan) - Friday, 16 May 2014, 11:04 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Allan McRae (Allan)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

In /usr/share/gcc-4.8.?/python/libstdcxx, there are three python scripts that apparently get run as root at some point. When this happens, they create bytecode compiled .pyc files, which, of course, are not tracked by pacman. On each upgrade of gcc, the .pyc files and the dirs get left behind because the path is specific to each version. I had /usr/share/gcc-4.8.0/ and /usr/share/gcc-4.8.1/ on my system in addition to the current /usr/share/gcc-4.8.2/.
This task depends upon

Closed by  Allan McRae (Allan)
Friday, 16 May 2014, 11:04 GMT
Reason for closing:  Deferred
Additional comments about closing:  Waiting on Arch to formalize a policy for .pyc/.pyo files being contained in a package
Comment by Doug Newgard (Scimmia) - Wednesday, 11 December 2013, 09:35 GMT
I was looking at this for a couple of my packages, it could be as simple as adding 'python2 -m compileall "$pkgdir"' to the end of the package function. This adds a makedep on python2 (or python, if they're python3 compatible), but I can't think of a way around that.
Comment by Hussam Al-Tayeb (hussam) - Tuesday, 06 May 2014, 21:19 GMT
Are you compiling applications as root?
Comment by Doug Newgard (Scimmia) - Wednesday, 07 May 2014, 00:34 GMT
Nope, never have.
Comment by Allan McRae (Allan) - Wednesday, 07 May 2014, 00:39 GMT
Oh - there! I had assumed (without actually reading the bug) that this was the gdb files. I have no idea how these get created then...

I have little intention of doing anything about this until Arch formalizes its policy on how to handle .pyc/.pyo files. I have tried several times to get that done.
Comment by Doug Newgard (Scimmia) - Wednesday, 07 May 2014, 00:58 GMT
I'm guessing most of the devs don't care, as the new files are usually installed over top of the previous files, so the .pyc files just get re-created in place. It's more of an issue here since the path is version specific. Not really a big deal, though, just extra cruft left in the filesystem.

Loading...