As of today, I have built Node.js 22.2.0 for Fedora Rawhide. It is
currently available as a non-default package (Node.js 20 remains the
default during this short transition period).
If you maintain a package that depends on Node.js (either runtime or
build-time), please take some time in the next
First, let me apologize for the short notice on this. We've been
discussing it at the public ELN meetings over the last month, but I
only just now realized that I forgot to send out one of these general
announcements.
Over the last few months, you've probably seen a number of Fedora ELN
packages p
Just a heads-up that we've begun the targeted mass-rebuild for Fedora
ELN. It's running in Koji's "background" priority, so it should
hopefully not significantly impact other builds. My estimate is that
it will be running for about the next two days, followed up by manual
rebuilds for flaky tests/n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On behalf of the ELN SIG, I'd like to share with you some of our plans
for summer 2023. First, as some of you may know, we will be more
actively beginning the process of launching CentOS Stream 10. We have
made some recent changes to our strategy and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
We wanted to send out a heads-up to let folks know that once Infrastructure
Freeze is lifted this week, we will be enabling modular builds for Fedora ELN.
Once this happens, `platform:eln` will become available as a target for module
builds. For anyo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Mon, Apr 6, 2020 at 5:53 PM Stephen Gallagher wrote:
> I've just published a fourth version[1] of the ELN proposal. With a
> lot of input from Miro Hrončok, I think I've finally been able to
> clarify some of the points that w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I've just published a fourth version[1] of the ELN proposal. With a
lot of input from Miro Hrončok, I think I've finally been able to
clarify some of the points that we were getting hung up on.
Changes in this version of the proposal[2]:
* Improve
I sent out the V2 version of the Change on Friday and then promptly
managed to injure myself and be away from email until today. I've read
through the email threads again this morning and I decided that,
rather than try to address them one by one, I'd try again with a V3
that hopefully answers some
andra Fedorova]]
* Email: al...@bookwar.info
* Name: [[User:Sgallagh | Stephen Gallagher]]
* Email: sgall...@redhat.com
[1] List of changes between the original and new versions:
https://fedoraproject.org/w/index.php?title=Changes%2FELN_Buildroot_and_Compose&type=revision&diff=569655&oldid=
One of the recurring themes in the ongoing Modularity threads has been that
we've made references to the problems we're trying to solve, but we haven't
done a good job of gathering those requirements and use-cases into a single
place. To resolve this, I've written a (fairly long) blog post describi
It was discovered[1] a short while ago that, due to a packaging
mistake in the fedora-workstation-repos package, upgrades from Fedora
28->Fedora 29 would replace the /etc/yum.repos.d/*.repo files provided
from that package with their default configuration.
What this meant in practice is that anyon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
This message is directed at anyone who maintains a Node.js package in Fedora.
On Friday, FESCo approved the Fedora 29 System-Wide Change to move the default
Node.js interpreter to the 10.x LTS stream. This means that we will need to
ensure that any
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
At today's FESCo meeting, we selected a new meeting time to accommodate the
schedules of the newly-elected members. As such, FESCo meetings for the next
cycle will be taking place on Mondays at 1500 UTC (1100 EDT, 1700 CEST).
However, in the interes
colate.
If you have thoughts, I'd really like to hear them.
On Mon, Mar 26, 2018 at 8:04 AM Stephen Gallagher
wrote:
> Quick reminder to please send me your thoughts on this; I'll be collating
> them tonight and sending them out for us to discuss tomorrow.
>
>
> On T
I'm going to be submitting an update for libmodulemd today for all released
branches of Fedora. This is *technically* in conflict with the Stable
Updates Policy, but it is both necessary and should be safe to accomplish.
1) The teams that were planning to switch to it from the previous
python-modu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Modularity is Dead, Long Live Modularity!
=
See this post in glorious technicolor
at:https://communityblog.fedoraproject.org/modularity-dead-long-live-modularity/
Summary
- ---
Fedora’s Modularity initi
There was an issue[1] with GCC7 during the mass-rebuild. Despite the Fedora-wide
setting of -Werror=format-security, GCC did not process its command-line
properly and an unknown number of packages were built without this flag
appropriately set. As a result, all of those packages built successfully
On 04/01/2016 02:51 PM, Kevin Fenzi wrote:
> Greetings.
>
> Recently FPC oked the use of rich boolean deps. However, we have run
> into an issue where the tools used to push updates are not able to
> correctly handle these new dependencies.
>
> At today's FESCo meeting we decided to ask maintain
Next week, I plan to upgrade Node.js from the 4.x LTS branch to the 5.x stable
branch in Rawhide. This upgrade does break backwards-compatibility and thus will
need re-testing of modules. Also, all native NPMs (those that are built with
architecture-specific packages rather than noarch) will need t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
At the FESCo meeting on October 14th, it was decided that the time
has come to finally complete the migration away from System V init
scripts. What does this mean for you as a packager?
When we branch from Rawhide for Fedora 24 (currently scheduled
On Tue, 2015-06-02 at 09:55 +0700, Truong Anh Tuan wrote:
> - Original Message -
> > From: "Stephen Gallagher"
> > To: "Server SIG" ,
> > desk...@lists.fedoraproject.org,
> > devel-announce@lists.fedoraproject.org,
> > cl...@lists.f
== Overview ==
Back at the beginning of the Fedora.next initiative when we created the
working groups, we tasked them with creating "Product Requirement
Documents" (PRDs) to guide the development of each of these core
groups.
* https://fedoraproject.org/wiki/Workstation/Workstation_PRD
*
http
This past week, David Strauss chose to step down from his position on
the Fedora Server Working Group, citing a lack of alignment with his
current work usage. The Fedora Server SIG would like to thank David for
his contributions up to this point and wish him well.
This means that there is currentl
As the $SUBJECT says, tomorrow we go into the two-week Final Freeze for
Fedora 21. That means that you need to have all of the packages that you
want to see land in Fedora 21 submitted for stable by the end of the day
*today*. After that point, we will initiate the Final Freeze Policy,
where you wi
== tl;dr Version ==
We are accelerating the Fedora 21 schedule so that we will enter Final
Freeze one week earlier than previously described on the schedule
page[1]. This means that all fixes intended for inclusion in the Fedora
21 release must be submitted for the stable repository no later than
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/23/2014 10:01 AM, Dennis Gilmore wrote:
...
> As testing progresses, common issues are tracked on the Fedora
> wiki: https://fedoraproject.org/wiki/Common_F20_bugs
This should have been:
https://fedoraproject.org/wiki/Common_F21_bugs
-BEGIN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
tl;dr: FESCo needs to know what is going to need extra time to deliver
Fedora.next in the Fedora 21 cycle.
Now that the Fedora.next product PRDs have been approved, the next
phase is to plan our execution. First of all, this will mean planning
out ho
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The first deliverable that the Fedora Server Working Group was tasked
with was the production of a Product Requirements Document. This
document is intended to provide a high-level view of the goals and
primary deliverables of the Fedora Server distribu
. Ultimately, the voting membership
will be the ones to make (and vote on) final decisions, particularly
in the case of controversy or disagreement. This should never be done
without careful consideration of all the facts.
The initial voting membership was selected by the FESCo coordinator
(me, S
29 matches
Mail list logo
