date:20230331

[Bug 2182563] perl-DateTime-TimeZone-2.60 is available

2023-03-31 Thread bugzilla

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



--- Comment #6 from Fedora Update System  ---
FEDORA-2023-7fda8f4297 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 --refresh
--advisory=FEDORA-2023-7fda8f4297`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2023-7fda8f4297

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2182563
___
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 2182563] perl-DateTime-TimeZone-2.60 is available

2023-03-31 Thread bugzilla

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



--- Comment #5 from Fedora Update System  ---
FEDORA-2023-7c0abce3ff 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 --refresh
--advisory=FEDORA-2023-7c0abce3ff`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2023-7c0abce3ff

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2182563
___
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 2181308] perl-DateTime-TimeZone-2.58 is available

2023-03-31 Thread bugzilla

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



--- Comment #12 from Fedora Update System  ---
FEDORA-2023-7c0abce3ff 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 --refresh
--advisory=FEDORA-2023-7c0abce3ff`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2023-7c0abce3ff

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2181308
___
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 2181578] perl-DateTime-TimeZone-2.59 is available

2023-03-31 Thread bugzilla

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



--- Comment #8 from Fedora Update System  ---
FEDORA-2023-7c0abce3ff 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 --refresh
--advisory=FEDORA-2023-7c0abce3ff`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2023-7c0abce3ff

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2181578
___
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

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

2023-03-31 Thread updates

The following Fedora EPEL 7 Security updates need testing:
 Age  URL
   5  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-9a3db4278b   
openbgpd-7.9-1.el7


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

chromium-111.0.5563.146-1.el7
seamonkey-2.53.16-1.el7

Details about builds:



 chromium-111.0.5563.146-1.el7 (FEDORA-EPEL-2023-e0ec985df4)
 A WebKit (Blink) powered web browser that Google doesn't want you to use

Update Information:

update to 111.0.5563.146    update to 111.0.5563.110. Fixes the following
security issues:  CVE-2023-1528 CVE-2023-1529 CVE-2023-1530 CVE-2023-1531
CVE-2023-1532 CVE-2023-1533 CVE-2023-1534

ChangeLog:

* Tue Mar 28 2023 Than Ngo  - 111.0.5563.146-1
- update to 111.0.5563.146
* Sat Mar 25 2023 Neal Gompa  - 111.0.5563.110-2
- Fix ffmpeg note in README.fedora
* Wed Mar 22 2023 Than Ngo  - 111.0.5563.110-1
- update to 111.0.5563.110
* Sun Mar 12 2023 Neal Gompa  - 111.0.5563.64-2
- Rebuild for ffmpeg 6.0

References:

  [ 1 ] Bug #2180693 - CVE-2023-1528 CVE-2023-1529 CVE-2023-1530 CVE-2023-1531 
CVE-2023-1532 CVE-2023-1533 CVE-2023-1534 chromium: various flaws [fedora-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2180693
  [ 2 ] Bug #2180694 - CVE-2023-1528 CVE-2023-1529 CVE-2023-1530 CVE-2023-1531 
CVE-2023-1532 CVE-2023-1533 CVE-2023-1534 chromium: various flaws [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2180694




 seamonkey-2.53.16-1.el7 (FEDORA-EPEL-2023-7be8f2df20)
 Web browser, e-mail, news, IRC client, HTML editor

Update Information:

Update to 2.53.16  Langpacks are now provided in the modern form of web
extensions. This may take a bit longer at startup if all languages are enabled
at the same time. To avoid this, just disable unneeded languages by Add-ons
Manager. (Note, langpacks are related to the language of the application menus
etc., and are not related to the Web content at all).

ChangeLog:

* Thu Mar 30 2023 Dmitry Butskoy  2.53.16-1
- update to 2.53.16


___
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

[Bug 2182563] perl-DateTime-TimeZone-2.60 is available

2023-03-31 Thread bugzilla

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #4 from Fedora Update System  ---
FEDORA-2023-ddbe264c1a has been pushed to the Fedora 38 testing repository.

You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2023-ddbe264c1a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2182563
___
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 2180461] perl-Test2-Suite-0.000150 is available

2023-03-31 Thread bugzilla

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-Test2-Suite-0.000150-1 |perl-Test2-Suite-0.000150-1
   |.fc38   |.fc38
   |perl-Test2-Suite-0.000150-1 |perl-Test2-Suite-0.000150-1
   |.fc36   |.fc36
   ||perl-Test2-Suite-0.000150-1
   ||.fc37



--- Comment #20 from Fedora Update System  ---
FEDORA-2023-8059a45d23 has been pushed to the Fedora 37 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=2180461
___
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 2180461] perl-Test2-Suite-0.000150 is available

2023-03-31 Thread bugzilla

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-Test2-Suite-0.000150-1 |perl-Test2-Suite-0.000150-1
   |.fc38   |.fc38
   ||perl-Test2-Suite-0.000150-1
   ||.fc36



--- Comment #19 from Fedora Update System  ---
FEDORA-2023-70eeaf2f67 has been pushed to the Fedora 36 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=2180461
___
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 2180461] perl-Test2-Suite-0.000150 is available

2023-03-31 Thread bugzilla

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |CLOSED
 Resolution|--- |ERRATA
   Fixed In Version||perl-Test2-Suite-0.000150-1
   ||.fc38
Last Closed||2023-04-01 00:16:34



--- Comment #18 from Fedora Update System  ---
FEDORA-2023-7275854584 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=2180461
___
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 2181091] perl-YAML-Tiny-1.74 is available

2023-03-31 Thread bugzilla

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-YAML-Tiny-1.74-1.fc39  |perl-YAML-Tiny-1.74-1.fc39
   ||perl-YAML-Tiny-1.74-1.fc38



--- Comment #7 from Fedora Update System  ---
FEDORA-2023-653edaaea3 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=2181091
___
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

[Test-Announce] 2023-04-03 @ 15:00 UTC - Fedora QA Meeting

2023-03-31 Thread Adam Williamson

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

Greetings testers!

It's meeting time again!

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. Window manager release criterion proposal
3. Fedora 38 status
4. Test Day / community event status
5. Open floor
-- 
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org
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

[Test-Announce] 2023-04-03 @ 16:00 UTC - Fedora 38 Blocker Review Meeting

2023-03-31 Thread Adam Williamson

# F38 Blocker Review meeting
# Date: 2023-04-03
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.libera.chat

Hi folks! We have 2 proposed Final blockers and 2 proposed Final freeze
exception issues to review, so let's have a review meeting.

If you have time this weekend, you can take a look at the proposed or
accepted blockers before the meeting -  the full lists can be found
here: https://qa.fedoraproject.org/blockerbugs/ .

Remember, you can also now vote on bugs outside of review meetings! If
you look at the bug list in the blockerbugs app, you'll see links
labeled "Vote!" next to all proposed blockers and freeze exceptions.
Those links take you to tickets where you can vote.
https://pagure.io/fedora-qa/blocker-review has instructions on how
exactly you do it. We usually go through the tickets shortly before the
meeting and apply any clear votes, so the meeting will just cover bugs
where there wasn't a clear outcome in the ticket voting yet. **THIS
MEANS IF YOU VOTE NOW, THE MEETING WILL BE SHORTER!**

We'll be evaluating these bugs to see if they violate any of the 
Release Criteria and warrant the blocking of a release if they're not 
fixed. Information on the release criteria for F38 can be found on the 
wiki [0].

For more information about the Blocker and Freeze exception process, 
check out these links:
 - https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
 - https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process

