Fedora rawhide compose report: 20231128.n.2 changes

[Fedora Rawhide Report]

OLD: Fedora-Rawhide-20231127.n.0
NEW: Fedora-Rawhide-20231128.n.2

= SUMMARY =
Added images:5
Dropped images:  0
Added packages:  5
Dropped packages:2
Upgraded packages:   151
Downgraded packages: 0

Size of added packages:  6.11 MiB
Size of dropped packages:2.09 MiB
Size of upgraded packages:   5.20 GiB
Size of downgraded packages: 0 B

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

= ADDED IMAGES =
Image: Silverblue dvd-ostree x86_64
Path: 
Silverblue/x86_64/iso/Fedora-Silverblue-ostree-x86_64-Rawhide-20231128.n.2.iso
Image: Silverblue dvd-ostree ppc64le
Path: 
Silverblue/ppc64le/iso/Fedora-Silverblue-ostree-ppc64le-Rawhide-20231128.n.2.iso
Image: Kinoite dvd-ostree aarch64
Path: Kinoite/aarch64/iso/Fedora-Kinoite-ostree-aarch64-Rawhide-20231128.n.2.iso
Image: Kinoite dvd-ostree x86_64
Path: Kinoite/x86_64/iso/Fedora-Kinoite-ostree-x86_64-Rawhide-20231128.n.2.iso
Image: Workstation live aarch64
Path: 
Workstation/aarch64/iso/Fedora-Workstation-Live-aarch64-Rawhide-20231128.n.2.iso

= DROPPED IMAGES =

= ADDED PACKAGES =
Package: anaconda-webui-1-1.fc40
Summary: Anaconda installer Web interface
RPMs:anaconda-webui
Size:1.35 MiB

Package: elementary-camera-6.2.2-1.fc40
Summary: Camera app designed for elementary
RPMs:elementary-camera
Size:498.72 KiB

Package: elementary-code-7.1.0-1.fc40
Summary: Code editor from elementary
RPMs:elementary-code elementary-code-devel
Size:3.72 MiB

Package: kdsingleapplication-1.0.0-2.fc40
Summary: KDAB's helper class for single-instance policy applications
RPMs:kdsingleapplication-qt5 kdsingleapplication-qt5-devel 
kdsingleapplication-qt6 kdsingleapplication-qt6-devel
Size:436.40 KiB

Package: rust-euclid-0.22.9-1.fc40
Summary: Geometry primitives
RPMs:rust-euclid+arbitrary-devel rust-euclid+bytemuck-devel 
rust-euclid+default-devel rust-euclid+libm-devel rust-euclid+mint-devel 
rust-euclid+serde-devel rust-euclid+std-devel rust-euclid+unstable-devel 
rust-euclid-devel
Size:131.82 KiB


= DROPPED PACKAGES =
Package: anaconda-user-help-26.2-6.fc39
Summary: Content for the Anaconda built-in help system
RPMs:anaconda-user-help
Size:307.22 KiB

Package: wlroots0.14-0.14.1-5.fc39
Summary: A modular Wayland compositor library
RPMs:wlroots0.14 wlroots0.14-devel
Size:1.79 MiB


= UPGRADED PACKAGES =
Package:  DevIL-1.7.8-43.fc40
Old package:  DevIL-1.7.8-42.fc39
Summary:  A cross-platform image library
RPMs: DevIL DevIL-ILUT DevIL-ILUT-devel DevIL-devel
Size: 1.76 MiB
Size change:  -835 B
Changelog:
  * Tue Nov 28 2023 Orion Poplawski  - 1.7.8-43
  - Rebuild for jasper 4.1


Package:  GraphicsMagick-1.3.40-4.fc40
Old package:  GraphicsMagick-1.3.40-3.fc39
Summary:  An ImageMagick fork, offering faster image generation and better 
quality
RPMs: GraphicsMagick GraphicsMagick-c++ GraphicsMagick-c++-devel 
GraphicsMagick-devel GraphicsMagick-doc GraphicsMagick-perl
Size: 10.93 MiB
Size change:  -8.86 KiB
Changelog:
  * Tue Nov 28 2023 Orion Poplawski  - 1.3.40-4
  - Rebuild for jasper 4.1


Package:  LibRaw-0.21.1-7.fc40
Old package:  LibRaw-0.21.1-6.fc40
Summary:  Library for reading RAW files obtained from digital photo cameras
RPMs: LibRaw LibRaw-devel LibRaw-samples LibRaw-static
Size: 4.96 MiB
Size change:  3.10 KiB
Changelog:
  * Tue Nov 28 2023 Orion Poplawski  - 0.21.1-7
  - Rebuild for jasper 4.1


Package:  OpenSceneGraph-3.6.5-21.fc40
Old package:  OpenSceneGraph-3.6.5-19.fc40
Summary:  High performance real-time graphics toolkit
RPMs: OpenSceneGraph OpenSceneGraph-Collada OpenSceneGraph-OpenEXR 
OpenSceneGraph-devel OpenSceneGraph-examples OpenSceneGraph-examples-SDL 
OpenSceneGraph-examples-fltk OpenSceneGraph-examples-gtk OpenSceneGraph-gdal 
OpenSceneGraph-gstreamer OpenSceneGraph-libs OpenThreads OpenThreads-devel 
mingw32-OpenSceneGraph mingw32-OpenSceneGraph-tools mingw64-OpenSceneGraph 
mingw64-OpenSceneGraph-tools
Size: 214.11 MiB
Size change:  -45.48 KiB
Changelog:
  * Mon Nov 20 2023 Richard Shaw  - 3.6.5-20
  - Rebuild for Coin4.

  * Tue Nov 28 2023 Orion Poplawski  - 3.6.5-21
  - Rebuild for jasper 4.1


