lib32 and lib64 not covered

Bug #1097972 reported by Michael Tomkins on 2013-01-09
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Safe-rm
Medium
François Marier

Bug Description

On my system I have a /lib and /lib32 /lib64. This is
because I run amd-64 but need some print drivers that only have lib32
versions. I'm pretty sure that /lib32 /lib64 are usual for adding this
functionality to systems but are not covered in the safe-rm protected
directories.

Changed in safe-rm:
status: New → Confirmed
importance: Undecided → Medium
Changed in safe-rm:
assignee: nobody → François Marier (fmarier)
Changed in safe-rm:
milestone: none → 0.9
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers