Fedora rawhide compose report: 20230119.n.1 changes

[Fedora Rawhide Report]

OLD: Fedora-Rawhide-20230118.n.0
NEW: Fedora-Rawhide-20230119.n.1

= SUMMARY =
Added images:2
Dropped images:  7
Added packages:  12
Dropped packages:3
Upgraded packages:   163
Downgraded packages: 0

Size of added packages:  6.73 MiB
Size of dropped packages:772.20 KiB
Size of upgraded packages:   4.61 GiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   -87.98 MiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =
Image: Workstation live ppc64le
Path: 
Workstation/ppc64le/iso/Fedora-Workstation-Live-ppc64le-Rawhide-20230119.n.1.iso
Image: Container_Minimal_Base docker s390x
Path: 
Container/s390x/images/Fedora-Container-Minimal-Base-Rawhide-20230119.n.1.s390x.tar.xz

= DROPPED IMAGES =
Image: Cloud_Base qcow2 ppc64le
Path: Cloud/ppc64le/images/Fedora-Cloud-Base-Rawhide-20230118.n.0.ppc64le.qcow2
Image: Cloud_Base qcow2 s390x
Path: Cloud/s390x/images/Fedora-Cloud-Base-Rawhide-20230118.n.0.s390x.qcow2
Image: Container_Base docker aarch64
Path: 
Container/aarch64/images/Fedora-Container-Base-Rawhide-20230118.n.0.aarch64.tar.xz
Image: Cloud_Base raw-xz ppc64le
Path: Cloud/ppc64le/images/Fedora-Cloud-Base-Rawhide-20230118.n.0.ppc64le.raw.xz
Image: Cloud_Base raw-xz s390x
Path: Cloud/s390x/images/Fedora-Cloud-Base-Rawhide-20230118.n.0.s390x.raw.xz
Image: Server_KVM qcow2 ppc64le
Path: Server/ppc64le/images/Fedora-Server-KVM-Rawhide-20230118.n.0.ppc64le.qcow2
Image: Server_KVM qcow2 s390x
Path: Server/s390x/images/Fedora-Server-KVM-Rawhide-20230118.n.0.s390x.qcow2

= ADDED PACKAGES =
Package: crosswords-puzzle-sets-nienteperniente-0.1.0-1.fc38
Summary: Italian puzzle sets from Niente per niente for GNOME Crosswords
RPMs:crosswords-puzzle-sets-nienteperniente
Size:22.36 KiB

Package: crosswords-puzzle-sets-oedipus-0.1.1-1.fc38
Summary: Italian puzzle sets from Oedipus for GNOME Crosswords
RPMs:crosswords-puzzle-sets-oedipus
Size:21.52 KiB

Package: gitklient-0-1.20230119git0645ced.fc38
Summary: Git gui client for KDE
RPMs:gitklient
Size:2.77 MiB

Package: golang-github-quic-qtls-go1-20-0.1.0~rc.1-1.fc38
Summary: Go standard library TLS 1.3 implementation, modified for QUIC.
RPMs:golang-github-quic-qtls-go1-20 golang-github-quic-qtls-go1-20-devel
Size:2.53 MiB

Package: rust-atomic_refcell-0.1.8-1.fc38
Summary: Threadsafe RefCell
RPMs:rust-atomic_refcell+default-devel rust-atomic_refcell-devel
Size:25.57 KiB

Package: rust-lib0-0.12.2-1.fc38
Summary: Efficient binary encoding library for Yrs
RPMs:rust-lib0+default-devel rust-lib0+lib0-serde-devel 
rust-lib0+serde-devel rust-lib0+serde_json-devel rust-lib0-devel
Size:56.40 KiB

Package: rust-nix0.24-0.24.3-2.fc38
Summary: Rust friendly bindings to *nix APIs
RPMs:rust-nix0.24+acct-devel rust-nix0.24+aio-devel 
rust-nix0.24+default-devel rust-nix0.24+dir-devel rust-nix0.24+env-devel 
rust-nix0.24+event-devel rust-nix0.24+feature-devel rust-nix0.24+fs-devel 
rust-nix0.24+hostname-devel rust-nix0.24+inotify-devel rust-nix0.24+ioctl-devel 
rust-nix0.24+kmod-devel rust-nix0.24+memoffset-devel rust-nix0.24+mman-devel 
rust-nix0.24+mount-devel rust-nix0.24+mqueue-devel rust-nix0.24+net-devel 
rust-nix0.24+personality-devel rust-nix0.24+poll-devel 
rust-nix0.24+process-devel rust-nix0.24+pthread-devel rust-nix0.24+ptrace-devel 
rust-nix0.24+quota-devel rust-nix0.24+reboot-devel rust-nix0.24+resource-devel 
rust-nix0.24+sched-devel rust-nix0.24+signal-devel rust-nix0.24+socket-devel 
rust-nix0.24+term-devel rust-nix0.24+time-devel rust-nix0.24+ucontext-devel 
rust-nix0.24+uio-devel rust-nix0.24+user-devel rust-nix0.24+zerocopy-devel 
rust-nix0.24-devel
Size:492.96 KiB

