Bug 245363 - MASTER_SITES=SF/ fails to fetch a correct tarball
Summary: MASTER_SITES=SF/ fails to fetch a correct tarball
Status: Closed Works As Intended
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Ports Framework (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Port Management Team
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-04-04 23:18 UTC by Yuri Victorovich
Modified: 2020-04-05 13:22 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 Yuri Victorovich freebsd_committer 2020-04-04 23:18:28 UTC
Testcase: misc/crosti

MASTER_SITES=SF/crosti/crosti%20${DISTVERSION}/ used to work, but then at some point began fetching a file with a different size, which led this port to become unfetchable.

MASTER_SITES=https://managedway.dl.sourceforge.net/project/crosti/crosti%201.14.0/ , however, still fetches the same tarball.

I had no choice but setting this URL as MASTER_SITES to unbreak the port.
Comment 1 Tobias Kortkamp freebsd_committer 2020-04-05 06:17:07 UTC
> I had no choice but setting this URL as MASTER_SITES to unbreak the port.

That does not seem to have solved the problem:

$ make checksum
===>  License GPLv2+ accepted by the user
===>   crosti-1.14.0_1 depends on file: /usr/local/sbin/pkg - found
=> crosti-1.14.0-source.zip doesn't seem to exist in /home/tobias/distfiles/.
=> Attempting to fetch https://managedway.dl.sourceforge.net/project/crosti/crosti%201.14.0/crosti-1.14.0-source.zip
fetch: https://managedway.dl.sourceforge.net/project/crosti/crosti%201.14.0/crosti-1.14.0-source.zip: size mismatch: expected 671143, actual 661721

Is this really a general problem or has crosti just rerolled
crosti-1.14.0-source.zip ?  I do not see it in other ports using SF.
Comment 2 Mathieu Arnold freebsd_committer 2020-04-05 13:22:10 UTC
Tested a few ports, this only happens for crosti.

Their distfile changed, probably got rerolled or something.  In any way, not a framework issue.