And for those of you who are curious how a Blocker Review Meeting 
works - or how it's supposed to go and you want to run one - check out 
the SOP on the wiki:
 - https://fedoraproject.org/wiki/QA:SOP_Blocker_Bug_Meeting

Have a good weekend and see you on Monday!

[0] https://fedoraproject.org/wiki/Fedora_Release_Criteria
-- 
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org
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

Fedora 38 compose report: 20230331.n.0 changes

2023-03-31 Thread Fedora Rawhide Report

OLD: Fedora-38-20230330.n.0
NEW: Fedora-38-20230331.n.0

= SUMMARY =
Added images:2
Dropped images:  1
Added packages:  12
Dropped packages:1
Upgraded packages:   49
Downgraded packages: 1

Size of added packages:  3.34 MiB
Size of dropped packages:199.45 KiB
Size of upgraded packages:   1.15 GiB
Size of downgraded packages: 791.07 KiB

Size change of upgraded packages:   1.46 MiB
Size change of downgraded packages: 5.49 KiB

= ADDED IMAGES =
Image: Silverblue dvd-ostree ppc64le
Path: 
Silverblue/ppc64le/iso/Fedora-Silverblue-ostree-ppc64le-38-20230331.n.0.iso
Image: Kinoite dvd-ostree ppc64le
Path: Kinoite/ppc64le/iso/Fedora-Kinoite-ostree-ppc64le-38-20230331.n.0.iso

= DROPPED IMAGES =
Image: Container_Minimal_Base docker s390x
Path: 
Container/s390x/images/Fedora-Container-Minimal-Base-38-20230330.n.0.s390x.tar.xz

= ADDED PACKAGES =
Package: fedrq-0.5.0-1.fc38
Summary: A tool to query the Fedora and EPEL repositories
RPMs:fedrq
Size:152.26 KiB

Package: python-awscrt-0.16.13-2.fc38
Summary: Python bindings for the AWS Common Runtime
RPMs:python3-awscrt
Size:2.75 MiB

Package: rust-crc64-2.0.0-1.fc38
Summary: CRC64 checksum implementation
RPMs:rust-crc64+default-devel rust-crc64-devel
Size:38.12 KiB

Package: rust-event-manager-0.3.0-1.fc38
Summary: Abstractions for implementing event based systems
RPMs:rust-event-manager+default-devel 
rust-event-manager+remote_endpoint-devel 
rust-event-manager+test_utilities-devel rust-event-manager-devel
Size:60.71 KiB

Package: rust-linux-loader-0.8.1-1.fc38
Summary: Linux kernel image loading crate
RPMs:rust-linux-loader+bzimage-devel rust-linux-loader+default-devel 
rust-linux-loader+elf-devel rust-linux-loader+pe-devel rust-linux-loader-devel
Size:93.00 KiB

Package: rust-pythonize-0.18.0-1.fc38
Summary: Serde Serializer & Deserializer from Rust <--> Python, backed by PyO3
RPMs:rust-pythonize+default-devel rust-pythonize-devel
Size:25.49 KiB

Package: rust-userfaultfd-0.5.1-1.fc38
Summary: Rust bindings for the Linux userfaultfd functionality
RPMs:rust-userfaultfd+default-devel rust-userfaultfd+linux4_14-devel 
rust-userfaultfd+linux5_7-devel rust-userfaultfd-devel
Size:48.23 KiB

Package: rust-userfaultfd-sys-0.4.3-1.fc38
Summary: Low-level bindings for userfaultfd functionality on Linux
RPMs:rust-userfaultfd-sys+default-devel 
rust-userfaultfd-sys+linux4_14-devel rust-userfaultfd-sys+linux5_7-devel 
rust-userfaultfd-sys-devel
Size:38.78 KiB

Package: rust-versionize-0.1.10-2.fc38
Summary: Version tolerant serialization/deserialization framework
RPMs:rust-versionize+default-devel rust-versionize-devel
Size:39.08 KiB

Package: rust-versionize_derive-0.1.5-1.fc38
Summary: Implements the Versionize derive proc macro
RPMs:rust-versionize_derive+default-devel rust-versionize_derive-devel
Size:30.80 KiB

Package: rust-vm-allocator-0.1.0-1.fc38
Summary: Helpers for allocating resources needed during the lifetime of a VM
RPMs:rust-vm-allocator+default-devel rust-vm-allocator-devel
Size:33.92 KiB

Package: rust-vm-superio-0.7.0-1.fc38
Summary: Emulation for legacy devices
RPMs:rust-vm-superio+default-devel rust-vm-superio-devel
Size:39.41 KiB


= DROPPED PACKAGES =
Package: python-certbot-dns-cloudxns-1.32.0-2.fc38
Summary: CloudXNS DNS Authenticator plugin for Certbot
RPMs:python-certbot-dns-cloudxns-doc python3-certbot-dns-cloudxns
Size:199.45 KiB


