On Thu, Aug 18, 2005 at 09:48:10AM +0200, Stefano Zacchiroli wrote:
> On Thu, Aug 18, 2005 at 07:56:28AM +0200, Christian T. Steigies wrote:
> > I tried to clean my buildd and now its broke worse than ever:
> >
> > Preparing to replace ocaml-nox 3.08.3-6 (using
> > .../ocaml-nox_3.08.3-7_m68k.deb) ...
> > ERROR: emacsen-common being used before being configured.
>
> Well, this is not related to ocaml-md5sums any longer, but to emacs.
That is true, but your prerm script uses emacs, so your package has to
(pre)depend on emacs or something.
# Automatically added by dh_installemacsen
if [ -x /usr/lib/emacsen-common/emacs-package-remove ] ; then
/usr/lib/emacsen-common/emacs-package-remove ocaml-nox
fi
Last night, when I cleaned up the buildd again, I thought I had all of ocaml
removed, only to notice this morning, that 146 packages failed to build,
because some ocaml zombies were still hiding on the system, preventing any
other package from being installed. I don't care if you have a separate
ocaml-emacs package, I just want to be able to remove ocaml-* without
manually editing some packaging scripts. The alternative would be to leave
ocaml installed, it gets pulled in anyhow everytime I build an ocaml related
package. But then it would not get upgraded automatically whenever you
release a new version, so packages depending on ocaml will be built against
outdated packages. The third alternative (can there be more than two
alternatives?) I am thinking about, is instructing my buildds never to touch
anything ocaml related again, I don't like packages that break my buildd,
epscially when we are fighting a backlog. Or are you actually part of the
conspiracy trying to demote m68k to second class citizens? ;-)
Christian
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
