From owner-cvs-ports@FreeBSD.ORG Fri Dec 3 01:16:32 2004 Return-Path: Delivered-To: cvs-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A99E616A4CE; Fri, 3 Dec 2004 01:16:32 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6704543D2F; Fri, 3 Dec 2004 01:16:32 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 3CDF0512B2; Thu, 2 Dec 2004 17:22:04 -0800 (PST) Date: Thu, 2 Dec 2004 17:22:04 -0800 From: Kris Kennaway To: Michael Nottebrock Message-ID: <20041203012204.GA75180@xor.obsecurity.org> References: <200412022355.iB2NthIi015200@repoman.freebsd.org> <20041203003624.GA59801@xor.obsecurity.org> <41AFB9F6.7030807@gmx.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="tKW2IUtsqtDRztdT" Content-Disposition: inline In-Reply-To: <41AFB9F6.7030807@gmx.net> User-Agent: Mutt/1.4.2.1i cc: cvs-ports@FreeBSD.org cc: ports-committers@FreeBSD.org cc: Michael Nottebrock cc: cvs-all@FreeBSD.org cc: Kris Kennaway Subject: Re: cvs commit: ports/www/akregator Makefile distinfo X-BeenThere: cvs-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Dec 2004 01:16:32 -0000 --tKW2IUtsqtDRztdT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Dec 03, 2004 at 01:57:26AM +0100, Michael Nottebrock wrote: > Kris Kennaway wrote: >=20 >=20 > >touch -t should work as expected, there must have been something else > >going on here. >=20 > Can't think of anything else. >=20 > I've encountered problems with modifying timestamps in workdirs and KDE's= =20 > buildsystem before (the kdevelop port was notorious for shipping broken= =20 > distfiles which needed surgery on the file timestamps for a while and it= =20 > would work for me and everyone I could get to test, but try to regenerate= =20 > stuff on random other people's machines and/or the package cluster). I do see this kind of thing quite commonly on the package machines (dctc is another egregious offender that is often broken). It could be some kind of a race condition, e.g. ntpd steps the time backwards during the extraction; the files are mis-ordered in the distfile which causes the "input" file to have a later timestamp than the "output" file (thus make will try to rebuild it); or something more subtle [1] Kris [1] Another common bug I see (only on 4.x now, thanks to bsdtar) is that gtar thinks a file "changed as we read it" during package creation and exits with an error, when nothing should have touched that file since installation finished, prior to the start of the package creation phase. I can only guess this is either a bug in gtar, or something like softupdates updating the timestamp on the written data after the file write returned, when the gtar process may already be running. --tKW2IUtsqtDRztdT Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBr7+7Wry0BWjoQKURAoDPAKDGEqWnUimOfimwlqc0JBJArWWyZACeNyg3 k5oOUGNqmV1429LKbrfPzjk= =26Yr -----END PGP SIGNATURE----- --tKW2IUtsqtDRztdT--