Re: F37 change proposal: Make Fedora CoreOS a Fedora Edition (System-Wide change)

On Tue, Jul 5, 2022 at 9:43 PM Dusty Mabe wrote: > > > > On 7/5/22 17:03, Neal Gompa wrote: > > On Sat, Jun 25, 2022 at 2:17 PM Vipul Siddharth > > wrote: > >> > >> > >> == Feedback == > >> > >> This change was previously submitted for Fedora 34 and feedback were > >> collected in the following

[Bug 2101223] Please branch and build perl-Term-ReadLine-Gnu for EPEL 9

https://bugzilla.redhat.com/show_bug.cgi?id=2101223 Fedora Update System changed: What|Removed |Added Fixed In Version||perl-Term-ReadLine-Gnu-1.42

Re: F37 Change Proposal: MAC Address Policy none (System-Wide Change)

On 6/25/22 15:06, Vipul Siddharth wrote: > 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. >

Re: F37 change proposal: Make Fedora CoreOS a Fedora Edition (System-Wide change)

On 7/5/22 17:03, Neal Gompa wrote: > On Sat, Jun 25, 2022 at 2:17 PM Vipul Siddharth > wrote: >> >> >> == Feedback == >> >> This change was previously submitted for Fedora 34 and feedback were >> collected in the following [https://pagure.io/fesco/issue/2516 FESCo >> ticket]. >> The 2 main

[Bug 2104311] New: Please build perl-Test-CheckDeps for EPEL 9

https://bugzilla.redhat.com/show_bug.cgi?id=2104311 Bug ID: 2104311 Summary: Please build perl-Test-CheckDeps for EPEL 9 Product: Fedora EPEL Version: epel9 Hardware: All OS: Linux Status: NEW Component:

Re: You can't be serious! you want to remove mesa-libGL.i686 support?

On 06. 07. 22 1:17, Miro Hrončok wrote: On 06. 07. 22 0:14, Kevin Kofler via devel wrote: Stephen Smoogen wrote: Hyperbole aside, it isn't a joke. Looking at the chain we see a common problem where subversion relies on java-11-openjdk and without it is going to cause a lot of packages to be

Re: You can't be serious! you want to remove mesa-libGL.i686 support?

On 06. 07. 22 0:14, Kevin Kofler via devel wrote: Stephen Smoogen wrote: Hyperbole aside, it isn't a joke. Looking at the chain we see a common problem where subversion relies on java-11-openjdk and without it is going to cause a lot of packages to be removed. Either subversion needs to lose

Re: Orphaned packages looking for new maintainers​​

On 06. 07. 22 0:55, Davide Cavalca via devel wrote: On Wed, 2022-07-06 at 00:43 +0200, Miro Hrončok wrote: On 06. 07. 22 0:35, Fabio Valentini wrote: Additionally, your update didn't actually fix any of the problems that caused it to be orphaned in the first place ... Yeah, the f36 and f35

Re: Orphaned packages looking for new maintainers​​

On Wed, 2022-07-06 at 00:43 +0200, Miro Hrončok wrote: > On 06. 07. 22 0:35, Fabio Valentini wrote: > > > > Additionally, your update didn't actually fix any of the > > > > problems > > > > that > > > > caused it to be orphaned in the first place ... > > > > > > Yeah, the f36 and f35 updates

Re: Orphaned packages looking for new maintainers​​

On 06. 07. 22 0:35, Fabio Valentini wrote: On Wed, Jul 6, 2022 at 12:31 AM Davide Cavalca via devel wrote: On Tue, 2022-07-05 at 22:24 +0200, Fabio Valentini wrote: On Tue, Jul 5, 2022 at 10:18 PM Davide Cavalca via devel wrote: On Mon, 2022-07-04 at 13:41 +0200, Miro Hrončok wrote:

Re: Orphaned packages looking for new maintainers​​

On Wed, Jul 6, 2022 at 12:31 AM Davide Cavalca via devel wrote: > > On Tue, 2022-07-05 at 22:24 +0200, Fabio Valentini wrote: > > On Tue, Jul 5, 2022 at 10:18 PM Davide Cavalca via devel > > wrote: > > > > > > On Mon, 2022-07-04 at 13:41 +0200, Miro Hrončok wrote: > > > > rust-curve25519-dalek

Re: Orphaned packages looking for new maintainers​​

On Tue, 2022-07-05 at 22:24 +0200, Fabio Valentini wrote: > On Tue, Jul 5, 2022 at 10:18 PM Davide Cavalca via devel > wrote: > > > > On Mon, 2022-07-04 at 13:41 +0200, Miro Hrončok wrote: > > > rust-curve25519-dalek    orphan, rust- > > > sig  1 > > > weeks ago > > > >

Re: You can't be serious! you want to remove mesa-libGL.i686 support?

Stephen Smoogen wrote: > Hyperbole aside, it isn't a joke. Looking at the chain we see a common > problem where subversion relies on java-11-openjdk and without it is going > to cause a lot of packages to be removed. Either subversion needs to lose > that requirement or a lot of packages are going

Re: You can't be serious! you want to remove mesa-libGL.i686 support?

On Tue, Jul 5, 2022 at 11:34 PM Stephen Smoogen wrote: > > On Tue, 5 Jul 2022 at 17:26, Leigh Scott wrote: >> >> Is this some sick joke? >> >> https://bugzilla.redhat.com/show_bug.cgi?id=2104255 > > Hyperbole aside, it isn't a joke. Looking at the chain we see a common > problem where

Re: You can't be serious! you want to remove mesa-libGL.i686 support?

On Tue, 5 Jul 2022 at 17:26, Leigh Scott wrote: > Is this some sick joke? > > https://bugzilla.redhat.com/show_bug.cgi?id=2104255 Hyperbole aside, it isn't a joke. Looking at the chain we see a common problem where subversion relies on java-11-openjdk and without it is going to cause a lot of

Re: F37 proposal: Add -fno-omit-frame-pointer to default compilation flags (System-Wide Change proposal)

Fabio Valentini wrote: > And if we say this argument is valid, then should we also build all our > packages with ASAN / TSAN / etc. instrumentation, as well? And ASAN would actually have tangible benefits for end users, namely preventing some memory bug exploits, whereas frame pointers only slow

You can't be serious! you want to remove mesa-libGL.i686 support?

Is this some sick joke? https://bugzilla.redhat.com/show_bug.cgi?id=2104255 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct:

Re: F37 proposal: Officially Support Raspberry Pi 4 (Self-Contained Change proposal)

On 05. 07. 22 23:16, Ben Cotton wrote: The work around Raspberry Pi 4 has been on going for a number of years, but we've never officially supported it due to lack of accelerated graphics and other key features. A few of us have led the push to get the accelerated graphics work over the line

F37 proposal: Officially Support Raspberry Pi 4 (Self-Contained Change proposal)

https://fedoraproject.org/wiki/Changes/RaspberryPi4 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.

F37 proposal: LXQt 1.1.0 (Self-Contained Change proposal)

https://fedoraproject.org/wiki/Changes/LXQt_1.1 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. ==

F37 proposal: Officially Support Raspberry Pi 4 (Self-Contained Change proposal)

https://fedoraproject.org/wiki/Changes/RaspberryPi4 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.

F37 proposal: LXQt 1.1.0 (Self-Contained Change proposal)

https://fedoraproject.org/wiki/Changes/LXQt_1.1 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. ==

Re: F37 change proposal: Make Fedora CoreOS a Fedora Edition (System-Wide change)

On Sat, Jun 25, 2022 at 2:17 PM Vipul Siddharth wrote: > > > == Feedback == > > This change was previously submitted for Fedora 34 and feedback were > collected in the following [https://pagure.io/fesco/issue/2516 FESCo > ticket]. > The 2 main feedback received are either addressed or in the

Re: F37 proposal: Linux Firmware Minimization (late System-Wide Change proposal)

On Fri, Jul 1, 2022 at 9:47 PM Dusty Mabe wrote: > > > > On 7/1/22 18:14, Neal Gompa wrote: > > On Fri, Jul 1, 2022 at 2:10 PM Michael Catanzaro > > wrote: > >> > >> On Fri, Jul 1 2022 at 01:54:58 PM -0400, Ben Cotton > >> wrote: > >>> A DNF plugin will be written to make use of the

Nest with Fedora Registration Open (CfP still open until July 8th!)

Hi folks, Nest with Fedora 2022 registration is now open [0]! Make sure to register and share the link with Fedora Friends. The Nest CfP is open until July 8th(this Friday!), and we encourage Fedorans to submit the latest and greatest projects(as well as all the usual standbys, of course;)) to

Nest with Fedora Registration Open (CfP still open until July 8th!)

Hi folks, Nest with Fedora 2022 registration is now open [0]! Make sure to register and share the link with Fedora Friends. The Nest CfP is open until July 8th(this Friday!), and we encourage Fedorans to submit the latest and greatest projects(as well as all the usual standbys, of course;)) to

