Red Hat Bugzilla – Bug 614147
Fails on f13
Last modified: 2011-06-01 13:57:40 EDT
Description of problem:
Does not run, appears to require Python 2.5 which is not in the repository
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install through Add/remove programs, then type gget at prompt
This is my experience as well.
[torstein@Desktor ~]$ gget
/usr/bin/env: python2.5: Ingen slik fil eller filkatalog
The same on F14.
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '13'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 13's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 13 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Still broken in both F15 and Rawhide. Please change the Version to either 15 or rawhide, or make this a FutureFeature. If this can't even be run, there's no point in continuing to package it.
[andre@compaq-pc ~]$ gget
/usr/bin/env: python2.5: No such file or directory
Closing as a dup of bug 702159, as that latter bug has more information on a possible fix for this bug.
*** This bug has been marked as a duplicate of bug 702159 ***