Re: Intention to retire mlocate

Are you sure you have the correct address for the plocate developer and that it's still actively maintained? I just got an error that the destination email address didn't exist from their mail server when I replied just now. On Fri, May 24, 2024, 02:15 Christopher wrote: > A flag to tr

Re: Intention to retire mlocate

, 20:04 Dominique Martinet wrote: > Christopher wrote on Thu, May 23, 2024 at 06:26:57PM -0400: > > One thing I've noticed is that plocate behaves differently when > > supplied with multiple arguments than mlocate. This broke some of my > > scripts. > > > > Previous

Re: Intention to retire mlocate

), mlocate was better. plocate should handle these arguments, or at least fail with a message letting you know that it is ignoring the rest of the arguments. -- Christopher -- ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe sen

Return-from-sleep display problems

For a while now, I've noticed that whenever Fedora returns from sleep, the native display resolution for at least one of my monitors seems to be missing, and my display settings get messed up for multiple monitors. I have a laptop with 3:2 ratio (from frame.work) whose native resolution is

Re: F41 Change Proposal: Drop Mandatory Requires on JRE (system-wide)

On Thu, May 2, 2024 at 9:24 PM Kevin Kofler via devel wrote: > > Christopher wrote: > > So, I actually think that building with the *latest* JDK that we ship, > > and using the `--release` flag during compilation is actually safer > > than building against the lowest

Re: F41 Change Proposal: Drop Mandatory Requires on JRE (system-wide)

that Fedora packagers communicate the JRE requirements for each package *if* it were to be run. Maybe that can be done with Recommends instead of Requires? I'm not sure about that part, but I acknowledge that installing a library is not the same as intending for it to be run. Christ

Re: Thanks to my FESCo friends! ♥

On 26/04/2024 15.41, Major Hayden wrote: Hey there, I'm incredibly thankful for all of the support I've received while serving on the Fedora Engineering Steering Committee (FESCo) since Fedora 38 in 2022. So many of you have taught me so many things and given me so much valuable feedback. ♥️

Re: CVE-2024-2905: World-readable /etc/shadow & /etc/gshadow on Fedora CoreOS, IoT, Atomic Desktops

On 10/04/2024 15.52, Timothée Ravier wrote: Due to a bug in rpm-ostree, the /etc/shadow, /etc/shadow-, /etc/gshadow and /etc/gshadow- files in Fedora CoreOS, IoT, Atomic Desktops have the world-readable bit set. == Affected versions == All Fedora CoreOS nodes installed starting from the

Re: convert everything to rpmautospec?

On 08/04/2024 11.31, Richard W.M. Jones wrote: On Mon, Apr 08, 2024 at 12:22:35AM +0200, Kevin Kofler via devel wrote: Emmanuel Seyman wrote: I've noticed a trend in proposed changes in the way Fedora works. I am fed up of this salami tactic as well. When we complain about the new stuff, we

Re: xz backdoor

On 01/04/2024 19.27, Kevin Fenzi wrote: On Mon, Apr 01, 2024 at 05:07:13PM +, Christopher Klooz wrote: On 31/03/2024 23.08, Kevin Fenzi wrote: On Sun, Mar 31, 2024 at 10:30:23PM +0200, Leon Fauster via devel wrote: Not sure, if it was already mentioned -> containers. I had here a tool

Re: xz backdoor

On 31/03/2024 23.08, Kevin Fenzi wrote: On Sun, Mar 31, 2024 at 10:30:23PM +0200, Leon Fauster via devel wrote: Not sure, if it was already mentioned -> containers. I had here a toolbox environment with F40. That I had not in my first actions on the screen. The last state had 5.6.0-3 installed

Re: xz backdoor

On 01/04/2024 16.32, Michael Catanzaro wrote: On Sun, Mar 31 2024 at 06:52:53 PM +00:00:00, Christopher Klooz wrote: "Fedora Linux 40 branched users (i.e. pre-Beta) likely received the potentially vulnerable 5.6.0-2.fc40 build if the system updated between March 2nd and March 6th. F

Re: xz backdoor

On 31/03/2024 21.33, Sandro wrote: On 31-03-2024 20:54, Christopher Klooz wrote: On 31/03/2024 20.52, Christopher Klooz wrote: On 31/03/2024 20.21, Michael Catanzaro wrote: On Sun, Mar 31 2024 at 09:56:04 AM -05:00:00, Michael Catanzaro wrote: I'm really frustrated with our communication

Re: xz backdoor

On 31/03/2024 23.11, Kevin Fenzi wrote: On Sun, Mar 31, 2024 at 08:55:37PM +, Christopher Klooz wrote: The repo files should be the same on Fedora containers, so if the container is F40 and the testing repo is enabled, it might have installed the malicious build. Right, if it was dnf

Re: xz backdoor

On 31/03/2024 22.30, Leon Fauster via devel wrote: Am 31.03.24 um 21:33 schrieb Sandro: On 31-03-2024 20:54, Christopher Klooz wrote: On 31/03/2024 20.52, Christopher Klooz wrote: On 31/03/2024 20.21, Michael Catanzaro wrote: On Sun, Mar 31 2024 at 09:56:04 AM -05:00:00, Michael Catanzaro

Re: xz backdoor

On 31/03/2024 20.52, Christopher Klooz wrote: On 31/03/2024 20.21, Michael Catanzaro wrote: On Sun, Mar 31 2024 at 09:56:04 AM -05:00:00, Michael Catanzaro wrote: I'm really frustrated with our communication regarding this issue. Does anybody know who can fix this? The Fedora Magazine

Re: xz backdoor

On 31/03/2024 20.21, Michael Catanzaro wrote: On Sun, Mar 31 2024 at 09:56:04 AM -05:00:00, Michael Catanzaro wrote: I'm really frustrated with our communication regarding this issue. Does anybody know who can fix this? The Fedora Magazine article has been fixed (thanks!). "*Fedora

Re: xz backdoor

On 31/03/2024 16.56, Michael Catanzaro wrote: On Sun, Mar 31 2024 at 12:55:23 PM +00:00:00, Christopher Klooz wrote: In case someone from the Fedora Magazine is in the devel mailing list and reads this: I'm really frustrated with our communication regarding this issue. Does anybody know

Re: xz backdoor

On 30/03/2024 15.45, Michael Catanzaro wrote: On Sat, Mar 30 2024 at 12:26:48 PM +00:00:00, Christopher Klooz wrote:  If I got Rich right, the malicious code is likely to be broken on F40, No, that is not correct, as explained by [1] and [2]. We have already asked Red Hat to investigate

Re: xz backdoor

On 30/03/2024 20.08, Sandro wrote: On 30-03-2024 13:26, Christopher Klooz wrote: I don't know how the assumption came up that F40 is only affected if users opted in for testing, but that interpretation already ended up in the Fedora Magazine and in the official linkedin post of Fedora (I

Re: xz backdoor

On 30/03/2024 15.45, Michael Catanzaro wrote: On Sat, Mar 30 2024 at 12:26:48 PM +00:00:00, Christopher Klooz wrote:  If I got Rich right, the malicious code is likely to be broken on F40, No, that is not correct, as explained by [1] and [2]. We have already asked Red Hat to investigate

Re: xz backdoor

On 29/03/2024 22.10, Michael Catanzaro wrote: On Fri, Mar 29 2024 at 08:16:55 PM +00:00:00, Richard W.M. Jones wrote: These are the exact builds which were vulnerable.  Note the tags are all empty because Kevin untagged them last night, so you'll probably need to cross-reference these with

Re: xz backdoor

On 29/03/2024 21.01, Richard W.M. Jones wrote: On Fri, Mar 29, 2024 at 06:46:59PM +, Christopher Klooz wrote: Yes, F40 beta is affected, along with rawhide, but not F38/F39. https://discussion.fedoraproject.org/t/warning-malicious-code-in-current-pre-release-testing-versions-variants-f40

Re: xz backdoor

Yes, F40 beta is affected, along with rawhide, but not F38/F39. https://discussion.fedoraproject.org/t/warning-malicious-code-in-current-pre-release-testing-versions-variants-f40-and-rawhide-affected-users-of-f40-rawhide-need-to-respond/110683

Re: Login issues to lists.* and src.*? Any outages?

On Mon, Feb 26, 2024 at 6:13 AM Michal Konecny wrote: [snip] > It's usually good to wait for some time and try again. If the issue persists > you can open ticket on > https://pagure.io/fedora-infrastructure/issues > > Michal I did try over the course of a few hours. It wasn't until 3 days later

Re: Login issues to lists.* and src.*? Any outages?

2024, at 20:20, Christopher wrote: > > Are there any known issues right now for logging in to > lists.fedoraproject.org or src.fedoraproject.org? > Do we have a page for known outages? > > I can log in to accounts.fedoraproject.org, so I know my password and 2FA > toke

Re: Login issues to lists.* and src.*? Any outages?

On Thu, Feb 22, 2024 at 4:01 PM Gary Buhrmaster wrote: > > On Thu, Feb 22, 2024 at 8:20 PM Christopher > wrote: > > > > Are there any known issues right now for logging in to > > lists.fedoraproject.org or src.fedoraproject.org? > > Do we have a

Login issues to lists.* and src.*? Any outages?

in there, to see if that had an effect, but it wouldn't let me (I thought it was optional?) I'm still in the packager group in accounts.f.o (not inactive). So, I'm not sure what the problem is. Is this a known issue? I haven't seen anything about this on the devel list recently. Thanks, Christopher

Re: Unresponsive maintainer: petersen / Pandoc package not updated since June 2023: Security vulnerability, CVE-2023-35936 (medium)

be appreciated. Thanks, Jens PS Special thanks to Neal Gompa for pinging me in Matrix.  On Fri, 9 Feb 2024, 20:05 Christopher Klooz, wrote: I cannot reach the maintainer petersen (see mail below): The package "pandoc" remains at 3.1.3 in Fedora, but pandoc is already at 3.1.11.1. A

Re: Unresponsive maintainer: petersen / Pandoc package not updated since June 2023: Security vulnerability, CVE-2023-35936 (medium)

Christopher Klooz, wrote: I cannot reach the maintainer petersen (see mail below): The package "pandoc" remains at 3.1.3 in Fedora, but pandoc is already at 3.1.11.1. Among the updates since 3.1.3, there have been two security-critical (including the medium CVE-2023-35936. Security fixes ar

Re: Unresponsive maintainer: petersen / Pandoc package not updated since June 2023: Security vulnerability, CVE-2023-35936 (medium)

thanks to Neal Gompa for pinging me in Matrix.  On Fri, 9 Feb 2024, 20:05 Christopher Klooz, wrote: I cannot reach the maintainer petersen (see mail below): The package "pandoc" remains at 3.1.3 in Fedora, but pandoc is already at 3.1.11.1. Among the updates since 3.1.3, there hav

Re: Fwd: Unresponsive maintainer: petersen / Pandoc package not updated since June 2023: Security vulnerability, CVE-2023-35936 (medium)

Thanks! :) On 09/02/2024 13.18, Luna Jernberg wrote: CCed his work email in case he looks there -- Forwarded message - Från: Christopher Klooz Date: fre 9 feb. 2024 kl 13:05 Subject: Unresponsive maintainer: petersen / Pandoc package not updated since June 2023: Security

Unresponsive maintainer: petersen / Pandoc package not updated since June 2023: Security vulnerability, CVE-2023-35936 (medium)

I cannot reach the maintainer petersen (see mail below): The package "pandoc" remains at 3.1.3 in Fedora, but pandoc is already at 3.1.11.1. Among the updates since 3.1.3, there have been two security-critical (including the medium CVE-2023-35936. Security fixes are in 3.1.4 & 3.1.6). The

Re: Brasero can't create CD images in F39

On 29/12/2023 17.31, Sergio Pascual wrote: Hello, I would like to bring attention to this bug https://bugzilla.redhat.com/show_bug.cgi?id=2250192 This problem prevents Brasero from creating CD images in F39. Brasero complains about "old version of cdrdao", but the version in F39 is the latest

Re: F40 Change Proposal: Wifi MAC Randomization (System Wide)

the MAC randomization if they are affected negatively could be a good mitigation without increasing the stuff in the installer. [1] https://discussion.fedoraproject.org/t/f40-change-proposal-wifi-mac-randomization-system-wide/99856/22 On 24/12/2023 11.19, Christopher Klooz wrote: On 24/12/2023

Re: F40 Change Proposal: Wifi MAC Randomization (System Wide)

On 24/12/2023 04.45, Sam Varshavchik wrote: Kevin Kofler via devel writes: Sam Varshavchik wrote: > Christopher Klooz writes: > >> Btw, does anyone know if this (in the practically-same manner) is really >> already introduced in Windows, Mac, Android by default? Globall

Re: F40 Change Proposal: Wifi MAC Randomization (System Wide)

I would like to avoid duplicates and unnecessary redundancy, but especially for the issue discussed below it might be worth to also review the discussion on discussion.fp.org -> I am not convinced if it is that easy for all users when it comes to existing network configurations / setups,

Fedora local meetup London - 2024 (likely January or February)

Because not everyone is active on discourse, I thought it makes sense to link this here for people from the area in or close to London: https://discussion.fedoraproject.org/t/local-meetup-london-2024/98029 -- ___ devel mailing list --

Re: DNF5: Checking signatures of packages installed out of a repository?

On Tue, Nov 14, 2023 at 9:30 AM Michael Catanzaro wrote: > > On Tue, Nov 14 2023 at 08:16:39 AM -0500, Christopher > wrote: > > I think for the sake of security, it'd be better if this were on by > > default, and you just had to specify the --nogpgcheck > > For con

Re: DNF5: Checking signatures of packages installed out of a repository?

On Tue, Nov 14, 2023 at 9:24 AM Petr Pisar wrote: > > V Tue, Nov 14, 2023 at 08:16:39AM -0500, Christopher napsal(a): > > On Tue, Nov 14, 2023 at 8:03 AM Jaroslav Mracek wrote: > > > > > > I believe that one of the strong complains was related to not signed

Re: DNF5: Checking signatures of packages installed out of a repository?

On Tue, Nov 14, 2023 at 8:03 AM Jaroslav Mracek wrote: > > I believe that one of the strong complains was related to not signed > packages. The use case is that when I build RPMs locally and then I install > them (see bellow). > > dnf install *.rpm --setopt=localpkg_gpgcheck=true > ... >

Re: DNF5: Checking signatures of packages installed out of a repository?

On Sun, Nov 5, 2023 at 3:54 PM Samuel Sieb wrote: > > On 11/2/23 06:36, Christopher wrote: > > On Wed, Nov 1, 2023 at 1:50 PM Kevin Fenzi wrote: > >> > >> On Wed, Nov 01, 2023 at 11:05:33AM -0400, Christopher wrote: > >>> It's also not clear when th

Re: DNF5: Checking signatures of packages installed out of a repository?

On Wed, Nov 1, 2023 at 5:39 PM Zbigniew Jędrzejewski-Szmek wrote: > > On Wed, Nov 01, 2023 at 10:49:36AM -0700, Kevin Fenzi wrote: > > On Wed, Nov 01, 2023 at 11:05:33AM -0400, Christopher wrote: > > > On Tue, Oct 31, 2023 at 7:50 PM Kevin Fenzi wrote: > > > &

Re: DNF5: Checking signatures of packages installed out of a repository?

On Wed, Nov 1, 2023 at 1:50 PM Kevin Fenzi wrote: > > On Wed, Nov 01, 2023 at 11:05:33AM -0400, Christopher wrote: > > On Tue, Oct 31, 2023 at 7:50 PM Kevin Fenzi wrote: > > > > > > FWIW, from what I can recall, yum used to check all packages, but this &g

Re: DNF5: Checking signatures of packages installed out of a repository?

On Wed, Nov 1, 2023 at 5:53 AM Paul Howarth wrote: > > On Tue, 31 Oct 2023 12:48:31 -0400 > Christopher wrote: > > I'm actually a bit concerned about this thread, because I assumed DNF4 > > and DNF5 would check signatures by default today, and that it would > >

Re: DNF5: Checking signatures of packages installed out of a repository?

On Tue, Oct 31, 2023 at 7:50 PM Kevin Fenzi wrote: > > FWIW, from what I can recall, yum used to check all packages, but this > resulted in tons of people complaining because they did not want it to > check their local packages. So, a localpkg_gpgcheck option was added and > set to false. dnf4

Re: DNF5: Checking signatures of packages installed out of a repository?

On Tue, Oct 31, 2023 at 1:38 PM Vít Ondruch wrote: > > > Dne 31. 10. 23 v 16:23 Petr Pisar napsal(a): > > Hello, > > > > DNF5 got a complaint > > that "dnf > > update > > https://...; skips verifying package signatures: > > > > $

Re: DNF5: Checking signatures of packages installed out of a repository?

On Tue, Oct 31, 2023 at 11:57 AM Petr Pisar wrote: > > V Tue, Oct 31, 2023 at 04:32:09PM +0100, Fabio Valentini napsal(a): > > On Tue, Oct 31, 2023 at 4:24 PM Petr Pisar wrote: > > > > > > Hello, > > > > > > DNF5 got a complaint > > >

Re: An update on RHEL moving to issues.redhat.com

It used to be different, but since GitLab changed their UI, I also would no longer choose it over alternatives (so, unfortunately: +1 for the UX mess & the preference for alternatives). The remaining advantage of GitLab is the time-effective drag/drop issue board, but that cannot balance the

Potential (security) issue for beginners/non-experts when release is End Of Life: Fedora doesn’t consider the behavior of beginners/non-experts sufficiently

The below is a duplicate from discourse (I suggest to focus the discussion there): https://discussion.fedoraproject.org/t/potential-security-issue-for-beginners-non-experts-when-release-is-end-of-life-fedora-doesnt-consider-the-behavior-of-beginners-non-experts-sufficiently/87311/1 I just

Re: [Question] how to make Fedora linux os ?

On Sun, Jul 16, 2023 at 7:30 AM Kevin Kofler via devel wrote: > > Miao, Jun wrote: > > Hi Guys, > > First of all, we are not all guys. (I happen to be one though.) I would advise not to get too picky about this. The term "guys" isn't necessarily gender-specific. In its plural form, it has

Re: F40 Change: Privacy-preserving Telemetry for Fedora Workstation (System-Wide)

Matt has started a poll with regards to the community's preferences about the topic: https://discussion.fedoraproject.org/t/straw-poll-on-your-preferences-about-opt-in-opt-out-for-possible-data-collection/85675/2 On 7/12/23 12:37, Eike Rathke wrote: Hi, On Tuesday, 2023-07-11 08:17:07

Re: F40 Change: Privacy-preserving Telemetry for Fedora Workstation (System-Wide)

Matt has started a poll with regards to the community's preferences about the topic: https://discussion.fedoraproject.org/t/straw-poll-on-your-preferences-about-opt-in-opt-out-for-possible-data-collection/85675/2 On 7/12/23 12:37, Eike Rathke wrote: Hi, On Tuesday, 2023-07-11 08:17:07 -0500,

Re: LXQt Spin: packages not updated since April 2022

:01, Neal Gompa wrote: On Sat, Jul 1, 2023 at 8:38 AM Christopher Klooz via devel wrote: Hi, I was testing an instance of the LXQt Spin in a VM and saw that after updating all packages, the LXQt packages are still with version 1.1.0, which is from April 2022. Current is 1.3.0. I read the LXQt

LXQt Spin: packages not updated since April 2022

Hi, I was testing an instance of the LXQt Spin in a VM and saw that after updating all packages, the LXQt packages are still with version 1.1.0, which is from April 2022. Current is 1.3.0. I read the LXQt team does not maintain itself, and 1.2.0 and 1.3.0 seem to not contain critical

Re: Modules without modularity

On Sat, Jun 17, 2023 at 9:12 PM Kevin Kofler via devel wrote: > > Petr Pisar wrote: > > I understand the horror that you can have two packages which cannot be > > installed at the same time. The same as you cannot start httpd and nginx > > services at the same time. But now the conflict is

Re: ACPI-related bug in 6.3.X? At least an issue in ucsi_acpi, affecting several systems

ues could both be explained by an acpi-related bug). I already asked Justin to change the BZ# in Bodhi. On 6/14/23 10:43, Hans de Goede wrote: Hi Christopher, On 6/13/23 23:26, Christopher Klooz via devel wrote: In case you are already aware of the issue, feel free to ignore this mail. I j

ACPI-related bug in 6.3.X? At least an issue in ucsi_acpi, affecting several systems

