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!
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!
FS#37924 - [ogre] New dependency on gcc-go
Attached to Project:
Community Packages
Opened by Philipp (hollunder) - Wednesday, 27 November 2013, 07:36 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Monday, 02 December 2013, 00:53 GMT
Opened by Philipp (hollunder) - Wednesday, 27 November 2013, 07:36 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Monday, 02 December 2013, 00:53 GMT
|
DetailsDescription:
Ogre now depends on gcc-go, but it is unclear why. As far as I know, ogre is still written in C++, not go. Additional info: * package version(s) ogre 1.9.0-1 |
This task depends upon
Closed by Sven-Hendrik Haase (Svenstaro)
Monday, 02 December 2013, 00:53 GMT
Reason for closing: Fixed
Additional comments about closing: ogre-1.9.0-2
Monday, 02 December 2013, 00:53 GMT
Reason for closing: Fixed
Additional comments about closing: ogre-1.9.0-2
Comment by Sven-Hendrik Haase (Svenstaro) -
Wednesday, 27 November 2013, 09:52 GMT
You are correct, though this was currently the only way to package ogre. There is a packaging bug (https://bugs.archlinux.org/task/37928) in gcc-libs where libatomic is in gcc-go instead of in gcc-libs. I will remove this dependency after libatomic moves to gcc-libs in a week or so. Will keep this bug open till then.