Summary: | Warning displayed at each login: /etc/bash_completion.d/bash-completion: is a directory | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Matteo Settenvini <matteo-ml> |
Component: | Current packages | Assignee: | Gentoo Shell Tools project <shell-tools> |
Status: | RESOLVED CANTFIX | ||
Severity: | minor | CC: | tor.klingberg |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Matteo Settenvini
2004-10-28 12:20:31 UTC
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 |