Regenerating rescue kernels (Fedora upgrade documentation)

[Jered Floyd]

I run into this every time I upgrade Fedora, but I always forget to
follow-up on it... 42's the charm!

In the Upgrading Fedora docs (
https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/#sect-update-rescue-kernel)
one of the optional post-upgrade steps is updating the rescue kernel.  The
documentation linked says:

The rescue kernel regeneration process can be automated by installing the
dracut-config-rescue package.

sudo dnf install dracut-config-rescue

Once installed, the rescue kernel will be regenerated as long as dracut is
the initrd generator. See
/usr/lib/kernel/install.d/51-dracut-rescue.install for details.

This seems to be incomplete or incorrect, because that package is installed
but I've never had rescue kernels generated.  The referenced file
(/usr/lib/kernel/install.d/51-dracut-rescue.install) isn't particularly
useful to be referenced for details because it's a shell script with no
user documentation.

Before I dig in and become a dracut expert... is this an easy doc fix for
someone familiar?

--Jered
-- 
___
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-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Fedocal] Reminder meeting : ELN SIG

[yselkowitz]

Dear all,

You are kindly invited to the meeting:
   ELN SIG on 2025-05-01 from 15:00:00 to 16:00:00 US/Eastern
   At meet...@fedoraproject.org

The meeting will be about:



Source: https://calendar.fedoraproject.org//meeting/11018/

-- 
___
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-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

PSA - A change in Docker cli plugin version management (Compose, BuildKit, Buildx)

[Brad Smith]

FESCo has approved an update policy exception that encompasses these
Docker plugins: Compose, BuildKit, and Buildx
(https://pagure.io/fesco/issue/3394). The rpms for these plugins will
now track the current plugin release across all Fedora releases. The
maintainers for all three plugins only support the current release for
bug and security fixes.

In the next few days versions for these rpms will be submitted for F42
and F41. No updates for F40 are planned given the imminent EOL for F40
and the very old version of Compose present.

Please let me know if you have any questions or concerns.

best regards

Brad
-- 
___
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-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Oniguruma project ended

[Vít Ondruch]

Dne 30. 04. 25 v 15:45 huangye wudeng napsal(a):

Ruby switched from oniguruma to onigurumo (repo 
https://github.com/k-takata/Onigmo) a long time ago (around 2021).
see https://github.com/ruby/ruby/pull/4306/files

Onigmo is a regular expressions library forked from Oniguruma.

See also the Wiki page: https://github.com/k-takata/Onigmo/wiki



The worrying thing is that if you check the authors activity [1], there 
is awkward silence recently. On top of that, Ruby ships some changes 
which IMHO were not backported to Onigmo. IOW I am worried about 
healthiness of the Onigmo project.



Vít



[1]  https://github.com/k-takata/



OpenPGP_signature.asc
Description: OpenPGP digital signature
-- 
___
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-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

fedpkg considering public key as private and refusing to give access

[Anirban Mitra via devel]

when i run command 
  fedpkg pull
I get the following warning 
@@@
@         WARNING: UNPROTECTED PRIVATE KEY FILE!          @
@@@
Permissions 0644 for '/home/user/.ssh/id_rsa.pub' are too open.
It is required that your private key files are NOT accessible by others.
This private key will be ignored.
Load key "/home/user/.ssh/id_rsa.pub": bad permissions
u...@pkgs.fedoraproject.org: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
Could not execute pull: Failed to execute command.

I checked that id_rsa has permission 0600 and id_rsa.pub has permission 0644 
What may be wrong? 
-- 
___
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-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Regenerating rescue kernels (Fedora upgrade documentation)

[Clemens Lang]

Hi Jered,

> On 30. Apr 2025, at 16:52, Jered Floyd  wrote:
> 
> 
> Once installed, the rescue kernel will be regenerated as long as dracut is 
> the initrd generator. See /usr/lib/kernel/install.d/51-dracut-rescue.install 
> for details.
> 
> This seems to be incomplete or incorrect, because that package is installed 
> but I've never had rescue kernels generated.  The referenced file 
> (/usr/lib/kernel/install.d/51-dracut-rescue.install) isn't particularly 
> useful to be referenced for details because it's a shell script with no user 
> documentation.
> 
> Before I dig in and become a dracut expert... is this an easy doc fix for 
> someone familiar?

Installing dracut-config-rescue only enables re-generation of the rescue kernel 
when the next kernel update happens, it does not trigger re-generation of the 
rescue kernel on its own.

If you want to do that, the simplest way is probably to just `dnf reinstall` 
the kernel. Alternatively, invoking /usr/bin/kernel-install with the right 
parameters will run this scriptlet, and also re-generate the rescue kernel.


HTH,
Clemens
-- 
Clemens Lang
RHEL Crypto Team
Red Hat

-- 
___
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-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Oniguruma project ended

[Remi Collet]

Hi,

See https://github.com/kkos/oniguruma/

=> "This project ended on April 24, 2025."

I see some projects using it
bat
bfs
comrak
git-delta
jq
kitutuki
lino
mfiler3
mfiler4
ochusha
php-mbstring
python3-onigurumacffi
saphire
slang-slsh
uutils-coreutils
xyzsh

Is there people taking maintenance for it ?
Other alternative ?
Ayy plan for Fedora ?


Regards,
Remi
--
___
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-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Any Ruby folks interested in bringing back Taskjuggler?

[Ankur Sinha]

On Tue, Apr 29, 2025 13:59:09 +0300, Benson Muite wrote:
> Hi Ankur,

Hi Benson,

> On Mon, Apr 28, 2025, at 10:50 PM, Ankur Sinha wrote:
> > Hi folks,
> >
> > 
> 
> Happy to help with this.

Awesome!

I've taken ownership of the package now and added you as a co-admin too.

-- 
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) | 
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London


signature.asc
Description: PGP signature
-- 
___
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-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Any Ruby folks interested in bringing back Taskjuggler?

[Ankur Sinha]

On Tue, Apr 29, 2025 11:07:50 -0300, Yasmin de Souza wrote:
> Hi there,
> 
> I have some Ruby experience and would love to help co-maintain the project. 
> I'm
> not very experienced yet, but I'm eager to get involved and contribute to
> Taskjuggler.

Hi Yasmin,

Thanks, that's great. Could you tell me your FAS username please and
I'll add you to the package too?

-- 
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) | 
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London