Package: rust-pyo3-build-config0.15-0.15.2-1.fc38
Summary: Build configuration for the PyO3 ecosystem
RPMs:rust-pyo3-build-config0.15+abi3-devel 
rust-pyo3-build-config0.15+abi3-py310-devel 
rust-pyo3-build-config0.15+abi3-py36-devel 
rust-pyo3-build-config0.15+abi3-py37-devel 
rust-pyo3-build-config0.15+abi3-py38-devel 
rust-pyo3-build-config0.15+abi3-py39-devel 
rust-pyo3-build-config0.15+default-devel 
rust-pyo3-build-config0.15+resolve-config-devel rust-pyo3-build-config0.15-devel
Size:86.78 KiB

Package: rust-pyo3-ffi-0.16.6-1.fc38
Summary: Python-API bindings for the PyO3 ecosystem
RPMs:rust-pyo3-ffi+abi3-devel rust-pyo3-ffi+abi3-py310-devel 
rust-pyo3-ffi+abi3-py37-devel rust-pyo3-ffi+abi3-py38-devel 
rust-pyo3-ffi+abi3-py39-devel rust-pyo3-ffi+default-devel 
rust-pyo3-ffi+extension-module-devel rust-pyo3-ffi-devel
Size:133.16 KiB

Package: rust-pyo3-macros-backend0.15-0.15.2-1.fc38
Summary: Code generation for PyO3 package
RPMs:rust-pyo3-macros-backend0.15+default-devel 
rust-pyo3-macros-backend0.15-devel
Size:60.70 KiB

Package: rust-pyo3-macros0.15-0.15.2-1.fc38
Summary: Proc macros for PyO3 package
RPMs:rust-pyo3-macros0.15+default-devel 
rust-pyo3-macros0.15+multiple-pymethods-devel rust-pyo3-macros0.15-devel
Size:29.55 KiB

Re: List of long term FTBFS packages to be retired in February​

[Jerry James]

On Wed, Jan 18, 2023 at 5:58 AM Miro Hrončok  wrote:
> Based on the current fail to build from source policy, the following packages
> should be retired from Fedora 38 approximately one week before branching.

[snip]

> maven-scm  mizdebsk, trawets

For those affected by this, I've made a COPR with a possible
resolution: 
https://copr.fedorainfracloud.org/coprs/jjames/buildnumber-maven-plugin/.
Things to note:

- plexus-interactivity must be unretired.
- I first tried updating maven-scm to version 1.13.0, but it requires
an older version of jgit than we have in Fedora Rawhide.  It would not
build.  I had to go to 2.0.0-M3 to get a successful build.
- There is a possible XMvn bug affecting maven-scm.  See the comment
in the %build section.  There are duplicate entries in .xmvn-reactor
for every pom.xml that includes pom.  I'm not
certain if this is an XMvn bug, or if the maven-scm pom.xml files are
wrong somehow.
- buildnumber-maven-plugin version 1.4 was too old, so I moved all the
way to 3.0.0.  Even then, it needed a small patch to work with
maven-scm 2.0.0.

Or we can all remove mvn-scm and buildnumber-maven-plugin from our
respective packages' POMs.


--
Jerry James
https://www.jamezone.org/
___
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/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[EPEL-devel] Fedora EPEL 7 updates-testing report

[updates]

The following Fedora EPEL 7 Security updates need testing:
 Age  URL
   5  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-a884ce2c71   
tor-0.4.7.13-1.el7
   3  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-3ab686a79f   
singularity-ce-3.10.5-1.el7


The following builds have been pushed to Fedora EPEL 7 updates-testing

ipython-3.2.3-1.el7

Details about builds:



 ipython-3.2.3-1.el7 (FEDORA-EPEL-2023-afd7021128)
 An enhanced interactive Python shell

Update Information:

- Update to 3.2.3 - Fix CVE-2022-21699, resolves rhbz#2135164

ChangeLog:

* Sun Oct 23 2022 Carl George  - 3.2.3-1
- Update to 3.2.3
- Fix CVE-2022-21699, resolves rhbz#2135164

References:

  [ 1 ] Bug #2135164 - CVE-2022-21699 ipython: arbitrary code execution by 
cross user temporary files mismanagment [epel-7]
https://bugzilla.redhat.com/show_bug.cgi?id=2135164


___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Test-Announce] 2023-01-23 @ 16:00 UTC - Fedora QA Meeting

[Adam Williamson]

# Fedora Quality Assurance Meeting
# Date: 2023-01-23
# Time: 16:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.libera.chat

Greetings testers!

It's time for the first meeting of 2023! Let's check in and see how
everything's going.

If anyone has any other items for the agenda, please reply to this
email and suggest them! Thanks.

== Proposed Agenda Topics ==

1. Previous meeting follow-up
2. Fedora 38 check-in
3. Test Day / community event status
4. Open floor
-- 
Adam Williamson
Fedora QA
IRC: adamw | Twitter: adamw_ha
https://www.happyassassin.net

