From time to time, I need to add some package to my keywords. For example, I started to try to use newer than stable udev versions due a bug with automounting, but I didn't keyworded every newer udev and co. versions, I tend to only add one version to my keywords and decide on every version whether to update or keep old one. The problem is that, once my keyworded version is removed from the tree, I don't easily notice that and, then, I could potentially skip and important change that caused older version to be dropped, for example. In my case I noticed it while today wanting to update to newer udev-197-r3 from 196, but "emerge -avuDN world" didn't show me that I have: # eix -e kmod [D] sys-apps/kmod Available versions: ~12-r1^t **9999^t {{debug doc lzma static-libs +tools zlib}} Installed versions: 12^t(21:10:39 13/12/12)(tools zlib -debug -doc -lzma -static-libs) Homepage: http://git.kernel.org/?p=utils/kernel/kmod/kmod.git Description: library and tools for managing linux kernel modules Would be nice if emerge could have a stricter OPTION to want to update to newer version (and, then, asking me to keyword a newer one) when my version is no longer in the tree and emerge cannot downgrade neither upgrade due keyword settings Thanks Reproducible: Always
If you run `emerge -pe @world` then it should trigger warnings for any such packages. I would like to add an option so you can get these warnings for installed packages without having to use -e.
(In reply to comment #1) > If you run `emerge -pe @world` then it should trigger warnings for any such > packages. I would like to add an option so you can get these warnings for > installed packages without having to use -e. A warning would be nice for sure :D
*** Bug 694164 has been marked as a duplicate of this bug. ***
(In reply to Zac Medico from comment #1) > If you run `emerge -pe @world` then it should trigger warnings for any such > packages. I would like to add an option so you can get these warnings for > installed packages without having to use -e. For that part, see also bug 911180 and bug 651018.