Re: Orphaned packages looking for new maintainers​​

On Tue, Jul 5, 2022 at 10:18 PM Davide Cavalca via devel wrote: > > On Mon, 2022-07-04 at 13:41 +0200, Miro Hrončok wrote: > > rust-curve25519-dalekorphan, rust-sig 1 > > weeks ago > > I took this one and just submitted an updated build for it. But why? Do you need

Re: Orphaned packages looking for new maintainers​​

On Mon, 2022-07-04 at 13:41 +0200, Miro Hrončok wrote: > rust-curve25519-dalek    orphan, rust-sig  1 > weeks ago I took this one and just submitted an updated build for it. Cheers Davide ___ devel mailing list --

Re: F37 proposal: Add -fno-omit-frame-pointer to default compilation flags (System-Wide Change proposal)

* Matthias Clasen: > not to mention hardware continuously getting faster too... The proposal is about enabling this feature for older hardware. Recent x86-64 CPUs can maintain an array of return addresses in hardware (so basically the backtrace is available directly). Kernel patches to enable

Re: F37 proposal: Add -fno-omit-frame-pointer to default compilation flags (System-Wide Change proposal)

On Tue, Jul 5, 2022 at 9:16 PM Matthias Clasen wrote: > > On Thu, Jun 30, 2022 at 4:55 AM Kevin Kofler via devel > wrote: >> >> Daan De Meyer via devel wrote: >> > Which shows a smaller than 1% slowdown between the binary built with frame >> > pointers and the binary built without frame