signature.asc
Description: PGP signature
-- 
___
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-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Oniguruma project ended

[huangye wudeng]

Ruby switched from oniguruma to onigurumo (repo 
https://github.com/k-takata/Onigmo) a long time ago (around 2021).
see https://github.com/ruby/ruby/pull/4306/files

Onigmo is a regular expressions library forked from Oniguruma.

See also the Wiki page: https://github.com/k-takata/Onigmo/wiki
-- 
___
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-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Any Ruby folks interested in bringing back Taskjuggler?

[Ankur Sinha]

On Tue, Apr 29, 2025 13:44:05 +0200, Vít Ondruch wrote:
> Seems this is the failing test suite, right?
> https://download.copr.fedorainfracloud.org/results/ankursinha/rubygem-taskjuggler/fedora-rawhide-x86_64/08910683-rubygem-taskjuggler/builder-live.log.gz
> Given the test case name:
> 
> ~~~
> 
>   2) TaskJuggler::StatusSheetTest TaskJuggler::StatusSheetSender should have
> generated 1 mail
> 
> ~~~
> And comparing with the last know Fedora version of the .spec:
> 
> https://src.fedoraproject.org/rpms/rubygem-taskjuggler/blob/20c97f4e0dbf3e5af96bb0688ef8256d467fe0e4/f/rubygem-taskjuggler.spec
> 
> Isn't the `BuildRequires: rubygem(mail)` what is missing?
> 
> And yes, there seems to be two parts of the test suite, one using
> rubygem-rspec while the other seems to be using rubygem-test-unit (yes, the
> former .spec file tried to convert the test suite to be executed by
> Minitest, but don't do that, stay with rubygem-test-unit and save some
> troubles to you). Executing the test/all.rb for the latter should be enough.

I've disabled the tests at the moment, so that'll be the first thing
I'll be working on for the re-review.

The new version, 3.8.1, is out, and that's what the COPR is at. There
are a few niggles with Ruby 3.4 at the moment from the looks of it[1],
but upstream is responsive and aware, so they should be fixed soon. I
did look into them, but they were beyond my limited Ruby-fu, so if any
Ruby pros want to take a look and submit fixes upstream, that'll be
great too:

https://github.com/taskjuggler/TaskJuggler/issues/303

-- 
Thanks,
Regards,
Ankur Sinha "FranciscoD" (He / Him / His) | 
https://fedoraproject.org/wiki/User:Ankursinha
Time zone: Europe/London


signature.asc
Description: PGP signature
-- 
___
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-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Self Introduction: John Whitington

[Dominik 'Rathann' Mierzejewski via devel]

Hello, John!

On Wednesday, 30 April 2025 at 14:12, John Whitington wrote:
> Hello everyone,
> 
> (Per 
> https://docs.fedoraproject.org/en-US/package-maintainers/Joining_the_Package_Maintainers/
>  
> 
>  )
> 
> For the past fifteen or so years, I've been writing a set of command
> line tools for processing PDF files. You can find them here:
> 
> https://community.coherentpdf.com/ 
> 
> Recently, I've opened up the license. And so, it is suitable for
> inclusion in many package managers. Packaging OCaml programs being a
> somewhat niche pastime, I'm doing it myself.

That's fantastic! We have a few OCaml packagers around and you're most
welcome to Fedora!

You might want to take a look at:
https://docs.fedoraproject.org/en-US/packaging-guidelines/OCaml/

Regards,
Dominik
-- 
Fedora   https://fedoraproject.org
Deep in the human unconscious is a pervasive need for a logical universe that
makes sense. But the real universe is always one step beyond logic.
-- from "The Sayings of Muad'Dib" by the Princess Irulan
-- 
___
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-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Switch gnome-software to use a dnf5 plugin in rawhide

[Milan Crha]

On Tue, 2025-04-29 at 19:08 +0200, Adam Williamson wrote:
> I don't know why we didn't catch this in pre-testing;

Hi,
no problem, good the change in behavior was discovered. It's not a bad
thing per se, but it's also true the gnome-software can prepare updates
in the background, at least download them, then when the user click
"Download" it makes it quick, because the packages are ready.

I "paused" on the update, in a meaning I won't push it further until it
passes the Fedora QA tests. It'll need changes on the dnf5 side too,
most likely.

Should I make it explicit and cancel the update, or I can let it live
on its own until the changes are ready? I won't revert the git changes,
the mass rebuild is far away, there's some time to make this better.

Bye,
Milan

-- 
___
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-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Fedora CoreOS Community Meeting Minutes 2025-04-23

[Michael Armijo]

Minutes:
https://meetbot-raw.fedoraproject.org/meeting-1_matrix_fedoraproject-org/2025-04-23/fedora-coreos-meeting.2025-04-23-16.31.html
Minutes (text):
https://meetbot-raw.fedoraproject.org/meeting-1_matrix_fedoraproject-org/2025-04-23/fedora-coreos-meeting.2025-04-23-16.31.txt
Log:
https://meetbot-raw.fedoraproject.org/meeting-1_matrix_fedoraproject-org/2025-04-23/fedora-coreos-meeting.2025-04-23-16.31.log.html

=
# #meeting-1:fedoraproject.org: fedora_coreos_meeting
=

Meeting started by @marmijo:fedora.im at 2025-04-23 16:31:32



Meeting summary
---
* TOPIC: roll call (@marmijo:fedora.im, 16:31:41)
* TOPIC: Action items from last meeting (@marmijo:fedora.im, 16:39:16)
* INFO: We skipped the meeting last week due to availability.
(@marmijo:fedora.im, 16:40:09)
* TOPIC: Review Fedora 43 Release Schedule (@marmijo:fedora.im, 16:40:40)
* LINK: https://fedorapeople.org/groups/schedule/f-43/f-43-key-tasks.html
(@marmijo:fedora.im, 16:40:48)
* TOPIC: Migrate existing systems to OCI updates (@marmijo:fedora.im, 16:47:47)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1890
(@marmijo:fedora.im, 16:47:53)
* INFO: We are preparing the migration of existing nodes to
container images for updates. Help with testing welcomed.
(@siosm:matrix.org, 16:55:53)
* LINK: https://github.com/coreos/fedora-coreos-config/pull/3355
(@siosm:matrix.org, 16:56:05)
* LINK: https://github.com/coreos/fedora-coreos-config/pull/3458
(@siosm:matrix.org, 16:56:12)
* TOPIC: Enable automatic bootloader updates (@marmijo:fedora.im, 16:56:41)
* LINK: https://github.com/coreos/fedora-coreos-tracker/issues/1468
(@marmijo:fedora.im, 16:56:47)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=2361849
(@conan_kudo:matrix.org, 17:04:21)
* TOPIC: Open Floor (@marmijo:fedora.im, 17:28:26)