= UPGRADED PACKAGES =
Package:  anaconda-38.23.4-1.fc38
Old package:  anaconda-38.23.3-1.fc38
Summary:  Graphical system installer
RPMs: anaconda anaconda-core anaconda-dracut anaconda-gui 
anaconda-install-env-deps anaconda-install-img-deps anaconda-live anaconda-tui 
anaconda-webui anaconda-widgets anaconda-widgets-devel
Size: 19.13 MiB
Size change:  8.16 KiB
Changelog:
  * Tue Mar 28 2023 Packit  - 38.23.4-1
  - Add 'vga' to the list of preserved kernel arguments (#2176782) (awilliam)
  - Move ostreecontainer deps to install-img-deps (jkonecny)
  - Update translations from Weblate


Package:  candy-icon-theme-0-35.20230309git01255451.fc38
Old package:  candy-icon-theme-0-34.20230107gitc27f6da2.fc38
Summary:  Sweet gradient icon theme
RPMs: candy-icon-theme
Size: 1.05 MiB
Size change:  9.91 KiB
Changelog:
  * Wed Mar 22 2023 Artur Frenszek-Iwicki  - 
0-35.20230309git01255451
  - Update to latest git snapshot (2023-03-09)


Package:  cockpit-machines-286-1.fc38
Old package:  cockpit-machines-285-1.fc38
Summary:  Cockpit user interface for virtual machines
RPMs: cockpit-machines
Size: 1.02 MiB
Size change:  386 B
Changelog:
  * Wed Mar 22 2023 Packit  - 286-1
  - Create VM based on cloud image and start it later


Package:  cockpit-podman-65-1.fc38
Old package:  cockpit-podman-64-1.fc38
Summary:  Cockpit component for Podman containers
RPMs: cock

[rpms/perl-Sub-Identify] PR #1: Update license to SPDX format

2023-03-31 Thread Michal Josef Špaček


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

Merged pull-request:

``
Update license to SPDX format
``

https://src.fedoraproject.org/rpms/perl-Sub-Identify/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

[Test-Announce] Fedora 38 Branched 20230331.n.0 nightly compose nominated for testing

2023-03-31 Thread rawhide

Announcing the creation of a new nightly release validation test event
for Fedora 38 Branched 20230331.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/QA:Release_validation_test_plan

Notable package version changes:
anaconda - 20230326.n.1: anaconda-38.23.3-1.fc38.src, 20230331.n.0: 
anaconda-38.23.4-1.fc38.src
lorax - 20230326.n.1: lorax-38.8-1.fc38.src, 20230331.n.0: 
lorax-38.10-1.fc38.src

Test coverage information for the current release can be seen at:
https://openqa.fedoraproject.org/testcase_stats/38

You can see all results, find testing instructions and image download
locations, and enter results on the Summary page:

https://fedoraproject.org/wiki/Test_Results:Fedora_38_Branched_20230331.n.0_Summary

The individual test result pages are:

https://fedoraproject.org/wiki/Test_Results:Fedora_38_Branched_20230331.n.0_Installation
https://fedoraproject.org/wiki/Test_Results:Fedora_38_Branched_20230331.n.0_Base
https://fedoraproject.org/wiki/Test_Results:Fedora_38_Branched_20230331.n.0_Server
https://fedoraproject.org/wiki/Test_Results:Fedora_38_Branched_20230331.n.0_Cloud
https://fedoraproject.org/wiki/Test_Results:Fedora_38_Branched_20230331.n.0_Desktop
https://fedoraproject.org/wiki/Test_Results:Fedora_38_Branched_20230331.n.0_Security_Lab

Thank you for testing!
-- 
Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer
___
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

[EPEL-devel] Re: Creating an epelrelease dnf variable

2023-03-31 Thread Troy Dawson

On Fri, Mar 31, 2023 at 11:19 AM Miroslav Suchý  wrote:

> Dne 31. 03. 23 v 16:42 Troy Dawson napsal(a):
> > How to set it, I suggest triggers.  But that needs a bit more
> investigation and testing.
>
> May I suggest file trigger?
>
> https://rpm-software-management.github.io/rpm/manual/file_triggers.html
>
> Miroslav
>

I've learned something new today.
Yes, that is exactly what we need.

Troy
___
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

[rpms/perl-Sub-Identify] PR #1: Update license to SPDX format

2023-03-31 Thread Michal Josef Špaček


mspacek opened a new pull-request against the project: `perl-Sub-Identify` that 
you are following:
``
Update license to SPDX format
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Sub-Identify/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

[EPEL-devel] Re: Creating an epelrelease dnf variable

2023-03-31 Thread Miroslav Suchý


Dne 31. 03. 23 v 16:42 Troy Dawson napsal(a):

How to set it, I suggest triggers.  But that needs a bit more investigation and 
testing.


May I suggest file trigger?

https://rpm-software-management.github.io/rpm/manual/file_triggers.html

Miroslav
___
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: %patchN deprecated?

2023-03-31 Thread Miro Hrončok


On 31. 03. 23 13:58, Petr Menšík wrote:
Is there also documented and preferred way to apply just single patch when 
%autosetup -N -S git is used? I mean, if I want to have all patches applied 
git-like way, I know I can use -m or -M parameters to %autopatch. But 
%autopatch -m 1 -M 1 does not look nice.


I haven't found how to do that from comments in /usr/lib/rpm/macros. Can you 
help?


  %autopatch 1

https://github.com/rpm-software-management/rpm/blob/rpm-4.18.1-release/macros.in#L1236-L1239

> %autopatch
> Apply patches using %autosetup configured SCM.
> Typically used with no arguments to apply all patches in the order
> introduced in the spec, but alternatively can be used to apply indvidual
> patches in arbitrary order by passing them as arguments.

Also documented in 
https://rpm-software-management.github.io/rpm/manual/autosetup.html#autopatch


> Some examples:
> Apply patches with number >= 100
> %autopatch -m 100
>
> Apply patches with number <= 400
> %autopatch -M 400
>
> Apply patches 80 to 99, inclusive
> %autopatch -m 80 -M 99
>
> Apply patches 1, 4 and 6
> %autopatch 1 4 6

The individual patch numbers as arguments feature is available since RPM 4.17, 
see https://github.com/rpm-software-management/rpm/pull/1697



--
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

Different binaries size in Rawhide and F38

2023-03-31 Thread Vitaly Zaitsev via devel


Hello all.

It looks like strip is broken in Rawhide. Affected package - 
telegram-desktop.


Fedora 38 binary size: 83,563,448 bytes. Rawhide binary size: 98,968,520 
bytes.


Builds:
https://koji.rpmfusion.org/koji/buildinfo?buildID=25349 (F38)
https://koji.rpmfusion.org/koji/buildinfo?buildID=25350 (Rawhide)

Build from 2023-03-24 is not affected:
https://koji.rpmfusion.org/koji/buildinfo?buildID=25265

They are built from the same sources. Just a release bump due to Qt 
6.4.3 update.


--
Sincerely,
  Vitaly Zaitsev (vit...@easycoding.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

Re: DNF Sytem Upgrade requirements for an F37 → F38 upgrade

2023-03-31 Thread Alexander Ploumistos

On Fri, Mar 31, 2023 at 7:09 PM Zbigniew Jędrzejewski-Szmek
 wrote:
>
> I will submit systemd-tests-251.14-2.fc37 with the patch.
> I doubt that it solves the issue completely, but it shouldn't make
> it worse, so let's at least do this for now.

Thank you, I see it's still being built in koji. I will spin a VM with
the same configuration over the weekend and try the upgrade again.
___
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: DNF Sytem Upgrade requirements for an F37 → F38 upgrade

2023-03-31 Thread Zbigniew Jędrzejewski-Szmek

On Thu, Mar 30, 2023 at 02:37:16PM +0200, Alexander Ploumistos wrote:
> On Thu, Mar 30, 2023 at 2:33 PM Zbigniew Jędrzejewski-Szmek
>  wrote:
> >
> > On Thu, Mar 30, 2023 at 02:25:33PM +0200, Alexander Ploumistos wrote:
> > > On Thu, Mar 30, 2023 at 2:10 PM Zbigniew Jędrzejewski-Szmek
> > >  wrote:
> > > >
> > > > On Thu, Mar 30, 2023 at 12:08:03AM +0200, Fabio Valentini wrote:
> > > > > On Mon, Mar 6, 2023 at 4:09 AM Alexander Ploumistos
> > > > >  wrote:
> > > > > >
> > > > > > Hello,
> > > > > >
> > > > > > TL;DR:
> > > > > > DNF memory usage during upgrades from F37 to F38 on a couple of 
> > > > > > Fedora
> > > > > > Cloud images (with 2 GB of RAM each) led to oomd kicking in and
> > > > > > killing the upgrade process. It might be worth looking into before 
> > > > > > the
> > > > > > final (also beta?) release.
> > > >
> > > > Please try with systemd-253.2-1.fc38 / systemd-253.2-1.fc39.
> > >
> > >
> > > Hi Zbigniew, is F37 getting that version too or are you talking about
> > > a future F38 → F39 upgrade?
> >
> > That version — no. The patch for oomd config — yes (if it proves to be
> > beneficial in F38/rawhide).
> 
> Could you please bump this thread when it's done?

I will submit systemd-tests-251.14-2.fc37 with the patch.
I doubt that it solves the issue completely, but it shouldn't make
it worse, so let's at least do this for now.

Zbyszek
___
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: Fedpkg: Could not execute pre_push_check: Fail to upload files. Server returns status 403

2023-03-31 Thread Kevin Fenzi

On Fri, Mar 31, 2023 at 11:40:28AM -, Ondřej Mejzlík wrote:
> Hi,
> 
> For the past week I have been having issues pushing changes into my own fork 
> of a package.
> 
> Here is what I have done:
> (All of this used to work fine about a week ago, my steps are always the 
> same.)
> 
> Click the Fork button for example here: 
> https://src.fedoraproject.org/rpms/ppp/tree/
> fedpkg clone -a forks/omejzlik/rpms/ppp
> cd ppp
> git checkout -b fedora_testing
> Make a change.
> git add .
> git commit -a -m 'Some comment'
> git push --set-upstream origin fedora_testing
> Could not execute pre_push_check: Fail to upload files. Server returns status 
> 403
> error: failed to push some refs to 
> 'https://src.fedoraproject.org/forks/omejzlik/rpms/ppp.git'
> 
> The same error happens if I try to make a change in the main/rawhide branch 
> and even when using fedpkg push.
> The error used to be "Unauthorized access..." about 3 days ago, then changed 
> to 403.
> 
> I have created and set new tokens for both:
> [fedpkg.distgit]
> apibaseurl = https://src.fedoraproject.org
> token = XH...
> 
> [fedpkg.pagure]
> url = https://pagure.io/
> token = AK...
> 
> I have updated my SSH key in my FAS profile just in case it has anything to 
> do with this. 
> And I tried logging into my fedora kerberos account.
> Nothing helps.
> 
> I have several older packages forked from a week or earlier, pushing there 
> throws a different error:
> error: RPC failed; HTTP 502 curl 22 The requested URL returned error: 502
> send-pack: unexpected disconnect while reading sideband packet
> fatal: the remote end hung up unexpectedly
> 
> Any idea what the problem is?

I think this may be: https://pagure.io/fedpkg/issue/513

in which case you need a valid kerberos ticket if you are a packager, 
and to pass --no-verify if you aren't.

kevin


signature.asc
Description: PGP signature
___
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 2181971] perl-Glib-Object-Introspection-0.050 is available

2023-03-31 Thread bugzilla

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



--- Comment #20 from Sergio Basto  ---
(In reply to Petr Pisar from comment #19)
> Now I apply these changes to all Fedoras where an update with
> perl-Glib-Object-Introspection-0.050 has been submitted.

Many thanks , I hope I did the right thing on update on stable branches ...


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2181971
___
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: Issue trying to add co-maintainer to package

2023-03-31 Thread Kevin Fenzi

On Fri, Mar 31, 2023 at 08:49:40AM -0700, Jerry Snitselaar wrote:
> Hi,
> 
> I'm trying add the user kgold as a co-maintainer to the tss2 package.
> Peter added him to the packagers group the other week. Ken shows
> up in the packagers group when I look at his profile in FAS, and
> it shows for him as well. Ken has logged out and back in, but
> every time I've tried to add user kgold as an admin it comes back
> complaining that the user needs to be in the packagers group. Is there
> something I need to or can do to sync the info with
> src.fedoraproject.org so it sees that Ken is in the packagers group?

Yes, they need to logout and back into src.fedoraproject.org

group memberships there are refreshed on login. 

kevin


signature.asc
Description: PGP signature
___
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: %patchN deprecated?

2023-03-31 Thread Ron Olson

One thing to note is that the new format doesn’t work with EPEL 
releases; I had to revert to the %patchN style for them.


On 29 Mar 2023, at 3:53, Florian Festi wrote:


On 3/29/23 10:31, Michael J Gruber wrote:

Has `%patchN` been deprecated in favour of `%patch N`?


Yes, see %patch section on
https://rpm-software-management.github.io/rpm/manual/spec.html

I got a push by a proven packager to one of the packages which I 
maintain, commit subject and changelog entry "Fix deprecated patch 
rpm macro". It contains no explanation and no reference whatsoever. I 
didn't find any heads up notice, nor info in the packaging 
guidelines, but I didn't try too hard - because it's not my job.


I mean: One person is doing that push. Is it too much to ask to get 
at least the slightest bit of reference or communication before or 
into a push which probably affects hundreds of people? If not out of 
courtesy then out of mere common sense of efficiency?


On the technical side, I'd be interested why this is better (fewer 
macros?) and which releases can take it, and what are the 
recommendations for `PatchN:`-lines (with or without N), and why (or 
whether) the recommendation isn't to go for `%autosetup` or 
`%autopatch` - maybe all answered in the missing reference.


Those macros are an ugly hack and RPM upstream rather had them go 
away.


The deprecation suggests a one to one replacement. Ofc using the use 
of

%autosetup or %autopatch is encouraged but that kinda out of scope of
the deprecation.

Florian
___
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___
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

Issue trying to add co-maintainer to package

2023-03-31 Thread Jerry Snitselaar

Hi,

I'm trying add the user kgold as a co-maintainer to the tss2 package.
Peter added him to the packagers group the other week. Ken shows
up in the packagers group when I look at his profile in FAS, and
it shows for him as well. Ken has logged out and back in, but
every time I've tried to add user kgold as an admin it comes back
complaining that the user needs to be in the packagers group. Is there
something I need to or can do to sync the info with
src.fedoraproject.org so it sees that Ken is in the packagers group?

Thanks,
Jerry
___
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: Fedora Linux 38 blocker status summary

2023-03-31 Thread Ben Cotton

The current target is the early target date (18 April).

Action summary


Accepted blockers
-

1. kernel — anaconda failed to detect the fcoe target(only affects ixgbe) — NEW
ACTION: Maintainers to diagnose issue
NEEDINFO: lnie

2. plasma-workspace — Logging out of Plasma 5.27.3 on Wayland as the
second user on the system resulted in a black screen — NEW
ACTION: Maintainers to diagnose issue

3. shim — Live image made with BOOTX64.EFI from latest shim-x64-15.6-2
fails to boot on some boards — NEW
ACTION: kernel upstream to merge NX support

Proposed blockers
-

1. abrt — crash data are erased occasionally — VERIFIED
ACTION: (none)

2. Podman — shadow-utils installations fails with “cap_set_file
failed” in toolbox/podman on F38 host
ACTION: Maintainers to diagnose issue



Bug-by-bug detail
=

Accepted blockers
-

1. kernel — https://bugzilla.redhat.com/show_bug.cgi?id=2171350 — NEW
anaconda failed to detect the fcoe target(only affects ixgbe)

The installer does not detect attached FCOE storage using ixgbe. The
device ends up in "NO-CARRIER state DORNMANT".

2. plasma-workspace — https://bugzilla.redhat.com/show_bug.cgi?id=2179591 — NEW
Logging out of Plasma 5.27.3 on Wayland as the second user on the
system resulted in a black screen

In some cases, a race condition prevents a user on a system from
logging out successfully. This appears to be an SELinux issue filed as
RHBZ 2181010 for which FEDORA-2023-624eb88729 contains a verified fix.
It seems that a failure of dbus-:1.2-org.kde.LogoutPrompt@0.service
causes the sddm session to not be restarted.

3. shim — https://bugzilla.redhat.com/show_bug.cgi?id=2113005 — NEW
Live image made with BOOTX64.EFI from latest shim-x64-15.6-2 fails to
boot on some boards

UEFI LoadOptions that start with NUL cause boot failure. This is fixed
upstream in https://github.com/rhboot/shim/pull/505 but the SecureBoot
signing process requires NX support in the kernel, which is still
pending upstream.

Proposed blockers
-

1. abrt — https://bugzilla.redhat.com/show_bug.cgi?id=2177153 — VERIFIED
MaxCrashReportsSize claims to be 5000 MB but is 1000 MB

abrt is using a smaller size limit than the hard-coded default of 5000
MB. FEDORA-2023-eb09dd6406 containes a verified fix.

2. podman — https://bugzilla.redhat.com/show_bug.cgi?id=2183034 — NEW
packages with file capabilities fail to install in podman on F38 host

DNF update in a freshly-created f38 toolbox fails. The issue seems to
only happen on F38 hosts; shadow-utlis is updatable in an F36 and F37
container and host using podman 4.4.1. Suspected issue is a change in
Podman between 4.4.2 -> 4.4.3 or a different config file in F38. This
does not appear to be specific to the shadow-utils package.

-- 
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
___
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: F39 proposal: RPM 4.19 (System-Wide Change proposal)

2023-03-31 Thread Florian Festi

On 3/31/23 15:40, Stephen Gallagher wrote:
> On Thu, Mar 30, 2023 at 3:42 PM Ben Cotton  wrote:
>>
>> https://fedoraproject.org/wiki/Changes/RPM-4.19
> 
>> == Detailed Description ==
>> RPM 4.19 contains various improvements over previous versions. Many of
>> them are internal in nature such as moving from automake to cmake,
>> improvements to the test suite, stripping copies of system functions,
>> splitting translations into a separate project and more. There are
>> still several user facing changes:
>>
>> * New rpmsort(8) utility for sorting RPM versions
> Handy!
> 
>> * x86-64 architecture levels (v2-v4) as architectures
> Could you explain more what this means, exactly?

No! But here is the commit:

 
https://github.com/rpm-software-management/rpm/commit/cd46c1704ccd8eeb9b600729a0a1c8738b66b847

It looks like it adds x86_64_v2, x86_64_v3 and x86_64_v4. Something
about some x86_64 processors having additional capabilities.

>> * Support for %preuntrans and %postuntrans scriptlets
>> * Creating User and Groups from sysusers.d files including Provides
>> and Requires or Recommends
> I may have cried a little bit in joy here. This is huge!
> 
>> ([https://github.com/rpm-software-management/rpm/pull/2432 PR],
>> [https://github.com/rpm-software-management/rpm/discussions/2277
>> Discussion])

There now is proper documentation online. This just got merged, so it
wasn't available yet, when I submitted the change page.

https://rpm-software-management.github.io/rpm/manual/users_and_groups.html

Note that this will not be enabled fully at first. There needs to be
another Global Change to enable this fully. The actual update of RPM is
meant to be as little disruptive as possible. After the update the new
features can be enabled or put into Packaging Policy. But I guess most
here know that dance already.


>> * [https://rpm-software-management.github.io/rpm/manual/dynamic_specs.html
>> Dynamic Spec generation]
> 
> This could be a real winner for glibc, texlive and fedora-release.

Yes. But this was actually meant to be used for whole ecosystems like
Python to turn Manifest files into sub packages.

>> ** find_lang now being able to generate language sub packages
> 
> Could you provide more info on this? It's written almost like a
> side-note, but this could be a big deal.

Well this was done as a prove of concept for the Dynamic Spec feature.
See https://github.com/rpm-software-management/rpm/pull/2300 for the
change itself

For packagers all they need to know that there is a new
--generate-subpackages parameter for find-lang.sh that creates sub
packages according to the %_langpack_template macro.

This could probably use a bit more review from people more into i18n
than myself.


>> The 4.19 alpha release is expected in April and the final release is
>> expected in time for the Fedora 39 release cycle as usual.
> But I want it now... 
The time will come. The time will come.

Florian

___
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 2183554] New: perl-Math-BigInt-1.999838 is available

2023-03-31 Thread bugzilla

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

Bug ID: 2183554
   Summary: perl-Math-BigInt-1.999838 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Math-BigInt
  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, ppi...@redhat.com
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 1.999838
Upstream release that is considered latest: 1.999838
Current version/release in rawhide: 1.9998.37-3.fc38
URL: http://search.cpan.org/dist/Math-BigInt/

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/7954/


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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2183554
___
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

[EPEL-devel] Re: EPEL2RHEL - New Wording? - New Workflow?

2023-03-31 Thread Carl George

That sounds great, thanks.

On Thu, Mar 30, 2023, 8:28 AM Troy Dawson  wrote:

> It doesn't look like they've done their merge yet, so I'll see if I can
> get your change in.
> How does this sound?
>
> Subject:
> Notice:  will be automatically retired from EPEL  when
> RHEL . is released
>
> Comment:
>
> This issue is purely informational, you do not need to take any action.
> Thank you for your work maintaining  in EPEL .  Red Hat
> considers this package important enough to promote it to official RHEL.  It
> will be part of RHEL ..  Please do not update  in
> EPEL  so the RHEL version can have a higher version and release.
> When RHEL . is released, EPEL automation will remove
>  from EPEL  and close this bug.
>
>
> On Tue, Mar 28, 2023 at 9:14 AM Carl George  wrote:
>
>> I'm also late to the party with this feedback, but just in case it's
>> not too late to include, can we include something about not updating
>> the package further?  Beyond just "you do not need to take any
>> action", we should advise against making any changes at that point, as
>> often the RHEL package will be exactly one release higher than the
>> current EPEL package, and updating the EPEL package further (either
>> release or version) will screw up the upgrade path.
>>
>> On Mon, Mar 27, 2023 at 7:22 PM Troy Dawson  wrote:
>> >
>> > On Sat, Mar 25, 2023 at 12:51 PM Miro Hrončok 
>> wrote:
>> >>
>> >> On 20. 03. 23 12:20, Neal Gompa wrote:
>> >> >> I could think of other reasons as well. E.g. it's not important for
>> customers
>> >> >> but it's important for Red Hat. Or maybe it is a not-so-important
>> dependency of
>> >> >> something else.
>> >> >>
>> >> > Does Red Hat have any other motivation with RHEL other than a
>> customer
>> >> > needing the functionality? Those other reasons are generally driven
>> by
>> >> > someone needing it.
>> >>
>> >> See e.g. https://bugzilla.redhat.com/2175213
>> >
>> >
>> > I see your point.  It sometimes also happens when the EPEL package is a
>> dependency of the important package, the customers aren't actually asking
>> for the EPEL package.
>> > It looks like this change still hasn't been merged in so I'll see if I
>> can get a change in.  How about this?
>> >
>> > Subject:
>> > Notice:  will be automatically retired from EPEL  when
>> RHEL . is released
>> >
>> > Comment:
>> >
>> > This issue is purely informational, you do not need to take any
>> action.  Thank you for your work maintaining  in EPEL .
>> Red Hat considers this package important enough to promote it to official
>> RHEL.  It will be part of RHEL ..  When that is released,
>> EPEL automation will remove  from EPEL  and close this bug.
>> >
>> > ___
>> > 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
>>
>>
>>
>> --
>> Carl George
>> ___
>> 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 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 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

[Bug 2181971] perl-Glib-Object-Introspection-0.050 is available

2023-03-31 Thread bugzilla

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



--- Comment #19 from Petr Pisar  ---
I finished changing Rawhide. Here
 you can see a
standalone update for perl-Glib-Object-Introspection which under
fedora-ci.koji-build.tier0.functional Automated tests shows passed tests for
both perl-Glib-Object-Introspection and perl-Gtk3 package.

Now I apply these changes to all Fedoras where an update with
perl-Glib-Object-Introspection-0.050 has been submitted.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2181971
___
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

[EPEL-devel] Creating an epelrelease dnf variable

2023-03-31 Thread Troy Dawson

This is mainly for EPEL10 planning, but others might find it useful, so I'm
sending it to the email vs the epel10 discussion on discourse.

I was talking with Carl about creating a dnf variable for the epel 10
repos.  He had been talking about using $releasever and $releaseminor.  But
we also talked about creating our own epel variable.
This is about creating our own epel variable.  I'm calling it epelrelease
but that it up for debate.

There is an often overlooked file called /etc/os-release
It's full of lots of good stuff, including a variable called "VERSION_ID"
In every Red Hat compatible release (Fedora, Stream, RHEL, Alma, Rocky)
this should give us what we need/want.
Fedora 39
Stream 8 / 9
RHEL 8.7 / 9.1
Alma 8.7 / 9.1
Rocky 8.7 / 9.1

The format of /etc/os-release makes it very easy to use.  The following
would give us a dnf variable called epelrelease

source /etc/os-release ; echo $VERSION_ID >> /etc/dnf/vars/epelrelease

We could then use epelrelease in our dnf configs.

How to set it, I suggest triggers.  But that needs a bit more investigation
and testing.

Troy
___
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

[rpms/perl-Package-Generator] PR #1: Update license to SPDX format

2023-03-31 Thread Michal Josef Špaček


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

Merged pull-request:

``
Update license to SPDX format
``

https://src.fedoraproject.org/rpms/perl-Package-Generator/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: Specfile - Upgrade - Check if the old and the new package versions are the same

2023-03-31 Thread Simon Pichugin

On Fri, Mar 31, 2023 at 4:00 AM Vít Ondruch  wrote:

> Out of curiosity, are you considering also package downgrades?
>
It's not described in OpenLDAP Upstream docs, so I was not trying to cover
that, but...
It's a good idea to add the check and do the same safety precautions I do
with the upgrade. Thanks!

On Fri, Mar 31, 2023 at 5:41 AM Miroslav Suchý  wrote:

> Dne 30. 03. 23 v 20:38 Simon Pichugin napsal(a):
> > When the server package upgrades to the next major version, there are
> upgrade instructions that need to be performed
> > by the administrator.
> > And what's most important, the server should not start automatically
> without explicit agreement from the administrator.
>
> Check postgresql.spec - this package has this case nicely resolved. You
> may get in touch with one of the maintainer as
> it may be hard to comprehend just from the code (and I do not know the
> details neither).
>

Yep, I was looking into that previously, and it's VERY nice. It'll be great
to implement something like that
but considering that the community never asked for this... It probably will
be overkill, especially as more and more people
move away from OpenLDAP as it was removed from RHEL since RHEL 8 (and we
provide reasonably limited support here on Fedora,
even though I'm doing my best to keep it updated and supported for the
community).

Thank you for the nice suggestion though!


>
> Miroslav
> ___
> 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
>
___
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: F39 proposal: RPM 4.19 (System-Wide Change proposal)

2023-03-31 Thread Miroslav Suchý


Dne 31. 03. 23 v 15:40 Stephen Gallagher napsal(a):

* Creating User and Groups from sysusers.d files including Provides
and Requires or Recommends

I may have cried a little bit in joy here. This is huge!


Yes! Huge thanks for this.

Miroslav
___
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: F39 proposal: RPM 4.19 (System-Wide Change proposal)

2023-03-31 Thread Stephen Gallagher

On Thu, Mar 30, 2023 at 3:42 PM Ben Cotton  wrote:
>
> https://fedoraproject.org/wiki/Changes/RPM-4.19

> == Detailed Description ==
> RPM 4.19 contains various improvements over previous versions. Many of
> them are internal in nature such as moving from automake to cmake,
> improvements to the test suite, stripping copies of system functions,
> splitting translations into a separate project and more. There are
> still several user facing changes:
>
> * New rpmsort(8) utility for sorting RPM versions
Handy!

> * x86-64 architecture levels (v2-v4) as architectures
Could you explain more what this means, exactly?

> * Support for %preuntrans and %postuntrans scriptlets
> * Creating User and Groups from sysusers.d files including Provides
> and Requires or Recommends
I may have cried a little bit in joy here. This is huge!

> ([https://github.com/rpm-software-management/rpm/pull/2432 PR],
> [https://github.com/rpm-software-management/rpm/discussions/2277
> Discussion])
> * [https://rpm-software-management.github.io/rpm/manual/dynamic_specs.html
> Dynamic Spec generation]

This could be a real winner for glibc, texlive and fedora-release.

> ** find_lang now being able to generate language sub packages

Could you provide more info on this? It's written almost like a
side-note, but this could be a big deal.

>
> The 4.19 alpha release is expected in April and the final release is
> expected in time for the Fedora 39 release cycle as usual.
But I want it now... 
___
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

Heads-up: fast_float 4.0.0 coming to Rawhide

2023-03-31 Thread Ben Beasley

In one week (2023-03-07), or slightly later, I plant to update 
fast_float to 4.0.0[1] in Rawhide. This new major release contains one 
small but technically incompatible change: errc::result_out_of_range is 
now set on over/underflow. A PR[2] is ready, and I have already verified 
(by local mock builds) that dependent packages c4core and libscn remain 
compatible.


[1] https://github.com/fastfloat/fast_float/releases/tag/v4.0.0

[2] https://src.fedoraproject.org/rpms/fast_float/pull-request/4
___
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: Specfile - Upgrade - Check if the old and the new package versions are the same

2023-03-31 Thread Miroslav Suchý


Dne 30. 03. 23 v 20:38 Simon Pichugin napsal(a):
When the server package upgrades to the next major version, there are upgrade instructions that need to be performed 
by the administrator.

And what's most important, the server should not start automatically without 
explicit agreement from the administrator.


Check postgresql.spec - this package has this case nicely resolved. You may get in touch with one of the maintainer as 
it may be hard to comprehend just from the code (and I do not know the details neither).


Miroslav
___
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 2183513] New: Upgrade perl-Data-Munge to 0.10

2023-03-31 Thread bugzilla

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

Bug ID: 2183513
   Summary: Upgrade perl-Data-Munge to 0.10
   Product: Fedora
   Version: rawhide
   URL: https://metacpan.org/release/Data-Munge
Status: NEW
 Component: perl-Data-Munge
  Assignee: emman...@seyman.fr
  Reporter: jples...@redhat.com
QA Contact: extras...@fedoraproject.org
CC: emman...@seyman.fr, perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Latest Fedora delivers 0.097 version. Upstream released 0.10. 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=2183513
___
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-Package-Generator] PR #1: Update license to SPDX format

