2012/11/30 Andreas Beckmann <deb...@abeckmann.de>: > On 2012-11-29 23:17, Sébastien Villemot wrote: >> I have installed lenny's emacs22 package in a wheezy chroot, then >> installed wheezy's emms and devscripts-el, and it worked fine. It also >> works when, in addition, I downgrade emacsen-common to squeeze's >> version. > > You could try squeeze + emacs22/lenny, install $PACKAGE/squeeze, > distupgrade to wheezy. > >> Andreas: how are we supposed to reproduce this? Maybe a full log of the >> upgrade session would help. > > Full piuparts logs attached to the individual bugs. > > a rough outline of the test is > > debootstrap lenny (or unpack lenny.tar.gz) > apt-get install $PACKAGE > sed s/lenny/squeeze/ sources.list > apt-get dist-upgrade > sed s/squeeze/wheezy/ sources.list > apt-get dist-upgrade
Tried a) Create lenny pbuilder chroot b) Install emacs22 in it c) Upgrade to squeeze d) Upgrade to wheezy No problems found with devscripts-el here. Originally provided piuparts log mentions something at install/devscripts-el: Handling emacs22, logged in /tmp/elc_VaIFTD.log However, since that file is not attached I am afraid we cannot look at that. Is that file somewhere at piuparts site? With emms I found the problem described in attached log. However, seems that after further apt runs this problem vanishes (In this case original piuparts log also does not provide the log at /tmp). Does emms need something to be byte-compiled previously without declaring a dependency? In my tests, speechd-el fails in emacs22 since eieio is no longer available as a standalone package but is now part of emacs23-common, which conflicts with old standalone eieio package. Error message is Loading /usr/share/emacs22/site-lisp/speechd-el/speechd-braille.el (source)... Cannot open load file: eieio make: *** [braille.elc] Error 255 ERROR: install script from speechd-el package failed diffferent than in original bug report, but reproducible here. I am afraid that the simple solution is to make speechd-el not build for emacs22. Will try to look further in the emms stuff in case I can reproduce it again. Regards, -- Agustin
emms.log
Description: Binary data