Re: F37 Change Proposal: Unfiltered Flathub (System-Wide Change)

Timothée Ravier wrote: > The two articles mentioned above all full of errors and misconceptions > about how Flatpak and Flathub works. > > See > https://theevilskeleton.gitlab.io/2022/05/16/response-to-flatpak-is-not-the-future.html Oh, I know that "response". That response fails to convincingly

Re: F37 proposal: Add -fno-omit-frame-pointer to default compilation flags (System-Wide Change proposal)

On Tue, Jul 5, 2022 at 3:40 PM Marek Polacek wrote: > > Maybe not, but even ~1% is still an unacceptable slowdown. It would take > about a year for the compiler to catch up. > > (Un)acceptable for whom? And why would it be unacceptable? You just said compilers will make up for it quickly, not

Re: F37 proposal: Add -fno-omit-frame-pointer to default compilation flags (System-Wide Change proposal)

On Tue, Jul 05, 2022 at 03:15:02PM -0400, Matthias Clasen wrote: > On Thu, Jun 30, 2022 at 4:55 AM Kevin Kofler via devel < > devel@lists.fedoraproject.org> wrote: > > > Daan De Meyer via devel wrote: > > > Which shows a smaller than 1% slowdown between the binary built with > > frame > > >

Re: F37 proposal: Add -fno-omit-frame-pointer to default compilation flags (System-Wide Change proposal)

On 7/5/22 06:06, Florian Weimer wrote: > * Daan De Meyer via devel: > >> Instead, we only saw differences from 0%-2% between Redis compiled >> with frame pointers and Redis compiled without frame pointers. These >> benchmarks were done using the phoronix-test-suite in exactly the same >> way as

[Bug 2104259] New: adapt perl to removal of java on i686

https://bugzilla.redhat.com/show_bug.cgi?id=2104259 Bug ID: 2104259 Summary: adapt perl to removal of java on i686 Product: Fedora Version: rawhide Status: NEW Component: perl Severity: high Assignee:

Re: F37 proposal: Add -fno-omit-frame-pointer to default compilation flags (System-Wide Change proposal)

