Your message dated Wed, 5 Sep 2007 17:40:53 -0600
with message-id <[EMAIL PROTECTED]>
and subject line Bug#362880: touch appears to behave incorrectly
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: coreutils
Version: current unstable, probably 5.94-1
Severity: normal
Please have a look at this [1] build log. You will find there
> touch -r aclocal.m4 configure configure.h.in `find . -name Makefile.in`
and later on
> Prerequisite `aclocal.m4' is newer than target `Makefile.in'.
which is the reason the build fails. This bug occurs only on sparc and
ia64 and is not reproducible with a manual build.
Kind regards,
Martin
[1]
http://buildd.debian.org/fetch.php?&pkg=cgoban&ver=1.9.14-10&arch=sparc&stamp=1145166681&file=log&as=raw
--- End Message ---
--- Begin Message ---
Bob Proulx wrote:
> Hello Martin,
>
> On Sun, 16 Apr 2006 08:37:42 +0200 Martin Godisch wrote:
> > > touch -r aclocal.m4 configure configure.h.in `find . -name Makefile.in`
> > and later on
> > > Prerequisite `aclocal.m4' is newer than target `Makefile.in'.
> >
> > which is the reason the build fails. This bug occurs only on sparc and
> > ia64 and is not reproducible with a manual build.
>
> Just checking in to see if this bug is still a problem. It has been
> over a year since this report. I can only imagine that if the problem
> persisted that there would be continuation in the bug log. If not is
> it okay to close this bug?
I believe that this bug is no longer an active problem. The details
of 'touch' not working only on sparc and ia64 seems strange and
probably points elsewhere other than coreutils anyway. In any case
since I believe this to no longer being an issue I am closing this
bug. If you believe otherwise or aquire additional information please
feel free to reopen the bug.
Thanks
Bob
--- End Message ---
