Re: F37 Proposal: Strong crypto settings: phase 3, forewarning 1/2 (System-Wide Change proposal)

On Tue, May 31, 2022 at 08:59:28AM +0200, Petr Pisar wrote: > V Tue, May 31, 2022 at 08:07:57AM +0200, Alexander Sosedkin napsal(a): > > On Mon, May 30, 2022 at 10:34 PM Garry T. Williams > > wrote: > > > On Friday, April 29, 2022 5:49:05 PM EDT Ben Cotton wrote: > > > > Cryptographic policies wi

Re: Ceph, virt packages (Re: Orphaned packages looking for new maintainers)

On Mon, May 30, 2022 at 02:05:58PM +0200, Miro Hrončok wrote: > On 30. 05. 22 10:09, Richard W.M. Jones wrote: > > On Mon, May 30, 2022 at 09:31:21AM +0200, Miro Hrončok wrote: > > > The following packages are orphaned and will be retired when they > > > are orphaned for six weeks, unless someone a

Fedora-Rawhide-20220531.n.0 compose check report

Missing expected images: Minimal raw-xz armhfp Compose PASSES proposed Rawhide gating check! All required tests passed Failed openQA tests: 8/231 (x86_64), 11/161 (aarch64) New failures (same test not failed in Fedora-Rawhide-20220530.n.0): ID: 1285782 Test: x86_64 Server-dvd-iso anaconda_

Fedora rawhide compose report: 20220531.n.0 changes

OLD: Fedora-Rawhide-20220530.n.0 NEW: Fedora-Rawhide-20220531.n.0 = SUMMARY = Added images:0 Dropped images: 1 Added packages: 0 Dropped packages:1 Upgraded packages: 99 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:2.73 MiB

F40 proposal: Retire python3.7 (Self-Contained Change proposal)

https://fedoraproject.org/wiki/Changes/RetirePython3.7 This document represents a proposed Change. As part of the Changes process, proposals are publicly announced in order to receive community feedback. This proposal will only be implemented if approved by the Fedora Engineering Steering Committe

Re: exploded git tree for kernel-5.17.4-200.fc35

On Tue, May 31, 2022 at 3:12 AM Laszlo Ersek wrote: > > On 05/31/22 08:58, Dan Horák wrote: > > On Tue, 31 May 2022 08:39:28 +0200 > > Laszlo Ersek wrote: > > > >> Hi, > >> > >> where can I find the exploded git tree for "kernel-5.17.4-200.fc35"? > >> > >> The tree at > >>

Re: F37 Proposal: Strong crypto settings: phase 3, forewarning 1/2 (System-Wide Change proposal)

V Tue, May 31, 2022 at 04:25:28PM +0200, Alexander Sosedkin napsal(a): > On Tue, May 31, 2022 at 4:09 PM Petr Pisar wrote: > > > > V Tue, May 31, 2022 at 03:51:26PM +0200, Alexander Sosedkin napsal(a): > > > On Tue, May 31, 2022 at 3:45 PM Petr Pisar wrote: > > > > > > > > V Tue, May 31, 2022 at

Re: ROCm-OpenCL package

Thanks Felix, An open concern that I have been discussing with the ROCm guys is that HIP (used for things like pytorch) requires rocm-opencl source code to compile. It seems they want to go with the llvm-project approach in the longterm, having opencl, hip, and the common static lib "ROCclr" as

Re: F37 Proposal: Strong crypto settings: phase 3, forewarning 1/2 (System-Wide Change proposal)

On Tue, May 31, 2022 at 4:09 PM Petr Pisar wrote: > > V Tue, May 31, 2022 at 03:51:26PM +0200, Alexander Sosedkin napsal(a): > > On Tue, May 31, 2022 at 3:45 PM Petr Pisar wrote: > > > > > > V Tue, May 31, 2022 at 02:56:56PM +0200, Alexander Sosedkin napsal(a): > > > > On Tue, May 31, 2022 at 12:

Re: F37 Proposal: Strong crypto settings: phase 3, forewarning 1/2 (System-Wide Change proposal)

V Tue, May 31, 2022 at 03:51:26PM +0200, Alexander Sosedkin napsal(a): > On Tue, May 31, 2022 at 3:45 PM Petr Pisar wrote: > > > > V Tue, May 31, 2022 at 02:56:56PM +0200, Alexander Sosedkin napsal(a): > > > On Tue, May 31, 2022 at 12:28 PM Vitaly Zaitsev via devel > > > wrote: > > > > On 31/05/2

Re: F37 Proposal: Strong crypto settings: phase 3, forewarning 1/2 (System-Wide Change proposal)

On Tue, May 31, 2022 at 3:45 PM Petr Pisar wrote: > > V Tue, May 31, 2022 at 02:56:56PM +0200, Alexander Sosedkin napsal(a): > > On Tue, May 31, 2022 at 12:28 PM Vitaly Zaitsev via devel > > wrote: > > > On 31/05/2022 10:21, Petr Pisar wrote: > > > > Not in current F37 FUTURE policy the user test

Re: F37 Proposal: Strong crypto settings: phase 3, forewarning 1/2 (System-Wide Change proposal)

