Your message dated Mon, 20 Oct 2008 19:15:07 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: Bug#21820: bug in debian-emacs-policy.gz example script has caused the Debian Bug report #21820, regarding [PROPOSED] bug in debian-emacs-policy.gz example script to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 21820: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=21820 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems
--- Begin Message ---Package: emacsen Version: 1.4-3 in the emacsen-install example, only the first file get's the complete path as prefix: el_files="a.el b.el" el_path_list=`echo ${el_files} | perl -pe "s|^|${el_dir}|o"` elc_path_list=`echo ${el_files} | perl -pe "s|^|${elc_dir}|o"` should read: el_path_list=`echo ${el_files} | tr ' ' '\n' | perl -pe "s|^|${el_dir}|o"` elc_path_list=`echo ${el_files} | tr ' ' '\n' | perl -pe "s|^|${elc_dir}|o"`
--- End Message ---
--- Begin Message ---Version: 1.4.15 On Tue, Apr 28, 1998 at 08:28:33PM +0200, Matthias Klose wrote: > Package: emacsen > Version: 1.4-3 > > in the emacsen-install example, only the first file get's the complete > path as prefix: > > el_files="a.el b.el" > el_path_list=`echo ${el_files} | perl -pe "s|^|${el_dir}|o"` > elc_path_list=`echo ${el_files} | perl -pe "s|^|${elc_dir}|o"` > > should read: > > el_path_list=`echo ${el_files} | tr ' ' '\n' | perl -pe "s|^|${el_dir}|o"` > elc_path_list=`echo ${el_files} | tr ' ' '\n' | perl -pe "s|^|${elc_dir}|o"` This is a pretty old bug report, and seems that in the meantime the problem it refers to has disappeared from debian-emacs-policy. Browsing through the old versions I could get, this seems to have been fixed in 1.4.15, although was not marked as fixed. I am then closing this bug report. -- Agustin
--- End Message ---
