Thanks for sharing, I had no clue this existed! I'll take a tour when I
have some spare cycles.
As my father used to say, "Learn something new every day!" :)
-daw-
On 3/30/26 5:03 PM, Peter-Paul Kurstjens via lists.fd.io wrote:
Hey!
Clear—I can fix a server running RHEL, but the technical debt remains,
which is something that still needs to be done, and I'm not an expert
at that :-)
Nucleo -> https://copr.fedorainfracloud.org/coprs/nucleo/vpp-git/
Regular updates of all packages—which currently work perfectly (for
now) on my RHEL 9 (BGP router) production systems. I've built them
myself before, but I figured if someone is already doing it, I'm more
than happy to reuse it.
Br
Peter-Paul
On Mon, Mar 30, 2026 at 9:56 PM Dave Wallace via lists.fd.io
<http://lists.fd.io> <[email protected]> wrote:
Hi Peter-Paul,
At the present time, both human and compute resources are very
limited, so cost is always the limiting factor.
First and foremost, there needs to be a maintainer who diligently
reviews rpm build changes and actively monitors/fixes rpm build
failures.
Second, there needs to be a statement of need from a qualified
consumer of VPP -- that is a person, company, or open source
project actively and publicly participating in the FD.io community
on a regular basis and a requirements specification / proposal.
In general, the build environment is a pile of technical debt that
has been on my TODO list to clean up for several years. I'm
willing to help by merging non ubuntu/debian build env changes,
but adding the rpm build env back into the CI without cleaning up
the technical debt is not something that I would be willing to
commit to investing in.
Thanks,
-daw-
ps. What's nucleo?
On 3/30/26 3:10 PM, Peter-Paul Kurstjens via lists.fd.io
<http://lists.fd.io> wrote:
Hey Dave,
What would you need eg a list/tasks to have a permanent redhat
build env integrated as well?
Br Peter-Paul
Ps im working at redhat
Ps2 nucleo has also already rpm builds which i use as well
Op ma 30 mrt 2026, 18:37 schreef Dave Wallace via lists.fd.io
<http://lists.fd.io> <[email protected]>:
Hi Alexan,
At one point in time, Red Hat developers created, then
maintained the VPP rpm build infrastructure as part of the
CI. Later, priorities changed and the CI verification was
decommissioned. Since that time, the rpm builds have been
maintained by interested vpp consumers on an ad-hoc basis.
Given that there is no way for committers to know that a
gerrit change is working, please include a statement of
testing (e.g. 'Manually tested in local build environment by
<submitter>') in the comment section of the commit message,
apply a 'Code-review +1' in gerrit, and send email to
[email protected]. At that point, I will merge the gerrit
change.
Thank you for your contributions to FD.io/VPP!
-daw-
On 3/30/26 6:30 AM, "Feng Lei via lists.fd.io
<http://lists.fd.io> wrote:
rpm package build for kylinV11
----------
alexan
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#26922): https://lists.fd.io/g/vpp-dev/message/26922
Mute This Topic: https://lists.fd.io/mt/118576335/21656
Group Owner: [email protected]
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/14379924/21656/631435203/xyzzy
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
