On 08/28/2017 11:06 AM, Eyal Lebedinsky wrote:
On 28/08/17 11:14, Ed Greshko wrote:
On 08/28/2017 08:59 AM, Ed Greshko wrote:
On 08/28/2017 08:56 AM, Eyal Lebedinsky wrote:
True, but I do build packages at times. Nevertheless, I can always reinstall the dependencies when needed, so I'll bite now and see how it goes.
Still, it is probably a good idea to fix the root cause...
Oh, it will be fixed....probably sooner than later.
Oh, shoot....
I just realized (can't keep numbering straight) that the problem you were seeing isn't the same problem that existed earlier last week.
You could have enabled the updates-testing repo an installed firefox-55.0.2-3 ....
Sorry about that.
Thanks again,
I actually think that enabling the updates-testing repo is introducing new risks that I prefer to stay away from. Many years ago I liked to live on the cutting edge, with all that it brings, but these days I can do without the extra "excitement".
I am OK to wait for the stable ff package.
cheers
OK.... But the only differences between the new releases was to correct the issues with nspr. So, the risk to update on single package is pretty much 0.
* Thu Aug 24 2017 Martin Stransky stransky@redhat.com - 55.0.2-3 - Enable to build with nspr-4.16.
* Wed Aug 23 2017 Martin Stransky stransky@redhat.com - 55.0.2-2 - Rebuilt to remove wrong dependency to nspr-4.16.
* Fri Aug 18 2017 Martin Stransky stransky@redhat.com - 55.0.2-1 - Updated to 55.0.2
* Mon Aug 14 2017 Jan Horak jhorak@redhat.com - 55.0.1-1 - Update to 55.0.1