___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue
___
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/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Rawhide updates stuck for the past ~4 hours?

[Michel Alexandre Salim]

On Fri, 2023-01-20 at 22:44 +0100, Miro Hrončok wrote:
> My Rawhide Bodhi updates are stuck in pending, so I've checked
> 
> https://bodhi.fedoraproject.org/updates/?releases=F38
> 
> and it seems that everything created after 2023-01-20 17:35 UTC is
> stuck.
> 
> Is this a natural slowdown due to the mass rebuild or is something
> broken?
> 
Per nirik on #releng, looks like robosignatory is backlogged on signing
packages.

Best,

-- 
Michel Alexandre Salim
identities:
https://keyoxide.org/5dce2e7e9c3b1cffd335c1d78b229d2f7ccc04f2


signature.asc
Description: This is a digitally signed message part
___
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/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Rawhide updates stuck for the past ~4 hours?

[Miro Hrončok]

My Rawhide Bodhi updates are stuck in pending, so I've checked

https://bodhi.fedoraproject.org/updates/?releases=F38

and it seems that everything created after 2023-01-20 17:35 UTC is stuck.

Is this a natural slowdown due to the mass rebuild or is something broken?

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
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/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[rpms/perl-Dist-Zilla-Plugin-Test-Compile] PR #1: Package tests and update license to SPDX format

[Michal Josef Špaček]

mspacek merged a pull-request against the project: 
`perl-Dist-Zilla-Plugin-Test-Compile` that you are following.

Merged pull-request:

``
Package tests and update license to SPDX format
``

https://src.fedoraproject.org/rpms/perl-Dist-Zilla-Plugin-Test-Compile/pull-request/1
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: When to close CVE's

[Richard Shaw]

On Fri, Jan 20, 2023 at 2:29 PM Demi Marie Obenour 
wrote:

>
> My general rule is that a security fix is worth backporting a SONAME change
> for, if there is no way to backport the patch.
>

In this case all the Fedora branches are recent enough but EL 7 and EL 8
are not and are impractical to fix at this point.

I've already been bitten in the past making major updates to EL branches. I
believe this was also with OpenImageIO. Someone was using it at work for
their project and had validated against the current version. Obviously in
this case there is NO way to determine out of repo dependencies.

The update was required to support a Review Request package so he
ultimately re-validated against the newer version, but lesson learned.

Since all of the severities are Medium and not High I think I will leave it
as is.

Thanks,
Richard
___
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/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: When to close CVE's

[Demi Marie Obenour]

On 1/20/23 10:48, Richard Shaw wrote:
> On Fri, Jan 20, 2023 at 9:22 AM Gary Buhrmaster 
> wrote:
> 
>> On Fri, Jan 20, 2023 at 1:54 PM Richard Shaw  wrote:
>>>
>>> So is it when a build is complete in Rawhide? Or must *ALL* active
>> releases get the "fix"?
>>>
>>
>> I am not sure it is official policy/practice, but in
>> theory I would think that the CVE is technically
>> closed when all impacted Fedora releases get
>> the fix, but if you use various "Resolves rhbz#1234567"
>> syntax in the change log (and I generally try to
>> do so in addition to referencing the CVE by it's
>> identifier) I seem to recall that as soon as the
>> package hits rawhide the issue gets closed.  It
>> is therefore up to the packager to make sure they
>> have actually done the necessary builds/backports
>> to previous releases as appropriate (not all CVEs
>> may apply to previous Fedora releases as they
>> may have different package versions, of course).
>> I have mostly decided that in practice, as long as
>> I have done any appropriate builds/backports, and
>> one is just waiting for the usual distribution delays,
>> that it is good enough (although high severity
>> CVEs may need special handling).
>>
>> Or are you asking something different?
>>
> 
> I think in practical terms that makes sense but our tools don't really
> help.
> 
> Let's take the case of OpenImageIO[1][2], which is why I'm asking this
> question, I only update Rawhide when SONAME is bumped, so if a CVE is only
> fixed in the latest release, then only Rawhide, or Rawhide-1 (depending on
> when we branch) gets the fix.

My general rule is that a security fix is worth backporting a SONAME change
for, if there is no way to backport the patch.
-- 
Sincerely,
Demi Marie Obenour (she/her/hers)
___
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/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[rpms/perl-Dist-Zilla-Plugin-Test-Compile] PR #1: Package tests and update license to SPDX format

[Michal Josef Špaček]

mspacek opened a new pull-request against the project: 
`perl-Dist-Zilla-Plugin-Test-Compile` that you are following:
``
Package tests and update license to SPDX format
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Dist-Zilla-Plugin-Test-Compile/pull-request/1
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

SPDX office hours - Second Session

[David Cantrell]

Hello.

The owners of SPDX Change proposal want to have this Change as smooth as
possible.  And we decided to setup Office hours.

Do you have any questions about SPDX migration?
Do you hesitate about what steps you should take?
How to proceed with your package? We will do our best to help you.

