Description of problem: The version of pcbnew in kicad won't open more recent projects (e.g. https://github.com/macpod/lasershark_hardware). Can we have the latest stable version packaged? Version-Release number of selected component (if applicable): kicad-2012.01.19-2.rev3256.fc18.x86_64
Amen, the KiCad packaged with Fedora is now nearly 18 months old. KiCad has undergone huge changes since then! Please can we have a refresh?
kicad-2013.06.11-1.rev4021.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/kicad-2013.06.11-1.rev4021.fc17
kicad-2013.06.11-1.rev4021.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/kicad-2013.06.11-1.rev4021.fc18
kicad-2013.06.11-1.rev4021.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/kicad-2013.06.11-1.rev4021.fc19
kicad-2013.06.11-1.rev4021.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/kicad-2013.06.11-1.rev4021.el6
Package kicad-2013.06.11-1.rev4021.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kicad-2013.06.11-1.rev4021.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-11537/kicad-2013.06.11-1.rev4021.fc19 then log in and leave karma (feedback).
kicad-2013.06.11-1.rev4021.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
kicad-2013.06.11-1.rev4021.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
kicad-2013.06.11-1.rev4021.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
kicad-2013.06.11-1.rev4021.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.