[Bug 2251622] CVE-2023-47038 perl: Write past buffer end via illegal user-defined Unicode property [fedora-all]

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2251622



--- Comment #5 from Fedora Update System  ---
FEDORA-2023-c67f4dbf13 has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh
--advisory=FEDORA-2023-c67f4dbf13`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2023-c67f4dbf13

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2251622

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202251622%23c5
--
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2251622] CVE-2023-47038 perl: Write past buffer end via illegal user-defined Unicode property [fedora-all]

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2251622

Fedora Update System  changed:

   What|Removed |Added

 Status|MODIFIED|ON_QA



--- Comment #4 from Fedora Update System  ---
FEDORA-2023-9ef8a60a05 has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh
--advisory=FEDORA-2023-9ef8a60a05`
You can provide feedback for this update here:
https://bodhi.fedoraproject.org/updates/FEDORA-2023-9ef8a60a05

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information
on how to test updates.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2251622

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202251622%23c4
--
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[EPEL-devel] Fedora EPEL 7 updates-testing report

[updates]

The following Fedora EPEL 7 Security updates need testing:
 Age  URL
   6  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-1c906d04ee   
golang-1.20.10-3.el7
   4  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-a371f42add   
openssl11-1.1.1k-6.el7


The following builds have been pushed to Fedora EPEL 7 updates-testing

chromium-119.0.6045.199-1.el7

Details about builds:



 chromium-119.0.6045.199-1.el7 (FEDORA-EPEL-2023-46696cc30b)
 A WebKit (Blink) powered web browser that Google doesn't want you to use

Update Information:

update to 119.0.6045.199, upstream security release  * High CVE-2023-6348: Type
Confusion in Spellcheck * High CVE-2023-6347: Use after free in Mojo * High
CVE-2023-6346: Use after free in WebAudio * High CVE-2023-6350: Out of bounds
memory access in libavif * High CVE-2023-6351: Use after free in libavif * High
CVE-2023-6345: Integer overflow in Skia

ChangeLog:

* Wed Nov 29 2023 Than Ngo  - 119.0.6045.199-1
- update to 119.0.6045.199
* Sun Nov 19 2023 Than Ngo  - 119.0.6045.159-2
- fix ffmpeg conflicts

References:

  [ 1 ] Bug #2252009 - CVE-2023-6346 CVE-2023-6347 CVE-2023-6350 CVE-2023-6351 
