tag 565727 + help thanks Hi Klaus,
Thanks for your report and sorry for following up so late. On 2010-01-18 at 11:17:05 +0100, Klaus Ethgen <kl...@ethgen.de> wrote: > Package: cscope > Version: 15.7a-3 > Severity: serious > > I wanted to fill a critical bug for this as it breaks upgrade procedure > of other packages. But serious is also true as it shouldn't. Well. > > The problem is that "/usr/lib/emacsen-common/emacs-package-remove > cscope" will fail if no emacs is installed (telling something that it is > called before emacs is configured, which is not true). I thought that was why I needed to depend on emacsen-common in the first place (also see #562550). As I myself don't use emacs and thus also don't use the cscope emacs bindings, I really lack the proper knowledge to correctly tackle this bug. I'd be happy about any emacs-expert pointing me towards a proper solution. I'm not sure about whom to Cc/contact about this. The best guess I came up with was the debian-emacsen mailing list. But that one seems orphaned for quite a while. > That ends in many packages not getting configured when upgrading the > system. However, a simple "|| :" at the end of the call would be > enough to work around the bug. Better would be to throw the whole emacs > stuf away as cscope is much of use without emacs installed! (I see no > reason why I should install emacs at all.) I think there are users who rely on cscope to provide the emacs bindings (also see bug #566302), so it'd be kind of sad to just throw the whole emacs-specific stuff away as you suggest. OTOH as I already mentioned I really lack the proper knowledge about emacs to get this right. So I guess throwing it away temporarily until somebody can come up with a feasible solution currently seems like the best "solution" I have to resolve this bug. Cheers, Tobias
signature.asc
Description: Digital signature
