pkg/49552: net/dhcpcd-gtk distfile checksum error

[kre%munnari.OZ.AU@localhost]

>Number:         49552
>Category:       pkg
>Synopsis:       net/dhcpcd-gtk distfile checksum error
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Jan 10 01:40:00 +0000 2015
>Originator:     Robert Elz
>Release:        NetBSD 6.99.30 (irrelevant) pkgsrc current 2015-01-09
>Organization:
	Prince of Songkla University
>Environment:
System: NetBSD munnari.OZ.AU 6.99.30 NetBSD 6.99.30 (MUNNARI-DomU) #0: Mon Feb 3 19:19:20 ICT 2014 kre%onyx.coe.psu.ac.th@localhost:/usr/obj/current/kernels/amd64/MUNNARI-DomU amd64
Architecture: x86_64
Machine: amd64
>Description:
	The upgrade from 0.7.3 to 0.7.5 a couple of days ago
	(of net/dhcpcd-gtk - or dhcpcd-ui as the distfile is called)
	seems to have resulted in an incorrect checksum/size in the
	distinfo file

>How-To-Repeat:
	cd ..../pkgsrc/net/dhcpcd-gtk
	make checksum

		It might be necessary to move a current copy of the
		distfile away first

>Fix:
	Normally this indicates (most commonly) that the upstream maintainers
	changed the distfile after a copy was fetched by the pkgsrc
	maintainer (whether before or after it was committed to pkgsrc).
	Here however, as I understand it, upstream and pkgsrc maintainers
	are the same person, so it is hard to see how that could have
	happened.

	So perhaps the less common situation has occurred, and the distfile
	has been hacked ?

	In any case, if the new distfile is as it should be, then if
	anyone using pkgsrc could have ever fetched the older version,
	a DIST_SUBDIR will be needed, and a revbump.   That would happen
	if the distfile changed after pkgsrc was updated.  On the other
	hand, if the distfile was updated before pkgsrc was updated
	(and just the wrong checksum/size were put into the distinfo
	file) then just fixing distinfo will be all that is needed.