chromium: various flaws [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2252009
  [ 2 ] Bug #2252188 - CVE-2023-6345 chromium: chromium-browser: Integer 
overflow [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2252188
  [ 3 ] Bug #2252191 - CVE-2023-6348 chromium: chromium-browser: Type Confusion 
in Spellcheck [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2252191


--
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[EPEL-devel] Fedora EPEL 8 updates-testing report

[updates]

The following builds have been pushed to Fedora EPEL 8 updates-testing

chromium-119.0.6045.199-1.el8
python-virt-firmware-23.11-1.el8
reproc-14.2.4-1.20230609git1c07bdb.el8

Details about builds:



 chromium-119.0.6045.199-1.el8 (FEDORA-EPEL-2023-d47bce8e4e)
 A WebKit (Blink) powered web browser that Google doesn't want you to use

Update Information:

update to 119.0.6045.199, upstream security release  * High CVE-2023-6348: Type
Confusion in Spellcheck * High CVE-2023-6347: Use after free in Mojo * High
CVE-2023-6346: Use after free in WebAudio * High CVE-2023-6350: Out of bounds
memory access in libavif * High CVE-2023-6351: Use after free in libavif * High
CVE-2023-6345: Integer overflow in Skia

ChangeLog:

* Wed Nov 29 2023 Than Ngo  - 119.0.6045.199-1
- update to 119.0.6045.199
* Sun Nov 19 2023 Than Ngo  - 119.0.6045.159-2
- fix ffmpeg conflicts

References:

  [ 1 ] Bug #2252009 - CVE-2023-6346 CVE-2023-6347 CVE-2023-6350 CVE-2023-6351 
chromium: various flaws [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2252009
  [ 2 ] Bug #2252188 - CVE-2023-6345 chromium: chromium-browser: Integer 
overflow [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2252188
  [ 3 ] Bug #2252191 - CVE-2023-6348 chromium: chromium-browser: Type Confusion 
in Spellcheck [epel-all]
https://bugzilla.redhat.com/show_bug.cgi?id=2252191




 python-virt-firmware-23.11-1.el8 (FEDORA-EPEL-2023-ce154fd563)
 Tools for virtual machine firmware volumes

Update Information:

update to version 23.11

ChangeLog:

* Thu Nov 30 2023 Gerd Hoffmann  - 23.11-1
- update to version 23.11




 reproc-14.2.4-1.20230609git1c07bdb.el8 (FEDORA-EPEL-2023-32952bbe06)
 A cross-platform (C99/C++11) process library

Update Information:

Build for EPEL

ChangeLog:

* Fri Aug  4 2023 Orion Poplawski  - 14.2.4-1.20230609git1c07bdb
- Update to 14.2.4 + latest git (FTBFS bz#2171704)
* Fri Jul 21 2023 Fedora Release Engineering  - 
14.2.2-6
- Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild
* Fri Jan 20 2023 Fedora Release Engineering  - 
14.2.2-5
- Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild
* Sat Jul 23 2022 Fedora Release Engineering  - 
14.2.2-4
- Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild
* Fri Jan 21 2022 Fedora Release Engineering  - 
14.2.2-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild
* Fri Jul 23 2021 Fedora Release Engineering  - 
14.2.2-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_35_Mass_Rebuild
* Wed Jun 16 2021 Orion Poplawski  - 14.2.2-1
- Initial package

References:

  [ 1 ] Bug #2252317 - Please branch and build reproc for EPEL8 and EPEL9
https://bugzilla.redhat.com/show_bug.cgi?id=2252317


--
___
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-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/epel-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: dracut problems quick docs page requires help

[Peter Boy]

> Am 30.11.2023 um 09:23 schrieb David Tardon :
> 
> Hi,
> 
> On Tue, 2023-11-21 at 06:39 +, Ankur Sinha wrote:
>> Hi folks,
>> 
>> We have this issue open on the quick-docs repo:
>> https://pagure.io/fedora-docs/quick-docs/issue/641
>> 
>> TLDR; the "debug-dracut-problems" quick doc seems to be out of date
>> and
>> needs review/updating.
>> 
>> https://docs.fedoraproject.org/en-US/quick-docs/debug-dracut-problems/
> 
> "It hasn't been changed in a while" does not equal "it's out of date".
> The kernel command line arguments for dracut that the page mentions
> still work the same way they worked 10 years ago. (With the exception
> of rd.udev.debug, which is ignored by systemd-based initrds; I've
> submitted a PR to fix that. And rd.udev.info is kinda pointless, as
> "info" is the default log level of systemd-udevd.)
> 
>> nfortunately, I don't know enough about dracut to do this myself.
>> Would
>> someone that knows this stuff please consider reviewing (even
>> updating?)
>> the page so we know what to do with it next?
> 
> Are there _actual_ problems there, i.e., something that doesn't work
> anymore?


Can I take that as „I had a look over the text and found no incorrect or 
outdated information about dracut“?

In that case I would want to change the "last review“ date.

(FYI: This is part of our strategy to increase the validity and trustworthiness 
of Fedora documentation, so your effort would really help a lot.) 

--
Peter Boy
https://fedoraproject.org/wiki/User:Pboy
p...@fedoraproject.org 

Timezone: CET (UTC+1) / CEST (UTC+2)

Fedora Server Edition Working Group member
Fedora Docs team contributor and board member
Java developer and enthusiast






--
___
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: packaging of nix

[Piotr Szubiakowski]

Hey!

On Wed, 2023-11-29 at 23:27 +, Zbigniew Jędrzejewski-Szmek wrote:

> I looked [1], and I see some differences in packaging:
> - I opted to put the libraries in /usr/lib64/nix/ and retain the
> RUNPATH
>   so that they get loaded from there. My thinking was that the
> libraries
>   are "private", i.e. they are used by the nix binaries and nothing
> else.
>   But I see that you have a -devel subpackage… Is it actually useful
>   for anything?
> 
>   (If there is no known user, then I'd prefer to not add the -devel
> package
>   initially. If it turns out to be useful later on, it can always be
>   added.)

I think that's a better approach. I added the devel package because
headers and the pkg-config file exist. Potential clients may be Nix
Python or Go bindings. It's unlikely we would need them in Fedora
anytime soon. I would also vote to add a devel package when requested.

> - for the users, I'd prefer to create a sysusers file and submit it
> upstream.

Looks good to me! Until accepted upstream, we can keep userfile as an
additional source.

I think the multi-user mode[1] of Nix would better fit Fedroa. It's
also how NixOS uses Nix. The multi-user mode requires the mentioned
users and Nix daemon.

> - I see you have aws-sdk-cpp-devel. The build seemed to work fine
> without.

Yes, we can build Nix without it. From AWS SDK for C++, the S3 and the
transfer APIs are helpful. They allow access to the Nix binary cache
via S3 "protocol".

I find the AWS SDK for C++ easy to build but quite challenging to
package. So maybe it is better to start without.

> - I see you have '%undefine _hardened_build'. I didn't see any issues
> without
>   that… Maybe it's not needed anymore?

Probably, it's not needed. I'll try to build a newer version of Nix on
a more recent version of Fedora.

Regarding collaboration, we may prepare an initial SPEC file on a
public GitHub/GitLab repository, where we can work via Pull/Merge
Requests.

I would happily test the outputs of our work. We have quite a strong
Nix community at ESO :)

Cheers,

Piotr

[1] https://nixos.org/manual/nix/stable/installation/multi-user

--
___
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

[Bug 2252295] perl-Business-ISBN-Data-20231130.001 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2252295

Paul Howarth  changed:

   What|Removed |Added

   Doc Type|--- |If docs needed, set a value
 Status|NEW |CLOSED
   Fixed In Version||perl-Business-ISBN-Data-202
   ||31130.001-1.fc40
 Resolution|--- |RAWHIDE
Last Closed||2023-11-30 17:54:16



--- Comment #1 from Paul Howarth  ---
Already built for Rawhide:
https://koji.fedoraproject.org/koji/taskinfo?taskID=109738200


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2252295

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202252295%23c1
--
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2252295] New: perl-Business-ISBN-Data-20231130.001 is available

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2252295

Bug ID: 2252295
   Summary: perl-Business-ISBN-Data-20231130.001 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Business-ISBN-Data
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: jples...@redhat.com, ka...@ucw.cz, mspa...@redhat.com,
p...@city-fan.org, perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 20231130.001
Upstream release that is considered latest: 20231130.001
Current version/release in rawhide: 20231125.001-1.fc40
URL: https://metacpan.org/dist/Business-ISBN-Data/

Please consult the package updates policy before you issue an update to a
stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at:
https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging
changes that need to be made. Specifically, please remember that it is your
responsibility to review the new version to ensure that the licensing is still
correct and that no non-free or legally problematic items have been added
upstream.


Based on the information from Anitya:
https://release-monitoring.org/project/2674/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/perl-Business-ISBN-Data


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2252295

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202252295%23c0
--
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Schedule for Thursday's FESCo Meeting (2023-11-30)

[Stephen Gallagher]

This meeting had to be canceled due to lack of quorum.

On Thu, Nov 30, 2023 at 9:41 AM Zbigniew Jędrzejewski-Szmek
 wrote:
>
> Following is the list of topics that will be discussed in the
> FESCo meeting Thursday at 17:00UTC in #fedora-meeting-2 on
> irc.libera.chat.
>
> To convert UTC to your local time, take a look at
>   http://fedoraproject.org/wiki/UTCHowto
>
> or run:
>   date -d '2023-11-30 17:00 UTC'
>
> Links to all issues to be discussed can be found at:
> https://pagure.io/fesco/report/meeting_agenda
>
> = Discussed and Voted in the Ticket =
>
> #3111 Change: Python3.13
> https://pagure.io/fesco/issue/3111
> APPROVED (+6, 0, 0)
>
> #3109 Change: Transitioning to Zlib-ng as compatible replacement for Zlib
> https://pagure.io/fesco/issue/3109
> APPROVED (+5, 0, 0)
>
> #3108 Change: Transitioning to Minizip-ng as compatible replacement for 
> Minizip
> https://pagure.io/fesco/issue/3108
> APPROVED (+4, 0, 0)
>
> #3107 Change: Removing SSSD 'files provider'
> https://pagure.io/fesco/issue/3107
> APPROVED (+5, 0, 0)
>
> #3106 Updates policy exception request for llhttp in F39 and F38
> https://pagure.io/fesco/issue/3106
> APPROVED (+4, 0, 0)
>
> #3102 Change: Ruby 3.3
> https://pagure.io/fesco/issue/3102
> APPROVED (+8,0,-0)
>
> #3100 Change: PostgreSQL 16
> https://pagure.io/fesco/issue/3100
> APPROVED (+7, 0, 0)
>
> #3099 Change: Modernize TBB
> https://pagure.io/fesco/issue/3099
> APPROVED(+9,0,-0)
>
> #3096 Change: Build Fedora with DNF 5
> https://pagure.io/fesco/issue/3096
> APPROVED: (+6, 0, 0)
>
> #3085 Nonresponsive maintainer: Karsten Hopp @karsten
> https://pagure.io/fesco/issue/3085
> APPROVED (+2, 0, -0)
>
>
> = Followups =
>
> #3097 Change: DNF Conditional File Lists
> https://pagure.io/fesco/issue/3097
>
> #3098 Change: Drop sshd Socket
> https://pagure.io/fesco/issue/3098
>
>
> = New business =
>
> #3101 Change: Remove OpenSSL Compat
> https://pagure.io/fesco/issue/3101
>
> #3103 Change: Tuned Replaces Power-profiles-daemon
> https://pagure.io/fesco/issue/3103
>
>
> = Open Floor =
>
> For more complete details, please visit each individual
> issue.  The report of the agenda items can be found at
> https://pagure.io/fesco/report/meeting_agenda
>
> If you would like to add something to this agenda, you can
> reply to this e-mail, file a new issue at
> https://pagure.io/fesco, e-mail me directly, or bring it
> up at the end of the meeting, during the open floor topic. Note
> that added topics may be deferred until the following meeting.
> --
> ___
> 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
--
___
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

Update on the Modern C initiative

[Florian Weimer]

This message is realted to:

  
  

The final patches for GCC 14 are currently under upstream review and
should land very soon.  Earlier, I had received feedback that the larger
community desires just one transition, so we end up with the following
warnings which turn into errors by default:

  -Wimplicit-function-declaration
  -Wimplicit-int
  -Wint-conversion
  -Wreturn-mismatch (new, previously part of -Wreturn-types)
  -Wdeclaration-missing-parameter-type (new, previously unnamed)
  -Wincompatible-pointer-types

Only the first two were covered in the initial Fedora conversion work.

I've done another round of test builds with an instrumented GCC for all
errors, and the numbers of problematic packages I have today are:

  autoconf
  all only
  implicit-function-declaration53   21
  implicit-int  20
  int-conversion   99   33
  return-mismatch  132
  declaration-missing-parameter-type00
  incompatible-pointer-types  374   50
  487   89

(I've updated the change page to describe those diagnostics briefly.)

The numbers don't add up because one package can have multiple issues.
Some of the reported issues are false positives, although the GCC
instrumentation is a bit better than it used to be.

The autoconf column covers packages which are particularly at risk for
silent miscompilation because of incorrect detection of build system
features.  This is based on file name heuristics and includes more than
just autoconf proper.

As you can see, the incompatible-pointer-types issues are a bit of a
problem.  We fixed over 800 packages during the first round, and now it
looks like we are only two thirds done.

It is unlikely that I will be able to work on all these issues
myself or with help from the people around me.  I just suggested to GCC
upstream that we may have to reconsider including this change in the GCC
14 release.

Consequently, my priorities are as follows:

* Try to resolve the autoconf issues in packages, to reduce the risk of
  silent miscompilation.

* Integrate a backport of the GCC 14 changes into the rawhide GCC 13
  version (rawhide only, not Fedora 39 or 38).  This will allow us
  to isolate these issues from GCC 14 issues that typically occur
  during the upcoming mass rebuild.

* Produce the final redhat-rpm-config integration, using -fpermissive
  for _build_type_safety_c 0, and -Wno-error= options for the higher
  type safety levels.  This obviously depends on -fpermissive and and
  the new warning names becoming available in rawhide, which is another
  reason for the GCC 13 backport.

* Come up with a way to resolve the Vala situation, likely by embedded
  “#pragma GCC diagnostic” in the generated C source files.  Vala is
  currently not able to generate type-safe C, and is unlikely that this
  going to change soon.  (The numbers above do not include packages
  which have failures in Vala code only.)  In some cases, there is
  nothing that can be done about this on the Vala source code side.  Not
  all of these type errors are harmless, of course, but I don't see a
  way to deal with this except by telling GCC to be less picky.

I'm attaching package maintainer lists, generated using the
find-package-maintainers script from fthe
 repository, for both
the full package set, and the autoconf-impacted package set.

Build logs with results from the instrumentation are available here;

  

We delete logs from that repository as packages get fixed.

Again, some of these are false positives.  The second link at the start
has instructions for a COPR repository if you want to verify things
locally (sadly the Koji build target is currently not in working order).

Thanks,
Florian
Maintainers by package:
0ad  kalev pcpa pwalter
389-ds-base  abbra jamiechap mreynolds spichugi tbordaz vashirov
3proxy   rathann
BibTool  mjg orion
BitchX   kme rdieter
Cython   churchyard ignatenkobrain nbecker stevetraylen
EMBOSS   spot
Io-language  limb
MagicPoint   jwrdegoede
ORBit2   alexl caolanm danw limb rhughes rstrode
OpenIPMI branto jridky pcahyna
SDL_imagejwrdegoede limb
TeXmacs  jnovy orion
Xaw3djwrdegoede orion
adobe-afdko  petersen vishalvvr
afflib   kwizart rebus
afpfs-ng rebus
ags  rathann
alfont   jwrdegoede
algol68g ol
alienarena   spot
alsa-tools   perex timj
anjuta   kalev limb
annobin

Schedule for Thursday's FESCo Meeting (2023-11-30)

[Zbigniew Jędrzejewski-Szmek]

Following is the list of topics that will be discussed in the
FESCo meeting Thursday at 17:00UTC in #fedora-meeting-2 on
irc.libera.chat.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2023-11-30 17:00 UTC'

Links to all issues to be discussed can be found at: 
https://pagure.io/fesco/report/meeting_agenda

= Discussed and Voted in the Ticket =

#3111 Change: Python3.13
https://pagure.io/fesco/issue/3111
APPROVED (+6, 0, 0)

#3109 Change: Transitioning to Zlib-ng as compatible replacement for Zlib
https://pagure.io/fesco/issue/3109
APPROVED (+5, 0, 0)

#3108 Change: Transitioning to Minizip-ng as compatible replacement for Minizip
https://pagure.io/fesco/issue/3108
APPROVED (+4, 0, 0)

#3107 Change: Removing SSSD 'files provider'
https://pagure.io/fesco/issue/3107
APPROVED (+5, 0, 0)

#3106 Updates policy exception request for llhttp in F39 and F38
https://pagure.io/fesco/issue/3106
APPROVED (+4, 0, 0)

#3102 Change: Ruby 3.3
https://pagure.io/fesco/issue/3102
APPROVED (+8,0,-0)

#3100 Change: PostgreSQL 16
https://pagure.io/fesco/issue/3100
APPROVED (+7, 0, 0)

#3099 Change: Modernize TBB
https://pagure.io/fesco/issue/3099
APPROVED(+9,0,-0)

#3096 Change: Build Fedora with DNF 5
https://pagure.io/fesco/issue/3096
APPROVED: (+6, 0, 0)

#3085 Nonresponsive maintainer: Karsten Hopp @karsten
https://pagure.io/fesco/issue/3085
APPROVED (+2, 0, -0)


= Followups =

#3097 Change: DNF Conditional File Lists
https://pagure.io/fesco/issue/3097

#3098 Change: Drop sshd Socket
https://pagure.io/fesco/issue/3098


= New business =

#3101 Change: Remove OpenSSL Compat
https://pagure.io/fesco/issue/3101

#3103 Change: Tuned Replaces Power-profiles-daemon
https://pagure.io/fesco/issue/3103


= Open Floor = 

For more complete details, please visit each individual
issue.  The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda

If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, e-mail me directly, or bring it
up at the end of the meeting, during the open floor topic. Note
that added topics may be deferred until the following meeting. 
--
___
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: [Fedocal] Reminder meeting : ELN SIG

[Stephen Gallagher]

On Thu, Nov 30, 2023 at 7:00 AM  wrote:
>
> Dear all,
>
> You are kindly invited to the meeting:
>ELN SIG on 2023-12-01 from 12:00:00 to 13:00:00 US/Eastern
>At fedora-meet...@irc.libera.chat
>
> The meeting will be about:
>

* Preparing for the fork to CentOS Stream 10 and the launch of Fedora ELN 11
** Upcoming mini-mass-rebuild for CentOS Stream 10 mass-import
--
___
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: Ancient compilation flags in my pkg - still needed ?

[Steve Grubb]

On Thursday, November 30, 2023 5:47:57 AM EST Michal Schorm wrote:
> I have this line in the SPECfile of 'mariadb' package:
> 
> CFLAGS="$CFLAGS -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE"
> 
> I read through these macros explanations:
>  
> https://www.gnu.org/software/libc/manual/html_node/Feature-Test-Macros.htm
>
> l however as I do not navigate well in the problematic, I haven't
> understood much. 
> My question is primarily, whether during the last 20 years something
> happened, making the line obsolete (e.g. these macros are no longer
> relevant, or they were added to the default build flags, ... )

You might want to check if  _GNU_SOURCE has been moved into the right 
Makefile.am files. Way back when, it may not have occurred to the developers to 
only use them for the compilation units that need them. If not, then keep it.

As for the others, they are to support gigantic files. It might have occurred 
to the developers to formalize this by adding an option in configure.ac. If 
they didn't, you may still need these to not regress when gigantic file 
support is needed.

I'd say, upstream should put all of these in the right places so that you do 
not pass them this way.

-Steve

--
___
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: Ancient compilation flags in my pkg - still needed ?

[İsmail Dönmez]

Hi,

On Thu, Nov 30, 2023 at 11:50 AM Michal Schorm  wrote:
>
> I have this line in the SPECfile of 'mariadb' package:
>
> CFLAGS="$CFLAGS -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE"

These are the necessary flags to support large (> 4 GB) files on 32bit
systems, any modern code would already define these already. You
should look into the build system for mariadb and confirm this, and
then you can remove the flags.

Regards,
Ismail
--
___
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: Ancient compilation flags in my pkg - still needed ?

[Priscila Gutierres]

Your reflection will make me a better engineer
Thank you

Em qui., 30 de nov. de 2023 às 08:19, Michal Schorm 
escreveu:

> On Thu, Nov 30, 2023 at 11:53 AM Priscila Gutierres 
> wrote:
> > When reading your email I thought about this video
> > https://youtu.be/U4ALzqqUIS8?si=_D5seS8Nu_0fxYdO
>
> Yeah, on point :)
>
> But as long as I get commit messages explaining *what* has been done
> (which is obvious from the code), instead of *why* it was done, I'm
> more of an archeologist, than a software engineer.
> If people would write *useful* commit messages, I wouldn't need to ask
> such questions.
>
> Michal
>
> --
>
> Michal Schorm
> Software Engineer
> Core Services - Databases Team
> Red Hat
>
> --
>
> On Thu, Nov 30, 2023 at 11:53 AM Priscila Gutierres 
> wrote:
> >
> > When reading your email I thought about this video
> >
> > https://youtu.be/U4ALzqqUIS8?si=_D5seS8Nu_0fxYdO
> >
> >
> > Em qui., 30 de nov. de 2023 às 07:50, Michal Schorm 
> escreveu:
> >>
> >> I have this line in the SPECfile of 'mariadb' package:
> >>
> >> CFLAGS="$CFLAGS -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64
> -D_LARGEFILE_SOURCE"
> >>
> >> Git blame says this line will soon celebrate 20 years:
> >>
> https://src.fedoraproject.org/rpms/mysql/c/b3810a49b3125662999f444810efd0fd3223612b?branch=rawhide
> >>
> https://src.fedoraproject.org/rpms/mysql/c/45466935f338593601cf8653b582dce92752152f?branch=rawhide
> >>
> >> As I'm not very good at baking cakes, I'm researching the possibility
> >> of removing the line instead.
> >>
> >> I read through these macros explanations:
> >>
> https://www.gnu.org/software/libc/manual/html_node/Feature-Test-Macros.html
> >> however as I do not navigate well in the problematic, I haven't
> understood much.
> >>
> >> My question is primarily, whether during the last 20 years something
> >> happened, making the line obsolete (e.g. these macros are no longer
> >> relevant, or they were added to the default build flags, ... )
> >>
> >> Michal
> >>
> >> --
> >>
> >> Michal Schorm
> >> Software Engineer
> >> Core Services - Databases 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
> >
> > --
> > ___
> > 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
> --
> ___
> 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
>
--
___
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: dracut problems quick docs page requires help

[Ankur Sinha]

On Thu, Nov 30, 2023 09:23:58 +0100, David Tardon wrote:
> Hi,

Hi David,

> On Tue, 2023-11-21 at 06:39 +, Ankur Sinha wrote:
> > Hi folks,
> > 
> > We have this issue open on the quick-docs repo:
> > https://pagure.io/fedora-docs/quick-docs/issue/641
> > 
> > TLDR; the "debug-dracut-problems" quick doc seems to be out of date
> > and
> > needs review/updating.
> > 
> > https://docs.fedoraproject.org/en-US/quick-docs/debug-dracut-problems/
> 
> "It hasn't been changed in a while" does not equal "it's out of date".

Yeh, sure. This page just hasn't been reviewed since it was imported
from the wiki so we don't know if it's out of date or not:

https://pagure.io/fedora-docs/quick-docs/history/modules/ROOT/pages/debug-dracut-problems.adoc?identifier=main

> The kernel command line arguments for dracut that the page mentions
> still work the same way they worked 10 years ago. (With the exception
> of rd.udev.debug, which is ignored by systemd-based initrds; I've
> submitted a PR to fix that. And rd.udev.info is kinda pointless, as
> "info" is the default log level of systemd-udevd.)

Thanks. Could you please link to the PRs (or have they already been
merged)? I don't see them here:
https://pagure.io/fedora-docs/quick-docs/pull-requests

> 
> > nfortunately, I don't know enough about dracut to do this myself.
> > Would
> > someone that knows this stuff please consider reviewing (even
> > updating?)
> > the page so we know what to do with it next?
> 
> Are there _actual_ problems there, i.e., something that doesn't work
> anymore?

I honestly don't know. The page has just never been reviewed since it
was auto-imported from the wiki. If the information there is all
correct, I can mark it as "up to date".


-- 
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

Advent of Python 3.13

[Karolina Surma]

Hello fellow Fedorans,

As many of you know, there's an ongoing yearly effort of integrating a 
new Python version to Fedora taking place in Copr[0]. This time we aim 
to rebuild over 4000 packages and we couldn't possibly do it without you.


There have already been over 300 of bugzillas[1] created for packages 
that fail to build with Python 3.13.0 alphas - and, I need to add, 
almost 90 of them already fixed.


I'd love to thank everyone who jumped at the early bugzillas and helped 
drive the progress of the rebuild. We're grateful and appreciate your 
time and effort.


As there's the end of the year coming, various advents of... start to 
appear. I'd like to propose (only half-jokingly) another one: Advent of 
Python 3.13.


How would that work?
We publish the status of rebuild online: 
https://befeleme.github.io/fedora-python-rebuild-status/


Look at a package you're familiar with and has got a red or orange dot 
/ - meaning it fails to build.
On the Build failures page[2] you can find links to the package in the 
rebuild Copr and if there's associated bugzilla blocking the main 
PYTHON3.13 tracker, the link to the ticket.


What can you do?
- Fix the package (preferably upstream first)
- Let upstream know about the issue
- If you know the issue comes from Rawhide and is unrelated to Python 
3.13, find (or create) a F40FTBFS ticket and set it to block PYTHON3.13 
tracker too.
- If you've got no clue, ping me (ksurma) or mhroncok in the Matrix 
channel[3], we'll be happy to cooperate in digging into the issue
- If a package is gray ⚪, it means we don't have all its dependencies 
built yet, so we haven't tried to build it. Feel free to ignore it, but 
any help with unblocking the dependencies will be welcome.


Cheers,
Karolina


For curious minds - what's currently blocking the rebuild?

The 50 most commonly needed components are:
  135 python-contourpy
  133 python-matplotlib
  100 python-multidict
   98 python-yarl
   91 python-azure-common
   85 python-aiohttp
   85 python-greenlet
   82 python-pandas
   73 python-parso
   72 python-msrest
   72 python-zmq
   70 python-jedi
   69 python-asttokens
   64 python-qt5
   64 python-stack-data
   63 ipython
   61 python-jsonpointer
   61 python-pyperclip
   61 python-jupyter-core
   57 python-jeepney
   57 python-jupyter-client
   56 python-SecretStorage
   56 python-cliff
   54 python-keyring
   52 python-markdown-it-py
   52 python-sqlalchemy
   51 python-netaddr
   51 python-stestr
   48 python-anyio
   47 python-django
   45 python-mccabe
   45 python-ipykernel
   44 python-twisted
   43 python-nbformat
   41 python-oslotest
   39 h5py
   39 python-arrow
   39 python-oslo-utils
   38 python-nbclient
   36 python-nbconvert
   32 python-jsonpatch
   32 python-oslo-config
   32 python-flake8
   31 python-keystoneauth1
   30 python-numpydoc
   29 python-rich
   29 python-oslo-serialization
   28 python-prometheus_client
   28 python-vcrpy
   27 python-isoduration

The 20 most commonly last-blocking components are (= if they're built, 
this amount of packages will be unblocked):

   26 python-azure-common
   24 python-qt5
   19 python-twisted
   19 python-django
   16 audit
   12 future
   12 h5py
   10 python-pandas
8 python-cython0.29
7 glade
7 python-pydantic-core
7 python-numpydoc
7 python-furo
6 mercurial
6 python-flexmock
6 python-greenlet
5 gdb
5 python-pycurl
5 python-oslotest
5 python-anyio

The 20 most commonly last-blocking small combinations of components are:
   38 python-azure-common, python-msrest
   29 python-contourpy, python-matplotlib
   24 python-aiohttp, python-multidict, python-yarl
   11 python-flake8, python-mccabe
   11 python-greenlet, python-sqlalchemy
7 poetry, python-CacheControl, python-SecretStorage, 
python-installer, python-jeepney, python-keyring, python-rapidfuzz

7 pylint, python-astroid, python-mccabe
7 python-azure-common, python-msrest, python-msrestazure
7 ipython, python-asttokens, python-ipykernel, python-jedi, 
python-jupyter-client, python-jupyter-core, python-parso, 
python-stack-data, python-zmq

6 python-multidict, python-vcrpy, python-yarl
6 python-cliff, python-pyperclip, python-stestr
6 python-gevent, python-greenlet
5 python-markdown-it-py, python-rich
5 ipython, python-asttokens, python-jedi, python-parso, 
python-stack-data
5 fedora-messaging, python-crochet, python-pika, 
python-service-identity, python-twisted

4 gnuradio, python-pyopengl, python-pyqtgraph, python-qt5
3 python-markdown-it-py, python-mdit-py-plugins, python-myst-parser
3 python-aiohttp, python-multidict, python-pytest-aiohttp, python-yarl
3 python-contourpy, python-matplotlib, python-pytest-mpl
3 python-cliff, python-oslotest, python-pyperclip, python-stestr


[0] https://copr.fedorainfracloud.org/coprs/g/python/python3.13/
[1] 
https://bugzilla.redhat.com/buglist.cgi?cmdtype=runnamed_id=13377511=python313-related-open

[2] 

Re: troff noise when grepping man page?

[Dominik 'Rathann' Mierzejewski]

On Thursday, 30 November 2023 at 01:13, Chris Murphy wrote:
> $ man 5 btrfs | grep enospc
>enospc_debug, noenospc_debug
> troff::870: warning: cannot select font 'C'
> troff::888: warning: cannot select font 'C'
> troff::905: warning: cannot select font 'C'
> troff::924: warning: cannot select font 'C'
> troff::962: warning: cannot select font 'C'
> troff::977: warning: cannot select font 'C'
> troff::999: warning: cannot select font 'C'
> troff::1013: warning: cannot select font 'C'
> troff::1168: warning: cannot select font 'C'
> troff::1184: warning: cannot select font 'C'
> troff::1259: warning: cannot select font 'C'
> troff::1275: warning: cannot select font 'C'
> troff::1293: warning: cannot select font 'C'
> troff::1354: warning: cannot select font 'C'
> ...snip...
> 
> This seems new with Fedora 39. The root file system is newly installed
> not an upgrade, but the ~/ is positively ancient (possibly 5 years).
> Any ideas what's going on, how to get more information, and what
> component to file a bug against?

FWIW, I get different warnings on Fedora 38:
$ man 5 btrfs|grep enospc
   enospc_debug, noenospc_debug
grotty: ():16289: character above first line 
discarded
grotty: ():16293: character above first line 
discarded
grotty: ():16297: character above first line 
discarded
grotty: ():16301: character above first line 
discarded

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

Adding/creating wasi-libc++ into the wasi-libc package

[Jan Horak]

Hi,
I'm trying to make the sandboxing using the wasi available for the 
Firefox and for that I need the wasi-sdk [1] in the build root.


Currently there's wasi-libc [2] available which is fine and it almost 
contains all the headers and libraries needed by the wasi-sdk, but 
there's libc++ stuff missing, namely:

wasi-sysroot/include/c++/v1/*
wasi-sysroot/lib/wasm32-wasi/libc++.a
wasi-sysroot/lib/wasm32-wasi/libc++abi.a

The Arch distro is dealing with that by having extra packages:
wasi-libc++ and wasi-libc++abi:

https://archlinux.org/packages/extra/any/wasi-libc++/
https://archlinux.org/packages/extra/any/wasi-libc++abi/

They use the llvm sources to build the c++ wasi package [3].

Could you help me out with that?

[1] https://github.com/WebAssembly/wasi-sdk
[2] https://koji.fedoraproject.org/koji/buildinfo?buildID=2288202
[3] 
https://gitlab.archlinux.org/archlinux/packaging/packages/wasi-libcplusplus/-/blob/main/PKGBUILD?ref_type=heads


--
Jan Horak
Senior Software Engineer
Red Hat
fedo
--
___
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 rawhide compose report: 20231130.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-Rawhide-20231129.n.0
NEW: Fedora-Rawhide-20231130.n.0

= SUMMARY =
Added images:3
Dropped images:  3
Added packages:  13
Dropped packages:5
Upgraded packages:   79
Downgraded packages: 0

Size of added packages:  232.16 MiB
Size of dropped packages:759.30 KiB
Size of upgraded packages:   10.09 GiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   672.81 MiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =
Image: Silverblue dvd-ostree aarch64
Path: 
Silverblue/aarch64/iso/Fedora-Silverblue-ostree-aarch64-Rawhide-20231130.n.0.iso
Image: Silverblue dvd-ostree x86_64
Path: 
Silverblue/x86_64/iso/Fedora-Silverblue-ostree-x86_64-Rawhide-20231130.n.0.iso
Image: Sericea dvd-ostree x86_64
Path: Sericea/x86_64/iso/Fedora-Sericea-ostree-x86_64-Rawhide-20231130.n.0.iso

= DROPPED IMAGES =
Image: Kinoite dvd-ostree aarch64
Path: Kinoite/aarch64/iso/Fedora-Kinoite-ostree-aarch64-Rawhide-20231129.n.0.iso
Image: Kinoite dvd-ostree x86_64
Path: Kinoite/x86_64/iso/Fedora-Kinoite-ostree-x86_64-Rawhide-20231129.n.0.iso
Image: Silverblue dvd-ostree ppc64le
Path: 
Silverblue/ppc64le/iso/Fedora-Silverblue-ostree-ppc64le-Rawhide-20231129.n.0.iso

= ADDED PACKAGES =
Package: postgresql15-15.5-1.fc40
Summary: PostgreSQL client programs
RPMs:postgresql15 postgresql15-contrib postgresql15-docs 
postgresql15-plperl postgresql15-plpython3 postgresql15-pltcl 
postgresql15-private-devel postgresql15-private-libs postgresql15-server 
postgresql15-server-devel postgresql15-static postgresql15-test 
postgresql15-test-rpm-macros postgresql15-upgrade postgresql15-upgrade-devel
Size:111.60 MiB

Package: postgresql15-decoderbufs-1.9.7-3.Final.fc40
Summary: PostgreSQL Protocol Buffers logical decoder plugin
RPMs:postgresql15-decoderbufs
Size:96.97 KiB

Package: postgresql15-pg_repack-1.4.8-5.fc40
Summary: Reorganize tables in PostgreSQL databases without any locks
RPMs:postgresql15-pg_repack
Size:377.87 KiB

Package: postgresql15-pgaudit-1.7.0-6.fc40
Summary: PostgreSQL Audit Extension
RPMs:postgresql15-pgaudit
Size:116.96 KiB

Package: postgresql16-16.1-1.fc40
Summary: PostgreSQL client programs
RPMs:postgresql postgresql-contrib postgresql-docs postgresql-plperl 
postgresql-plpython3 postgresql-pltcl postgresql-private-devel 
postgresql-private-libs postgresql-server postgresql-server-devel 
postgresql-static postgresql-test postgresql-test-rpm-macros postgresql-upgrade 
postgresql-upgrade-devel
Size:118.73 MiB

Package: postgresql16-decoderbufs-1.9.7-3.Final.fc40
Summary: PostgreSQL Protocol Buffers logical decoder plugin
RPMs:postgresql16-decoderbufs
Size:94.38 KiB

Package: postgresql16-pg_repack-1.4.8-4.fc40
Summary: Reorganize tables in PostgreSQL databases without any locks
RPMs:postgresql16-pg_repack
Size:376.68 KiB

Package: postgresql16-pgaudit-16.0-1.fc40
Summary: PostgreSQL Audit Extension
RPMs:postgresql16-pgaudit
Size:117.86 KiB

Package: python-boltons-23.1.1-2.fc40
Summary: Functionality that should be in the standard library
RPMs:python3-boltons
Size:422.56 KiB

Package: rust-educe-0.4.23-1.fc40
Summary: Procedural macros to help you implement Rust-built-in traits quickly
RPMs:rust-educe+Clone-devel rust-educe+Copy-devel rust-educe+Debug-devel 
rust-educe+Default-devel rust-educe+Deref-devel rust-educe+DerefMut-devel 
rust-educe+Eq-devel rust-educe+Hash-devel rust-educe+Ord-devel 
rust-educe+PartialEq-devel rust-educe+PartialOrd-devel rust-educe+default-devel 
rust-educe-devel
Size:144.20 KiB

Package: rust-enum-ordinalize-3.1.15-1.fc40
Summary: Construct enum variant from its ordinal
RPMs:rust-enum-ordinalize+default-devel 
rust-enum-ordinalize+nightly-test-devel rust-enum-ordinalize-devel
Size:28.83 KiB

Package: rust-pmutil-0.6.1-1.fc40
Summary: Utils for proc-macro
RPMs:rust-pmutil+default-devel rust-pmutil-devel
Size:26.66 KiB

Package: rust-ruzstd-0.5.0-1.fc40
Summary: Decoder for the zstd compression format
RPMs:rust-ruzstd+default-devel rust-ruzstd+std-devel rust-ruzstd-devel
Size:74.52 KiB


= DROPPED PACKAGES =
Package: python-ratelimiter-1.2.0-12.post0.fc39
Summary: Python module providing rate limiting
RPMs:python3-ratelimiter
Size:19.22 KiB

Package: rust-pyo3-build-config0.15-0.15.2-3.fc39
Summary: Build configuration for the PyO3 ecosystem
RPMs:rust-pyo3-build-config0.15+abi3-devel 
rust-pyo3-build-config0.15+abi3-py310-devel 
rust-pyo3-build-config0.15+abi3-py36-devel 
rust-pyo3-build-config0.15+abi3-py37-devel 
rust-pyo3-build-config0.15+abi3-py38-devel 
rust-pyo3-build-config0.15+abi3-py39-devel 
rust-pyo3-build-config0.15+default-devel 
rust-pyo3-build-config0.15+resolve-config-devel rust-pyo3-build-config0.15-devel
Size:89.42 KiB

Package: rust-pyo3-macros-backend0.15-0.15.2-3.fc39
Summary: Code generation for PyO3 package
RPMs:rust-pyo3-macros-backend0.15+default-devel 
rust

[Fedocal] Reminder meeting : ELN SIG

[sgallagh]

Dear all,

You are kindly invited to the meeting:
   ELN SIG on 2023-12-01 from 12:00:00 to 13:00:00 US/Eastern
   At fedora-meet...@irc.libera.chat

The meeting will be about:



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

--
___
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

[Bug 2251622] CVE-2023-47038 perl: Write past buffer end via illegal user-defined Unicode property [fedora-all]

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2251622

Fedora Update System  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED



--- Comment #2 from Fedora Update System  ---
FEDORA-2023-9ef8a60a05 has been submitted as an update to Fedora 38.
https://bodhi.fedoraproject.org/updates/FEDORA-2023-9ef8a60a05


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2251622

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202251622%23c2
--
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Bug 2251622] CVE-2023-47038 perl: Write past buffer end via illegal user-defined Unicode property [fedora-all]

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2251622



--- Comment #3 from Fedora Update System  ---
FEDORA-2023-c67f4dbf13 has been submitted as an update to Fedora 39.
https://bodhi.fedoraproject.org/updates/FEDORA-2023-c67f4dbf13


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2251622

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202251622%23c3
--
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-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/perl-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Ancient compilation flags in my pkg - still needed ?

[Michal Schorm]

On Thu, Nov 30, 2023 at 11:53 AM Priscila Gutierres  wrote:
> When reading your email I thought about this video
> https://youtu.be/U4ALzqqUIS8?si=_D5seS8Nu_0fxYdO

Yeah, on point :)

But as long as I get commit messages explaining *what* has been done
(which is obvious from the code), instead of *why* it was done, I'm
more of an archeologist, than a software engineer.
If people would write *useful* commit messages, I wouldn't need to ask
such questions.

Michal

--

Michal Schorm
Software Engineer
Core Services - Databases Team
Red Hat

--

On Thu, Nov 30, 2023 at 11:53 AM Priscila Gutierres  wrote:
>
> When reading your email I thought about this video
>
> https://youtu.be/U4ALzqqUIS8?si=_D5seS8Nu_0fxYdO
>
>
> Em qui., 30 de nov. de 2023 às 07:50, Michal Schorm  
> escreveu:
>>
>> I have this line in the SPECfile of 'mariadb' package:
>>
>> CFLAGS="$CFLAGS -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE"
>>
>> Git blame says this line will soon celebrate 20 years:
>> https://src.fedoraproject.org/rpms/mysql/c/b3810a49b3125662999f444810efd0fd3223612b?branch=rawhide
>> https://src.fedoraproject.org/rpms/mysql/c/45466935f338593601cf8653b582dce92752152f?branch=rawhide
>>
>> As I'm not very good at baking cakes, I'm researching the possibility
>> of removing the line instead.
>>
>> I read through these macros explanations:
>>   https://www.gnu.org/software/libc/manual/html_node/Feature-Test-Macros.html
>> however as I do not navigate well in the problematic, I haven't understood 
>> much.
>>
>> My question is primarily, whether during the last 20 years something
>> happened, making the line obsolete (e.g. these macros are no longer
>> relevant, or they were added to the default build flags, ... )
>>
>> Michal
>>
>> --
>>
>> Michal Schorm
>> Software Engineer
>> Core Services - Databases 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
>
> --
> ___
> 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
--
___
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: Ancient compilation flags in my pkg - still needed ?

[Priscila Gutierres]

When reading your email I thought about this video

https://youtu.be/U4ALzqqUIS8?si=_D5seS8Nu_0fxYdO


Em qui., 30 de nov. de 2023 às 07:50, Michal Schorm 
escreveu:

> I have this line in the SPECfile of 'mariadb' package:
>
> CFLAGS="$CFLAGS -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE"
>
> Git blame says this line will soon celebrate 20 years:
>
> https://src.fedoraproject.org/rpms/mysql/c/b3810a49b3125662999f444810efd0fd3223612b?branch=rawhide
>
> https://src.fedoraproject.org/rpms/mysql/c/45466935f338593601cf8653b582dce92752152f?branch=rawhide
>
> As I'm not very good at baking cakes, I'm researching the possibility
> of removing the line instead.
>
> I read through these macros explanations:
>
> https://www.gnu.org/software/libc/manual/html_node/Feature-Test-Macros.html
> however as I do not navigate well in the problematic, I haven't understood
> much.
>
> My question is primarily, whether during the last 20 years something
> happened, making the line obsolete (e.g. these macros are no longer
> relevant, or they were added to the default build flags, ... )
>
> Michal
>
> --
>
> Michal Schorm
> Software Engineer
> Core Services - Databases 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
>
--
___
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

Ancient compilation flags in my pkg - still needed ?

[Michal Schorm]

I have this line in the SPECfile of 'mariadb' package:

CFLAGS="$CFLAGS -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE"

Git blame says this line will soon celebrate 20 years:
https://src.fedoraproject.org/rpms/mysql/c/b3810a49b3125662999f444810efd0fd3223612b?branch=rawhide
https://src.fedoraproject.org/rpms/mysql/c/45466935f338593601cf8653b582dce92752152f?branch=rawhide

As I'm not very good at baking cakes, I'm researching the possibility
of removing the line instead.

I read through these macros explanations:
  https://www.gnu.org/software/libc/manual/html_node/Feature-Test-Macros.html
however as I do not navigate well in the problematic, I haven't understood much.

My question is primarily, whether during the last 20 years something
happened, making the line obsolete (e.g. these macros are no longer
relevant, or they were added to the default build flags, ... )

Michal

--

Michal Schorm
Software Engineer
Core Services - Databases 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

Re: troff noise when grepping man page?

[Michael J Gruber]

Am Do., 30. Nov. 2023 um 01:14 Uhr schrieb Chris Murphy <
li...@colorremedies.com>:

> $ man 5 btrfs | grep enospc
>enospc_debug, noenospc_debug
> troff::870: warning: cannot select font 'C'
> troff::888: warning: cannot select font 'C'
> troff::905: warning: cannot select font 'C'
> troff::924: warning: cannot select font 'C'
> troff::962: warning: cannot select font 'C'
> troff::977: warning: cannot select font 'C'
> troff::999: warning: cannot select font 'C'
> troff::1013: warning: cannot select font 'C'
> troff::1168: warning: cannot select font 'C'
> troff::1184: warning: cannot select font 'C'
> troff::1259: warning: cannot select font 'C'
> troff::1275: warning: cannot select font 'C'
> troff::1293: warning: cannot select font 'C'
> troff::1354: warning: cannot select font 'C'
> ...snip...
>
> This seems new with Fedora 39. The root file system is newly installed not
> an upgrade, but the ~/ is positively ancient (possibly 5 years). Any ideas
> what's going on, how to get more information, and what component to file a
> bug against?
>
>
> That man page contains `.ft C` sequences to select a font, but that should
probably be `.ft CR` (for constant width Roman) or any other of the C
variants, but not just `C`. Either roff sequences changed ( I don't think
so) or doc generation. More likely, we get warnings on stderr now here we
used to ignore them in /dev/null ...

A quick scan shows indeed many man pages with problems or warnings.

Michael
--
___
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: Packaging guidelines - dynamic allocation of users and groups

[Zbigniew Jędrzejewski-Szmek]

On Wed, Nov 29, 2023 at 07:38:25PM -0500, Neal Gompa wrote:
> On Wed, Nov 29, 2023 at 7:26 PM Michal Schorm  wrote:
> >
> > On Thu, Nov 30, 2023 at 12:54 AM Zbigniew Jędrzejewski-Szmek
> >  wrote:
> > > Yeah, there are no guidelines for this case because it didn't really
> > > come up before. I think this case can be used to figure out the best
> > > way to do this and then the guidelines can be informed by the solution.
> >
> > Okay. I don't mind being a pioneer.
> > I asked to avoid reinventing the wheel.
> >
> 
> I think this is actually going to be pretty simple: just have a
> package "system-user-mysql" that just installs the file and be done
> with it.
> 
> You can then have the database packages "Requires(pre): (user(mysql) and
> group(mysql))" and things should just work.

That is exactly what the first message in the thread was proposing ;)

Zbyszek
--
___
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

[Test-Announce] Fedora 40 Rawhide 20231130.n.0 nightly compose nominated for testing

[rawhide]

Announcing the creation of a new nightly release validation test event
for Fedora 40 Rawhide 20231130.n.0. Please help run some tests for this
nightly compose if you have time. For more information on nightly
release validation testing, see:
https://fedoraproject.org/wiki/QA:Release_validation_test_plan

Notable package version changes:
anaconda - 20231127.n.0: anaconda-40.10-1.fc40.src, 20231130.n.0: 
anaconda-40.11-1.fc40.src
pykickstart - 20231127.n.0: pykickstart-3.50-1.fc40.src, 20231130.n.0: 
pykickstart-3.51-1.fc40.src

Test coverage information for the current release can be seen at:
https://openqa.fedoraproject.org/testcase_stats/40

You can see all results, find testing instructions and image download
locations, and enter results on the Summary page:

https://fedoraproject.org/wiki/Test_Results:Fedora_40_Rawhide_20231130.n.0_Summary

The individual test result pages are:

https://fedoraproject.org/wiki/Test_Results:Fedora_40_Rawhide_20231130.n.0_Installation
https://fedoraproject.org/wiki/Test_Results:Fedora_40_Rawhide_20231130.n.0_Base
https://fedoraproject.org/wiki/Test_Results:Fedora_40_Rawhide_20231130.n.0_Server
https://fedoraproject.org/wiki/Test_Results:Fedora_40_Rawhide_20231130.n.0_Cloud
https://fedoraproject.org/wiki/Test_Results:Fedora_40_Rawhide_20231130.n.0_Desktop
https://fedoraproject.org/wiki/Test_Results:Fedora_40_Rawhide_20231130.n.0_Security_Lab

Thank you for testing!
-- 
Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer
--
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-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/test-annou...@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue
--
___
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: dracut problems quick docs page requires help

[David Tardon]

Hi,

On Tue, 2023-11-21 at 06:39 +, Ankur Sinha wrote:
> Hi folks,
> 
> We have this issue open on the quick-docs repo:
> https://pagure.io/fedora-docs/quick-docs/issue/641
> 
> TLDR; the "debug-dracut-problems" quick doc seems to be out of date
> and
> needs review/updating.
> 
> https://docs.fedoraproject.org/en-US/quick-docs/debug-dracut-problems/

"It hasn't been changed in a while" does not equal "it's out of date".
The kernel command line arguments for dracut that the page mentions
still work the same way they worked 10 years ago. (With the exception
of rd.udev.debug, which is ignored by systemd-based initrds; I've
submitted a PR to fix that. And rd.udev.info is kinda pointless, as
"info" is the default log level of systemd-udevd.)

> nfortunately, I don't know enough about dracut to do this myself.
> Would
> someone that knows this stuff please consider reviewing (even
> updating?)
> the page so we know what to do with it next?

Are there _actual_ problems there, i.e., something that doesn't work
anymore?

D.
--
___
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