golang-github-prometheus-node-exporter seems to be unmaintained at this point.
There are a few open CVEs that have been corrected upstream in the last year
but not made it down to the fedora package.
In Feb I opened a maintainer check ticket :
https://bugzilla.redhat.com/show_bug.cgi?id=216694
Somehow I missed the orphaning of perl-Parse-EDID.
Anyway, I'd like to take over maintenance of this package as other packages I
maintain are dependent on it.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-
Thanks for providing this information!
I'll confess my primary worry/complaint about Modularity/AppStream in RHEL8 is
one of lifecycle.
The default Stream in RHEL8 does not have the full 10 year lifecycle[1] present
in RHEL7. Folks doing a standard 'yum install ' get the default stream,
b
On Fri, Mar 13, 2020 at 9:48 AM Robbie Harwood wrote:
>
> Daniel Mach writes:
>
> > Dne 12. 03. 20 v 19:26 Pat Riehecky napsal(a):
> >
> >> I realize I'm thinking about the Pie in the Sky, but:
> >>
> >> Would it be possible for 'micr
I realize I'm thinking about the Pie in the Sky, but:
Would it be possible for 'microdnf' to become the base for 'dnf' so
that extra 'dnf' functionality is added via some kind of
modules/plugins/etc behaviour? Perhaps "somehow" it could (for
example) find out "oh I've got python, lets load those
On 01/12/2016 11:54 AM, Orion Poplawski wrote:
On 01/12/2016 08:28 AM, Johnny Hughes wrote:
'LibRaw-0.17.1-3.el7.x86_64 (epel-testing)' and
'LibRaw-0.14.8-5.el7.20120830git98d925.x86_64 (@base/$releasever)' are
conflicting
I think there is some confusion around this. It seems that it may hav
vel mailing list
epel-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel
--
Pat Riehecky
Scientific Linux developer
http://www.scientificlinux.org/
___
epel-devel mailing list
epel-de...@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel
