Ian Zimmerman <i...@buug.org> writes:
> Looks to me like /usr/lib/emacsen-common/packages/install/emacsen-common
> is where it happens. It is probably called with $FLAVOR set in turn to
> each file name in /var/lib/emacsen-common/state/flavor/installed, and as
> I say in the other subthread, somehow that directory contained a file
> "emacs" on my system.
So, at least in the new infrastructure (unless I'm missing something),
the only way an "emacs" file could end up in flavor/installed/ is via
the emacsen-common postinst:
# Convert installed-flavors to flavor/installed/*.
if test -e /var/lib/emacsen-common/installed-flavors
then
for flavor in $(cat /var/lib/emacsen-common/installed-flavors)
do
touch "/var/lib/emacsen-common/state/flavor/installed/$flavor"
done
rm -f /var/lib/emacsen-common/installed-flavors
fi
...and the only way that could produce installed/emacs is if emacs ended
up in the legacy /var/lib/emacsen-common/installed-flavors, and *that*
shouldn't be possible (as far as I recall).
It suggests that some package was installed that thought of itself (as
far as emacsen-common is concerned) as the "emacs" flavor of emacs,
which shouldn't exist (i.e. the flavor should always be emacsXY, or
xemacsXY, etc.).
Any chance you might have installed some "unofficial" emacs package that
might have tried to use the "emacs" flavor for itself?
Thanks
--
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
