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-20220219.0):
ID: 1137653 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://op
Il 19/02/22 19:38, Björn Persson ha scritto:
> Zbigniew Jędrzejewski-Szmek wrote:
>> I think it'd be better to check the status weekly and only require
>> account reconfirmation if the quarantine status is detected ⌊N / 7 - 1⌋
>> times in a row (where N=quarantine length in days).
> It will be fine
OLD: Fedora-Rawhide-20220219.n.0
NEW: Fedora-Rawhide-20220220.n.0
= SUMMARY =
Added images:1
Dropped images: 0
Added packages: 1
Dropped packages:0
Upgraded packages: 118
Downgraded packages: 0
Size of added packages: 10.59 KiB
Size of dropped packages:0
I'm running a package review request for a package which uses suid and
rpmlint complaints that it is not using hardened build flags. However,
the specfile doesn't explicitly disable them with %undefine _hardened_build.
Looking at the build log of this one [1] I see that export CFLAGS and
other fla
Missing expected images:
Iot dvd x86_64
Iot dvd aarch64
Failed openQA tests: 3/16 (x86_64), 2/15 (aarch64)
Old failures (same test failed in Fedora-IoT-37-20220219.0):
ID: 1138115 Test: x86_64 IoT-dvd_ostree-iso iot_clevis
URL: https://openqa.fedoraproject.org/tests/1138115
ID: 1138116
No missing expected images.
Soft failed openQA tests: 1/8 (aarch64), 1/8 (x86_64)
(Tests completed, but using a workaround for a known bug)
New soft failures (same test not soft failed in Fedora-Cloud-34-20220219.0):
ID: 1138074 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi
URL:
On 20. 02. 22 8:09, Adam Williamson wrote:
On Sun, 2022-02-20 at 00:39 +0100, Miro Hrončok wrote:
On 16. 02. 22 9:03, Adam Williamson wrote:
Full version: gnome-shell and mutter 42~beta builds were run yesterday.
For Fedora 36 they were done in a sidetag, but for Rawhide, no sidetag
yet existed
Missing expected images:
Minimal raw-xz armhfp
Compose FAILS proposed Rawhide gating check!
4 of 43 required tests failed, 4 results missing
openQA tests matching unsatisfied gating requirements shown with **GATING**
below
Failed openQA tests: 24/231 (x86_64), 26/161 (aarch64)
New failures (sa
On 2/20/22 05:00, Mattia Verga via devel wrote:
> Il 19/02/22 19:38, Björn Persson ha scritto:
>> Zbigniew Jędrzejewski-Szmek wrote:
>>> I think it'd be better to check the status weekly and only require
>>> account reconfirmation if the quarantine status is detected ⌊N / 7 - 1⌋
>>> times in a row
On Sun, Feb 20, 2022 at 4:01 PM Demi Marie Obenour
wrote:
> I think we should also require security key-based 2fa for all
> packagers.
In a previous discussion on this topic that was
suggested (and at least partially rejected(*)).
Many (larger) orgs have decided that issuing
hardware security k
Mattia Verga via devel wrote:
> Il 19/02/22 19:38, Björn Persson ha scritto:
> > Zbigniew Jędrzejewski-Szmek wrote:
> >> I think it'd be better to check the status weekly and only require
> >> account reconfirmation if the quarantine status is detected ⌊N / 7 - 1⌋
> >> times in a row (where N=qua
Demi Marie Obenour wrote:
> Security keys are the only form of 2fa that is immune to
> phishing attacks.
U2F and FIDO2 are said to be immune to phishing. HOTP, TOTP and various
proprietary challenge-respone protocols are not immune.
Björn Persson
pgp_7IhtLa4JI.pgp
Description: OpenPGP digital s
On 20/02/2022 11:31, Mattia Verga via devel wrote:
So, where -fPIE/-fPIC are supposed to be injected in build flags?
$ rpm -E %optflags
-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches
-pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2
-Wp,-D_GLIBCXX_ASSERTIONS
> I'm running a package review request for a package which uses suid and
> rpmlint complaints that it is not using hardened build flags. However,
> the specfile doesn't explicitly disable them with %undefine _hardened_build.
>
> Looking at the build log of this one [1] I see that export CFLAGS and
Il 20/02/22 19:10, Peter Robinson ha scritto:
>> I'm running a package review request for a package which uses suid and
>> rpmlint complaints that it is not using hardened build flags. However,
>> the specfile doesn't explicitly disable them with %undefine _hardened_build.
>>
>> Looking at the buil
Il 20/02/22 18:51, Vitaly Zaitsev via devel ha scritto:
> On 20/02/2022 11:31, Mattia Verga via devel wrote:
>> So, where -fPIE/-fPIC are supposed to be injected in build flags?
> $ rpm -E %optflags
> -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches
> -pipe -Wall -Werror=forma
OLD: Fedora-36-20220219.n.0
NEW: Fedora-36-20220220.n.0
= SUMMARY =
Added images:1
Dropped images: 0
Added packages: 1
Dropped packages:0
Upgraded packages: 107
Downgraded packages: 0
Size of added packages: 10.51 KiB
Size of dropped packages:0 B
Size of
No missing expected images.
Failed openQA tests: 3/16 (x86_64), 2/15 (aarch64)
Old failures (same test failed in Fedora-IoT-36-20220219.0):
ID: 1138947 Test: x86_64 IoT-dvd_ostree-iso iot_clevis
URL: https://openqa.fedoraproject.org/tests/1138947
ID: 1138948 Test: x86_64 IoT-dvd_ostree-i
I've just pushed zchunk-1.2.0 to all active Fedora branches, and it's
passed the (admittedly non-comprehensive) zchunk test suite, but I'm
seeing 2 OpenQA failed tests in Bodhi:
https://bodhi.fedoraproject.org/updates/FEDORA-2022-e4bcaeea7a
https://bodhi.fedoraproject.org/updates/FEDORA-2022-a3da9
No missing expected images.
Failed openQA tests: 92/229 (x86_64), 60/161 (aarch64)
New failures (same test not failed in Fedora-36-20220219.n.0):
ID: 1138743 Test: x86_64 Workstation-upgrade gnome_text_editor
URL: https://openqa.fedoraproject.org/tests/1138743
ID: 1138820 Test: x86_64 un
Hi
Following recent discussions and to reduce the maintenance burden, I'm
planning to start merging native and mingw packages. Initially, I'll be
looking at these packages where I maintain both variants:
eigen3 mingw-eigen3
enchant2 mingw-enchant2
freeimage mingw-freeimage
gdal mingw-gdal
Geo
On Sun, 2022-02-20 at 20:26 +, Jonathan Dieter wrote:
> I've just pushed zchunk-1.2.0 to all active Fedora branches, and it's
> passed the (admittedly non-comprehensive) zchunk test suite, but I'm
> seeing 2 OpenQA failed tests in Bodhi:
>
> https://bodhi.fedoraproject.org/updates/FEDORA-2022-
On Sun, 2022-02-20 at 16:42 +, Gary Buhrmaster wrote:
> Unfortunately, last I checked, the FAS account
> system did not support adding something
> like a FIDO2 security key to an account(**).
> Even if it did, I suspect not all the other parts
> of the system would support FIDO keys.
It used t
On Sun, Feb 20, 2022, 16:09 Adam Williamson
wrote:
> It used to support these, but the support was lost with the recent
> rewrite. However, it supports Google Authenticator-style OTPs. Folks
> with infra privileges on their accounts (like me) are already required
> to use these. It works fine. I
Hi all,
I am currently trying to open a UI / UX review of the FMN /
Notifications system and just chasing isome raw feedback on how you
all get notifications (email / IRC / or otherwise) when developing /
packaging / working on Fedora.
Please check out the following discussion thread to log your
On Sun, Feb 20, 2022 at 04:43:13PM -0800, Gary Buhrmaster wrote:
> On Sun, Feb 20, 2022, 16:09 Adam Williamson
> wrote:
>
> > It used to support these, but the support was lost with the recent
> > rewrite. However, it supports Google Authenticator-style OTPs. Folks
> > with infra privileges on th
Hi, Thanks for your suggestion, and I will rework my package based on your
comments. A question by the way: I built an epel package on CentOS7, my package
will depend on cmake 3.18 when it is building___
devel mailing list -- devel@lists.fedoraproject.o
27 matches
Mail list logo