On Sep 20, Roman Hodek <[EMAIL PROTECTED]> wrote: >As you see, aclocal, automake, ... are all rerun, i.e. a new >Makefile.in is generated. (Probably a change in the Debian patch to Yes, this is the problem, another developer found it. But I have no idea about how to solve it. I Cc: -devel, maybe someone who knows about automake will help me. (Short summary: if automake is installed then a new Makefile.in is created and it has no dependencies inside. There is nothing to update so auto* should not be run.)
>configure.in or the like is the cause.) Therefore, you have to make >this change also to Makefile.am. The only change is in Makefile.in, which is *newer* than .am: -rw-r--r-- 1 root root 27334 Sep 10 17:49 Makefile -rw-r--r-- 1 md users 4388 Aug 8 16:31 Makefile.am -rw-r--r-- 1 root root 26629 Sep 9 08:45 Makefile.in -rw-r--r-- 1 root root 12770 Sep 9 08:09 configure.in -rw-r--r-- 1 md users 17148 Sep 9 08:45 aclocal.m4 so I don't understand why it's remade (it depends on aclocal.m4 and configure.in but it has the same date). Please also look at #45265, it's very important and could be a bug in the build daemon: in (at least) the packages built for m68k and alpha mutt_lock is not installed setuid. -- ciao, Marco