2023-03-31 Thread Michal Josef Špaček


mspacek opened a new pull-request against the project: `perl-Package-Generator` 
that you are following:
``
Update license to SPDX format
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Package-Generator/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 2158384] Upgrade perl-Convert-Color to 0.16

2023-03-31 Thread bugzilla

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

Jitka Plesnikova  changed:

   What|Removed |Added

Version|38  |rawhide
Summary|Upgrade perl-Convert-Color  |Upgrade perl-Convert-Color
   |to 0.14 |to 0.16



--- Comment #2 from Jitka Plesnikova  ---
Latest Fedora delivers 0.13 version. Upstream released 0.16. 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=2158384
___
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

Fedora rawhide compose report: 20230331.n.0 changes

2023-03-31 Thread Fedora Rawhide Report

OLD: Fedora-Rawhide-20230330.n.0
NEW: Fedora-Rawhide-20230331.n.0

= SUMMARY =
Added images:2
Dropped images:  1
Added packages:  5
Dropped packages:9
Upgraded packages:   126
Downgraded packages: 0

Size of added packages:  158.59 MiB
Size of dropped packages:10.55 MiB
Size of upgraded packages:   7.88 GiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   428.31 MiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =
Image: Silverblue dvd-ostree ppc64le
Path: 
Silverblue/ppc64le/iso/Fedora-Silverblue-ostree-ppc64le-Rawhide-20230331.n.0.iso
Image: Xfce raw-xz aarch64
Path: Spins/aarch64/images/Fedora-Xfce-Rawhide-20230331.n.0.aarch64.raw.xz

