On 09/11/2022 05:26, Naheem Zaffar wrote:
Not all builds in rawhide are release builds. You will get for instance
the whole gnome stack beta releases and rc releases during development.
To achieve the goal, you must rebuild every single package in a
dependency tree, including such important
On 11/9/22 10:08, Panu Matilainen wrote:
On 11/8/22 21:45, Adam Williamson wrote:
On Tue, 2022-11-08 at 08:11 -0800, Adam Williamson wrote:
On Tue, 2022-11-08 at 13:32 +0200, Panu Matilainen wrote:
But I don't know the slightest thing about ansible, beyond a very rough
idea of what kind of
On 11/8/22 21:45, Adam Williamson wrote:
On Tue, 2022-11-08 at 08:11 -0800, Adam Williamson wrote:
On Tue, 2022-11-08 at 13:32 +0200, Panu Matilainen wrote:
But I don't know the slightest thing about ansible, beyond a very rough
idea of what kind of tool it is. Just understanding what exactly
On Wed, Nov 09, 2022 at 04:26:23AM +, Naheem Zaffar wrote:
> On Tue, 8 Nov 2022, 19:22 Vitaly Zaitsev via devel, <
> devel@lists.fedoraproject.org> wrote:
>
> > On 08/11/2022 19:53, Naheem Zaffar wrote:
> > > Has there been any consideration to turn on frame pointers for atleast
> > > dev
Minutes:
https://meetbot.fedoraproject.org/fedora-meeting-1/2022-11-09/fedora_coreos_meeting.2022-11-09-16.35.html
Minutes (text):
https://meetbot.fedoraproject.org/fedora-meeting-1/2022-11-09/fedora_coreos_meeting.2022-11-09-16.35.txt
Log:
When I’ve been mass-CC’d on irrelevant CVEs, I have been able to determine that
it was due to a package-lock.json file, which names and pins the versions of
all recursive dependencies, that was included with some example NodeJS project
in the source tarball. I’ve had trouble with this on a
Dne 09. 11. 22 v 3:10 Ian McInerney via devel napsal(a):
On Wed, Sep 7, 2022 at 7:45 PM Ben Cotton wrote:
On Wed, Sep 7, 2022 at 2:05 PM Maxwell G via devel
wrote:
>
> Does anyone know how to reach prodsec about this?
I'll reach out to the people I know and see what the
OLD: Fedora-37-20221108.n.0
NEW: Fedora-37-20221109.n.0
= SUMMARY =
Added images:0
Dropped images: 0
Added packages: 0
Dropped packages:0
Upgraded packages: 1
Downgraded packages: 0
Size of added packages: 0 B
Size of dropped packages:0 B
Size of upgraded
On 07/11/2022 17:46, Miroslav Suchý wrote:
8.
After you migrate your SPEC file, please add the string “SPDX” to
the entry of the packages’ %changelog. This is the easiest way to
detect the migration has been done. The second best option is to add
it to the dist-git commit
Dne 09. 11. 22 v 13:58 Neal Gompa napsal(a):
What do we do if the SPDX tag is the same as the existing license
tag (eg ISC) though? Do we just add a dummy change/commit entry that
mentions SPDX to confirm we've reviewed it?
Don't bother. Eventually, we'll re-process all spec files and identify
The Fedora Linux 37 Final Go/No-Go[1] meeting is scheduled for
Thursday 10 November at 1700 UTC in #fedora-meeting. Note that
depending on your time zone, this may be an hour earlier in your local
time than you're used to. At this time, we will determine the status
of the F37 Final for the 15
Dne 08. 11. 22 v 11:07 Petr Pisar napsal(a):
Could you remove from the listing spec files whose License tag contains
capitalized SPDX conjunctions (OR AND WITH)? Cf. perl-Alien-Build.
Great idea. Will do.
Miroslav
___
devel mailing list --
On Wed, Nov 9, 2022 at 1:52 PM Miroslav Suchý wrote:
> Actually... if you add there the dummy changelog entry, it makes my work
> easier.
Does it make sense for your script in some future
iteration to add in the capability to check if the
license is identical pre/post SPDX if the spec does
not
On Tue, 01 Nov 2022 11:26:13 -
Daan De Meyer via devel wrote:
> I've added a new section to the proposal with the benchmark results of some
> benchmarks we performed against a Fedora 37 system built with frame pointers
> and a regular Fedora 37 system. The impact on most benchmarks seems
* Demi Marie Obenour:
> On 11/8/22 18:46, Frank Ch. Eigler wrote:
>> Demi Marie Obenour writes:
>>
>>> Three other options I can think of:
>>> [...]
>>
>> Another one:
>>
>> 4. Speed up out-of-context backtracer(s), possibly consuming
>> kernel-perf-ringbuffer stack dumps, or possibly
On Wed, Nov 9, 2022 at 7:51 AM Tom Hughes via devel
wrote:
>
> On 07/11/2022 17:46, Miroslav Suchý wrote:
>
> > 8.
> >
> > After you migrate your SPEC file, please add the string “SPDX” to
> > the entry of the packages’ %changelog. This is the easiest way to
> > detect the migration
OLD: Fedora-Rawhide-20221108.n.0
NEW: Fedora-Rawhide-20221109.n.0
= SUMMARY =
Added images:2
Dropped images: 0
Added packages: 4
Dropped packages:2
Upgraded packages: 152
Downgraded packages: 0
Size of added packages: 5.21 MiB
Size of dropped packages
On Wed, Nov 9, 2022 at 2:52 PM Miroslav Suchý wrote:
>
> Dne 09. 11. 22 v 13:58 Neal Gompa napsal(a):
>
> What do we do if the SPDX tag is the same as the existing license
> tag (eg ISC) though? Do we just add a dummy change/commit entry that
> mentions SPDX to confirm we've reviewed it?
>
>
Kevin Kofler via devel wrote:
> Mattia Verga via devel wrote:
>> with the current workflow, Bodhi doesn't know when a release is freezed.
>> There is support for a "Freeze" state, but it was never used.
>
> How do we prevent then that pushes to stable actually move forward? If
> rel- eng just
On Wed, 2022-11-09 at 19:27 -0500, Demi Marie Obenour wrote:
> On 11/9/22 05:21, Dan Horák wrote:
> > On Tue, 01 Nov 2022 11:26:13 -
> > Daan De Meyer via devel wrote:
> >
> > > I've added a new section to the proposal with the benchmark
> > > results of some benchmarks we performed against
Mattia Verga via devel wrote:
> with the current workflow, Bodhi doesn't know when a release is freezed.
> There is support for a "Freeze" state, but it was never used.
How do we prevent then that pushes to stable actually move forward? If rel-
eng just hits a different button / runs a different
On 11/9/22 05:21, Dan Horák wrote:
> On Tue, 01 Nov 2022 11:26:13 -
> Daan De Meyer via devel wrote:
>
>> I've added a new section to the proposal with the benchmark results of some
>> benchmarks we performed against a Fedora 37 system built with frame pointers
>> and a regular Fedora 37
What is the driver for choosing Phosh over GNOME Shell? Let me first say the
amount of work put in by both Purism and the GNOME community into Phosh and
other mobile components like libhandy has been critical to Linux mobile space.
While mobile friendly GNOME Shell improvements only recently
Am 07.11.22 um 14:49 schrieb Petr Pisar:
V Mon, Nov 07, 2022 at 01:40:18PM +0100, Lukas Javorsky napsal(a):
Hi,
Minizip-ng has changed its soname name from "libminizip.so.3.0" to
"libminizip.so.3" thus we need to rebuild all the packages that are
requiring this soname.
I've listed them with
https://bugzilla.redhat.com/show_bug.cgi?id=2140480
Upstream Release Monitoring
changed:
What|Removed |Added
Summary|perl-Dist-Zilla-6.027 is|perl-Dist-Zilla-6.028 is
https://bugzilla.redhat.com/show_bug.cgi?id=2141400
Bug ID: 2141400
Summary: perl-Catalyst-Runtime-5.90130 is available
Product: Fedora
Version: rawhide
Status: NEW
Component: perl-Catalyst-Runtime
Keywords:
mspacek merged a pull-request against the project: `perl-Module-Package` that
you are following.
Merged pull-request:
``
Update license to SPDX format
``
https://src.fedoraproject.org/rpms/perl-Module-Package/pull-request/1
___
perl-devel mailing
On 08. 11. 22 22:36, Troy Dawson wrote:
Hi Miro,
You have explained the problem very well, and a possible solution.
But I'm a bit confused as to what you want to happen.
Is this a heads up, that you are going to change something?
Do you want us to discuss what is the best thing to do?
Yes,
https://bugzilla.redhat.com/show_bug.cgi?id=2138492
Fedora Update System changed:
What|Removed |Added
Fixed In Version|perl-DateTime-TimeZone-2.56 |perl-DateTime-TimeZone-2.56
mspacek merged a pull-request against the project: `perl-Text-VCardFast` that
you are following.
Merged pull-request:
``
Package tests and update license to SPDX format
``
https://src.fedoraproject.org/rpms/perl-Text-VCardFast/pull-request/1
___
mspacek opened a new pull-request against the project: `perl-Text-VCardFast`
that you are following:
``
Package tests and update license to SPDX format
``
To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Text-VCardFast/pull-request/1
mspacek opened a new pull-request against the project: `perl-Module-Package`
that you are following:
``
Update license to SPDX format
``
To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Module-Package/pull-request/1
___
https://bugzilla.redhat.com/show_bug.cgi?id=2138492
Fedora Update System changed:
What|Removed |Added
Fixed In Version|perl-DateTime-TimeZone-2.56 |perl-DateTime-TimeZone-2.56
tl;dr: Python 3.12 should be built with no-omit-frame-pointer if
upstream recommends it.
Hello,
You might be aware of a Fedora change proposal [0] (discussed on
fedora-devel [1] and FESCo [2]) are discussing turning on C compiler
flags that help with performance *measurement*, but might hurt
The Fedora Linux 37 Final Go/No-Go[1] meeting is scheduled for
Thursday 10 November at 1700 UTC in #fedora-meeting. Note that
depending on your time zone, this may be an hour earlier in your local
time than you're used to. At this time, we will determine the status
of the F37 Final for the 15
https://bugzilla.redhat.com/show_bug.cgi?id=2137026
Petr Pisar changed:
What|Removed |Added
Fixed In Version||perl-Chart-2.403.8-1.fc38
https://bugzilla.redhat.com/show_bug.cgi?id=2137026
Petr Pisar changed:
What|Removed |Added
Status|MODIFIED|CLOSED
Resolution|---
https://bugzilla.redhat.com/show_bug.cgi?id=2141527
Bug ID: 2141527
Summary: perl-CGI-Application-Plugin-ValidateRM-2.52 is
available
Product: Fedora
Version: rawhide
Status: NEW
Component:
38 matches
Mail list logo
