Bug 492756 - Bugzilla no longer works after "yum update"
Summary: Bugzilla no longer works after "yum update"
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: bugzilla
Version: 10
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Itamar Reis Peixoto
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-03-29 10:51 UTC by Nadav Har'El
Modified: 2009-07-28 03:36 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-07-28 03:36:40 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Nadav Har'El 2009-03-29 10:51:50 UTC
Last week, after a routine "yum update", bugzilla installed on my system stopped working, giving bizarre database errors each time it is used.

After reading some documents on the web, I discovered that after an upgrade to bugzilla, one must run checksetup.pl. I ran it, and everything returned to normal.

The question is - why doesn't Fedora's bugzilla post-install script run checksetup.pl? How is the user expected to know he supposed to run this script, or even more fundamentally - that bugzilla was upgraded at all? After all, every time I run "yum update" dozens of packages get upgraded, and I don't pay attention to every one (most people probably don't even run yum update manually, and don't see the list of packages at all).

Thanks,
Nadav.

Comment 1 Itamar Reis Peixoto 2009-04-05 04:28:14 UTC
thats true, but bugzilla rpm already do this, please check

[itamar@localhost bugzilla]$ rpm -q bugzilla --scripts


postinstall scriptlet (using /bin/sh):
pushd /usr/share/bugzilla > /dev/null
./checksetup.pl > /dev/null
popd > /dev/null
[itamar@localhost bugzilla]$


I will make some tests, I will probably need to change to something like this, putting the commands inside a parentheses 


(cd /usr/share/bugzilla;
./checksetup.pl > /dev/null
)

I will test this as soon as possible.

Comment 2 Itamar Reis Peixoto 2009-07-28 03:36:40 UTC
I am closing this, if you have more problems please reopen this bug.


Note You need to log in before you can comment on or make changes to this bug.