This is intended to be bi-weekly.

Every time in a different time, to match the time of different people in
different time zones.

Wednesday 2023-02-01 01:00-02:00 UTC

(8pm 2023-01-31 EST, 5pm 2023-01-31 PST, 2am 2023-02-01 CET, 10am 2023-02-01 
JST)

Google Meet joining info
Video call link: meet.google.com/zsu-tbci-cfi
Or dial: (US) +1 413-752-4319  PIN: 755 481 969#
More phone numbers: 
https://meet.google.com/tel/zsu-tbci-cfi?pin=7170141193104=1=1
Or join via SIP: 7170141193...@gmeet.redhat.com

-- 
David Cantrell 
Red Hat, Inc. | Boston, MA | EST5EDT
___
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/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[EPEL-devel] Re: New EPEL KDE Proposal

[Neal Gompa]

On Fri, Jan 20, 2023 at 2:44 PM Troy Dawson  wrote:
>
> I plan on making two changes to the current EPEL KDE Update Schedule.[1]
>
> ** First:  EPEL 8 KDE Plasma Desktop is going to stay at the releases that 
> they currently are at.  We will backport major security fixes.  Bugs and 
> bugfixes will be best effort.  But we will not do any across the board 
> updates.
> This is due to the older libraries in RHEL 8.  We've hit the limit that the 
> newer KDE versions can run on the older libraries.
> EPEL 8 will have these versions (with a few exceptions)
> plasma - 5.24
> kf5 - 5.96
> kde apps - 22.04 / 21.12 / 21.08 and some 21.04
> qt5 - 5.15
>
> **Second: We will do the across the board updates to the main epel branches 
> [2] every six months instead of once a year.  They will coincide with each 
> RHEL minor release, instead of every other RHEL minor release.
> With the last release, we found that KDE packages like to build on 
> themselves.  Meaning that some 22.04 packages needed a previous version of at 
> least 21.08 to build.  That was fine on epel-next where we had updated each 
> six months.  But when we tried to build on plain epel8 or epel9, things got 
> complicated.
> Doing a release every six months will allow users to get the newer updates 
> faster.  And although it sounds counter-intuitive, it will save the 
> maintainers time.
>
> We haven't officially made this change yet.  So if anyone sees any issues 
> and/or problems.  Please let us know.
>

I fully support this change. I think our users will benefit from this
considerably. :)



-- 
真実はいつも一つ！/ Always, there's only one truth!
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[EPEL-devel] New EPEL KDE Proposal

[Troy Dawson]

I plan on making two changes to the current EPEL KDE Update Schedule.[1]

** First:  EPEL 8 KDE Plasma Desktop is going to stay at the releases that
they currently are at.  We will backport major security fixes.  Bugs and
bugfixes will be best effort.  But we will not do any across the board
updates.
This is due to the older libraries in RHEL 8.  We've hit the limit that the
newer KDE versions can run on the older libraries.
EPEL 8 will have these versions (with a few exceptions)
plasma - 5.24
kf5 - 5.96
kde apps - 22.04 / 21.12 / 21.08 and some 21.04
qt5 - 5.15

**Second: We will do the across the board updates to the main epel branches
[2] every six months instead of once a year.  They will coincide with each
RHEL minor release, instead of every other RHEL minor release.
With the last release, we found that KDE packages like to build on
themselves.  Meaning that some 22.04 packages needed a previous version of
at least 21.08 to build.  That was fine on epel-next where we had updated
each six months.  But when we tried to build on plain epel8 or epel9,
things got complicated.
Doing a release every six months will allow users to get the newer updates
faster.  And although it sounds counter-intuitive, it will save the
maintainers time.

We haven't officially made this change yet.  So if anyone sees any issues
and/or problems.  Please let us know.

Thank You
Troy Dawson
Fedora KDE SIG

[1] - https://fedoraproject.org/wiki/SIGs/KDE/EPEL#Update_Schedule
[2] - Currently epel9, but epel10 when it comes out
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: When to close CVE's

[Gary Buhrmaster]

On Fri, Jan 20, 2023 at 4:47 PM Gary Buhrmaster
 wrote:

> such as yourself are contentious about
> doing the right thing).

Obviously that word should have been conscientious
(I hate autocorrect).
___
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/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Improving Fedora boot time when libvirt is installed

[Colin Walters]

On Thu, Jan 19, 2023, at 11:53 AM, Gordon Messmer wrote:
> On 2023-01-19 00:55, Lennart Poettering wrote:
>>
>> What you could do is split up the problem: have iscsi-starter.service
>> or so, that is separate from the iscsi.service main service. The
>> former's job would be to scan if iscsi volumes are configured. If it
>> finds configured ones, it would then issue "systemctl start --no-block
>> iscsi.service" to enqueue a start job for the real thing.
>
>
> Something like that was suggested last year, and Colin Walters objected, 
> for what that's worth.
>
> If the PR to allow installing only the "core" storage drivers is 
> rejected, then I'll work on a PR to implement this change instead.

