Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 02 Jan 2022 00:37:53 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 260870] sqlite3 does not download when the year advances.
Message-ID:  <bug-260870-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D260870

            Bug ID: 260870
           Summary: sqlite3 does not download when the year advances.
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs@FreeBSD.org
          Reporter: henri.de.veer@gmail.com

Today (Jan 2st, 2022) I wanted to update the sqlite3 package
(/usr/ports/databases/sqlite3).

I found out that the download link in the Makefile points to:
https://www.sqlite.org/${%Y:L:gmtime}/ (as one example, all other links use=
 a
similar construction)

This means it tries to download it from .../2022/... but nothing is there y=
et,
so the download breaks!



The issue here is that a policy decision at the sqlite makers to use a year=
 in
its links now causes the build of the port to break, example link to the sr=
c:
https://www.sqlite.org/2021/sqlite-amalgamation-3370100.zip

So maybe create a list of download mirrors that use the current year AND as
alternative a link with "year-1". Ofcourse still not completely bulletproof=
 but
anyhow better, this scheme also breaks if nothing changes in sqlite3 for at
least a year.

Workaround: Temporary change the Makefile variable MASTER_SITE from
'${%Y:L:gmtime}' to '2022' to get it to work.

uname -a:
FreeBSD srv08.cashdns.com 12.2-RELEASE-p1 FreeBSD 12.2-RELEASE-p1 GENERIC=20
amd64

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-260870-7788>