Package:  PDAL-2.6.1-1.fc40
Old package:  PDAL-2.6.0-5.fc40
Summary:  Point Data Abstraction Library
RPMs: PDAL PDAL-devel PDAL-doc PDAL-libs
Size: 45.01 MiB
Size change:  13.12 KiB
Changelog:
  * Tue Nov 28 2023 Sandro Mani  - 2.6.1-1
  - Update to 2.6.1


Package:  RediSearch-1.2.2-11.fc40
Old package:  RediSearch-1.2.2-7.fc37
Summary:  Full-text search over Redis
RPMs: RediSearch
Size: 1.28 MiB
Size change:  3.05 KiB
Changelog:
  * Wed Jul 20 2022 Fedora Release Engineering  - 
1.2.2-8
  - Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild

  * Wed Jan 18 2023 Fedora Release Engineering  - 
1.2.2-9
  - Rebuilt for https

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

[updates]

The following Fedora EPEL 8 Security updates need testing:
 Age  URL
   6  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-330054b0a8   
dbus-broker-28-4.el8


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

clazy-1.11-10.el8
libarrow-8.0.1-2.el8
libkdumpfile-0.5.4-1.el8
liborc-1.7.10-1.el8
php-Smarty-3.1.48-2.el8
php-smarty-gettext-1.7.0-2.el8
scorep-6.0-20.el8
syncthing-1.26.1-1.el8

Details about builds:



 clazy-1.11-10.el8 (FEDORA-EPEL-2023-13f7894087)
 Qt oriented code checker based on clang framework

Update Information:

Fix build with GCC 8 for EPEL 8

ChangeLog:

* Tue Nov 28 2023 Thomas Zimmermann  - 
1.11-10
- Fix build with GCC 8 for EPEL 8
* Wed Sep  6 2023 Jan Grulich  - 1.11-9
- Rebuild (clang-17)
* Wed Jul 19 2023 Fedora Release Engineering  - 1.11-8
- Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild
* Thu Apr 13 2023 Jan Grulich  - 1.11-7
- Rebuild against fixed clang
* Thu Apr 13 2023 Jan Grulich  - 1.11-6
- Rebuild (clang-16)
* Tue Apr 11 2023 Jan Grulich  - 1.11-5
- Rebuild (clang-16)
* Mon Feb 20 2023 Neal Gompa  - 1.11-4
- Explicitly Require: specific major version of Clang
* Tue Jan 31 2023 Jan Grulich  - 1.11-3
- migrated to SPDX license
* Wed Jan 18 2023 Fedora Release Engineering  - 1.11-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_38_Mass_Rebuild
* Wed Jan 18 2023 Jan Grulich  - 1.11-1
- 1.11
* Wed Jul 20 2022 Fedora Release Engineering  - 1.9-4
- Rebuilt for https://fedoraproject.org/wiki/Fedora_37_Mass_Rebuild
* Wed Jan 19 2022 Fedora Release Engineering  - 1.9-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_36_Mass_Rebuild
* Wed Jul 21 2021 Fedora Release Engineering  - 1.9-2
- Rebuilt for https://fedoraproject.org/wiki/Fedora_35_Mass_Rebuild
* Sat May  1 2021 FeRD (Frank Dana)  - 1.9-1
- New upstream release 1.9
- Build against LLVM-12 for clang-12 in Fedora 34+
- Drop upstreamed patches
* Tue Jan 26 2021 Fedora Release Engineering  - 1.7-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_34_Mass_Rebuild
* Fri Jan 22 2021 Tom Stellard  - 1.7-2
- Rebuild for clang-11.1.0
* Mon Oct 26 2020 Jan Grulich  - 1.6-7
- Update 1.7
* Sat Aug  1 2020 Fedora Release Engineering  - 1.6-6
- Second attempt - Rebuilt for
  https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild
* Mon Jul 27 2020 Fedora Release Engineering  - 1.6-5
- Rebuilt for https://fedoraproject.org/wiki/Fedora_33_Mass_Rebuild
* Thu Jul  9 2020 Jan Grulich  - 1.6-4
- Fix build against LLVM 10
* Tue Jan 28 2020 Fedora Release Engineering  - 1.6-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_32_Mass_Rebuild
* Fri Dec 13 2019 Tom Stellard  - 1.6-2
- Link against libclang-cpp.so
- 
https://fedoraproject.org/wiki/Changes/Stop-Shipping-Individual-Component-Libraries-In-clang-lib-Package
* Wed Oct 30 2019 Jan Grulich  - 1.6-1
- 1.6
* Wed Jul 24 2019 Fedora Release Engineering  - 1.5-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild
* Tue Apr 30 2019 Tom Stellard  - 1.5-2
- Rebuild for clang-8.0.0
* Sun Feb  3 2019 Jan Grulich  - 1.5-1
- Update to 1.5
* Thu Jan 31 2019 Fedora Release Engineering  - 1.4-3
- Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild
* Mon Dec  3 2018 Jan Grulich  - 1.4-2
- Require clang
* Tue Oct  2 2018 Jan Grulich  - 1.4-1
- Initial version

References:

  [ 1 ] Bug #2209263 - [EPEL8] Please branch and build clazy in epel8
https://bugzilla.redhat.com/show_bug.cgi?id=2209263




 libarrow-8.0.1-2.el8 (FEDORA-EPEL-2023-c612dc6b0d)
 A toolbox for accelerated data interchange and in-memory processing

Update Information:

Apache Arrow 8.0.1 rebuilt for liborc-1.7.10

