When I remove an entry in files like /etc/portage/package.mask/foo, I occasionally forget about the foo~ or foo.bck backup file the editor creates. It still has the line I removed, and so my changes don't apply. Happened a couple of times to me, I assume I'm not the only one. Reproducible: Always Steps to Reproduce: 1. create /etc/portage/package.mask/foo with entry like >=x11-libs/cairo-1.8.10 2. emerge -pu x11-libs/cairo wants to downgrade 3. remove this line with an editor like Nedit or nano that makes automatic backups Actual Results: emerge -pu x11-libs/cairo still wants to downgrade Expected Results: It would be nice if portage would know about the common backup extensions like .bak, .bck, ~, % and what else there are, and ignore them. I'm using Portage 2.2.0_alpha4.
Portage already should ignore files ending with ~ suffix. Doesn't that really work for you?
Sorry, my bad. A '~' at the end is indeed being ignored already. I must admit I only tried '.bck' for this report, but I'm pretty sure I had a problem with '~' also not far in the past. Maybe when I accidentally downgraded portage? Still, extending the suffix list to {~,%,.bak,.bck,.backup} (are there more?) would be nice. I think.
(In reply to comment #2) > Still, extending the suffix list to {~,%,.bak,.bck,.backup} (are there more?) > would be nice. I think. Yeah, and then extending all helper tools to behave exactly the same. And then extending the list even more. And fixing all the tools. And then adding intelligent backup recognition. And then fixing it. Is it that hard to keep a clean configuration dir?
