Re: Proposal: gate stable release critical path updates on openQA test results

On Fri, 2021-01-08 at 23:26 +0100, Miro Hrončok wrote: > On 08. 01. 21 23:24, Matthew Miller wrote: > > On Fri, Jan 08, 2021 at 09:34:29PM +0100, Kevin Kofler via devel wrote: > > > > So if anything, I think this change is in line with your views here. > > > > > > Well, if (and as long as) the gat

Re: Proposal: gate stable release critical path updates on openQA test results

On Fri, 2021-01-08 at 21:34 +0100, Kevin Kofler via devel wrote: > Stephen Gallagher wrote: > > I think you've got this backwards, Kevin. This is about disabling the > > autopush if any of those tests fail. So the result would be that > > critical path packages would get 1) more testing before the

Re: F33: kernel 5.10.x

Yeah, I'm aware of alternative testing mechanisms and I already participated in the testing of kernel 5.10. That's not the problem. Kernel 5.9 is EOL. 5.10.5 fixes CVE-2020-36158, for example. There is no choice but to go to that branch now anyway. So, I am wondering whether there is some known bi

Re: Non-responsive maintainer check: tnorth (for autojump branch request)

On Fri, 2021-01-08 at 15:34 -0800, Michel Alexandre Salim wrote: > Hi, > > I'm initiating the non-responsive maintainer process for tnorth, > per  > https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/ > > An EPEL branch request has been open since November 19

Non-responsive maintainer check: tnorth (for autojump branch request)

Hi, I'm initiating the non-responsive maintainer process for tnorth, per  https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/ An EPEL branch request has been open since November 19 with no response. Does anyone know how to get in touch with him? Bugzilla: ht

Re: F33: kernel 5.10.x

Before be submitted in bodhi , we can test here: https://copr.fedorainfracloud.org/coprs/jforbes/kernel-stabilization On Fri, 2021-01-08 at 22:40 +, Bojan Smojver via devel wrote: > Just wondering whether there is a particular reason 5.10 kernel has > not been submitted for testing in bod

F33: kernel 5.10.x

Just wondering whether there is a particular reason 5.10 kernel has not been submitted for testing in bodhi for F33. Or is it simply an oversight? -- Bojan ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le

Re: Proposal: gate stable release critical path updates on openQA test results

