From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1NrSdr-0004S4-QS for garchives@archives.gentoo.org; Tue, 16 Mar 2010 09:00:47 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 49E22E0B8C; Tue, 16 Mar 2010 09:00:10 +0000 (UTC) Received: from mail.digimed.co.uk (82-69-83-178.dsl.in-addr.zen.co.uk [82.69.83.178]) by pigeon.gentoo.org (Postfix) with ESMTP id 004E4E0B8C for ; Tue, 16 Mar 2010 09:00:09 +0000 (UTC) Received: from digimed.co.uk (grunthos.digimed.co.uk [192.168.1.4]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.digimed.co.uk (Postfix) with ESMTPSA id 4A2944FA329 for ; Tue, 16 Mar 2010 09:00:09 +0000 (GMT) Date: Tue, 16 Mar 2010 09:00:03 +0000 From: Neil Bothwick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] what's wrong with rsync 3.0.6? Message-ID: <20100316090003.6bbbf83b@digimed.co.uk> In-Reply-To: <20100316010021.4a18bfdc@karnak.local> References: <20100316010021.4a18bfdc@karnak.local> Organization: Digital Media Production X-Mailer: Claws Mail 3.7.5cvs33 (GTK+ 2.18.7; i686-pc-linux-gnu) X-GPG-Fingerprint: 7260 0F33 97EC 2F1E 7667 FE37 BA6E 1A97 4375 1903 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/v5EFvB3xAfkwh8W8ODktXNH"; protocol="application/pgp-signature" X-Archives-Salt: b2336552-c370-4ca7-add6-76dfee930286 X-Archives-Hash: 566d98bbc59cebdca1dcc5cb4712de37 --Sig_/v5EFvB3xAfkwh8W8ODktXNH Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Tue, 16 Mar 2010 01:00:21 +0000, David W Noon wrote: > >As do the log files in $PORT_LOGDIR, they contain exactly the same > >output you would see in the terminal. =20 >=20 > Not quite. The sequence in which the ebuilds were run is lost when the > discrete logs are your only source of tracing through, although one > could attempt to reconstruct it using the timestamps in the file names > of the ebuild logs. genlop -l gives you that, in a more useful format. > They also do not contain the results of the "pretend > depclean" that occurs at the end of an emerge job. Do you means the autoclean? That never picks up anything here. I think it only will if you have an unclean system. >Moreover, they do > not contain the report of the number of configuration files that need > updating by. > cfg-update (or the like). You can get that at the end of any emerge command. Parsing all that information in one large email without missing anything important sounds like a nightmare. I prefer each warning in a separate mail that I can mark as read when I have dealt with that particular issue, but each to their own. --=20 Neil Bothwick I used to live in the real world, but I got evicted. --Sig_/v5EFvB3xAfkwh8W8ODktXNH Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) iEYEARECAAYFAkufSJgACgkQum4al0N1GQPqbwCfcC5NhRnP+F55joDReDZxkhxy Ro8An3yqNlK3qEiQG6vFHIHqab5Q7lnY =plBW -----END PGP SIGNATURE----- --Sig_/v5EFvB3xAfkwh8W8ODktXNH--