On Tue, Jun 26, 2012 at 05:55:14PM +0200, Agustin Martin wrote:
> So, seems that the problem appears when both xemacs21 stuff and emacsen-common
> are ugraded at the same time. Seems that xemacs21 stuff needs something from
> a postinst to become available for byte-compilation, so byte-compilation
> fails and needed postinst is not reached. If in the failing chroot I run
> 
> # xemacs21 -vanilla -nw
> 
> WARNING:
> Couldn't find obvious defaults for:
> data-directory
> mule-lisp-directory
> lisp-directory
> Perhaps some directories don't exist, or the XEmacs executable,
> /usr/bin/xemacs21
> is in a strange place?
> .
> 
> and once xemacs is started I see
> 
> (1) (warning/warning) Autoload error in:
> /usr/share/xemacs21/mule-packages/lisp/latin-euro-standards/auto-autoloads: 
>         Cannot open load file: cl-macs
> 
> I think that emacsen-common > 2.0.0 considering the failure of any
> add-on package install or remove script as a fatal error just makes this
> underlying xemacs21 problem evident, but seems to be something wrong in
> xemacs21.
> 
> Reading more carefully http://bugs.debian.org/619367 I see that it points 
> to http://bugs.debian.org/391778, where some symlinks are done at
> xemacs21-* postinst. May be those symlinks should be done in appropriate
> preinst if needed, so paths are available even if xemacs21* is not yet
> configured.

I am thinking about a possible alternative, a dirty workaround from the
emacsen-common side, make "emacs-install" and "emacs-package-install" 
skip byte compilation for xemacs21 if those symlinks are not set, warning
about this.

"emacs-install" should be called again from relevant xemacs21* postinsts,
and this last must be done after symlinks are set.

Did not look at "emacs-install" and "emacs-package-install", nor sure how
reasonable / rock solid/ easy is this. Also, I find this a bit weak
regarding possible changes in xemacs21, but ...

Regards,

-- 
Agustin



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to