the Option "auto-orphans" is listed in urpmi --help. urpmi --auto-orphans seems to be an "valid" option since not "unknown option" is shown, but without any function. Compare: [root@MediaCenter ~]# urpmi --xxx Unknown option: xxx --> help message is shown and [root@MediaCenter ~]# urpmi --auto-orphans --> help message is shown
It seems a valid option when combined with installing something (what urpmi is for!) e.g. like this: [root@cldrn_64 marja]# LC_ALL=C urpmi --auto-update --auto-orphans medium "Core Release (RedHD21)" is up-to-date medium "Nonfree Release (RedHD211)" is up-to-date medium "Core 32bit Release (RedHD231)" is up-to-date medium "Nonfree 32bit Release (RedHD236)" is up-to-date ^C[root@cldrn_64 marja]# (I stopped it, because I didn't want my orphans to be removed!) Would you like to try?
Keywords: (none) => NEEDINFOCC: (none) => marja11
It seems to work fine and do what is says in the help, though as marja mentioned it only acts upon a package installation: ----- # LC_ALL=C urpmi --test null --auto-orphans writing /var/lib/rpm/installed-through-deps.list The following orphan packages will be removed. lib64iodbc2-3.52.10-1.mga6.x86_64 lib64dc1394-devel-2.2.4-1.mga6.x86_64 lib64nut-devel-0.0.675-8.mga6.x86_64 [...] lib64freealut-devel-1.1.0-13.mga6.x86_64 lib64usb1.0-devel-1.0.20-3.mga6.x86_64 installing null-12-52.mga6.x86_64.rpm from /var/cache/urpmi/rpms Preparing... ########################################################################################################################################################## Installation is possible ----- (I guess it doesn't try the uninstall with the `--test` argument)
Thanks, Rémi, I had forgotten about "--test" @ Marc I feel very much tempted to close this report as invalid, because urpmi is for installing, and I don't think it is a good idea to clutter the help page with additional info for every argument that won't work when nothing gets (test-)installed. "urpmi --test" returns the help page, too.
I'm fine with closing it. When the option has a function, it's not a bug ;)
Status: NEW => RESOLVEDResolution: (none) => INVALID