Bug 711615 - emacs-mozc puts mozc.elc in wrong directory
Summary: emacs-mozc puts mozc.elc in wrong directory
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: mozc
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Akira TAGOH
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-07 22:24 UTC by Nick Urbanik
Modified: 2011-06-11 04:33 UTC (History)
2 users (show)

Fixed In Version: mozc-1.1.717.102-2.fc15
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-11 04:33:15 UTC
Type: ---


Attachments (Terms of Use)

Description Nick Urbanik 2011-06-07 22:24:17 UTC
Description of problem: emacs-mozc puts mozc.elc in wrong directory


Version-Release number of selected component (if applicable):
mozc-1.1.717.102-1.fc15.src.rpm

How reproducible: always


Steps to Reproduce:
1. Open emacs
2. startup interrupted with message: Cannot open load file: mozc
3. do rpm -ql emacs-mozc and see obvious problem
  
Actual results:
emacs won't start up while mozc-init.el attempts to find mozx.elc

Expected results:
emacs works with mozc support.

Additional info:
$ rpm -ql emacs-mozc
/usr/share/emacs/site-lisp/%{pkg}
/usr/share/emacs/site-lisp/%{pkg}/mozc.elc
/usr/share/emacs/site-lisp/site-start.d/mozc-init.el

It seems that %{pkg} was intended to be expanded rather than reproduced verbatim.

Comment 1 Akira TAGOH 2011-06-08 01:54:52 UTC
thanks for filing a bug. this issue has already been fixed in 1.1.717.102-2. need some karma for early push.

https://admin.fedoraproject.org/updates/mozc-1.1.717.102-2.fc15

Comment 2 Fedora Update System 2011-06-08 01:56:12 UTC
mozc-1.1.717.102-2.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/mozc-1.1.717.102-2.fc15

Comment 3 Fedora Update System 2011-06-11 04:33:10 UTC
mozc-1.1.717.102-2.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.