ChangeLog:

* Tue Nov 28 2023 Kaleb S. KEITHLEY  - 8.0.1-2
- Apache Arrow 8.0.1, rebuild with liborc-1.7.10




 libkdumpfile-0.5.4-1.el8 (FEDORA-EPEL-2023-114e550b97)
 Kernel coredump file access

Update Information:

- Full support for 64-bit RISC-V. - Improved error messages.

ChangeLog:

* Tue Nov 28 2023 Michel Lind  - 0.5.4-1
- Update to 0.5.4

[Bug 2250650] perl-Module-CoreList-5.20231120 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-Module-CoreList-5.2023 |perl-Module-CoreList-5.2023
   |1120-1.fc40 |1120-1.fc40
   |perl-Module-CoreList-5.2023 |perl-Module-CoreList-5.2023
   |1120-1.fc38 |1120-1.fc38
   |perl-Module-CoreList-5.2023 |perl-Module-CoreList-5.2023
   |1120-1.fc39 |1120-1.fc39
   ||perl-Module-CoreList-5.2023
   ||1120-1.fc37



--- Comment #11 from Fedora Update System  ---
FEDORA-2023-00d8d2586b has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202250650%23c11
--
___
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 2250655] perl-CPAN-Perl-Releases-5.20231120 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-CPAN-Perl-Releases-5.2 |perl-CPAN-Perl-Releases-5.2
   |0231120-1.fc40  |0231120-1.fc40
   |perl-CPAN-Perl-Releases-5.2 |perl-CPAN-Perl-Releases-5.2
   |0231120-1.fc38  |0231120-1.fc38
   |perl-CPAN-Perl-Releases-5.2 |perl-CPAN-Perl-Releases-5.2
   |0231120-1.fc39  |0231120-1.fc39
   ||perl-CPAN-Perl-Releases-5.2
   ||0231120-1.fc37



--- Comment #11 from Fedora Update System  ---
FEDORA-2023-74023c1af8 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202250655%23c11
--
___
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 2250650] perl-Module-CoreList-5.20231120 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-Module-CoreList-5.2023 |perl-Module-CoreList-5.2023
   |1120-1.fc40 |1120-1.fc40
   |perl-Module-CoreList-5.2023 |perl-Module-CoreList-5.2023
   |1120-1.fc38 |1120-1.fc38
   ||perl-Module-CoreList-5.2023
   ||1120-1.fc39



--- Comment #10 from Fedora Update System  ---
FEDORA-2023-2ad7c686d7 has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202250650%23c10
--
___
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 2250655] perl-CPAN-Perl-Releases-5.20231120 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-CPAN-Perl-Releases-5.2 |perl-CPAN-Perl-Releases-5.2
   |0231120-1.fc40  |0231120-1.fc40
   |perl-CPAN-Perl-Releases-5.2 |perl-CPAN-Perl-Releases-5.2
   |0231120-1.fc38  |0231120-1.fc38
   ||perl-CPAN-Perl-Releases-5.2
   ||0231120-1.fc39



--- Comment #10 from Fedora Update System  ---
FEDORA-2023-0b847ca121 has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202250655%23c10
--
___
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 2250655] perl-CPAN-Perl-Releases-5.20231120 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-CPAN-Perl-Releases-5.2 |perl-CPAN-Perl-Releases-5.2
   |0231120-1.fc40  |0231120-1.fc40
   ||perl-CPAN-Perl-Releases-5.2
   ||0231120-1.fc38



--- Comment #9 from Fedora Update System  ---
FEDORA-2023-9b3386fd9b has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202250655%23c9
--
___
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 2250650] perl-Module-CoreList-5.20231120 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-Module-CoreList-5.2023 |perl-Module-CoreList-5.2023
   |1120-1.fc40 |1120-1.fc40
   ||perl-Module-CoreList-5.2023
   ||1120-1.fc38



--- Comment #9 from Fedora Update System  ---
FEDORA-2023-0021855787 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202250650%23c9
--
___
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 2252003] New: perl-Unix-Mknod-0.05 is available

[bugzilla]

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

Bug ID: 2252003
   Summary: perl-Unix-Mknod-0.05 is available
   Product: Fedora
   Version: rawhide
Status: NEW
 Component: perl-Unix-Mknod
  Keywords: FutureFeature, Triaged
  Assignee: jples...@redhat.com
  Reporter: upstream-release-monitor...@fedoraproject.org
QA Contact: extras...@fedoraproject.org
CC: jples...@redhat.com,
perl-devel@lists.fedoraproject.org
  Target Milestone: ---
Classification: Fedora



Releases retrieved: 0.05
Upstream release that is considered latest: 0.05
Current version/release in rawhide: 0.04-27.fc39
URL: http://search.cpan.org/dist/Unix-Mknod/

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


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


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202252003%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: FESCo Nominations are now Open!

[Aoife Moloney]

Hi folks,

There is still time to nominate yourself or someone else (with their knowledge 
and
approval) for FESCo 
https://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations

Nominations will close tomorrow night so don't delay! :)


Kind regards,
Aoife
--
___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel-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: FESCo Nominations are now Open!

[Aoife Moloney]

Hi folks,

There is still time to nominate yourself or someone else (with their knowledge 
and
approval) for FESCo 
https://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations

Nominations will close tomorrow night so don't delay! :)


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

Re: Fedora Mindshare Committee election nominations are open!

[Aoife Moloney]

Hi folks,

There is still time to nominate yourself or someone else (with their knowledge 
and approval) for the Fedora Mindshare Committee 
https://fedoraproject.org/wiki/Mindshare/Nominations

