The following builds have been pushed to Fedora EPEL 7 updates-testing
chromium-119.0.6045.159-1.el7
isa-l-2.30.0-1.el7
xrootd-5.6.3-2.el7
Details about builds:
chromium-119.0.6045.159-1.el7
The following Fedora EPEL 8 Security updates need testing:
Age URL
5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-bdf128f5d3
audiofile-0.3.6-36.el8
The following builds have been pushed to Fedora EPEL 8 updates-testing
ansible-8.3.0-1.el8
On 2023-11-19 10:34, Richard W.M. Jones wrote:
On Sun, Nov 19, 2023 at 08:33:02AM +, Mattia Verga via devel wrote:
rpms/libldm
I thought I was already doing this one, since I semi-maintain it
upstream already. I'd like to comaintainer it, but I totally can't
find the right button in the
Am 19.11.23 um 14:30 schrieb Neal Gompa:
On Sat, Nov 18, 2023 at 4:20 PM Leon Fauster via epel-devel
wrote:
Just noticed that the current chromium in epel-testing can not be
installed on E9 with rpmfusion repo enabled. All versions before did not
have this problem. It seems the build pulls a
Also... if you meant the scm-commits mailing list, then yeah, that is broken
currently. ;(
https://github.com/fedora-infra/fmn/issues/1024
kevin
signature.asc
Description: PGP signature
--
___
devel mailing list -- devel@lists.fedoraproject.org
To
On Sun, Nov 19, 2023 at 03:13:21PM -0500, Stephen Smoogen wrote:
> It could be due to the retirement of the old notifications system earlier
> this month. See the email "intent to retire: fedmsg-irc, old fmn, osbs"
> sent to the mailing list earlier.
>
> FMN is the tool which sends notifications
On Mon, Nov 20, 2023 at 08:27:47AM +1100, Arthur G wrote:
> I recall a number of years back a proposed gcc upgrade broke many builds.
> This required most maintainers to log in and refactor their source code
> against the new gcc (and new gcc options).
>
> I hadn't logged into Fedora for years
On Sun, Nov 19, 2023 at 06:34:39PM +, Richard W.M. Jones wrote:
> On Sun, Nov 19, 2023 at 08:33:02AM +, Mattia Verga via devel wrote:
> > rpms/cairo
> > rpms/createrepo_c
> > rpms/desktop-backgrounds
> > rpms/ed
> > rpms/libcap
> > rpms/vim
>
> Just noting that these packages seem to be
On Mon, 2023-11-20 at 08:27 +1100, Arthur G wrote:
> I recall a number of years back a proposed gcc upgrade broke many
> builds. This required most maintainers to log in and refactor their
> source code against the new gcc (and new gcc options).
>
> I hadn't logged into Fedora for years however I
I think the problem on src.fp.o
is
https://lists.fedorahosted.org/archives/list/devel@lists.fedoraproject.org/message/EHDPRFVIWWN33XVWPPZ4HFADDZ64BPBK/
On Sun, 2023-11-19 at 15:13 -0500, Stephen Smoogen wrote:
>
> It could be due to the retirement of the old notifications system
> earlier
I recall a number of years back a proposed gcc upgrade broke many builds.
This required most maintainers to log in and refactor their source code
against the new gcc (and new gcc options).
I hadn't logged into Fedora for years however I did do my due diligence and
rather quickly logged in and
https://bugzilla.redhat.com/show_bug.cgi?id=2250558
--- Comment #2 from Upstream Release Monitoring
---
the-new-hotness/release-monitoring.org's scratch build of
perl-ExtUtils-CppGuess-0.27-1.fc38.src.rpm for rawhide completed
http://koji.fedoraproject.org/koji/taskinfo?taskID=109267754
--
https://bugzilla.redhat.com/show_bug.cgi?id=2250558
Bug ID: 2250558
Summary: perl-ExtUtils-CppGuess-0.27 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: perl-ExtUtils-CppGuess
Keywords: FutureFeature,
https://bugzilla.redhat.com/show_bug.cgi?id=2250558
--- Comment #1 from Upstream Release Monitoring
---
Created attachment 2000388
--> https://bugzilla.redhat.com/attachment.cgi?id=2000388=edit
Update to 0.27 (#2250558)
--
You are receiving this mail because:
You are on the CC list for
It could be due to the retirement of the old notifications system earlier
this month. See the email "intent to retire: fedmsg-irc, old fmn, osbs"
sent to the mailing list earlier.
FMN is the tool which sends notifications and it was replaced with a newer
version earlier this year. Here is the
On Sun, Nov 19, 2023 at 1:35 PM Richard W.M. Jones
wrote:
> On Sun, Nov 19, 2023 at 08:33:02AM +, Mattia Verga via devel wrote:
> > rpms/cairo
> > rpms/createrepo_c
> > rpms/desktop-backgrounds
> > rpms/ed
> > rpms/libcap
> > rpms/vim
>
> Just noting that these packages seem to be very
Hi,
Same issue here. I noticed that I'm not getting regular notifications, even
from BZ.
Thanks
On Sunday, 19 November 2023 at 20:19, Mikel Olasagasti
wrote:
> Hi,
>
> I'm not receiving mails from some updates like koschei build status or
> src.f.o commits.
>
> Has something changed in
Hi all,
Hau idatzi du Kevin Fenzi (ke...@scrye.com) erabiltzaileak (2023 aza.
18(a), lr. (21:09)):
>
> rpms/golang-github-kurin-blazer
> rpms/golang-github-minio
> rpms/golang-rsc-pdf
Took these as are required by other packages I maintain.
> rpms/ed
> rpms/multitail
I was already co-admin,
Hi,
I'm not receiving mails from some updates like koschei build status or
src.f.o commits.
Has something changed in this regard or is it the mail service having
issues again?
Kind regards,
Mikel
--
___
devel mailing list --
On Sun, Nov 19, 2023 at 08:33:02AM +, Mattia Verga via devel wrote:
> rpms/cairo
> rpms/createrepo_c
> rpms/desktop-backgrounds
> rpms/ed
> rpms/libcap
> rpms/vim
Just noting that these packages seem to be very important, yet not
volunteering to take them ...
> rpms/libldm
I thought I was
Try adding this to the file
#include
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
Hello, Carlos.
On Sunday, 19 November 2023 at 15:20, Carlos Rodriguez-Fernandez wrote:
> Hi all,
> I have been in the process of becoming a co-maintainer of *libcap*. But I
> still need the sponsorship part of it. Hoping it is resolved before the 6
> weeks mark. I got the non-responsive issue
Hi all,
I have been in the process of becoming a co-maintainer of *libcap*. But
I still need the sponsorship part of it. Hoping it is resolved before
the 6 weeks mark. I got the non-responsive issue approved, the
sponsorship issue, and the PR with updates, tests converted to tmt, and
cleanups
https://bugzilla.redhat.com/show_bug.cgi?id=2250416
Fedora Update System changed:
What|Removed |Added
Resolution|--- |ERRATA
Fixed In Version|
https://bugzilla.redhat.com/show_bug.cgi?id=2250416
Fedora Update System changed:
What|Removed |Added
Status|NEW |MODIFIED
--- Comment #1 from
On Sat, Nov 18, 2023 at 4:20 PM Leon Fauster via epel-devel
wrote:
>
> Just noticed that the current chromium in epel-testing can not be
> installed on E9 with rpmfusion repo enabled. All versions before did not
> have this problem. It seems the build pulls a new dep (libavformat-free)
> that
OLD: Fedora-Rawhide-20231118.n.0
NEW: Fedora-Rawhide-20231119.n.0
= SUMMARY =
Added images:1
Dropped images: 3
Added packages: 5
Dropped packages:0
Upgraded packages: 24
Downgraded packages: 0
Size of added packages: 14.14 MiB
Size of dropped packages:0 B
Il 18/11/23 21:08, Kevin Fenzi ha scritto:
> Hi all,
>
> Today, 2023-11-18, we have removed inactive packagers
> from the packager group.
>
> This is in accordance with the FESCo policy on inactive packagers:
> https://docs.fedoraproject.org/en-US/fesco/Policy_for_inactive_packagers/
>
> If the
28 matches
Mail list logo
