can use it as an opportunity to show what we do, but also to teach how
we do it. For example OpenStack has a bot which replies on every
GitHub issue and pull-request to the read-only mirrored repository
with a manual on how one can send the same change through the
OpenStack development process. We
s new alternate buildroot. You might apply a patch to the package
> in the spec conditional on the new dist tag. That patch should go
> upstream right? So it works with both normal rawhide and the new flags?
>
> kevin
> ____
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
/archives/list/devel@lists.fedoraproject.org/thread/IFBHS2WKKPKJH6H54OX4DV3U7A4XYOPU/
--
Aleksandra Fedorova
bookwar
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code
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 b
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 b
with RelEng[1]
> > and they will discuss what work is necessary for this at the next
> > meeting.
> >
> > [1] https://pagure.io/releng/issue/9154
>
> OK, thanks.
>
--
Aleksandra Fedorova
bookwar
___
devel mailing list -- devel@lists.f
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
> Create a dedicated buildroot to test packages built with x86-64
> > micro-architecture update.
> >
> > == Owner ==
> >
> > * Name: [[User:bookwar| Aleksandra Fedorova]]
> > * Email: [mailto:al...@bookwar.info al...@bookwar.info]
> > * Name: [[User:
On Mon, 6 Jan 2020, 18:32 Kamil Paral, wrote:
> On Sun, Jan 5, 2020 at 12:43 PM Aleksandra Fedorova
> wrote:
>
>> I wonder, how I as a user going to be informed about the
>> earlyoom-event? I assume abrt will recognize the crash? Will it be
>> easily v
On Sun, Jan 5, 2020 at 12:39 AM Chris Murphy wrote:
>
> On Sat, Jan 4, 2020 at 2:51 AM Aleksandra Fedorova wrote:
>
> > Since in the Change we are not introducing just the earlyoom tool but
> > enable it with a specific profile I would add those details here. Smth li
On Sun, Jan 5, 2020 at 10:18 AM Zbigniew Jędrzejewski-Szmek
wrote:
>
> On Sat, Jan 04, 2020 at 04:38:19PM -0700, Chris Murphy wrote:
> > On Sat, Jan 4, 2020 at 2:51 AM Aleksandra Fedorova
> > wrote:
> >
> > > Since in the Change we are not introducing just th
rnel.org/doc/gorman/html/understand/understand016.html
>
> == Release Notes ==
> Earlyoom service is enabled by default, which will cause kernel
> oom-killer to trigger sooner. To revert to previous behavior:
> {{code|sudo systemctl disable earlyoom.service}}
>
> And to customize
sant.
>
> It's better to light a candle than curse the darkness.
>
> Writing a script that automates figuring out how many candles are
> needed (and where) is also better than cursing the darkness.
>
I am so going to make a poster on my wall with this message.
Thank you, Dave.
--
currently shadowing non-modular packages (since they have
> default streams), but I understand this is getting fixed. This means
> that the non-modular Java packages (especially maven, ant, xmvn, their
> dependencies, and other packages which are used for building Java RPM
> packages in fed
ularity is not relevant to this conversation,
I filed the issue for Fedora Infrastructure [1] with the proposal how
I think we can fix it.
[1] https://pagure.io/fedora-infrastructure/issue/8390
--
Aleksandra Fedorova
bookwar
___
devel mailing list -- dev
e of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
--
Aleksandra Fedorova
bookwar
___
On Wed, Nov 13, 2019 at 1:25 AM Kevin Kofler wrote:
>
> Aleksandra Fedorova wrote:
> > 1) I don't think Modularity is about being LTS and "enterprisy".
> > Lifecycle differences are not the only feature Modularity provides.
> >
> > I see Modularity
On Wed, Nov 13, 2019 at 12:00 AM Miro Hrončok wrote:
>
> On 12. 11. 19 18:25, Aleksandra Fedorova wrote:
> > On Tue, Nov 12, 2019 at 5:10 PM Miro Hrončok wrote:
> >>
> >> On 12. 11. 19 17:02, Aleksandra Fedorova wrote:
> >>> Again, no one forces y
On Tue, Nov 12, 2019 at 7:03 PM Aleksandar Kurtakov wrote:
>
>
>
> On Tue, Nov 12, 2019 at 7:55 PM Aleksandra Fedorova
> wrote:
>>
>> Hi, Aleksandar,
>>
>> On Tue, Nov 12, 2019 at 6:40 PM Aleksandar Kurtakov
>> wrote:
>> >
>> >
Hi Stephen,
On Tue, Nov 12, 2019 at 6:40 PM Stephen John Smoogen wrote:
>
> On Tue, 12 Nov 2019 at 12:26, Aleksandra Fedorova wrote:
> >
> > On Tue, Nov 12, 2019 at 5:10 PM Miro Hrončok wrote:
> > >
> > > On 12. 11. 19 17:02, Aleksandra Fedorova wrote:
>
Hi, Aleksandar,
On Tue, Nov 12, 2019 at 6:40 PM Aleksandar Kurtakov wrote:
>
>
>
> On Tue, Nov 12, 2019 at 7:31 PM Aleksandra Fedorova
> wrote:
>>
>> On Tue, Nov 12, 2019 at 5:10 PM Miro Hrončok wrote:
>> >
>> > On 12. 11. 19 17:02, Aleksandra Fe
On Tue, Nov 12, 2019 at 5:10 PM Miro Hrončok wrote:
>
> On 12. 11. 19 17:02, Aleksandra Fedorova wrote:
> > Again, no one forces you or any other packager to use modularity
> > tooling right now.
> >
> > As Fedora developer you have a choice to join the effort, brin
Hi, Igor,
On Tue, Nov 12, 2019 at 4:20 PM Igor Gnatenko
wrote:
>
> On Tue, Nov 12, 2019, 14:13 Aleksandra Fedorova wrote:
>>
>> Hi,
>>
>> On Tue, Nov 12, 2019 at 10:50 AM Dominik 'Rathann' Mierzejewski
>> wrote:
>> >
>> > Hi.
>> >
l_.
Anyway, default streams is just one side of a story. It did get into
the critical path of Fedora and did create upgrade problems and
certain UX issues, but I think we can restrict and resolve it.
For that we need to focus on the issue, which is, from my point of
view: default st
to join the Python SIG appreciation thread.
The group does outstanding work indeed, and the impact is clearly
visible in Fedora and outside of it.
Thank you, everyone involved!
--
Aleksandra Fedorova
bookwar
___
devel mailing list -- devel@lists.fedoraprojec
t a joint effort and file one change for both
rpminspect and annocheck?
[1] https://github.com/rpminspect/rpminspect
[2] https://www.youtube.com/watch?v=lPxC185PBeI
[3] https://fedoraproject.org/wiki/SIGs/CI
[4] https://apps.fedoraproject.org/calendar/SIGs/2019/11/4/#m9
l to ambassadors-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/ar
cations are due
>> > soon and I'd like to see us coordinate again with our friends in CentOS.
>> > Is there anyone interested in owning this? If so, can you put together a
>> > proposal for Mindshare?
>> >
>> > regards,
>> >
>> &g
submit a proposal for the same on
> Mindshare. If anyone else would be leading, I would be happy to help
> as well. :D
--
Aleksandra Fedorova
bookwar
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to dev
Hi,
On Mon, Oct 7, 2019 at 7:53 PM Zbigniew Jędrzejewski-Szmek
wrote:
>
> On Mon, Oct 07, 2019 at 05:38:51PM +0200, Aleksandra Fedorova wrote:
> > On Mon, Oct 7, 2019 at 5:21 PM Michael Catanzaro
> > wrote:
> > >
> > > On Mon, Oct 7, 2019 at 3:11 pm, An
On Mon, Oct 7, 2019 at 5:21 PM Michael Catanzaro wrote:
>
> On Mon, Oct 7, 2019 at 3:11 pm, Ankur Sinha
> wrote:
> > So I guess I am arguing that while the "new package for existing
> > maintainers" remain at the `fedpkg` level of doing things, the "join
> > the
> > package collection
Hi,
On Mon, Oct 7, 2019 at 4:12 PM Ankur Sinha wrote:
>
> On Mon, Oct 07, 2019 12:56:51 +, Zbigniew Jędrzejewski-Szmek wrote:
> > On Mon, Oct 07, 2019 at 12:13:34PM +0100, Ankur Sinha wrote:
> > > On Mon, Oct 07, 2019 12:16:28 +0200, Vít Ondruch wrote:
> > > > If you would like to have
I created a wiki page [1] to collect notes. Feel free to contribute.
[1] https://fedoraproject.org/wiki/User:Bookwar/fedocal_notes
--
Aleksandra Fedorova
bookwar
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email t
ce interactive
calendar on top of it.
[1] https://pagure.io/fedora-infrastructure/issue/8274
[2] https://opendev.org/opendev/irc-meetings/
[3] https://fullcalendar.io/docs/events-array
--
Aleksandra Fedorova
bookwar
___
devel mailing list -- devel@list
Hi, Ralf,
one of the goals of the change process (mailing list announcements and
discussion we have right here) is to identify various impacts of the
change and also to find better wording for it (including the title).
So you shouldn't feel cheated, just contribute your thoughts and
suggest the
On Wed, Jun 19, 2019 at 10:29 AM Vít Ondruch wrote:
>
>
> Dne 18. 06. 19 v 16:54 Aleksandra Fedorova napsal(a):
> > On Tue, Jun 18, 2019 at 1:31 PM Neal Gompa wrote:
> >> On Tue, Jun 18, 2019 at 5:21 AM Aleksandra Fedorova
> >> wrote:
> >>> Hi,
>
Sorry, missed part of the sentence.
> There are several ways how one can implement it. I would personally
> prefer pull requests to dist-git over scratch builds. I think it is
> important to keep some visibility in the system, so that not just the
> owner of a change, but also random lurkers can
On Tue, Jun 18, 2019 at 1:31 PM Neal Gompa wrote:
>
> On Tue, Jun 18, 2019 at 5:21 AM Aleksandra Fedorova
> wrote:
> >
> > Hi,
> > On Tue, Jun 18, 2019 at 3:05 AM Neal Gompa wrote:
> > >
> > > On Mon, Jun 17, 2019 at 8:53 PM Kevin Fenzi wrote:
>
Hi,
On Tue, Jun 18, 2019 at 3:05 AM Neal Gompa wrote:
>
> On Mon, Jun 17, 2019 at 8:53 PM Kevin Fenzi wrote:
> >
> > On 6/17/19 4:47 PM, Kevin Kofler wrote:
> > > Kevin Fenzi wrote:
> > >> I disagree. I think we need gating to block as much stuff that breaks
> > >> things from landing as we can
On Tue, May 28, 2019 at 12:15 PM Aleksandra Fedorova wrote:
>
> Hi, all,
>
> I created a poll for the meeting time http://whenisgood.net/kdd4zmq
> Please add you votes.
As we have nonoverlapping meeting requirements, making it work for
everyone is impossible. Let's choose the
, fas groups..
* Open floor
--
Aleksandra Fedorova
bookwar
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List
platform.
Virtualization, containerization and many other tools available in Fedora
provide a good foundation to build flexible, open and modern CI solutions
and CI architectures on top of it. Let's make use of them.
--
Aleksandra Fedorova
bookwar on IRC
Hi, Mikolaj,
On Fri, Mar 29, 2019 at 10:24 AM Mikolaj Izdebski
wrote:
> On Thu, Mar 28, 2019 at 7:46 PM Christopher
> wrote:
> >
> > On Thu, Mar 28, 2019 at 9:50 AM Mikolaj Izdebski
> wrote:
> > > - javapackages-tools, stream 201801 (buildroot-only module, not
> > > intended to be delivered
to prevent them, suggest guidelines
on how to decide whether or not one should move package to the module -
topics like that.
It extends the scope, but it also opens some possibilities for us to work
on the root cause.
What do you think?
--
Aleksandra Fedorova
bookwar
ere on the Change page.
Generally, I think that the Change itself is a content, which requires
versioning, review and collaborative editing, and it fits much better to be
the source code rather than the issues workflow.
[1] http://docs.getpelican.com/en/3.6.3/content.html
--
Aleksandra Fedoro
101 - 146 of 146 matches
Mail list logo