Nominations will close tomorrow night so don't delay! :)


Kind regards,
Aoife
--
___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel-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: Fedora Council election nominations are open!

[Aoife Moloney]

Hi folks,

There is still time to nominate yourself or someone else (with their knowledge 
and approval) for the Fedora Council 
https://fedoraproject.org/wiki/Council/Nominations

Nominations will close tomorrow night so dont delay! :)


Kind regards,
Aoife
--
___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel-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

Fedora 37 End Of Life in one week

[Tomas Hrcka]

Hello all,

Fedora Linux 37 will go end of life for updates and support on 2023-12-05.
No more updates of any kind, including security updates or security
announcements, will be available for Fedora Linux 37 after the said
date. All the updates of Fedora Linux 37 being pushed to stable will also
be stopped.

Please ensure your builds will land in stable[3] updates in Bodhi before
the EOL date.

This email template is also in https://pagure.io/releng if you wish to
propose improvements or changes to it.

Regards,
Fedora Release Engineering

[1]
https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule
[2]https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades
[3]https://bodhi.fedoraproject.org/updates/?releases=F37=stable

-- 
Tomas Hrcka
fas: humaton
libera.CHAT: jednorozec
@humaton:fedora.im
--
___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel-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: Fedora Mindshare Committee election nominations are open!

[Aoife Moloney]

Hi folks,

There is still time to nominate yourself or someone else (with their knowledge 
and approval) for the Fedora Mindshare Committee 
https://fedoraproject.org/wiki/Mindshare/Nominations

Nominations will close tomorrow night so don't delay! :)


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

Re: Fedora Council election nominations are open!

[Aoife Moloney]

Hi folks,

There is still time to nominate yourself or someone else (with their knowledge 
and approval) for the Fedora Council 
https://fedoraproject.org/wiki/Council/Nominations

Nominations will close tomorrow night so dont delay! :)


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

Fedora 37 End Of Life in one week

[Tomas Hrcka]

Hello all,

Fedora Linux 37 will go end of life for updates and support on 2023-12-05.
No more updates of any kind, including security updates or security
announcements, will be available for Fedora Linux 37 after the said
date. All the updates of Fedora Linux 37 being pushed to stable will also
be stopped.

Please ensure your builds will land in stable[3] updates in Bodhi before
the EOL date.

This email template is also in https://pagure.io/releng if you wish to
propose improvements or changes to it.

Regards,
Fedora Release Engineering

[1]
https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#Maintenance_Schedule
[2]https://fedoraproject.org/wiki/Upgrading?rd=DistributionUpgrades
[3]https://bodhi.fedoraproject.org/updates/?releases=F37=stable

-- 
Tomas Hrcka
fas: humaton
libera.CHAT: jednorozec
@humaton:fedora.im
--
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-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/devel-announce@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: libxml2 2.12.0 (and 2.12.1) in rawhide, with some API breaks

[Dodji Seketeli]

Hello,

Petr Pisar  a écrit:

> V Tue, Nov 28, 2023 at 12:24:45PM +0100, Dodji Seketeli napsal(a):

[...]

>> For what it's worth, the ABI compatibility verifier caught this change
>> between libxml2.so.2.11.5 and libxml2.so.2.12.0 and categorized it as
>> being "ABI compatible" (i.e, not incompatible/breaking) at:
>> https://artifacts.dev.testing-farm.io/b7d369b0-f288-4564-a331-48492c20bf8c/:
>> 
>>   [C] 'function int xmlCopyError(xmlErrorPtr, xmlErrorPtr)' at error.c:985:1 
>> has some indirect sub-type changes:
>> parameter 1 of type 'typedef xmlErrorPtr' changed:
>>   entity changed from 'typedef xmlErrorPtr' to compatible type 'const 
>> xmlError*'
>> in pointed to type 'struct _xmlError':
>>   entity changed from 'struct _xmlError' to 'const _xmlError'
>>   type size hasn't changed
>> 
>> I guess the important bit here is "entity changed from 'struct _xmlError' to 
>> 'const _xmlError'".
>> 
>> So, yes, this is not an ABI incompatible change.
>>
> Well abidiff for createrepo_c
> 
> complains:
>
>   underlying type 'xmlParserCtxt*' changed:
> in pointed to type 'typedef xmlParserCtxt' at tree.h:40:1:
>   underlying type 'struct _xmlParserCtxt' at parser.h:181:1 
> changed:
> type size changed from 3840 to 3968 (in bits)
> 4 data member insertions:
>   'unsigned int maxAmpl', at offset 3840 (in bits) at 
> parser.h:323:1
>   'xmlParserNsData* nsdb', at offset 3872 (in bits) at 
> parser.h:325:1
>   'unsigned int attrHashMax', at offset 3904 (in bits) at 
> parser.h:326:1
>   'xmlAttrHashBucket* attrHash', at offset 3936 (in bits) at 
> parser.h:327:1
> 1 data member changes (5 filtered):
>   type of 'int* attallocs' changed:
> in pointed to type 'int':
>   type name changed from 'int' to 'unsigned int'
>   type size hasn't changed

That is correct.  That change to the layout of struct _xmlParserCtxt is
an ABI change.

However that change is only "reachable" (from an exported libxml2
function) through a pointer, abidiff categorized the change as "needing
review".  Hence the "VERIFY" categorization of the rpminspect.

In other words determining if this is an /incompatible/ ABI change
(a.k.a ABI break) or not ought to be discussed by human beings.

> While most (all?) libxml2 functions pass a pointer to xmlParserCtxt, a
> definition of the xmlParserCtxt structure is open to anybody in
> .

Correct, again.