On Fri, Jan 08, 2021 at 11:26:57PM +0100, Miro Hrončok wrote: > >>Well, if (and as long as) the gating only blocks the autopush and does not > >>prevent a manual push (as yet another requirement), I withdraw my objection. > > > >I think we should get to the point where it blocks manual pushes (with

Re: Proposal: gate stable release critical path updates on openQA test results

On 08. 01. 21 23:24, Matthew Miller wrote: On Fri, Jan 08, 2021 at 09:34:29PM +0100, Kevin Kofler via devel wrote: So if anything, I think this change is in line with your views here. Well, if (and as long as) the gating only blocks the autopush and does not prevent a manual push (as yet anoth

Re: Proposal: gate stable release critical path updates on openQA test results

On Fri, Jan 08, 2021 at 09:34:29PM +0100, Kevin Kofler via devel wrote: > > So if anything, I think this change is in line with your views here. > > Well, if (and as long as) the gating only blocks the autopush and does not > prevent a manual push (as yet another requirement), I withdraw my objec

Nmap Public Source License (NPSL) Version 0.92

After review, Fedora has determined that the Nmap Public Source License (NPSL) Version 0.92[1] is not acceptable for use in Fedora. We have updated our "Bad License" list[2] to include NPSL. No software under that license may be included in Fedora (including EPEL and COPRs). The license includes r

Fedora 35 Change: PHP 8.0 (Self-Contained Change proposal)

https://fedoraproject.org/wiki/Changes/php80 == Summary == Update the PHP stack in Fedora to latest version 8.0.x == Owner == * Name: [[User:Remi| Remi Collet]] and [[SIGs/PHP|PHP SIG]] * Email: remi at fedoraproject dot org == Detailed Description == Update the PHP stack in Fedora to latest v

Re: Proposal: gate stable release critical path updates on openQA test results

Stephen Gallagher wrote: > I think you've got this backwards, Kevin. This is about disabling the > autopush if any of those tests fail. So the result would be that > critical path packages would get 1) more testing before the existing > autopush occurs and 2) if any of those tests fail, it won't ge

Orphaned jabberpy

I orphaned: jabberpy This package was used by Spacewalk and RH no longer work on this project and I have no use for this package. -- Miroslav Suchy, RHCA Red Hat, Associate Manager, Community Packaging Tools, #brno, #fedora-buildsys ___ devel mailing l

Re: heads up: nss 3.59 breaks firefox add-ons

On Fri, Jan 08, 2021 at 06:41:36AM +0100, Onyeibo Oku wrote: > Is this still active? My Firefox plugins are getting disabled and I > cannot install new ones (they are reported as corrupt). Is there a new > instance of this bug? Yeah, it came back because as Adams says: https://bugzilla.redhat.co

Re: How to troubleshoot aarch64 and s390x?

On Thu, Dec 17, 2020 at 07:32:59AM -0600, Richard Shaw wrote: > I'm working on building the new openexr package but the unit tests are > failing > but just on aarch64 and s390x. > > The aarch64 test instances are down due to the infra move and there are none > for s390x. > > What's the best wa

Re: Fedora 34 Change: Signed RPM Contents (late System-Wide Change)

> * Peter Robinson: > > > If the signatures end up in RPM headers, they will land in the RPM > database, too. > > “rpm -qla | wc -l” shows around 28,589 files for me, in the Fedora 33 > container image. / seems to need 183 MiB right now. If the signatures > land in the RPM database and the fil

fedora-server: permanent meeting time?

Hello all, Looking at the reboot meeting logs, looks like we initially meant to reconvene on January 6, then pivoted to finding a next meeting time and avoid selection bias... then with the holidays that never happened. I've started a WhenIsGood, picking a timezone that should work for people fro

Re: Un-retire the package python-pyswip

On Friday, January 8, 2021 3:38:44 PM WET Christoph Karl wrote: > Hello everyone! > > I want to un-retire the package python-pyswip. > > According to "dead.package" the reason for retiring this package is/was: > "SWI Prolog (package pl) has been retired from Fedora, this package > provided Python

Re: Mass spec file change: Adding BuildRequires: make

On 11/30/20 2:06 PM, Tom Stellard wrote: Hi, As part of the f34 change request[1] for removing make from the buildroot, I will be doing a mass update of packages[2] to add BuildRequires: make where it is needed. If you are a package maintainer and would prefer to update your packages on you

Re: Chromium built in rawhide does not render most strings

Based on my (admittedly extremely limited) understanding of things, this seems correct as is: #if defined(__x86_64__) || defined(__aarch64__) case __NR_newfstatat: // fstatat(). EPERM not a valid errno. #elif defined(__i386__) || defined(__arm__) || \ (defined(ARCH_CPU_MIPS_FAMILY) && def

Un-retire the package python-pyswip

Hello everyone! I want to un-retire the package python-pyswip. According to "dead.package" the reason for retiring this package is/was: "SWI Prolog (package pl) has been retired from Fedora, this package provided Python bindings for SWI Prolog." I checked this with Jerry James (maintainer of SW

Re: Chromium built in rawhide does not render most strings

* Tom Callaway: > Looks like this might be it. Running with --no-sandbox brings back the > strings. Is there a reference to how the stat calls should now be > done? I suspect some of the preprocessor conditionals in SyscallSets::IsFileSystem in

Re: Proposal: gate stable release critical path updates on openQA test results

On Thu, Jan 7, 2021 at 6:26 PM Adam Williamson wrote: > Hey folks! > > So here's an idea I was thinking about over the RH shutdown: I propose > we gate stable release critical path updates on the openQA tests. > +1, awesome I'm glad I'm not going to be that person that everybody pokes when some

Re: Chromium built in rawhide does not render most strings

Looks like this might be it. Running with --no-sandbox brings back the strings. Is there a reference to how the stat calls should now be done? Thanks, ~spot On Fri, Jan 8, 2021 at 8:58 AM Florian Weimer wrote: > * Tom Callaway: > > > This makes me very suspicious of something in glibc between 2

Re: Fedora 34 Change: Ruby 3.0 (System-Wide Change)

Just to let everybody know, Ruby 3.0 has landed in Rawhide. The binary packages have been rebuilt, but there might be other compatibility issue. If you need help fixing your package, please come to discuss the issue to ruby-sig ML. Vít Dne 02. 12. 20 v 19:07 Ben Cotton napsal(a): https://f

Re: Chromium built in rawhide does not render most strings

* Daniel P. Berrangé: > On Fri, Jan 08, 2021 at 02:58:02PM +0100, Florian Weimer wrote: >> * Tom Callaway: >> >> > This makes me very suspicious of something in glibc between 2.32 >> > (Fedora 33) and 2.32.9000 (rawhide), but I'm not sure where to look >> > from here. Any ideas? >> >> Does the i

Re: Chromium built in rawhide does not render most strings

On Fri, Jan 08, 2021 at 02:58:02PM +0100, Florian Weimer wrote: > * Tom Callaway: > > > This makes me very suspicious of something in glibc between 2.32 > > (Fedora 33) and 2.32.9000 (rawhide), but I'm not sure where to look > > from here. Any ideas? > > Does the issue go away if you disable the

Re: Chromium built in rawhide does not render most strings

* Tom Callaway: > This makes me very suspicious of something in glibc between 2.32 > (Fedora 33) and 2.32.9000 (rawhide), but I'm not sure where to look > from here. Any ideas? Does the issue go away if you disable the Chromium sandbox? One difference is that the stat functions are called in a d

Non-responsive maintainer Eduardo Augusto Mayorga (mayorga)

Happy New Year everyone! I've tried to get in touch with Eduardo concerning co-maintainership of the python-rfc3987 package for EPEL8 a couple times at/after December 7th and haven't heard back from him. If anybody knows how to contact him other than via his email address stored in FAS (on Cc), p

Re: Fwd: Thoughts on the file system layout

Silverblue is already quite close to that proposal. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-c

Re: Proposal: gate stable release critical path updates on openQA test results

On Thu, Jan 7, 2021 at 9:09 PM Kevin Kofler via devel wrote: > > Adam Williamson wrote: > > So here's an idea I was thinking about over the RH shutdown: I propose > > we gate stable release critical path updates on the openQA tests. > > -1 > > We already enforce too strict requirements on updates,