= DROPPED IMAGES =
Image: Kinoite dvd-ostree ppc64le
Path: Kinoite/ppc64le/iso/Fedora-Kinoite-ostree-ppc64le-Rawhide-20230330.n.0.iso

= ADDED PACKAGES =
Package: delve-1.20.1-1.fc39
Summary: A debugger for the Go programming language
RPMs:delve
Size:8.15 MiB

Package: fim-0.6-1.fc39
Summary: Lightweight universal image viewer
RPMs:fim
Size:2.26 MiB

Package: google-noto-sans-cjk-subset-fonts-1:2.004-2.fc39
Summary: Google Noto Sans CJK Subset Fonts
RPMs:google-noto-sans-hk-fonts google-noto-sans-jp-fonts 
google-noto-sans-kr-fonts google-noto-sans-sc-fonts google-noto-sans-tc-fonts
Size:145.22 MiB

Package: kommit-1.0.1-1.fc39
Summary: Git gui client for KDE
RPMs:kommit
Size:2.91 MiB

Package: rust-miniz_oxide0.5-0.5.4-1.fc39
Summary: DEFLATE compression and decompression library rewritten in Rust based 
on miniz
RPMs:rust-miniz_oxide0.5+default-devel rust-miniz_oxide0.5-devel
Size:62.26 KiB


