Description of problem:
No such file or directory at Bugzilla/Install/Filesystem.pm line 485."
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. remove previous failed install of bugzilla
2. create new database for bugzilla (note: I'm not using "bugs")
3. "yum install bugzilla" with db info in /etc/bugzilla/localconfig
the install of bugzilla attempts to connect to the DB, and acts surprised that it can't; "rpm -e bugzilla" left the "/etc/bugzilla/localconfig" file so I just filled it in. Recommend making the error a little more meaningful, since it might confuse people who are just installing the package. No mention of running checksetup.pl is mentioned, for instance.
Creating the contrib directory caused the install to just hang; commenting out the connect info in /etc/bugzilla/localconfig and then installing caused it to complete the install. At that point I set the connect info again, ran checksetup.pl, and it worked fine.
Which is to say, the contrib directory (/usr/share/bugzilla/contrib) should be created by the package.
note that due to the fact that the install hangs when the contrib directory exists, I can't think of a way that the install would actually be successful if it runs checksetup.pl? I'd recommend just displaying text at the end of the package install that tells the user to run the script.
I imagine that the "hanging" was really the checksetup.pl script prompting me for an admin email, but since I don't get all of stdout during a yum install, I wasn't seeing it. This is the reason I suggest just not running checksetup.pl in the post-install section (assuming) of the rpm at all; just have the user run it after.
Same problem from cron, when yum-cron updated bugzilla to bugzilla-3.4.7-1.fc12.noarch.
No such file or directory at Bugzilla/Install/Filesystem.pm line 485, <DATA>
Although it's present in rpm package, this error was displayed. Is it possible, that it was displayed before file was moved?
bugzilla-3.6.2-1.fc14 has been submitted as an update for Fedora 14.
bugzilla-3.4.8-2.fc13 has been submitted as an update for Fedora 13.
bugzilla-3.4.8-1.fc12 has been submitted as an update for Fedora 12.
bugzilla-3.4.8-1.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update bugzilla'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/bugzilla-3.4.8-1.fc12
bugzilla-3.6.2-1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
bugzilla-3.4.8-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.
bugzilla-3.4.8-2.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
I am still having this problem on Fedora ARM F13 beta. Bugzilla in that release is 3.4.5, so it doesn't have this fix.
For anyone in this situation, a workaround is: