Description of problem:
Bugzilla appears to be missing the "maxima" component for Extras. It has been
added to the Extras "owners/owners.list", so should now appear as a selectable
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Click on
2. Search for "maxima"
No "maxima" component appears
"Maxima" component appears
Elliot, can you take a look at this?
There was an error in the URL I originally posted for the component list. Of
course, I *meant* this:
Please expedite this. There is a serious bug in maxima-gui (see bug #167870)
that needs to be reported properly.
Rex, I was wondering, maybe you could try removing the maxima entry in the
owners.list file in CVS and recommiting it? Perhaps it missed being added to
the component list, because it was being at the same time a cron job was being
run or somesuch. Either way it shouldn't hurt.
I fear that no new components are being added, I just checked some recent CVS
commits to owners.list at:
and several new components have been added since "maxima", including
"nautilus-search-tool" and "tomoe", which also don't show up the list of Extras
*** Bug 167870 has been marked as a duplicate of this bug. ***
Add e-mail address of person watching bug #167870, so they can follow updates.
Retitling summary, and updating severity, to reflect a wider problem beyond just
maxima. It appears that Bugzilla components added at least as far back as
August 31 aren't in bugzilla, see nedit and cproto added here:
These don't appear in the list of components, or in the drop-down lists when
entering a Fedora Extras bug. Don't know how far back this problem goes.
Elliot is on vacation until sometime next week, I am attempting to investigate,
waiting on some info.
Still no movement on this bug? There are some major bugs in maxima that need to
be filed, it would be good if these Bugzilla components could be created soon.
Also, what is the difference between the Bugzilla statuses "NEEDINFO" and
Change component to "Other", not really about the Account System itself.
Sopwith is back, reassigning.
It appears that some of these older components have now been created. The last
added Bugzilla components are already over 35 hours old, perl-Class-DBI-Loader
is is now in the list of components and was added in this diff, over 35 hours ago:
Is there any way the creation of Bugzilla components can be speeded up? Over 30
hours seems like far too long a time to wait especially if security related bugs
that may need to be filed shortly after a package is built and deployed.
Confirmed that cproto and nedit bugzilla components were added.
Yep those older ones have since been added, but none have been added since
perl-Class-DBI-Loader component was added over 35 hours ago. Is this done by a
cron job or somesuch? Either way it should run more frequently.
(In reply to comment #15)
> Either way it should run more frequently.
For example, python-mygthy was added 31 hours ago:
But does not yet appear in the list.
Still no updates on python-mygthy! New components don't appear to be being
added. Please look into this ASAP, nobody can file bugs on new packages. I
consider this a security issue, switching severity. Please bump up the
According to Elliot:
this was a problem with the machine running the cron job, which is now fixed.
Have verified that the last component created was "colorscheme" 40 hours ago.
Will leave this bug open until components added 6 hours ago (like "ks3switch")
get created, just to make sure cron job is working properly, then I will close
This cron job doesn't seem to be working, last update was colorscheme, which was
now over 2 days ago (surely it runs more frequently than that!), none of the
have yet made it into bugzilla. Please kick this cron job and/or machine again.
Last component added to CVS was tagtool 19hrs ago and is now in the Bugzilla
interface, so assuming that the cron job is working again. Closing bug for now.
If more long delays for Extras Bugzilla component creation/modification occur,