Meeting ended at 2025-04-23 17:31:04

Action items


People Present (lines said)
---
* @dustymabe:matrix.org (47)
* @siosm:matrix.org (36)
* @marmijo:fedora.im (30)
* @jlebon:fedora.im (11)
* @zodbot:fedora.im (7)
* @conan_kudo:matrix.org (6)
* @aaradhak:matrix.org (3)
* @meetbot:fedora.im (2)
* @ravanelli:matrix.org (1)
* @fifofonix:matrix.org (1)
* @jbtrystram:matrix.org (1)
-- 
___
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-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: fedpkg considering public key as private and refusing to give access

[Benson Muite]

On Wed, Apr 30, 2025, at 6:13 PM, Anirban Mitra via devel wrote:
> when i run command 
>   fedpkg pull
> I get the following warning 
> @@@
> @         WARNING: UNPROTECTED PRIVATE KEY FILE!          @
> @@@
> Permissions 0644 for '/home/user/.ssh/id_rsa.pub' are too open.
> It is required that your private key files are NOT accessible by others.
> This private key will be ignored.
> Load key "/home/user/.ssh/id_rsa.pub": bad permissions
> u...@pkgs.fedoraproject.org: Permission denied (publickey).
> fatal: Could not read from remote repository.
>
> Please make sure you have the correct access rights
> and the repository exists.
> Could not execute pull: Failed to execute command.
>
> I checked that id_rsa has permission 0600 and id_rsa.pub has permission 
> 0644 
> What may be wrong? 
> -- 

Public key should have -rw-r--r-- (0644)
Private key should have -rw--- (0600)
Which seems ok.  However, your public key seems to be recognized as a private 
key. Not sure why this is.
-- 
___
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-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: fedpkg considering public key as private and refusing to give access

[Peter Pentchev]

On Wed, Apr 30, 2025 at 03:13:35PM +, Anirban Mitra via devel wrote:
> when i run command 
>   fedpkg pull
> I get the following warning 
> @@@
> @         WARNING: UNPROTECTED PRIVATE KEY FILE!          @
> @@@
> Permissions 0644 for '/home/user/.ssh/id_rsa.pub' are too open.
> It is required that your private key files are NOT accessible by others.
> This private key will be ignored.
> Load key "/home/user/.ssh/id_rsa.pub": bad permissions
> u...@pkgs.fedoraproject.org: Permission denied (publickey).
> fatal: Could not read from remote repository.
> 
> Please make sure you have the correct access rights
> and the repository exists.
> Could not execute pull: Failed to execute command.
> 
> I checked that id_rsa has permission 0600 and id_rsa.pub has permission 0644 
> What may be wrong? 

Is there a chance that there is some kind of mistake in your ~/.ssh/config file
saying something like "IdentityFile /path/to/id_rsa.pub" so that OpenSSH
would think that id_rsa.pub is a private keyfile and not a public one?

G'luck,
Peter
 
-- 
Peter Pentchev  r...@ringlet.net r...@debian.org pe...@morpheusly.com
PGP key:https://www.ringlet.net/roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13


signature.asc
Description: PGP signature
-- 
___
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-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Regenerating rescue kernels (Fedora upgrade documentation)

[Jered Floyd]

Hi Clemens,

On Wed, Apr 30, 2025 at 11:19 AM Clemens Lang  wrote:

>
> Installing dracut-config-rescue only enables re-generation of the rescue
> kernel when the next kernel update happens, it does not trigger
> re-generation of the rescue kernel on its own.


