https://bugzilla.novell.com/show_bug.cgi?id=766778
https://bugzilla.novell.com/show_bug.cgi?id=766778#c15
Jan Matejek changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |RESOLVED
InfoProvider|jmatejek@suse.com |
Resolution| |FIXED
--- Comment #15 from Jan Matejek 2012-08-13 15:53:44 UTC ---
i checked-in the SR, un-breaking Factory is more important at this point.
This still leaves the possibility of breakage if a subpackage of python.spec
gets updated and doesn't pull the corresponding libpython or python-base.
I don't really see a way out. Defining "custom release" symbol and propagating
it through all specs could work, as this would make the new packages require a
non-auto-generated value and thus they'd be different every time this value
changed. But it would be error-prone and pain to maintain, which i'm trying to
avoid here, not to mention that it partially defeats the purpose of
build-compare.
I guess we'll have to keep it at that and hope that no more cross-package
changes happen in a bugfix release.
I'm closing the bug as this specific issue is fixed; if any of you have
suggestions on how to solve this, please comment.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.