On Sat, Jun 10, 2023 at 4:36 PM Kevin Kofler via devel
wrote:
> Considering that Fedora buildroots always get killed off within days of the
> EOL, I do not see why you are keeping epel-6 buildroots active 2½ years (!)
> after its EOL.
Well, EL6 ELS support is still available for (around)
another
# Fedora Quality Assurance Meeting
# Date: 2023-06-12
# Time: 15:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.libera.chat
Greetings testers!
It's meeting time again!
If anyone has any other items for the agenda, please reply to this
email and
Pavel Raiskup wrote:
> I'm not strongly against anything; but rather than weaker policy for
> everything I slightly prefer keeping the _stricter default policy_ with
> _disabled gpgcheck for EL6_ (we should phase epel-6 out entirely anyway
> since it's long time EOL, but we still keep it for the di
Yes, but all rpm distros could use of it and in theory it could be extended to
non-rpms as well if you used the right abstraction layer.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproje
Hello!
I have updated contingency plan:
https://fedoraproject.org/wiki/Changes/BuildJdkOncePackEverywhere#Contingency_Plan
/
https://fedoraproject.org/w/index.php?title=Changes%2FBuildJdkOncePackEverywhere&type=revision&diff=679828&oldid=679493
Sorry for not writing this out of the box. It was
On Fri, 09 Jun 2023 21:22:44 -
Reon Beon via devel wrote:
> It it atomaticly add/update the spec file when more files are added
> in the right places in the spec file?
So, are you suggesting that a neural network be trained on all existing
spec files in fedora, and then used to automatically
Announcing the creation of a new nightly release validation test event
for Fedora 39 Rawhide 20230610.n.0. Please help run some tests for this
nightly compose if you have time. For more information on nightly
release validation testing, see:
https://fedoraproject.org/wiki
