Hide Forgot
Description of problem: When I use emacs , I found a error -- "(file-error Setting current directory no such file or directory /builddir/build/BUILD/emacs-23.1/src/)" I saw the builder is your about http://koji.fedoraproject.org/koji/buildinfo?buildID=129952. Maybe it use the chroot enviroment directory which create by mock on koji building system. my emacs is : -------------------------------- $ rpm -qa|grep emacs-23.1 emacs-23.1-6.fc12.i686 ===================== Rich info : --------------------------------------------------- $ LANG=en_US && emacs -q -batch -l muse-init.el -f muse-project-batch-publish --force Computer.Python Loading /usr/share/emacs/site-lisp/site-start.d/focus-init.el (source)... Loading /usr/share/emacs/site-lisp/site-start.d/git-init.el (source)... Loading /usr/share/emacs/site-lisp/site-start.d/muse-init.el (source)... Loading /usr/share/emacs/site-lisp/site-start.d/php-mode-init.el (source)... Loading /usr/share/emacs/site-lisp/site-start.d/po-mode-init.el (source)... Loading /usr/share/emacs/site-lisp/site-start.d/rpm-spec-mode-init.el (source)... Publishing project Computer.Python ... OptionParser: Error occured: (file-error Setting current directory no such file or directory /builddir/build/BUILD/emacs-23.1/src/) backtrace() byte-code("ÂÀÃÄÅ #Æ ÇÈÉÅ #!Â" [muse-batch-publishing-p err boundp message "%s: Error occured: %s" muse-page-name backtrace muse-display-warning format "An error occurred while publishing %s: ==========================================================
hello, under which circumstances the error appears?
No circumstances info, Just "file-error Setting current directory no such file or directory /builddir/build/BUILD/emacs-23.1/src/" when run a lisp scripts by emacs from command . I'm not familarity the inner in emacs. But maybe the emacs.spec let mock set the "/builddir/build/"(chroot's topdir) as some dir in emacs. Thanks,
can you attach the "muse-init.el" script, which produces the error, when you run it? or, if this is secret, some another reproducer?
hmmm, this seems the same as Bug 474958 - there's a better reproducer there, so I will close dup this one *** This bug has been marked as a duplicate of bug 474958 ***