$summary
I've already tested and stabilized on Alpha. Amd64 I've been testing for ages, so if the arch team is fine with it, it can be stabilized.
Stable for HPPA.
ago@amd64box ~ $ lib_users Traceback (most recent call last): File "/usr/bin/lib_users", line 141, in <module> main() File "/usr/bin/lib_users", line 110, in main deletedlibs = get_deleted_libs(mapsfile) File "/usr/bin/lib_users", line 29, in get_deleted_libs for line in map_file: IOError: [Errno 13] Permission denied Seems does not work for me, any suggestion?
(In reply to comment #3) > ago@amd64box ~ $ lib_users > Traceback (most recent call last): > File "/usr/bin/lib_users", line 141, in <module> > main() > File "/usr/bin/lib_users", line 110, in main > deletedlibs = get_deleted_libs(mapsfile) > File "/usr/bin/lib_users", line 29, in get_deleted_libs > for line in map_file: > IOError: [Errno 13] Permission denied > > > Seems does not work for me, any suggestion? You have to run it as root. Next version will include code that handles running as a user (and will give a helpful warning message).
(In reply to comment #4) > You have to run it as root. Next version will include code that handles running > as a user (and will give a helpful warning message). Ok, if only root can touch it, how about s/newbin/newsbin/ in the ebuild?
(In reply to comment #5) > Ok, if only root can touch it, how about s/newbin/newsbin/ in the ebuild? It _is_ usable by non-root users, but it will only show the user's stuff (v0.4, that is). The main use case is restarting daemons after updating packages, so usually it is run as root. I'd still keep in /usr/bin as the average user might have a use case for it -- and the classic reasons for being in sbin (statically linked, needed for system recovery) are not the case.
amd64 ok
amd64 stable
ppc done; closing as last arch
