s means that they have less time to fix when things break,
let alone re-engineer away some of that tech debt. It seems like we should
be able to automate the simple cases (adding F34 and F35 branches should be
even easier, since we don't have the "is it in EL?" question even).
atically now" or "Oh, this is in EL, sorry"*. What are the
other cases?
* I'm very sad that this isn't "So, would you like to do it anyway, and then
make a module?", but c'est la vie
--
Matthew Miller
Fedora Project Leader
_
n-default repo
available but not enabled by default, it could be optional to mirror and
probably still be okay.
--
Matthew Miller
Fedora Project Leader
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to
On Thu, Nov 25, 2021 at 05:20:00PM +0100, Leon Fauster wrote:
> >I mean, seriously, RH should make this easy for Fedora packagers.
>
> +1
> and COPR and mock packagers in general.
Yes, but _I_ only have one lever. :)
--
Matthew Miller
Fedora
should make this easy for Fedora packagers.
--
Matthew Miller
Fedora Project Leader
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://d
On Wed, Nov 17, 2021 at 01:43:59PM -0500, Josh Boyer wrote:
> Further RHEL 9 documentation will center around the 'dnf' moniker,
> eventually transitioning away from yum.
Thus completing my long, slow loss of this argument. :)
Oh well! dnf it is!
--
Matthew Miller
Fedor
n that RHEL minor updates
have required EPEL packages to be rebuilt, or EPEL packages built on the
latest to not install on older point-releases of RHEL? I'm sure it happens
occasionally, but it's not the typical case.
--
Matthew Miller
Fedor
ferent than non-responsive
> package maintainers. Fedora package maintainers don't have to do anything
> with EPEL if they don't want to, thus we needed it to be a bit different.
Thanks for the correction, Troy. I'll remember this for the next time!
--
M
EPEL8 build of
> pdsh. I would be happy to become the maintainer of the EPEL builds for
> pdsh.
If reaching out to them directly isn't getting results, there is the
non-responsive maintainer process:
https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintai
o this is no different from what happens with the status quo when
an update happens in a RHEL minor release which requires an EPEL package
change.
--
Matthew Miller
Fedora Project Leader
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.
eps would be the same other than the name and
> where it points for it's repo.
Makes sense to me!
--
Matthew Miller
Fedora Project Leader
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an em
ok at Rocky Linux and CloudLinux. And, you know, the Oracle
one. And Amazon Linux. And all of the source code is 100% available.
But also, ironic or not, EPEL is already built on RHEL.
--
Matthew Miller
Fedora Project Leader
___
epel-devel mailing list --
orrectly,
> is slowly worked-around by CentOS-only packages).
As I understand it, these are available as part of "CodeReady Linux Builder"
with the developer subscription.
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/package_manifest/codereadylinuxbuilde
uld be made easy enough that it isn't
painful for EPEL packagers.
--
Matthew Miller
Fedora Project Leader
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fe
p it shouldn't be too much extra work. This does seem like a good use case
for it!
--
Matthew Miller
Fedora Project Leader
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedora
uot;EPEL for Stream". (epel-for-stream? epel-4-stream? epel4s? no not that
last one for sure.)
--
Matthew Miller
Fedora Project Leader
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@list
and understand than anything else I can
think of. So I'm willing to tackle the red tape and legal work if
that's the blocker.
--
Matthew Miller
Fedora Project Leader
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubs
e day before.
Hi Troy. Can you let me know if the modular-versions proposal is on an
upcoming agenda?
--
Matthew Miller
Fedora Project Leader
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-deve
would be fine also.
These should all be fine. In the case of 2, it's just now another alternate
non-default stream. It would only override if explicitly asked for.
--
Matthew Miller
Fedora Project Leader
___
epel-devel mailing list -- epel-
efix also makes it immediately obvious that a stream is EPEL and not
product or supported.
--
Matthew Miller
Fedora Project Leader
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel
if the module is
explicitly enabled.
--
Matthew Miller
Fedora Project Leader
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fed
odules, but it is functionally possible.
--
Matthew Miller
Fedora Project Leader
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
which stubs in a similar way the perl and some
> other modules do.
No, this is not the case. If the module isn't enabled its packages will just
be ignored. It's only if you enable the module that you get the RPMs from
that module.
--
Matthew Miller
Fedora Project Leader
ule for this
to work.)
What do you think?
*
https://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies#Packaging_Guidelines_and_Policies_for_EPEL
--
Matthew Miller
Fedora Project Leader
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To
that the Red Hat security team and Red
Hat developers do to develop fixes should be available to paying customers
first. That seems reasonable to me. Also, of course, many such fixes have
embargo dates and _can't_ be made public early. The mechanisms for doing
this aren't actually built yet.
rt,
and then once we have modular EPEL up and running you could migrate packages
to that.
--
Matthew Miller
Fedora Project Leader
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedo
> We can also potentially run a mass-rebuild at this time to help
> identify issues early.
I don't think 8.x+1 betas are going to always be a thing if CentOS Stream is
successful. Also, I'm not sure this helps at all except splitting what's
broken in time between RHEL and CentOS S
t's changing, but the net sum of changes over a six month period is
exactly equal to the net sum of changes from one RHEL minor release to the
next.
--
Matthew Miller
Fedora Project Leader
___
epel-devel mailing list -- epel-devel@lists.fedoraproj
am and RHEL will be always there.
I think if we changed EPEL Playground to build against CentOS Stream, we'd
just move the bifurcation problem rather than solving it. I kind of think we
need _both_ epel8 and epel8-playground built against both RHEL and CentOS
Stream. But I'd love to hear bette
;t necessarily need to do that, if we want to include a
different version of the package as an alternate module stream. (Sometimes
the RHEL versions have reduced functionality, or maybe we want to offer
newer versions.)
--
Matthew Miller
Fedora
a module -- at least when
we get the details around that worked out.
--
Matthew Miller
Fedora Project Leader
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
F
N DESIGN does not allow me to request it
> send me a reminder of my username.
Yeah, we know. As I understand it, aa replacement for FAS (the account
system) is a high-priority infrastructure project for this year.
Sorry for the frustrating experience, and thank you for your feedback on it.
--
Ma
I don't have a problem with it.. I just didn't see it as
> inside of what we influenced.
That's all fair too. I just don't want to undershoot, either. :)
--
Matthew Miller
Fedora Project Leader
___
epel-devel mailing list -- epel-d
Community?
> > Extra Packages Including Community?
> > Extra Packages for Interprise Community? (Or "EPEC"?)
> Extra Packages for Introverted Communities
Extroverted Packages for Introverted Communities!
--
Matthew Miller
Fedora Project Leader
__
ackages for Impassioned Community?
Extra Packages Included by Community?
Extra Packages Introduced by Community?
Extra Packages Including Community?
Extra Packages for Interprise Community? (Or "EPEC"?)
--
Matthew Miller
Fedora Project Leader
_
.fedorainfracloud.org/coprs/ngompa/dnf2-el7/
Have you seen this?
https://blog.centos.org/2018/04/yum4-dnf-for-centos-7-updates/
--
Matthew Miller
Fedora Project Leader
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe sen
On Thu, Mar 09, 2017 at 03:11:21PM -0600, Jason L Tibbitts III wrote:
> It will be interesting to see if this appreciably increases traffic to
> my mirrors.
Yes, it will — I'd love to see any analysis of that you do.
--
Matthew Miller
Fedora Pro
icular thing.
> Now while it would be nice to get them to talk together more.. most of
> the time the only useful conversations seem to happen over beer and
> dinner.. while email lists turn into tribal fights of slights and
> sarcasm.
That's probably more a matter of having
dback. At this moment my
> impression is that we are posting links to bugzilla and we expect the
> users to educate themselves.
That's probably true. What else can we do to improve that?
--
Matthew Miller
Fedora Project Leader
___
epel-devel
ningful karma. But I'd
really rather encourage just getting Fedora accounts and helping draw
people who are in the Fedora community though EPEL into more close
connections.
--
Matthew Miller
Fedora Project Leader
___
epel-devel mailing list -- epe
oth functionality and look & feel.
Honestly, I think this is an example of an application which is not a
great fit for EPEL. It'd be better if we would make a Flatpak which
RHEL/CentOS users could transparently use.
--
Matthew Miller
Fedora Project Leader
__
ntOS infra, then it can't be called "CentOS."
Rebuilding things for the sake of not trusting each other seems like
extra work we are making for ourselves (in both directions). Maybe we
could figure out what the drivers are behind having that barrier and
work on overcoming them.
? In that case, why
import instead of just using the packages directly?
--
Matthew Miller
Fedora Project Leader
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
-released/
--
Matthew Miller
Fedora Project Leader
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel
as well as Fedora can we build a better
bridge of trust, here?
--
Matthew Miller
Fedora Project Leader
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel
On Fri, Jan 02, 2015 at 01:27:16AM +, Karanbir Singh wrote:
> Everyone able to make it please let me know your names so I can track
> attendance and make reservations accordingly.
I'll be there. Sorry for the slow reply!
--
Matthew Miller
Fedora Pro
ollection to collection.
This makes me kind of scared. I'm all for the first sort of software
collection, but I think limiting this helps constrain the problem set.
(Although I don't think such packages should be limited from, eg, Fedora
Playground.)
--
Matthew Miller
. Let's be
constructive and get this worked out without making it personal. Thank you.
--
Matthew Miller
Fedora Project Leader
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel
rom the man page, this is set with the '-fn'
flag at runtime. I didn't look at xmonad, but there's nothing inherently in
dmenu which seems to need it. I removed terminus-fonts with --nodeps from a
test system, and it seems to run fine maybe that's an easier solution?
PEL packages may not work on
distributions like Amazon Linux, which sometimes makes significant changes."
In the future, if CentOS "varients" catch on, this could be expanded to note
that those won't necessarily work either.
--
M
m the symbol I can see there should be a problem in pcre package.
> Therefore here comes a question, what's the difference between
> RHEL(CentOS) and Amazon?
Quite a lot; they make no attempt at compatibility. I think I'd respond with
that. EPEL packages might work on Amazon Linux, a
value for any talk including reusing numbers, and
high means very interested and 0 means not at all.)
Obviously you should also vote for other interesting talks as well at the
same time. And I hope to see a bunch of the interested people there!
--
M
weight
in terms of process than the concept we have for them in Fedora, for better
or worse.) Some new joint upstream to be the meeting point?
Robyn, you around? Want to lay out the idea in more depth?
--
Matthew Miller-- Fedora Project--
__
ense?
It makes a ton of sense to me, at least.
--
Matthew Miller-- Fedora Project--
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel
; keys on the hub, passphrases in the koji config and is pretty much
> never going to be acceptable to upstream koji to add.
Maybe an intermediate thing would be a less-secure-than-sigil-but-still-
separate automatic signing server?
--
Matthew Miller
be quite valuable, I think we should
aim for doing it. (Whether it should replace or just supplement the current
signing process, I don't have a really strong opinion on, although I'm in
general in favor of more automation and less work which depends on
intervention from
ve at the end of that period.
I'm thinking here about SCLs (or possibly other stack/env tech) that might
target current supported Fedora but have a longer lifecyle of its own (with
best-effort compatibility for three years).
I keep coming back to this idea because it's what people
ming year or so". The new repo might target both EL and Fedora and provide
alternative versions maintained on, say, a 3-year lifecycle.
--
Matthew Miller-- Fedora Project--
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel
ards-compatible, but there is one change of note: it now
> verifies SSL certs by default. Will that break anybody? I can help
> with patches if necessary.
> https://admin.fedoraproject.org/updates/python-boto-2.9.6-2.el6
We've still got the 2.6.0 in Fedora 19 -- at what point did the
rors would be able to provide logs?
--
Matthew Miller ☁☁☁ Fedora Cloud Architect ☁☁☁
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel
60 matches
Mail list logo