= DROPPED PACKAGES =
Package: emelfm2-0.9.1-20.fc38
Summary: File manager that implements the popular two-pane design
RPMs:emelfm2
Size:3.50 MiB

Package: fbpanel-7.0-15.fc38
Summary: A lightweight X11 desktop panel
RPMs:fbpanel fbpanel-doc
Size:4.29 MiB

Package: gtrayicon-1.1-26.fc38
Summary: Generic tray icon for GNOME
RPMs:gtrayicon
Size:137.26 KiB

Package: gxmessage-2.20.0-24.fc38
Summary: GTK2 based xmessage clone
RPMs:gxmessage
Size:285.70 KiB

Package: lilyterm-0.9.9.2-22.fc38
Summary: Light and easy to use X Terminal Emulator
RPMs:lilyterm
Size:805.98 KiB

Package: preferences-menus-1-23.fc38
Summary: Categorized submenus for the Preferences menu
RPMs:preferences-menus
Size:7.92 KiB

Package: python3-pyPEG2-2.15.2-24.fc38
Summary: A PEG Parser-Interpreter in Python
RPMs:python3-pyPEG2
Size:83.64 KiB

Package: regexxer-0.9-33.fc38
Summary: A nifty GUI search/replace tool
RPMs:regexxer
Size:968.48 KiB