Matthias Clasen wrote: > I am coming a bit late to this discussion, but I would like to inject the > viewpoint that 'performance' (however defined) > isn't the only criterion by which we should just judge what Fedora > produces. At least for Fedora Workstation, being > a useful system for

Re: F37 proposal: Add -fno-omit-frame-pointer to default compilation flags (System-Wide Change proposal)

On Thu, Jun 30, 2022 at 4:55 AM Kevin Kofler via devel < devel@lists.fedoraproject.org> wrote: > Daan De Meyer via devel wrote: > > Which shows a smaller than 1% slowdown between the binary built with > frame > > pointers and the binary built without frame pointers. > > I am still strongly

Retiring/orphaning my packages

I should have done this a long time ago; I don't have the time or energy to maintain my packages anymore  If anyone is interested in any of these, you're welcome to take them. https://src.fedoraproject.org/user/terrycloth/projects Applications: * BleachBit (bleachbit) -- delete traces of your

Re: Bugzilla: You can't ask Lennart Poettering because that account is disabled.

Am 03.07.22 um 19:33 schrieb Kevin Fenzi: On Sun, Jul 03, 2022 at 11:52:26AM +0200, Marius Schwarz wrote: Am 03.07.22 um 04:02 schrieb Neal Gompa: On Sat, Jul 2, 2022 at 8:52 PM Kevin Kofler via devel wrote: Kevin Kofler via devel wrote: The e-mail address reaches nowhere or actually, does

Re: Suggestion: Use a unified kernel image by default in the future.

Once upon a time, Sharpened Blade said: > How can you know if this interface is not emulated, and you never talk to the > real cpu. That's like saying you can't know if https://www.google.com/ is Google because your computer only talks to AT -- Chris Adams

Re: Orphaned packages looking for new maintainers​​

I've taken gnome-online-accounts, comaintainers welcome! --  Gwyn Ciesla she/her/hers   in your fear, seek only peace  in your fear, seek only love -d. bowie signature.asc Description: OpenPGP digital signature

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

Minutes: https://meetbot.fedoraproject.org/fedora-meeting/2022-07-05/fesco.2022-07-05-17.00.html Minutes (text): https://meetbot.fedoraproject.org/fedora-meeting/2022-07-05/fesco.2022-07-05-17.00.txt Log:

Re: Suggestion: Use a unified kernel image by default in the future.

Lennart Poettering writes: > On Di, 05.07.22 01:44, Fedora Development ML (devel@lists.fedoraproject.org) > wrote: > >> Also, if users have "special" hardware, shouldn't they also have >> security. > > if you need a special kernel cmdline to get your system to boot, then > that's a bug in the

Re: Suggestion: Use a unified kernel image by default in the future.

On Tuesday, 5 July 2022 17:26:40 BST Sharpened Blade via devel wrote: > How can you know if this interface is not emulated, and you never talk to > the real cpu The TDX white papers address how this is meant to work - it's based around the same "measurement" concept as TPM measured boot (see

[Bug 2102655] Add perl-MooseX-Types-Path-Class to EPEL 9

https://bugzilla.redhat.com/show_bug.cgi?id=2102655 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #3 from

[Bug 2102624] Add perl-Devel-ArgNames to EPEL 9

https://bugzilla.redhat.com/show_bug.cgi?id=2102624 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #3 from

[Bug 2103511] perl-Finance-Quote-1.52 is available

https://bugzilla.redhat.com/show_bug.cgi?id=2103511 --- Comment #10 from Fedora Update System --- FEDORA-EPEL-2022-3e813929e6 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here:

[Bug 2102661] Add perl-Time-Piece-MySQL to EPEL 9

https://bugzilla.redhat.com/show_bug.cgi?id=2102661 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #3 from

[Bug 2102644] Add perl-Config-Any to EPEL 9

https://bugzilla.redhat.com/show_bug.cgi?id=2102644 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #3 from

[Bug 2102671] Add perl-Class-C3 to EPEL 9

https://bugzilla.redhat.com/show_bug.cgi?id=2102671 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #3 from

[Bug 2102647] Add perl-Data-GUID to EPEL 9

https://bugzilla.redhat.com/show_bug.cgi?id=2102647 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #3 from

