Hi,

On Sun, 2005-03-13 at 19:58 +0100, Christoph Wegscheider wrote:
> > =========================================================================
> > [...]
> > /usr/bin/make
> > make[1]: Entering directory `/tmp/buildd/rsnapshot-1.2.0'
> > cd . && /tmp/buildd/rsnapshot-1.2.0/missing aclocal-1.4
> > WARNING: `aclocal-1.4' is needed, and you do not seem to have it handy on 
> > your
> >          system.  You might have modified some files without having the
> >          proper tools for further handling them.  Check the `README' file,
> >          it often tells you about the needed prerequirements for installing
> >          this package.  You may also peek at any GNU archive site, in case
> >          some other package would contain this missing `aclocal-1.4' 
> > program.
> > make[1]: *** [aclocal.m4] Error 1
> > make[1]: Leaving directory `/tmp/buildd/rsnapshot-1.2.0'
> > make: *** [build-stamp] Error 2
> > =========================================================================
> 
> I tested it (before uploading and now again) with pbuilder also on i386
> without this error. Please retest it with an updated sid environment and
> a fresh source package of rsnapshot and attach a full log if the error
> is still there.

I retried on i386 and sparc in a current pbuilder chroot and a fresh
source tarball (that actually didn't change :-) and encountered the same
problem.

My experience with similar bugs is that reproduction results can be
improved by actually fetching the package ("apt-get source ...") from a
standard Debian mirror since on the machine of the maintainer in the
development directory, the repository is sometimes handled differently.
Does it help?

> As I understand this Bug report was filed by a script (or at least the
> testing was done with one), please do the retesting manually so we are
> sure the failure is not caused by a bug in that script. 

While I'm searching for bugs automatically and letting DARTS help me in
reporting, I always re-check problems manually since I consider fully
automatic as bad practice as you do.

Thanks for considering.

bye,
  Roland




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to