On Tue, Nov 20, 2012 at 06:07:46PM +0100, Agustin Martin wrote:
> On Tue, Nov 20, 2012 at 05:28:23PM +0100, intrigeri wrote:
> > Hi,
> > 
> > (Meta: I was going to express my intent to NMU emacsen-common to fix the
> > #676424 RC bug, when I discovered that the package had another one
> > (#677191) => trying to understand what can be done with that one first.)
> > 
> > Rob Browning wrote (26 Jun 2012 02:08:56 GMT) :
> > > Agustin Martin <agmar...@debian.org> writes:
> > >> As pointed out in #132355, using single dashed -no-site-file should
> > >> work for both XEmacs and (although undocumented) FSF Emacs.
> > >> 
> > >> If maintainer wants to be in the safe side and use only documented
> > >> features I expect something like attached patch to work for
> > >> emacsen-common.
> > >
> > > OK, I either hadn't seen this before, or just forgot. It looks an
> > > update to emacsen-common would be in order, right?
> > 
> > Reading these bugs log, it's not clear to me whether the single-dashed
> > option idea:
> > 
> >   1. has any chance to fix #677191 and friends
> >   2. was tried in the context of the Squeeze -> Wheezy dist-upgrade
> 
> #132355 is about decreasing verbosity when byte-compiling emacsen-common. 
> When I mentioned it in #677191 I did not yet know what was causing the
> #677191 problem and thought that some of the files loaded at init might
> be related, but few messages below in #677191 that was discarded and the
> real reason for this problem become more evident.
> 
> The -no-site-file changes now seems mostly a cosmetic issue for XEmacs
> with no relation at all to #677191.

Looking again at xemacs21 status I see that it is not in testing and that
sid version ships the missing symlinks in the package instead of creating
them from a postinst on configuration. 

I would expect that this should make all lisp stuff available during
emacsen-common configuration, thus fixing both #677191 and #619367 as well
as #670292, closed with sid upload. As a matter of fact I no longer see
the problem in squeeze->sid upgrade.

Can others still reproduce the problem?

-- 
Agustin


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

Reply via email to