[Bug 2033196] New: Please branch and build perl-Task-Weaken for EPEL-9
https://bugzilla.redhat.com/show_bug.cgi?id=2033196 Bug ID: 2033196 Summary: Please branch and build perl-Task-Weaken for EPEL-9 Product: Fedora EPEL Version: epel9 Status: NEW Component: perl-Task-Weaken Assignee: si...@sxw.org.uk Reporter: p...@city-fan.org QA Contact: extras...@fedoraproject.org CC: perl-devel@lists.fedoraproject.org, si...@sxw.org.uk Target Milestone: --- Classification: Fedora Could you please branch and build perl-Task-Weaken for EPEL-9 ? If you prefer, you could add me (FAS: pghmcfc) as a committer and I'll do it myself. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2033196 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2032454] perl-UUID-Tiny for EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2032454 Fedora Update System changed: What|Removed |Added Status|ASSIGNED|MODIFIED --- Comment #2 from Fedora Update System --- FEDORA-EPEL-2021-a68006ce1e has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-a68006ce1e -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2032454 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
When is Firefox on Wayland Going to be the Default On KDE
I don't want to run MOZ_ENABLE_WAYLAND=1 firefox from the command line forever. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: I quit packaging
On Wed, Dec 15, 2021 at 09:27:51PM -0700, Orion Poplawski wrote: > On 12/15/21 16:57, Michel Alexandre Salim wrote: > > On Sun, Dec 12, 2021 at 11:03:14PM +0100, Volker Fröhlich wrote: > > > I don't want to be a package maintainer anymore. > > > > > > All of my packages are up for grabs. > > > > > To help people get started, here's the URL: > > https://src.fedoraproject.org/user/volter/projects > > There are two problems here: > > * This shows projects that volter is a part of, not just ones where he is > the main admin (which presumably are the ones we care about) True - sadly this doesn't seem exposed in the web UI. Could be a nice improvement, though I suppose we can already get this via the Pagure API. > > * There is no way from the interface to request taking over the package > unless it is orphaned (but then you wouldn't see the package in this list > presumably if volter orphaned it) > Yeah - though looks like the orphaning hasn't happened. In any case, the packages have been posted in another subthread, I made the mistake of replying while the subthread was collapsed. Cheers, -- Michel Alexandre Salim profile: https://keyoxide.org/mic...@michel-slm.name 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: missing pyproject-rpm-macros component from EPEL (Bugzilla)
On Tue, Dec 14, 2021 at 10:57:14PM +0100, chedi toueiti wrote: > fair enough, will this be also the case for EPEL9? > > On Tue, Dec 14, 2021 at 10:47 PM Adam Williamson > wrote: > > > On Tue, 2021-12-14 at 22:24 +0100, chedi toueiti wrote: > > > I noticed that pyproject-rpm-macros is not listed as a Bugzilla component > > > in the EPEL product. Is there a specific reason for that? If not can > > > someone add it or direct me to the adequate procedure to request it. > > > > It's 'missing' because the package isn't built on EPEL. It's not built > > on EPEL because the EL 7 and EL 8 environments are too old for the > > macros to work. It's not in EPEL9 because it's part of CentOS Stream 9 (and so it will be in RHEL 9): https://gitlab.com/redhat/centos-stream/rpms/pyproject-rpm-macros PS please consider bottom posting: http://www.idallen.com/topposting.html - it makes it easier to follow long threads. Best regards, -- Michel Alexandre Salim profile: https://keyoxide.org/mic...@michel-slm.name 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: I quit packaging
Volker Fröhlich wrote: > I don't want to be a package maintainer anymore. Too bad! Thank you for your contributions so far! Kevin Kofler ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: I quit packaging
Emmanuel Seyman wrote: > * routino That one has actually been maintained by Dan Horák for a while. Volker is/was only co-admin. (I am still co-admin, too. I used to be the primary maintainer, Dan picked it up from me a few years ago.) Kevin Kofler ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: I quit packaging
On 12/15/21 16:57, Michel Alexandre Salim wrote: On Sun, Dec 12, 2021 at 11:03:14PM +0100, Volker Fröhlich wrote: I don't want to be a package maintainer anymore. All of my packages are up for grabs. To help people get started, here's the URL: https://src.fedoraproject.org/user/volter/projects There are two problems here: * This shows projects that volter is a part of, not just ones where he is the main admin (which presumably are the ones we care about) * There is no way from the interface to request taking over the package unless it is orphaned (but then you wouldn't see the package in this list presumably if volter orphaned it) -- Orion Poplawski he/him/his - surely the least important thing about me Manager of NWRA Technical Systems 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane or...@nwra.com Boulder, CO 80301 https://www.nwra.com/ smime.p7s Description: S/MIME Cryptographic 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2032104] perl-IO-Pipely-0.006 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2032104 --- Comment #4 from Fedora Update System --- FEDORA-2021-3018d9bda1 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-3018d9bda1` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-3018d9bda1 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=2032104 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: F36 Change: Enable exclude_from_weak_autodetect by default in LIBDNF (System-Wide Change proposal)
On Friday, December 10, 2021 8:29:10 AM CST Kamil Paral wrote: > Hey Maxwell, > can you please file a new bug in bugzilla against dnf and copy the problem > description into it? Then make your new bug block bug 2013327 [1], which is > the tracker for this Change. This way you'll make sure that this problem > doesn't get lost and the maintainer has to deal with it before the > appropriate Change deadline. Thanks! > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=2013327 > I just did[1]. Thank you for pointing me in the right direction! [1]: https://bugzilla.redhat.com/show_bug.cgi?id=2033130 -- Maxwell G (@gotmax23) Pronouns: He/Him/His PGP Key Fingerprint: f57c76e5a238fe0a628e2ecef79e4e25e8c661f8 PGP Keyserver: hkp://keyserver.ubuntu.com gotmax@e.email signature.asc Description: This is a digitally signed message part. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2032104] perl-IO-Pipely-0.006 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2032104 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #3 from Fedora Update System --- FEDORA-EPEL-2021-00578b3c2c has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-00578b3c2c 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=2032104 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2032872] perl-Safe-Isa for EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2032872 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #3 from Fedora Update System --- FEDORA-EPEL-2021-2453e1c489 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-2453e1c489 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=2032872 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2032261] perl-Math-BigInt-GMP for EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2032261 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #3 from Fedora Update System --- FEDORA-EPEL-2021-b675a4c0f6 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-b675a4c0f6 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=2032261 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2031754] perl-Authen-PAM for EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2031754 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #3 from Fedora Update System --- FEDORA-EPEL-2021-8643de577a has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-8643de577a 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=2031754 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2031819] perl-Test-Output for EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2031819 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #3 from Fedora Update System --- FEDORA-EPEL-2021-f429da3989 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-f429da3989 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=2031819 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2031079] perl-Crypt-DES for EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2031079 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #4 from Fedora Update System --- FEDORA-EPEL-2021-b25c48e97c has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-b25c48e97c 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=2031079 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2031862] Please branch and build perl-Test-File-Contents for EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2031862 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #3 from Fedora Update System --- FEDORA-EPEL-2021-bd33056b63 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-bd33056b63 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=2031862 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2032511] Please branch and build perl-Modern-Perl in epel9
https://bugzilla.redhat.com/show_bug.cgi?id=2032511 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #3 from Fedora Update System --- FEDORA-EPEL-2021-b2a51a5cf3 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-b2a51a5cf3 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=2032511 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2031541] Please branch and build perl-Mail-Sendmail in epel9
https://bugzilla.redhat.com/show_bug.cgi?id=2031541 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #2 from Fedora Update System --- FEDORA-EPEL-2021-9c6e0d2580 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-9c6e0d2580 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=2031541 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2032209] Branch and build perl-Crypt-Cracklib in epel9
https://bugzilla.redhat.com/show_bug.cgi?id=2032209 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #3 from Fedora Update System --- FEDORA-EPEL-2021-6adbee71a8 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-6adbee71a8 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=2032209 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2029201] perl-Net-Amazon-S3-0.99 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2029201 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-Net-Amazon-S3-0.99-1.f |perl-Net-Amazon-S3-0.99-1.f |c36 |c36 ||perl-Net-Amazon-S3-0.99-1.f ||c35 Resolution|--- |ERRATA Status|ON_QA |CLOSED Last Closed||2021-12-16 01:16:41 --- Comment #3 from Fedora Update System --- FEDORA-2021-942138a7e7 has been pushed to the Fedora 35 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=2029201 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2028912] Please branch and build perl-Linux-Inotify2 in epel9
https://bugzilla.redhat.com/show_bug.cgi?id=2028912 Fedora Update System changed: What|Removed |Added Resolution|--- |ERRATA Status|ON_QA |CLOSED Fixed In Version||perl-Linux-Inotify2-2.3-1.e ||l9 Last Closed||2021-12-16 00:21:04 --- Comment #4 from Fedora Update System --- FEDORA-EPEL-2021-98d7654945 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=2028912 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: I quit packaging
On Sun, Dec 12, 2021 at 11:03:14PM +0100, Volker Fröhlich wrote: > I don't want to be a package maintainer anymore. > > All of my packages are up for grabs. > To help people get started, here's the URL: https://src.fedoraproject.org/user/volter/projects -- Michel Alexandre Salim profile: https://keyoxide.org/mic...@michel-slm.name 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2033110] New: perl-IO-Async-0.801 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2033110 Bug ID: 2033110 Summary: perl-IO-Async-0.801 is available Product: Fedora Version: rawhide Status: NEW Component: perl-IO-Async Keywords: FutureFeature, Triaged Assignee: emman...@seyman.fr Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: emman...@seyman.fr, kwiz...@gmail.com, perl-devel@lists.fedoraproject.org Target Milestone: --- Classification: Fedora Latest upstream release: 0.801 Current version/release in rawhide: 0.800-1.fc36 URL: http://search.cpan.org/dist/IO-Async 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://fedoraproject.org/wiki/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/7999/ -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2033110 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Review request to fix FailsToInstall: mingw-qt6-qtshadertools
On Wed, Dec 15, 2021 at 10:58:24PM +0100, Sandro Mani wrote: > Hi > > I'd need mingw-qt6-qtshadertools reviewed: > > https://bugzilla.redhat.com/show_bug.cgi?id=2009221 > > mingw-qt6-qtdeclarative, which is currently FailsToInstall, grew a > dependency on it. > Happy to take this! > Happy to review in exchange! > I'll just hit you up with package ACL requests :) Best, -- Michel Alexandre Salim profile: https://keyoxide.org/mic...@michel-slm.name 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Adjusting python-django to latest Python Packaging Guidelines
On Wed, Dec 15, 2021 at 12:49:51PM -0800, Michel Alexandre Salim wrote: > On Tue, Dec 14, 2021 at 02:29:58PM -0800, Michel Alexandre Salim wrote: > > Hi all, > > > > Neal Gompa and I have been reviving the effort to get our mailing list > > server infrastructure (currently running on RHEL 7 with missing packages > > provided in an unofficial repo) hostable on RHEL 9 + EPEL. > > > > Pagure issue: https://pagure.io/fedora-infrastructure/issue/8455 > > Bugzilla tracker: https://bugzilla.redhat.com/show_bug.cgi?id=2030061 > > Status: https://hackmd.io/Pb9otlVGQHe1r9BIC5bi7w (not fully updated yet) > > > > Any objection if I modernize python-django's spec file so we get > automatic BRs? I accidentally branched python-mock for EPEL9 because > Django BR-ed it, before realizing that it's an out of date BR and the > unit tests all use `from unittest import mock` already > > ref: https://fedoraproject.org/wiki/Changes/DeprecatePythonMock > > python-django without python-mock built for Rawhide: > https://koji.fedoraproject.org/koji/buildinfo?buildID=1867385 > PR: https://src.fedoraproject.org/rpms/python-django/pull-request/20 This now adheres closely to the Python Packaging Guidelines https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/ - automatic BRs - Consistently use pyproject macros As a bonus, it's so much cleaner and we track the directories for localization files better. Provides and Requires are sane (I provided details in the PR comments) I'll leave this open for a couple of days and then merge it if there's no objection. Thanks, -- Michel Alexandre Salim profile: https://keyoxide.org/mic...@michel-slm.name 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: F36 Change: Enable fs-verity in RPM (System-Wide Change proposal)
On Mon, Dec 13, 2021, at 5:21 PM, Tom Stellard wrote: > > Did you test the impact this has on package build times? Particularly > packages like llvm, clang, webkit2gtk3, etc. that have very large > debuginfo files? I think far too often the culture here is "make $change for all RPMs". But this "everything is an RPM" mindset can lead to outcomes and methodology that is at best weird. For e.g. "let's try building with newer gcc", it would seem far better to me to e.g. start with the things that are in Fedora CoreOS or Workstation or whatever. (And, optionally their build dependencies) For *this* particular change, the value of pre-signing the -debug RPMs seems...weak. Or even the `-devel` RPMs. Now, obviously choosing *which* binaries to sign would require some thought. But I think that's worth doing instead of blindly doing everything. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Fedora-Rawhide-20211215.n.0 compose check report
No missing expected images. Compose FAILS proposed Rawhide gating check! 14 of 43 required tests failed, 4 results missing openQA tests matching unsatisfied gating requirements shown with **GATING** below Failed openQA tests: 85/228 (x86_64), 65/159 (aarch64) New failures (same test not failed in Fedora-Rawhide-20211212.n.0): ID: 1086638 Test: x86_64 Server-dvd-iso install_blivet_standard_partition_ext4 URL: https://openqa.fedoraproject.org/tests/1086638 ID: 1086639 Test: x86_64 Server-dvd-iso install_blivet_standard_partition_ext4@uefi URL: https://openqa.fedoraproject.org/tests/1086639 ID: 1086640 Test: x86_64 Server-dvd-iso install_blivet_btrfs_preserve_home_uefi@uefi URL: https://openqa.fedoraproject.org/tests/1086640 ID: 1086641 Test: x86_64 Server-dvd-iso install_btrfs_preserve_home URL: https://openqa.fedoraproject.org/tests/1086641 ID: 1086642 Test: x86_64 Server-dvd-iso install_lvm_ext4@uefi URL: https://openqa.fedoraproject.org/tests/1086642 ID: 1086643 Test: x86_64 Server-dvd-iso install_standard_partition_ext4@uefi URL: https://openqa.fedoraproject.org/tests/1086643 ID: 1086647 Test: x86_64 Server-dvd-iso install_blivet_btrfs_preserve_home URL: https://openqa.fedoraproject.org/tests/1086647 ID: 1086648 Test: x86_64 Server-dvd-iso install_repository_hd_variation URL: https://openqa.fedoraproject.org/tests/1086648 ID: 1086650 Test: x86_64 Server-dvd-iso install_lvm_ext4 URL: https://openqa.fedoraproject.org/tests/1086650 ID: 1086657 Test: x86_64 Server-dvd-iso install_btrfs_preserve_home_uefi@uefi URL: https://openqa.fedoraproject.org/tests/1086657 ID: 1086660 Test: x86_64 Server-dvd-iso install_vnc_server URL: https://openqa.fedoraproject.org/tests/1086660 ID: 1086662 Test: x86_64 Server-dvd-iso install_standard_partition_ext4 URL: https://openqa.fedoraproject.org/tests/1086662 ID: 1086665 Test: x86_64 Server-dvd-iso server_role_deploy_domain_controller **GATING** URL: https://openqa.fedoraproject.org/tests/1086665 ID: 108 Test: x86_64 Server-dvd-iso support_server URL: https://openqa.fedoraproject.org/tests/108 ID: 1086667 Test: x86_64 Server-dvd-iso install_blivet_lvm_ext4 URL: https://openqa.fedoraproject.org/tests/1086667 ID: 1086668 Test: x86_64 Server-dvd-iso install_blivet_lvm_ext4@uefi URL: https://openqa.fedoraproject.org/tests/1086668 ID: 1086669 Test: x86_64 Server-dvd-iso install_repository_nfsiso_variation URL: https://openqa.fedoraproject.org/tests/1086669 ID: 1086678 Test: x86_64 Server-dvd-iso install_vncconnect_server URL: https://openqa.fedoraproject.org/tests/1086678 ID: 1086679 Test: x86_64 Server-dvd-iso install_updates_nfs URL: https://openqa.fedoraproject.org/tests/1086679 ID: 1086684 Test: x86_64 Server-dvd-iso install_repository_nfs_graphical URL: https://openqa.fedoraproject.org/tests/1086684 ID: 1086685 Test: x86_64 Server-dvd-iso install_repository_nfs_variation URL: https://openqa.fedoraproject.org/tests/1086685 ID: 1086689 Test: x86_64 Server-dvd-iso server_realmd_join_kickstart **GATING** URL: https://openqa.fedoraproject.org/tests/1086689 ID: 1086695 Test: x86_64 Workstation-live-iso anaconda_help URL: https://openqa.fedoraproject.org/tests/1086695 ID: 1086696 Test: x86_64 Workstation-live-iso desktop_notifications_live URL: https://openqa.fedoraproject.org/tests/1086696 ID: 1086754 Test: x86_64 Silverblue-dvd_ostree-iso release_identification URL: https://openqa.fedoraproject.org/tests/1086754 ID: 1086756 Test: x86_64 Cloud_Base-qcow2-qcow2 base_reboot_unmount URL: https://openqa.fedoraproject.org/tests/1086756 ID: 1086757 Test: x86_64 Cloud_Base-qcow2-qcow2 base_reboot_unmount@uefi URL: https://openqa.fedoraproject.org/tests/1086757 ID: 1086758 Test: x86_64 Cloud_Base-qcow2-qcow2 base_system_logging@uefi URL: https://openqa.fedoraproject.org/tests/1086758 ID: 1086759 Test: x86_64 Cloud_Base-qcow2-qcow2 base_update_cli@uefi URL: https://openqa.fedoraproject.org/tests/1086759 ID: 1086760 Test: x86_64 Cloud_Base-qcow2-qcow2 base_package_install_remove@uefi URL: https://openqa.fedoraproject.org/tests/1086760 ID: 1086761 Test: x86_64 Cloud_Base-qcow2-qcow2 base_service_manipulation@uefi URL: https://openqa.fedoraproject.org/tests/1086761 ID: 1086762 Test: x86_64 Cloud_Base-qcow2-qcow2 base_services_start URL: https://openqa.fedoraproject.org/tests/1086762 ID: 1086763 Test: x86_64 Cloud_Base-qcow2-qcow2 base_services_start@uefi URL: https://openqa.fedoraproject.org/tests/1086763 ID: 1086764 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi **GATING** URL: https://openqa.fedoraproject.org/tests/1086764 ID: 1086765 Test: x86_64 Cloud_Base-qcow2-qcow2 base_selinux@uefi URL: https://openqa.fedoraproject.org/tests/1086765 ID: 1086777 Test: aarch64 Server-dvd-iso install_blivet_lvm_ext4@uefi URL: https://openqa.fedoraproject.org/tests/1086777 ID: 1086779 Test: aarch64 Server-dvd-iso
Re: F36 Change: Enable fs-verity in RPM (System-Wide Change proposal)
On Wed, Dec 15, 2021, at 1:45 PM, Luca Boccassi wrote: >> On Fri, Dec 10, 2021 at 10:47:52AM +0100, Vít Ondruch wrote: >> >> Any file covered by fs-verity is immutable after installation. So you >> cannot modify the contents, the kernel refuses. But you can just >> replace the file (like during an upgrade), and of course copy and edit >> in a different location. If replaced, no fs-verity checking is done >> any more by the kernel. There was some talk about high-level solution >> to prevent such files from being executed, e.g. an LSM module, but no >> details... (Thinking about this, it would be pretty hard, because the >> LSM would need to be smart enough to know which files are installed >> through rpm, and which files are not. I would love to hear more details >> about what is planned here.) >> >> Zbyszek > > There is such an LSM that supports fs-verity (and dm-verity), being > reviewed right now: IPE > > https://lore.kernel.org/lkml/81d5e825-1ee2-8f6b-cd9d-07b0f8bd3...@linux.microsoft.com/T/ > https://microsoft.github.io/ipe/ Hmm. Some interesting stuff going on there but I would have started with a new SELinux access vector. That'd allow fine-grained constraints, e.g. disallowing `init_t` but allowing `unconfined_service_t`. Possibly also landlock should be able to hook into this. IOW it's not clear to me that a new LSM is the best thing for the ecosystem here. But bigger picture I'd agree that fs-verity is significantly stronger when coupled with such a policy - strong enough to block exploits like the runc one: https://unit42.paloaltonetworks.com/breaking-docker-via-runc-explaining-cve-2019-5736/ (Of course that one was *also* stopped by ostree's default read-only bind mount, which I keep saying is not really primarily about security, but hey it worked there) I said this about the IMA-for-Fedora proposal too - to me the approach of "sign all the RPMs" is not a good idea. Instead the focus should be on ensuring the capability works, and is usable from tools to build custom systems. And this of course runs into a bigger picture question of whether we should emphasize the entry point into Fedora being Anaconda/FCOS like (provision and configure a "pre-built" system) or more like Image Builder and tools like that. I think the answer has to be "we do both" really - it's just hard. ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Packaging pgAdmin4
Hi, if the packages is using yarn, you can simply use its caching mechanism for bundling the needed node modules. You will have an offline cache where you can install the modules from! Example: https://src.fedoraproject.org/rpms/nodejs-bash-language-server Take a look at prepare_vendor.sh which creates a tarball with the yarn cache for you. Thanks! Sandro ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2032104] perl-IO-Pipely-0.006 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2032104 Fedora Update System changed: What|Removed |Added Status|ASSIGNED|MODIFIED --- Comment #1 from Fedora Update System --- FEDORA-EPEL-2021-00578b3c2c has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-00578b3c2c -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2032104 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Review request to fix FailsToInstall: mingw-qt6-qtshadertools
Hi I'd need mingw-qt6-qtshadertools reviewed: https://bugzilla.redhat.com/show_bug.cgi?id=2009221 mingw-qt6-qtdeclarative, which is currently FailsToInstall, grew a dependency on it. Happy to review in exchange! Sandro ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: The great Mailman 3 / Hyperkitty upgrade: bumping flufl-lock and mistune?
On Wed, Dec 15, 2021 at 10:26 PM Michel Alexandre Salim < sali...@fedoraproject.org> wrote: > On Wed, Dec 15, 2021 at 10:20:27PM +0100, Charalampos Stratakis wrote: > > On Wed, Dec 15, 2021 at 10:03 PM Miro Hrončok > wrote: > > > > > On 15. 12. 21 21:49, Michel Alexandre Salim wrote: > > > > (I haven't built python-mock in EPEL9 yet, and am not going to > unless we > > > > really need it for something - but I'll hold off on retiring the > branch) > > > > > > Please, retire it for EPEL9. It should never be needed. > > > > > > > > Unfortunately it's quite possible something might need it as there are > > still a lot of packages relying on the external mock. > > > True, but we probably should patch these going forward? I'm happy to > help. I wonder how many of those will turn out to be obsolete BRs too. > > > I would keep the branch but defer building it for now. > > > Argh, too late, but unretiring is easy anyway. > > No worries, I agree patching the imports out is a better solution IMHO. > Regards, > > -- > Michel Alexandre Salim > profile: https://keyoxide.org/mic...@michel-slm.name > ___ > 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 on the list, report it: > https://pagure.io/fedora-infrastructure > -- Regards, Charalampos Stratakis Senior Software Engineer Python Maintenance Team, Red Hat ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: The great Mailman 3 / Hyperkitty upgrade: bumping flufl-lock and mistune?
On Wed, Dec 15, 2021 at 10:26 PM Michel Alexandre Salim < sali...@fedoraproject.org> wrote: > On Wed, Dec 15, 2021 at 10:20:27PM +0100, Charalampos Stratakis wrote: > > On Wed, Dec 15, 2021 at 10:03 PM Miro Hrončok > wrote: > > > > > On 15. 12. 21 21:49, Michel Alexandre Salim wrote: > > > > (I haven't built python-mock in EPEL9 yet, and am not going to > unless we > > > > really need it for something - but I'll hold off on retiring the > branch) > > > > > > Please, retire it for EPEL9. It should never be needed. > > > > > > > > Unfortunately it's quite possible something might need it as there are > > still a lot of packages relying on the external mock. > > > True, but we probably should patch these going forward? I'm happy to > help. I wonder how many of those will turn out to be obsolete BRs too. > > > I would keep the branch but defer building it for now. > > > Argh, too late, but unretiring is easy anyway. > > No worries, I agree patching the imports out is a better solution IMHO. > Regards, > > -- > Michel Alexandre Salim > profile: https://keyoxide.org/mic...@michel-slm.name > ___ > devel mailing list -- de...@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/de...@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > -- Regards, Charalampos Stratakis Senior Software Engineer Python Maintenance Team, Red Hat ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: The great Mailman 3 / Hyperkitty upgrade: bumping flufl-lock and mistune?
On Wed, Dec 15, 2021 at 10:20:27PM +0100, Charalampos Stratakis wrote: > On Wed, Dec 15, 2021 at 10:03 PM Miro Hrončok wrote: > > > On 15. 12. 21 21:49, Michel Alexandre Salim wrote: > > > (I haven't built python-mock in EPEL9 yet, and am not going to unless we > > > really need it for something - but I'll hold off on retiring the branch) > > > > Please, retire it for EPEL9. It should never be needed. > > > > > Unfortunately it's quite possible something might need it as there are > still a lot of packages relying on the external mock. > True, but we probably should patch these going forward? I'm happy to help. I wonder how many of those will turn out to be obsolete BRs too. > I would keep the branch but defer building it for now. > Argh, too late, but unretiring is easy anyway. Regards, -- Michel Alexandre Salim profile: https://keyoxide.org/mic...@michel-slm.name signature.asc Description: PGP signature ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: The great Mailman 3 / Hyperkitty upgrade: bumping flufl-lock and mistune?
On Wed, Dec 15, 2021 at 10:20:27PM +0100, Charalampos Stratakis wrote: > On Wed, Dec 15, 2021 at 10:03 PM Miro Hrončok wrote: > > > On 15. 12. 21 21:49, Michel Alexandre Salim wrote: > > > (I haven't built python-mock in EPEL9 yet, and am not going to unless we > > > really need it for something - but I'll hold off on retiring the branch) > > > > Please, retire it for EPEL9. It should never be needed. > > > > > Unfortunately it's quite possible something might need it as there are > still a lot of packages relying on the external mock. > True, but we probably should patch these going forward? I'm happy to help. I wonder how many of those will turn out to be obsolete BRs too. > I would keep the branch but defer building it for now. > Argh, too late, but unretiring is easy anyway. Regards, -- Michel Alexandre Salim profile: https://keyoxide.org/mic...@michel-slm.name 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2032104] perl-IO-Pipely-0.006 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2032104 Denis Fateyev changed: What|Removed |Added Assignee|jples...@redhat.com |de...@fateyev.com 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=2032104 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: The great Mailman 3 / Hyperkitty upgrade: bumping flufl-lock and mistune?
On Wed, Dec 15, 2021 at 10:03:29PM +0100, Miro Hrončok wrote: > On 15. 12. 21 21:49, Michel Alexandre Salim wrote: > > (I haven't built python-mock in EPEL9 yet, and am not going to unless we > > really need it for something - but I'll hold off on retiring the branch) > > Please, retire it for EPEL9. It should never be needed. > Done, sorry for the noise https://src.fedoraproject.org/rpms/python-mock/blob/9cca66d7e2b5ac0784e160e02383807991890f5c/f/dead.package Thanks, -- Michel Alexandre Salim profile: https://keyoxide.org/mic...@michel-slm.name 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: The great Mailman 3 / Hyperkitty upgrade: bumping flufl-lock and mistune?
On Wed, Dec 15, 2021 at 10:03 PM Miro Hrončok wrote: > On 15. 12. 21 21:49, Michel Alexandre Salim wrote: > > (I haven't built python-mock in EPEL9 yet, and am not going to unless we > > really need it for something - but I'll hold off on retiring the branch) > > Please, retire it for EPEL9. It should never be needed. > > Unfortunately it's quite possible something might need it as there are still a lot of packages relying on the external mock. I would keep the branch but defer building it for now. > -- > 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 on the list, report it: > https://pagure.io/fedora-infrastructure > -- Regards, Charalampos Stratakis Senior Software Engineer Python Maintenance Team, Red Hat ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: The great Mailman 3 / Hyperkitty upgrade: bumping flufl-lock and mistune?
On Wed, Dec 15, 2021 at 10:03 PM Miro Hrončok wrote: > On 15. 12. 21 21:49, Michel Alexandre Salim wrote: > > (I haven't built python-mock in EPEL9 yet, and am not going to unless we > > really need it for something - but I'll hold off on retiring the branch) > > Please, retire it for EPEL9. It should never be needed. > > Unfortunately it's quite possible something might need it as there are still a lot of packages relying on the external mock. I would keep the branch but defer building it for now. > -- > Miro Hrončok > -- > Phone: +420777974800 > IRC: mhroncok > ___ > devel mailing list -- de...@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/de...@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > -- Regards, Charalampos Stratakis Senior Software Engineer Python Maintenance Team, Red Hat ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: The great Mailman 3 / Hyperkitty upgrade: bumping flufl-lock and mistune?
On 15. 12. 21 21:49, Michel Alexandre Salim wrote: (I haven't built python-mock in EPEL9 yet, and am not going to unless we really need it for something - but I'll hold off on retiring the branch) Please, retire it for EPEL9. It should never be needed. -- 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: The great Mailman 3 / Hyperkitty upgrade: bumping flufl-lock and mistune?
On Tue, Dec 14, 2021 at 02:29:58PM -0800, Michel Alexandre Salim wrote: > Hi all, > > Neal Gompa and I have been reviving the effort to get our mailing list > server infrastructure (currently running on RHEL 7 with missing packages > provided in an unofficial repo) hostable on RHEL 9 + EPEL. > > Pagure issue: https://pagure.io/fedora-infrastructure/issue/8455 > Bugzilla tracker: https://bugzilla.redhat.com/show_bug.cgi?id=2030061 > Status: https://hackmd.io/Pb9otlVGQHe1r9BIC5bi7w (not fully updated yet) > Any objection if I modernize python-django's spec file so we get automatic BRs? I accidentally branched python-mock for EPEL9 because Django BR-ed it, before realizing that it's an out of date BR and the unit tests all use `from unittest import mock` already ref: https://fedoraproject.org/wiki/Changes/DeprecatePythonMock python-django without python-mock built for Rawhide: https://koji.fedoraproject.org/koji/buildinfo?buildID=1867385 (I haven't built python-mock in EPEL9 yet, and am not going to unless we really need it for something - but I'll hold off on retiring the branch) Thanks, -- Michel Alexandre Salim profile: https://keyoxide.org/mic...@michel-slm.name signature.asc Description: PGP signature ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: The great Mailman 3 / Hyperkitty upgrade: bumping flufl-lock and mistune?
On Tue, Dec 14, 2021 at 02:29:58PM -0800, Michel Alexandre Salim wrote: > Hi all, > > Neal Gompa and I have been reviving the effort to get our mailing list > server infrastructure (currently running on RHEL 7 with missing packages > provided in an unofficial repo) hostable on RHEL 9 + EPEL. > > Pagure issue: https://pagure.io/fedora-infrastructure/issue/8455 > Bugzilla tracker: https://bugzilla.redhat.com/show_bug.cgi?id=2030061 > Status: https://hackmd.io/Pb9otlVGQHe1r9BIC5bi7w (not fully updated yet) > Any objection if I modernize python-django's spec file so we get automatic BRs? I accidentally branched python-mock for EPEL9 because Django BR-ed it, before realizing that it's an out of date BR and the unit tests all use `from unittest import mock` already ref: https://fedoraproject.org/wiki/Changes/DeprecatePythonMock python-django without python-mock built for Rawhide: https://koji.fedoraproject.org/koji/buildinfo?buildID=1867385 (I haven't built python-mock in EPEL9 yet, and am not going to unless we really need it for something - but I'll hold off on retiring the branch) Thanks, -- Michel Alexandre Salim profile: https://keyoxide.org/mic...@michel-slm.name 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 on the list, report it: https://pagure.io/fedora-infrastructure
Fedora rawhide compose report: 20211215.n.0 changes
OLD: Fedora-Rawhide-20211212.n.0 NEW: Fedora-Rawhide-20211215.n.0 = SUMMARY = Added images:8 Dropped images: 2 Added packages: 23 Dropped packages:47 Upgraded packages: 235 Downgraded packages: 0 Size of added packages: 26.64 MiB Size of dropped packages:214.74 MiB Size of upgraded packages: 18.49 GiB Size of downgraded packages: 0 B Size change of upgraded packages: -5.44 MiB Size change of downgraded packages: 0 B = ADDED IMAGES = Image: Container_Minimal_Base docker ppc64le Path: Container/ppc64le/images/Fedora-Container-Minimal-Base-Rawhide-20211215.n.0.ppc64le.tar.xz Image: Container_Minimal_Base docker x86_64 Path: Container/x86_64/images/Fedora-Container-Minimal-Base-Rawhide-20211215.n.0.x86_64.tar.xz Image: Scientific_KDE live x86_64 Path: Labs/x86_64/iso/Fedora-Scientific_KDE-Live-x86_64-Rawhide-20211215.n.0.iso Image: Scientific vagrant-virtualbox x86_64 Path: Labs/x86_64/images/Fedora-Scientific-Vagrant-Rawhide-20211215.n.0.x86_64.vagrant-virtualbox.box Image: Container_Minimal_Base docker armhfp Path: Container/armhfp/images/Fedora-Container-Minimal-Base-Rawhide-20211215.n.0.armhfp.tar.xz Image: Security live x86_64 Path: Labs/x86_64/iso/Fedora-Security-Live-x86_64-Rawhide-20211215.n.0.iso Image: Container_Minimal_Base docker aarch64 Path: Container/aarch64/images/Fedora-Container-Minimal-Base-Rawhide-20211215.n.0.aarch64.tar.xz Image: Scientific vagrant-libvirt x86_64 Path: Labs/x86_64/images/Fedora-Scientific-Vagrant-Rawhide-20211215.n.0.x86_64.vagrant-libvirt.box = DROPPED IMAGES = Image: Container_Base docker s390x Path: Container/s390x/images/Fedora-Container-Base-Rawhide-20211212.n.0.s390x.tar.xz Image: Design_suite live x86_64 Path: Labs/x86_64/iso/Fedora-Design_suite-Live-x86_64-Rawhide-20211212.n.0.iso = ADDED PACKAGES = Package: golang-github-cli-oauth-0.9.0-1.fc36 Summary: Library for performing OAuth Device and Web application flow RPMs:golang-github-cli-oauth-devel Size:22.01 KiB Package: golang-github-letsencrypt-pebble-2.3.1-3.fc36 Summary: Pebble is a miniature version of Boulder, a small RFC 8555 ACME test server RPMs:golang-github-letsencrypt-pebble golang-github-letsencrypt-pebble-devel Size:14.65 MiB Package: ocaml-logs-0.7.0-1.fc36 Summary: Logging infrastructure for OCaml RPMs:ocaml-logs ocaml-logs-devel Size:1.71 MiB Package: ocaml-rresult-0.7.0-1.fc36 Summary: Result value combinators for OCaml RPMs:ocaml-rresult ocaml-rresult-devel Size:686.53 KiB Package: ocaml-version-3.4.0-1.fc36 Summary: Manipulate, parse and generate OCaml compiler version strings RPMs:ocaml-version ocaml-version-devel Size:1.20 MiB Package: php-composer-pcre-1.0.0-1.fc36 Summary: PCRE wrapping library version 1 RPMs:php-composer-pcre Size:15.21 KiB Package: python-aiosignal-1.2.0-1.fc36 Summary: List of registered asynchronous callbacks RPMs:python-aiosignal-doc python3-aiosignal Size:181.35 KiB Package: python-aws-sam-translator-1.42.0-1.fc36 Summary: Transform SAM templates into AWS CloudFormation templates RPMs:python-aws-sam-translator-doc python3-aws-sam-translator Size:566.41 KiB Package: python-django-picklefield-3.0.1-2.fc36 Summary: A multiprocessing distributed task queue for Django RPMs:python3-django-picklefield Size:20.32 KiB Package: python-django-q-1.3.9-2.fc36 Summary: A multiprocessing distributed task queue for Django RPMs:python3-django-q Size:149.76 KiB Package: python-dotmap-1.3.26-1.fc36 Summary: Dot access dictionary with dynamic hierarchy creation and ordered iteration RPMs:python3-dotmap Size:30.27 KiB Package: python-frozenlist-1.2.0-1.fc36 Summary: List-like structure which can be made immutable RPMs:python-frozenlist-doc python3-frozenlist Size:378.98 KiB Package: python-hyperkitty-1.3.5-1.fc36 Summary: A web interface to access GNU Mailman v3 archives RPMs:hyperkitty hyperkitty-doc Size:1.93 MiB Package: python-ibm-cloud-sdk-core-3.13.2-2.fc36 Summary: Core library used by SDKs for IBM Cloud Services RPMs:python3-ibm-cloud-sdk-core Size:63.12 KiB Package: python-robot-detection-0.4-1.fc36 Summary: Library for detecting bot HTTP UA headers RPMs:python3-robot-detection Size:30.57 KiB Package: rust-actix-web-3.3.2-4.fc36 Summary: Powerful, pragmatic, and extremely fast web framework for Rust RPMs:rust-actix-web+compress-devel rust-actix-web+default-devel rust-actix-web+open-ssl-devel rust-actix-web+openssl-devel rust-actix-web+secure-cookies-devel rust-actix-web-devel Size:155.51 KiB Package: rust-awc-2.0.3-3.fc36 Summary: Async HTTP client library that uses the Actix runtime RPMs:rust-awc+compress-devel rust-awc+default-devel rust-awc+open-ssl-devel rust-awc+openssl-devel rust-awc-devel Size:74.94 KiB Package: rust-base64ct-1.3.0-1.fc36 Summary: Pure Rust, constant-time implementation of Base64 (RFC 4648) RPMs:rust-base64ct+alloc
[Bug 2033073] New: Please branch and build perl-Test-MemoryGrowth for EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2033073 Bug ID: 2033073 Summary: Please branch and build perl-Test-MemoryGrowth for EPEL 9 Product: Fedora EPEL Version: epel9 Status: NEW Component: perl-Test-MemoryGrowth Assignee: jples...@redhat.com Reporter: p...@city-fan.org QA Contact: extras...@fedoraproject.org CC: jples...@redhat.com, perl-devel@lists.fedoraproject.org Target Milestone: --- Classification: Fedora Could you please branch and build perl-Test-MemoryGrowth for EPEL 9 ? If you like you could add me (FAS: pghmcfc) as a committer to the package and I'll do it myself. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2033073 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2033063] New: [RFE:EPEL9] EPEL9 branch for perl-Test-Kwalitee
https://bugzilla.redhat.com/show_bug.cgi?id=2033063 Bug ID: 2033063 Summary: [RFE:EPEL9] EPEL9 branch for perl-Test-Kwalitee Product: Fedora EPEL Version: epel9 Status: NEW Component: perl-Test-Kwalitee Assignee: p...@city-fan.org Reporter: riehe...@fnal.gov QA Contact: extras...@fedoraproject.org CC: p...@city-fan.org, perl-devel@lists.fedoraproject.org Target Milestone: --- Classification: Fedora Can you please branch and build perl-test-Kwalitee in epel9? -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2033063 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2032872] perl-Safe-Isa for EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2032872 Fedora Update System changed: What|Removed |Added Status|ASSIGNED|MODIFIED --- Comment #2 from Fedora Update System --- FEDORA-EPEL-2021-2453e1c489 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-2453e1c489 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2032872 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Request for sponsorship in fedora-contributor group
On Wed, Dec 15, 2021 at 09:27:42AM +, Roberto Sassu via devel wrote: > Hello everyone > > I have done some work in the integrity subsystem, called > Digest Lists Integrity Module (DIGLIM). > > It simplifies the effort necessary to do IMA appraisal, by > reusing the digests included in the header of existing > RPM packages as reference values. It wouldn't require > any change in the building infrastructure. > > It also provides an alternative way of attesting systems, > by keeping the TPM PCR extended with software > measurements, stable and predictable. The main benefit > is the ability to seal a TPM key to the desired software > configuration, so that a TLS secure communication can > be established when only software from installed RPMs > is executed. It would be possible to integrate this solution > in Keylime. > > I have proposed this feature for upstream inclusion: > > https://lore.kernel.org/linux-integrity/20210914163401.864635-1-roberto.sa...@huawei.com/ > > I also rebuilt the Fedora kernel in copr, with DIGLIM: > > https://copr.fedorainfracloud.org/coprs/robertosassu/DIGLIM/ > > You can find the instructions about how to use it here: > > https://lore.kernel.org/linux-integrity/48cd737c504d45208377daa27d625...@huawei.com/ > > I would like to join one of your subgroups, for example > fedora-contributor, so that I can propose a new feature > for Fedora 36/37. You don't need any particular group membership to propose changes. :) https://docs.fedoraproject.org/en-US/program_management/changes_policy/ Of course being a fedora packager is useful if your change involves updates/changes to packages, but you could submit them as PR's and convince existing maintainers to merge them. kevin signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2031079] perl-Crypt-DES for EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2031079 Fedora Update System changed: What|Removed |Added Status|ASSIGNED|MODIFIED --- Comment #3 from Fedora Update System --- FEDORA-EPEL-2021-b25c48e97c has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-b25c48e97c -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2031079 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Re: Requesting branches for epel9
On Wed, Dec 15, 2021 at 05:46:18PM +0100, Miroslav Suchý wrote: > Dne 14. 12. 21 v 17:12 Matthew Miller napsal(a): > > > > But it seems like "request an EPEL branch" should generally be either > > > > "Okay! > > > > Doing that automatically now" or "Oh, this is in EL, sorry"*. What are > > > > the > > > > other cases? > > > As far as I know this isn't about requesting EPEL branches, as much as > > > requesting any branches by hand. If I add something to Fedora rawhide > > > and then ask for a F34 branch, the same issues can happen. Remember > > > our build infrastructure is a pile of band-aids on top of duct tape on > > > top of bungee cords. Lots of tools are written for a toolchain which > > > existed years ago and have been hacked to make it work with whatever > > > new initiative that comes into play. 'Unexpected' side effects and > > > corner cases happen all the time and the fixing of them tends to add > > > new ones. > > Sure. But also, asking people to spend a lot of their time running > > grunt-work tasks means that they have less time to fix when things break, > > let alone re-engineer away some of that tech debt. It seems like we should > > be able to automate the simple cases (adding F34 and F35 branches should be > > even easier, since we don't have the "is it in EL?" question even). > > *nod* > > So ... the question is how can I help? Can you document the check-list? I > volunteer to start writing the script. So, I suspect the epel-devel list isn't really the place to discuss this (I would think devel list + direct engagement with releng folks). That said, fedscm-admin _does_ do a bunch of checks currently. For branch requests for existing packages it checks that the requestor is a maintainer of that package and then just auto approves it. Those requests could potentially be automated (we have talked about it in releng land, but it's also a bit difficult due to all the perms you have to have). For new packages it does a bunch of checks like 'is the reviewer in the packager group', did the reviewer set 'fedora-review: +', are the requested branches valid, etc, etc https://pagure.io/fedscm-admin/blob/main/f/fedscm_admin/utils.py#_285 I can't speak for the current folks doing the processing, but I did this for 3-4 years a long time ago. When I did it I looked for a lot of things it was hard to automate checks for, like "Did this review check list a bunch of things, or just say 'ok, approved'". I would typically look closely at those and find things that were missed. I also recall several reviews that I blocked due to legal reasons where the reviewer didn't understand things correctly. That said, the volume of new packages is pretty high these days so I don't know how much extra scrutiny they are really getting. Perhaps it's time to just completely automate it and have better ways to clean up if something bad gets in. kevin signature.asc Description: PGP signature ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
License update: svummvm-tools
Hello, beginning with version 2.5.0, the license for the package scummvm-tools has been changed to "GPLv2+ and LGPLv2+ and MIT" Best regards, Christian ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Test-Announce] Fedora 36 Rawhide 20211215.n.0 nightly compose nominated for testing
Announcing the creation of a new nightly release validation test event for Fedora 36 Rawhide 20211215.n.0. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan Notable package version changes: lorax - 20211210.n.0: lorax-36.3-1.fc36.src, 20211215.n.0: lorax-36.4-1.fc36.src Test coverage information for the current release can be seen at: https://openqa.fedoraproject.org/testcase_stats/36 You can see all results, find testing instructions and image download locations, and enter results on the Summary page: https://fedoraproject.org/wiki/Test_Results:Fedora_36_Rawhide_20211215.n.0_Summary The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_36_Rawhide_20211215.n.0_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_36_Rawhide_20211215.n.0_Base https://fedoraproject.org/wiki/Test_Results:Fedora_36_Rawhide_20211215.n.0_Server https://fedoraproject.org/wiki/Test_Results:Fedora_36_Rawhide_20211215.n.0_Cloud https://fedoraproject.org/wiki/Test_Results:Fedora_36_Rawhide_20211215.n.0_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_36_Rawhide_20211215.n.0_Security_Lab Thank you for testing! -- Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: F36 Change: Enable fs-verity in RPM (System-Wide Change proposal)
> We don't have a proof of concept for the LSM module. I agree with you that in > practice > it would probably need to implement some kind of "list of files we care > about", > but I do not have an intelligent opinion about that. > > Based on Roberto's comment in a different sub-thread, there could be some > ongoing work > integrating with IMA that might be past the hypothetical stage? IPE supports fs-verity and dm-verity, and allows to write a policy such as "only allow execution of binaries/libraries from fs-verity verified files or dm-verity verified volumes): https://lore.kernel.org/lkml/81d5e825-1ee2-8f6b-cd9d-07b0f8bd3...@linux.microsoft.com/T/ https://microsoft.github.io/ipe/ ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: F36 Change: Enable fs-verity in RPM (System-Wide Change proposal)
> On Fri, Dec 10, 2021 at 10:47:52AM +0100, Vít Ondruch wrote: > > Any file covered by fs-verity is immutable after installation. So you > cannot modify the contents, the kernel refuses. But you can just > replace the file (like during an upgrade), and of course copy and edit > in a different location. If replaced, no fs-verity checking is done > any more by the kernel. There was some talk about high-level solution > to prevent such files from being executed, e.g. an LSM module, but no > details... (Thinking about this, it would be pretty hard, because the > LSM would need to be smart enough to know which files are installed > through rpm, and which files are not. I would love to hear more details > about what is planned here.) > > Zbyszek There is such an LSM that supports fs-verity (and dm-verity), being reviewed right now: IPE https://lore.kernel.org/lkml/81d5e825-1ee2-8f6b-cd9d-07b0f8bd3...@linux.microsoft.com/T/ https://microsoft.github.io/ipe/ ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2031541] Please branch and build perl-Mail-Sendmail in epel9
https://bugzilla.redhat.com/show_bug.cgi?id=2031541 Fedora Update System changed: What|Removed |Added Status|NEW |MODIFIED --- Comment #1 from Fedora Update System --- FEDORA-EPEL-2021-9c6e0d2580 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-9c6e0d2580 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2031541 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Fedora CoreOS Meeting Minutes 2021-12-15
Minutes: https://meetbot.fedoraproject.org/fedora-meeting-1/2021-12-15/fedora_coreos_meeting.2021-12-15-16.28.html Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting-1/2021-12-15/fedora_coreos_meeting.2021-12-15-16.28.txt Log: https://meetbot.fedoraproject.org/fedora-meeting-1/2021-12-15/fedora_coreos_meeting.2021-12-15-16.28.log.html #fedora-meeting-1: fedora_coreos_meeting Meeting started by dustymabe at 16:28:23 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2021-12-15/fedora_coreos_meeting.2021-12-15-16.28.log.html . Meeting summary --- * roll call (dustymabe, 16:28:27) * Action items from last meeting (dustymabe, 16:34:40) * meetings over the next few weeks (dustymabe, 16:35:22) * we won't hold our Wednesday meeting on 12/22/21 and 12/29/21. (dustymabe, 16:35:27) * networking: consider the effects of BOOTIF kernel argument on nm-initrd-generator (dustymabe, 16:37:45) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1048 (dustymabe, 16:37:52) * Fedora CoreOS images should support discoverable partitions (dustymabe, 16:44:10) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1038 (dustymabe, 16:44:14) * LINK: https://github.com/coreos/coreos-assembler/blob/main/src/create_disk.sh#L126-L171 (dustymabe, 16:52:00) * AGREED: While we don't see a lot of immediate value in changing the partition type UUIDs we don't currently know of anything consuming the ones we do set. Switching them to match the Discoverable Partitions Specification is not something we're opposed to and may be worth it if other tools start to use this information when inspecting disk images. We need to consult for more expertise on (dustymabe, 17:12:15) * Add AWS Systems Manager parameters for Fedora CoreOS images (dustymabe, 17:12:33) * LINK: https://github.com/coreos/fedora-coreos-tracker/issues/636 (dustymabe, 17:12:38) * AGREED: This sounds like a nice addition to our offering. (dustymabe, 17:26:04) * Open Floor (dustymabe, 17:26:11) Meeting ended at 17:35:14 UTC. Action Items Action Items, by person --- * **UNASSIGNED** * (none) People Present (lines said) --- * dustymabe (101) * jlebon (38) * zodbot (22) * nemric (16) * lucab (13) * travier (4) * saqali (2) * jmarrero (1) * skunkerk (1) * walters (1) * miabbott (1) * ravanelli (1) Generated by `MeetBot`_ 0.4 .. _`MeetBot`: https://fedoraproject.org/wiki/Zodbot#Meeting_Functions ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: The great Mailman 3 / Hyperkitty upgrade: bumping flufl-lock and mistune?
On Tue, Dec 14, 2021 at 05:21:43PM -0800, Michel Alexandre Salim wrote: > On Tue, Dec 14, 2021 at 05:50:46PM -0500, Elliott Sales de Andrade wrote: > > > > > > ❯ sudo dnf repoquery --enablerepo=fedora-source,rawhide,rawhide-source > > > --whatrequires python3-flufl-lock > > > mailman3-0:3.3.4-5.fc35.noarch > > > mailman3-0:3.3.4-5.fc35.src > > > mailman3-0:3.3.4-5.fc36.noarch > > > mailman3-0:3.3.4-5.fc36.src > > > odcs-0:0.3.4-6.fc35.noarch > > > odcs-0:0.3.4-6.fc35.src > > > odcs-0:0.3.4-6.fc36.noarch > > > odcs-0:0.3.4-6.fc36.src > > > python-cartopy-0:0.20.0-1.fc35.src > > > python-cartopy-0:0.20.1-2.fc36.src > > > > > > > Cartopy only needs flufl-lock to run tests. I suppose since those are > > installed, it could also have a runtime dependency, but it'd be > > largely unused, and anyway Cartopy won't need it at all after the next > > minor release. > Thanks, I just checked and all cartopy tests still pass with flufl-lock 6.0. > So for flufl-lock, if odcs works fine with the latest version then we can merge this in (I'll ping the maintainers directly); mailman3 and hyperkitty are both maintained by the same project (mailman) so I'm 99% sure there's no issue with it. Will probably only build for Rawhide though until we sort out mistune, otherwise we risk breakage without being able to get hyperkitty anyway. Thanks, -- Michel Alexandre Salim profile: https://keyoxide.org/mic...@michel-slm.name 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: The great Mailman 3 / Hyperkitty upgrade: bumping flufl-lock and mistune?
On Wed, Dec 15, 2021 at 11:53:02AM +0100, Miro Hrončok wrote: > On 15. 12. 21 11:51, Miro Hrončok wrote: > > On 14. 12. 21 23:29, Michel Alexandre Salim wrote: > > > In particular, python-nbconvert specifically requires mistune < 2, and > > > upstream doesn't seem to have a newer release yet. > > > > This is the biggest blocker. If nbconvert figures it out in git, we can > > backport it. Until then, I would not merge the update. If we really need > > this ASAP, we can introduce python-mistune0.8 compat pacakge. > > Upstream issue https://github.com/jupyter/nbconvert/issues/1685 > > I am quite confident they would accept a PR, but I don't have the capacity > to contribute one at this moment. I can try looking at this to unblock then. Thanks, -- Michel Alexandre Salim profile: https://keyoxide.org/mic...@michel-slm.name 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: F36 Change: Enable fs-verity in RPM (System-Wide Change proposal)
On Tue, Dec 14, 2021 at 4:20 PM Zbigniew Jędrzejewski-Szmek wrote: > > On Tue, Dec 14, 2021 at 08:08:19PM +0100, Fabio Valentini wrote: > > I thought fsverity was about determining at runtime that the system > > has not been tampered with? But if somebody who has (physical) access > > to the device can just ... move verified files out of the way and put > > their own (unverified) files there (which then apparently does not > > trigger red warning signs?) - doesn't that defeat the whole purpose of > > enabling fsverity? > > That's a good question. fs-verity and dm-verity share the same > underlying concept (merkle trees and signature verification by the > kernel). So this raises the question that you asked… which can also be > phrased as "why would you even use fs-verity, if you can do dm-verity"? dm-verity presents a read-only block device. It can't be modified once created. fs-verity works at the VFS layer. The block device and file system remain read-write capable, only the fs-verity enabled file contents are read-only. Also, fs-verity only really provides integrity checking in an efficient manner, with an optional mechanism for user space to enforce authentication - the kernel doesn't do this. A further option for user space is auditing. There is this dance in computer security where you're constantly plugging holes, looking for holes, but also assuming certain holes are definitely filled. It might seem like a contradiction. But of course we say physical access means the system is compromised, so you have to assume that hole is filled or all bets are off. Here you have to assume enough of user space is not compromised enough that you can trust that the fs-verity mechanisms can be used (create and verify), and the reason why you're using this regime is to make certain modifications impossible without detection so that the system doesn't become compromised, or at least compromised in silent fashion. fs-verity does not completely provide a secure and closed system, it's just one aspect of creating a more secure system. I'd go so far as to say it takes some esoteric knowledge to understand that this is only a "probably important small thing", and not a "critical big thing", to do. This is a few years old, 2018, but it discusses some of the confusing points when fs-verity was merged. https://lwn.net/Articles/763729/ Chris Murphy > My understanding it the following: fs-verity originated in the Android > world where you can have an unprivileged process downloading a file, > e.g. a jar. This unprivileged process manages the download, but the > file is only trusted and executed when it has a matching signature > from some central authority. The file contains the whole app, > including all resources, so there is no question of other unverified > files being used by the app. And the file can be large enough that > it's practical to do chunked verification, since checksumming the whole > file on first use would be slow. > > We don't really have the same considerations: the download process > has full privileges, and the download is exploded into individual files, > and more importantly, unpackaged files are also used. -- Chris Murphy ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Re: EPEL 9 is now available
On 15. 12. 21 17:49, Miroslav Suchý wrote: Dne 03. 12. 21 v 19:06 Troy Dawson napsal(a): Instructions to enable the EPEL repository are available in our documentation.[1] If there is a Fedora package you would like to see added to EPEL 9, please let the relevant package maintainer know with a package request.[2] For new builds, should we file an update in Bodhi? Yes. Or it gets to compose automagically? No. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Re: EPEL 9 is now available
Dne 03. 12. 21 v 19:06 Troy Dawson napsal(a): Instructions to enable the EPEL repository are available in our documentation.[1] If there is a Fedora package you would like to see added to EPEL 9, please let the relevant package maintainer know with a package request.[2] For new builds, should we file an update in Bodhi? Or it gets to compose automagically? Miroslav ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[EPEL-devel] Re: Requesting branches for epel9
Dne 14. 12. 21 v 17:12 Matthew Miller napsal(a): But it seems like "request an EPEL branch" should generally be either "Okay! Doing that automatically now" or "Oh, this is in EL, sorry"*. What are the other cases? As far as I know this isn't about requesting EPEL branches, as much as requesting any branches by hand. If I add something to Fedora rawhide and then ask for a F34 branch, the same issues can happen. Remember our build infrastructure is a pile of band-aids on top of duct tape on top of bungee cords. Lots of tools are written for a toolchain which existed years ago and have been hacked to make it work with whatever new initiative that comes into play. 'Unexpected' side effects and corner cases happen all the time and the fixing of them tends to add new ones. Sure. But also, asking people to spend a lot of their time running grunt-work tasks means that they have less time to fix when things break, let alone re-engineer away some of that tech debt. It seems like we should be able to automate the simple cases (adding F34 and F35 branches should be even easier, since we don't have the "is it in EL?" question even). *nod* So ... the question is how can I help? Can you document the check-list? I volunteer to start writing the script. Miroslav ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2033001] New: perl-Module-Install-CheckLib-0.14 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2033001 Bug ID: 2033001 Summary: perl-Module-Install-CheckLib-0.14 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Module-Install-CheckLib Keywords: FutureFeature, Triaged Assignee: ppi...@redhat.com Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: jples...@redhat.com, perl-devel@lists.fedoraproject.org, ppi...@redhat.com Target Milestone: --- Classification: Fedora Latest upstream release: 0.14 Current version/release in rawhide: 0.12-16.fc36 URL: http://search.cpan.org/dist/Module-Install-CheckLib/ 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://fedoraproject.org/wiki/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/10661/ -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2033001 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Provisional %{pyproject_build_lib} macro
On Tuesday, 14 December 2021 20.11.54 WET Miro Hrončok wrote:
> Hello Pythonistas,
> the pyproject-rpm-macros-0-51 update (available in Rawhide+ELN and updates
> ready for 33 and 34) introduces a new provisional %{pyproject_build_lib}
> macro.
"ready for 33 and 34"
This is a proof, not that it were necessary, that Miro is true Pythonista by
heart. :-D
We always start counting on 0: so Fedora Core 0, ..., Fedora Core 5, Fedora 6,
... Fedora 34 (the current)
On the probably more serious side thank you for adding this. There were times
were this would have been useful to have this for reasons you have explained.
:-)
Thank you,
--
José Abílio___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
Re: F36 Change: Enable fs-verity in RPM (System-Wide Change proposal)
On Tue, Dec 14, 2021 at 09:18:20PM +, Zbigniew Jędrzejewski-Szmek wrote: > My understanding it the following: fs-verity originated in the Android > world where you can have an unprivileged process downloading a file, > e.g. a jar. This unprivileged process manages the download, but the > file is only trusted and executed when it has a matching signature > from some central authority. The file contains the whole app, > including all resources, so there is no question of other unverified > files being used by the app. And the file can be large enough that > it's practical to do chunked verification, since checksumming the whole > file on first use would be slow. This does seem rather reminiscent of our LiveCD squashfs situation -- Matthew Miller Fedora Project Leader ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Automatically generated Obsoletes tags?
On 12/1/21 14:07, Miro Hrončok wrote: On 29. 11. 21 23:32, Elliott Sales de Andrade wrote: On Mon, 29 Nov 2021 at 08:04, Tomáš Orsava wrote: The downside is that we will have a few thousand (est. 3624 [1]) additional Obsoletes tags in the Fedora repos that are mostly useless. Does anyone see a problem with this? Given the amount of tags already present (e.g. 336 thousand provides [2], 80 thousand requires [3] and 7.5 thousand obsoletes [4]), I think it won't negatively affect anything, but I might be mistaken. That's a question for Fedora Devel, not the Python SIG specifically. https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/BHMCIBJXR2ZTCU7YNF2DJDI52U7KRIY5/ Based on the feedback from the devel mailing list and from the dnf team, we won't be turning on the automatic Obsoletes in Fedora, only in ELN. Tomáš ___ python-devel mailing list -- python-de...@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-de...@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: Is there a problem if we add ~4 thousand automatically generated obsoletes?
On 12/3/21 19:11, Kevin Fenzi wrote: On Wed, Dec 01, 2021 at 02:06:41PM +0100, Miro Hrončok wrote: Seehttps://lists.fedoraproject.org/archives/list/python-de...@lists.fedoraproject.org/thread/2OCCFIKT7LZ7IPO3OKIEH3TDTGERSORM/ Would adding automatically generated obsoletes to 3624 Python packages have any observable negative impact (e.g. on the repodata size or time to resolve deps)? I think that would increase the size of the primary repodata... I guess by number * length of obsolete, so might not be that bad? It would likely affect dnf processing time as well, but not sure how much. It seems like something to try and avoid if possible. kevin Hi, point taken. I've checked with the dnf team as well, and they're of the same opinion. So we won't be turning on the automatic Obsoletes in Fedora, only in ELN. Thanks for the feedback! Tomáš ___ devel mailing list --devel@lists.fedoraproject.org To unsubscribe send an email todevel-le...@lists.fedoraproject.org Fedora Code of Conduct:https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives:https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam on the list, report it:https://pagure.io/fedora-infrastructure___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2032872] perl-Safe-Isa for EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2032872 Paul Howarth changed: What|Removed |Added Status|NEW |ASSIGNED --- Comment #1 from Paul Howarth --- https://pagure.io/releng/fedora-scm-requests/issue/39620 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2032872 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2031079] perl-Crypt-DES for EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2031079 Paul Howarth changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|jpazdzi...@redhat.com |p...@city-fan.org --- Comment #2 from Paul Howarth --- Thanks Jan. https://pagure.io/releng/fedora-scm-requests/issue/39619 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2031079 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2032799] perl-Crypt-DH for EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2032799 Paul Howarth changed: What|Removed |Added Status|NEW |ASSIGNED --- Comment #1 from Paul Howarth --- https://pagure.io/releng/fedora-scm-requests/issue/39618 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2032799 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: new systemd in rawhide
On Wed, Dec 15, 2021 at 07:13:49AM -0500, Neal Gompa wrote: > On Sat, Dec 11, 2021 at 5:43 AM Zbigniew Jędrzejewski-Szmek > wrote: > > > > On Fri, Dec 10, 2021 at 05:03:45PM +, Richard W.M. Jones wrote: > > > On Fri, Dec 10, 2021 at 07:34:42AM +, Zbigniew Jędrzejewski-Szmek > > > wrote: > > > > Also, I moved more stuff into the -udev subpackage: > > > > systemd-integritysetup, systemd-veritysetup, systemd-binfmt, > > > > systemd-sysctl, systemd-coredump. IIUC, none of those are useful > > > > in containers, so they fit better in -udev which is supposed to be > > > > installed > > > > on real hardware or VMs. > > > > > > Could we keep udev to being for udev and introduce a different package > > > for extras? This change affects libguestfs which only wants udev, not > > > systemd or anything else. > > > > Hmm, I don't think this changes anything for libguestfs. The > > systemd-udev rpm requires systemd, so if have systemd-udev, this is a > > noop. > > > > Please put systemd-coredump back in the main systemd package. Unlike > the others, this is actually required functionality for backtrace > stuff, especially if you're running OS containers (nspawn, ubi-init, > etc.). The handler for coredumps (/proc/sys/kernel/core_pattern) is not namespaced, so coredumps reported in a container are handled on the host (*). Are you sure that your coredump processing happens in the container? How does the pattern look like and how is the whole thing set up? (*) In principle systemd-coredump on the host could feed the core file back to some handler invoked in the container. We discussed this a few times in the past and it would be quite useful for some types of containers. But I'm not aware of this being implemented anywhere. 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2031079] perl-Crypt-DES for EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2031079 Jan Pazdziora changed: What|Removed |Added Doc Type|--- |If docs needed, set a value --- Comment #1 from Jan Pazdziora --- Hello Paul, I've added you now, so feel free to handle the EPEL 9 onboarding. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2031079 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 1744782] (RFE) EPEL8 branch of perl-Crypt-SSLeay
https://bugzilla.redhat.com/show_bug.cgi?id=1744782 Jitka Plesnikova changed: What|Removed |Added Flags|needinfo?(jplesnik@redhat.c | |om) | Status|NEW |ASSIGNED --- Comment #8 from Jitka Plesnikova --- The scratch build passed against EPEL 8, so I requested the branch. https://pagure.io/releng/fedora-scm-requests/issue/39615 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=1744782 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: Raising the attachment size limit in bugzilla?
On Tue, Dec 14, 2021 at 4:50 PM Carlos O'Donell wrote: > > I have not seen any Fedora-specific customization for sos (the package e.g. > sos.spec) > but it should be possible to do that. > > I could file a bug asking for a Fedora-specific customization to default to > collecting less information? That would probably be the better approach in this case. I can certainly talk to the BZ admins about making config changes. I'm not sure if they could make these on a per-product basis or if it would have to be site wide. But if we're reporting too much information and can pare it down on the sending side, that's a win for everyone. Particularly for people who are on capped and/or slow-upload Internet connections. -- 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2032874] New: perl-Module-Runtime-Conflicts for EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2032874 Bug ID: 2032874 Summary: perl-Module-Runtime-Conflicts for EPEL 9 Product: Fedora EPEL Version: epel9 Status: NEW Component: perl-Module-Runtime-Conflicts Assignee: emman...@seyman.fr Reporter: jples...@redhat.com QA Contact: extras...@fedoraproject.org CC: emman...@seyman.fr, perl-devel@lists.fedoraproject.org Blocks: 2032450 Target Milestone: --- Classification: Fedora Could you please branch and build perl-Module-Runtime-Conflicts for EPEL 9 ? Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2032450 [Bug 2032450] perl-Test-LWP-UserAgent for EPEL 9 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2032874 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2032450] perl-Test-LWP-UserAgent for EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2032450 Jitka Plesnikova changed: What|Removed |Added Depends On||2032874 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2032874 [Bug 2032874] perl-Module-Runtime-Conflicts for EPEL 9 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2032450 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2032450] perl-Test-LWP-UserAgent for EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2032450 Jitka Plesnikova changed: What|Removed |Added Depends On||2032872 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2032872 [Bug 2032872] perl-Safe-Isa for EPEL 9 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2032450 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2032872] New: perl-Safe-Isa for EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2032872 Bug ID: 2032872 Summary: perl-Safe-Isa for EPEL 9 Product: Fedora EPEL Version: epel9 Status: NEW Component: perl-Safe-Isa Assignee: p...@city-fan.org Reporter: jples...@redhat.com QA Contact: extras...@fedoraproject.org CC: iarn...@gmail.com, p...@city-fan.org, perl-devel@lists.fedoraproject.org Blocks: 2032450 Target Milestone: --- Classification: Fedora Could you please branch and build perl-Safe-Isa for EPEL 9 ? Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2032450 [Bug 2032450] perl-Test-LWP-UserAgent for EPEL 9 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2032872 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2032440] perl-JSON-MaybeXS for EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2032440 Jitka Plesnikova changed: What|Removed |Added Blocks||2032450 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2032450 [Bug 2032450] perl-Test-LWP-UserAgent for EPEL 9 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2032440 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2032425] perl-Moose for EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2032425 Jitka Plesnikova changed: What|Removed |Added Blocks||2032450 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2032450 [Bug 2032450] perl-Test-LWP-UserAgent for EPEL 9 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2032425 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2032450] perl-Test-LWP-UserAgent for EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2032450 Jitka Plesnikova changed: What|Removed |Added Depends On||2032425, 2031812, 2032440 Doc Type|--- |If docs needed, set a value Status|NEW |ASSIGNED Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2031812 [Bug 2031812] perl-Plack for EPEL 9 https://bugzilla.redhat.com/show_bug.cgi?id=2032425 [Bug 2032425] perl-Moose for EPEL 9 https://bugzilla.redhat.com/show_bug.cgi?id=2032440 [Bug 2032440] perl-JSON-MaybeXS for EPEL 9 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2032450 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2031812] perl-Plack for EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2031812 Jitka Plesnikova changed: What|Removed |Added Blocks||2032450 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2032450 [Bug 2032450] perl-Test-LWP-UserAgent for EPEL 9 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2031812 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: new systemd in rawhide
On Sat, Dec 11, 2021 at 5:43 AM Zbigniew Jędrzejewski-Szmek wrote: > > On Fri, Dec 10, 2021 at 05:03:45PM +, Richard W.M. Jones wrote: > > On Fri, Dec 10, 2021 at 07:34:42AM +, Zbigniew Jędrzejewski-Szmek wrote: > > > Also, I moved more stuff into the -udev subpackage: > > > systemd-integritysetup, systemd-veritysetup, systemd-binfmt, > > > systemd-sysctl, systemd-coredump. IIUC, none of those are useful > > > in containers, so they fit better in -udev which is supposed to be > > > installed > > > on real hardware or VMs. > > > > Could we keep udev to being for udev and introduce a different package > > for extras? This change affects libguestfs which only wants udev, not > > systemd or anything else. > > Hmm, I don't think this changes anything for libguestfs. The > systemd-udev rpm requires systemd, so if have systemd-udev, this is a > noop. > Please put systemd-coredump back in the main systemd package. Unlike the others, this is actually required functionality for backtrace stuff, especially if you're running OS containers (nspawn, ubi-init, etc.). -- 真実はいつも一つ！/ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2032857] please branch and build perl-Module-Install-CheckLib for EPEL-9
https://bugzilla.redhat.com/show_bug.cgi?id=2032857 Petr Pisar changed: What|Removed |Added Status|NEW |ASSIGNED --- Comment #1 from Petr Pisar --- https://pagure.io/releng/fedora-scm-requests/issue/39608 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2032857 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2031819] perl-Test-Output for EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2031819 Fedora Update System changed: What|Removed |Added Status|ASSIGNED|MODIFIED --- Comment #2 from Fedora Update System --- FEDORA-EPEL-2021-f429da3989 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-f429da3989 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2031819 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2031862] Please branch and build perl-Test-File-Contents for EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2031862 Fedora Update System changed: What|Removed |Added Status|ASSIGNED|MODIFIED --- Comment #2 from Fedora Update System --- FEDORA-EPEL-2021-bd33056b63 has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-bd33056b63 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2031862 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2032857] please branch and build perl-Module-Install-CheckLib for EPEL-9
https://bugzilla.redhat.com/show_bug.cgi?id=2032857 Paul Howarth changed: What|Removed |Added Doc Type|--- |If docs needed, set a value Blocks||2032799 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2032799 [Bug 2032799] perl-Crypt-DH for EPEL 9 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2032857 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2032799] perl-Crypt-DH for EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2032799 Paul Howarth changed: What|Removed |Added Depends On||2032857 Referenced Bugs: https://bugzilla.redhat.com/show_bug.cgi?id=2032857 [Bug 2032857] please branch and build perl-Module-Install-CheckLib for EPEL-9 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2032799 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2032857] New: please branch and build perl-Module-Install-CheckLib for EPEL-9
https://bugzilla.redhat.com/show_bug.cgi?id=2032857 Bug ID: 2032857 Summary: please branch and build perl-Module-Install-CheckLib for EPEL-9 Product: Fedora Version: rawhide Status: NEW Component: perl-Module-Install-CheckLib Assignee: ppi...@redhat.com Reporter: p...@city-fan.org QA Contact: extras...@fedoraproject.org CC: jples...@redhat.com, perl-devel@lists.fedoraproject.org, ppi...@redhat.com Target Milestone: --- Classification: Fedora Could you please branch and build perl-Module-Install-CheckLib for EPEL-9 ? If you prefer, you could add me (FAS: pghmcfc) as a committer and I'll do it myself. I am taking care of the build dependencies perl-Module-Install-AutoLicense and perl-Module-Install-GithubMeta at the moment and they should be ready by tomorrow. -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2032857 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: HEADS UP: Update to tesseract-5.0.0 in rawhide
On 15.12.21 11:11, Michael J Gruber wrote: Are you planning to bring these to F35, as well? Tesseract-5.0.0 appears to be mostly a bugfix release along with some other improvements, so I dunno (and haven't tested so far - the heads up was a few hours before the push). Since it brings along a soname bump, I wasn't planning on building it for stable releases. Sandro ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: The great Mailman 3 / Hyperkitty upgrade: bumping flufl-lock and mistune?
On 15. 12. 21 11:51, Miro Hrončok wrote: On 14. 12. 21 23:29, Michel Alexandre Salim wrote: In particular, python-nbconvert specifically requires mistune < 2, and upstream doesn't seem to have a newer release yet. This is the biggest blocker. If nbconvert figures it out in git, we can backport it. Until then, I would not merge the update. If we really need this ASAP, we can introduce python-mistune0.8 compat pacakge. Upstream issue https://github.com/jupyter/nbconvert/issues/1685 I am quite confident they would accept a PR, but I don't have the capacity to contribute one at this moment. -- 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: The great Mailman 3 / Hyperkitty upgrade: bumping flufl-lock and mistune?
On 14. 12. 21 23:29, Michel Alexandre Salim wrote: Hi all, Neal Gompa and I have been reviving the effort to get our mailing list server infrastructure (currently running on RHEL 7 with missing packages provided in an unofficial repo) hostable on RHEL 9 + EPEL. Pagure issue: https://pagure.io/fedora-infrastructure/issue/8455 Bugzilla tracker: https://bugzilla.redhat.com/show_bug.cgi?id=2030061 Status: https://hackmd.io/Pb9otlVGQHe1r9BIC5bi7w (not fully updated yet) We're currently stuck on the following: https://bugzilla.redhat.com/show_bug.cgi?id=2032607 Your package (python-hyperkitty) Fails To Install in Fedora 36: can't install hyperkitty: - nothing provides python3.10dist(flufl-lock) >= 4 needed by hyperkitty-1.3.5-1.fc36.noarch - nothing provides python3.10dist(mistune) >= 2~rc1 needed by hyperkitty-1.3.5-1.fc36.noarch I have PRs attached to the upgrade requests for mistune: https://bugzilla.redhat.com/show_bug.cgi?id=1782288 and flufl-lock: https://bugzilla.redhat.com/show_bug.cgi?id=1852603 but both have breaking changes I detailed in the above Bz entries; if you're a maintainer cc:ed on this email please check the relevant bz: ... ❯ sudo dnf repoquery --enablerepo=fedora-source,rawhide,rawhide-source --whatrequires python3-mistune python-m2r-0:0.2.1-5.20190604git66f4a5a.fc35.src python-nbconvert-0:6.1.0-2.fc35.src python-nbconvert-0:6.1.0-3.fc36.src python3-m2r-0:0.2.1-5.20190604git66f4a5a.fc35.noarch python3-nbconvert-0:6.1.0-2.fc35.noarch python3-nbconvert-0:6.1.0-3.fc36.noarch In particular, python-nbconvert specifically requires mistune < 2, and upstream doesn't seem to have a newer release yet. This is the biggest blocker. If nbconvert figures it out in git, we can backport it. Until then, I would not merge the update. If we really need this ASAP, we can introduce python-mistune0.8 compat pacakge. PRs: https://src.fedoraproject.org/rpms/python-flufl-lock/pull-request/1 https://src.fedoraproject.org/rpms/python-mistune/pull-request/5 ... We should probably bump the packages in Rawhide anyway No, please don't yet. , but also to note: - both of these packages are not co-maintained by the Python SIG mistune is. - most of the recent updates have been done by non-maintainers For mistune, it was by Python SIG members. Would it make sense to get the following groups officially added to the package ACLs? - infra-sig (admin), to ease maintaining the dependencies for Mailman and Hyperkitty Python SIG is very responsive to pull requests, so I don't think adding another SIG makes the "ease of maintaining" significantly better. - python-sig (commit or admin), for fixing issues e.g. with newer Python versions Already there. - epel-packagers-sig (collaborator, epel* branches) for helping to bootstrap on new EL releases Fine by me, although I prefer actual maintainers to be responsible for EPEL branches. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/python-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: The great Mailman 3 / Hyperkitty upgrade: bumping flufl-lock and mistune?
On 14. 12. 21 23:29, Michel Alexandre Salim wrote: Hi all, Neal Gompa and I have been reviving the effort to get our mailing list server infrastructure (currently running on RHEL 7 with missing packages provided in an unofficial repo) hostable on RHEL 9 + EPEL. Pagure issue: https://pagure.io/fedora-infrastructure/issue/8455 Bugzilla tracker: https://bugzilla.redhat.com/show_bug.cgi?id=2030061 Status: https://hackmd.io/Pb9otlVGQHe1r9BIC5bi7w (not fully updated yet) We're currently stuck on the following: https://bugzilla.redhat.com/show_bug.cgi?id=2032607 Your package (python-hyperkitty) Fails To Install in Fedora 36: can't install hyperkitty: - nothing provides python3.10dist(flufl-lock) >= 4 needed by hyperkitty-1.3.5-1.fc36.noarch - nothing provides python3.10dist(mistune) >= 2~rc1 needed by hyperkitty-1.3.5-1.fc36.noarch I have PRs attached to the upgrade requests for mistune: https://bugzilla.redhat.com/show_bug.cgi?id=1782288 and flufl-lock: https://bugzilla.redhat.com/show_bug.cgi?id=1852603 but both have breaking changes I detailed in the above Bz entries; if you're a maintainer cc:ed on this email please check the relevant bz: ... ❯ sudo dnf repoquery --enablerepo=fedora-source,rawhide,rawhide-source --whatrequires python3-mistune python-m2r-0:0.2.1-5.20190604git66f4a5a.fc35.src python-nbconvert-0:6.1.0-2.fc35.src python-nbconvert-0:6.1.0-3.fc36.src python3-m2r-0:0.2.1-5.20190604git66f4a5a.fc35.noarch python3-nbconvert-0:6.1.0-2.fc35.noarch python3-nbconvert-0:6.1.0-3.fc36.noarch In particular, python-nbconvert specifically requires mistune < 2, and upstream doesn't seem to have a newer release yet. This is the biggest blocker. If nbconvert figures it out in git, we can backport it. Until then, I would not merge the update. If we really need this ASAP, we can introduce python-mistune0.8 compat pacakge. PRs: https://src.fedoraproject.org/rpms/python-flufl-lock/pull-request/1 https://src.fedoraproject.org/rpms/python-mistune/pull-request/5 ... We should probably bump the packages in Rawhide anyway No, please don't yet. , but also to note: - both of these packages are not co-maintained by the Python SIG mistune is. - most of the recent updates have been done by non-maintainers For mistune, it was by Python SIG members. Would it make sense to get the following groups officially added to the package ACLs? - infra-sig (admin), to ease maintaining the dependencies for Mailman and Hyperkitty Python SIG is very responsive to pull requests, so I don't think adding another SIG makes the "ease of maintaining" significantly better. - python-sig (commit or admin), for fixing issues e.g. with newer Python versions Already there. - epel-packagers-sig (collaborator, epel* branches) for helping to bootstrap on new EL releases Fine by me, although I prefer actual maintainers to be responsible for EPEL branches. -- 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2032838] New: perl-HTML-Template-Pro-0.9523 is available
https://bugzilla.redhat.com/show_bug.cgi?id=2032838 Bug ID: 2032838 Summary: perl-HTML-Template-Pro-0.9523 is available Product: Fedora Version: rawhide Status: NEW Component: perl-HTML-Template-Pro Keywords: FutureFeature, Triaged Assignee: emman...@seyman.fr Reporter: upstream-release-monitor...@fedoraproject.org QA Contact: extras...@fedoraproject.org CC: emman...@seyman.fr, jakub.jedel...@gmail.com, lkund...@v3.sk, perl-devel@lists.fedoraproject.org, tjczep...@gmail.com Target Milestone: --- Classification: Fedora Latest upstream release: 0.9523 Current version/release in rawhide: 0.9522-1.fc36 URL: http://search.cpan.org/dist/HTML-Template-Pro 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://fedoraproject.org/wiki/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/7119/ -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2032838 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2031829] Please branch and build perl-Redis for EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2031829 Jitka Plesnikova changed: What|Removed |Added Status|NEW |ASSIGNED --- Comment #2 from Jitka Plesnikova --- https://pagure.io/releng/fedora-scm-requests/issue/39604 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2031829 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Re: HEADS UP: Update to tesseract-5.0.0 in rawhide
Are you planning to bring these to F35, as well? Tesseract-5.0.0 appears to be mostly a bugfix release along with some other improvements, so I dunno (and haven't tested so far - the heads up was a few hours before the push). ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
[Bug 2032454] perl-UUID-Tiny for EPEL 9
https://bugzilla.redhat.com/show_bug.cgi?id=2032454 Jitka Plesnikova changed: What|Removed |Added Status|NEW |ASSIGNED --- Comment #1 from Jitka Plesnikova --- https://pagure.io/releng/fedora-scm-requests/issue/39602 -- You are receiving this mail because: You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2032454 ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Fedora-Cloud-34-20211215.0 compose check report
No missing expected images. Soft failed openQA tests: 1/8 (x86_64), 1/8 (aarch64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-Cloud-34-20211214.0): ID: 1086510 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/1086510 ID: 1086521 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/1086521 Passed openQA tests: 7/8 (x86_64), 7/8 (aarch64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Request for sponsorship in fedora-contributor group
Hello everyone I have done some work in the integrity subsystem, called Digest Lists Integrity Module (DIGLIM). It simplifies the effort necessary to do IMA appraisal, by reusing the digests included in the header of existing RPM packages as reference values. It wouldn't require any change in the building infrastructure. It also provides an alternative way of attesting systems, by keeping the TPM PCR extended with software measurements, stable and predictable. The main benefit is the ability to seal a TPM key to the desired software configuration, so that a TLS secure communication can be established when only software from installed RPMs is executed. It would be possible to integrate this solution in Keylime. I have proposed this feature for upstream inclusion: https://lore.kernel.org/linux-integrity/20210914163401.864635-1-roberto.sa...@huawei.com/ I also rebuilt the Fedora kernel in copr, with DIGLIM: https://copr.fedorainfracloud.org/coprs/robertosassu/DIGLIM/ You can find the instructions about how to use it here: https://lore.kernel.org/linux-integrity/48cd737c504d45208377daa27d625...@huawei.com/ I would like to join one of your subgroups, for example fedora-contributor, so that I can propose a new feature for Fedora 36/37. Thanks Roberto HUAWEI TECHNOLOGIES Duesseldorf GmbH, HRB 56063 Managing Director: Li Peng, Zhong Ronghua ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
Fedora-Cloud-35-20211215.0 compose check report
No missing expected images. Soft failed openQA tests: 1/8 (x86_64), 1/8 (aarch64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-Cloud-35-20211214.0): ID: 1086493 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://openqa.fedoraproject.org/tests/1086493 ID: 1086504 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL: https://openqa.fedoraproject.org/tests/1086504 Passed openQA tests: 7/8 (x86_64), 7/8 (aarch64) -- Mail generated by check-compose: https://pagure.io/fedora-qa/check-compose ___ 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 on the list, report it: https://pagure.io/fedora-infrastructure
