Subject: pkg/19873: audio/festvox voice packages need distinfo updates
To: None <gnats-bugs@gnats.netbsd.org>
From: None <kre@munnari.OZ.AU>
List: netbsd-bugs
Date: 01/16/2003 20:26:17
>Number: 19873
>Category: pkg
>Synopsis: audio/festvox voice packages need distinfo updates
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: pkg-manager
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Jan 16 05:29:00 PST 2003
>Closed-Date:
>Last-Modified:
>Originator: Robert Elz
>Release: NetBSD 1.6K pkgsrc of 2003-01-15
>Organization:
Prince of Songkla University
>Environment:
System: NetBSD delta.cs.mu.OZ.AU 1.6K NetBSD 1.6K (DELTA) #6: Sat Dec 21 23:51:46 EST 2002 kre@delta.cs.mu.OZ.AU:/usr/src/sys/arch/i386/compile/DELTA i386
Architecture: i386
Machine: i386
>Description:
The checksums in the distinfo files for (some of) the festvox
packages ( festvox-abc festvox-jph festvox-ked16 festvox-mwm
and festvox-ogirab I believe, no guarantees it is a complete list)
are out of date wrt the files available at the master site.
What's more, it looks to have been this way for a LONG time (years)
if one can believe the file mod times at the master server (2000...)
It looks as if when the distinfo files were updated from md5 to
sha1 (yes, that long ago...) the master files had already been
changed (the old md5 checksums don't match either).
[Aside: no, I don't want to use festvox - I just like to have a
complete set of distfiles, and decided I should actually verify
all of the checksums of the files I have - the files I had in my
collection I fetched last July 31, Aug 1, so the checksums have
certainly been bad at least that long.]
Naturally, I have no grarantees that the files haven't been
spoofed, nor any inclination to find out - but one would wonder at
why anyone would bother!
Since festvox clearly gets ~0 use, perhaps its packages should
just be retired ?
>How-To-Repeat:
rm .../distfiles/voice*
cd .../pkgsrc/audio/festvox-abc
make checksum
>Fix:
make distinfo
(after the make checksum fails, and after
verifying that the current version of the correct
file was fetched)
Ideally, the files would be fetched to a version dependent
sub-directory, so old versions wouldn't attempt to be used.
>Release-Note:
>Audit-Trail:
>Unformatted: