Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#69113 - [rgbds] [0.4.2-2] Wrong version number constants

Attached to Project: Community Packages
Opened by Eldred Habert (ISSOtm) - Saturday, 26 December 2020, 00:39 GMT
Last edited by Doug Newgard (Scimmia) - Saturday, 26 December 2020, 13:13 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
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 wrong version number is reported, including in code (__RGBDS_PATCH__), failing some builds.

```
issotm@sheik-kitty ~/pokered% pacman -Q rgbds
rgbds 0.4.2-2
issotm@sheik-kitty ~/pokered% rgbasm -V
rgbasm v0.4.1
issotm@sheik-kitty ~/pokered% make compare
rgbasm -o rgbdscheck.o rgbdscheck.asm
ERROR: rgbdscheck.asm(12):
pokered requires rgbds 0.4.2 or newer.
make: *** [Makefile:72: rgbdscheck.o] Error 1
```

Manually cloning, `git checkout v0.4.2`, `cmake` etc. produces correct executables. Since the 0.4.2 tag was force-pushed at some point, maybe the package just needs to be rebuilt?
This task depends upon

Closed by  Doug Newgard (Scimmia)
Saturday, 26 December 2020, 13:13 GMT
Reason for closing:  Not a bug
Comment by loqs (loqs) - Saturday, 26 December 2020, 00:48 GMT
I can not reproduce your results. Installing the package produces the following on my system:

pacman -Q rgbds
rgbds 0.4.2-2
rgbasm --version
rgbasm v0.4.2
Comment by Doug Newgard (Scimmia) - Saturday, 26 December 2020, 00:54 GMT
what does `type -a rgbasm` give you?
Comment by Eldred Habert (ISSOtm) - Saturday, 26 December 2020, 01:13 GMT
```
rgbasm is /usr/bin/rgbasm
rgbasm is /bin/rgbasm
```
I will try reinstalling...
Comment by Eldred Habert (ISSOtm) - Saturday, 26 December 2020, 01:16 GMT
Reinstalling after syncing db's worked. Probably just a fluke. Sorry for the false alarm!

Loading...