Oh, yes -- I understand this part!  I installed the package many fedora
releases ago, but rescue kernel generation on new kernel update hasn't
happened on any of my systems.  So there seems to be another step missing
from the doc, but it's not immediately clear to me what.

--Jered
-- 
___
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-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: failed to add subkeys for /var/cache/PackageKit/43/metadata/google-chrome-rawhide-x86_64/linux_signing_key.pub to rpmdb

[Petr Pisar]

V Tue, Apr 29, 2025 at 09:32:18PM -, Ryan Bach via devel napsal(a):
> failed to add subkeys for 
> /var/cache/PackageKit/43/metadata/google-chrome-rawhide-x86_64/linux_signing_key.pub
>  to rpmdb

Report it please against PackageKit in Fedora's Bugzilla and don't forget to
describe how a repository with the problematic key is configured on your
system.

I believe the cause is that Google distributes invalid keys in that file. See
 and
.

-- Petr


signature.asc
Description: PGP signature
-- 
___
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-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Self Introduction: John Whitington

[John Whitington]

Hello everyone,

(Per 
https://docs.fedoraproject.org/en-US/package-maintainers/Joining_the_Package_Maintainers/
 

 )

For the past fifteen or so years, I've been writing a set of command line tools 
for processing PDF files. You can find them here:

https://community.coherentpdf.com/ 

Recently, I've opened up the license. And so, it is suitable for inclusion in 
many package managers. Packaging OCaml programs being a somewhat niche pastime, 
I'm doing it myself.

Thanks,

John

-- 
John Whitington
Director, Coherent Graphics Ltd

-- 
___
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-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Self Introduction: John Whitington

[Alexander Sosedkin]

On Wed, Apr 30, 2025 at 2:13 PM John Whitington
 wrote:
> (Per 
> https://docs.fedoraproject.org/en-US/package-maintainers/Joining_the_Package_Maintainers/
>  )
>
> For the past fifteen or so years, I've been writing a set of command line 
> tools for processing PDF files. You can find them here:
>
> https://community.coherentpdf.com/
>
> Recently, I've opened up the license. And so, it is suitable for inclusion in 
> many package managers. Packaging OCaml programs being a somewhat niche 
> pastime, I'm doing it myself.

(OCaml pdf manipu-- wait a minute!)

Hi, John, just wanna let you know that cpdf is outright wonderful.
I used it last year when I needed a
debug side-by-side-with-aligning-blanks-inserted build
of my book written in two languages at once,
and it was an absolute godsend:
blazing fast with adequate interface and perfect documentation.
I found it by searching nixpkgs, made it do what I wanted in mere minutes
and then kept reading the manual anyway, just for fun.
Just checked it out again, and it seems like it got even longer?
Glad to see it coming to Fedora as well, and welcome!

-- 
___
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-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Fedora eln compose report: 20250501.n.0 changes

[Fedora ELN Report]

OLD: Fedora-eln-20250430.n.0
NEW: Fedora-eln-20250501.n.0

= SUMMARY =
Added images:0
Dropped images:  0
Added packages:  0
Dropped packages:0
Upgraded packages:   21
Downgraded packages: 1

Size of added packages:  0 B
Size of dropped packages:0 B
Size of upgraded packages:   966.80 MiB
Size of downgraded packages: 23.97 MiB

Size change of upgraded packages:   1.62 MiB
Size change of downgraded packages: -26.10 KiB

= ADDED IMAGES =

= DROPPED IMAGES =

= ADDED PACKAGES =

= DROPPED PACKAGES =

= UPGRADED PACKAGES =
Package:  anaconda-43.17-1.eln148
Old package:  anaconda-43.16-1.eln147
Summary:  Graphical system installer
RPMs: anaconda anaconda-core anaconda-dracut anaconda-gui 
anaconda-install-env-deps anaconda-install-img-deps anaconda-tui 
anaconda-widgets anaconda-widgets-devel
Size: 16.98 MiB
Size change:  -28.66 KiB
Changelog:
  * Tue Apr 29 2025 Packit  - 43.17-1
  - pyanaconda: storage: efi: never try to decode utf8 when calling efibootmgr
(k.koukiou)
  - Add additional config_get Dracut function tests (jkonecny)
  - Run restorecon after copying logs (champetier.etienne)
  - rpm_ostree/installation.py: fix image deployment on s390x (nikita)


