Missing expected images:
Minimal raw-xz armhfp
Compose PASSES proposed Rawhide gating check!
All required tests passed
Failed openQA tests: 11/163 (aarch64), 11/233 (x86_64)
New failures (same test not failed in Fedora-Rawhide-20220624.n.1):
ID: 1306578 Test: aarch64 Cloud_Base-qcow2-qcow2
On Sat, Jun 25, 2022 at 4:14 PM Demi Marie Obenour
wrote:
>
> On 6/25/22 07:56, Roberto Ragusa wrote:
> > On 6/19/22 22:54, Sharpened Blade via devel wrote:
> >
> >> Use unified kernel images by default for new releases. This can allow for
> >> the local installation to sign the kernel and the in
On 6/25/22 06:59, Richard Shaw wrote:
Fail2ban works fine in F35 but now has an SELinux problem in F36[1]...
While not a SELinux expert I can often reason things out but the
"unconfined" stuff confuses me.
type=AVC msg=audit(1655618425.791:3076): avc: denied { connectto } for
pid=1286608
OLD: Fedora-Rawhide-20220624.n.1
NEW: Fedora-Rawhide-20220625.n.0
= SUMMARY =
Added images:2
Dropped images: 1
Added packages: 1
Dropped packages:0
Upgraded packages: 17
Downgraded packages: 0
Size of added packages: 8.75 MiB
Size of dropped packages:0 B
On 6/25/22 07:56, Roberto Ragusa wrote:
> On 6/19/22 22:54, Sharpened Blade via devel wrote:
>
>> Use unified kernel images by default for new releases. This can allow for
>> the local installation to sign the kernel and the initrd, so the boot chain
>> can be verified until after the uefi.
>
>
On Wed, 2022-06-22 at 08:52 -0700, Kevin Fenzi wrote:
> On Tue, Jun 21, 2022 at 01:47:33PM -0500, Maxwell G via devel wrote:
> > On Monday, June 20, 2022 10:02:00 AM CDT Sérgio Basto wrote:
> > > Is is possible include builds of one side-tag into other side-tag
> > > ?
> >
> > It is also possible
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 Committee.
== Summary ==
The `systemd-udev` package installs
Up to a couple days ago, mock and fedora-review were working fine for
me, but just recently I have started getting permission errors:
```
...
Building target platforms: x86_64
Building for target x86_64
setting SOURCE_DATE_EPOCH=1656028800
RPM build errors:
error: error creating temporary file /
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 Committee.
== Summary ==
This change is to promote Fedora Cor
On Saturday, June 25, 2022 9:46:17 AM CDT Benjamin Beasley wrote:
> what happens if you end up doing the mass rebuild
> with a pre-release version? Would you need to do a second mass rebuild with
> the final version between the beta and final freezes?
Yes. as go binaries are statically linked, if
The License field for python-chardet has been corrected from LGPLv2 to
LGPLv2+, as all of the source file header comments have the requisite
“or […] any later version” language. A PR was sent upstream[1] to
clarify the trove classifier in the Python package metadata.
– Ben
[1] https://github.
Hi,
Ben Beasley writes:
> However, dropping the -devel package is almost as drastic as simply
> retiring the OpenSSL 1.1 package altogether. Grepping spec files for
> 'BuildRequires:.*openssl1' turns up the following packages that would
> immediately FTBFS:
> ...
> - dotnet3.1
> ...
This packag
I imagine I could answer this myself by looking carefully at the history of the
golang package, but what happens if you end up doing the mass rebuild with a
pre-release version? Would you need to do a second mass rebuild with the final
version between the beta and final freezes?
The Beta Freeze
On Sat, 2022-06-25 at 12:01 +0200, Miro Hrončok wrote:
> docker-compose
docker-compose is not updated [1] since May 11, 2021, and we haven't
new versions of 2.x.
I think we should think in rules about packages which have gaps more
than one year and what rules we should add to avoid these gaps, I
s
On 6/19/22 22:54, Sharpened Blade via devel wrote:
Use unified kernel images by default for new releases. This can allow for the
local installation to sign the kernel and the initrd, so the boot chain can be
verified until after the uefi.
How big is the demand for this kind of lockdown?
As a
Hello folks,
I've just orphaned python-chardet. I maintained it as a dependency of requests,
but requests use python-charset-normalizer instead now.
I recommend any dependency to migrate as well.
The package is in good shape, it builds and installs fine.
There is one update pending (reported
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)
ID: 1306223 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/1306223
ID: 1306227 Test: aarch64 Cloud_B
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)
ID: 1306207 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://openqa.fedoraproject.org/tests/1306207
ID: 1306211 Test: aarch64 Cloud_B
18 matches
Mail list logo
