5489: Make release: tar on Windows 11 "option --force-local is not supported" - Composr CMS feature tracker

ID	Project	Category	View Status	Date Submitted	Last Update

5489	Composr alpha bug reports	General / Uncategorised	public	2023-12-06 16:24	2024-07-31 19:07

Reporter	PDStig	Assigned To	Chris Graham
Priority	normal	Severity	major
Status	assigned	Resolution	open

Summary	5489: Make release: tar on Windows 11 "option --force-local is not supported"
Description	Later builds of Windows 10, and Windows 11, come with their own tar which does not support --force-local. This causes make-release to fail. However, we can't just assume everyone building Composr on Windows has the Windows tar which doesn't support --force-local, so we can't remove it. But we also can't assume vice versa, so we can't just leave it in there either. Modify make_release to handle both cases.
Tags	No tags attached.
Attach Tags	(Separate by ",")

Sponsorship open

Date Added	Member	Amount Sponsored

PDStig 2023-12-06 17:14 administrator ~8104	temporary fix via https://gitlab.com/composr-foundation/composr/-/commit/0ab6279a603337319fcc11995679482c22ad87bb I added a force_local get parameter. Must be specified and = 1 to put --force-local in the tar command on Windows.

Chris Graham 2024-07-31 19:07 administrator ~9020	I think it's reasonable to assume core developers are running a newer version of Windows. The constituency is now just 1, it's reasonable to have a higher baseline for developers, it's reasonable for us to not even officially document it for core development situations like this that are just dealing with legacy situations. I'd just add a code comment saying "Tested to work on Windows version xxx, known to not run on versions older than yyy due to not having tar bundled."

View Status	Private (for security issues or disclosing of private information; if you submit as a guest, you will not be able to see your submission)
Note
Upload Files Maximum size: 32,768 KiB	Attach files by dragging & dropping, selecting or pasting them.
You are not logged in	You are not logged in. This means you will not get any e-mail notifications. And if you reply, we will not know for sure you are the original poster of the issue.

Date Modified	Username	Field	Change
2023-12-06 16:24	PDStig	New Issue
2023-12-06 16:24	PDStig	Status	Not Assigned => Assigned
2023-12-06 16:24	PDStig	Assigned To	=> Chris Graham
2023-12-06 17:14	PDStig	Note Added: 0008104
2024-07-31 19:07	Chris Graham	Note Added: 0009020