[EPEL-devel] Fedora EPEL 7 updates-testing report
The following Fedora EPEL 7 Security updates need testing: Age URL 4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-5418332424 chromium-120.0.6099.109-1.el7 2 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-33f7b7a10c unrealircd-6.1.4-1.el7 The following builds have been pushed to Fedora EPEL 7 updates-testing php-Smarty-3.1.48-2.el7 zchunk-1.4.0-1.el7 Details about builds: php-Smarty-3.1.48-2.el7 (FEDORA-EPEL-2023-2ff4055b33) Smarty - the compiling PHP template engine Update Information: Fixed Cross site scripting vulnerability in Javascript escaping. This addresses CVE-2023-28447 ChangeLog: * Fri Jul 21 2023 Fedora Release Engineering - 3.1.48-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild * Mon Apr 3 2023 Shawn Iwinski - 3.1.48-1 - Update to 3.1.48 - CVE-2023-28447 (RHBZ #2183911, 2183912, 2183913, 2183914) * Fri Jan 20 2023 Fedora Release Engineering - 3.1.47-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild zchunk-1.4.0-1.el7 (FEDORA-EPEL-2023-dc53e7a420) Compressed file format that allows easy deltas Update Information: * Add native OpenSSL 3 compatibility * Add new function for getting zchunk context from chunk * Fix bug when assembling from multiple sources ChangeLog: * Tue Dec 19 2023 Jonathan Dieter - 1.4.0-1 - Add native OpenSSL 3 compatibility - Add new function for getting zchunk context from chunk - Fix bug when assembling from multiple sources -- ___ 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 2252479] perl-Date-Manip-6.93 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2252479 Fedora Update System changed: What|Removed |Added Fixed In Version||perl-Date-Manip-6.93-1.fc39 Resolution|--- |ERRATA Status|ON_QA |CLOSED Last Closed||2023-12-20 01:24:20 --- Comment #5 from Fedora Update System --- FEDORA-2023-c6885fca46 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=2252479 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202252479%23c5 -- ___ 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 8 updates-testing report
The following Fedora EPEL 8 Security updates need testing: Age URL 4 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-a79d31df77 chromium-120.0.6099.109-1.el8 2 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-4cbae7b5bd unrealircd-6.1.4-1.el8 0 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-1bdb2efa01 tor-0.4.8.10-1.el8 The following builds have been pushed to Fedora EPEL 8 updates-testing ansible-collection-awx-awx-23.5.1-1.el8 php-adodb-5.22.7-1.el8 zchunk-1.4.0-1.el8 Details about builds: ansible-collection-awx-awx-23.5.1-1.el8 (FEDORA-EPEL-2023-8552238e30) Ansible modules and plugins for working with AWX Update Information: Update to 23.5.1 ChangeLog: * Tue Dec 19 2023 Andrew Heath - 23.5.1-1 - Update to 23.5.1 and clean up spec file php-adodb-5.22.7-1.el8 (FEDORA-EPEL-2023-4138b387a7) Database abstraction layer for PHP Update Information: 5.22.7, fix for CVE-2021-3850 ChangeLog: * Tue Dec 19 2023 Gwyn Ciesla - 5.22.7-1 - 5.22.7 * Fri Jul 21 2023 Fedora Release Engineering - 5.22.6-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild * Mon Jun 12 2023 Gwyn Ciesla - 5.22.6-1 - 5.22.6 * Tue Apr 4 2023 Gwyn Ciesla - 5.22.5-1 - 5.22.5 * Wed Mar 1 2023 Gwyn Ciesla - 5.22.4-3 - migrated to SPDX license * Fri Jan 20 2023 Fedora Release Engineering - 5.22.4-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild * Mon Dec 5 2022 Gwyn Ciesla - 5.22.4-1 - 5.22.4 * Fri Jul 22 2022 Fedora Release Engineering - 5.20.6-14 - Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild * Fri Jan 21 2022 Fedora Release Engineering - 5.20.6-13 - Rebuilt for https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild * Fri Jul 23 2021 Fedora Release Engineering - 5.20.6-12 - Rebuilt for https://fedoraproject.org/wiki/Fedora_35_Mass_Rebuild * Wed Jan 27 2021 Fedora Release Engineering - 5.20.6-11 - Rebuilt for https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild * Tue Jul 28 2020 Fedora Release Engineering - 5.20.6-10 - Rebuilt for https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild References: [ 1 ] Bug #2255193 - CVE-2021-3850 php-adodb: authentication bypass in PostgreSQL connections [epel-all] https://bugzilla.redhat.com/show_bug.cgi?id=2255193 zchunk-1.4.0-1.el8 (FEDORA-EPEL-2023-bafa27d160) Compressed file format that allows easy deltas Update Information: * Add native OpenSSL 3 compatibility * Add new function for getting zchunk context from chunk * Fix bug when assembling from multiple sources ChangeLog: * Tue Dec 19 2023 Jonathan Dieter - 1.4.0-1 - Add native OpenSSL 3 compatibility - Add new function for getting zchunk context from chunk - Fix bug when assembling from multiple sources -- ___ 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: Enabling GOPROXY and GOSUMDB in Fedora
On Tue, Dec 19, 2023 at 4:14 PM Brad Smith wrote: > > At a minimum, I recommend that the patch include the original values > for GOPROXY, GOSUMDB, and GOTOOLCHAIN as comments. This makes it > easier to change back to default values. At the moment, one has to > visit the relevant web pages. > > I lean towards providing upstream defaults in this case with updated > content on the developer portal (and elsewhere?) with information on > why changing these values would be useful. I agree that the comments > in the thread are persuasive (for me). > I agree with this. I'd rather keep the patch than revert to upstream defaults. -- 真実はいつも一つ！/ 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
SCons-4.6.0
Hi all. SCons-4.6.0 will be built in Rawhide. Here there are testing builds if you need to try your packages with it: https://copr.fedorainfracloud.org/coprs/sagitter/ForTesting/build/6771118/ Regards. -- --- Antonio Trande Fedora Project https://fedoraproject.org/wiki/User:Sagitter mailto: sagit...@fedoraproject.org GPG key: 0x40FDA7B70789A9CD GPG keys server: https://keys.openpgp.org/ OpenPGP_signature.asc 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
Re: Enabling GOPROXY and GOSUMDB in Fedora
At a minimum, I recommend that the patch include the original values for GOPROXY, GOSUMDB, and GOTOOLCHAIN as comments. This makes it easier to change back to default values. At the moment, one has to visit the relevant web pages. I lean towards providing upstream defaults in this case with updated content on the developer portal (and elsewhere?) with information on why changing these values would be useful. I agree that the comments in the thread are persuasive (for me). best regards Brad On Tue, Dec 19, 2023 at 8:34 AM Alejandro Saez Morollon wrote: > > Hi everyone. > > > TL;DR: Remove a patch we ship in Go that disables GOPROXY and GOSUMDB and > follow upstream defaults, or keep it? > > > Recently, I had a short conversation in a public forum about two Go features > that we modified in Fedora. GOPROXY and GOSUMDB. As I prepare the Fedora 40 > and Go 1.22 proposal, it is a great time to discuss it. > > > You can see the conversation here, I think they bring really good points that > we should consider: > > https://mas.to/@zekjur/111359951465906642 > > > So first, what are these variables? > > GOPROXY sets the server for fetching module-related information and > dependencies. > > GOSUMDB sets the checksum database URL to verify module downloads and ensure > their integrity during module resolution. > > > You can read them more in detail here: > > https://go.dev/ref/mod#environment-variables > > https://go.dev/ref/mod#authenticating > > https://go.dev/ref/mod#module-proxy > > > There are four approaches as I see this: > > Keep it the way it is right now. > > Remove the patch and follow upstream. > > Create a way to ensure the users know that that option can be changed and > leave one of the two previous options as default (by creating two packages, > one with the default setting and another that applies the patch). > > Have a GOPROXY service by Fedora. > > > 1 and 2 are the easiest and most logical ones. 3rd is complex, and I'm not > sure it brings any value. 4th would be ideal, but that means maintaining a > service with all its costs and time. > > > -- > ___ > 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: Change of cronie and crontabs CIS compliance
In my opinion none of these permission changes make any sense for installations that aren't guided by some mostly much more strict requirements than those for the Fedora workstations or other general installations of Fedora. They simply should not be applied. Removing the setuid bit from the crontab command is simply wrong as it breaks crontab for regular users. I do not even know why the /var/spool/anacron/cron.* permissions on the ghost files should be set to executable by owner - there is no point doing that as that makes the permissions more allowing than they currently are. And making /etc/cron.d and /etc/cron.hourly unreadable to anybody else than root will break the possibility to examine what would be the next job run by the cronnext command. -- ___ 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
Orphaning python-pytzdata
Hello,
I found myself being the main admin of python-pytzdata.
I have not done this on purpose, somebody must have given the package to me.
I'm orphaning it.
$ repoquery -q --repo=rawhide{,-source} --whatrequires python3-pytzdata
python-maya-0:0.6.1-10.fc39.src
python-pendulum-0:2.1.2-12.fc39.src
python3-pendulum-0:2.1.2-12.fc39.x86_64
--
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
Re: Obsoleting zlib in Fedora Rawhide
Tulio Magno Quites Machado Filho writes: > Following the recent approval from Fesco, I'm planning to distribute > zlib-ng-compat packages for Rawhide later this week. > I hope this will give us enough time to work on the issues before > Fedora 40 is released. 爛 > > So, keep in mind this will *obsolete zlib in Rawhide*. > > This update is also known to trigger test failures in the following > packages: > > - binutils > - cpp-httplib > - git > - jose > - libpng > - openexr1 > - openms > - python-3.12 > - qpdf With the help from upstream and downstream, all these packages already have a solution available. Some had fixes upstream and a few of them had changes applied only downstream. With that said, I'm finally moving forward with the zlib-ng rebuilt that will obsolete zlib. Again, if you have any questions or find any issues, let me know. Thanks to all maintainers upstream and downstream that helped with this! -- Tulio Magno -- ___ 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: *****SPAM***** Enabling GOPROXY and GOSUMDB in Fedora
On Tue Dec 19, 2023 at 17:33 +0100, Alejandro Saez Morollon wrote: > TL;DR: Remove a patch we ship in Go that disables GOPROXY and GOSUMDB and > follow upstream defaults, or keep it? I support keeping the Google Go module proxy disabled by default. Our packages should not send telemetry data to Google without explicit opt-in. We can highlight in the documentation how to re-eanble GOPROXY and GOSUMDB if necessary. -- Maxwell G (@gotmax23) Pronouns: He/They -- ___ 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
Enabling GOPROXY and GOSUMDB in Fedora
Hi everyone. TL;DR: Remove a patch we ship in Go that disables GOPROXY and GOSUMDB and follow upstream defaults, or keep it? Recently, I had a short conversation in a public forum about two Go features that we modified in Fedora. GOPROXY and GOSUMDB. As I prepare the Fedora 40 and Go 1.22 proposal, it is a great time to discuss it. You can see the conversation here, I think they bring really good points that we should consider: https://mas.to/@zekjur/111359951465906642 So first, what are these variables? - GOPROXY sets the server for fetching module-related information and dependencies. - GOSUMDB sets the checksum database URL to verify module downloads and ensure their integrity during module resolution. You can read them more in detail here: - https://go.dev/ref/mod#environment-variables - https://go.dev/ref/mod#authenticating - https://go.dev/ref/mod#module-proxy There are four approaches as I see this: 1. Keep it the way it is right now. 2. Remove the patch and follow upstream. 3. Create a way to ensure the users know that that option can be changed and leave one of the two previous options as default (by creating two packages, one with the default setting and another that applies the patch). 4. Have a GOPROXY service by Fedora. 1 and 2 are the easiest and most logical ones. 3rd is complex, and I'm not sure it brings any value. 4th would be ideal, but that means maintaining a service with all its costs and time. -- ___ 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] [Fedocal] Reminder meeting : EPEL Steering Committee
Dear all, You are kindly invited to the meeting: EPEL Steering Committee on 2023-12-20 from 16:00:00 to 17:00:00 US/Eastern At fedora-meet...@chat.fedoraproject.org The meeting will be about: https://chat.fedoraproject.org/#/room/#meeting:fedoraproject.org This is the weekly EPEL Steering Committee Meeting. A general agenda is the following: #topic aloha #topic EPEL Issues https://pagure.io/epel/issues * https://pagure.io/epel/issues?tags=meeting=Open #topic Old Business (if needed) #topic General Issues / Open Floor Source: https://calendar.fedoraproject.org//meeting/9854/ -- ___ 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
Fedora rawhide compose report: 20231219.n.0 changes
OLD: Fedora-Rawhide-20231218.n.0 NEW: Fedora-Rawhide-20231219.n.0 = SUMMARY = Added images:0 Dropped images: 2 Added packages: 5 Dropped packages:1 Upgraded packages: 305 Downgraded packages: 0 Size of added packages: 30.94 MiB Size of dropped packages:1.19 MiB Size of upgraded packages: 26.49 GiB Size of downgraded packages: 0 B Size change of upgraded packages: 28.08 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = = DROPPED IMAGES = Image: Workstation live aarch64 Path: Workstation/aarch64/iso/Fedora-Workstation-Live-aarch64-Rawhide-20231218.n.0.iso Image: Cloud_Base tar-gz x86_64 Path: Cloud/x86_64/images/Fedora-Cloud-Base-GCP-Rawhide-20231218.n.0.x86_64.tar.gz = ADDED PACKAGES = Package: elementary-calculator-2.0.2-1.fc40 Summary: Calculator app designed for elementary RPMs:elementary-calculator Size:611.95 KiB Package: elementary-calendar-7.0.0-1.fc40 Summary: Desktop calendar app designed for elementary RPMs:elementary-calendar elementary-calendar-devel Size:2.00 MiB Package: kaffeine-2.0.18-10.fc40 Summary: KDE media player based on VLC RPMs:kaffeine Size:24.72 MiB Package: kdiagram2-2.8.0-8.fc40 Summary: Powerful libraries (KChart, KGantt) for creating business diagrams RPMs:kdiagram2 kdiagram2-devel Size:3.60 MiB Package: python-expandvars-0.12.0-2.fc40 Summary: Expand system variables Unix style RPMs:python3-expandvars Size:19.54 KiB = DROPPED PACKAGES = Package: rubygem-byebug-11.1.3-5.fc39 Summary: Ruby 2.0 fast debugger - base + CLI RPMs:rubygem-byebug rubygem-byebug-doc Size:1.19 MiB = UPGRADED PACKAGES = Package: alt-ergo-2.3.3-13.fc40 Old package: alt-ergo-2.3.3-12.fc40 Summary: Automated theorem prover including linear arithmetic RPMs: alt-ergo alt-ergo-gui ocaml-alt-ergo-lib ocaml-alt-ergo-lib-devel ocaml-alt-ergo-parsers ocaml-alt-ergo-parsers-devel Size: 88.20 MiB Size change: 5.01 KiB Changelog: * Mon Dec 18 2023 Richard W.M. Jones - 2.3.3-13 - OCaml 5.1.1 + s390x code gen fix for Fedora 40 Package: apron-0.9.14-4.fc40 Old package: apron-0.9.14-3.fc40 Summary: Numerical abstract domain library RPMs: apron apron-devel japron ocaml-apron ocaml-apron-devel Size: 14.37 MiB Size change: 3.69 KiB Changelog: * Mon Dec 18 2023 Richard W.M. Jones - 0.9.14-4 - OCaml 5.1.1 + s390x code gen fix for Fedora 40 Package: asahi-audio-1.6-1.fc40 Old package: asahi-audio-1.5-1.fc40 Summary: PipeWire DSP profiles for Apple Silicon machines RPMs: asahi-audio Size: 1.63 MiB Size change: -166 B Changelog: * Mon Dec 18 2023 Hector Martin - 1.6-1 - Update to 1.6 Package: autofs-1:5.1.9-4.fc40 Old package: autofs-1:5.1.9-3.fc40 Summary: A tool for automatically mounting and unmounting filesystems RPMs: autofs Size: 1.54 MiB Size change: -170 B Changelog: * Mon Dec 18 2023 Florian Weimer - 1:5.1.9-4 - Further C compatibility fixes, run autoconf Package: brltty-6.6-8.fc40 Old package: brltty-6.6-6.fc40 Summary: Braille display driver for Linux/Unix RPMs: brlapi brlapi-devel brlapi-java brltty brltty-at-spi2 brltty-docs brltty-dracut brltty-espeak brltty-espeak-ng brltty-minimal brltty-speech-dispatcher brltty-xw ocaml-brlapi python3-brlapi tcl-brlapi Size: 17.56 MiB Size change: 11.85 KiB Changelog: * Mon Dec 18 2023 Richard W.M. Jones - 6.6-7 - OCaml 5.1.1 + s390x code gen fix for Fedora 40 * Mon Dec 18 2023 Richard W.M. Jones - 6.6-8 - Bump release and rebuild Package: certbot-2.8.0-1.fc40 Old package: certbot-2.7.2-1.fc40 Summary: A free, automated certificate authority client RPMs: certbot python-acme-doc python-certbot-dns-cloudflare-doc python-certbot-dns-digitalocean-doc python-certbot-dns-dnsimple-doc python-certbot-dns-dnsmadeeasy-doc python-certbot-dns-gehirn-doc python-certbot-dns-google-doc python-certbot-dns-linode-doc python-certbot-dns-luadns-doc python-certbot-dns-nsone-doc python-certbot-dns-ovh-doc python-certbot-dns-rfc2136-doc python-certbot-dns-route53-doc python-certbot-dns-sakuracloud-doc python-certbot-doc python3-acme python3-certbot python3-certbot-apache python3-certbot-dns-cloudflare python3-certbot-dns-digitalocean python3-certbot-dns-dnsimple python3-certbot-dns-dnsmadeeasy python3-certbot-dns-gehirn python3-certbot-dns-google python3-certbot-dns-linode python3-certbot-dns-luadns python3-certbot-dns-nsone python3-certbot-dns-ovh python3-certbot-dns-rfc2136 python3-certbot-dns-route53 python3-certbot-dns-sakuracloud python3-certbot-nginx Size: 3.70 MiB Size change: 7.42 KiB Changelog: * Mon Dec 18 2023 Jonathan Wright - 2.8.0-1 - Update to 2.8.0 rhbz#2246252 Package: coccinelle-1.1.1-26.20230624git0afff7f.fc40 Old package: coccinelle-1.1.1-25.20230624git0afff7f.fc40 Summary: Semantic
[Bug 2249049] perl-Eval-Context-0.09.11-32.fc40 FTBFS: Failed test 'Test STDOUT' at t/012_safe.t line 127
https://bugzilla.redhat.com/show_bug.cgi?id=2249049 Fedora Update System changed: What|Removed |Added Fixed In Version||perl-Eval-Context-0.09.11-3 ||3.fc40 Status|MODIFIED|CLOSED Resolution|--- |ERRATA Last Closed||2023-12-19 15:06:15 --- Comment #3 from Fedora Update System --- FEDORA-2023-a57fae73a2 has been pushed to the Fedora 40 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=2249049 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202249049%23c3 -- ___ 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 2249049] perl-Eval-Context-0.09.11-32.fc40 FTBFS: Failed test 'Test STDOUT' at t/012_safe.t line 127
https://bugzilla.redhat.com/show_bug.cgi?id=2249049 Fedora Update System changed: What|Removed |Added Status|NEW |MODIFIED --- Comment #2 from Fedora Update System --- FEDORA-2023-a57fae73a2 has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2023-a57fae73a2 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2249049 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202249049%23c2 -- ___ 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: Mock Configs v39.3 released - DNF5 used for F40+ builds
On Mon, Dec 18, 2023 at 10:08 AM Pavel Raiskup wrote: > > On pátek 1. prosince 2023 15:04:10 CET Pavel Raiskup wrote: > > Hello maintainers! > > > > Let me announce a new release of Mock Core Configs v39.3, aka > > the configuration files for Mock, the chroot build environment manager > > for building RPMs. > > > > The notable change in this release is that we are switching the default > > package_manager from DNF4 to DNF5, according to the F40 change: > > https://fedoraproject.org/wiki/Changes/BuildWithDNF5 > > Full release notes: > >https://rpm-software-management.github.io/mock/Release-Notes-Configs-39.3 > > > > We plan to push this update into Fedora Copr to get some early testing > > next week. Then, depending on the releng team, we might push this into > > Koji soon. The Bodhi updates links are here: > > > > F39 https://bodhi.fedoraproject.org/updates/FEDORA-2023-0a947db1d0 > > F38 https://bodhi.fedoraproject.org/updates/FEDORA-2023-6ef1e12930 > > F37 https://bodhi.fedoraproject.org/updates/FEDORA-2023-cd9c489f40 > > EL9 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-c2c4082053 > > EL8 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-eab5217f46 > > > > Note that we **will not** push these updates into Fedora stable earlier > > than on Monday 2023-12-18 (but very likely we'll wait till the next > > year, depending on the feedback). > > And the push eventually happened, despite that I did not want it to > happen, yet. I probably messed up the Bodhi updates (I thought I > disabled the stable-by-time feature). Sorry, folks. We're now in the weird situation where this update is stable in F38, EPEL9, and EPEL8, but not stable in F39. Since it's already stable on the most stablest branches, can we get it stable in F39 too please? Having the latest and greatest Fedora release lag behind EPEL is weird. Fabio -- ___ 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 2255149] perl-MooseX-Getopt-0.76 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2255149 Fedora Update System changed: What|Removed |Added Resolution|--- |ERRATA Fixed In Version||perl-MooseX-Getopt-0.76-1.f ||c40 Status|MODIFIED|CLOSED Last Closed||2023-12-19 12:03:10 --- Comment #2 from Fedora Update System --- FEDORA-2023-240bf4d960 has been pushed to the Fedora 40 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=2255149 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202255149%23c2 -- ___ 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 2255149] perl-MooseX-Getopt-0.76 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2255149 Fedora Update System changed: What|Removed |Added Status|NEW |MODIFIED --- Comment #1 from Fedora Update System --- FEDORA-2023-240bf4d960 has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2023-240bf4d960 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2255149 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202255149%23c1 -- ___ 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: F40 Change Proposal: Unified Kernel Support Phase Two (System-Wide)
Hi, > > > This is IMHO a mistake, the systemd-boot and UKI paths are the perfect > > > time > > > to break with shim and require some form of actual fedora/whatever secure > > > boot key enrollment on the machine. > > > > This is not going to fly. There are too many cases where you simply > > can't enroll fedora keys, so booting on machines with the MS 3rd party > > certificate enrolled IMHO must continue to work. > > I agree solving this for every possible machine combination is an > intractable problem at the moment. But, the UKI use case, as I understand > it, is a handful of hyperscalers and machines. Well, that is the main focus for now. At the end of the day I think using UKIs is good for all hardware. There are a number of roadblocks to be solved before they will actually work in more complex setups though. For the simple cases (no multiboot, ...) and standard storage (ahci/nvme) the virt UKI does also boot on physical hardware, I have a thinkpad running with it. But even when limiting things to the hyperscalers it doesn't work everywhere. On AWS you can bring your own uefi variable store, with whatever you want in 'db' etc. On Azure you can't. > I'm talking about removing shim from the boot flow. That is not a goal of this change proposal, and it's not up for debate for phase #2. Maybe an option in a later phase, once we have a signed systemd-boot (see below). > The UKI would be signed with the fedora key same as would be done with > shim in the boot path. The fedora public key is itself enrolled in the > UEFI key db alongside the assortment of existing db entries, and the > boot path would be UEFI->UKI. If the 'enroll fedora public key in db' part would be *that* simple shim would not exist in the first place. > > Problem #2 is we don't have a signed system-boot binary. Switching over > > to use systemd-boot when this has changed should be easy. The UKIs are > > already placed in $ESP/EFI/Linux, according to the boot loader spec, > > where systemd-boot would look for them. So the kernel-install workflow > > would need only minor changes. > > I'm not sure that is strictly needed. It'll be useful for multiple reasons, especially if you want make shim optional in the boot chain: (1) systemd-boot already supports secure boot key enrollment in case the machine is in setup mode. (2) It will remove the dependency on shim's fallback.efi (to create BDS entries for the UKIs on first boot). take care, Gerd -- ___ 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
