pkg/49220: devel/deforaos-libsystem distfile checksum error

[kre%munnari.OZ.AU@localhost]

>Number:         49220
>Category:       pkg
>Synopsis:       devel/deforaos-libsystem distfile checksum error
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Sep 19 10:50:00 +0000 2014
>Originator:     Robert Elz
>Release:        NetBSD 6.99.30 (irrelevant) (pkgsrc current (HEAD) 2014-09-19)
>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 distinfo file for devel/deforaos-libsystem expects the
        distfile to be 60538 - the file fetched is actually 60539
        bytes ... needless to say the checksums do not match.

>How-To-Repeat:
        mv ..../distfiles/libSystem-0.2.0.tar.gz /somewhere/safe/.
        cd ..../pkgsrc/devel/deforaos-libsystem
        make checksum

>Fix:
        Find out what changed in the distfile from the version that was
        used to build the package, to the version that is being
        distributed now, and assuming the change is benign, update
        the distinfo file (given the timing of this problem compared
        with the package update, I doubt anyone but the updater has the
        original distfile, so neither a DIST_SUBDIR nor a revbump
        should be needed).   Certainly f.n.o didn't manage to fetch the
        original distfile, which suggests that it changed on the master
        site before the update to the package was actually committed.

        Should it appear that the distfile has been hacked (or similar)
        report it upstream, and put the original on f.n.o