Heh well, I'm obviously going to defer to Lennart if he has an opinion on how 
you should do something with systemd.

It wouldn't even be the first thing calling `systemctl start` in the boot 
process...sadly there's NetworkManager dispatcher scripts that *also* 
`try-restart iscsid` =/

That said, I do think a general better pattern is to either:

- Have the daemon itself run `systemctl enable` if it detects the scenario; 
though the problem with this is that if the daemon is removed, the enablement 
state will "leak", but a workaround for that is to ship a unit in your daemon 
which is itself conditionally enabled, and *that* unit has 
Wants/Requires=iscsid.service.  So there'd be 
libvirt-iscsid-requirement.service or so.
- Write a "stamp file" to /var/lib/mydaemon, then a generator can key off that. 
 (Instead of e.g. starting up libvirt and parsing its whole database etc.)  But 
this intersects with the /var requirement, unless you move it to /etc.  

(I had actually forgotten though that it's not guaranteed /var is mounted, I'm 
pretty sure we have some implicit requirements on that some places)

This thread is really similar to https://github.com/containers/podman/pull/17110
___
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/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2162566] perl-Function-Parameters-2.001004 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2162566

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version||perl-Function-Parameters-2.
   ||1.4-1.fc38
 Status|MODIFIED|CLOSED
 Resolution|--- |ERRATA
Last Closed||2023-01-20 17:57:52



--- Comment #2 from Fedora Update System  ---
FEDORA-2023-aaf2bad48a has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2162566
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[rpms/perl-Tangerine] PR #1: Package tests and update license to SPDX format

[Michal Josef Špaček]

mspacek merged a pull-request against the project: `perl-Tangerine` that you 
are following.

Merged pull-request:

``
Package tests and update license to SPDX format
``

https://src.fedoraproject.org/rpms/perl-Tangerine/pull-request/1
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2162740] New: perl-Module-CoreList-5.20230120 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2162740

Bug ID: 2162740
   Summary: perl-Module-CoreList-5.20230120 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Module-CoreList
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: jose.p.oliveira@gmail.com, jples...@redhat.com,
mspa...@redhat.com,
perl-devel@lists.fedoraproject.org, spo...@gmail.com,
st...@silug.org
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 5.20230120
Upstream release that is considered latest: 5.20230120
Current version/release in rawhide: 5.20221220-1.fc38
URL: http://search.cpan.org/dist/Module-CoreList/

Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at:
https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.


Based on the information from Anitya:
https://release-monitoring.org/project/3080/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/perl-Module-CoreList


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2162740
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: When to close CVE's

[Gary Buhrmaster]

On Fri, Jan 20, 2023 at 4:53 PM Kevin P. Fleming  wrote:

> Small clarification: where you wrote 'component' you meant 'product' :-)
> BZ has both Products and Components, forming two levels. RHEL 7/8/9 are
> Products, on the same level as Fedora.

Thanks.  I suppose I should have actually checked
the terms before posting.  But posting before
checking is a time honored tradition which I
am too often guilty of :-).
___
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/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: New WASM related mailing list

[Jun Aruga (he / him)]

>> as there has been an interest in creating WASM SIG, I moved on with it.
>>
>> You can already join our mailing list: wasm-...@lists.fedoraproject.org

Thanks for the malling list!

I just wanted to share the page to subscribe to the WASM SIG.
https://lists.fedoraproject.org/admin/lists/wasm-sig.lists.fedoraproject.org/

--
Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
See  for
the timezone.
___
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/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: When to close CVE's

[Kevin P. Fleming]

On 1/20/23 11:47, Gary Buhrmaster wrote:

I agree, and that seems to be an artifact of
the single Fedora component in RHBZ, which
treats Fedora as one thing.

I supposed (in theory again) that there could
be a master bugzilla for the CVE which depends
on child bugzillas for each impacted Fedora
release, and would get (auto) closed only when
all the child bugzillas are resolved (either by
updates or the Fedora release aging out).

Alternatively, an entirely different bugzilla for
each Fedora release (but as Fedora is just
a single component, unlike each RHEL
which has different components for each
version, I don't think that works).
Small clarification: where you wrote 'component' you meant 'product' :-) 
BZ has both Products and Components, forming two levels. RHEL 7/8/9 are 
Products, on the same level as Fedora.


--
Kevin P. Fleming
He/Him/His
Principal Program Manager, RHEL
Red Hat US/Eastern Time Zone
___
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/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: When to close CVE's

[Gary Buhrmaster]

On Fri, Jan 20, 2023 at 3:48 PM Richard Shaw  wrote:

> I think in practical terms that makes sense but our tools don't really help.

I agree, and that seems to be an artifact of
the single Fedora component in RHBZ, which
treats Fedora as one thing.

I supposed (in theory again) that there could
be a master bugzilla for the CVE which depends
on child bugzillas for each impacted Fedora
release, and would get (auto) closed only when
all the child bugzillas are resolved (either by
updates or the Fedora release aging out).

