FS#53476 - mention the actual pkgver value when it has a bad value

Attached to Project: Pacman
Opened by lilydjwg (lilydjwg) - Tuesday, 28 March 2017, 02:18 GMT
Task Type Bug Report
Category makepkg
Status Unconfirmed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 5.0.1
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

Summary and Info:

It'll be better to show the actual value of the bad value so the error is obvious. I have a script to update and build packages. When it does something wrong with pkgver (it usually happens when upstreams change version string format), I can't easily see why it's wrong.

I know I can show it from my script, but wouldn't it be better to just include it in the error message?

Steps to Reproduce:

Edit a PKGBUILD to contain a bad value, then run

$ LANG=C updpkgsums
==> ERROR: pkgver is not allowed to contain colons, hyphens or whitespace.
==> ERROR: An unknown error has occurred. Exiting...
==> ERROR: Failed to generate new checksums
This task depends upon

Loading...