[Bug 2103511] perl-Finance-Quote-1.52 is available

https://bugzilla.redhat.com/show_bug.cgi?id=2103511 --- Comment #8 from Fedora Update System --- FEDORA-2022-b92bd8e9e8 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing

[Bug 2103511] perl-Finance-Quote-1.52 is available

https://bugzilla.redhat.com/show_bug.cgi?id=2103511 --- Comment #9 from Fedora Update System --- FEDORA-2022-2af2d277e2 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing

Re: F37 proposal: Linux Firmware Minimization (late System-Wide Change proposal)

Agree with Dusty here: it's likely that the DNF plugin won't be used at all with rpm-ostree. This change would however enable some rpm-ostree variants to more finely select the firmwares that they want: for example, Fedora CoreOS could skip all WiFi related firmwares and Fedora Silverblue

Re: Suggestion: Use a unified kernel image by default in the future.

How can you know if this interface is not emulated, and you never talk to the real cpu. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct:

Re: F37 Change Proposal: Unfiltered Flathub (System-Wide Change)

The two articles mentioned above all full of errors and misconceptions about how Flatpak and Flathub works. See https://theevilskeleton.gitlab.io/2022/05/16/response-to-flatpak-is-not-the-future.html ___ devel mailing list --

Re: Python 3.11 final release might be delayed to December

On 05. 07. 22 16:22, Kaleb Keithley wrote: On Tue, Jul 5, 2022 at 9:45 AM Miro Hrončok > wrote: On 05. 07. 22 15:20, Kaleb Keithley wrote: > > > On Tue, Jul 5, 2022 at 9:07 AM Richard W.M. Jones mailto:rjo...@redhat.com> >

Re: F37 change proposal: Make Fedora CoreOS a Fedora Edition (System-Wide change)

On 7/5/22 10:10, Timothée Ravier wrote: > We also probably need a new FESCO ticket. The current one still points to the > one from the F34 change request: > - https://fedoraproject.org/wiki/Changes/FedoraCoreOS > - https://pagure.io/fesco/issue/2516 Yes. I imagine as part of this process a new

Re: Python 3.11 final release might be delayed to December

On Tue, Jul 5, 2022 at 9:45 AM Miro Hrončok wrote: > On 05. 07. 22 15:20, Kaleb Keithley wrote: > > > > > > On Tue, Jul 5, 2022 at 9:07 AM Richard W.M. Jones > > wrote: > > > > On Tue, Jul 05, 2022 at 01:17:39PM +0200, Miro Hrončok wrote: > > > Hello, > >

Re: Bugzilla Assignee

On 05. 07. 22 8:32, Jamie Nguyen wrote: Hi, I was wondering if someone could help me. I stopped (co-)maintaining weechat and adobe-source-code-pro-fonts several years ago, but I discovered I'm still listed as the Bugzilla Assignee for EPEL on both packages [1][2] despite not have commit

Re: F37 change proposal: Make Fedora CoreOS a Fedora Edition (System-Wide change)

We also probably need a new FESCO ticket. The current one still points to the one from the F34 change request: - https://fedoraproject.org/wiki/Changes/FedoraCoreOS - https://pagure.io/fesco/issue/2516 ___ devel mailing list --

Re: Python 3.11 final release might be delayed to December

On 05. 07. 22 16:02, Richard W.M. Jones wrote: On Tue, Jul 05, 2022 at 03:46:47PM +0200, Miro Hrončok wrote: On 05. 07. 22 15:05, Richard W.M. Jones wrote: On Tue, Jul 05, 2022 at 01:17:39PM +0200, Miro Hrončok wrote: Hello, forwarding this message to Fedora. Will know more by the end of

Re: Python 3.11 final release might be delayed to December

On 05. 07. 22 16:02, Richard W.M. Jones wrote: On Tue, Jul 05, 2022 at 03:46:47PM +0200, Miro Hrončok wrote: On 05. 07. 22 15:05, Richard W.M. Jones wrote: On Tue, Jul 05, 2022 at 01:17:39PM +0200, Miro Hrončok wrote: Hello, forwarding this message to Fedora. Will know more by the end of

Re: Python 3.11 final release might be delayed to December