Alternatively, an entirely different bugzilla for
each Fedora release (but as Fedora is just
a single component, unlike each RHEL
which has different components for each
version, I don't think that works).

> So I guess what I'm asking is if there is a specific policy around this? If 
> not, should there be?

I think there should be at least an agreed
upon best practice, which needs to be
explicitly documented somewhere (maybe
it is, but I don't recall seeing it, so I am
not following it).

So, as with much of Fedora, we fall back
to depending on (usually volunteer)
packagers to do the right thing (which works
out well most of the time because packagers
such as yourself are contentious about
doing the right thing).
___
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/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2162728] New: perl-CPAN-Perl-Releases-5.20230120 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2162728

Bug ID: 2162728
   Summary: perl-CPAN-Perl-Releases-5.20230120 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-CPAN-Perl-Releases
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: iarn...@gmail.com, jples...@redhat.com,
mspa...@redhat.com, perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 5.20230120
Upstream release that is considered latest: 5.20230120
Current version/release in rawhide: 5.20221220-1.fc38
URL: http://search.cpan.org/dist/CPAN-Perl-Releases/

Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at:
https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.


Based on the information from Anitya:
https://release-monitoring.org/project/5881/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/perl-CPAN-Perl-Releases


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2162728
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2160057] perl-WWW-Curl-4.17-31.fc38 FTBFS: curlopt-constants.c:19:51: error: 'CURL_DEPRECATED' undeclared

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2160057



--- Comment #1 from Petr Pisar  ---
Built into f38-rebuild tag. This package will appear in F38 once the tag is
merged into f38-candidate.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2160057
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2160057] perl-WWW-Curl-4.17-31.fc38 FTBFS: curlopt-constants.c:19:51: error: 'CURL_DEPRECATED' undeclared

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2160057

Petr Pisar  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED
   Fixed In Version||perl-WWW-Curl-4.17-33.fc38




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2160057
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2160057] perl-WWW-Curl-4.17-31.fc38 FTBFS: curlopt-constants.c:19:51: error: 'CURL_DEPRECATED' undeclared

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2160057

Petr Pisar  changed:

   What|Removed |Added

   Assignee|emman...@seyman.fr  |ppi...@redhat.com
 Status|NEW |ASSIGNED




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2160057
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: When to close CVE's

[Richard Shaw]

On Fri, Jan 20, 2023 at 9:22 AM Gary Buhrmaster 
wrote:

> On Fri, Jan 20, 2023 at 1:54 PM Richard Shaw  wrote:
> >
> > So is it when a build is complete in Rawhide? Or must *ALL* active
> releases get the "fix"?
> >
>
> I am not sure it is official policy/practice, but in
> theory I would think that the CVE is technically
> closed when all impacted Fedora releases get
> the fix, but if you use various "Resolves rhbz#1234567"
> syntax in the change log (and I generally try to
> do so in addition to referencing the CVE by it's
> identifier) I seem to recall that as soon as the
> package hits rawhide the issue gets closed.  It
> is therefore up to the packager to make sure they
> have actually done the necessary builds/backports
> to previous releases as appropriate (not all CVEs
> may apply to previous Fedora releases as they
> may have different package versions, of course).
> I have mostly decided that in practice, as long as
> I have done any appropriate builds/backports, and
> one is just waiting for the usual distribution delays,
> that it is good enough (although high severity
> CVEs may need special handling).
>
> Or are you asking something different?
>

I think in practical terms that makes sense but our tools don't really
help.

Let's take the case of OpenImageIO[1][2], which is why I'm asking this
question, I only update Rawhide when SONAME is bumped, so if a CVE is only
fixed in the latest release, then only Rawhide, or Rawhide-1 (depending on
when we branch) gets the fix.

Typically in Bodhi you would mark the BZ as being fixed by the release
which by default closes the bug.

So I guess what I'm asking is if there is a specific policy around this? If
not, should there be?

Thanks,
Richard

[1] Actually not the best example, but the most immediate one. Upstream
(Larry) is actually quite good at backporting changes when needed.
[2]
https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW_status=ASSIGNED=Fedora=OpenImageIO=Fedora=Fedora%20EPEL
___
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/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: New WASM related mailing list

[Jun Aruga (he / him)]

On Thu, Jan 19, 2023 at 6:23 PM Zuzana Svetlikova  wrote:
>
>  Hi all,
>
> as there has been an interest in creating WASM SIG, I moved on with it.
>
> You can already join our mailing list: wasm-...@lists.fedoraproject.org

Thanks for the malling list!

I just wanted to share the page to subscribe to the WASM SIG.
https://lists.fedoraproject.org/admin/lists/wasm-sig.lists.fedoraproject.org/

Note I initially sent an email by "Reply All", then I got the message
below from the Fedora
s mailing system. So, just reply to the devel@ only. Sorry for the
duplicated email, if the moderator approved.

> Subject: Your message to devel@lists.fedoraproject.org awaits moderator 
> approval
>
> Your mail to 'devel@lists.fedoraproject.org
> ' with the subject
>
> Re: New WASM related mailing list
>
> Is being held until the list moderator can review it for approval.
>
> The message is being held because:
>
> Message has more than 10 recipients
>
> Either the message will get posted to the list, or you will receive
> notification of the moderator's decision.