V Tue, May 31, 2022 at 02:56:56PM +0200, Alexander Sosedkin napsal(a): > On Tue, May 31, 2022 at 12:28 PM Vitaly Zaitsev via devel > wrote: > > On 31/05/2022 10:21, Petr Pisar wrote: > > > Not in current F37 FUTURE policy the user tested. > > > > Yes. If the new F37 cryptographic policy considers

Re: F37 Proposal: Strong crypto settings: phase 3, forewarning 1/2 (System-Wide Change proposal)

On Tue, May 31, 2022 at 12:28 PM Vitaly Zaitsev via devel wrote: > On 31/05/2022 10:21, Petr Pisar wrote: > > Not in current F37 FUTURE policy the user tested. > > Yes. If the new F37 cryptographic policy considers RSA-2048 to be weak, > it should be reverted. The actual proposal is in the OP. N

unpaper-7.0.0 license change

unpaper-7.0.0 changed a license from (GPLv2) to (GPLv2 and 0BSD and MIT). -- Petr signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedor

Call for review: Borg Backup (crypto & python)

Hi all, Borg Backup (https://www.borgbackup.org/), which is also part of the Fedora repository, is a widespread open source incremental backup tool with authenticated encryption. Quite sure many of you know & use it. The crypto was completely redesigned for the upcoming version 1.3. Therefor

Re: exploded git tree for kernel-5.17.4-200.fc35

On Tue, May 31, 2022 at 2:39 AM Laszlo Ersek wrote: > > Hi, > > where can I find the exploded git tree for "kernel-5.17.4-200.fc35"? > > The tree at > is > no good; it does not have tags beyond .fc33. I'm going to delete this tr

Re: intend to orphan python-cairosvg

On 31. 05. 22 12:44, Felix Schwarz wrote: Hi *, I'd like to orphan python-cairosvg. This package was required by older WeasyPrint releases but WeasyPrint v53 (Fedora 35+) stopped using cairo so I don't use this package anymore. The package should be ok however I expect very little upstream m

intend to orphan python-cairosvg

Hi *, I'd like to orphan python-cairosvg. This package was required by older WeasyPrint releases but WeasyPrint v53 (Fedora 35+) stopped using cairo so I don't use this package anymore. The package should be ok however I expect very little upstream maintainance as the code was maintained by

intend to orphan python-cairocffi

Hi *, I'd like to orphan python-cairocffi. This package was required by older WeasyPrint releases but WeasyPrint v53 (Fedora 35+) stopped using cairo so I don't use this package anymore. On top of this cairocffi was developed by the WeasyPrint developers and they stopped maintaining it once

Re: F37 Proposal: Strong crypto settings: phase 3, forewarning 1/2 (System-Wide Change proposal)

On 31/05/2022 10:21, Petr Pisar wrote: Not in current F37 FUTURE policy the user tested. Yes. If the new F37 cryptographic policy considers RSA-2048 to be weak, it should be reverted. Many servers still use RSA-2048 (the default in Let's Encrypt). -- Sincerely, Vitaly Zaitsev (vit...@easy

Initiated non-responsive maintainer process for terrycloth

The gnome-shell-extension-freon isn't getting updated, see: https://bugzilla.redhat.com/show_bug.cgi?id=2009382 So as a result, nonresponsive maintainer process is initiated: https://bugzilla.redhat.com/show_bug.cgi?id=2091906 If you have a way to notify Audrey please help. It's better if I can

Fedora-Cloud-34-20220531.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-20220530.0): ID: 1285073 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://op

Re: Looking for pam_radius maintainer

Hi Jason, I can take over it. I'm already the maintainer of the pam package and it feels natural that I also take care of pam_radius. On Sun, May 29, 2022 at 2:39 AM Jason Taylor wrote: > Hi All, > > I am looking for someone to take over the pam_radius packaging as I no > longer have time to do

Re: F37 Proposal: Strong crypto settings: phase 3, forewarning 1/2 (System-Wide Change proposal)

V Tue, May 31, 2022 at 10:20:10AM +0200, Vitaly Zaitsev via devel napsal(a): > On 31/05/2022 08:59, Petr Pisar wrote: > > It's a 2048-bit RSA key of an intermediate certificate. > > RSA-2048 is still okay. It should work without errors. > Not in current F37 FUTURE policy the user tested. -- Petr

Re: F37 Proposal: Strong crypto settings: phase 3, forewarning 1/2 (System-Wide Change proposal)

On 31/05/2022 08:59, Petr Pisar wrote: It's a 2048-bit RSA key of an intermediate certificate. RSA-2048 is still okay. It should work without errors. -- Sincerely, Vitaly Zaitsev (vit...@easycoding.org) ___ devel mailing list -- devel@lists.fedorap

Re: exploded git tree for kernel-5.17.4-200.fc35

On 05/31/22 08:58, Dan Horák wrote: > On Tue, 31 May 2022 08:39:28 +0200 > Laszlo Ersek wrote: > >> Hi, >> >> where can I find the exploded git tree for "kernel-5.17.4-200.fc35"? >> >> The tree at >> is >> no good; it does not h

Fedora-Cloud-36-20220531.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-36-20220530.0): ID: 1284882 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://op

Re: ROCm-OpenCL package

Hi Jeremy, just wanted to thank you for your contributions to ROCm on Fedora + your upstream work to make the stack more distro-friendly. I'm pretty much swamped right now. Maybe I find some time to chime in but I hope someone else could review this. Debian has a pretty active ROCm packagin