On Tue, Jul 05, 2022 at 03:46:47PM +0200, Miro Hrončok wrote: > On 05. 07. 22 15:05, Richard W.M. Jones wrote: > >On Tue, Jul 05, 2022 at 01:17:39PM +0200, Miro Hrončok wrote: > >>Hello, > >>forwarding this message to Fedora. > >> > >>Will know more by the end of this week -- we might need to

Re: Bugzilla Assignee

On Tue, Jul 5, 2022 at 2:34 AM Jamie Nguyen wrote: > > Could someone please set the Bugzilla Assignee for EPEL for both > packages to match the main Bugzilla Assignee? It looks like you're still the EPEL assignee in dist-git. I could make the change in Bugzilla, but it will get reset the next

Re: Python 3.11 final release might be delayed to December

On 05. 07. 22 15:05, Richard W.M. Jones wrote: On Tue, Jul 05, 2022 at 01:17:39PM +0200, Miro Hrončok wrote: Hello, forwarding this message to Fedora. Will know more by the end of this week -- we might need to consider reverting back to Python 3.10 if we don't want to ship Fedora 37 GA with a

Re: Python 3.11 final release might be delayed to December

On 05. 07. 22 15:05, Richard W.M. Jones wrote: On Tue, Jul 05, 2022 at 01:17:39PM +0200, Miro Hrončok wrote: Hello, forwarding this message to Fedora. Will know more by the end of this week -- we might need to consider reverting back to Python 3.10 if we don't want to ship Fedora 37 GA with a

Re: Python 3.11 final release might be delayed to December

On 05. 07. 22 15:20, Kaleb Keithley wrote: On Tue, Jul 5, 2022 at 9:07 AM Richard W.M. Jones > wrote: On Tue, Jul 05, 2022 at 01:17:39PM +0200, Miro Hrončok wrote: > Hello, > forwarding this  message to Fedora. > > Will know more by the end

Re: Python 3.11 final release might be delayed to December

On Tue, Jul 5, 2022 at 9:07 AM Richard W.M. Jones wrote: > On Tue, Jul 05, 2022 at 01:17:39PM +0200, Miro Hrončok wrote: > > Hello, > > forwarding this message to Fedora. > > > > Will know more by the end of this week -- we might need to consider > > reverting back to Python 3.10 if we don't

Re: Python 3.11 final release might be delayed to December

On Tue, Jul 05, 2022 at 01:17:39PM +0200, Miro Hrončok wrote: > Hello, > forwarding this message to Fedora. > > Will know more by the end of this week -- we might need to consider > reverting back to Python 3.10 if we don't want to ship Fedora 37 GA > with a beta version of Python :( Is there a

Re: F37 proposal: Add -fno-omit-frame-pointer to default compilation flags (System-Wide Change proposal)

* Daan De Meyer via devel: > The proposed configuration is to add "-fno-omit-frame-pointer > -mno-omit-leaf-frame-pointer" to the default compilation flags. Are > you alluding to inline assembly that won't have frame pointers set up > correctly even with these two options enabled? The change

[EPEL-devel] Re: python-attrs on epel very outdated

On Tue, 5 Jul 2022 at 08:07, Sérgio Basto wrote: > On Tue, 2022-07-05 at 13:00 +0200, Miro Hrončok wrote: > > On 05. 07. 22 12:43, Stephen Smoogen wrote: > > > You will need to work with the upstream RHEL team to see if they > > > can update > > > python-attrs > > > > The rule of thumb is that

[EPEL-devel] Re: python-attrs on epel very outdated

On Tue, 2022-07-05 at 13:00 +0200, Miro Hrončok wrote: > On 05. 07. 22 12:43, Stephen Smoogen wrote: > > You will need to work with the upstream RHEL team to see if they > > can update > > python-attrs > > The rule of thumb is that we don't. If you need a certain feature > from the > newer

Re: F37 proposal: Add -fno-omit-frame-pointer to default compilation flags (System-Wide Change proposal)

On Tue, Jul 5, 2022 at 1:17 PM Daan De Meyer via devel wrote: > > The proposed configuration is to add "-fno-omit-frame-pointer > -mno-omit-leaf-frame-pointer" to the default compilation flags. Are you > alluding to inline assembly that won't have frame pointers set up correctly > even with

Python 3.11 final release might be delayed to December

Hello, forwarding this message to Fedora. Will know more by the end of this week -- we might need to consider reverting back to Python 3.10 if we don't want to ship Fedora 37 GA with a beta version of Python :( Fedora 37 mass rebuild is planned for 2022-07-20 -- I will make sure we know

Python 3.11 final release might be delayed to December

Hello, forwarding this message to Fedora. Will know more by the end of this week -- we might need to consider reverting back to Python 3.10 if we don't want to ship Fedora 37 GA with a beta version of Python :( Fedora 37 mass rebuild is planned for 2022-07-20 -- I will make sure we know

Re: F37 proposal: Add -fno-omit-frame-pointer to default compilation flags (System-Wide Change proposal)

The proposed configuration is to add "-fno-omit-frame-pointer -mno-omit-leaf-frame-pointer" to the default compilation flags. Are you alluding to inline assembly that won't have frame pointers set up correctly even with these two options enabled? Cheers, Daan

Re: F37 proposal: Add -fno-omit-frame-pointer to default compilation flags (System-Wide Change proposal)

* Daan De Meyer via devel: > The goal was to try and reproduce the phoronix benchmark results so > this is without any system dependencies rebuilt with frame pointers, > same as the phoronix benchmark. But is this build configuration what are you proposing for Fedora? Thanks, Florian

[EPEL-devel] Re: python-attrs on epel very outdated

On 05. 07. 22 12:43, Stephen Smoogen wrote: You will need to work with the upstream RHEL team to see if they can update python-attrs The rule of thumb is that we don't. If you need a certain feature from the newer version, you can try requesting a backport, explaining your use case. We

Re: F37 proposal: Add -fno-omit-frame-pointer to default compilation flags (System-Wide Change proposal)

The goal was to try and reproduce the phoronix benchmark results so this is without any system dependencies rebuilt with frame pointers, same as the phoronix benchmark. Cheers, Daan ___ devel mailing list -- devel@lists.fedoraproject.org To

[EPEL-devel] Re: python-attrs on epel very outdated

On Tue, 5 Jul 2022 at 06:35, Sérgio Basto wrote: > Hi, > > looking to > https://koji.fedoraproject.org/koji/packageinfo?packageID=22940 > and > https://www.attrs.org/en/stable/changelog.html > and > https://git.centos.org/rpms/python-attrs > > 18.1.0 was release on 2018-05-03 , but centos 8 have

[EPEL-devel] python-attrs on epel very outdated

Hi, looking to https://koji.fedoraproject.org/koji/packageinfo?packageID=22940 and https://www.attrs.org/en/stable/changelog.html and https://git.centos.org/rpms/python-attrs 18.1.0 was release on 2018-05-03 , but centos 8 have 17.04 in 2019-02-25 we have the first update of python-attrs to

Re: F37 proposal: Add -fno-omit-frame-pointer to default compilation flags (System-Wide Change proposal)

* Daan De Meyer via devel: > Instead, we only saw differences from 0%-2% between Redis compiled > with frame pointers and Redis compiled without frame pointers. These > benchmarks were done using the phoronix-test-suite in exactly the same > way as documented in the phoronix article. Did you

Schedule for Tuesday's FESCo Meeting (2022-07-05)

Following is the list of topics that will be discussed in the FESCo meeting Tuesday at 17:00UTC in #fedora-meeting on irc.libera.chat. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/UTCHowto or run: date -d '2022-07-05 17:00 UTC' Links to all issues to be

Fedora-Cloud-35-20220705.0 compose check report

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-35-20220704.0): ID: 1315995 Test: aarch64 Cloud_Base-qcow2-qcow2 cloud_autocloud@uefi URL:

[Bug 2103792] perl-URI-5.11 is available

https://bugzilla.redhat.com/show_bug.cgi?id=2103792 Paul Howarth changed: What|Removed |Added Status|ASSIGNED|CLOSED Fixed In Version|

Re: Suggestion: Use a unified kernel image by default in the future.

On Mon, Jul 04, 2022 at 07:20:32PM -, Sharpened Blade via devel wrote: > With virtual machines, nothing can actually be verified completely, > the host running the vm can, 1) Modify the firmware to intercept > anything the attacker wants, or 2) directly intercept things at the > cpu level.

