Bug 61660 - [SW-BUG] emulators/linux_base has duplicate distinfo entry
Summary: [SW-BUG] emulators/linux_base has duplicate distinfo entry
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Trevor Johnson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-21 02:20 UTC by Paul Dlug
Modified: 2004-02-06 01:16 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Dlug 2004-01-21 02:20:09 UTC
	In emulators/linux_base/distinfo.i386 redhat-release-7.1-1.noarch.rpm is listed twice, this causes it to be endlessly re-fetched even after a successful download

MD5 (rpm/redhat-release-7.1-1.noarch.rpm) = 50c7e24be0727971a1253bb75d30a1ed
MD5 (rpm/redhat-release-7.1-1.noarch.rpm) = db4e20d62c96ae3cd7fb3d9da89f0ec0

The first checksum appears to be the correct one, at least based on the RPM I was able to fetch. Removing the second entry allows the port to build and install successfully.

Fix: 

Remove the second rpm/redhat-release-7.1-1.noarch.rpm entry from emulators/linux_base/distinfo.i386
How-To-Repeat: 	Attempt installation of emulators/linux_base
Comment 1 Joe Marcus Clarke freebsd_committer freebsd_triage 2004-01-22 02:48:03 UTC
State Changed
From-To: open->closed

This should be fixed now.  Thanks for reporting.
Comment 2 Trevor Johnson freebsd_committer freebsd_triage 2004-01-22 03:09:52 UTC
State Changed
From-To: closed->open

According to marcus, this misbehaviour is caused by recent changes 
to bsd.port.mk.  I expect that some of the Festival ports, and maybe 
others, have also been broken. 


Comment 3 Trevor Johnson freebsd_committer freebsd_triage 2004-01-22 03:09:52 UTC
Responsible Changed
From-To: freebsd-ports-bugs->trevor

I'll look into this.
Comment 4 Trevor Johnson freebsd_committer freebsd_triage 2004-02-06 01:15:52 UTC
State Changed
From-To: open->closed

This has been fixed.