Arch Linux

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#79032 - [gcc-go] incorrectly provides go=1.18

Attached to Project: Arch Linux
Opened by Repentinus (Repentinus) - Monday, 10 July 2023, 02:36 GMT
Last edited by freswa (frederik) - Tuesday, 11 July 2023, 11:51 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Giancarlo Razzolini (grazzolini)
freswa (frederik)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

gcc-go should currently provide go=1.17, not go=1.18, as it fails to support Go 1.18 generics.

Steps to reproduce:

Attempt to build [this Go 1.18 program](https://github.com/protocolbuffers/protoscope/tree/main) and see [gcc-go fail miserably](http://ix.io/4Ac2).
This task depends upon

Closed by  freswa (frederik)
Tuesday, 11 July 2023, 11:51 GMT
Reason for closing:  Implemented
Additional comments about closing:  Commit 992be668a57d633a83f5cc33aaa97fd28349a690

Will be released with the next gcc rebuild.
Comment by Toolybird (Toolybird) - Monday, 10 July 2023, 22:10 GMT
Related:  FS#62934 

Someone actually uses gcc-go? It's use is discouraged as per PM's comment here [1].

[1] https://bugs.archlinux.org/task/74739#comment208326
Comment by freswa (frederik) - Monday, 10 July 2023, 22:24 GMT
Is there any pkg that provides a version for its go dependency?
Comment by Morten Linderud (Foxboron) - Tuesday, 11 July 2023, 11:14 GMT
Changed some details on the request of Repentinus over IRC.
Comment by Repentinus (Repentinus) - Tuesday, 11 July 2023, 11:25 GMT
1) Had Foxboron edit the ticket as there was some 3:30 am nonsense in it before.

2) I am unaware of repo packages using versioned Go for its dependencies, but it is impossible to write a reliably working PKGBUILD for any Go package that makes use of Go 1.18 features like generics whilst this package claims to provide something it does not in fact provide. When I first came across the linked repo, I thought it was their issue as their repo declared itself to require Go 1.18 and supposedly I had Go 1.18. Why I had gcc-go, not extra/go, I do not know, but I can hardly be the only person who is generally not immersed in the Go ecosystem, but may need to build a package now and then.

Loading...