Package:  bind-32:9.18.36-1.eln148
Old package:  bind-32:9.18.35-2.eln147
Summary:  The Berkeley Internet Name Domain (BIND) DNS (Domain Name System) 
server
RPMs: bind bind-chroot bind-devel bind-dnssec-utils bind-doc bind-libs 
bind-utils
Size: 11.85 MiB
Size change:  -16.60 KiB
Changelog:
  * Fri Apr 25 2025 Petr Mensik  - 32:9.18.36-1
  - Update to 9.18.36 (rhbz#2346607)


Package:  bind-dyndb-ldap-11.11-4.eln148
Old package:  bind-dyndb-ldap-11.11-3.eln147
Summary:  LDAP back-end plug-in for BIND
RPMs: bind-dyndb-ldap
Size: 443.28 KiB
Size change:  -474 B
Changelog:
  * Fri Apr 25 2025 Petr Menk  - 11.11-4
  - Rebuilt for BIND 9.18.36 (rhbz#2346607)


Package:  bison-3.8.2-10.eln148
Old package:  bison-3.8.2-9.eln144
Summary:  A GNU general-purpose parser generator
RPMs: bison bison-devel bison-runtime
Size: 4.18 MiB
Size change:  -8.20 KiB
Changelog:
  * Thu Jan 16 2025 Fedora Release Engineering  - 
3.8.2-10
  - Rebuilt for https://fedoraproject.org/wiki/Fedora_42_Mass_Rebuild


Package:  container-selinux-4:2.237.0-1.eln148
Old package:  container-selinux-4:2.236.0-1.eln146
Summary:  SELinux policies for container runtimes
RPMs: container-selinux
Size: 58.48 KiB
Size change:  -697 B
Changelog:
  * Mon Apr 28 2025 Packit  - 4:2.237.0-1
  - Update to 2.237.0 upstream release


Package:  firefox-138.0-1.eln148
Old package:  firefox-137.0.2-3.eln147
Summary:  Mozilla Firefox Web browser
RPMs: firefox
Size: 302.11 MiB
Size change:  1.13 MiB
Changelog:
  * Tue Apr 22 2025 Martin Stransky  - 138.0-1
  - Updated to 138.0

  * Sat Apr 26 2025 Bojan Smojver  - 138.0-1
  - Add fix for mzbz#1957628
  - Remove browser/features/*.xpi files, no longer shipped


Package:  libxkbcommon-1.9.0-1.eln148
Old package:  libxkbcommon-1.8.1-1.eln147
Summary:  X.Org X11 XKB parsing library
RPMs: libxkbcommon libxkbcommon-devel libxkbcommon-x11 
libxkbcommon-x11-devel
Size: 1.05 MiB
Size change:  35.20 KiB
Changelog:
  * Tue Apr 29 2025 Peter Hutterer  - 1.9.0-1
  - libkxbcommon 1.9.0


Package:  mokutil-2:0.7.2-1.eln148
Old package:  mokutil-2:0.7.1-5.eln146
Summary:  Tool to manage UEFI Secure Boot MoK Keys
RPMs: mokutil
Size: 96.40 KiB
Size change:  560 B
Changelog:
  * Tue Apr 29 2025 Leo Sandoval  - 0.7.2-1
  - Bump version to 0.7.2 upstream tag
  - Incorporate patch with enables --help on non-supported systems


Package:  pcp-6.3.7-4.eln148
Old package:  pcp-6.3.7-3.eln147
Summary:  System-level performance monitoring and performance management
RPMs: pcp pcp-conf pcp-devel pcp-doc pcp-export-pcp2elasticsearch 
pcp-export-pcp2graphite pcp-export-pcp2influxdb pcp-export-pcp2json 
pcp-export-pcp2openmetrics pcp-export-pcp2spark pcp-export-pcp2xml 
pcp-export-pcp2zabbix pcp-export-zabbix-agent pcp-geolocate pcp-gui 
pcp-import-collectl2pcp pcp-import-ganglia2pcp pcp-import-iostat2pcp 
pcp-import-mrtg2pcp pcp-import-sar2pcp pcp-libs pcp-libs-devel 
pcp-pmda-activemq pcp-pmda-amdgpu pcp-pmda-apache pcp-pmda-bash pcp-pmda-bcc 
pcp-pmda-bind2 pcp-pmda-bonding pcp-pmda-bpf pcp-pmda-bpftrace pcp-pmda-cifs 
pcp-pmda-cisco pcp-pmda-dbping pcp-pmda-denki pcp-pmda-dm pcp-pmda-docker 
pcp-pmda-ds389 pcp-pmda-ds389log pcp-pmda-elasticsearch pcp-pmda-farm 
pcp-pmda-gluster pcp-pmda-gpfs pcp-pmda-gpsd pcp-pmda-hacluster 
pcp-pmda-haproxy pcp-pmda-infiniband pcp-pmda-json pcp-pmda-libvirt 
pcp-pmda-lio pcp-pmda-lmsensors pcp-pmda-logger pcp-pmda-lustre 
pcp-pmda-lustrecomm pcp-pmda-mailq pcp-pmda-memcache pcp-pmda-mic 
pcp-pmda-mongodb pcp-pmda-mounts pcp-pmda-mssql pcp-pmda-mysql pcp-pmda-named

Re: Regenerating rescue kernels (Fedora upgrade documentation)

[Samuel Sieb]

On 4/30/25 7:52 AM, Jered Floyd wrote:


I run into this every time I upgrade Fedora, but I always forget to 
follow-up on it... 42's the charm!


In the Upgrading Fedora docs (https://docs.fedoraproject.org/en-US/ 
quick-docs/upgrading-fedora-offline/#sect-update-rescue-kernel docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/#sect- 
update-rescue-kernel>) one of the optional post-upgrade steps is 
updating the rescue kernel.  The documentation linked says:


The rescue kernel regeneration process can be automated by installing 
the dracut-config-rescue package.


sudo dnf install dracut-config-rescue

Once installed, the rescue kernel will be regenerated as long as dracut 
is the initrd generator. See /usr/lib/kernel/install.d/51-dracut- 
rescue.install for details.


This seems to be incomplete or incorrect, because that package is 
installed but I've never had rescue kernels generated.  The referenced 
file (/usr/lib/kernel/install.d/51-dracut-rescue.install) isn't 
particularly useful to be referenced for details because it's a shell 
script with no user documentation.


Before I dig in and become a dracut expert... is this an easy doc fix 
for someone familiar?


That doc page is a bit unclear.  That package will cause the rescue 
image to be created if it doesn't exist.  You only need to do the "rm" 
part and the next kernel (re)install will re-create the rescue images.


--
___
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-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: PSA - A change in Docker cli plugin version management (Compose, BuildKit, Buildx)

[Sérgio Basto via devel]

On Wed, 2025-04-30 at 08:05 -0700, Brad Smith wrote:
> FESCo has approved an update policy exception that encompasses these
> Docker plugins: Compose, BuildKit, and Buildx
> (https://pagure.io/fesco/issue/3394). The rpms for these plugins will
> now track the current plugin release across all Fedora releases. The
> maintainers for all three plugins only support the current release
> for
> bug and security fixes.
> 
> In the next few days versions for these rpms will be submitted for
> F42
> and F41. No updates for F40 are planned given the imminent EOL for
> F40
> and the very old version of Compose present.
> 
> Please let me know if you have any questions or concerns.
> 

Great news Brad, you / we managed to bring back the docker ecosystem

-- 
Sérgio M. B.
-- 
___
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-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Oniguruma project ended

[Fabio Valentini]

On Wed, Apr 30, 2025 at 10:23 AM Remi Collet  wrote:
>
> Hi,
>
> See https://github.com/kkos/oniguruma/
>
> => "This project ended on April 24, 2025."
>
> I see some projects using it
> bat
> bfs
> comrak
> git-delta
> jq
> kitutuki
> lino
> mfiler3
> mfiler4
> ochusha
> php-mbstring
> python3-onigurumacffi
> saphire
> slang-slsh
> uutils-coreutils
> xyzsh

At least some of these can be easily switched to a different regex
implementation (bat, git-delta) - oniguruma is just the default
backend, but there is an option to build with the (very good) Rust
"regex" crate instead of linking to oniguruma.

Fabio
-- 
___
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-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue