Following is the list of topics that will be discussed in the FPC
meeting Thursday at 2022-03-10 17:00 UTC in #fedora-meeting-1 on
irc.libera.chat.
Local time information (via. uitime):
= Day: Thursday ==
2022-03-10 09:00 PST US/Pacific
2022-03-10 12
Peter Boy (p...@uni-bremen.de) said:
> And, by the way, it is one of Linux’s (and Fedora Linux’s) core
> distinguishing features that it does not follow the short-term commercial
> life cycles, but enables long-term usability, for "old" hardware as well
> as software. And we should not give that
On Wed, Mar 09, 2022 at 06:05:06PM +0100, Fabio Valentini wrote:
> On Wed, Mar 9, 2022 at 5:55 PM Miro Hrončok wrote:
>
> (...)
>
> > OK then, I can +1 that, but please: Make that more obvious in the proposal.
>
> Honest question: How do I do that? Do you have a suggestion?
Drop this part:
Leigh Scott kirjoitti 9.3.2022 klo 18.15:
Sérgio Basto kirjoitti 7.3.2022 klo 18.17:
Crossfire and freedroidrpg are games, so "is it needed?" and
"does it
have a replacement?" are not good questions to ask. A better question
would be "does anybody want to play it?". Games do not really ever
becom
Excerpts from Dan Callaghan's message of 2022-03-06 20:13:26 +11:00:
> python-phonenumbers
I took python-phonenumbers back. I forgot that it's in the dependency
chain of matrix-synapse which I very much still use.
--
Dan Callaghan
___
devel mailing li
On Wed, Mar 09, 2022 at 19:58:30 -,
Leigh Scott wrote:
On Wed, Mar 09, 2022 at 09:06:01 -0600,
Chris Adams
That is a very poor excuse for a slip, why would any one need it?
That is specified in the release criteria. I believe the rational is covered
there if you are really intereste
On Mon, 2022-03-07 at 12:44 -0500, Josh Boyer wrote:
> Hi Fedora, CentOS, and EPEL Communities!
>
> As part of our continued 3 year major Red Hat Enterprise Linux
> release
> cadence, RHEL 9 development is starting to wrap up with the spring
> 2022 release coming soon. That means planning for the
Realizing I probably didn’t include some important information, but -fPIC is in
fact being included in the compiler flags. For completeness, this is the
command that is failing:
/home/rolson/rpmbuild/BUILD/swift-source/build/buildbot_linux/llvm-linux-x86_64/./bin/clang++
-fPIC -O2 -flto=auto -f
Hey all-
Building swiftlang on F36/Rawhide results in a a failure that, boiled down to
its essence, appears to be:
/usr/bin/ld: /tmp/lto-llvm-4fd0b1.o: relocation R_X86_64_PC32 against undefined
symbol `__libc_stack_end' can not be used when making a shared object;
recompile with -fPIC
It com
On 03.03.22 11:29, Sandro Mani wrote:
Hi
I'm planing on landing tesseract-5.1.0 and proj-9.0.0 in rawhide and
F36 in the coming days. I'm doing a test run in these COPR repos:
tesseract: https://copr.fedorainfracloud.org/coprs/smani/tesseract5/
(all builds already complete)
proj: https://c
Hi Jerry,
On Fri, Mar 04, 2022 at 05:23:40PM -0700, Jerry James wrote:
> This message is for those of you who have expressed an interest in
> packaging Facebook's Infer code analysis tool. There is now a COPR
> repo available with, I think, all of the dependencies in it. Create
> ~/.config/mock/
> On Wed, Mar 09, 2022 at 09:06:01 -0600,
> Chris Adams
> The Fedora 36 beta is likely to slip because firefox was not building
> successfully on i686, but was on other arches.
That is a very poor excuse for a slip, why would any one need it?
Why not add an ExcludeArch to fix?
__
On Wed, Mar 09, 2022 at 12:23:41 -0600,
Bruno Wolff III wrote:
On Wed, Mar 09, 2022 at 09:06:01 -0600,
The Fedora 36 beta is likely to slip because firefox was not building
successfully on i686, but was on other arches.
It is actually more complicated than I remembered. Firefox needed a gcc
On 3/9/22 08:52, Alexander Sosedkin wrote:
> On Wed, Mar 9, 2022 at 2:47 PM Richard W.M. Jones wrote:
>>
>> Previous tightening of crypto defaults caused problems with us
>> connecting to older ssh servers.
>>
>> I am particularly interested / worried about sshd from RHEL 5, 6 & 7
>> for virt-p2v
On Wed, Mar 9, 2022 at 7:19 PM Daniel P. Berrangé wrote:
>
> On Wed, Mar 09, 2022 at 01:05:38PM -0500, Matthew Miller wrote:
> > On Wed, Mar 09, 2022 at 05:40:50PM +, Daniel P. Berrangé wrote:
> > > > But: maybe if we logged it _and_ had a tool people could run to
> > > > look specifically for
On Wed, Mar 09, 2022 at 07:13:14PM +0100, Alexander Sosedkin wrote:
> On Wed, Mar 9, 2022 at 7:05 PM Daniel P. Berrangé wrote:
> >
> > On Wed, Mar 09, 2022 at 06:45:49PM +0100, Alexander Sosedkin wrote:
> > > On Wed, Mar 9, 2022 at 6:22 PM Matthew Miller
> > > wrote:
> > > >
> > > > On Wed, Mar
On Wed, Mar 09, 2022 at 09:06:01 -0600,
Chris Adams wrote:
So I guess this is the part I don't really understand (and I guess why I
don't see this proposal as a "win") - how is i686 painful to package
maintainers for non-delivered packages? Maybe I'm just missing
something, but what causes is
On Wed, Mar 09, 2022 at 01:05:38PM -0500, Matthew Miller wrote:
> On Wed, Mar 09, 2022 at 05:40:50PM +, Daniel P. Berrangé wrote:
> > > But: maybe if we logged it _and_ had a tool people could run to
> > > look specifically for those log entries, we could do something like a Test
> > > Day wher
On Wed, Mar 9, 2022 at 7:05 PM Daniel P. Berrangé wrote:
>
> On Wed, Mar 09, 2022 at 06:45:49PM +0100, Alexander Sosedkin wrote:
> > On Wed, Mar 9, 2022 at 6:22 PM Matthew Miller
> > wrote:
> > >
> > > On Wed, Mar 09, 2022 at 12:14:28PM +0100, Alexander Sosedkin wrote:
> > > > I left my crystal
Benjamin Berg writes:
> On Wed, 2022-03-09 at 12:35 -0500, Robbie Harwood wrote:
>
>> Speaking of which, what *are* we expected to do? Aleksei on IRC
>> suggested that the preferred solution is to swap the BuildRequires to
>> pkgconfig(libusb) - is that right? Is this going to stick around, or
On Wed, Mar 09, 2022 at 05:40:50PM +, Daniel P. Berrangé wrote:
> > But: maybe if we logged it _and_ had a tool people could run to
> > look specifically for those log entries, we could do something like a Test
> > Day where people could send in reports?
>
> Or just have it logging in rawhide,
On Wed, Mar 09, 2022 at 06:45:49PM +0100, Alexander Sosedkin wrote:
> On Wed, Mar 9, 2022 at 6:22 PM Matthew Miller
> wrote:
> >
> > On Wed, Mar 09, 2022 at 12:14:28PM +0100, Alexander Sosedkin wrote:
> > > I left my crystal ball at home today,
> > > but I don't need it to say it'd be ~0 bugs fil
Hi,
On Wed, 2022-03-09 at 12:35 -0500, Robbie Harwood wrote:
> Hi, today I went to build grub2 in rawhide and got this:
>
> DEBUG util.py:444: No matching package to install: 'libusb-devel'
>
> grub2 has a `BuildRequires: libusb-devel`, and suddenly that package
> doesn't exist anymore. li
On Wed, Mar 9, 2022 at 6:22 PM Matthew Miller wrote:
>
> On Wed, Mar 09, 2022 at 12:14:28PM +0100, Alexander Sosedkin wrote:
> > I left my crystal ball at home today,
> > but I don't need it to say it'd be ~0 bugs filed if we log to syslog
> > and ~3 if we log to stderr/stdout, all named
> > "$CRY
On Wed, Mar 09, 2022 at 12:21:18PM -0500, Matthew Miller wrote:
> On Wed, Mar 09, 2022 at 12:14:28PM +0100, Alexander Sosedkin wrote:
> > I left my crystal ball at home today,
> > but I don't need it to say it'd be ~0 bugs filed if we log to syslog
> > and ~3 if we log to stderr/stdout, all named
>
On Tue, Mar 08, 2022 at 04:28:58PM -0600, Michael Cronenworth wrote:
> On 3/8/22 4:08 PM, Kevin Fenzi wrote:
> > Perhaps you could share with the list how used/important wine.i686 is
> > these days? Are most folks still using it? Slowly switching to
> > wine.x86_64?
>
> Yes, wine.i686 is still imp
Hi, today I went to build grub2 in rawhide and got this:
DEBUG util.py:444: No matching package to install: 'libusb-devel'
grub2 has a `BuildRequires: libusb-devel`, and suddenly that package
doesn't exist anymore. libusb was apparently dead.package'd two days
ago.
So this is sudden, and I
On Wed, Mar 9, 2022 at 4:40 PM Robbie Harwood wrote:
>
> Alexander Sosedkin writes:
>
> > Daniel P. Berrangé wrote:
> >
> >> Perhaps a useful first step is to just modify the three main
> >> crypto libs (gnutls, openssl, and nss) to send a scary warnihg
> >> message to stderr/syslog any time the
Minutes:
https://meetbot.fedoraproject.org/fedora-meeting-1/2022-03-09/fedora_coreos_meeting.2022-03-09-16.30.html
Minutes (text):
https://meetbot.fedoraproject.org/fedora-meeting-1/2022-03-09/fedora_coreos_meeting.2022-03-09-16.30.txt
Log:
https://meetbot.fedoraproject.org/fedora-meeting-1/2022
On Wed, Mar 09, 2022 at 12:14:28PM +0100, Alexander Sosedkin wrote:
> I left my crystal ball at home today,
> but I don't need it to say it'd be ~0 bugs filed if we log to syslog
> and ~3 if we log to stderr/stdout, all named
> "$CRYPTOLIB has no business messing up my stderr/stdout",
> which we'll
On Wed, Mar 9, 2022 at 6:05 PM Richard Shaw wrote:
(snip)
> I'll add some context to these. I'm currently the primary maintainer of three
> major projects in the VFX stack, OpenImageIO, OpenColorIO, and OpenEXR. Do we
> really need i686/arm packages for these? No one is using the 32bit version
On Wed, Mar 9, 2022 at 5:55 PM Miro Hrončok wrote:
(...)
> OK then, I can +1 that, but please: Make that more obvious in the proposal.
Honest question: How do I do that? Do you have a suggestion?
The proposal already does not contain anything language that could be
interpreted as "this will be
On Wed, Mar 9, 2022 at 10:09 AM Ben Beasley wrote:
> The packaging effort is real; it’s just unevenly distributed across
> different types of packages, so some packagers might not have noticed it.
>
> Packaging work that, with the demise of 32-bit ARM, can now be ascribed
> purely to these gener
On 09. 03. 22 15:51, Fabio Valentini wrote:
On Tue, Mar 8, 2022 at 9:57 PM Miro Hrončok wrote:
(snip)
I think we are all misinterpreting the intention of this change proposal.
We are suggesting better ways to get rid of i686. And the arguments are valid.
However, I now think that this change
Hello,
python-setuptools 60.9.x will be shipped to Rawhide on Friday, Mar 11.
During the efforts to integrate the new version to Fedora we have
discovered ~25 affected packages.
Wherever it was straightforward to fix, I sent a Pull Request directly
to the package repository in Fedora's dist-git. F
> On Tue, 2022-03-08 at 16:01 +, Leigh Scott wrote:
>
> Hi Leigh ,
> yes , it looks like glib-devel is not needed , I'm curious , how do you
> find these mistakes ?
>
> Thank you
I checked the built rpm requires and did mock test builds.
___
devel
> Sérgio Basto kirjoitti 7.3.2022 klo 18.17:
> Crossfire and freedroidrpg are games, so "is it needed?" and
> "does it
> have a replacement?" are not good questions to ask. A better question
> would be "does anybody want to play it?". Games do not really ever
> become obsolete, each is a unique
The packaging effort is real; it’s just unevenly distributed across different
types of packages, so some packagers might not have noticed it.
Packaging work that, with the demise of 32-bit ARM, can now be ascribed purely
to these generally-unused i686 packages includes:
- As Fabio noted, occas
On Tue, Mar 08, 2022 at 05:51:35PM +, Richard W.M. Jones wrote:
> On Tue, Mar 08, 2022 at 01:41:30AM +0100, Kevin Kofler via devel wrote:
> > Michael Catanzaro wrote:
> > > The maintainer is unwilling to retire them.
> > >
> > > I think we should ask FESCo to force them to be retired. It's con
Alexander Sosedkin writes:
> Daniel P. Berrangé wrote:
>
>> Perhaps a useful first step is to just modify the three main
>> crypto libs (gnutls, openssl, and nss) to send a scary warnihg
>> message to stderr/syslog any time they get use of SHA1 in a
>> signature. Leave that active for a release
No missing expected images.
Failed openQA tests: 13/161 (aarch64), 7/229 (x86_64)
New failures (same test not failed in Fedora-36-20220308.n.0):
ID: 1166793 Test: aarch64 Server-dvd-iso install_vncconnect_client@uefi
URL: https://openqa.fedoraproject.org/tests/1166793
ID: 1166794 Test: a
On Wednesday, 09 March 2022 at 15:59, Chris Adams wrote:
[...]
> I am very much not a UI/UX person, but Firefox and other browsers really
> could use a good way to override system crypto policy on a per-site
> basis.
Have you opened a ticket in Firefox bugzilla?
Regards,
Dominik
--
Fedora http
On Wed, Mar 9, 2022 at 4:06 PM Chris Adams wrote:
>
> Once upon a time, Fabio Valentini said:
> > Package maintainers who would benefit from dropping i686 from their
> > packages probably already know that i686 is painful for them.
>
> So I guess this is the part I don't really understand (and I
Missing expected images:
Minimal raw-xz armhfp
Compose PASSES proposed Rawhide gating check!
All required tests passed
Failed openQA tests: 15/231 (x86_64), 16/161 (aarch64)
New failures (same test not failed in Fedora-Rawhide-20220308.n.0):
ID: 1166276 Test: x86_64 Workstation-live-iso ap
Once upon a time, Fabio Valentini said:
> Package maintainers who would benefit from dropping i686 from their
> packages probably already know that i686 is painful for them.
So I guess this is the part I don't really understand (and I guess why I
don't see this proposal as a "win") - how is i686
Once upon a time, Richard W.M. Jones said:
> Previous tightening of crypto defaults caused problems with us
> connecting to older ssh servers.
I also have had trouble connecting to major vendor websites. The vendor
response is just "works in Chrome and Firefox on Windows, must be your
problem".
On Tue, Mar 8, 2022 at 9:57 PM Miro Hrončok wrote:
(snip)
> I think we are all misinterpreting the intention of this change proposal.
>
> We are suggesting better ways to get rid of i686. And the arguments are valid.
> However, I now think that this change proposal was not proposed to get rid of
On Wed, Mar 09, 2022 at 02:54:40PM +0100, Dmitry Belyavskiy wrote:
> At least RHEL 6 issues can be fixed server-side generating an ecdsa key...
If you can log in ...
This doesn't really work for us because of the way virt-v2v works --
it wants to ssh to the RHEL 5/6/7 server to fetch some files w
No missing expected images.
Failed openQA tests: 2/15 (x86_64), 1/15 (aarch64)
Old failures (same test failed in Fedora-IoT-36-20220308.0):
ID: 1167131 Test: x86_64 IoT-dvd_ostree-iso iot_zezere_server@uefi
URL: https://openqa.fedoraproject.org/tests/1167131
ID: 1167143 Test: x86_64 IoT-
At least RHEL 6 issues can be fixed server-side generating an ecdsa key...
On Wed, Mar 9, 2022 at 2:47 PM Richard W.M. Jones wrote:
> Previous tightening of crypto defaults caused problems with us
> connecting to older ssh servers.
>
> I am particularly interested / worried about sshd from RHEL
On Wed, Mar 9, 2022 at 2:47 PM Richard W.M. Jones wrote:
>
> Previous tightening of crypto defaults caused problems with us
> connecting to older ssh servers.
>
> I am particularly interested / worried about sshd from RHEL 5, 6 & 7
> for virt-p2v and virt-v2v conversions. This broke before, requi
On Tuesday, 08 March 2022 at 23:08, Kevin Fenzi wrote:
> On Mon, Mar 07, 2022 at 03:54:25PM -0600, Michael Cronenworth wrote:
> > On 3/7/22 2:03 PM, Neal Gompa wrote:
> > > A simpler solution would be to just default-off i686 and check-in some
> > > marker file that indicates the package needs to b
Previous tightening of crypto defaults caused problems with us
connecting to older ssh servers.
I am particularly interested / worried about sshd from RHEL 5, 6 & 7
for virt-p2v and virt-v2v conversions. This broke before, requiring
us to advise users to set the global policy for the machine to L
On ke, 09 maalis 2022, Daniel P. Berrangé wrote:
On Wed, Mar 09, 2022 at 02:32:48PM +0200, Alexander Bokovoy wrote:
On ke, 09 maalis 2022, Daniel P. Berrangé wrote:
> On Wed, Mar 09, 2022 at 10:46:21AM +0100, Alexander Sosedkin wrote:
> > On Wed, Mar 9, 2022 at 10:20 AM Daniel P. Berrangé
wrot
On Wed, Mar 09, 2022 at 02:32:48PM +0200, Alexander Bokovoy wrote:
> On ke, 09 maalis 2022, Daniel P. Berrangé wrote:
> > On Wed, Mar 09, 2022 at 10:46:21AM +0100, Alexander Sosedkin wrote:
> > > On Wed, Mar 9, 2022 at 10:20 AM Daniel P. Berrangé
> > > wrote:
> > > >
> > > > On Tue, Mar 08, 2022
OLD: Fedora-36-20220308.n.0
NEW: Fedora-36-20220309.n.0
= SUMMARY =
Added images:0
Dropped images: 0
Added packages: 0
Dropped packages:0
Upgraded packages: 0
Downgraded packages: 0
Size of added packages: 0 B
Size of dropped packages:0 B
Size of upgraded
On ke, 09 maalis 2022, Daniel P. Berrangé wrote:
On Wed, Mar 09, 2022 at 10:46:21AM +0100, Alexander Sosedkin wrote:
On Wed, Mar 9, 2022 at 10:20 AM Daniel P. Berrangé wrote:
>
> On Tue, Mar 08, 2022 at 07:40:15PM +0100, Alexander Sosedkin wrote:
> > We've been disabling it in TLS, but its usag
Announcing the creation of a new nightly release validation test event
for Fedora 36 Branched 20220309.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
Em seg., 7 de mar. de 2022 às 18:22, Jerry James
escreveu:
>
> As you all know by now, I'm trying to retire as steward of the
> sagemath and Macaulay2 stacks. Nevertheless, after some impassioned
Many thanks for your work maintaining sagemath!
> pleas from a couple of sagemath users, I have p
On Tue, 2022-03-08 at 16:01 +, Leigh Scott wrote:
> > On Mon, 07 Mar 2022 10:29:02 -0600
> > Michael Catanzaro >
> >
> > I'm not unwilling to retire them, I just want their users to be
> > retired
> > first so I don't leave a bunch of broken dependencies behind.
> >
> > Paul.
>
> dillo, al
On Wed, 2022-03-09 at 08:20 +0200, Otto Urpelainen wrote:
> Sérgio Basto kirjoitti 7.3.2022 klo 18.17:
> > Hi,
> > In resume glib still required for 20 packages [1],
> > apart of the sweet memories that some package bring to us , any of
> > these packages is needed ? or haven't replacement ?
> >
On Wed, Mar 9, 2022 at 10:57 AM Daniel P. Berrangé wrote:
>
> On Wed, Mar 09, 2022 at 10:46:21AM +0100, Alexander Sosedkin wrote:
> > On Wed, Mar 9, 2022 at 10:20 AM Daniel P. Berrangé
> > wrote:
> > >
> > > On Tue, Mar 08, 2022 at 07:40:15PM +0100, Alexander Sosedkin wrote:
> > > > We've been d
OLD: Fedora-Rawhide-20220308.n.0
NEW: Fedora-Rawhide-20220309.n.0
= SUMMARY =
Added images:0
Dropped images: 0
Added packages: 6
Dropped packages:0
Upgraded packages: 127
Downgraded packages: 0
Size of added packages: 910.05 MiB
Size of dropped packages:0
Hi Mike,
If you're not in a hurry I can review them in the upcoming days.
Kind regards,
Mikel
Hau idatzi du W. Michael Petullo (m...@flyn.org) erabiltzaileak (2022
mar. 9, az. (04:40)):
>
> I would like to update Fedora's Hugo package, but the recent versions
> depend on Go packages not yet in F
On 3/9/22 04:48, Daniel P. Berrangé wrote:
> On Wed, Mar 09, 2022 at 10:44:28AM +0100, Miroslav Lichvar wrote:
>> On Tue, Mar 08, 2022 at 07:40:15PM +0100, Alexander Sosedkin wrote:
>>> Took git years to migrate from SHA-1, and some others haven't even started.
>>
>> git is a good example showing t
On Wed, Mar 09, 2022 at 10:46:21AM +0100, Alexander Sosedkin wrote:
> On Wed, Mar 9, 2022 at 10:20 AM Daniel P. Berrangé
> wrote:
> >
> > On Tue, Mar 08, 2022 at 07:40:15PM +0100, Alexander Sosedkin wrote:
> > > We've been disabling it in TLS, but its usage is much wider than TLS.
> > > The next
Hello,
I am orphaning perl-Math-Prime-XS, which I used to maintain for slic3r, but
appears no longer needed:
$ repoquery -q --repo=rawhide{,-source} --whatrequires perl-Math-Prime-XS
perl-Math-NumSeq-0:74-9.fc36.noarch
perl-Math-NumSeq-0:74-9.fc36.src
$ repoquery -q --repo=rawhide{,-source} -
On Wed, Mar 09, 2022 at 10:44:28AM +0100, Miroslav Lichvar wrote:
> On Tue, Mar 08, 2022 at 07:40:15PM +0100, Alexander Sosedkin wrote:
> > Took git years to migrate from SHA-1, and some others haven't even started.
>
> git is a good example showing that this won't be easy. The SHA-256
> object fo
On Wed, Mar 9, 2022 at 10:20 AM Daniel P. Berrangé wrote:
>
> On Tue, Mar 08, 2022 at 07:40:15PM +0100, Alexander Sosedkin wrote:
> > We've been disabling it in TLS, but its usage is much wider than TLS.
> > The next agonizing step is to restrict its usage for signatures
> > on the cryptographic l
On Tue, Mar 08, 2022 at 07:40:15PM +0100, Alexander Sosedkin wrote:
> Took git years to migrate from SHA-1, and some others haven't even started.
git is a good example showing that this won't be easy. The SHA-256
object format is still marked as experimental and not the default.
Is there a plan t
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-20220308.0):
ID: 1166200 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://op
On 09. 03. 22 8:57, Felix Schwarz wrote:
Hi Kevin,
Am 08.03.22 um 01:33 schrieb Kevin Kofler via devel:
There is actually a "mock shell" command that opens a shell inside the mock
chroot. You can also run arbitrary shell commands (including scripts that
you have previously manually copied in us
On Tue, Mar 8, 2022 at 8:52 PM Zbigniew Jędrzejewski-Szmek
wrote:
>
> On Tue, Mar 08, 2022 at 07:40:15PM +0100, Alexander Sosedkin wrote:
> > the only realistic way to weed out its reliance on SHA-1 signatures
> > from all of its numerous dark corners is to break them.
> > Make creation and verifi
Filed infra ticket:
https://pagure.io/fedora-infrastructure/issue/10585
On 3/9/22 09:08, Zdenek Dohnal wrote:
Hi all,
today I've found out F34 branch is already set as inactive in
dist-git, so every commit to the branch is rejected.
IMHO it is a bug, because the branch should become inactiv
On Tue, Mar 08, 2022 at 07:40:15PM +0100, Alexander Sosedkin wrote:
> We've been disabling it in TLS, but its usage is much wider than TLS.
> The next agonizing step is to restrict its usage for signatures
> on the cryptographic libraries level, with openssl being the scariest one.
>
> Good news i
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-20220308.0):
ID: 1166184 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud
URL: https://op
On Tue, Mar 08, 2022 13:34:26 -0700, Jerry James wrote:
> On Tue, Mar 8, 2022 at 1:17 PM Ankur Sinha wrote:
> > Hi folks,
> >
> > I'd like to get libsonata reviewed for inclusion in Fedora as part of
> > the NeuroFedora packages. Would anyone have any pending reviews they'd
> > like to swap please
Hi all,
today I've found out F34 branch is already set as inactive in dist-git,
so every commit to the branch is rejected.
IMHO it is a bug, because the branch should become inactive with F34
EOL, and right now we are in F36 Beta Freeze (about 2 months from
estimated F34 EOL [1]).
Does any
78 matches
Mail list logo
