Re: A way to prepare custom source tarballs from .spec file to improve CI experience

Dne 26. 04. 22 v 12:40 Vít Ondruch napsal(a): Dne 25. 04. 22 v 10:41 Vít Ondruch napsal(a): We already have signature of source files as additional source. Do you mean the 'sources' file? I mean https://docs.fedoraproject.org/en-US/packaging-guidelines/#_verifying_signatures Miroslav __

Fedora-IoT-37-20220503.0 compose check report

Missing expected images: Iot dvd aarch64 Iot dvd x86_64 Failed openQA tests: 4/15 (aarch64) ID: 1251815 Test: aarch64 IoT-dvd_ostree-iso iot_clevis@uefi URL: https://openqa.fedoraproject.org/tests/1251815 ID: 1251817 Test: aarch64 IoT-dvd_ostree-iso podman@uefi URL: https://openqa.fedora

[Test-Announce] Fedora-IoT 36 RC 20220503.0 nightly compose nominated for testing

Announcing the creation of a new nightly release validation test event for Fedora-IoT 36 RC 20220503.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_pl

Fedora rawhide compose report: 20220503.n.0 changes

OLD: Fedora-Rawhide-20220502.n.0 NEW: Fedora-Rawhide-20220503.n.0 = SUMMARY = Added images:1 Dropped images: 0 Added packages: 9 Dropped packages:9 Upgraded packages: 78 Downgraded packages: 0 Size of added packages: 49.19 MiB Size of dropped packages

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

Ian Pilcher wrote: > It sure feels like we're reaching the point where anyone who has to work > with any sort of older equipment or servers is going to to forced to > switch their entire system to the LEGACY policy, which seems really > unfortunate. Even worse is that even the LEGACY policy is get

Fedora-IoT-36-20220503.0 compose check report

No missing expected images. Failed openQA tests: 3/15 (aarch64) New failures (same test not failed in Fedora-IoT-36-20220429.0): ID: 1252295 Test: aarch64 IoT-dvd_ostree-iso podman@uefi URL: https://openqa.fedoraproject.org/tests/1252295 ID: 1252301 Test: aarch64 IoT-dvd_ostree-iso podma

Fedora 36 compose report: 20220503.n.0 changes

OLD: Fedora-36-20220501.n.0 NEW: Fedora-36-20220503.n.0 = SUMMARY = Added images:1 Dropped images: 0 Added packages: 0 Dropped packages:0 Upgraded packages: 6 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:0 B Size of upgraded

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

Hi, Kevin Kofler via devel wrote: I think we need a REALLY_LEGACY that continues allowing MD5 and the like. According to https://github.com/corkami/collisions#chosen-prefix-collisions, a chosen-prefix collision on MD5 took 72 hours to compute in 2009. 13 years later, you really should treat

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

Missing expected images: Minimal raw-xz armhfp Compose FAILS proposed Rawhide gating check! 3 of 43 required tests failed openQA tests matching unsatisfied gating requirements shown with **GATING** below Failed openQA tests: 23/231 (x86_64), 22/161 (aarch64) New failures (same test not failed

HEADS UP: podofo-0.9.8 coming to rawhide

Hi I'm landing podofo 0.9.8 which carries a soname bump. I'll build it and rebuild the following dependent packages in f37-build-side-53387: calibre gimagereader krename pdfsign scribus vfrnav Sandro ___ devel mailing list -- devel@lists.fedoraproje

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

On Mon, May 02, 2022 at 08:56:06AM -0500, Ian Pilcher wrote: > It sure feels like we're reaching the point where anyone who has to work > with any sort of older equipment or servers is going to to forced to > switch their entire system to the LEGACY policy, which seems really > unfortunate. See al

Re: F37 Change: Deprecate Legacy BIOS (System-Wide Change proposal)

Hi, On 5/2/22 22:53, Chris Murphy wrote: On Mon, May 2, 2022 at 5:29 PM Jeremy Linton wrote: On 4/6/22 12:57, Neal Gompa wrote: (trimming) * NVIDIA graphics * Broadcom wireless The former case is excessively common, and the latter case is fairly common with HP and Dell machines as well as s

Fedora-36-20220503.n.0 compose check report

No missing expected images. Failed openQA tests: 7/229 (x86_64), 12/161 (aarch64) New failures (same test not failed in Fedora-36-20220501.n.0): ID: 1252415 Test: x86_64 KDE-live-iso desktop_login URL: https://openqa.fedoraproject.org/tests/1252415 ID: 1252431 Test: x86_64 Silverblue-dvd

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

On Tue, May 3, 2022 at 1:20 PM Kevin Kofler via devel wrote: > > Ian Pilcher wrote: > > It sure feels like we're reaching the point where anyone who has to work > > with any sort of older equipment or servers is going to to forced to > > switch their entire system to the LEGACY policy, which seems

Summary/Minutes from today's FESCo Meeting (2022-05-03)

=== #fedora-meeting: FESCO (2022-05-03) === Meeting started by mhroncok at 17:00:04 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting/2022-05-03/fesco.2022-05-03-17.00.log.html . Meeting summary

rdkit package re-review

Hi all. rdkit package is under re-review for unretiring. Please, take a look if you can. Bug ticket: https://bugzilla.redhat.com/show_bug.cgi?id=2081113 Regards -- --- Antonio Trande Fedora Project mailto: sagit...@fedoraproject.org GPG key: 0xCC1CFEF30920C8AE GPG key server: https://keyserver1

Re: F37 Change: Deprecate Legacy BIOS (System-Wide Change proposal)

On Tue, May 3, 2022 at 11:32 AM Jeremy Linton wrote: > Hi, > > On 5/2/22 22:53, Chris Murphy wrote: > > On Mon, May 2, 2022 at 5:29 PM Jeremy Linton > wrote: > >> > >> On 4/6/22 12:57, Neal Gompa wrote: > >> (trimming) > >>> * NVIDIA graphics > >>> * Broadcom wireless > >>> > >>> The former case

Re: Third-party repositories and Fedora

On Mon, May 02, 2022 at 10:51:10PM +0200, Fabio Valentini wrote: > On a related note: > I've had a package stuck in package review, because the reviewer > (rightfully) wanted clarification whether we could ship some files. > We blocked the FE-Legal bug in bugzilla on the review bug over a month > a

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

On Mon, 2022-05-02 at 19:33 +0200, Clemens Lang wrote: > This is the reason why the proposal contains extensive methods to test > whether things are going to break by modifying the crypto-policy or using > bpftrace. Unfortunately there are hundreds of packages that depend on > cryptographic librari

[HEADS UP] Fedora 37 Boost 1.78 rebuilds starting in a side tag

We are starting the rebuilds forhttps://fedoraproject.org/wiki/Changes/F37Boost178 in the f37-boost side tag. If your package depends on Boost, or just if you see a "Rebuilt for Boost 1.78" commit pushed to your package's dist-git repo, please c

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

On 5/3/22 18:41, David Woodhouse wrote: > On Mon, 2022-05-02 at 19:33 +0200, Clemens Lang wrote: >> This is the reason why the proposal contains extensive methods to test >> whether things are going to break by modifying the crypto-policy or using >> bpftrace. Unfortunately there are hundreds of pa