Package: taggle-1.0-26.fc38
Summary: An online french word game
RPMs:taggle taggle-server
Size:543.86 KiB


= UPGRADED PACKAGES =
Package:  abrt-2.16.1-1.fc39
Old package:  abrt-2.16.0-2.fc38
Summary:  Automatic bug detection and reporting tool
RPMs: abrt abrt-addon-ccpp abrt-addon-kerneloops abrt-addon-pstoreoops 
abrt-addon-upload-watch abrt-addon-vmcore abrt-addon-xorg abrt-atomic abrt-cli 
abrt-console-notification abrt-dbus abrt-desktop abrt-devel abrt-gui 
abrt-gui-devel abrt-gui-libs abrt-libs abrt-plugin-bodhi abrt-plugin-machine-id 
abrt-tui python3-abrt python3-abrt-addon python3-abrt-container-addon 
python3-abrt-doc
Size: 5.05 MiB
Size change:  2.94 KiB
Changelog:
  * Thu Mar 30 2023 Michal Srb  - 2.16.1-1
  - Update to upstream release 2.16.1


Package:  abseil-cpp-20230125.2-1.fc39
Old package:  abseil-cpp-20230125.1-1.fc39
Summary:  C++ Common Libraries
RPMs: abseil-cpp abseil-cpp-devel
Size: 7.36 MiB
Size change:  72.86 KiB
Changelog:
  * Thu Mar 30 2023 Benjamin A. Beasley  - 20230125.2-1
  - Update to 20230125.2 (close RHBZ#2182229)


Package:  annobin-12.01-1.fc39
Old package:  annobin-12.00-1.fc39
Summary:  Annotate and examine compiled binary files
RPMs: annobin-annocheck annobin-docs annobin-libannocheck 
annobin-plugin-clang annobin-plugin-gcc annobin-plugin-llvm
Size: 5.02 MiB
Size change:  7.79 KiB
Changelog:
  * Thu Mar 30 2023 Nick Clifton   - 12.01-1
  - gcc plugin: Keep ELF notes at protocol version 3.


Package:  ansifilter-2.19-1.fc39
Old package:  ansifilter-2.18-5.fc38
Summary:  ANSI terminal escape code converter
RPMs: ansifilter ansifilter-gui
Size: 1.02 MiB
Size change:  7.82 KiB
Changelog:
  * Fri Mar 31 2023 Filipe Rosset  - 2.19-1
  - Update to 2.19 fixes rhbz#2178834


Package:  awscli-1.27.103-1.fc39
Old package:  awscli-1.27.101-1.fc39
Summary:  Universal Command Line Environment for AWS
RPMs: awscli
Size: 3.29 MiB
Size change:  -223 B
Changelog:
  * Thu Mar 30 2023 Gwyn Ciesla  - 1.27.102-1
  - 1.27.102

  * Thu Mar 30 2023 Gwyn Ciesla  - 1.27.103-1
  - 1.27.103


Package:  azote-1.11.0-1.fc39
Old package:  azote-1.10.1-1.fc39
Summary:  Wallpaper and color manager for Sway, i3 and some other

i-nex core dumped on fc38

2023-03-31 Thread Martin Gansser

Hi,

when i run i-nex on fedora 38 i get a core dump [1] see debugging-i-nex.txt
I have compiled i-nex [2] with a new patch, since a newer libcpuid version is 
used on fedora 38.
I cannot expect any help from upstream, as development has been discontinued in 
the meantime.

[1] https://martinkg.fedorapeople.org/ErrorReports/debugging-i-nex.txt
[2] https://martinkg.fedorapeople.org/ErrorReports/i-nex-7.6.1-14.fc38.src.rpm

any help is appreciated

Regards
Martin
___
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-Scope-Guard] PR #1: Update license to SPDX format

2023-03-31 Thread Michal Josef Špaček


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

Merged pull-request:

``
Update license to SPDX format
``

https://src.fedoraproject.org/rpms/perl-Scope-Guard/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: %patchN deprecated?

2023-03-31 Thread Petr Menšík

I would suggest creating at least self-contained change on Fedora to 
describe what has changed and why. Those syntax might be a little weird, 
but were used quite often. It would be nice to have some place to read 
about it. Because frankly it just started warning when used, but I do 
not remember it announced. When I searched approved changes mentioning 
this, there were none. Wiki page might provide links to external sources 
and could be used by other to reference why they are changing %patchX 
format.


Is there also documented and preferred way to apply just single patch 
when %autosetup -N -S git is used? I mean, if I want to have all patches 
applied git-like way, I know I can use -m or -M parameters to 
%autopatch. But %autopatch -m 1 -M 1 does not look nice.


I haven't found how to do that from comments in /usr/lib/rpm/macros. Can 
you help?


On 3/29/23 17:58, Todd Zullinger wrote:

Florian Festi wrote:

On 3/29/23 10:31, Michael J Gruber wrote:

Has `%patchN` been deprecated in favour of `%patch N`?

Yes, see %patch section on
https://rpm-software-management.github.io/rpm/manual/spec.html

