From owner-freebsd-ports Thu Nov 30 12:10: 6 2000 Delivered-To: freebsd-ports@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 9486837B400 for ; Thu, 30 Nov 2000 12:10:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id eAUKA3970146; Thu, 30 Nov 2000 12:10:03 -0800 (PST) (envelope-from gnats) Date: Thu, 30 Nov 2000 12:10:03 -0800 (PST) Message-Id: <200011302010.eAUKA3970146@freefall.freebsd.org> To: freebsd-ports@FreeBSD.org Cc: From: Johann Visagie Subject: Re: ports/23193: Port fix: biology/emboss (MAINTAINER) Reply-To: Johann Visagie Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR ports/23193; it has been noted by GNATS. From: Johann Visagie To: Peter Pentchev Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: ports/23193: Port fix: biology/emboss (MAINTAINER) Date: Thu, 30 Nov 2000 22:01:37 +0200 > Do you by any chance keep the old distfiles, so you can check what has > changed? Not that it's all that uncommon to reroll dist tarballs without > notice (I've had that happen to fetchmail on me just the other day), but > sometimes this could be an indication of backdoored distributions on > compromised distsites.. It never hurts to be sure - that's just why > the distfiles MD5 sums were introduced in the first place, I should think :) Hmm, valid point! And yes, I was silly enough to delete the old distfiles after ensuring that the new ones build and appear to work. However, I was just in touch with the EMBOSS project leader, and apparently those distributions were indeed recreated due to a minor bug. So it all appears to be above board. *phew* Thanks for pointing this out; I won't make that mistake again. :-) -- Johann To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message