Pacman

Historical bug tracker for the Pacman package manager.

The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues

This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
Tasklist

FS#26278 - [pacman 4.0.0rc2 git][makepkg] ERROR: pkgver is not allowed to contain colons, hyphens or whitespace

Attached to Project: Pacman
Opened by Keshav Amburay (the.ridikulus.rat) - Wednesday, 05 October 2011, 15:30 GMT
Last edited by Dan McGee (toofishes) - Wednesday, 05 October 2011, 15:37 GMT
Task Type Bug Report
Category makepkg
Status Closed
Assigned To No-one
Architecture All
Severity Very Low
Priority Normal
Reported Version git
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Summary and Info:

==> ERROR: pkgver is not allowed to contain colons, hyphens or whitespace.

Problem occurs with https://aur.archlinux.org/packages/go/google-chrome-dev/PKGBUILD due to

pkgver=16.0.899.0 # Check for new Linux releases in: http://googlechromereleases.blogspot.com/search/label/Dev%20updates

Also

pkgver='16.0.899.0' # Check for new Linux releases in: http://googlechromereleases.blogspot.com/search/label/Dev%20updates

or

pkgver="16.0.899.0" # Check for new Linux releases in: http://googlechromereleases.blogspot.com/search/label/Dev%20updates

do not work (same error).

Is this the intended behaviour or a bug in makepkg?
This task depends upon

Closed by  Dan McGee (toofishes)
Wednesday, 05 October 2011, 15:37 GMT
Reason for closing:  Won't fix
Additional comments about closing:  Patches welcome.
Comment by Dan McGee (toofishes) - Wednesday, 05 October 2011, 15:37 GMT
Move the comment to a different line. We're not going to kludge to fix an issue that has a dead-simple workaround.
Comment by Keshav Amburay (the.ridikulus.rat) - Wednesday, 05 October 2011, 15:49 GMT
My question is - Is this the SUPPOSED (NEW) BEHAVIOUR?

[QUOTE from https://aur.archlinux.org/packages.php?ID=27031 - comments in descending order]

Comment by: Det on Thu, 29 Sep 2011 08:04:37 +0000

Then it's a pacman bug and you should report it to the actual pacman developers (while the thing is still a release candidate).

Comment by: skodabenz on Wed, 28 Sep 2011 15:53:27 +0000

@Det:

keshav_pr@my-system ~/Desktop/google-chrome-dev % makepkg
==> ERROR: pkgver is not allowed to contain colons, hyphens or whitespace.

makepkg from pacman 4.0.0 RC2.

Comment by: Det on Sat, 24 Sep 2011 08:56:52 +0000

@skodabenz, or you should just start using a better AUR tool (or at least notify the maintainer).

("pkgver='15.0.874.21' # Check [..]" should be enough anyway. It doesn't need to be separated into 2 different lines.)

Comment by: skodabenz on Sat, 24 Sep 2011 07:24:19 +0000

ERROR: pkgver is not allowed to contain colons, hyphens or whitespace.

Should change

pkgver=15.0.874.21 # Check for new Linux releases in: http://googlechromereleases.blogspot.com/search/label/Dev%20updates

to

## Check for new Linux releases in: http://googlechromereleases.blogspot.com/search/label/Dev%20updates
pkgver="15.0.874.21"

[/QUOTE]

Loading...