Bug 141843

Summary:	ebuild digest should have a --force option to discard existing digests
Product:	Portage Development	Reporter:	Zac Medico <zmedico>
Component:	Core - Ebuild Support	Assignee:	Portage team <dev-portage>
Status:	RESOLVED FIXED
Severity:	enhancement	CC:	flameeyes
Priority:	High	Keywords:	InVCS
Version:	2.1
Hardware:	All
OS:	All
Whiteboard:
Package list:		Runtime testing required:	---
Bug Depends on:
Bug Blocks:	136244, 142283

Description Zac Medico gentoo-dev

2006-07-26 18:40:46 UTC

Currently, existing distfiles digests are automatically assumed when local copies of the distfiles are not available in $DISTDIR.  The problem with behavior is that if the upstream distfiles change identity while keeping the same name, the user may be forced to manually remove both the Manifest and files/digest-$PF file in order to force the fetch and/or digest to occur correctly.  I propose that a --force option to be supported by the ebuild command in order to automate this process.  The --force option will simply remove the digests associated with the current ebuild (from both the Manifest and files/digest-$PF files) so that fetch and/or digest will ignore the previously existing distfiles digests.

Comment 1 Zac Medico gentoo-dev

2006-07-27 22:01:35 UTC

This is fixed in svn r4041.

Comment 2 Zac Medico gentoo-dev

2006-07-28 11:11:25 UTC

This has been released in 2.1.1_pre4.

Comment 3 Zac Medico gentoo-dev

2006-07-31 08:55:54 UTC

This is in svn r4060 for 2.1-r2.