--
Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
See  for
the timezone.
___
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/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: When to close CVE's

[Gary Buhrmaster]

On Fri, Jan 20, 2023 at 1:54 PM Richard Shaw  wrote:
>
> So is it when a build is complete in Rawhide? Or must *ALL* active releases 
> get the "fix"?
>

I am not sure it is official policy/practice, but in
theory I would think that the CVE is technically
closed when all impacted Fedora releases get
the fix, but if you use various "Resolves rhbz#1234567"
syntax in the change log (and I generally try to
do so in addition to referencing the CVE by it's
identifier) I seem to recall that as soon as the
package hits rawhide the issue gets closed.  It
is therefore up to the packager to make sure they
have actually done the necessary builds/backports
to previous releases as appropriate (not all CVEs
may apply to previous Fedora releases as they
may have different package versions, of course).
I have mostly decided that in practice, as long as
I have done any appropriate builds/backports, and
one is just waiting for the usual distribution delays,
that it is good enough (although high severity
CVEs may need special handling).

Or are you asking something different?
___
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/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[rpms/perl-Wx] PR #2: Rebuild with wxWidgets 3.2

[Scott Talbert]

swt2c commented on the pull-request: `Rebuild with wxWidgets 3.2` that you are 
following:
``
> I manually applied this, since it went out of sync with the mass rebuild.
> 
> I did notice that wxWidgets 3.2 doesn't seem to be in rawhide yet, you might 
> want to make sure you get that in there quickly or this will start failing to 
> build. :)

Huh?  It's been in Rawhide since July.
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Wx/pull-request/2
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[rpms/perl-Tangerine] PR #1: Package tests and update license to SPDX format

[Michal Josef Špaček]

mspacek opened a new pull-request against the project: `perl-Tangerine` that 
you are following:
``
Package tests and update license to SPDX format
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Tangerine/pull-request/1
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[rpms/perl-Wx] PR #2: Rebuild with wxWidgets 3.2

[Tom Callaway]

spot closed without merging a pull-request against the project: `perl-Wx` that 
you
are following.

Closed pull-request:

``
Rebuild with wxWidgets 3.2
``

https://src.fedoraproject.org/rpms/perl-Wx/pull-request/2
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[rpms/perl-Wx] PR #2: Rebuild with wxWidgets 3.2

[Tom Callaway]

spot commented on the pull-request: `Rebuild with wxWidgets 3.2` that you are 
following:
``
I manually applied this, since it went out of sync with the mass rebuild.

I did notice that wxWidgets 3.2 doesn't seem to be in rawhide yet, you might 
want to make sure you get that in there quickly or this will start failing to 
build. :)
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Wx/pull-request/2
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2161894] Branch Request: perl-Net-GitHub for epel8

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2161894

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #2 from Fedora Update System  ---
FEDORA-EPEL-2023-7a53ea10f3 has been submitted as an update to Fedora EPEL 8.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-7a53ea10f3


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2161894
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[rpms/perl-Alien-wxWidgets] PR #2: Rebuild with wxWidgets 3.2

[Tom Callaway]

spot merged a pull-request against the project: `perl-Alien-wxWidgets` that you 
are following.

Merged pull-request:

``
Rebuild with wxWidgets 3.2
``

https://src.fedoraproject.org/rpms/perl-Alien-wxWidgets/pull-request/2
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: When to close CVE's

[Siddhesh Poyarekar]

On Fri, Jan 20, 2023 at 8:54 AM Richard Shaw  wrote:
>
> So is it when a build is complete in Rawhide? Or must *ALL* active releases 
> get the "fix"?
>

It depends on the severity of the CVE.  For High severity ones it
makes sense to fix in all active releases, less so for Medium/Low
CVEs.

hth

Sid
___
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/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2160057] perl-WWW-Curl-4.17-31.fc38 FTBFS: curlopt-constants.c:19:51: error: 'CURL_DEPRECATED' undeclared

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2160057

Petr Pisar  changed:

   What|Removed |Added

Link ID||CPAN 145992




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2160057
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

When to close CVE's

[Richard Shaw]

So is it when a build is complete in Rawhide? Or must *ALL* active releases
get the "fix"?

Thanks,
Richard
___
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/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[rpms/tangerine] PR #1: Simplify build and install phases

[Michal Josef Špaček]

mspacek merged a pull-request against the project: `tangerine` that you are 
following.

Merged pull-request:

``
Simplify build and install phases
``

https://src.fedoraproject.org/rpms/tangerine/pull-request/1
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[rpms/tangerine] PR #1: Simplify build and install phases

[Michal Josef Špaček]

mspacek opened a new pull-request against the project: `tangerine` that you are 
following:
``
Simplify build and install phases
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/tangerine/pull-request/1
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[rpms/perl-Dist-Zilla-App-Command-cover] PR #1: Update license to SPDX format

