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#10628 - kino needs a patch and to be updated to 1.3.0
Attached to Project:
Arch Linux
Opened by christopher rogers (godane) - Tuesday, 10 June 2008, 22:19 GMT
Last edited by Eduardo Romero (kensai) - Tuesday, 08 July 2008, 23:04 GMT
Opened by christopher rogers (godane) - Tuesday, 10 June 2008, 22:19 GMT
Last edited by Eduardo Romero (kensai) - Tuesday, 08 July 2008, 23:04 GMT
|
DetailsDescription:
kino 1.2.0 and 1.3.0 will not compile on gcc 4.3 without this patch here: http://bugs.gentoo.org/attachment.cgi?id=147524 This patch fixes the problem with compiling kino 1.3.0. Since the patch is for kino 1.2.0 i think its affected too. Additional info: * package version(s) 1.2.0 and 1.3.0 * config and/or log files etc. Steps to reproduce: download kino PKGNAME put in folder makepkg --asroot (i run in root when i compile) |
This task depends upon
Closed by Eduardo Romero (kensai)
Tuesday, 08 July 2008, 23:04 GMT
Reason for closing: Fixed
Additional comments about closing: Kino has been upgraded to the latest version, and yes, the patch for gcc 2.3 was useful indeed.
Tuesday, 08 July 2008, 23:04 GMT
Reason for closing: Fixed
Additional comments about closing: Kino has been upgraded to the latest version, and yes, the patch for gcc 2.3 was useful indeed.
http://aur.archlinux.org/packages.php?ID=17430
I will delete it when the package is fix and updated.
I did a quick search on kino's bugtracker and I couldn't find a bugreport like this one, so please report it to them so that the fix may be included in the next (maintenance) release.
http://sourceforge.net/tracker/?group_id=14103&atid=114103