| Summary: | revdep-rebuild doesn't catch broken deps in e.g. /usr/bin | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Frank Richter <res> |
| Component: | Tools | Assignee: | Portage Tools Team <tools-portage> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Which version of gentoolkit do you have installed? Hm, was 0.2.1. Sorry for the fuzz, 0.2.2 seems to be fine... as apparently the "-perm /u+x" path is used. Anyhow, "/" matches if any of the permissions are set; while "+" may match exactly. Maybe "-u+x" would still be more preferable as the fallback permissions filter? |
I noticed that, when updating dbus (which is used by quite a number of apps), revdep-rebuild missed a lot of broken binaries. Digging into the revdep-rebuild source, I noticed that it only finds binaries that are _at most_ executable by the user ("-perm +u+x" in the find statement). Changing that to "-perm -u+x" (ie _at least_ executable by the user), and, behold, a lot of binaries are now recognized as broken. Reproducible: Always