OLD: Fedora-Rawhide-20240816.n.0
NEW: Fedora-Rawhide-20240817.n.0
= SUMMARY =
Added images:1
Dropped images: 4
Added packages: 2
Dropped packages:0
Upgraded packages: 84
Downgraded packages: 1
Size of added packages: 442.95 MiB
Size of dropped packages:0
Announcing the creation of a new nightly release validation test event
for Fedora 41 Branched 20240817.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
Is there still any work being done on this? I'm interested in running
Fedora on LoongArch and helping with the porting efforts. I do have
hardware as well (it's available on AliExpress, even outside of China).
--
Jonathan
--
___
devel mailing list --
OLD: Fedora-41-20240816.n.0
NEW: Fedora-41-20240817.n.0
= SUMMARY =
Added images:0
Dropped images: 1
Added packages: 58
Dropped packages:0
Upgraded packages: 115
Downgraded packages: 0
Size of added packages: 6.78 MiB
Size of dropped packages:0 B
Size of
On Sat, Aug 17, 2024 at 9:12 AM Matthew Krupcale wrote:
>
> On Fri, Aug 16, 2024 at 10:59 PM Neal Gompa wrote:
> >
> > On Tue, Aug 13, 2024 at 7:09 AM Neal Gompa wrote:
> > >
> > > On Wed, Aug 7, 2024 at 5:32 AM Neal Gompa wrote:
> > > >
> > > > On Wed, Aug 7, 2024 at 4:49 AM Fabio Valentini
> Today we have:
>
> * 24312 spec files in Fedora
>
> * 30925 license tags in all spec files
>
> * 5740 tags have not been converted to SPDX yet
Soon we will have 5739 license tags left to update as I'm ready to
push a package update.
kcov bundles 3 javascript libraries in HTML reports so I ended
Dne 17. 08. 24 v 8:02 odp. Dridi Boukelmoune napsal(a):
I ended up with the following license tag that I moved to SPDX as part
of the incoming update:
License: GPL-2.0-only AND MIT AND (GPL-2.0-only OR MIT)
I feel like I could technically factor it to just "GPL-2.0-only AND
MIT" because pi
At some point we added a rule,
“A license should normally appear only once in the License: tag license
expression. But if the license expression includes an OR sub-expression, that
OR sub-expression is treated as though it were a single license for purposes of
this rule. *As an exception to
On Sat, Aug 17, 2024 at 8:44 PM Ben Beasley wrote:
>
> At some point we added a rule,
>
> “A license should normally appear only once in the License: tag license
> expression. But if the license expression includes an OR sub-expression, that
> OR sub-expression is treated as though it were a sin
On Sat, Aug 17, 2024 at 3:13 PM Miroslav Suchý wrote:
>
> Dne 17. 08. 24 v 8:02 odp. Dridi Boukelmoune napsal(a):
>
> I ended up with the following license tag that I moved to SPDX as part
> of the incoming update:
>
> License: GPL-2.0-only AND MIT AND (GPL-2.0-only OR MIT)
>
> I feel like I c
10 matches
Mail list logo