I just committed a fix to master and f19-branch for dealing with the latest yum's change to the yum.config._getsysver function. There are other pending changes in both of those branches.
Is there any reason I shouldn't do new builds for rawhide, f20 and f19?
I also noticed we haven't created f20-branch yet. Is there a reason not to do that?
On Sat, Dec 21, 2013 at 01:42:05PM -0600, Bruno Wolff III wrote:
I just committed a fix to master and f19-branch for dealing with the latest yum's change to the yum.config._getsysver function. There are other pending changes in both of those branches.
Is there any reason I shouldn't do new builds for rawhide, f20 and f19?
I also noticed we haven't created f20-branch yet. Is there a reason not to do that?
I can do builds after I do another pass through my buglists to see if there is anything else worth adding. As long as master works fine for f20 and rawhide I don't see any reason to make a new branch.
On Mon, Jan 06, 2014 at 14:52:42 -0800, "Brian C. Lane" bcl@redhat.com wrote:
On Sat, Dec 21, 2013 at 01:42:05PM -0600, Bruno Wolff III wrote:
I just committed a fix to master and f19-branch for dealing with the latest yum's change to the yum.config._getsysver function. There are other pending changes in both of those branches.
Is there any reason I shouldn't do new builds for rawhide, f20 and f19?
I also noticed we haven't created f20-branch yet. Is there a reason not to do that?
I can do builds after I do another pass through my buglists to see if there is anything else worth adding. As long as master works fine for f20 and rawhide I don't see any reason to make a new branch.
OK. I'll just wait. (I've got plenty of stuff to keep me busy.)
livecd@lists.fedoraproject.org
-
Brian C. Lane -
Bruno Wolff III