Quoting that:

 %patch is used to apply patches on top of the just unpacked
 pristine sources. Historically it supported multiple strange
 syntaxes and buggy behaviors, which are no longer
 maintained. To apply patch number 1, the following are
 recognized:

 %patch 1 (since rpm >= 4.18)
 %patch -P1 (all rpm versions)
 %patch1 (deprecated, do not use)

 For new packages, the positional argument form 1) is
 preferred. For maximal compatibility use 2). Both forms can
 be used to apply several patches at once, in the order they
 appear on the line. The third form where the number is a
 part of the directive is deprecated and should not be used
 anymore.

Which gets to Michael's question "which releases can take
it?"

Changing `%patch1` to `%patch 1` limits support to Fedora 37
and above, unless this has been backported to older Fedora
and/or RHEL rpm?  Until it's supported by all current Fedora
and RHEL releases, it's not a change I'd want in the
packages I maintain.  I'd have to go with `%patch -P1`
(anywhere that %autosetup / %autopatch wasn't used).


___
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


--
Petr Menšík
Software Engineer, RHEL
Red Hat, https://www.redhat.com/
PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB
___
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 2181971] perl-Glib-Object-Introspection-0.050 is available

2023-03-31 Thread bugzilla

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

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|CLOSED
 Resolution|--- |ERRATA
Last Closed||2023-03-31 11:52:15



--- Comment #18 from Fedora Update System  ---
FEDORA-2023-9cec1a7508 has been pushed to the Fedora 39 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=2181971
___
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 2181971] perl-Glib-Object-Introspection-0.050 is available

2023-03-31 Thread bugzilla

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



--- Comment #17 from Fedora Update System  ---
FEDORA-2023-9cec1a7508 has been submitted as an update to Fedora 39.
https://bodhi.fedoraproject.org/updates/FEDORA-2023-9cec1a7508


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2181971
___
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 2181971] perl-Glib-Object-Introspection-0.050 is available

2023-03-31 Thread bugzilla

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

Petr Pisar  changed:

   What|Removed |Added

   Fixed In Version||perl-Glib-Object-Introspect
   ||ion-0.050-2.fc39
 Status|ASSIGNED|MODIFIED




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2181971
___
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

Fedpkg: Could not execute pre_push_check: Fail to upload files. Server returns status 403

2023-03-31 Thread Ondřej Mejzlík

Hi,

For the past week I have been having issues pushing changes into my own fork of 
a package.

Here is what I have done:
(All of this used to work fine about a week ago, my steps are always the same.)

Click the Fork button for example here: 
https://src.fedoraproject.org/rpms/ppp/tree/
fedpkg clone -a forks/omejzlik/rpms/ppp
cd ppp
git checkout -b fedora_testing
Make a change.
git add .
git commit -a -m 'Some comment'
git push --set-upstream origin fedora_testing
Could not execute pre_push_check: Fail to upload files. Server returns status 
403
error: failed to push some refs to 
'https://src.fedoraproject.org/forks/omejzlik/rpms/ppp.git'

The same error happens if I try to make a change in the main/rawhide branch and 
even when using fedpkg push.
The error used to be "Unauthorized access..." about 3 days ago, then changed to 
403.

I have created and set new tokens for both:
[fedpkg.distgit]
apibaseurl = https://src.fedoraproject.org
token = XH...

[fedpkg.pagure]
url = https://pagure.io/
token = AK...

I have updated my SSH key in my FAS profile just in case it has anything to do 
with this. 
And I tried logging into my fedora kerberos account.
Nothing helps.

I have several older packages forked from a week or earlier, pushing there 
throws a different error:
error: RPC failed; HTTP 502 curl 22 The requested URL returned error: 502
send-pack: unexpected disconnect while reading sideband packet
fatal: the remote end hung up unexpectedly

Any idea what the problem is?
Thanks.
___
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-Scope-Guard] PR #1: Update license to SPDX format

2023-03-31 Thread Michal Josef Špaček


mspacek opened a new pull-request against the project: `perl-Scope-Guard` that 
you are following:
``
Update license to SPDX format
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Scope-Guard/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: Specfile - Upgrade - Check if the old and the new package versions are the same

2023-03-31 Thread Vít Ondruch


Out of curiosity, are you considering also package downgrades?


Vít


Dne 30. 03. 23 v 20:38 Simon Pichugin napsal(a):

Hi folks,
Thank you for the answers!

On Thu, Mar 30, 2023 at 1:16 AM Vít Ondruch  wrote:

I wonder what the "do something" is, because comparing versions is
almost always the wrong choice IMHO.

When the server package upgrades to the next major version, there are 
upgrade instructions that need to be performed by the administrator.
And what's most important, the server should not start automatically 
without explicit agreement from the administrator.


But we don't need to do that when the package upgrade happens with 
just a release number bump (2.6.4-1 -> 2.6.4-2).

That's what I'm trying to solve with the RPM tools.

BTW there are "vercmp(v1, v2)" and "ver(evr), ver(e, v, r)" Lua
functions for EVR comparisons.

I'll check it out. Thanks!


On Thu, Mar 30, 2023 at 3:14 AM Miroslav Suchý  wrote:

I second Vít. Comparing version is wrong approach. IMO.

1) it is definitelly bad idea if you call `rpm -qa` because rpm is
not reentrant. So calling rpm from scriptlet may work, but one day
it will do something really bad.

2) you did not take in consideration epoch. So it may cause you a
problem few years in future.

3) such decision should be always based on capabilities. Does such
config exists? Is some variable in config set? Or not set?

In your case, I would check for existence of
/etc/openldap/migrated_from_version_1 file. And if it does not
exist then do the migration and when done, touch this file. And
you should own this file as %ghost.

It looks like a great fit for my situation! The only downside I can 
see it's if the administrator will remove the file.
And then, when he needs to upgrade, we won't be able to tell if it's a 
major or minor upgrade. But it's really minor and can be worked out, I 
think.

Thank you! I'll look into that option, and we'll see how it goes. :)

Regards,
Simon

Miroslav

___
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


___
devel mailing list --devel@lists.fedoraproject.org
To unsubscribe send an email todevel-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


OpenPGP_signature
Description: OpenPGP digital signature
___
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-Test-LeakTrace] PR #1: Update license to SPDX format

2023-03-31 Thread Michal Josef Špaček


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

Merged pull-request:

``
Update license to SPDX format
``

https://src.fedoraproject.org/rpms/perl-Test-LeakTrace/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-Test-LeakTrace] PR #1: Update license to SPDX format

2023-03-31 Thread Michal Josef Špaček


mspacek opened a new pull-request against the project: `perl-Test-LeakTrace` 
that you are following:
``
Update license to SPDX format
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Test-LeakTrace/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: RPM 4.19: Dynamic subpackages with Python extras

2023-03-31 Thread Miro Hrončok


On 30. 03. 23 23:55, Miro Hrončok wrote:

Hello Python packagers.

RPM 4.19 introduces this feature:

https://rpm-software-management.github.io/rpm/manual/dynamic_specs.html

I decided to write this email to gather my thoughts. I believe that with this, 
we can turn manual Python extras subpackages like this:


   %package -n python3-...
   Summary:    %{summary}

   %description -n python3-... %_description

   %pyproject_extras_subpkg -n python3-xxx extra1 extra2

(See https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/#Extras 
for what that means.)


Into something like this:

   %package -n python3-...
   Summary:    %{summary}

   %description -n python3-... %_description
   ...

   %install
   %pyproject_install
   ...
   %pyproject_generate_extras_subpkgs -n python3-xxx


The %pyproject_generate_extras_subpkgs macro would parse the installed 
.dist-info directory to find out what extras are available and generate 
subpackages for all of them.


One challenge: When an extra is removed upstream, the packager might not notice 
that it needs to be provided/obsoleted/etc.


--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-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/python-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

55 matches

Mail list logo