[Michal Josef Špaček]

mspacek merged a pull-request against the project: 
`perl-Dist-Zilla-App-Command-cover` that you are following.

Merged pull-request:

``
Update license to SPDX format
``

https://src.fedoraproject.org/rpms/perl-Dist-Zilla-App-Command-cover/pull-request/1
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2161894] Branch Request: perl-Net-GitHub for epel8

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2161894

Jan Pazdziora  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
   Assignee|lkund...@v3.sk  |jpazdzi...@redhat.com
   Doc Type|--- |If docs needed, set a value



--- Comment #1 from Jan Pazdziora  ---
I requested the EPEL 8 branch:
https://pagure.io/releng/fedora-scm-requests/issue/50543


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2161894
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[rpms/perl-Dist-Zilla-App-Command-cover] PR #1: Update license to SPDX format

[Michal Josef Špaček]

mspacek opened a new pull-request against the project: 
`perl-Dist-Zilla-App-Command-cover` that you are following:
``
Update license to SPDX format
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Dist-Zilla-App-Command-cover/pull-request/1
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2162651] New: perl-Sub-Quote-2.006008 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2162651

Bug ID: 2162651
   Summary: perl-Sub-Quote-2.006008 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Sub-Quote
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: jples...@redhat.com, mspa...@redhat.com,
perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 2.006008
Upstream release that is considered latest: 2.006008
Current version/release in rawhide: 2.006006-10.fc37
URL: http://search.cpan.org/dist/Sub-Quote/

Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at:
https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.


Based on the information from Anitya:
https://release-monitoring.org/project/12678/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/perl-Sub-Quote


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2162651
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Web Assembly on Fedora: interested in a Fedora SIG to work on this?

[Jun Aruga (he / him)]

I am happy to join the group Now. I have a limited time, and more
prioritized tasks in Fedora, but maybe I can help something for the
SIG.

-- 
Jun | He - Him | Timezone: UTC+1 or 2, Czech Republic
See  for
the timezone.
___
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/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2162633] Upgrade perl-Date-Extract to 0.07

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2162633

Ralf Corsepius  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED



--- Comment #1 from Ralf Corsepius  ---
This upgrade is a bit complicated.

It fixes a bug/malfunction in rawhide having been introduced by newer versions
of 
DateTime::Format::Natural which require Test::MockTime::HiRes, but is
incompatible 
and inapplicable to fedora <= 37 due lack of Test::MockTime::HiRes.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2162633
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2162566] perl-Function-Parameters-2.001004 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2162566

Fedora Update System  changed:

   What|Removed |Added

 Status|NEW |MODIFIED



--- Comment #1 from Fedora Update System  ---
FEDORA-2023-aaf2bad48a has been submitted as an update to Fedora 38.
https://bodhi.fedoraproject.org/updates/FEDORA-2023-aaf2bad48a


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2162566
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2162633] New: Upgrade perl-Date-Extract to 0.07

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2162633

Bug ID: 2162633
   Summary: Upgrade perl-Date-Extract to 0.07
   Product: Fedora
   Version: rawhide
   URL: https://metacpan.org/release/Date-Extract
Status: NEW
 Component: perl-Date-Extract
  Assignee: rc040...@freenet.de
  Reporter: jples...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: perl-devel@lists.fedoraproject.org,
rc040...@freenet.de
  Target Milestone: ---
Classification: Fedora



Latest Fedora delivers 0.06 version. Upstream released 0.07. When you have free
time, please upgrade it.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2162633
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

releng pushed to rpms/perl-namespace-sweep (rawhide). "Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild (..more)"

[notifications]

Notification time stamped 2023-01-20 08:04:21 UTC

From 9e722d85abc2b693536e847504845a8997ebff24 Mon Sep 17 00:00:00 2001
From: Fedora Release Engineering 
Date: Jan 20 2023 08:04:16 +
Subject: Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild


Signed-off-by: Fedora Release Engineering 

---

diff --git a/perl-namespace-sweep.spec b/perl-namespace-sweep.spec
index 2c0cb89..45b13f8 100644
--- a/perl-namespace-sweep.spec
+++ b/perl-namespace-sweep.spec
@@ -1,6 +1,6 @@
 Name:   perl-namespace-sweep
 Version:0.006
-Release:19%{?dist}
+Release:20%{?dist}
 Summary:Sweep up imported subs in your classes
 License:GPL-1.0-or-later OR Artistic-1.0-Perl
 URL:https://metacpan.org/release/namespace-sweep
@@ -62,6 +62,9 @@ will still be able to use the imported functions without any 
problems.
 %{_mandir}/man3/*
 
 %changelog
+* Fri Jan 20 2023 Fedora Release Engineering  - 
0.006-20
+- Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild
+
 * Mon Nov 28 2022 Ralf Corsépius  - 0.006-19
 - Modernize spec.
 - Convert license to SPDX.



https://src.fedoraproject.org/rpms/perl-namespace-sweep/c/9e722d85abc2b693536e847504845a8997ebff24?branch=rawhide
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue