FS#79753 - [terragrunt] --version information does not match package version

Attached to Project: Arch Linux
Opened by Josh (joshaw) - Friday, 22 September 2023, 11:23 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:19 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Christian Rebischke (Shibumi)
Levente Polyak (anthraxx)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

The method for setting the version string when building terragrunt appears to have recently changed, ref: https://github.com/gruntwork-io/terragrunt/commit/73d2c831bdae08aee7bc5df1d04165e0c7d5554e#diff-76ed074a9305c04054cdebb9e9aad2d818052b07091de1f20cad0bbac34ffb52

This means the version is not currently reported correctly:

$ terragrunt --version
terragrunt version latest

$ pacman -Qi terragrunt
Name : terragrunt
Version : 0.50.14-1

The --version information being wrong isn't too much of a problem, but this also breaks the `terraform_version_constraint` (https://terragrunt.gruntwork.io/docs/reference/config-blocks-and-attributes/#terragrunt_version_constraint) feature as that compares the current version to a string, and the current version is incorrect.

Additional info:
* package version(s): 0.50.14-1
* config and/or log files etc.
* link to upstream bug report, if any

Steps to reproduce:
This task depends upon

Closed by  Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:19 GMT
Reason for closing:  Moved
Additional comments about closing:  https://gitlab.archlinux.org/archlinux/p ackaging/packages/terragrunt/issues/1
Comment by loqs (loqs) - Friday, 22 September 2023, 14:43 GMT
Does rebuilding terragrunt with the attached diff applied resolved the issue for you?
   PKGBUILD.diff (0.5 KiB)
Comment by Josh (joshaw) - Friday, 22 September 2023, 15:22 GMT
That change does resolve the issue, yes. Thanks.
Comment by Josh (joshaw) - Wednesday, 01 November 2023, 14:13 GMT
This issue is still present in the most recently updated version of the package - 0.53.0-1.

Loading...