Re: Suggestion: Use a unified kernel image by default in the future.

On Di, 05.07.22 09:49, Gerd Hoffmann (kra...@redhat.com) wrote: > Hi, > > > > > https://raw.githubusercontent.com/keszybz/mkosi-initrd-talk/main/mkosi-initrd.pdf > > > > we tried to make rh image builder people inetreested in that, but they > > weren't interested in that at all. > > For initrd

Re: Suggestion: Use a unified kernel image by default in the future.

On Mon, Jul 04, 2022 at 07:24:28PM -, Sharpened Blade via devel wrote: > > My expectation would be that by default we'd just use the GPT auto > discovery stuff > > Existing Fedora installations do not follow the GPT auto discovery > spec. Also, I think the existing system for the root device

Fedora-Cloud-36-20220705.0 compose check report

No missing expected images. Failed openQA tests: 1/8 (aarch64) New failures (same test not failed in Fedora-Cloud-36-20220704.0): ID: 1315977 Test: aarch64 Cloud_Base-qcow2-qcow2 base_services_start@uefi URL: https://openqa.fedoraproject.org/tests/1315977 Soft failed openQA tests: 1/8

Re: Suggestion: Use a unified kernel image by default in the future.

On Mon, Jul 04, 2022 at 10:25:05PM +0100, Richard W.M. Jones wrote: > On Mon, Jul 04, 2022 at 03:59:25PM +0200, Gerd Hoffmann wrote: > > Hi, > > > > > https://raw.githubusercontent.com/keszybz/mkosi-initrd-talk/main/mkosi-initrd.pdf > > > > Hmm. Nice ideas (reproducible initrds, yay!), but it

Re: Suggestion: Use a unified kernel image by default in the future.

Hi, > > > https://raw.githubusercontent.com/keszybz/mkosi-initrd-talk/main/mkosi-initrd.pdf > > we tried to make rh image builder people inetreested in that, but they > weren't interested in that at all. For initrd building or for cloud image building? > > I don't think mkosi is a hard

[Bug 2103792] perl-URI-5.11 is available

https://bugzilla.redhat.com/show_bug.cgi?id=2103792 Paul Howarth changed: What|Removed |Added Doc Type|--- |If docs needed, set a value

Re: Suggestion: Use a unified kernel image by default in the future.

On Di, 05.07.22 02:34, Fedora Development ML (devel@lists.fedoraproject.org) wrote: > > Like what? > > I know there are some efi implementations that need > pcie_ports=compat. I also know that sometimes you need intel_iommu > or amd_iommu=off. Those are local hacks to get very new or very

Re: Suggestion: Use a unified kernel image by default in the future.

On Di, 05.07.22 01:44, Fedora Development ML (devel@lists.fedoraproject.org) wrote: > Also, if users have "special" hardware, shouldn't they also have > security. if you need a special kernel cmdline to get your system to boot, then that's a bug in the kernel, and should be fixed there. Adding

Re: With F36 systemd-nspawn test environment not usable, no login possible

On Di, 05.07.22 14:38, Dominique Martinet (asmad...@codewreck.org) wrote: > Peter Boy wrote on Tue, Jul 05, 2022 at 07:19:28AM +0200: > > […]# dnf --releasever=36 --best --setopt=install_weak_deps=False \ > > --installroot=/var/lib/machines/testf36 install dhcp-client dnf \ > >

Re: With F36 systemd-nspawn test environment not usable, no login possible

> Am 05.07.2022 um 07:38 schrieb Dominique Martinet : > > Peter Boy wrote on Tue, Jul 05, 2022 at 07:19:28AM +0200: >> […]# dnf --releasever=36 --best --setopt=install_weak_deps=False \ >>--installroot=/var/lib/machines/testf36 install dhcp-client dnf \ >>fedora-release glibc

Bugzilla Assignee

Hi, I was wondering if someone could help me. I stopped (co-)maintaining weechat and adobe-source-code-pro-fonts several years ago, but I discovered I'm still listed as the Bugzilla Assignee for EPEL on both packages [1][2] despite not have commit access. (FAS username: jamielinux) I