Bug#309637: Some warnings during upgrade
tags 309637 + fixed-experimental
stop
On 18.05.05 Juhapekka Tolvanen (juhtolv@cc.jyu.fi) wrote:
> Setting up tetex-bin (2.0.2-30) ...
> /root/.bashrc: line 40: /.bash_common.sh: No such file or directory
> /root/.bashrc: line 40: /.bash_common.sh: No such file or directory
> /root/.bashrc: line 40: /.bash_common.sh: No such file or directory
> /root/.bashrc: line 40: /.bash_common.sh: No such file or directory
> /root/.bashrc: line 40: /.bash_common.sh: No such file or directory
> /root/.bashrc: line 40: /.bash_common.sh: No such file or directory
> /root/.bashrc: line 40: /.bash_common.sh: No such file or directory
> /root/.bashrc: line 40: /.bash_common.sh: No such file or directory
> /root/.bashrc: line 40: /.bash_common.sh: No such file or directory
> Merging information from /etc/texmf/texmf.d/ into /etc/texmf/texmf.cnf ... /root/.bashrc: line 40: /.bash_common.sh: No such file or directory
> done
>
>
> Line 40 in /root/.bashrc looks like this:
>
> . "${HOME}/.bash_common.sh"
>
> And that file really exist. Somehow that environment variable
> called $HOME is unset.
>
tetex-bin (3.0-2) experimental; urgency=low
* Revert the change from the last version: Do not unset HOME.
It's better to create/update ls-R files in root's or a
sudo-user's $HOME/texmf, than in /texmf. There is currently no
way to stop mktexlsr from doing that, if the directories exist.
-- Frank Küster <frank@debian.org> Sun, 13 Mar 2005 15:41:39 +0100
--> tagging
H.
--
sigmentation fault
Reply to: