Upgrading bash-completion from 20040704-r1 to any later version (such as 20041017) cause a two lines warning every time I log in into a new shell (or I "su" to a user, of course). The error is: bash: .: /etc/bash_completion.d/bash-completion: is a directory bash: .: /etc/bash_completion.d/bash-completion: is a directory Bash completion works normally, altough the annoying warning displayed. Reverting back to 20040704-r1 is ok. The problem lies in /etc/bash_completion (I updated the etc files one by one to see the one that caused the issue). --------------- EMERGE INFO OUTPUT --------------- Portage 2.0.51-r2 (default-x86-1.4, gcc-3.4.2, glibc-2.3.4.20041006-r0, 2.6.8-gentoo-r8 i686) ================================================================= System uname: 2.6.8-gentoo-r8 i686 Intel(R) Pentium(R) 4 CPU 2.40GHz Gentoo Base System version 1.6.4 distcc 2.18 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.15.92.0.2-r1 Headers: sys-kernel/linux26-headers-2.6.8.1-r1 Libtools: sys-devel/libtool-1.5.2-r5 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O3 -march=pentium4 -pipe" CHOST="i686-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/bind /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=pentium4 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache distlocks sandbox" GENTOO_MIRRORS="http://ftp.linux.ee/pub/gentoo/distfiles/ ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo ftp://ftp.tu-clausthal.de/pub/linux/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X aalib alsa apache2 apm arts avi berkdb bitmap-fonts bonobo cdr crypt cups directfb doc dvd emacs encode esd f77 foomaticdb gdbm gif gnome gpm gtk gtk2 gtkhtml guile imap imlib jack java jpeg kde ldap libg++ libwww mad maildir mbox mikmod mmx motif mpeg mysql nas ncurses nls oggvorbis opengl oss pam pcmcia pdflib perl png python qt quicktime readline samba sasl sdl slang spell sse sse2 ssl svga tcltk tcpd tetex truetype x86 xml2 xmms xprint xv zlib video_cards_i915 linguas_it"
I am unable to reproduce this. Did you try merging the old and new /etc/bash_completion when updating or did you replace it outright?
I replaced it with etc-update.
Same bug here. Appeared after upgrading to 20040711. Though I get only one "bash: .: /etc/bash_completion.d/bash-completion: is a directory" line
Mmmh... Probably the ebuild didn't remove an old symlink to a directory in /etc/bash_completion.d/ when upgrading... Try to ls -l /etc/bash_completion.d/bash-completion and see if it's a symlink to a dir. if it is, unlink it. I cannot try now (since I'm on MacOSX, yup) If this solves the issue, please report, and I'll close the bug as WORKSFORME.
/etc/bash_completion.d/bash-completion was a link to /usr/share/bash-completion, and removing it fixed the problem. Can this be automated in the ebuild?
Nope. We can't mess around with anything inside /etc really. Kinda annoying on occasion.
Resolving.
That sucks. It can't even be done through etc-update? Also, is WORKSFORME really the correct resolution. It is described as "All attempts at reproducing this bug were futile, reading the code produces no clues as to why this behavior would occur. If more information appears later, please re-assign the bug, for now, file it." How about CANTFIX? (Ok, thats a detail, but I like things to be done the right way)
Right, but I thought that "Works-for-me" could also mean "The purposed solution works, I'm not able to reproduce it anew, and no modification of the ebuild are needed, so from my (dev) side is worksforme". At least, this in other Bugzillas. ;-) This bugzilla need a "workaround" for these cases imho. Anyway, reproducing this bug on a fresh installation can't be done, and also many people doesn't experience this also when upgrading. So "worksforme" made sense. If you feel brave, file a bug requesting for "workaround" as a keyword in b.g.o. "cantfix" is if possible even worse since a user that reads the buglist think "oh, well, so there's NO fix? how wonderful." these are just opinions, anyway.
One could set "Severity" to Minor("minor loss of function, or other problem where easy workaround is present"), and "Resolution" to CANTFIX. The bug can't be fixed, but there is an easy workaround.
sorry for the spam people
doneit
