https://bugzilla.redhat.com/show_bug.cgi?id=2188483
--- Comment #7 from Fedora Update System ---
FEDORA-2023-53842b5fbf has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing
https://bugzilla.redhat.com/show_bug.cgi?id=2185669
--- Comment #12 from Fedora Update System ---
FEDORA-2023-6a59d7 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing
https://bugzilla.redhat.com/show_bug.cgi?id=2186030
--- Comment #9 from Fedora Update System ---
FEDORA-2023-6a59d7 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing
https://bugzilla.redhat.com/show_bug.cgi?id=2188469
--- Comment #7 from Fedora Update System ---
FEDORA-2023-6a59d7 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing
The following Fedora EPEL 7 Security updates need testing:
Age URL
1 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-30f3deb00a
chromium-112.0.5615.165-1.el7
The following builds have been pushed to Fedora EPEL 7 updates-testing
libmediainfo-23.03-2.el7
The following Fedora EPEL 8 Security updates need testing:
Age URL
39 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-1e00c3d01e
cutter-re-2.2.0-1.el8 rizin-0.5.1-1.el8
4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-4f43a624e1
libsignal-protocol-c-2.3.3-8.el8
https://bugzilla.redhat.com/show_bug.cgi?id=2186030
--- Comment #8 from Fedora Update System ---
FEDORA-2023-aadca8fe4c has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing
https://bugzilla.redhat.com/show_bug.cgi?id=2188469
--- Comment #6 from Fedora Update System ---
FEDORA-2023-aadca8fe4c has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing
https://bugzilla.redhat.com/show_bug.cgi?id=2185669
--- Comment #11 from Fedora Update System ---
FEDORA-2023-aadca8fe4c has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing
https://bugzilla.redhat.com/show_bug.cgi?id=2188483
--- Comment #6 from Fedora Update System ---
FEDORA-2023-562659a921 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing
https://bugzilla.redhat.com/show_bug.cgi?id=2188469
Fedora Update System changed:
What|Removed |Added
Status|MODIFIED|ON_QA
--- Comment #5 from
https://bugzilla.redhat.com/show_bug.cgi?id=2186030
--- Comment #7 from Fedora Update System ---
FEDORA-2023-1a290e1046 has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing
https://bugzilla.redhat.com/show_bug.cgi?id=2185669
--- Comment #10 from Fedora Update System ---
FEDORA-2023-1a290e1046 has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing
https://bugzilla.redhat.com/show_bug.cgi?id=2188483
Fedora Update System changed:
What|Removed |Added
Status|MODIFIED|ON_QA
--- Comment #5 from
https://bugzilla.redhat.com/show_bug.cgi?id=2178064
Fedora Update System changed:
What|Removed |Added
Fixed In Version||perl-MooseX-Types-DateTime-
Kamil Paral wrote:
> I've spent more than a decade perfecting my email filters and I have a
> setup that works for me very well. I dislike certain aspects of mailing
> lists (cross-posting, top-posting, reply-to, etc, which just can't work
> well when everyone has to be vigilant all the time to do
https://bugzilla.redhat.com/show_bug.cgi?id=2177873
Bug 2177873 depends on bug 2178064, which changed state.
Bug 2178064 Summary: Add perl-MooseX-Types-DateTime-MoreCoercions to EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2178064
What|Removed |Added
Once upon a time, Ben Cotton said:
> Steam Deck is shipping with a default of `2147483642` (MAX_INT - 5) up
> from `65530` of Fedora; it makes sense to follow their lead and set
> the same value.
It doesn't necessarily make sense for a general-purpose OS to follow
what is effectively an embedded
The increase step looks very massive. And I wonder why we should make such a
change to make games of all things work out of the box. Are games the main use
case of Fedora?
Wouldn't it make more sense to create a game spin instead? After all, we
already have a Lab. Or make a corresponding
Kevin Fenzi wrote:
> On Sun, Apr 23, 2023 at 11:21:58PM +0200, Björn Persson wrote:
> > Kevin Fenzi wrote:
> > > We could probibly come up with some
> > > better way to start new topics/discussions
> >
> > Yes I think I can come up with a better way. Give each tag its own
> > email address,
Interesting that this came up. I was just talking to someone else about
this the other day. From what I understand, that sysctl affects the max
number of memory map areas a process can have, i.e. contiguous reserved
memory. For a game that's great because it can pack more into memory and
https://wiki.gnome.org/Hackfests/ShellDisplayNext2023
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
On Mon, Apr 24, 2023 at 4:10 PM Demi Marie Obenour
wrote:
>
> On 4/24/23 08:33, Neal Gompa wrote:
> > On Mon, Apr 24, 2023 at 4:19 AM Peter Robinson wrote:
> >>
> There is no problem technically; the Copr repo[2] is building
> Firecracker RPMs with musl. Maintainers of both Rust and
On 4/24/23 08:33, Neal Gompa wrote:
> On Mon, Apr 24, 2023 at 4:19 AM Peter Robinson wrote:
>>
There is no problem technically; the Copr repo[2] is building
Firecracker RPMs with musl. Maintainers of both Rust and musl seemed
to be against it in Fedora. From this thread:
>>> Why
On 4/23/23 18:32, Kevin Fenzi wrote:
You can write the tag after the plus sign if that makes it easier to
implement. Instead of"fedoraproject+newto...@discoursemail.com" the
address could be"fedoraproject+de...@discoursemail.com" or maybe
"fedoraproject+devel/newto...@discoursemail.com". Or
Congratulations on the new release, and thanks team for the hard work on
modernizing FMN over the past several months.
On Mon, Apr 24, 2023 at 9:31 AM Aurelien Bompard
wrote:
> Hi folks!
>
> The "FMN replacement" team has finished writing the new version of our
> notification system, and we are
There wasn't much in the FESCo queue this week, so April 25th's meeting is
canceled.
However, issue 2981 could use more feedback for the FESCo election interview
questions. If FESCo members could take a moment to look over the questions and
reply on the ticket[0], that would be helpful!
I'll
On Thu, Apr 20, 2023 at 11:21 PM Matthew Miller
wrote:
> I propose that we transition devel list, and eventually most of our
> mailing lists, to Fedora Discussion (our Discourse-powered forum).
>
I've spent more than a decade perfecting my email filters and I have a
setup that works for me very
Il 24/04/23 11:47, Aurelien Bompard ha scritto:
> Hi folks!
>
> The FMN replacement team has finished writing the new version of our
> notification system, and we are ready to deploy! We plan on deploying
> the new version on https://notifications.fedoraproject.org this week,
> we'll keep the old
On Mon, Apr 24, 2023 at 12:15:12PM -0400, Ben Cotton wrote:
> https://fedoraproject.org/wiki/Changes/BiggerESP
>
> This document represents a proposed Change. As part of the Changes
> process, proposals are publicly announced in order to receive
> community feedback. This proposal will only be
A few questions:
* Could we perhaps try and get upstream to adjust this higher?
* Is there any description/docs on what happens when this value is too
low? do games error in a particular way?
* Is there any adverse impact increasing this? More memory used?
Thanks for putting this together.
On Sun, Apr 23, 2023 at 07:28:08AM +, Mattia Verga via devel wrote:
> Isn't simpler to schedule:
>
> 1. lock down Koji in (stop accepting new builds,
> possibly only for Rawhide)
> 2. let Koji finish running builds (assuming there are none which
> requires more than 24h)
> 3. at check any
https://bugzilla.redhat.com/show_bug.cgi?id=172792
Petr Pisar changed:
What|Removed |Added
CC||ppi...@redhat.com
--
You are receiving
https://fedoraproject.org/wiki/Changes/BiggerESP
This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive
community feedback. This proposal will only be implemented if approved
by the Fedora Engineering Steering Committee.
https://fedoraproject.org/wiki/Changes/IncreaseVmMaxMapCount
This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive
community feedback. This proposal will only be implemented if approved
by the Fedora Engineering Steering
https://fedoraproject.org/wiki/Changes/BiggerESP
This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive
community feedback. This proposal will only be implemented if approved
by the Fedora Engineering Steering Committee.
https://fedoraproject.org/wiki/Changes/IncreaseVmMaxMapCount
This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive
community feedback. This proposal will only be implemented if approved
by the Fedora Engineering Steering
https://linuxunplugged.com/507 Fedora 38 review of LUP from yesterday
uploaded now
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
mspacek merged a pull-request against the project: `perl-Pod-Parser` that you
are following.
Merged pull-request:
``
1.66 bump
``
https://src.fedoraproject.org/rpms/perl-Pod-Parser/pull-request/8
___
perl-devel mailing list --
https://bugzilla.redhat.com/show_bug.cgi?id=172792
AbnerBruen changed:
What|Removed |Added
CC||loganej...@pixiil.com
--- Comment #3
mspacek opened a new pull-request against the project: `perl-Pod-Parser` that
you are following:
``
1.66 bump
``
To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Pod-Parser/pull-request/8
___
perl-devel mailing list --
On Mon, 24 Apr 2023 at 09:38, Simo Sorce wrote:
> On Sat, 2023-04-22 at 12:16 -0700, Adam Williamson wrote:
> > On Sat, 2023-04-22 at 10:37 -0700, Kevin Fenzi wrote:
> > > On Fri, Apr 21, 2023 at 02:30:45PM -0700, Adam Williamson wrote:
> > > > On Fri, 2023-04-21 at 23:20 +0200, Florian Weimer
mspacek merged a pull-request against the project: `perl-Pod-Parser` that you
are following.
Merged pull-request:
``
1.66 bump
``
https://src.fedoraproject.org/rpms/perl-Pod-Parser/pull-request/7
___
perl-devel mailing list --
mspacek opened a new pull-request against the project: `perl-Pod-Parser` that
you are following:
``
1.66 bump
``
To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Pod-Parser/pull-request/7
___
perl-devel mailing list --
On Sat, Apr 22, 2023 at 1:24 AM Benson Muite wrote:
>
> Thanks, this is helpful. Can you make the scripts/programs you used for
> these available to allow for a more detailed analysis?
No, because I literally went to each page of the archives and copied
the numbers into a spreadsheet. If you
On Sat, 2023-04-22 at 12:16 -0700, Adam Williamson wrote:
> On Sat, 2023-04-22 at 10:37 -0700, Kevin Fenzi wrote:
> > On Fri, Apr 21, 2023 at 02:30:45PM -0700, Adam Williamson wrote:
> > > On Fri, 2023-04-21 at 23:20 +0200, Florian Weimer wrote:
> > > >
> > > > > For lists that are active, the
Hi folks!
The "FMN replacement" team has finished writing the new version of our
notification system, and we are ready to deploy!
We plan on:
- deploying the new version on https://notifications.fedoraproject.org
this week,
- keep the old one around but move it to
Hi folks!
The "FMN replacement" team has finished writing the new version of our
notification system, and we are ready to deploy!
We plan on:
- deploying the new version on https://notifications.fedoraproject.org
this week,
- keep the old one around but move it to
On Fri, 2023-04-21 at 15:39 -0500, Carl George wrote:
> As Matthew stated, Ben has measured it and fewer people are
> participating on the mailing list over time. We are already leaving
> out many contributors.
This is an interpretation, but are we sure we are missing them because
the mailing
mspacek merged a pull-request against the project: `perl-Pod-Parser` that you
are following.
Merged pull-request:
``
1.66 bump
``
https://src.fedoraproject.org/rpms/perl-Pod-Parser/pull-request/6
___
perl-devel mailing list --
On 07. 04. 23 4:49, Orion Poplawski wrote:
I can work around it by defining RHEL_ALLOW_PYTHON2_FOR_BUILD=1, but it seems
like we really should be pulling in python2 from the module?
FTR I agree EPEL should pull Python 2 from the module.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
mspacek opened a new pull-request against the project: `perl-Pod-Parser` that
you are following:
``
1.66 bump
``
To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Pod-Parser/pull-request/6
___
perl-devel mailing list --
mspacek merged a pull-request against the project: `perl-Pod-Parser` that you
are following.
Merged pull-request:
``
1.66 bump
``
https://src.fedoraproject.org/rpms/perl-Pod-Parser/pull-request/5
___
perl-devel mailing list --
On Mon, Apr 24, 2023 at 4:19 AM Peter Robinson wrote:
>
> > > There is no problem technically; the Copr repo[2] is building
> > > Firecracker RPMs with musl. Maintainers of both Rust and musl seemed
> > > to be against it in Fedora. From this thread:
> > Why does Fedora not want to ship
Matthew Miller wrote:
> I propose that we transition devel list, and eventually most of our
> mailing lists, to Fedora Discussion (our Discourse-powered forum).
You are 19 days late for April Fools!
Discourse is an absolute pain in the neck because it not only requires
JavaScript to be able to
https://bugzilla.redhat.com/show_bug.cgi?id=2189187
Bug ID: 2189187
Summary: Upgrade perl-Image-ExifTool to 12.60
Product: Fedora
Version: rawhide
URL: https://metacpan.org/release/Image-ExifTool
Status: NEW
https://bugzilla.redhat.com/show_bug.cgi?id=2189182
Bug ID: 2189182
Summary: Upgrade perl-DBIx-SearchBuilder to 1.76
Product: Fedora
Version: rawhide
URL: https://metacpan.org/release/DBIx-SearchBuilder
Status: NEW
OLD: Fedora-Rawhide-20230423.n.0
NEW: Fedora-Rawhide-20230424.n.0
= SUMMARY =
Added images:1
Dropped images: 0
Added packages: 3
Dropped packages:0
Upgraded packages: 32
Downgraded packages: 0
Size of added packages: 183.38 KiB
Size of dropped packages:0
https://bugzilla.redhat.com/show_bug.cgi?id=2189180
Bug ID: 2189180
Summary: Upgrade perl-Convert-Color to 0.17
Product: Fedora
Version: rawhide
URL: https://metacpan.org/release/Convert-Color
Status: NEW
Component:
In my opinion, in this kind of big change, it's important for us to
make things reversible, and to consider a possibility for us to go
back.
I think it's better for us to keep the infra of the mailing list for a
while. When we migrate the devel@ to the discourse, we should still
keep to manage
Dne 24. 04. 23 v 2:32 Kevin Fenzi napsal(a):
On Sun, Apr 23, 2023 at 11:21:58PM +0200, Björn Persson wrote:
Kevin Fenzi wrote:
We could probibly come up with some
better way to start new topics/discussions
Yes I think I can come up with a better way. Give each tag its own
email address, like
mspacek opened a new pull-request against the project: `perl-Pod-Parser` that
you are following:
``
1.66 bump
``
To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Pod-Parser/pull-request/5
___
perl-devel mailing list --
Dne 24. 04. 23 v 12:10 Felix Schwarz napsal(a):
I have updated some of my packages, but they're still listed there. I've
used "Update license tag to SPDX" in the changelog.
similar for me.
For example take python-pydyf:
https://src.fedoraproject.org/rpms/python-pydyf/commits/rawhide
After
https://bugzilla.redhat.com/show_bug.cgi?id=2188829
Michal Josef Spacek changed:
What|Removed |Added
Doc Type|--- |If docs needed, set a value
https://bugzilla.redhat.com/show_bug.cgi?id=2188483
--- Comment #3 from Fedora Update System ---
FEDORA-2023-3791af5ab6 has been submitted as an update to Fedora 38.
https://bodhi.fedoraproject.org/updates/FEDORA-2023-3791af5ab6
--
You are receiving this mail because:
You are on the CC list
https://bugzilla.redhat.com/show_bug.cgi?id=2188483
--- Comment #2 from Fedora Update System ---
FEDORA-2023-562659a921 has been submitted as an update to Fedora 37.
https://bodhi.fedoraproject.org/updates/FEDORA-2023-562659a921
--
You are receiving this mail because:
You are on the CC list
Hello everyone,
Please join us at the next Open NeuroFedora team meeting on Monday 24th April
at 1300UTC in #fedora-neuro on Matrix or IRC
(Libera.chat). The meeting is a public meeting, and open for everyone
to attend. You can join us over:
Matrix: https://matrix.to/#/#neuro:fedoraproject.org
https://bugzilla.redhat.com/show_bug.cgi?id=2188483
Jitka Plesnikova changed:
What|Removed |Added
Doc Type|--- |If docs needed, set a value
Dne 23. 04. 23 v 11:59 Mattia Verga via devel napsal(a):
I have updated some of my packages, but they're still listed there. I've
used "Update license tag to SPDX" in the changelog.
Ag! I forgot to git-push. Fixed. Sorry.
Miroslav
___
devel
Am 23.04.23 um 11:59 schrieb Mattia Verga via devel:
I have updated some of my packages, but they're still listed there. I've
used "Update license tag to SPDX" in the changelog.
similar for me.
For example take python-pydyf:
https://src.fedoraproject.org/rpms/python-pydyf/commits/rawhide
https://bugzilla.redhat.com/show_bug.cgi?id=2188469
--- Comment #2 from Fedora Update System ---
FEDORA-2023-1a290e1046 has been submitted as an update to Fedora 38.
https://bodhi.fedoraproject.org/updates/FEDORA-2023-1a290e1046
--
You are receiving this mail because:
You are on the CC list
https://bugzilla.redhat.com/show_bug.cgi?id=2188469
--- Comment #4 from Fedora Update System ---
FEDORA-2023-6a59d7 has been submitted as an update to Fedora 36.
https://bodhi.fedoraproject.org/updates/FEDORA-2023-6a59d7
--
You are receiving this mail because:
You are on the CC list
Hi folks!
The FMN replacement team has finished writing the new version of our
notification system, and we are ready to deploy! We plan on deploying
the new version on https://notifications.fedoraproject.org this week,
we'll keep the old one around but move it to
https://bugzilla.redhat.com/show_bug.cgi?id=2188469
Jitka Plesnikova changed:
What|Removed |Added
Status|ASSIGNED|MODIFIED
Fixed In Version|
Dne 23. 04. 23 v 13:29 Richard Shaw napsal(a):
NEW: the package fedora-license-data now contains BNF grammar which you can
use. It is available in
`/usr/share/fedora-license-data/grammar.lark`
You'll have to explain to me the significance of this.
This is good starting point:
https://bugzilla.redhat.com/show_bug.cgi?id=2188469
Jitka Plesnikova changed:
What|Removed |Added
Doc Type|--- |If docs needed, set a value
On 4/24/23 09:42, Herald Yu wrote:
> Hello everyone, I am Herald come from Shanghai, China. It's nice to meet you
> in Fedora Devel Community.
>
> I am a Tech Writer who is passionate about open-source technology. I have
> contributed to JuiceFS and I am willing to package and maintain this
> > There is no problem technically; the Copr repo[2] is building
> > Firecracker RPMs with musl. Maintainers of both Rust and musl seemed
> > to be against it in Fedora. From this thread:
> Why does Fedora not want to ship Firecracker statically linked to musl?
> That is the supported and
https://bugzilla.redhat.com/show_bug.cgi?id=2189099
Petr Pisar changed:
What|Removed |Added
Blocks||2168842
|
https://bugzilla.redhat.com/show_bug.cgi?id=2189099
Bug ID: 2189099
Summary: perl-Protocol-WebSocket-0.26-13.fc39 FTBFS: File not
found:
/builddir/build/BUILDROOT/perl-Protocol-WebSocket-0.26
https://bugzilla.redhat.com/show_bug.cgi?id=2189098
--- Comment #1 from Petr Pisar ---
From Module-Build-Tiny changelog:
0.040 2023-02-05 23:06:28+01:00 Europe/Amsterdam (TRIAL RELEASE)
- Manify .pod after .pm
- Filter out script documentation from scripts
-
https://bugzilla.redhat.com/show_bug.cgi?id=2189098
Petr Pisar changed:
What|Removed |Added
Blocks||2168842
|
https://bugzilla.redhat.com/show_bug.cgi?id=2189098
Bug ID: 2189098
Summary: dropbox-api-command-2.13-11.fc39 FTBFS: File not
found:
/home/test/rpmbuild/BUILDROOT/dropbox-api-command-2.13
On 4/21/23 23:38, Ben Cotton wrote:
On Fri, Apr 21, 2023 at 4:05 PM Maxwell G wrote:
What evidence shows that the group is ever shrinking? I often see Self
Introduction posts and new people interacting with project. I suppose
that whether they continue interacting afterwards is another
Hello everyone, I am Herald come from Shanghai, China. It's nice to meet you in
Fedora Devel Community.
I am a Tech Writer who is passionate about open-source technology. I have
contributed to JuiceFS and I am willing to package and maintain this software
package. I hope to join the Fedora
On 4/21/23 22:07, Matthew Miller wrote:
On Fri, Apr 21, 2023 at 11:54:09AM -0400, JT wrote:
So I'm interested by what you bring up here. Have you run into situations
where someone wanted to contribute to development but was unwilling to use
a mailing list? With a community as big as Fedora
86 matches
Mail list logo