However, ABI matters are often a about conventions that are specific to
each project.

In the case of libxml2, there is a (probably unwritten) convention which
says that data structures that are essentially internal to the library
have to be let alone.  Client code should not access those and should
only pass them to libxml2 functions through pointers, even though these
data structures are defined in /usr/include/libxml2/libxml/*.h.

> That means an application built against old libxml2 can construct a
> different structure than libxml2 expects.

If the application does that, then it violates the ABI convention
(softly) set by libxml2.

Maybe we should send patches to the libxml2 hackers to put that
convention into writing and help better set expectations in the future.

We can also teach abidiff about these essentially private data
structures of libxml2 so that it doesn't complain whenever they are
modified in the feature.  This would be done by providing a
libxml2-specific ABI change suppression specification[1].

> That is called an ABI breakage.

I guess I would argue (as I started above) that these things are not
that simple, unfortunately.

[...]

[1]: 
https://sourceware.org/libabigail/manual/libabigail-concepts.html#suppression-specifications

Cheers,

-- 
Dodji
--
___
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 2251701] perl-Time-Out-0.24 is available

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

 Status|MODIFIED|CLOSED
 Resolution|--- |RAWHIDE
Last Closed||2023-11-28 17:03:32




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2251701
--
___
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] Proposed incompatible security update (again) for llhttp in EPEL9

[Ben Beasley]

This email proposes upgrading the llhttp package in EPEL9 from 8.1.1 to 
9.1.3, which would break the ABI and bump the SONAME version, under the 
EPEL Incompatible Upgrades Policy[1].


The llhttp package is a C library (transpiled from TypeScript) that 
provides the low-level HTTP support for NodeJS and for python-aiohttp. 
Currently, only python-aiohttp depends on the llhttp package in EPEL9.


Versions of python-aiohttp prior to 3.8.6[2] are affected by 
CVE-2023-47627[3][4], an HTTP request/response smuggling vulnerability 
rated 5.3 in CVSS v3 and rated Moderate by Red Hat. This was reported as 
RHBZ#2249825[5]. Since the flaw is only in the pure-Python parser, and 
we compile the llhttp-based parser, this affects only code using the 
AIOHTTP_NO_EXTENSIONS environment variable. Updating aiohttp from 3.8.5 
to 3.8.6 to fix that still requires updating llhttp from 8.x to 9.x. 
Additionally, according to the release notes this includes an 
llhttp-related security fix[6] with no assigned CVE, which provides 
added motivation to update.


The ABI break in llhttp would only affect python-aiohttp. The 
python-aiohttp update itself is compatible (by upstream intent, and as 
already demonstrated in Rawhide and F39/F38); and a large list of 
packages that depend on python-aiohttp would benefit from the fix. The 
necessary rebuild would be conducted in a side tag.


The same incompatible update was approved by FESCo for Fedora 38 and 
39[7]. Furthermore, it appears that FESCo will approve a permanent 
exception for llhttp[8].


The purpose of this email is to document and explain the proposed 
update, to begin the minimum one-week discussion period mandated by the 
EPEL Incompatible Upgrades Policy, and to request that the update be 
added to the agenda for an upcoming EPEL meeting.


[1] 
https://docs.fedoraproject.org/en-US/epel/epel-policy-incompatible-upgrades/#process_for_incompatible_upgrades


[2] https://github.com/aio-libs/aiohttp/releases/tag/v3.8.6

[3] https://access.redhat.com/security/cve/CVE-2023-47627

[4] 
https://github.com/aio-libs/aiohttp/security/advisories/GHSA-gfw2-4jvh-wgfg


[5] https://bugzilla.redhat.com/show_bug.cgi?id=2249825

[6] https://github.com/aio-libs/aiohttp/releases/tag/v3.8.6

[7] https://pagure.io/fesco/issue/3106

[8] https://pagure.io/fesco/issue/3115
--
___
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

[Bug 2251701] perl-Time-Out-0.24 is available

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

   Fixed In Version||perl-Time-Out-0.24-1.fc40
 Status|ASSIGNED|MODIFIED



--- Comment #1 from Petr Pisar  ---
Time::Out::ParamConstraints::assert_non_negative_number() was renamed to
assert_NonNegativeNumber(). Suitable for Rawhide only.


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

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202251701%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

Re: libxml2 2.12.0 (and 2.12.1) in rawhide, with some API breaks

[Florian Weimer]

* Petr Pisar:

> Well abidiff for createrepo_c
> 
> complains:
>
>   underlying type 'xmlParserCtxt*' changed:
> in pointed to type 'typedef xmlParserCtxt' at tree.h:40:1:
>   underlying type 'struct _xmlParserCtxt' at parser.h:181:1 
> changed:
> type size changed from 3840 to 3968 (in bits)
> 4 data member insertions:
>   'unsigned int maxAmpl', at offset 3840 (in bits) at 
> parser.h:323:1
>   'xmlParserNsData* nsdb', at offset 3872 (in bits) at 
> parser.h:325:1
>   'unsigned int attrHashMax', at offset 3904 (in bits) at 
> parser.h:326:1
>   'xmlAttrHashBucket* attrHash', at offset 3936 (in bits) at 
> parser.h:327:1
> 1 data member changes (5 filtered):
>   type of 'int* attallocs' changed:
> in pointed to type 'int':
>   type name changed from 'int' to 'unsigned int'
>   type size hasn't changed
>
> While most (all?) libxml2 functions pass a pointer to xmlParserCtxt, a
> definition of the xmlParserCtxt structure is open to anybody in
> . That means an application built against old libxml2 can
> construct a different structure than libxml2 expects. That is called
> an ABI breakage.

I don't think the API allows you to bring your own xmlParserCtxt object
(stack-allocated or heap-allocated).  The new members are added at the
end, so this is probably fine.

Thanks,
Florian
--
___
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 2251701] perl-Time-Out-0.24 is available

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

 CC|ppi...@redhat.com   |
 Status|NEW |ASSIGNED
   Doc Type|--- |If docs needed, set a value




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2251701
--
___
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] [Fedocal] Reminder meeting : EPEL Steering Committee

[tdawson]

Dear all,

You are kindly invited to the meeting:
   EPEL Steering Committee on 2023-11-29 from 16:00:00 to 17:00:00 US/Eastern
   At fedora-meet...@chat.fedoraproject.org

The meeting will be about:
https://chat.fedoraproject.org/#/room/#meeting:fedoraproject.org

This is the weekly EPEL Steering Committee Meeting.

A general agenda is the following:

#topic aloha

#topic EPEL Issues https://pagure.io/epel/issues
* https://pagure.io/epel/issues?tags=meeting=Open

#topic Old Business (if needed)

#topic General Issues / Open Floor




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

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

[Bug 2251181] perl-XML-LibXML: FTBFS with libxml2 2.12.0

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

 Status|MODIFIED|CLOSED
 Resolution|--- |RAWHIDE
Last Closed||2023-11-28 15:58:17




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2251181
--
___
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: libxml2 2.12.0 (and 2.12.1) in rawhide, with some API breaks

[Petr Pisar]

V Tue, Nov 28, 2023 at 12:24:45PM +0100, Dodji Seketeli napsal(a):
> Daniel P. Berrangé  a écrit:
> 
> > On Mon, Nov 27, 2023 at 04:20:16PM +0100, Fabio Valentini wrote:
> >> On Fri, Nov 24, 2023 at 12:08 PM David King  
> >> wrote:
> >> >
> >> > The latest released versions of libxml2 have a couple of important
> >> > changes in header files that have unintentionally caused some packages
> >> > to fail to build without modification, including:
> >> >
> >> > * several functions now accept or return a const xmlError struct
> >> > * cyclic dependencies in header files were fixed (by dropping some
> >> >includes)
> >> 
> >> Sorry if the answer to this question is obvious - but shouldn't
> >> breaking changes like these cause an soname bump?
> >> I realize the whole "unintentional" part - but if these changes also
> >> affect ABI (the first sounds like it might do that), dependent
> >> packages would need to be rebuilt either way, wouldn't they?
> >
> > IIUC, the changes in libxml2 are API breaks, but not ABI breaks.
> >
> > ie the 'xmlError' parameter should have been const all along,
> > and apps would have been using it as if it were const. The
> > API was changed to correct this mistake and should be backcompat
> > with an pre-existing compiled app, but cause warnings on new
> > builds. Annoying, but an acceptable change without soname bump.
> 
> For what it's worth, the ABI compatibility verifier caught this change
> between libxml2.so.2.11.5 and libxml2.so.2.12.0 and categorized it as
> being "ABI compatible" (i.e, not incompatible/breaking) at:
> https://artifacts.dev.testing-farm.io/b7d369b0-f288-4564-a331-48492c20bf8c/:
> 
>   [C] 'function int xmlCopyError(xmlErrorPtr, xmlErrorPtr)' at error.c:985:1 
> has some indirect sub-type changes:
> parameter 1 of type 'typedef xmlErrorPtr' changed:
>   entity changed from 'typedef xmlErrorPtr' to compatible type 'const 
> xmlError*'
> in pointed to type 'struct _xmlError':
>   entity changed from 'struct _xmlError' to 'const _xmlError'
>   type size hasn't changed
> 
> I guess the important bit here is "entity changed from 'struct _xmlError' to 
> 'const _xmlError'".
> 
> So, yes, this is not an ABI incompatible change.
>
Well abidiff for createrepo_c

complains:

  underlying type 'xmlParserCtxt*' changed:
in pointed to type 'typedef xmlParserCtxt' at tree.h:40:1:
  underlying type 'struct _xmlParserCtxt' at parser.h:181:1 changed:
type size changed from 3840 to 3968 (in bits)
4 data member insertions:
  'unsigned int maxAmpl', at offset 3840 (in bits) at 
parser.h:323:1
  'xmlParserNsData* nsdb', at offset 3872 (in bits) at 
parser.h:325:1
  'unsigned int attrHashMax', at offset 3904 (in bits) at 
parser.h:326:1
  'xmlAttrHashBucket* attrHash', at offset 3936 (in bits) at 
parser.h:327:1
1 data member changes (5 filtered):
  type of 'int* attallocs' changed:
in pointed to type 'int':
  type name changed from 'int' to 'unsigned int'
  type size hasn't changed

While most (all?) libxml2 functions pass a pointer to xmlParserCtxt, a
definition of the xmlParserCtxt structure is open to anybody in
. That means an application built against old libxml2 can
construct a different structure than libxml2 expects. That is called
an ABI breakage.

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

[EPEL-devel] Missing EL sub-package: perl-lasso-epel EPEL only package for perl bindings

[Xavier Bachelot via epel-devel]

Hi,

Lasso, as provided in EL7, EL8 and EL9, doesn't have a perl-lasso 
sub-package, which provides the perl bindings. It is not built for EL7, 
and is built but not shipped for both EL8 and EL9.
Quite some time ago, I have filed a ticket requesting that the perl and 
python bindings be shipped in EL8 and EL9 [1]. python was just a guess, 
but it turned out to be correct. It was granted for python, as epsilon 
as a need for it, but was not for perl. I have since re-opened the 
ticket, as the software I need the perl bindings for is now available in 
Fedora, which does have the perl sub-package and thus has SAML support, 
and also in EPEL, where SAML support is indeed missing [2].
I have prepared a perl-lasso-epel spec file to add missing perl bindings 
support to EL releases and as this is the first time I go this route, 
although the EPEL guidelines states this is a review request exception 
[3], I would like the package to be looked at by people with more 
experience on the matter [4].


Thanks,
Xavier

[1] https://bugzilla.redhat.com/show_bug.cgi?id=2041941
[2] https://src.fedoraproject.org/rpms/lemonldap-ng
[3] 
https://docs.fedoraproject.org/en-US/epel/epel-policy-missing-sub-packages/

[4] https://bugzilla.redhat.com/show_bug.cgi?id=2251952
--
___
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

[Bug 2251181] perl-XML-LibXML: FTBFS with libxml2 2.12.0

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

 Status|ASSIGNED|MODIFIED
   Fixed In Version||perl-XML-LibXML-2.0209-3.fc
   ||40




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2251181
--
___
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 2251181] perl-XML-LibXML: FTBFS with libxml2 2.12.0

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

 CC|jples...@redhat.com,|ppi...@redhat.com
   |mspa...@redhat.com  |
   Assignee|jples...@redhat.com |ppi...@redhat.com
 Status|NEW |ASSIGNED




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2251181
--
___
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: unresponsive maintainer for python-installer

[Charalampos Stratakis]

On Mon, Nov 27, 2023 at 2:15 PM Kaleb Keithley  wrote:

>
> Is someone in contact with cstratak?
>
> I started the non-responsive maintainer process [1], because I asked that
> python-installer be branched and built for epel, or to add the EPEL
> packagers SIG to the maintainers [2] on 14 Nov 2023 and added a NEEDINFO on
> 16 Nov.
>
> Even after allowing for holidays, PTOs, and etc., there is still no
> response.
>
> Thanks
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=2251761
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=2249631
>
>
> --
>
> Kaleb
> --
> ___
> 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
>

Hey Kaleb,

Apologies for not responding, I've been extremely busy and I didn't have
much time to look at Fedora.

I've added the epel-packagers-sig as a collaborator to the python-installer
package.

However you could contact me directly on email before initiating the formal
process, that would have been easier.
-- 
Regards,

Charalampos Stratakis
Senior Software Engineer
Python Maintenance 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: unresponsive maintainer for python-installer

[Miro Hrončok]

On 27. 11. 23 14:14, Kaleb Keithley wrote:


Is someone in contact with cstratak?

I started the non-responsive maintainer process [1], because I asked that 
python-installer be branched and built for epel, or to add the EPEL packagers 
SIG to the maintainers [2] on 14 Nov 2023 and added a NEEDINFO on 16 Nov.


Side note: You should probably follow 
https://docs.fedoraproject.org/en-US/epel/epel-package-request/#fedora_packagers 
instead.


tl;dr After 1 week, add a reminder. After 2 weeks, open a releng ticket, become 
the epel maintainer.


--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
--
___
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: [Anaconda-devel] Re: Possible deprecation/removal of Initial Setup from Fedora

[mkolman]

On Mon, 2023-11-27 at 08:51 -0500, Neal Gompa wrote:
> On Mon, Nov 27, 2023 at 8:13 AM  wrote:
> > 
> > On Fri, 2023-11-24 at 15:15 -0800, Adam Williamson wrote:
> > > On Tue, 2023-11-21 at 13:34 +0100, Jiri Konecny wrote:
> > > > Hello everyone,
> > > > 
> > > > Is Anaconda Initial Setup important for your project or
> > > > workflow?
> > > > What
> > > > functionality is absolutely necessary for you? Do you use the
> > > > text
> > > > mode
> > > > or the graphical mode? Are you aware of any alternatives? Is
> > > > there
> > > > anything that would prevent you from migrating to one of the
> > > > proposed
> > > > alternatives? Also please feel free to share this mail to any
> > > > relevant
> > > > groups.
> > > 
> > > In addition to the other uses identified: if you do a KDE install
> > > and
> > > set the root password but do not create a user account, i-s will
> > > run
> > > on
> > > first boot and allow (not sure if it requires) user creation.
> > > This is
> > > probably the case for other non-GNOME desktops too (GNOME uses
> > > its
> > > own
> > > gnome-initial-setup).
> > Sure, but is this really necessary on those images ? If it only
> > triggers if no user account is present only only provides user
> > creation, what about enforcing user creation at installation time
> > instead ?
> > 
> 
> That is not possible in all cases. Two cases offhand that it is not
> possible on:
> 
> * ARM images
> * OEM preload images
> 
> These two cases require us to not pre-configure a user but also allow
> the user to be created on first boot.
Sure - those require to run int the reconfig mode, where Initial Setup
provides access to all the screens it can run on a booted machine.

I was just wondering if the Live media use case, where Initial Setup
only creates a user account if none is created at installation time
makes sense & could be perhaps replaced by Anaconda just requiring
users to create a user at installation time on the Live images.

That could reduce the overall complexity a bit. :)

> 
> 
> 
--
___
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: libxml2 2.12.0 (and 2.12.1) in rawhide, with some API breaks

[Dodji Seketeli]

Daniel P. Berrangé  a écrit:

> On Mon, Nov 27, 2023 at 04:20:16PM +0100, Fabio Valentini wrote:
>> On Fri, Nov 24, 2023 at 12:08 PM David King  wrote:
>> >
>> > The latest released versions of libxml2 have a couple of important
>> > changes in header files that have unintentionally caused some packages
>> > to fail to build without modification, including:
>> >
>> > * several functions now accept or return a const xmlError struct
>> > * cyclic dependencies in header files were fixed (by dropping some
>> >includes)
>> 
>> Sorry if the answer to this question is obvious - but shouldn't
>> breaking changes like these cause an soname bump?
>> I realize the whole "unintentional" part - but if these changes also
>> affect ABI (the first sounds like it might do that), dependent
>> packages would need to be rebuilt either way, wouldn't they?
>
> IIUC, the changes in libxml2 are API breaks, but not ABI breaks.
>
> ie the 'xmlError' parameter should have been const all along,
> and apps would have been using it as if it were const. The
> API was changed to correct this mistake and should be backcompat
> with an pre-existing compiled app, but cause warnings on new
> builds. Annoying, but an acceptable change without soname bump.

For what it's worth, the ABI compatibility verifier caught this change
between libxml2.so.2.11.5 and libxml2.so.2.12.0 and categorized it as
being "ABI compatible" (i.e, not incompatible/breaking) at:
https://artifacts.dev.testing-farm.io/b7d369b0-f288-4564-a331-48492c20bf8c/:

  [C] 'function int xmlCopyError(xmlErrorPtr, xmlErrorPtr)' at error.c:985:1 
has some indirect sub-type changes:
parameter 1 of type 'typedef xmlErrorPtr' changed:
  entity changed from 'typedef xmlErrorPtr' to compatible type 'const 
xmlError*'
in pointed to type 'struct _xmlError':
  entity changed from 'struct _xmlError' to 'const _xmlError'
  type size hasn't changed

I guess the important bit here is "entity changed from 'struct _xmlError' to 
'const _xmlError'".

So, yes, this is not an ABI incompatible change.

Cheers,

-- 
Dodji
--
___
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: [HEADS UP] Jasper update with .so name update

[Mamoru TASAKA]

Orion Poplawski wrote on 2023/11/28 11:26:

On 11/27/23 13:31, Adam Williamson wrote:

On Tue, 2023-11-21 at 10:55 +0100, Josef Řídký wrote:

Hi,

there is a new jasper version (4.1.0) that will be available in Fedora 40+.
As this version is bumping it's .so name, the rebuild of the dependent
package will be necessary.

There is a side tag created for safe rebuild of those packages
(f40-build-side-77302) with a new jasper version available.

I would like to ask maintainers of affected packages to rebuild their
packages using this tag, so I will be able to push the update to f40 once
all is done.

List of affected packages is:
- eccodes-devel
- g2clib-devel
- grib_api-devel


Somehow your list is far too short:

[adamw@xps13a tmp]$ sudo dnf repoquery --whatrequires
"libjasper.so.6()(64bit)"
DevIL-0:1.7.8-42.fc39.x86_64
DevIL-ILUT-0:1.7.8-42.fc39.x86_64
GraphicsMagick-0:1.3.40-3.fc39.x86_64
LibRaw-0:0.21.1-6.fc40.x86_64
OpenSceneGraph-libs-0:3.6.5-19.fc40.x86_64
dcraw-0:9.28.0-20.fc39.x86_64
digikam-libs-0:8.1.0-3.fc39.x86_64
eccodes-0:2.32.1-1.fc40.x86_64
gegl04-0:0.4.46-1.fc40.x86_64
grib_api-0:1.27.0-19.fc39.x86_64
jasper-0:3.0.6-4.fc39.x86_64
jasper-devel-0:3.0.6-4.fc39.x86_64
jasper-utils-0:3.0.6-4.fc39.x86_64
kdelibs-6:4.14.38-40.fc40.x86_64
kdelibs3-0:3.5.10-123.fc40.x86_64
libicns-0:0.8.1-27.fc39.x86_64
ncl-0:6.6.2-38.fc40.x86_64
netpbm-progs-0:11.02.00-2.fc39.x86_64
qt5-qtimageformats-0:5.15.11-1.fc40.x86_64
qt6-qtimageformats-0:6.6.0-1.fc40.x86_64
wgrib2-0:3.1.3-1.fc40.x86_64

the update failed gating because of qt5-qtimageformats, but all the
others also ought to be rebuilt onto the side tag before this is
pushed.


I've built most of these and working on the rest - but I think we're bumping 
into a qt6 update at the same time.  Pinging maintainers here.


qt6-qtimageformats rebuilt for f40-build-side-78512 .
(new jasper-4.1.0-1.fc40 already in buildroot)



Other issues:
kdelibs/kdelibs3 are FTBFS



I've fixed these FTBFS (actually was libxml2-2.12.0 issue).

Regards,
Mamoru
--
___
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

Synching user database from Fedora IPA to pagure

[Mattia Verga via devel]

I'd like to start writing a script to synch users/groups from Fedora IPA 
to pagure.io and src.fp.o: both pagure.io and src.fp.o logins are based 
on Fedora accounts, but the Pagure user database is only updated when a 
user login in Pagure.

That means that by searching for a user or looking group memberships in 
Pagure we don't have an updated, real view of what we have in IPA. With 
the old FAS system there used to be a synch script provided by 
pagure-dist-git plugin, so I plan to use that as the base for a new 
synch script from IPA.

However, before digging in how (and if) is possible to add new users 
using pagure libraries, I'd like to ask if it would be acceptable to 
"copy" user data from one database to another (except passwords, which 
remain in IPA only). We will need to pass username, full name, email and 
group memberships from IPA to pagure.io/src.fp.o, which is what is done 
when a user logs in for the first time.

If that's not acceptable, I think I can just only update group 
membership for users already in pagure database.

Thoughts?

Mattia

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