From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.54) id 1FCdsU-0000mH-RV for garchives@archives.gentoo.org; Fri, 24 Feb 2006 14:25:03 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.5/8.13.5) with SMTP id k1OENVk7003433; Fri, 24 Feb 2006 14:23:31 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id k1OEJm82003564 for ; Fri, 24 Feb 2006 14:19:48 GMT Received: from [213.121.151.206] (helo=snowdrop.home) by smtp.gentoo.org with esmtpa (Exim 4.54) id 1FCdnQ-0004T6-0f for gentoo-dev@lists.gentoo.org; Fri, 24 Feb 2006 14:19:48 +0000 Received: from localhost ([127.0.0.1] helo=snowdrop.home) by snowdrop.home with esmtp (Exim 4.54) id 1FCdnM-0008LZ-Ix for gentoo-dev@lists.gentoo.org; Fri, 24 Feb 2006 14:19:44 +0000 Date: Fri, 24 Feb 2006 14:19:40 +0000 From: Ciaran McCreesh To: gentoo-dev@lists.gentoo.org Subject: [gentoo-dev] SRC_URI component naming collision Message-ID: <20060224141940.16864042@snowdrop.home> X-Mailer: Sylpheed-Claws 2.0.0 (GTK+ 2.8.12; i686-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_qtecTGvWElpJFUGORj9=GFu"; protocol="application/pgp-signature"; micalg=PGP-SHA1 X-Archives-Salt: 357b3d0c-6ab1-4a58-976f-5a5c4e6f27bc X-Archives-Hash: 719a64a0f3f4e978f9cd2f3b12e5b41e --Sig_qtecTGvWElpJFUGORj9=GFu Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Two ways this one can occur. Way the first: foo-1.0 has a file in SRC_URI called foo.pdf. Then foo-1.1 comes along, and has a different foo.pdf. Way the second: foo-1.0 has a file called examples-1.0.tar.bz2. bar-1.0 also has a file called examples-1.0.tar.bz2. To avoid this, ensure that your packages use versioned SRC_URI component names, and that the name part is something that's reasonably likely to be unique (e.g. includes the package name). Side note: if the packages in question are fetch restricted, you're screwed, and will not be able to add them to the tree. Current offenders shall be receiving bugs shortly, since That Which Shall Not Be Named now checks for this. --=20 Ciaran McCreesh : Gentoo Developer (Wearer of the shiny hat) Mail : ciaranm at gentoo.org Web : http://dev.gentoo.org/~ciaranm --Sig_qtecTGvWElpJFUGORj9=GFu Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (GNU/Linux) iD8DBQFD/xYA96zL6DUtXhERAvkcAKDSUFMR6BfwjWfj5xoJGXjJJjKthgCg5kNP 9F5q+XyJzDNXaZVbg/gh1kg= =3YJW -----END PGP SIGNATURE----- --Sig_qtecTGvWElpJFUGORj9=GFu-- -- gentoo-dev@gentoo.org mailing list