-
Notifications
You must be signed in to change notification settings - Fork 10
Switching default OneCRL pin to 'stable' tag #127
Conversation
Mind that #123 is breaking our tests, too. We have to test locally with s/nsILocalFile/nsIFile in |
Rebased on top of #125. Tests should be passing now. |
Now that's brilliant. The OneCRL "stable" version bails out with an error:
|
I have filed mozmark/OneCRL-Tools/issues/40. There is no immediate pressure, but actually syncing up to OneCRL-Tools' stable tag was part of the milestone v3.1.2 release. Since that can't wait much longer, I am inclined to move this over to v3.1.3. |
Upstream tag has been fixed. This is now RTL. Thumbs up, @mwobensmith? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Excellent!
How embarrassing. I missed to land this one. Should be good to land, but I'd wait for OneCRL-Tools's stable tag to move to mozilla/OneCRL-Tools@3bf3462 or a later commit. |
2dce037
to
1d1881b
Compare
Rebased the patch and finally advanced OneCRL-Tools' stable tag to a commit that works in TLS Canary. Travis should finally go green on this in a couple of minutes. |
This resolves #62.