Aleksandra Fedorova wrote:
> Hi, Chris,
>
> On Fri, Jan 10, 2020 at 4:29 PM Chris Adams wrote:
>>
>> Once upon a time, Aleksandra Fedorova said:
>> > Similarly to what Josh said, we want to setup an environment for
>> > experiments. It doesn't mean that things we experiment on are going to
>>
On Thu, Jan 16, 2020 at 02:09:45PM +0100, Aleksandra Fedorova wrote:
>
> While on one hand we don't need a long-term storage for development
> builds, on the other: it is quite valuable to be able to compare the
> latest successful build with some previous ones to see if we actually
> improve
On Thu, Jan 16, 2020 at 7:46 AM Neal Gompa wrote:
>
> On Thu, Jan 16, 2020 at 8:43 AM Justin Forbes wrote:
> >
> > On Thu, Jan 16, 2020 at 7:11 AM Neal Gompa wrote:
> > >
> > > On Thu, Jan 16, 2020 at 8:01 AM Aleksandra Fedorova
> > > wrote:
> > > >
> > > > Hi, Chris,
> > > >
> > > > On Fri,
On Thu, Jan 16, 2020 at 8:43 AM Justin Forbes wrote:
>
> On Thu, Jan 16, 2020 at 7:11 AM Neal Gompa wrote:
> >
> > On Thu, Jan 16, 2020 at 8:01 AM Aleksandra Fedorova
> > wrote:
> > >
> > > Hi, Chris,
> > >
> > > On Fri, Jan 10, 2020 at 4:29 PM Chris Adams wrote:
> > > >
> > > > Once upon a
On Thu, Jan 16, 2020 at 7:11 AM Neal Gompa wrote:
>
> On Thu, Jan 16, 2020 at 8:01 AM Aleksandra Fedorova
> wrote:
> >
> > Hi, Chris,
> >
> > On Fri, Jan 10, 2020 at 4:29 PM Chris Adams wrote:
> > >
> > > Once upon a time, Aleksandra Fedorova said:
> > > > Similarly to what Josh said, we want
On Thu, Jan 16, 2020 at 8:01 AM Aleksandra Fedorova wrote:
>
> Hi, Chris,
>
> On Fri, Jan 10, 2020 at 4:29 PM Chris Adams wrote:
> >
> > Once upon a time, Aleksandra Fedorova said:
> > > Similarly to what Josh said, we want to setup an environment for
> > > experiments.
> > > It doesn't mean
On Mon, Jan 13, 2020 at 5:18 PM Kevin Fenzi wrote:
>
> On Mon, Jan 13, 2020 at 10:52:32AM +0100, Florian Weimer wrote:
> > * Kevin Fenzi:
> >
> > > Can packages built in this buildroot be used on the same system with
> > > packages from the normal buildroot?
> >
> > Yes, I expect them to be
Hi, Chris,
On Fri, Jan 10, 2020 at 4:29 PM Chris Adams wrote:
>
> Once upon a time, Aleksandra Fedorova said:
> > Similarly to what Josh said, we want to setup an environment for
> > experiments.
> > It doesn't mean that things we experiment on are going to be merged in
> > Fedora. And it
On Friday, January 10, 2020 6:37:11 AM MST Chris Adams wrote:
> AVX2 is not a reasonable requirement as a replacement for the current
> Fedora x86_64, as there are CPUs still being made today that don't
> support that.
Relevant lines from /proc/cpuinfo
flags : fpu vme de pse tsc msr
On Friday, January 10, 2020 8:09:18 AM MST Aleksandra Fedorova wrote:
> We are not proposing the new architecture. We are proposing a "staging
> environment" for the current architecture. Which can be used for
> experiments which currently can not be performed without disrupting
> the release and
I have some concerns about this proposal. Given that this change was
essentially unanimously rejected, this line stood out to me:
> * As soon as feature is accepted by the community, there will be a
> smooth process to update baseline in the main Fedora, as all packages
> will be already
On Fri, Jan 10, 2020 at 04:09:18PM +0100, Aleksandra Fedorova wrote:
> Based on the impact described above, I wouldn't consider the change
> system-wide.
>
> But I think we touch an interesting topic here: It seems our
> definition of Change is quite limited and focused on packaged changes.
>
On Mon, 2020-01-13 at 10:52 +0100, Florian Weimer wrote:
> * Kevin Fenzi:
>
> > Can packages built in this buildroot be used on the same system with
> > packages from the normal buildroot?
>
> Yes, I expect them to be compatible at the interface level because the
> flags do not directly alter
On Mon, Jan 13, 2020 at 10:52:32AM +0100, Florian Weimer wrote:
> * Kevin Fenzi:
>
> > Can packages built in this buildroot be used on the same system with
> > packages from the normal buildroot?
>
> Yes, I expect them to be compatible at the interface level because the
> flags do not directly
* Kevin Fenzi:
> Can packages built in this buildroot be used on the same system with
> packages from the normal buildroot?
Yes, I expect them to be compatible at the interface level because the
flags do not directly alter calling conventions. There could be a
slowdown mixing package versions,
On Thu, Jan 09, 2020 at 12:16:17PM -0500, Ben Cotton wrote:
> https://fedoraproject.org/wiki/Changes/Additional_buildroot_to_test_x86-64_micro-architecture_update
>
> == Summary ==
>
> Create a dedicated buildroot to test packages built with x86-64
> micro-architecture update.
So, a few
On Fri, 2020-01-10 at 11:05 +0100, Florian Weimer wrote:
> * Neal Gompa:
>
> > On Fri, Jan 10, 2020 at 4:28 AM Florian Weimer wrote:
> > > We do not want to change the RPM architecture, so that users still can
> > > install third-party software. This means that we need to change the
> > > dist
Once upon a time, Aleksandra Fedorova said:
> Similarly to what Josh said, we want to setup an environment for experiments.
> It doesn't mean that things we experiment on are going to be merged in
> Fedora. And it definitely doesn't mean that whatever we did in the
> experimental environment can
On Fri, Jan 10, 2020 at 3:56 PM Chris Adams wrote:
>
> Once upon a time, Aleksandra Fedorova said:
> > No. Afaik, the main reason the change was rejected is that we are not
> > ready yet (or don't see yet the reason) for the update of the
> > architecture. And the benefit of such an update is
On Fri, Jan 10, 2020 at 3:56 PM Chris Adams wrote:
>
> Once upon a time, Aleksandra Fedorova said:
> > No. Afaik, the main reason the change was rejected is that we are not
> > ready yet (or don't see yet the reason) for the update of the
> > architecture. And the benefit of such an update is
On Fri, Jan 10, 2020 at 9:16 AM Zbigniew Jędrzejewski-Szmek
wrote:
>
> On Thu, Jan 09, 2020 at 05:23:16PM -0500, Ben Cotton wrote:
> > On Thu, Jan 9, 2020 at 5:03 PM Zbigniew Jędrzejewski-Szmek
> > wrote:
> > >
> > > 4. This certainly needs to be a "system wide change" with the related
> > >
Once upon a time, Josh Boyer said:
> As an experiment. To see if it actually has real, tangible benefit.
I guess my biggest issue with it is the proposal does nothing to address
the harm of the original proposal (namely, that Fedora would no longer
support some brand-new hardware). To me, it
On Fri, Jan 10, 2020 at 9:13 AM Chris Adams wrote:
>
> Once upon a time, Josh Boyer said:
> > I don't believe that is fair or even true. The premise of the new
> > change is to allow alternative experimentation within Fedora proper
> > without impacting the mainline distribution. There is no
Once upon a time, Aleksandra Fedorova said:
> No. Afaik, the main reason the change was rejected is that we are not
> ready yet (or don't see yet the reason) for the update of the
> architecture. And the benefit of such an update is unclear.
I disagree that that was the reason - the fact that
Hi, Chris,
On Fri, Jan 10, 2020 at 2:37 PM Chris Adams wrote:
>
> Once upon a time, Aleksandra Fedorova said:
> > The rejected change
> > https://fedoraproject.org/wiki/Changes/x86-64_micro-architecture_update
> > is explicitly referenced from the current one. So yes, it is the
> > architecture
Once upon a time, Josh Boyer said:
> I don't believe that is fair or even true. The premise of the new
> change is to allow alternative experimentation within Fedora proper
> without impacting the mainline distribution. There is no assumption
> that the results will magically replace Fedora in
On Fri, Jan 10, 2020 at 8:37 AM Chris Adams wrote:
>
> Once upon a time, Aleksandra Fedorova said:
> > The rejected change
> > https://fedoraproject.org/wiki/Changes/x86-64_micro-architecture_update
> > is explicitly referenced from the current one. So yes, it is the
> > architecture update we
Once upon a time, Aleksandra Fedorova said:
> The rejected change
> https://fedoraproject.org/wiki/Changes/x86-64_micro-architecture_update
> is explicitly referenced from the current one. So yes, it is the
> architecture update we are looking for.
>
> And I would suggest to avoid calling things
On Fri, Jan 10, 2020 at 5:05 AM Florian Weimer wrote:
>
> * Neal Gompa:
>
> > On Fri, Jan 10, 2020 at 4:28 AM Florian Weimer wrote:
> >>
> >> We do not want to change the RPM architecture, so that users still can
> >> install third-party software. This means that we need to change the
> >> dist
* Neal Gompa:
> On Fri, Jan 10, 2020 at 4:28 AM Florian Weimer wrote:
>>
>> We do not want to change the RPM architecture, so that users still can
>> install third-party software. This means that we need to change the
>> dist tag to avoid confusion.
>>
>
> Changing the RPM architecture does not
On Fri, Jan 10, 2020 at 4:28 AM Florian Weimer wrote:
>
> We do not want to change the RPM architecture, so that users still can
> install third-party software. This means that we need to change the
> dist tag to avoid confusion.
>
Changing the RPM architecture does not necessarily mean that
Le ven. 10 janv. 2020 à 10:29, Florian Weimer a écrit :
>
> * Neal Gompa:
>
> > 1. Our builder resources are squeezed enough as it is. In doing this,
> > are we going to get more machines so that we can have more builders?
> > Between modules and this, I worry our resources will get squeezed far
* Neal Gompa:
> 1. Our builder resources are squeezed enough as it is. In doing this,
> are we going to get more machines so that we can have more builders?
> Between modules and this, I worry our resources will get squeezed far
> too tightly for my comfort.
Please send me the required hardware
Hi, Neal,
On Thu, Jan 9, 2020 at 10:01 PM Neal Gompa wrote:
>
> On Thu, Jan 9, 2020 at 12:17 PM Ben Cotton wrote:
> >
> > https://fedoraproject.org/wiki/Changes/Additional_buildroot_to_test_x86-64_micro-architecture_update
> >
> > == Summary ==
> >
> > Create a dedicated buildroot to test
On Thu, Jan 09, 2020 at 05:23:16PM -0500, Ben Cotton wrote:
> On Thu, Jan 9, 2020 at 5:03 PM Zbigniew Jędrzejewski-Szmek
> wrote:
> >
> > 4. This certainly needs to be a "system wide change" with the related
> >additional info required for such changes. We certainly need releng
> >to sign
On Thu, Jan 9, 2020 at 3:03 PM Zbigniew Jędrzejewski-Szmek
wrote:
> Those are all good points. To add more:
>
> 4. This certainly needs to be a "system wide change" with the related
>additional info required for such changes. We certainly need releng
>to sign off on this.
>
> 5.
On Thu, Jan 9, 2020 at 5:03 PM Zbigniew Jędrzejewski-Szmek
wrote:
>
> 4. This certainly needs to be a "system wide change" with the related
>additional info required for such changes. We certainly need releng
>to sign off on this.
>
Apart from potential capacity impacts, this seems
On Thu, Jan 09, 2020 at 03:59:41PM -0500, Neal Gompa wrote:
> On Thu, Jan 9, 2020 at 12:17 PM Ben Cotton wrote:
> >
> > https://fedoraproject.org/wiki/Changes/Additional_buildroot_to_test_x86-64_micro-architecture_update
> >
> > == Summary ==
> >
> > Create a dedicated buildroot to test packages
On Thu, Jan 9, 2020 at 12:17 PM Ben Cotton wrote:
>
> https://fedoraproject.org/wiki/Changes/Additional_buildroot_to_test_x86-64_micro-architecture_update
>
> == Summary ==
>
> Create a dedicated buildroot to test packages built with x86-64
> micro-architecture update.
>
> == Owner ==
>
> * Name:
https://fedoraproject.org/wiki/Changes/Additional_buildroot_to_test_x86-64_micro-architecture_update
== Summary ==
Create a dedicated buildroot to test packages built with x86-64
micro-architecture update.
== Owner ==
* Name: [[User:bookwar| Aleksandra Fedorova]]
* Email:
https://fedoraproject.org/wiki/Changes/Additional_buildroot_to_test_x86-64_micro-architecture_update
== Summary ==
Create a dedicated buildroot to test packages built with x86-64
micro-architecture update.
== Owner ==
* Name: [[User:bookwar| Aleksandra Fedorova]]
* Email:
41 matches
Mail list logo
