On Tue, Jan 24, 2017 at 7:44 PM, Roberto Ragusa wrote:
> On 01/21/2017 04:15 PM, Kai Engert wrote:
>> On Sat, 2017-01-21 at 15:47 +0100, Christian Dersch wrote:
>
>> The current Firefox 50.x will go unsupported on Tuesday, replaced by Firefox
>> 51.
>> Usually new
On 01/21/2017 04:15 PM, Kai Engert wrote:
> On Sat, 2017-01-21 at 15:47 +0100, Christian Dersch wrote:
> The current Firefox 50.x will go unsupported on Tuesday, replaced by Firefox
> 51.
> Usually new important security fixes are contained in the new Firefox update.
Going unsupported upstream
Now you see why I and some others asked you to wait for more testing:
https://bugzilla.redhat.com/show_bug.cgi?id=1415137 So pushing on monday
was really the wrong solution. Such things *have* to be handled more
carefully!
On 01/21/2017 04:15 PM, Kai Engert wrote:
> On Sat, 2017-01-21 at 15:47
Hi,
On 23-01-17 11:35, Martin Stransky wrote:
On 01/21/2017 04:33 PM, Christian Dersch wrote:
On 01/21/2017 04:15 PM, Kai Engert wrote:
I've disabled autokarma.
Thanks :)
The current Firefox 50.x will go unsupported on Tuesday, replaced by
Firefox 51.
Usually new important security fixes
On ma, 23 tammi 2017, Martin Stransky wrote:
On 01/21/2017 04:33 PM, Christian Dersch wrote:
On 01/21/2017 04:15 PM, Kai Engert wrote:
I've disabled autokarma.
Thanks :)
The current Firefox 50.x will go unsupported on Tuesday, replaced by
Firefox 51.
Usually new important security fixes
On 01/23/2017 11:35 AM, Martin Stransky wrote:
We should not break FreeIPA critically with that update (crashes on
start or so) for sure. But don't expect rock solid experience from
Fedora - there are RHEL/CentOS or other enterprise distros for that.
Fedora is focused mainly on new
On 01/21/2017 04:33 PM, Christian Dersch wrote:
On 01/21/2017 04:15 PM, Kai Engert wrote:
I've disabled autokarma.
Thanks :)
The current Firefox 50.x will go unsupported on Tuesday, replaced by
Firefox 51.
Usually new important security fixes are contained in the new Firefox
update.
Christian Dersch wrote:
> Autokarma just means the package will not be pushed automatically, but
> karma mechanism is still active. So once your update reached the stable
> karma level you defined, you can hit the push to stable button.
This may be true for Firefox because it is a critpath
On Sat, Jan 21, 2017 at 3:15 PM, Kai Engert wrote:
> On Sat, 2017-01-21 at 15:47 +0100, Christian Dersch wrote:
>> On 01/21/2017 03:44 PM, Christian Dersch wrote:
>> >
>> > Autokarma just means the package will not be pushed automatically, but
>> > karma mechanism is still active.
On 01/21/2017 04:15 PM, Kai Engert wrote:
I've disabled autokarma.
Thanks :)
The current Firefox 50.x will go unsupported on Tuesday, replaced by Firefox 51.
Usually new important security fixes are contained in the new Firefox update.
Unless we want to delay Firefox 51, this update must
On Sat, 2017-01-21 at 15:47 +0100, Christian Dersch wrote:
> On 01/21/2017 03:44 PM, Christian Dersch wrote:
> >
> > Autokarma just means the package will not be pushed automatically, butĀ
> > karma mechanism is still active. So once your update reached theĀ
> > stable karma level you defined,
On 01/21/2017 03:44 PM, Christian Dersch wrote:
On 01/21/2017 03:25 PM, Kai Engert wrote:
With autokarma disabled, is there a minimum test duration, before it
can get
pushed to stable?
Because we probably want to have it pushed to stable on Monday.
Autokarma just means the package will
On Sat, Jan 21, 2017 at 2:25 PM, Kai Engert wrote:
> On Sat, 2017-01-21 at 13:20 +0100, Christian Dersch wrote:
>> > > The combined updates have been submitted to testing:
>> > > F24: https://bodhi.fedoraproject.org/updates/FEDORA-2017-bbb320ba18
>> > > F25:
On 01/21/2017 03:25 PM, Kai Engert wrote:
With autokarma disabled, is there a minimum test duration, before it can get
pushed to stable?
Because we probably want to have it pushed to stable on Monday.
Autokarma just means the package will not be pushed automatically, but
karma mechanism is
On Sat, 2017-01-21 at 13:20 +0100, Christian Dersch wrote:
> > > The combined updates have been submitted to testing:
> > > F24: https://bodhi.fedoraproject.org/updates/FEDORA-2017-bbb320ba18
> > > F25: https://bodhi.fedoraproject.org/updates/FEDORA-2017-e42b513012
> > >
> > > If you can, please
On 01/21/2017 01:17 PM, Peter Robinson wrote:
> On Sat, Jan 21, 2017 at 11:57 AM, Kai Engert wrote:
>> On Fri, 2017-01-20 at 10:22 -0600, Michael Catanzaro wrote:
>>> Please just make sure they all get released in the same Bodhi update to
>>> avoid breakage.
>>
>> The combined
On Sat, Jan 21, 2017 at 11:57 AM, Kai Engert wrote:
> On Fri, 2017-01-20 at 10:22 -0600, Michael Catanzaro wrote:
>>
>> Please just make sure they all get released in the same Bodhi update to
>> avoid breakage.
>
>
> The combined updates have been submitted to testing:
> F24:
On Fri, 2017-01-20 at 10:22 -0600, Michael Catanzaro wrote:
>
> Please just make sure they all get released in the same Bodhi update to
> avoid breakage.
The combined updates have been submitted to testing:
F24: https://bodhi.fedoraproject.org/updates/FEDORA-2017-bbb320ba18
F25:
On pe, 20 tammi 2017, Kai Engert wrote:
On Fri, 2017-01-20 at 18:40 +0200, Alexander Bokovoy wrote:
FreeIPA is broken when trying to install with nss 3.28.1. We reliably
reproduce this issue with
https://bodhi.fedoraproject.org/updates/FEDORA-2017-e42b513012
It seems that new nss also breaks
On 01/20/2017 01:16 PM, Kai Engert wrote:
I've been granted the required permissions.
Good.
(Note that provenpackagers don't have access to firefox, I've been told, so
their powers wouldn't have been sufficient.)
I'm not aware of that. I pulled up the current Firefox update that is
On Fri, 2017-01-20 at 13:12 -0600, Michael Cronenworth wrote:
> On 01/20/2017 12:15 PM, Kai Engert wrote:
> > In order to create the combined update, I need commit access for all
> > involved
> > packages. The remaining piece are the commit privileges for Icecat. I've
> > requested them, but
On 01/20/2017 12:15 PM, Kai Engert wrote:
In order to create the combined update, I need commit access for all involved
packages. The remaining piece are the commit privileges for Icecat. I've
requested them, but haven't received them yet.
If we're under a time constraint I'm sure a
On Fri, 2017-01-20 at 10:22 -0600, Michael Catanzaro wrote:
> On Fri, 2017-01-20 at 16:17 +0100, Martin Stransky wrote:
> > All builds are ready except TB on arm. I'm sure we make that in time.
> >
> > Martin
>
> Please just make sure they all get released in the same Bodhi update to
> avoid
On Fri, 2017-01-20 at 18:40 +0200, Alexander Bokovoy wrote:
>
> FreeIPA is broken when trying to install with nss 3.28.1. We reliably
> reproduce this issue with
> https://bodhi.fedoraproject.org/updates/FEDORA-2017-e42b513012
>
> It seems that new nss also breaks 389-ds LDAP server's selection
On pe, 20 tammi 2017, Hubert Kario wrote:
On Friday, 20 January 2017 18:40:13 CET Alexander Bokovoy wrote:
On pe, 20 tammi 2017, Kai Engert wrote:
>Hello,
>
>we are currently dealing with a tricky situation, that the NSS and Mozilla
>package maintainers have been discussing, and I'd like to
On pe, 20 tammi 2017, Kai Engert wrote:
Hello,
we are currently dealing with a tricky situation, that the NSS and Mozilla
package maintainers have been discussing, and I'd like to publish our plan.
The most recent NSS update, version 3.28.1, is required to ship to the Firefox
51 update planned
On Fri, 2017-01-20 at 16:17 +0100, Martin Stransky wrote:
> All builds are ready except TB on arm. I'm sure we make that in time.
>
> Martin
Please just make sure they all get released in the same Bodhi update to
avoid breakage.
Michael
___
devel
On 01/20/2017 04:13 PM, Josh Boyer wrote:
On Fri, Jan 20, 2017 at 9:52 AM, Kai Engert wrote:
Hello,
we are currently dealing with a tricky situation, that the NSS and Mozilla
package maintainers have been discussing, and I'd like to publish our plan.
The most recent NSS update,
On Fri, Jan 20, 2017 at 9:52 AM, Kai Engert wrote:
> Hello,
>
> we are currently dealing with a tricky situation, that the NSS and Mozilla
> package maintainers have been discussing, and I'd like to publish our plan.
>
> The most recent NSS update, version 3.28.1, is required to
Hello,
we are currently dealing with a tricky situation, that the NSS and Mozilla
package maintainers have been discussing, and I'd like to publish our plan.
The most recent NSS update, version 3.28.1, is required to ship to the Firefox
51 update planned for January 24.
Unfortunately, NSS
30 matches
Mail list logo