package icu: be more verbose about the tools and utilities in description
Nimi : icu Versio : 67.1 Julkaisu : 9.el8 Arkkiteht. : x86_64 Koko : 626 k Lähdekoodi : icu-67.1-9.el8.src.rpm Asennuslähde : @System Tiivistelmä : International Components for Unicode URL : http://site.icu-project.org/ Lisenssi : MIT and UCD and Public Domain Kuvaus : Tools and utilities for developing with icu. pkg provides at least in x86_64: icu-config icu-config-64 icuinfo icupkg ___ 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
CentOS8/RHEL8/Fedora: dependency control: make gcc-c++ provide g++,required for pulseaudio.
Kind regards, Ilari Jääskeläinen. ___ 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 2178063] Add perl-MooseX-StrictConstructor to EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2178063 Fedora Update System changed: What|Removed |Added Resolution|--- |ERRATA Status|ON_QA |CLOSED Last Closed||2023-03-25 03:05:52 --- Comment #4 from Fedora Update System --- FEDORA-EPEL-2023-fa06873253 has been pushed to the Fedora EPEL 9 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=2178063 ___ 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 2177873] Please provide perl-Net-Amazon-S3 for EPEL9
https://bugzilla.redhat.com/show_bug.cgi?id=2177873 Bug 2177873 depends on bug 2178067, which changed state. Bug 2178067 Summary: Add perl-VM-EC2-Security-CredentialCache to EPEL 9 https://bugzilla.redhat.com/show_bug.cgi?id=2178067 What|Removed |Added Status|ON_QA |CLOSED Resolution|--- |ERRATA -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2177873 ___ 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 2178067] Add perl-VM-EC2-Security-CredentialCache to EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2178067 Fedora Update System changed: What|Removed |Added Resolution|--- |ERRATA Status|ON_QA |CLOSED Last Closed||2023-03-25 03:05:49 --- Comment #4 from Fedora Update System --- FEDORA-EPEL-2023-40c1e35c83 has been pushed to the Fedora EPEL 9 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=2178067 ___ 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 2178067] Add perl-VM-EC2-Security-CredentialCache to EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2178067 Bug 2178067 depends on bug 2178068, which changed state. Bug 2178068 Summary: Add perl-VM-EC2 to EPEL 9 https://bugzilla.redhat.com/show_bug.cgi?id=2178068 What|Removed |Added Status|ON_QA |CLOSED Resolution|--- |ERRATA -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2178067 ___ 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 2177873] Please provide perl-Net-Amazon-S3 for EPEL9
https://bugzilla.redhat.com/show_bug.cgi?id=2177873 Bug 2177873 depends on bug 2178063, which changed state. Bug 2178063 Summary: Add perl-MooseX-StrictConstructor to EPEL 9 https://bugzilla.redhat.com/show_bug.cgi?id=2178063 What|Removed |Added Status|ON_QA |CLOSED Resolution|--- |ERRATA -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2177873 ___ 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 2178068] Add perl-VM-EC2 to EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2178068 Fedora Update System changed: What|Removed |Added Status|ON_QA |CLOSED Resolution|--- |ERRATA Last Closed||2023-03-25 03:05:47 --- Comment #4 from Fedora Update System --- FEDORA-EPEL-2023-26dedf30bf has been pushed to the Fedora EPEL 9 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=2178068 ___ 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 2179198] perl-Business-ISBN-Data-20230316.001 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2179198 --- Comment #5 from Fedora Update System --- FEDORA-2023-b80bcf5b8f has been pushed to the Fedora 38 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-b80bcf5b8f 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=2179198 ___ 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 2180986] perl-Business-ISBN-Data-20230322.001 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2180986 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #2 from Fedora Update System --- FEDORA-2023-b80bcf5b8f has been pushed to the Fedora 38 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-b80bcf5b8f 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=2180986 ___ 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 2181237] perl-Business-ISBN-3.007-5.fc39 FTBFS: t/errors.t: Failed test 'ISBN 9786316294241 error text mentions 'group''
https://bugzilla.redhat.com/show_bug.cgi?id=2181237 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #3 from Fedora Update System --- FEDORA-2023-5b3f14cd81 has been pushed to the Fedora 38 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-5b3f14cd81 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=2181237 ___ 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 2181377] perl-Business-ISBN-3.008 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2181377 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #2 from Fedora Update System --- FEDORA-2023-5b3f14cd81 has been pushed to the Fedora 38 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-5b3f14cd81 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=2181377 ___ 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 2177939] perl-Perl4-CoreLibs-0.005 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2177939 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-Perl4-CoreLibs-0.005-1 |perl-Perl4-CoreLibs-0.005-1 |.fc36 |.fc36 |perl-Perl4-CoreLibs-0.005-1 |perl-Perl4-CoreLibs-0.005-1 |.fc37 |.fc37 ||perl-Perl4-CoreLibs-0.005-1 ||.fc38 --- Comment #11 from Fedora Update System --- FEDORA-2023-da8de27a58 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=2177939 ___ 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: Fedora Linux 38 blocker status summary
On Fri, Mar 24, 2023 at 02:25:46PM -0400, Ben Cotton wrote: > 3. kernel — https://bugzilla.redhat.com/show_bug.cgi?id=2176782 — POST > The kernel sometimes does not initialize SimpleDRM when booting in > basic graphics mode on BIOS, causing SDDM to fail > > In BIOS mode only, sddm results in a blank screen when using basic > graphics mode. This is the result of a SimpleDRM device not being > created. gdm uses a fallback to x11 in this scenario, so it works. > Setting `vga=791` in grub appears to work. Pending lorax PR adds this > for basic graphics mode on BIOS: > https://github.com/weldr/lorax/pull/1317 It would be helpful if people with hardware could make sure this generally works for them, so if you have found that you need to use basic graphics in the past, try booting with vga=791 just to be sure it doesn't cause problems. I'll likely do a new build with that on Monday. Brian -- Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart ___ 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: Changes of defaults in createrepo_c-1.0.0 (System-Wide Change proposal)
> - When adding groups.xml to repodata createrepo_c currently adds two > variants to repomd.xml. The specified file as is, uncompressed, with > the type "group" and also a compressed variant with type "group_XX", > where XX is compression suffix. This is atypical and unexpected. We > propose to include just one variant of groups.xml using specified > compression and repomd.xml type "group". This is not compatible with > yum in RHEL 7. If required users will still be able to create > repositories with the old layout using modifyrepo_c. > Further information: https://bugzilla.redhat.com/show_bug.cgi?id=2056318 If we're planning to drop by-default compatibility with EL7 anyway and bump to 1.0, we could go a little bit further. * "createrepo_c" doesn't need to support sqlite metadata generation at all, so long as the repository producer can run "sqliterepo_c". If I recall correctly, yum on EL7 doesn't actually need the sqlite metadata to be generated in any case, it can produce that metadata itself so long as it has the XML. Making it available only avoids a local processing step. But if "modifyrepo_c" will be necessary to work with most EL7 repos, then making "sqliterepo_c" necessary for a minor optimization isn't a big leap. * createrepo_c currently has two different switches for compression types, "compress-type" and "general-compress-type", where the latter applies to everything and the former only applies to files that are *not* "primary", "filelists", and "other". there should be one compression type option and it should be applied uniformly to all metadata produced by the "createrepo_c" tool. Yum would have choked on this because of the special handling around "comps", but I believe it should no longer be a concern? ___ 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: GitHub.com SSH host key changed
Public service announcement for anyone who uses GitHub: they have changed their SSH host key as a result of an inadvertent disclosure. See their blog for more information: https://github.blog/2023-03-23-we-updated-our-rsa-ssh-host-key/ -- 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: Fedora Linux 38 blocker status summary
The current target is the early target date (18 April). Action summary Accepted blockers - 1. crypto-policies — Insecure installed RPMs (like Google Chrome) prevent system updates in F38, can't be removed — ASSIGNED ACTION: Maintainers to propose solution for this case 2. kernel — anaconda failed to detect the fcoe target(only affects ixgbe) — NEW ACTION: Maintainers to diagnose issue 3. kernel — The kernel sometimes does not initialize SimpleDRM when booting in basic graphics mode on BIOS, causing SDDM to fail — POST ACTION: lorax maintainers to review and merge PR 1317 4. openssh — Update hostkey migration to support OSTree systems and dynamically detect hostkey location — POST ACTION: fedora-release and openssh maintainers to merge pending pull requests NEEDIFNO: dbelyavs 5. sddm — Virtual keyboard (on-screen) not working at sddm-wayland-plasma — NEW ACTION: Maintainers to diagnose issue or revert to using X11 NEEDINFO: ngompa13 6. 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 — NEW ACTION: Maintainer to diagnose issue 2. accountservice — GDM takes "long" before allowing mouse moves and showing the user list. — MODIFIED ACTION: QA to verfiy FEDORA-2023-a5af7d5db0 3. gnome-shell — gnome-shell crashes and sysops happens when users logout — NEW ACTION: Upstream to complete work on MR 2722 4. gnome-software — Incorrect priority order of app sources — MODIFIED ACTION: QA to verify FEDORA-2023-49b5dec107 5. kwin — Logging out of Plasma 5.27.3 on Wayland as the second user on the system resulted in a black screen — NEW ACTION: selinux-policy maintainers to create an update that contains upstream PR 1628 Bug-by-bug detail = Accepted blockers - 1. crypto-policies — https://bugzilla.redhat.com/show_bug.cgi?id=2170878 — ASSIGNED Insecure installed RPMs (like Google Chrome) prevent system updates in F38, can't be removed A fix to let RPM use a separate crytpo policy has not covered all cases. Certain AnyDesk RPMs were apparently signed outside the window when the certificate was valid. 2. 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". 3. kernel — https://bugzilla.redhat.com/show_bug.cgi?id=2176782 — POST The kernel sometimes does not initialize SimpleDRM when booting in basic graphics mode on BIOS, causing SDDM to fail In BIOS mode only, sddm results in a blank screen when using basic graphics mode. This is the result of a SimpleDRM device not being created. gdm uses a fallback to x11 in this scenario, so it works. Setting `vga=791` in grub appears to work. Pending lorax PR adds this for basic graphics mode on BIOS: https://github.com/weldr/lorax/pull/1317 4. openssh — https://bugzilla.redhat.com/show_bug.cgi?id=2172956 — POST Update hostkey migration to support OSTree systems and dynamically detect hostkey location rpm-ostree systems don't run RPM scriptlets on upgrade, which could result in an upgrade locking users out of remote machines. Package pull requests https://src.fedoraproject.org/rpms/fedora-release/pull-request/253 and https://src.fedoraproject.org/rpms/openssh/pull-request/45 contain a candidate fix. 5. sddm — https://bugzilla.redhat.com/show_bug.cgi?id=2174563 — NEW Virtual keyboard (on-screen) not working at sddm-wayland-plasma The virtual keyboard at the login screen does not appear when you click the appropriate button. This appears to be a Wayland-specific issue; reverting to X11 allows the keyboard to work as expected. The keyboard works and the button enables/disables the keyboard, but does not bring up the keyboard 6. 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 — NEW 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. This seems likely to be an integer overflow. 2. accountservice — https://bugzilla.redhat.com/show_bug.cgi?id=2180768 — MODIFIED GDM takes "long" before allowing mouse moves and showing the user list. When wtmp is modified during boot, accountservice would have a blocking wait for 10 seconds. Update FEDORA-2023-a5af7d5db0 contains a candidate fix to enable high priority reload requests. 3. gnome-shell —
Re: F39 proposal: Changes of defaults in createrepo_c-1.0.0 (System-Wide Change proposal)
Il 23/03/23 19:52, Ben Cotton ha scritto: > https://fedoraproject.org/wiki/Changes/createrepo_c_1.0.0 > A quick look about this change impact on bodhi-server, as I understand from the relevant module at https://github.com/fedora-infra/bodhi/blob/develop/bodhi-server/bodhi/server/metadata.py : > == Detailed Description == > - Switch default compression from gz to zstd. DNF is able to > decompress zstd via libsolv since Fedora 30 and RHEL 8.4. It will > still be possible to create gz compressed repodata by manually > specifying gz compression. As I understand, bodhi sets XZ compression on all repos but those with a release prefix set to 'FEDORA-EPEL' (EPEL7, EPEL8 and EPEL9) where it uses BZ2. Do we want to continue using XZ or switch to the new ZSTD default? Do we want to continue using BZ for EPEL9 or switch to ZSTD/XZ? (EPEL Next, both 8 and 9, are already using XZ if I understand correctly) > > - Stop generating metadata in sqlite database format by default. It > will still be possible to create them using a --database switch or via > sqliterepo_c tool. (It looks like the only user left is mdapi: > https://github.com/fedora-infra/mdapi/issues/97). I think this haven't got impact on bodhi-server. > > - When adding groups.xml to repodata createrepo_c currently adds two > variants to repomd.xml. The specified file as is, uncompressed, with > the type "group" and also a compressed variant with type "group_XX", > where XX is compression suffix. This is atypical and unexpected. We > propose to include just one variant of groups.xml using specified > compression and repomd.xml type "group". This is not compatible with > yum in RHEL 7. If required users will still be able to create > repositories with the old layout using modifyrepo_c. I'm not sure if this has impact on bodhi-server. We're composing repodata for EPEL7 and EPEL8 which still use yum, but I don't think we're adding groups metadata? Mattia ___ 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-Needs] PR #1: Update license to SPDX format
mspacek merged a pull-request against the project: `perl-Test-Needs` that you are following. Merged pull-request: `` Update license to SPDX format `` https://src.fedoraproject.org/rpms/perl-Test-Needs/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-Needs] PR #1: Update license to SPDX format
mspacek opened a new pull-request against the project: `perl-Test-Needs` that you are following: `` Update license to SPDX format `` To reply, visit the link below https://src.fedoraproject.org/rpms/perl-Test-Needs/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
compiling gnome-extension with meson fails: ERROR: File null.gschema.xml does not exist.
Hi, I would like to compile the gnome extension netspeed [1] with meson, but unfortunately I cannot. If I compile the software with the following command: /usr/bin/meson setup --buildtype=plain --prefix=/usr --libdir=/usr/lib64 --libexecdir=/usr/libexec --bindir=/usr/bin --sbindir=/usr/sbin --includedir=/usr/include --datadir=/usr/share -- mandir=/usr/share/man --infodir=/usr/share/info --localedir=/usr/share/locale --sysconfdir=/etc --localstatedir=/var --sharedstatedir=/var/lib --wrap-mode=nodownload --auto-features=enabled . redhat-linux-build I get the error message: The Meson build system Version: 1.0.1 Source dir: /home/martin/rpmbuild/BUILD/gnome-shell-extension-netspeed-32 Build dir: /home/martin/rpmbuild/BUILD/gnome-shell-extension-netspeed-32/redhat-linux-build Build type: native build Project name: gnome-shell-extension-netspeed Project version: 32 Host machine cpu family: x86_64 Host machine cpu: x86_64 Program sh found: YES (/usr/bin/sh) Program jq found: YES (/usr/bin/jq) WARNING: You should add the boolean check kwarg to the run_command call. It currently defaults to false, but it will default to true in future releases of meson. See also: https://github.com/mesonbuild/meson/issues/9300 schemas/meson.build:6:0: ERROR: File null.gschema.xml does not exist. A full log can be found at /home/martin/rpmbuild/BUILD/gnome-shell-extension-netspeed-32/redhat-linux-build/meson-logs/meson-log.txt [1] https://martinkg.fedorapeople.org/Sources/gnome-shell-extension-netspeed-32.tar.gz thanks for any help 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
[Bug 2181578] New: perl-DateTime-TimeZone-2.59 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2181578 Bug ID: 2181578 Summary: perl-DateTime-TimeZone-2.59 is available Product: Fedora Version: rawhide Status: NEW Component: perl-DateTime-TimeZone Keywords: FutureFeature, Triaged Assignee: jples...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: iarn...@gmail.com, jples...@redhat.com, perl-devel@lists.fedoraproject.org Target Milestone: --- Classification: Fedora Releases retrieved: 2.59 Upstream release that is considered latest: 2.59 Current version/release in rawhide: 2.58-1.fc39 URL: http://metacpan.org/dist/DateTime-TimeZone/ 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/2801/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/perl-DateTime-TimeZone -- 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
Re: F39 proposal: Register EC2 Cloud Images with uefi-preferred AMI flag (Self-Contained Change proposal)
On Fri, Mar 24, 2023 at 11:24 AM Robbie Harwood wrote: > > Ben Cotton writes: > > > https://fedoraproject.org/wiki/Changes/CloudEC2UEFIPreferred > > > > This document represents a proposed Change. As part of the Changes > > process, proposals are publicly announced in order to receive > > community feedback. This proposal will only be implemented if approved > > by the Fedora Engineering Steering Committee. > > > > == Summary == > > A new feature of EC2 is to be able to register AMIs with a boot mode > > of `uefi-preferred` rather than picking one of `bios` or `uefi`. In > > EC2, aarch64 has always been UEFI, while x86-64 started out as BIOS > > only and some instance types have recently begun to support booting in > > UEFI mode. Previously, an AMI had to pick if it was UEFI or BIOS. With > > `uefi-preferred` it allows an AMI to launch with whatever firmware > > stack is available for the instance type, preferring UEFI when UEFI is > > an option. > > > > This proposal is to register the Fedora EC2 images with > > `uefi-preferred`, having the effect of switching to booting in UEFI > > mode on x86-64 in EC2 where available. > > > > == Owner == > > * Name: [[User:Trawets| Stewart Smith]] [[User:Davdunc| David Duncan]] > > * Email: traw...@amazon.com > > > > > > == Detailed Description == > > Some features of some EC2 instance types (such as secure boot) are > > only available in UEFI mode. There is also the standard set of > > advantages of UEFI over BIOS. All aarch64 instance types in EC2 have > > always been UEFI, while all x86-64 instance types were historically > > all BIOS. Recently, some x86-64 instance types have started to support > > UEFI mode. This was originally implemented as an option for instance > > launches and AMI registration. An AMI could state that it should be > > booted in UEFI mode. An AMI registered for UEFI would *not* boot on > > BIOS-only instance types. This meant that if you wanted to make > > available an OS that could boot on all instance types, you'd need a > > trio of AMIs: aarch64 UEFI, x86-64 BIOS, and x86-64 UEFI. > > > > With the `uefi-preferred` boot mode, one AMI registered for x86-64 > > will boot on UEFI where possible, but also boot BIOS if the instance > > type doesn't support UEFI. > > > > By registering Fedora AMIs with this boot mode, EC2 features that > > require UEFI (such as Secure Boot and NitroTPM) will be able to be > > used in Fedora, while still maintaining compatibility with BIOS only > > instance types. > > > > == Feedback == > > We have started registering Amazon Linux 2023 AMIs with this boot > > mode, albeit quite late in the development cycle of AL2023 due to the > > timing of when the `uefi-preferred` boot mode flag was added to EC2. > > > > == Benefit to Fedora == > > UEFI is becoming more ubiquitous amongst hardware, and operating under > > UEFI inside EC2 unlocks an increasing number of features such as > > Secure Boot and NitroTPM. The benefit for Fedora is a more uniform > > experience across cloud and non-cloud environments, simplifying the > > boot and runtime software stack. > > On behalf of the Fedora bootloader maintainers, thank you for this > change. > This is something we've been pushing across our cloud partners since I made our images support both boot modes. I'm really happy to finally take the next step to prefer UEFI on AWS. There's still a long tail of partners to work with on moving to UEFI, so we'll still maintain BIOS support for the time being, but it's being worked on. -- 真実はいつも一つ！/ Always, there's only one truth! ___ 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: Register EC2 Cloud Images with uefi-preferred AMI flag (Self-Contained Change proposal)
Ben Cotton writes: > https://fedoraproject.org/wiki/Changes/CloudEC2UEFIPreferred > > This document represents a proposed Change. As part of the Changes > process, proposals are publicly announced in order to receive > community feedback. This proposal will only be implemented if approved > by the Fedora Engineering Steering Committee. > > == Summary == > A new feature of EC2 is to be able to register AMIs with a boot mode > of `uefi-preferred` rather than picking one of `bios` or `uefi`. In > EC2, aarch64 has always been UEFI, while x86-64 started out as BIOS > only and some instance types have recently begun to support booting in > UEFI mode. Previously, an AMI had to pick if it was UEFI or BIOS. With > `uefi-preferred` it allows an AMI to launch with whatever firmware > stack is available for the instance type, preferring UEFI when UEFI is > an option. > > This proposal is to register the Fedora EC2 images with > `uefi-preferred`, having the effect of switching to booting in UEFI > mode on x86-64 in EC2 where available. > > == Owner == > * Name: [[User:Trawets| Stewart Smith]] [[User:Davdunc| David Duncan]] > * Email: traw...@amazon.com > > > == Detailed Description == > Some features of some EC2 instance types (such as secure boot) are > only available in UEFI mode. There is also the standard set of > advantages of UEFI over BIOS. All aarch64 instance types in EC2 have > always been UEFI, while all x86-64 instance types were historically > all BIOS. Recently, some x86-64 instance types have started to support > UEFI mode. This was originally implemented as an option for instance > launches and AMI registration. An AMI could state that it should be > booted in UEFI mode. An AMI registered for UEFI would *not* boot on > BIOS-only instance types. This meant that if you wanted to make > available an OS that could boot on all instance types, you'd need a > trio of AMIs: aarch64 UEFI, x86-64 BIOS, and x86-64 UEFI. > > With the `uefi-preferred` boot mode, one AMI registered for x86-64 > will boot on UEFI where possible, but also boot BIOS if the instance > type doesn't support UEFI. > > By registering Fedora AMIs with this boot mode, EC2 features that > require UEFI (such as Secure Boot and NitroTPM) will be able to be > used in Fedora, while still maintaining compatibility with BIOS only > instance types. > > == Feedback == > We have started registering Amazon Linux 2023 AMIs with this boot > mode, albeit quite late in the development cycle of AL2023 due to the > timing of when the `uefi-preferred` boot mode flag was added to EC2. > > == Benefit to Fedora == > UEFI is becoming more ubiquitous amongst hardware, and operating under > UEFI inside EC2 unlocks an increasing number of features such as > Secure Boot and NitroTPM. The benefit for Fedora is a more uniform > experience across cloud and non-cloud environments, simplifying the > boot and runtime software stack. On behalf of the Fedora bootloader maintainers, thank you for this change. Be well, --Robbie 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
F39 proposal: Register EC2 Cloud Images with uefi-preferred AMI flag (Self-Contained Change proposal)
https://fedoraproject.org/wiki/Changes/CloudEC2UEFIPreferred This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee. == Summary == A new feature of EC2 is to be able to register AMIs with a boot mode of `uefi-preferred` rather than picking one of `bios` or `uefi`. In EC2, aarch64 has always been UEFI, while x86-64 started out as BIOS only and some instance types have recently begun to support booting in UEFI mode. Previously, an AMI had to pick if it was UEFI or BIOS. With `uefi-preferred` it allows an AMI to launch with whatever firmware stack is available for the instance type, preferring UEFI when UEFI is an option. This proposal is to register the Fedora EC2 images with `uefi-preferred`, having the effect of switching to booting in UEFI mode on x86-64 in EC2 where available. == Owner == * Name: [[User:Trawets| Stewart Smith]] [[User:Davdunc| David Duncan]] * Email: traw...@amazon.com == Detailed Description == Some features of some EC2 instance types (such as secure boot) are only available in UEFI mode. There is also the standard set of advantages of UEFI over BIOS. All aarch64 instance types in EC2 have always been UEFI, while all x86-64 instance types were historically all BIOS. Recently, some x86-64 instance types have started to support UEFI mode. This was originally implemented as an option for instance launches and AMI registration. An AMI could state that it should be booted in UEFI mode. An AMI registered for UEFI would *not* boot on BIOS-only instance types. This meant that if you wanted to make available an OS that could boot on all instance types, you'd need a trio of AMIs: aarch64 UEFI, x86-64 BIOS, and x86-64 UEFI. With the `uefi-preferred` boot mode, one AMI registered for x86-64 will boot on UEFI where possible, but also boot BIOS if the instance type doesn't support UEFI. By registering Fedora AMIs with this boot mode, EC2 features that require UEFI (such as Secure Boot and NitroTPM) will be able to be used in Fedora, while still maintaining compatibility with BIOS only instance types. == Feedback == We have started registering Amazon Linux 2023 AMIs with this boot mode, albeit quite late in the development cycle of AL2023 due to the timing of when the `uefi-preferred` boot mode flag was added to EC2. == Benefit to Fedora == UEFI is becoming more ubiquitous amongst hardware, and operating under UEFI inside EC2 unlocks an increasing number of features such as Secure Boot and NitroTPM. The benefit for Fedora is a more uniform experience across cloud and non-cloud environments, simplifying the boot and runtime software stack. == Scope == * Proposal owners: * Modify the AMI registration call to include `uefi-preferred`, verifying that Fedora AMIs are assembled correctly for booting under UEFI. * Other developers: No changes needed by other developers * Release engineering: N/A * Policies and guidelines: N/A (not needed for this Change) * Trademark approval: N/A (not needed for this Change) * Alignment with Community Initiatives: == Upgrade/compatibility impact == == How To Test == Once the AMI is registered, verify that the parameter is set, and that instances can be launched for each instance type. Normal testing should cover this. == User Experience == Users will be able to use features in EC2 that require UEFI such as Secure Boot and NitroTPM. == Dependencies == == Contingency Plan == * Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change) * Contingency deadline: N/A (not a System Wide Change) * Blocks release? N/A (not a System Wide Change) == Documentation == * https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ami-boot.html * https://docs.aws.amazon.com/cli/latest/reference/ec2/register-image.html == Release Notes == EC2 images are now registered with the `uefi-preferred` boot mode, thus boot in UEFI mode where possible. -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis ___ devel-announce mailing list -- devel-announce@lists.fedoraproject.org To unsubscribe send an email to devel-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/devel-announce@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
F39 proposal: Register EC2 Cloud Images with uefi-preferred AMI flag (Self-Contained Change proposal)
https://fedoraproject.org/wiki/Changes/CloudEC2UEFIPreferred This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committee. == Summary == A new feature of EC2 is to be able to register AMIs with a boot mode of `uefi-preferred` rather than picking one of `bios` or `uefi`. In EC2, aarch64 has always been UEFI, while x86-64 started out as BIOS only and some instance types have recently begun to support booting in UEFI mode. Previously, an AMI had to pick if it was UEFI or BIOS. With `uefi-preferred` it allows an AMI to launch with whatever firmware stack is available for the instance type, preferring UEFI when UEFI is an option. This proposal is to register the Fedora EC2 images with `uefi-preferred`, having the effect of switching to booting in UEFI mode on x86-64 in EC2 where available. == Owner == * Name: [[User:Trawets| Stewart Smith]] [[User:Davdunc| David Duncan]] * Email: traw...@amazon.com == Detailed Description == Some features of some EC2 instance types (such as secure boot) are only available in UEFI mode. There is also the standard set of advantages of UEFI over BIOS. All aarch64 instance types in EC2 have always been UEFI, while all x86-64 instance types were historically all BIOS. Recently, some x86-64 instance types have started to support UEFI mode. This was originally implemented as an option for instance launches and AMI registration. An AMI could state that it should be booted in UEFI mode. An AMI registered for UEFI would *not* boot on BIOS-only instance types. This meant that if you wanted to make available an OS that could boot on all instance types, you'd need a trio of AMIs: aarch64 UEFI, x86-64 BIOS, and x86-64 UEFI. With the `uefi-preferred` boot mode, one AMI registered for x86-64 will boot on UEFI where possible, but also boot BIOS if the instance type doesn't support UEFI. By registering Fedora AMIs with this boot mode, EC2 features that require UEFI (such as Secure Boot and NitroTPM) will be able to be used in Fedora, while still maintaining compatibility with BIOS only instance types. == Feedback == We have started registering Amazon Linux 2023 AMIs with this boot mode, albeit quite late in the development cycle of AL2023 due to the timing of when the `uefi-preferred` boot mode flag was added to EC2. == Benefit to Fedora == UEFI is becoming more ubiquitous amongst hardware, and operating under UEFI inside EC2 unlocks an increasing number of features such as Secure Boot and NitroTPM. The benefit for Fedora is a more uniform experience across cloud and non-cloud environments, simplifying the boot and runtime software stack. == Scope == * Proposal owners: * Modify the AMI registration call to include `uefi-preferred`, verifying that Fedora AMIs are assembled correctly for booting under UEFI. * Other developers: No changes needed by other developers * Release engineering: N/A * Policies and guidelines: N/A (not needed for this Change) * Trademark approval: N/A (not needed for this Change) * Alignment with Community Initiatives: == Upgrade/compatibility impact == == How To Test == Once the AMI is registered, verify that the parameter is set, and that instances can be launched for each instance type. Normal testing should cover this. == User Experience == Users will be able to use features in EC2 that require UEFI such as Secure Boot and NitroTPM. == Dependencies == == Contingency Plan == * Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change) * Contingency deadline: N/A (not a System Wide Change) * Blocks release? N/A (not a System Wide Change) == Documentation == * https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ami-boot.html * https://docs.aws.amazon.com/cli/latest/reference/ec2/register-image.html == Release Notes == EC2 images are now registered with the `uefi-preferred` boot mode, thus boot in UEFI mode where possible. -- 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
[Bug 2181509] perl-Lexical-Var-0.010 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2181509 Jitka Plesnikova changed: What|Removed |Added Fixed In Version||perl-Lexical-Var-0.010-1.fc ||39 Status|ASSIGNED|CLOSED Resolution|--- |RAWHIDE Last Closed||2023-03-24 13:00:08 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2181509 ___ 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-Lexical-Var] PR #1: 0.010 bump; Package tests
jplesnik merged a pull-request against the project: `perl-Lexical-Var` that you are following. Merged pull-request: `` 0.010 bump; Package tests `` https://src.fedoraproject.org/rpms/perl-Lexical-Var/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-Lexical-Var] PR #1: 0.010 bump; Package tests
jplesnik opened a new pull-request against the project: `perl-Lexical-Var` that you are following: `` 0.010 bump; Package tests `` To reply, visit the link below https://src.fedoraproject.org/rpms/perl-Lexical-Var/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
Fedora 38 compose report: 20230324.n.0 changes
OLD: Fedora-38-20230323.n.0 NEW: Fedora-38-20230324.n.0 = SUMMARY = Added images:1 Dropped images: 0 Added packages: 1 Dropped packages:1 Upgraded packages: 91 Downgraded packages: 0 Size of added packages: 267.66 KiB Size of dropped packages:708.66 KiB Size of upgraded packages: 801.56 MiB Size of downgraded packages: 0 B Size change of upgraded packages: 3.44 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = Image: Kinoite dvd-ostree ppc64le Path: Kinoite/ppc64le/iso/Fedora-Kinoite-ostree-ppc64le-38-20230324.n.0.iso = DROPPED IMAGES = = ADDED PACKAGES = Package: libcuefile-0-0.1.20110810svn475.fc38 Summary: CUE file library from Musepack RPMs:libcuefile libcuefile-devel Size:267.66 KiB = DROPPED PACKAGES = Package: zn_poly-0.9.2-9.fc38 Summary: C library for polynomial arithmetic RPMs:zn_poly zn_poly-devel zn_poly-static Size:708.66 KiB = UPGRADED PACKAGES = Package: adwaita-icon-theme-44.0-1.fc38 Old package: adwaita-icon-theme-44~beta-1.fc38 Summary: Adwaita icon theme RPMs: adwaita-cursor-theme adwaita-icon-theme adwaita-icon-theme-devel Size: 1.71 MiB Size change: -11 B Changelog: * Mon Mar 20 2023 David King - 44.0-1 - Update to 44.0 Package: at-spi2-core-2.48.0-1.fc38 Old package: at-spi2-core-2.47.90-1.fc38 Summary: Protocol definitions and daemon for D-Bus at-spi RPMs: at-spi2-atk at-spi2-atk-devel at-spi2-core at-spi2-core-devel atk atk-devel Size: 6.34 MiB Size change: -183 B Changelog: * Sun Mar 19 2023 David King - 2.48.0-1 - Update to 2.48.0 Package: atomix-44.0-1.fc38 Old package: atomix-44~rc-1.fc38 Summary: Puzzle game: Build molecules out of isolated atoms RPMs: atomix Size: 2.00 MiB Size change: 273 B Changelog: * Sat Mar 18 2023 David King - 44.0-1 - Update to 44.0 Package: baobab-44.0-1.fc38 Old package: baobab-44~rc-1.fc38 Summary: A graphical directory tree analyzer RPMs: baobab Size: 1.85 MiB Size change: 1.61 KiB Changelog: * Sun Mar 19 2023 David King - 44.0-1 - Update to 44.0 Package: btrfs-progs-6.2.1-2.fc38 Old package: btrfs-progs-6.2.1-1.fc38 Summary: Userspace programs for btrfs RPMs: btrfs-progs btrfs-progs-devel libbtrfs libbtrfsutil python3-btrfsutil Size: 5.71 MiB Size change: 4.67 KiB Changelog: * Wed Mar 22 2023 Neal Gompa - 6.2.1-2 - Add patch to force default sectorsize to 4k Package: container-selinux-2:2.205.0-1.fc38 Old package: container-selinux-2:2.204.0-1.fc38 Summary: SELinux policies for container runtimes RPMs: container-selinux Size: 51.00 KiB Size change: 44 B Changelog: * Thu Mar 16 2023 RH Container Bot - 2:2.205.0-1 - auto bump to v2.205.0 Package: eog-44.0-1.fc38 Old package: eog-44~beta-1.fc38 Summary: Eye of GNOME image viewer RPMs: eog eog-devel eog-tests Size: 9.22 MiB Size change: -5.95 KiB Changelog: * Sun Mar 19 2023 David King - 44.0-1 - Update to 44.0 Package: eog-plugins-44.0-1.fc38 Old package: eog-plugins-42.3-2.fc38 Summary: A collection of plugins for the eog image viewer RPMs: eog-plugin-exif-display eog-plugin-export-to-folder eog-plugin-fit-to-width eog-plugin-fullscreenbg eog-plugin-light-theme eog-plugin-map eog-plugin-maximize-windows eog-plugin-postasa eog-plugin-pythonconsole eog-plugin-send-by-mail eog-plugin-slideshowshuffle eog-plugins eog-plugins-data Size: 1.03 MiB Size change: -11.79 KiB Changelog: * Sun Mar 19 2023 David King - 44.0-1 - Update to 44.0 Package: epiphany-1:44.0-1.fc38 Old package: epiphany-1:44~rc-3.fc38 Summary: Web browser for GNOME RPMs: epiphany epiphany-runtime Size: 11.10 MiB Size change: -10.83 KiB Changelog: * Tue Mar 21 2023 David King - 1:44.0-1 - Update to 44.0 Package: evince-44.1-1.fc38 Old package: evince-44~rc-2.fc38 Summary: Document viewer RPMs: evince evince-devel evince-djvu evince-dvi evince-libs evince-previewer evince-thumbnailer Size: 12.91 MiB Size change: 9.46 KiB Changelog: * Sat Mar 18 2023 David King - 44.0-1 - Update to 44.0 * Wed Mar 22 2023 David King - 44.1-1 - Update to 44.1 Package: evolution-3.48.0-1.fc38 Old package: evolution-3.47.2-1.fc38 Summary: Mail and calendar client for GNOME RPMs: evolution evolution-bogofilter evolution-devel evolution-devel-docs evolution-help evolution-langpacks evolution-pst evolution-spamassassin Size: 30.27 MiB Size change: -21.69 KiB Changelog: * Fri Mar 03 2023 Milan Crha - 3.47.3-1 - Update to 3.47.3 - Resolves: #2142385 (Properly apply TEMP_HOME compile time option for Flatpak) * Fri Mar 17 2023 Milan Crha - 3.48.0-1 - Update to 3.48.0 Package: evolution-data-server-3.48.0-1.fc38 Old package: evolution-data
[rpms/perl-IO-Socket-IP] PR #2: Remove not needed Socket6 package in build
mspacek merged a pull-request against the project: `perl-IO-Socket-IP` that you are following. Merged pull-request: `` Remove not needed Socket6 package in build `` https://src.fedoraproject.org/rpms/perl-IO-Socket-IP/pull-request/2 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[rpms/perl-IO-Socket-IP] PR #2: Remove not needed Socket6 package in build
mspacek opened a new pull-request against the project: `perl-IO-Socket-IP` that you are following: `` Remove not needed Socket6 package in build `` To reply, visit the link below https://src.fedoraproject.org/rpms/perl-IO-Socket-IP/pull-request/2 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[rpms/perl-IO-Socket-IP] PR #1: Remove not needed Socket6 package in build
mspacek merged a pull-request against the project: `perl-IO-Socket-IP` that you are following. Merged pull-request: `` Remove not needed Socket6 package in build `` https://src.fedoraproject.org/rpms/perl-IO-Socket-IP/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 2181509] perl-Lexical-Var-0.010 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2181509 Jitka Plesnikova changed: What|Removed |Added CC|jples...@redhat.com,| |p...@city-fan.org | Status|NEW |ASSIGNED Doc Type|--- |If docs needed, set a value -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2181509 ___ 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-IO-Socket-IP] PR #1: Remove not needed Socket6 package in build
mspacek opened a new pull-request against the project: `perl-IO-Socket-IP` that you are following: `` Remove not needed Socket6 package in build `` To reply, visit the link below https://src.fedoraproject.org/rpms/perl-IO-Socket-IP/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 2181509] New: perl-Lexical-Var-0.010 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2181509 Bug ID: 2181509 Summary: perl-Lexical-Var-0.010 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Lexical-Var Keywords: FutureFeature, Triaged Assignee: jples...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: jples...@redhat.com, p...@city-fan.org, perl-devel@lists.fedoraproject.org Target Milestone: --- Classification: Fedora Releases retrieved: 0.010 Upstream release that is considered latest: 0.010 Current version/release in rawhide: 0.009-31.fc38 URL: http://search.cpan.org/dist/Lexical-Var/ 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/3021/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/perl-Lexical-Var -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2181509 ___ 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
Apache Maven 3.9 update in Fedora
Package maven in Fedora Rawhide will be updated from version 3.8.6 to version 3.9.1 on 31 March 2023. This minor version update contains breaking behavioral changes that are known to affect some packages. More information can be found in upstream release notes at https://maven.apache.org/docs/3.9.0/release-notes.html I will take care of fixing packages listed on https://versions.kjnet.xyz/ There is no API/ABI break that I know of, so I'm not CCing maintainers of dependent packages directly. Packages are known to require or build-require maven: - DecodeIR - IPAddress - ant-antunit - antlr-maven-plugin - antlr3 - antlr32 - antlr4-project - antlrworks - apache-commons-beanutils - apache-commons-cli - apache-commons-collections - apache-commons-collections4 - apache-commons-compress - apache-commons-digester - apache-commons-exec - apache-commons-fileupload - apache-commons-jxpath - apache-commons-logging - apache-commons-math - apache-commons-modeler - apache-commons-net - apache-commons-parent - apache-commons-pool - apache-parent - apache-resource-bundles - apache-sshd - apiguardian - aqute-bnd - args4j - assertj-core - atinject - auto - batik - bcel - beust-jcommander - build-helper-maven-plugin - buildnumber-maven-plugin - byte-buddy - byteman - canl-java - cdi-api - cglib - classloader-leak-test-framework - classpathless-compiler - clojure - clojure-core-specs-alpha - clojure-maven-plugin - clojure-spec-alpha - codehaus-parent - decentxml - directory-maven-plugin - dirgra - disruptor - dogtag-pki - dom4j - easymock - ed25519-java - exec-maven-plugin - extra-enforcer-rules - fasterxml-oss-parent - felix-parent - felix-utils - fishbowl - fop - forge-parent - fusesource-pom - google-gson - hamcrest - hawtjni - hibernate-jpa-2.0-api - hibernate-jpa-2.1-api - hid4java - httpcomponents-project - jackson-annotations - jackson-bom - jackson-core - jackson-databind - jackson-dataformats-binary - jackson-dataformats-text - jackson-jaxrs-providers - jackson-modules-base - jackson-parent - jacoco - jacop - jakarta-activation - jakarta-activation1 - jakarta-annotations - jakarta-el - jakarta-interceptors - jakarta-json - jakarta-mail - jakarta-saaj - jakarta-server-pages - jakarta-servlet - jakarta-xml-ws - janino - jansi - jansi-native - jansi1 - java-diff-utils - java-dirq - java-jd-decompiler - java-runtime-decompiler - java-scrypt - javacc-maven-plugin - javaewah - javapackages-tools - javaparser - javapoet - javassist - jaxb - jaxb-api - jaxb-api2 - jaxb-dtd-parser - jaxb-fi - jaxb-istack-commons - jaxb-stax-ex - jaxen - jboss-jaxrs-2.0-api - jboss-logging - jboss-logging-tools - jboss-parent - jchardet - jcommon - jdeparser - jdependency - jetty - jflex - jfreechart - jgit - jglobus - jgoodies-common - jgoodies-forms - jgoodies-looks - jigawatts - jline - jline2 - jmock - jneuroml-core - jni-inchi - jol - jolokia-jvm-agent - joni - jopt-simple - jsch - jsch-agent-proxy - json_simple - junit - junit5 - juniversalchardet - jzlib - log4j - lucene - mariadb-java-client - maven - maven-antrun-plugin - maven-archetype - maven-archiver - maven-artifact-transfer - maven-assembly-plugin - maven-bundle-plugin - maven-clean-plugin - maven-common-artifact-filters - maven-compiler-plugin - maven-dependency-analyzer - maven-dependency-plugin - maven-dependency-tree - maven-doxia - maven-doxia-sitetools - maven-enforcer - maven-file-management - maven-filtering - maven-invoker - maven-invoker-plugin - maven-jar-plugin - maven-mapping - maven-native - maven-parent - maven-patch-plugin - maven-plugin-testing - maven-plugin-tools - maven-remote-resources-plugin - maven-reporting-api - maven-reporting-impl - maven-resources-plugin - maven-script-interpreter - maven-shade-plugin - maven-shared-incremental - maven-shared-io - maven-shared-utils - maven-source-plugin - maven-surefire - maven-verifier - maven-verifier-plugin - maven2 - mockito - modello - modulemaker-maven-plugin - mojo-executor - mojo-parent - munge-maven-plugin - mxparser - nom-tam-fits - objectweb-asm - objenesis - ongres-scram - ongres-stringprep - openjdk-asmtools - openjdk-asmtools7 - openjfx - openstack-java-sdk - opentest4j - options - osgi-annotation - osgi-compendium - osgi-core - parserng - pcfi - pdfbox - picocli - plexus-active-collections - plexus-archiver - plexus-build-api - plexus-compiler - plexus-component-api - plexus-components-pom - plexus-containers - plexus-i18n - plexus-languages - plexus-pom - plexus-resources - plexus-utils - plexus-velocity - pomchecker - postgresql-jdbc - prometheus-jmx-exporter - prometheus-simpleclient-java - python-javaobj - qdox - rachota - reflections - replacer - resteasy - rhino - rsyntaxtextarea - scala - scalacheck - scannotation - sequence-library - serp - sisu-mojos - snakeyaml - spec-version-maven-plugin - spice-parent - string-template-maven-plugin - stringtemplate4 - svnkit - t-digest - testng - tomcat-taglibs-parent - treelayout - trilead-ssh2 - truth - tuxguitar - univocity-parsers - velocity -
Google Guice 5 update in Fedora
Package google-guice in Fedora Rawhide will be updated from version 4.2.3 to version 5.1.0 on 31 March 2023. This major version update breaks ABI and API, so I'm sending this notice one week in advance, per Fedora Updates Policy. Packages that require or build-require google-guice: - maven - maven-resolver - maven-shade-plugin - modello - pomchecker - sisu - testng - xmvn I will take care of porting all above packages except pomchecker. -- Mikolaj Izdebski ___ 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: Changes of defaults in createrepo_c-1.0.0 (System-Wide Change proposal)
On Thu, Mar 23, 2023 at 02:52:50PM -0400, Ben Cotton wrote: > https://fedoraproject.org/wiki/Changes/createrepo_c_1.0.0 > == Summary == > Update createrepo_c to 1.0.0, new release will include change of > default compression to zstd, no longer generating metadata in sqlite > database format by default and simplified comps xml type in repodata. LGTM. Thank you for taking the time to figure out all the dependencies. While at it, would it be possible to narrow down the check for which file paths are included in primary filelists to match the packaging docs? Currently [1] the pattern is implemented as '(^/etc|^/usr/lib/sendmail$|bin/)' (note that "bin/" can apply anywhere in the string). The comment says that this is for yum compat [2]. Our guidelines only mention files under /usr/bin, /usr/sbin, /etc [3]. I think that the number of files affected is small, but it is a potential source of confusion and a hard-to-explain discrepancy between what the guidelines say and actual dnf behaviour. Yum is long gone and we clearly intended to clean this up many years ago but never got round to it. [1] https://github.com/rpm-software-management/createrepo_c/blob/master/src/misc.h#L106 [2] https://github.com/rpm-software-management/createrepo_c/blob/master/src/misc.c#L180 [3] https://docs.fedoraproject.org/en-US/packaging-guidelines/#_file_and_directory_dependencies 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
[Bug 2181377] perl-Business-ISBN-3.008 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2181377 Jitka Plesnikova changed: What|Removed |Added Fixed In Version||perl-Business-ISBN-3.008-1. ||fc39 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2181377 ___ 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 2181237] perl-Business-ISBN-3.007-5.fc39 FTBFS: t/errors.t: Failed test 'ISBN 9786316294241 error text mentions 'group''
https://bugzilla.redhat.com/show_bug.cgi?id=2181237 Jitka Plesnikova changed: What|Removed |Added Fixed In Version||perl-Business-ISBN-3.008-1. ||fc39 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2181237 ___ 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 2181377] perl-Business-ISBN-3.008 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2181377 Fedora Update System changed: What|Removed |Added Status|ASSIGNED|MODIFIED --- Comment #1 from Fedora Update System --- FEDORA-2023-5b3f14cd81 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-5b3f14cd81 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2181377 ___ 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 2181237] perl-Business-ISBN-3.007-5.fc39 FTBFS: t/errors.t: Failed test 'ISBN 9786316294241 error text mentions 'group''
https://bugzilla.redhat.com/show_bug.cgi?id=2181237 Fedora Update System changed: What|Removed |Added Status|NEW |MODIFIED --- Comment #2 from Fedora Update System --- FEDORA-2023-5b3f14cd81 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-5b3f14cd81 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2181237 ___ 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-Business-ISBN] PR #2: 3.008 bump
jplesnik merged a pull-request against the project: `perl-Business-ISBN` that you are following. Merged pull-request: `` 3.008 bump `` https://src.fedoraproject.org/rpms/perl-Business-ISBN/pull-request/2 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[rpms/perl-Business-ISBN] PR #2: 3.008 bump
jplesnik opened a new pull-request against the project: `perl-Business-ISBN` that you are following: `` 3.008 bump `` To reply, visit the link below https://src.fedoraproject.org/rpms/perl-Business-ISBN/pull-request/2 ___ perl-devel mailing list -- perl-devel@lists.fedoraproject.org To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
[Bug 2181377] perl-Business-ISBN-3.008 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2181377 Jitka Plesnikova changed: What|Removed |Added Status|NEW |ASSIGNED Doc Type|--- |If docs needed, set a value -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2181377 ___ 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
