Re: file bugs to bugzilla from anaconda

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Chris Lumens wrote:
* bugUrl doesn't have to be a bugzilla instance.  And are the XML-RPC
methods being used even available at other bugzilla instances?  There
probably needs to be a way to say that this bug instance "supports"
things filed in this manner.
  * Maybe this should be rolled in to the question of what to do about
product.img

After talking with Will for a while, an idea has begun to form in my
head.  As we've already discussed elsewhere in this thread, different
products use entirely different bug reporting systems.  Therefore we
probably need some sort of abstract layer on top of python-bugzilla that
hides all the details.

This layer could define some base class that doesn't actually do
anything.  Then, the anaconda install classes could hold a reference to
their bug reporting class.  The default BaseInstallClass uses the
useless base bug reporting class.  Our more interesting install classes
make use of the Bugzilla class.  This holds all the information about it
being a supported method, XML-RPC works, etc.

We could even toss the install class file in a product.img that sits
alongside the stage2.img like we were discussing, if that makes things
easier.  I don't really know how to make this work with the tree
composition scripts in anaconda, though.  Ideas?  Am I just going crazy?

Doesn't sound entirely crazy. It'd be just like the package install backends now as the install backend gets chosen by the installclass. Maybe it does make sense to make these sorts of things more explicit, though, and specified via some other file rather than just being "figured out" through the install class. But that cna be a second step

* Should think hard about the right things to hash on.  Especially given
different products using the same/similar anaconda

Okay, what are your thoughts about what we should hash on?  If you're
concerned that various products are going to have the same bug and those
end up getting duped when they should be separate, we can always add the
productName into the hash.

productName is the obvious one. I'm also not sure how relevant or not the different versions are. eg, should a Fedora 9 bug be a dupe of a Fedora 8 one? anaconda-11.4.0.87 vs anaconda-11.4.0.86 should almost certainly be a dupe though

Jeremy

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list

[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux