touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #63287
[Bug 503761] Re: bash behaves different on symlinks than the GNU tools
EOL reached or very close. Time to use some newer version.
** Changed in: gnubash
Importance: Unknown => Undecided
** Changed in: gnubash
Remote watch: Debian Bug tracker #538891 => None
** Changed in: gnubash
Status: New => Invalid
** Changed in: bash (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/503761
Title:
bash behaves different on symlinks than the GNU tools
Status in The GNU Bash Shell:
Invalid
Status in bash package in Ubuntu:
Invalid
Bug description:
Binary package hint: bash
as example I have 'ln -s /tmp $HOME/tmp'
when I now cd into tmp/ I correcty get to the /tmp folder, cd .. gets me back to ~. So far so good.
now... when I'm in tmp and try to work with bash auto-completion or pwd I can't use cp, rm, mv, file, stat, etc... anymore
when I do 'cp ../.bashr<tab>' it gets auto-completed to 'cp ../.bashrc'
but when I actually run the command 'cp ../.bashrc .' I get
cp: cannot stat `../.bashrc': No such file or directory
you easily find out why that happens with 'ls ..' which shows
bin cdrom etc initrd.img lib mnt proc sbin srv tmp var vmlinuz.old
boot dev home initrd.img.old media opt root selinux sys usr vmlinuz
and finally pwd shows that bash and the GNU tools think differently:
$ pwd
/home/yofel/tmp
$ /bin/pwd
/tmp
ProblemType: Bug
Architecture: i386
Date: Wed Jan 6 12:33:52 2010
DistroRelease: Ubuntu 10.04
Package: bash 4.1-1ubuntu1
ProcEnviron:
LANGUAGE=en_US.UTF-8
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-9.13-generic
SourcePackage: bash
Tags: lucid
Uname: Linux 2.6.32-9-generic i686
To manage notifications about this bug go to:
https://bugs.launchpad.net/gnubash/+bug/503761/+subscriptions