On 9/15/22 16:20, Piscium wrote:
On Thu, 15 Sept 2022 at 22:13, pete via arch-general <arch-general@lists.archlinux.org> wrote:
Hope someone can trow some light on this it appeared a few days ago after an update "pacman -Syu"
I would suggest finding what is your login shell (set in /etc/passwd) then check all the files used by that shell, for example for bash .bash_profile, etc, and the files in the /etc/profile.d folder.
If you don't find anything whether on global or system shell calls/dependencies, if you perform 'grep -r' for /usr/bin and /usr/lib, you'll fine several things calling for 'egrep' still, it doesn't matter you're not calling directly those, but perhaps some of their dependencies are. So it's not that even if you're up to date on Arch, that means nothing in your systems calls for egrep anymore. Some upstream SW might still be calling egrep... BTW, currently the message is not dangerous:
% cat /usr/bin/egrep #!/bin/sh cmd=${0##*/} echo "$cmd: warning: $cmd is obsolescent; using grep -E" >&2 exec grep -E "$@"
Of course seeing such messages is somehow scary, :) -- Javier