In case you are already aware of the issue, feel free to ignore this mail. I just want to make aware that there could be multiple interrelated (bug) reports that might be considered in conjunction and not on their own, given that the amount of affected users is above average (I could imagine

Re: Modules without modularity

On Tue, Jun 13, 2023 at 12:33 PM Petr Pisar wrote: > > Hello, > > as it seems that module build infrastructure isn't getting any better, as > modular YUM repositories are going to be deconfigured > , > there is a time to look

Re: Kernel Bug Reports: Template broken?

On 6/9/23 02:24, Kevin Fenzi wrote: On Thu, Jun 08, 2023 at 09:21:38PM +0200, Christopher Klooz wrote: Hi, I saw that some users filed kernel bug reports, which lacked information. Then I wanted to check the kernel bug report template and found out: there is no longer a template. So

Kernel Bug Reports: Template broken?

Hi, I saw that some users filed kernel bug reports, which lacked information. Then I wanted to check the kernel bug report template and found out: there is no longer a template. So in the past, once the component "kernel" was chosen, the user was provided with a template of the bug report,

Salt is broken in Fedora 38 - asking a python-savvy provenpackager to help

permission to use Fedora at work. So, any help to get this fixed would be greatly appreciated. Thanks, Christopher ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code

Error with libheif package

Several users experience an issue with Fedora's `libheif` package, which can be easily reproduced: See https://discussion.fedoraproject.org/t/unknown-update-error-with-libheif/81302/6 With regards to our default dnf repositories: our package has weak dependencies that are not satisfied by

Re: It’s time to transform the Fedora devel list into something new

On 4/21/23 17:27, Daniel Alley wrote: If one uses OpenPGP and if people verify it As you mention, that's a big "if" Absolutely, and if the majority does not verify in the devel mailing list, it is clearly an indicator that this type of security is not relevant here ;) But finally, I am not

Re: It’s time to transform the Fedora devel list into something new

On 4/21/23 16:30, Aleksandra Fedorova wrote: On 4/21/23 15:25, Christopher Klooz wrote: Just a slight addition about "archaic email" and related comments: Email and its capability for being used in conjunction with OpenPGP ensures two major institutions in kernel development and

Re: It’s time to transform the Fedora devel list into something new

Just a slight addition about "archaic email" and related comments: Email and its capability for being used in conjunction with OpenPGP ensures two major institutions in kernel development and elsewhere: "Trusting the developers, not infrastructure" [1], and, assume "any part of the

[EPEL-devel] Packages for PHP 8.1

Hello, I have a RHEL 9 system running PHP 8.1 from the Red Hat AppStream module. I tried to install php-sodium and php-pecl-imagick from EPEL 9 on it, but DNF gave an error that basically said those packages only work with PHP 8.0. Would it be possible to provide versions of those packages

Re: asciiDoc: Package outdated; unresponsive maintainer?

Thanks for the information. I filed a ticket, so everyone should get an email, including Fab by his private mail address: https://bugzilla.redhat.com/show_bug.cgi?id=2171184 On 2/18/23 14:06, Ben Beasley wrote: Fabian Affolter has been consistently active in Fedora. At the same time, he

asciiDoc: Package outdated; unresponsive maintainer?

Hi all, Does anyone know about the maintainer "Fab"? I have tried to contact him through asciidoc-maintain...@fedoraproject.org on 29th January and through f...@fedoraproject.org on 11th February, but did not received an answer from either. asciiDoc has not been updated for two years with

Re: Obsolete version of "x11docker" in koji/bodhi; no updates for two years (orphaned?)

No worries. Thanks! On 1/27/23 19:41, Davide Cavalca wrote: On 2023-01-27 10:34, Christopher Klooz wrote: Hi, I just saw that a package (x11docker) seems to be orphaned: we ship a very old release (many releases since June 2021), and when reviewing the release notes of subsequent releases

Obsolete version of "x11docker" in koji/bodhi; no updates for two years (orphaned?)

Hi, I just saw that a package (x11docker) seems to be orphaned: we ship a very old release (many releases since June 2021), and when reviewing the release notes of subsequent releases on github of that package, I think this old release (from June 2021) should no longer be deployed: see

Re: Fedoras GnuPG default option is deprecated

: On Wed, Jan 4, 2023 at 3:37 PM Christopher Klooz wrote: A fresh installation of Fedora 37 has by default the "--supervised" option active in its gpg-agent systemd file (/usr/lib/systemd/user/gpg-agent.service). According to GnuPG Docs [1], this option is deprecated. Once gpg-agent

Fedoras GnuPG default option is deprecated

A fresh installation of Fedora 37 has by default the "--supervised" option active in its gpg-agent systemd file (/usr/lib/systemd/user/gpg-agent.service). According to GnuPG Docs [1], this option is deprecated. Once gpg-agent is invoked, the log of "systemctl --user status gpg-agent.service"

Re: Issue with configuration of nested virtualization

ecessary, open a topic there. We had nested virtualization topics in the past, so maybe someone there can help you with that. Cheers, Chris On 28/12/2022 09:34, Peter Boy wrote: Hi Chris, Am 27.12.2022 um 23:01 schrieb Christopher Klooz: ... The Red Hat Docs you refer to differ to the Qui

Re: Issue with configuration of nested virtualization

Hi Peter, I have not much experience with nested virtualization in particular. But although I am quite sure that it will not fail without host-passthrough, I cannot imagine it to be sufficiently efficient without making use of host-passthrough in production (and also not effective in many use

Re: Karma for OpenSSL needed

Just tested and added karma to f36 and f37. Thanks! On 01/11/2022 18:22, Dmitry Belyavskiy wrote: Dear colleagues, I've just pushed the updates for OpenSSL fixing 2 CVEs evaluated as HIGH. Could you please check the freshly pushed builds to get necessary karma ASAP? Many thanks! -- Dmitry

Re: Grub menu with 3 kernels by default

On 05/10/2022 20:28, Hans de Goede wrote: Hi, On 10/5/22 19:59, Christopher Klooz wrote: On 05/10/2022 18:39, Christopher Klooz wrote: On 05/10/2022 17:33, Chris Murphy wrote: On Wed, Oct 5, 2022, at 11:16 AM, Christopher Klooz wrote: However, on ask.fp, a user mentioned that the grub

Re: Grub menu with 3 kernels by default

On 05/10/2022 18:39, Christopher Klooz wrote: On 05/10/2022 17:33, Chris Murphy wrote: On Wed, Oct 5, 2022, at 11:16 AM, Christopher Klooz wrote: However, on ask.fp, a user mentioned that the grub menu is no longer enabled by default on single boot systems so that changing the kernel

Re: Grub menu with 3 kernels by default

On 05/10/2022 17:33, Chris Murphy wrote: On Wed, Oct 5, 2022, at 11:16 AM, Christopher Klooz wrote: However, on ask.fp, a user mentioned that the grub menu is no longer enabled by default on single boot systems so that changing the kernel is no longer easily possible, and put forward https

Grub menu with 3 kernels by default

The current issue on 5.19.12 made it necessary for some users to change their kernel on boot to avoid 5.19.12 until the update to 5.19.13 was pushed to stable. Obviously, the option to easily boot recent kernels can be necessary in several circumstances, especially for non-advanced users it

[EPEL-devel] Re: Proposal: Dropping modules from EPEL-8. Not adding modules to EPEL-9

I found it useful to ship the nextcloud package as a module, particularly in EPEL, but if after multiple years there really are only 12 packages in the repo and even those may or may not work then that is a pretty clear argument for eating the sunk cost & abandoning the idea. -- Christo

Re: Packages in repo not signed: fedora-cisco-openh264 repository

On 26/08/2022 01:28, Kevin Fenzi wrote: Everything should be back to working. Try a 'dnf --refresh...' or a 'dnf clean all'. Yes, the packages are no longer in the update list. So the errors are gone for now. Thanks! It's not fully clear yet some of the events. ;( The person who used to

Packages in repo not signed: fedora-cisco-openh264 repository

I just tried an update (`dnf update`, F36). Three packages that are to be updated are from the fedora-cisco-openh264 repository. In all three cases, I get the dnf output that these packages have not been signed, which finally makes the GPG verification to fail. The packages are:  

Re: List of long term FTBFS packages to be retired in 1 week

Hi, On 01.08.22 14:55, Miro Hrončok wrote: php-aws-sdk3 lcts php-pimple   lcts both fixed. Best, Christopher ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le

Orphaning some packages

-icon rubygem-prawn-manual_builder rubygem-prawn-svg rubygem-prawn-templates stress-ng Thanks Christopher ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct

Re: Support for Realtek RTL8811CU (WiFi)

: You can became maintainer and add this to rpmfusion. Makes sense ;) пт, 1 июл. 2022 г., 10:50 Christopher Klooz : Sorry, I didn't mean to implement this specific solution. That was only meant as example that the issue is known. I meant it more generic, any solution for the user that can

Re: Support for Realtek RTL8811CU (WiFi)

it with nvidia. I was wondering as the 8811CU seems widespread. On 01/07/2022 01:39, Naheem Zaffar wrote: On Thu, 30 Jun 2022, 23:50 Christopher Klooz, wrote: It seems that Fedora does not support the Realtek RTL8811CU for WiFi. A user at ask.Fedora just had the issue. `lsusb

Support for Realtek RTL8811CU (WiFi)

It seems that Fedora does not support the Realtek RTL8811CU for WiFi. A user at ask.Fedora just had the issue. `lsusb` classifies it just as "Bus 001 Device 010: ID 0bda:c811 Realtek Semiconductor Corp. 802.11ac NIC"; correspondingly, `nmcli` does not recognize it at all. A bug report with

Re: Hardware without AES-NI: use xchacha12/Adiantum instead of AES-XTS

The irony is that XTS uses two different keys for different parts of the operation. This means that AES-XTS-256 is AES128 and AES-XTS-512 is AES256 (security is not increased by the second key). So, you compared AES with 128 bit encryption with XChaCha with 256 bit. And despite the doubled

Call for review: Borg Backup (crypto & python)

Hi all, Borg Backup (https://www.borgbackup.org/), which is also part of the Fedora repository, is a widespread open source incremental backup tool with authenticated encryption. Quite sure many of you know & use it. The crypto was completely redesigned for the upcoming version 1.3.

Re: Live USB rescue mode, do we still have one? Does it work?

On 28/05/2022 00:34, Stephen Snow wrote: On Fri, 2022-05-27 at 09:52 -0700, Brian C. Lane wrote: On Fri, May 27, 2022 at 09:38:43AM -0400, Stephen Snow wrote: On Wed, 2022-05-25 at 14:02 -0700, Adam Williamson wrote: The rescue mode has always been on the traditional installer images, not the

Re: Live USB rescue mode, do we still have one? Does it work?

Just as a short incentive from my side: I currently try to solve the issue Stephen is talking about. Feel free to have a look on: https://ask.fedoraproject.org/t/not-boot-not-disks/21992 My point is that the complexity we are able to tackle and the complexity some users are able to tackle

Re: GNOME Online Accounts "Fedora" - Pre-authentication failed

On Fri, Apr 8, 2022 at 1:29 PM Björn Persson wrote: > > Michael Catanzaro wrote: > > On Thu, Apr 7 2022 at 12:30:42 PM -0400, Stephen Gallagher > > wrote: > > > Well, it *could* grow an interface to some of the password wallet > > > services that support TOTP or HOTP codes (like Bitwarden,

Re: GNOME Online Accounts "Fedora" - Pre-authentication failed

On Thu, Apr 7, 2022 at 2:21 PM Michael Catanzaro wrote: > > On Thu, Apr 7 2022 at 02:10:06 PM -0400, Christopher > wrote: > > At the very least, it could give a more useful error message. One of > > my questions in the original post was whether this is even related to &

Re: GNOME Online Accounts "Fedora" - Pre-authentication failed

On Thu, Apr 7, 2022 at 10:59 AM Michael Catanzaro wrote: > > On Thu, Apr 7 2022 at 02:41:42 PM +, Gary Buhrmaster > wrote: > > I had thought there was an open (RFE) issue with > > gnome-online-accounts to request support for > > OTP use cases, although, as a hard problem, it > > is likely

GNOME Online Accounts "Fedora" - Pre-authentication failed

omething else to use this method to authenticate for Fedora packager tools? Or is this permanently broken? Thanks, Christopher ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fe

Re: What has the PDC ever done for us?

On Fri, Mar 18, 2022 at 3:59 AM Petr Pisar wrote: > > V Thu, Mar 17, 2022 at 12:58:54PM -0400, Christopher napsal(a): > > Even if PDC is the most valuable thing to Fedora composes ever, casual > > contributors who only work on packaging should never have to care > > ab

Re: What has the PDC ever done for us?

On Thu, Mar 17, 2022 at 12:29 PM Adam Williamson wrote: > It stores the metadata of all composes that have been run, ever. (Well, > when there isn't a bug in the sync, anyway). This is useful in several > ways: [snip] I think a lot of the Fedora infrastructure complexity and difficulty

Re: Self-introduction: Christopher Crouse (amz)

Hi Ben, Noted, and thank you for reviewing my packages and sponsoring me. Appreciate it! Regards, Christopher Crouse ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora

Re: Bugzilla email confirmation notices from FAS

On Tue, Jan 11, 2022 at 1:53 PM Adam Williamson wrote: > > On Tue, 2022-01-11 at 18:15 +0100, Alexander Sosedkin wrote: > > On Tue, Jan 11, 2022 at 6:04 PM Yaakov Selkowitz > > wrote: > > > > > > On Tue, 2022-01-11 at 11:58 -0500, Christopher wrote: > >

  1   2   3   4   5   6   7   8   9   10   >