[Bug 2252645] perl-File-MimeInfo-0.34 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

   Fixed In Version|perl-File-MimeInfo-0.34-1.f |perl-File-MimeInfo-0.34-1.f
   |c40 |c40
   ||perl-File-MimeInfo-0.34-1.f
   ||c39



--- Comment #5 from Fedora Update System  ---
FEDORA-2023-715630ea6f 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=2252645

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla=report-spam_desc=Report%20of%20Bug%202252645%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 2239168] perl-GnuPG-Interface-1.04 is available

[bugzilla]

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

Upstream Release Monitoring  
changed:

   What|Removed |Added

Summary|perl-GnuPG-Interface-1.03   |perl-GnuPG-Interface-1.04
   |is available|is available



--- Comment #1 from Upstream Release Monitoring 
 ---
Releases retrieved: 1.04
Upstream release that is considered latest: 1.04
Current version/release in rawhide: 1.02-7.fc38
URL: https://metacpan.org/dist/GnuPG-Interface

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


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


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

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

[Lennart Poettering]

On Mo, 11.12.23 11:10, DJ Delorie (d...@redhat.com) wrote:

> Lennart Poettering  writes:
> > Well, as you might be aware many distributions these days do more than
> > "files dns" for "hosts", and similar for the other databases, and
> > hence a built-in default in glibc is great, but most distributions and
> > image builders probably want to pick different defaults without having
> > to patch glibc for this.
>
> I agree.  My point was that (1) glibc has a built-in default, and (2)
> most distros/users/installers customize it anyway, so storing a
> "default" version anywhere other than /etc is not needed.

This doesn't work though. Take Fedora for example. It supports a
systemd feature called "DynamicUser=". If you turn that on for some
service it will get a transient UID assigned the moment it is started
and it's released again when it is stopped. It's a resonably popular
feature. It requires that the "nss-systemd" modules is listed in
nsswitch.conf.

The glibc built-in default does not list "systemd" in its
nsswitch.conf line though. On Fedora, the module is patched in via
/etc/nsswitch.conf. But then you already lost, because now the distro
default and the configuration the user made are all mixed up in a
hairy ball and cannot be separated anymore.

I don't think it's realistic to ask the glibc maintainers to change
their built-in version of nsswitch.conf to always list systemd though
(as that doesn't even make sense in many cases, i.e. when you run
glibc inside a docker container without any systemd).

Hence it makes sense to isolate this cleanly:

0. have upstream defaults built-in to the binaries, where this applies
1. have distro/OS image defaults in /usr/
2. have user's own configuration in /etc/

That's a very clear separation of ownership, and means you can always
very clearly trace back where a change comes from, and combine things
flexibly in a multitude of ways without ever losing this concept
of provenance.

In systemd we have a tool "systemd-delta" which makes use of this
separation of ownership, and allows you to diff local settings
vs. distro/OS defaults.

Lennart

--
Lennart Poettering, Berlin
--
___
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

F40 Change Propsal: Boost 1.83 upgrade (System-Wide)

[Aoife Moloney]

Wiki https://fedoraproject.org/wiki/Changes/F40Boost183

This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive
community feedback. This proposal will only be implemented if approved
by the Fedora Engineering Steering Committee.

== Summary ==
This change brings Boost 1.83 to Fedora. This will mean Fedora ships
with a recent upstream Boost release.

== Owner ==

* Name: [[User:jwakely| Jonathan Wakely]]
* Email: jwak...@redhat.com
* Name: [[User:ppalka| Patrick Palka]]
* Email: ppa...@redhat.com


== Detailed Description ==

The aim is to synchronize Fedora with the most recent Boost release.
Because ABI stability is absent from Boost, this entails rebuilding of
all dependent packages. This also entails the change owner assisting
maintainers of client packages in decoding cryptic boost-ese seen in
output from g++.

The equivalent changes for previous releases were
[[Changes/F39Boost181]], [[Changes/F37Boost178]],
[[Changes/F35Boost176]], [[Changes/F34Boost175]],
[[Changes/F33Boost173]], [[Changes/F30Boost169|Fedora 30 Change]],
[[Changes/F29Boost167|Fedora 29 Change]], [[Changes/F28Boost166|Fedora
28 Change]], [[Changes/F27Boost164|Fedora 27 Change]],
[[Changes/F26Boost163|Fedora 26 Change]], [[Changes/F25Boost161|Fedora
25 Change]], [[Changes/F24Boost160|Fedora 24 Change]],
[[Changes/F23Boost159|Fedora 23 Change]] and
[[Changes/F22Boost158|Fedora 22 Change]].

== Benefit to Fedora ==

Fedora 40 includes Boost 1.83.

Fedora will stay relevant, as far as Boost clients are concerned.

Boost 1.83 and 1.82 do not bring any new components, but includes two
new header-only libraries -
* Compat: A repository of C++11 implementations of standard components
added in later C++ standards, from Peter Dimov and contributors.
* Mysql: A C++11 client for the MySQL database server, based on
Boost.Asio, from Ruben Perez.

Boost 1.83 also includes many fixes and enhancements to existing
components, including major and potentially breaking changes to
* Multi-index Containers: Serialization now uses std::size_t instead
of unsigned long to save and load the size of a multi_index_container
(unsigned long is smaller than std::size_t in LLP64 data models).
multi_index_container serialization class version has been bumped from
3 to 4 to reflect this change.
* Timer: Disable deprecated headers unless
BOOST_TIMER_ENABLE_DEPRECATED is defined.

Additionally the following breaking changes were introduced in Boost
1.82 and so also affect 1.83:
* Atomic: Removed atomic::storage() accessors and
atomic::storage_type types that were deprecated in Boost.Atomic
1.73. Users are recommended to use atomic::value() and
atomic::value_type instead.
* Geometry: The WKT output presentation of an empty polygon is now
POLYGON() to make it consistent with other geometries
* Math: Deprecated C++11 support.
* Multiprecision: Deprecated C++11 support.
* Process: Deprecated wait_for & wait_until in V1 - they will be
removed in the future!

== Scope ==
* Proposal owners:
** Build will be done with Boost.Build v2 (which is the
upstream-sanctioned way of building Boost)
** Request a "f40-boost"
[https://docs.pagure.org/releng/sop_adding_side_build_targets.html
build system tag]
([http://lists.fedoraproject.org/pipermail/devel/2011-November/159908.html
discussion]):


** Build boost into that tag (take a look at the
[http://koji.fedoraproject.org/koji/buildinfo?buildID=606493 build
#606493] for inspiration)
** Post a request for rebuilds to fedora-devel
** Work on rebuilding dependent packages in the tag.
** When most is done, re-tag all the packages to rawhide
** Watch fedora-devel and assist in rebuilding broken Boost clients
(by fixing the client, or Boost).

* Other developers:
** Those who depend on Boost DSOs will have to rebuild their packages.
Feature owners will alleviate some of this work as indicated above,
and will assist those whose packages fail to build in debugging them.


* Release engineering: TODO  (a check of an impact with Release Engineering is needed)

* Policies and guidelines:
** Apart from scope, this is business as usual, so no new policies, no
new guidelines.

* Trademark approval: N/A (not needed for this Change)


== Upgrade/compatibility impact ==
* No manual configuration or data migration needed.
* Some impact on other packages needing code changes to rebuild.
Historically this hasn't been too much of a problem and could always
be resolved before deadline.

== How To Test ==
* No special hardware is needed.
* Integration testing simply consists of installing Boost packages
(`dnf install boost`) on Fedora and checking that it does not break
other packages (see below for a way to obtain a list of boost
clients).


== User Experience ==
* Expected to remain largely the same.
* Developers building third-party software on Fedora may need to
rebuild against the new Boost packages, and may need to adjust their
code if 

F40 Change Propsal: Boost 1.83 upgrade (System-Wide)

[Aoife Moloney]

Wiki https://fedoraproject.org/wiki/Changes/F40Boost183

This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive
community feedback. This proposal will only be implemented if approved
by the Fedora Engineering Steering Committee.

== Summary ==
This change brings Boost 1.83 to Fedora. This will mean Fedora ships
with a recent upstream Boost release.

== Owner ==

* Name: [[User:jwakely| Jonathan Wakely]]
* Email: jwak...@redhat.com
* Name: [[User:ppalka| Patrick Palka]]
* Email: ppa...@redhat.com


== Detailed Description ==

The aim is to synchronize Fedora with the most recent Boost release.
Because ABI stability is absent from Boost, this entails rebuilding of
all dependent packages. This also entails the change owner assisting
maintainers of client packages in decoding cryptic boost-ese seen in
output from g++.

The equivalent changes for previous releases were
[[Changes/F39Boost181]], [[Changes/F37Boost178]],
[[Changes/F35Boost176]], [[Changes/F34Boost175]],
[[Changes/F33Boost173]], [[Changes/F30Boost169|Fedora 30 Change]],
[[Changes/F29Boost167|Fedora 29 Change]], [[Changes/F28Boost166|Fedora
28 Change]], [[Changes/F27Boost164|Fedora 27 Change]],
[[Changes/F26Boost163|Fedora 26 Change]], [[Changes/F25Boost161|Fedora
25 Change]], [[Changes/F24Boost160|Fedora 24 Change]],
[[Changes/F23Boost159|Fedora 23 Change]] and
[[Changes/F22Boost158|Fedora 22 Change]].

== Benefit to Fedora ==

Fedora 40 includes Boost 1.83.

Fedora will stay relevant, as far as Boost clients are concerned.

Boost 1.83 and 1.82 do not bring any new components, but includes two
new header-only libraries -
* Compat: A repository of C++11 implementations of standard components
added in later C++ standards, from Peter Dimov and contributors.
* Mysql: A C++11 client for the MySQL database server, based on
Boost.Asio, from Ruben Perez.

Boost 1.83 also includes many fixes and enhancements to existing
components, including major and potentially breaking changes to
* Multi-index Containers: Serialization now uses std::size_t instead
of unsigned long to save and load the size of a multi_index_container
(unsigned long is smaller than std::size_t in LLP64 data models).
multi_index_container serialization class version has been bumped from
3 to 4 to reflect this change.
* Timer: Disable deprecated headers unless
BOOST_TIMER_ENABLE_DEPRECATED is defined.

Additionally the following breaking changes were introduced in Boost
1.82 and so also affect 1.83:
* Atomic: Removed atomic::storage() accessors and
atomic::storage_type types that were deprecated in Boost.Atomic
1.73. Users are recommended to use atomic::value() and
atomic::value_type instead.
* Geometry: The WKT output presentation of an empty polygon is now
POLYGON() to make it consistent with other geometries
* Math: Deprecated C++11 support.
* Multiprecision: Deprecated C++11 support.
* Process: Deprecated wait_for & wait_until in V1 - they will be
removed in the future!

== Scope ==
* Proposal owners:
** Build will be done with Boost.Build v2 (which is the
upstream-sanctioned way of building Boost)
** Request a "f40-boost"
[https://docs.pagure.org/releng/sop_adding_side_build_targets.html
build system tag]
([http://lists.fedoraproject.org/pipermail/devel/2011-November/159908.html
discussion]):


** Build boost into that tag (take a look at the
[http://koji.fedoraproject.org/koji/buildinfo?buildID=606493 build
#606493] for inspiration)
** Post a request for rebuilds to fedora-devel
** Work on rebuilding dependent packages in the tag.
** When most is done, re-tag all the packages to rawhide
** Watch fedora-devel and assist in rebuilding broken Boost clients
(by fixing the client, or Boost).

* Other developers:
** Those who depend on Boost DSOs will have to rebuild their packages.
Feature owners will alleviate some of this work as indicated above,
and will assist those whose packages fail to build in debugging them.


* Release engineering: TODO  (a check of an impact with Release Engineering is needed)

* Policies and guidelines:
** Apart from scope, this is business as usual, so no new policies, no
new guidelines.

* Trademark approval: N/A (not needed for this Change)


== Upgrade/compatibility impact ==
* No manual configuration or data migration needed.
* Some impact on other packages needing code changes to rebuild.
Historically this hasn't been too much of a problem and could always
be resolved before deadline.

== How To Test ==
* No special hardware is needed.
* Integration testing simply consists of installing Boost packages
(`dnf install boost`) on Fedora and checking that it does not break
other packages (see below for a way to obtain a list of boost
clients).


== User Experience ==
* Expected to remain largely the same.
* Developers building third-party software on Fedora may need to
rebuild against the new Boost packages, and may need to adjust their
code if 

F40 Change Proposal: Podman 5 (Self-Contained)

[Aoife Moloney]

Wiki https://fedoraproject.org/wiki/Changes/Podman5

This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive
community feedback. This proposal will only be implemented if approved
by the Fedora Engineering Steering Committee.

== Summary ==
Ship Podman 5 in Fedora 40.


== Owner ==
* Name: [[User:lsm5| Lokesh Mandvekar]], [[User:mohanboddu| Mohan Boddu]]


== Detailed Description ==

== Feedback ==

== Benefit to Fedora ==
Podman 5 will:
* No longer support cgroups v1
* Deprecate CNI plugins
* Deprecate Boltdb
* Have passt as the default rootless network service instead of slirp4netns
* Support stable `--format` Go template structs
* Isolate podman bindings leading to improved usability
* Allow better handling of containers.conf



== Scope ==
* Proposal owners:

* Other developers:

* Release engineering: [https://pagure.io/releng/issues #Releng issue number]

* Policies and guidelines: N/A (not needed for this Change) 


* Trademark approval: N/A (not needed for this Change)


* Alignment with Community Initiatives:


== Upgrade/compatibility impact ==

Podman 5 will come with breaking changes affecting upgradability:
* CGroups v1 environments will be required to switch to CGroups v2
* CNI plugin environemnts will need to switch to netavark
* Changes in `--format` Go template structs



== How To Test ==
Probably best handled in a Podman Test Day aligned with Fedora 40 Test Days.

* Install Fedora 40
* Install Podman 5
* Run test cases / suite (TBD)


== User Experience ==

Podman 5 will provide better usability of Podman bindings, easier to
maintain containers.conf and other configuration files along with
database performance improvements and CLI enhancements.



== Dependencies ==
Projects / Packages likely to be affected:
* Cockpit
* CoreOS
* Toolbox
* Silverblue / Kinoite
* Podman Desktop



== Contingency Plan ==
* Contingency mechanism: (What to do?  Who will do it?) N/A
* Contingency deadline: N/A (not a System Wide Change)
* Blocks release? N/A (not a System Wide Change)


== Documentation ==
N/A (not a System Wide Change)

== Release Notes ==



-- 
Aoife Moloney

Fedora Operations Architect

Fedora Project

Matrix: @amoloney:fedora.im

IRC: amoloney
--
___
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

F40 Change Proposal: Podman 5 (Self-Contained)

[Aoife Moloney]

Wiki https://fedoraproject.org/wiki/Changes/Podman5

This is a proposed Change for Fedora Linux.
This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive
community feedback. This proposal will only be implemented if approved
by the Fedora Engineering Steering Committee.

== Summary ==
Ship Podman 5 in Fedora 40.


== Owner ==
* Name: [[User:lsm5| Lokesh Mandvekar]], [[User:mohanboddu| Mohan Boddu]]


== Detailed Description ==

== Feedback ==

== Benefit to Fedora ==
Podman 5 will:
* No longer support cgroups v1
* Deprecate CNI plugins
* Deprecate Boltdb
* Have passt as the default rootless network service instead of slirp4netns
* Support stable `--format` Go template structs
* Isolate podman bindings leading to improved usability
* Allow better handling of containers.conf



== Scope ==
* Proposal owners:

* Other developers:

* Release engineering: [https://pagure.io/releng/issues #Releng issue number]

* Policies and guidelines: N/A (not needed for this Change) 


* Trademark approval: N/A (not needed for this Change)


* Alignment with Community Initiatives:


== Upgrade/compatibility impact ==

Podman 5 will come with breaking changes affecting upgradability:
* CGroups v1 environments will be required to switch to CGroups v2
* CNI plugin environemnts will need to switch to netavark
* Changes in `--format` Go template structs



== How To Test ==
Probably best handled in a Podman Test Day aligned with Fedora 40 Test Days.

* Install Fedora 40
* Install Podman 5
* Run test cases / suite (TBD)


== User Experience ==

Podman 5 will provide better usability of Podman bindings, easier to
maintain containers.conf and other configuration files along with
database performance improvements and CLI enhancements.



== Dependencies ==
Projects / Packages likely to be affected:
* Cockpit
* CoreOS
* Toolbox
* Silverblue / Kinoite
* Podman Desktop



== Contingency Plan ==
* Contingency mechanism: (What to do?  Who will do it?) N/A
* Contingency deadline: N/A (not a System Wide Change)
* Blocks release? N/A (not a System Wide Change)


== Documentation ==
N/A (not a System Wide Change)

== Release Notes ==



-- 
Aoife Moloney

Fedora Operations Architect

Fedora Project

Matrix: @amoloney:fedora.im

IRC: amoloney
--
___
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: Creation of new package repo failed, Invalid or expired token

[Kevin Fenzi]

On Tue, Dec 12, 2023 at 11:14:03AM -, Felix Wang wrote:
> I opened an releng issue about this. [1] At the time of writing, I noticed 
> that there is probably an similar issue of failure of package creation 
> appeared. [2] Hope anyone can help me solve the problem, which maybe the 
> cause of my personal issue, or other factors. Thanks in advance.
> 
> [1] https://pagure.io/releng/issue/11829
> [2] https://pagure.io/releng/fedora-scm-requests/issue/58752

Just to note, this was all taken care shortly after you opened the
tickets. :) 

kevin


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

Migration to pkcs11-provider from OpenSSL engines

[Sahana Prasad]

Hello,

OpenSSL 3.0.0 deprecated the support for using engines and introduced the
concept of providers.
 If your package requires openssl-pkcs11 (libp11, engine_pkcs11), we
recommend that you stop using it, and migrate to using the pkcs11-provider
instead. We plan to deprecate and remove openssl-pkcs11 by Fedora 41

The pkcs11-provider [1] (available since Fedora 38) is an Openssl 3.0.0
provider designed to access Hardware or Software Tokens using the PKCS#11
Cryptographic Token Interface.

To read more about the pkcs11-provider you can have a look at [2]-
 If you have any questions kindly start a discussion here [4] we are more
than happy to help.

List of packages that require openssl-pkcs11 -
libssh, rng-tools, libp11-devel, freeipa-server-dns, bind-dyndb-ldap,
cryptobone, nginx, apache2

Just a note that pkcs11-provider is a new project and we are working
continuously to improve it and test it extensively. If you encounter any
issues, feel free to report them upstream [3].

Thank you for your understanding and we are looking forward to your
collaboration.

[1] https://koji.fedoraproject.org/koji/packageinfo?packageID=37379
[2]  https://github.com/latchset/pkcs11-provider.
[3] https://github.com/latchset/pkcs11-provider/issues
[4] https://github.com/latchset/pkcs11-provider/discussions
--
___
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] [Fedocal] Reminder meeting : EPEL Steering Committee

[tdawson]

Dear all,

You are kindly invited to the meeting:
   EPEL Steering Committee on 2023-12-13 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

RFC: OpenScanHub Prototype for Fedora

[Siteshwar Vashisht]

Hello,

I am writing this email to get feedback from the members of the Fedora
development community about OpenScanHub for Fedora.

# tl;dr

OpenScanHub does static and dynamic analysis of rpm packages and it may be
helpful in the Fedora community. Please take a look at our staging proof of
concept[4] and provide feedback. The proof of concept is in its early
stages so there may be some bugs here or there! If the feedback is positive
we may roll this out in official infrastructure and integrate with Fedora
CI and Packit.

# What

OpenScanHub is a service for static and dynamic analysis. It has been in
development inside Red Hat[1] for more than 12 years and was open sourced
on GitHub[2] earlier this year. You can read a brief explanation of this
service on my blog[3]. We would like to deploy this service on the Fedora
infrastructure and start scanning packages shipped in the Fedora project
through it.

# Why

I am sharing a prototype[4] of this service to get feedback from the
community. This prototype is running on the staging instance of the Fedora
infrastructure, so you would have to login[5] to the staging instance
before submitting any scan. If you have never logged into that account, it
may require you to do a password reset.

Once you are logged into the staging instance, you can login through the
`krb5login` button[6] on the top right corner of the homepage and submit a
scan through this form[7].

There are 3 different types of scans supported by OpenScanHub:

   -

   MockBuild performs a full scan of the package including downstream
   patches. Example[8] mockbuild for `openssl-3.1.1-4.fc39`.
   -

   DiffBuild performs a differential scan on the downstream patches. So you
   can find only the defects that are introduced by the downstream patches.
   Example[9] diffbuild for `openssl-3.1.1-4.fc39`. This option would not work
   if the package fails to compile without patches.
   -

   VersionDiffBuild performs a differential scan between 2 different
   versions of the package, and you can see defects introduced by the “newer”
   version of the package. Example[10] differential build between
   `openssl-3.1.1-4.fc39` and `openssl-3.0.9-2.fc38`.

All the submitted scans can be seen on the tasks[11] page.

This prototype is running on very limited resources, so please do not
submit scan for any resource consuming package. Not all defects reported by
OpenScanHub may be actual bugs, so please avoid fixing reported defects
without careful examination. If we receive positive feedback on this
prototype, there may be a possibility of integrating this service with the
Fedora CI and Packit projects.

This is a very early stage prototype and may behave inconsistently. Please
keep the discussion in this thread constructive. Thank you!

[1] https://kdudka.fedorapeople.org/muni23.pdf

[2] https://github.com/openscanhub/openscanhub

[3] https://situ.im/posts/openscanhub

[4] https://staging-openscanhub.apps.ocp.stg.fedoraproject.org/

[5] https://accounts.stg.fedoraproject.org

[6]
https://staging-openscanhub.apps.ocp.stg.fedoraproject.org/auth/krb5login/


[7] https://staging-openscanhub.apps.ocp.stg.fedoraproject.org/scan/new/

[8]
https://staging-openscanhub.apps.ocp.stg.fedoraproject.org/task/6/log/openssl-3.1.1-4.fc39/scan-results.html

[9]
https://staging-openscanhub.apps.ocp.stg.fedoraproject.org/task/9/log/openssl-3.1.1-4.fc39/scan-results.html

[10]
https://staging-openscanhub.apps.ocp.stg.fedoraproject.org/task/7/log/added.html
[11] https://staging-openscanhub.apps.ocp.stg.fedoraproject.org/task/
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Self Introduction: Rafel Amer

[Priscila Gutierres]

Hello Rafel

I'm also a mathematician and I'm happy to see other people from mathematics
get involved with Fedora
Until you not become a Fedora maintainer (I hope you find a sponsor soon!)
we can work together
As a Fedora maintainer I think I can check and merge your PRs.

Priscila.

On Sun, Dec 10, 2023 at 6:17 PM Rafel Amer Ramon  wrote:

> Hi,
>
> my name is Rafel Amer and I'm professor at the Technical University of
> Catalonia https:/www.upc.edu. I teach Maths
> and I use sagemath for my classes. After the sagemath package is
> orphandend, I would like to be a maintainer or
> co-maintainer this package.
>
> I have successfully build sagemath 10.1 packages for Fedora 38 in x86_64
> and aarch64 architectures, so I think that
> I could maintain this package.
>
> I started using Linux in  1995 with Slackware and I have administered
> server with Debian and CentOS. At house and
> for my classes I use Fedora 28.
>
> Regards,
>
> Rafel Amer
>
> --
> ___
> 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

Fedora rawhide compose report: 20231212.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-Rawhide-20231211.n.0
NEW: Fedora-Rawhide-20231212.n.0

= SUMMARY =
Added images:2
Dropped images:  7
Added packages:  6
Dropped packages:0
Upgraded packages:   91
Downgraded packages: 0

Size of added packages:  2.40 GiB
Size of dropped packages:0 B
Size of upgraded packages:   2.29 GiB
Size of downgraded packages: 0 B

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

= ADDED IMAGES =
Image: Silverblue dvd-ostree ppc64le
Path: 
Silverblue/ppc64le/iso/Fedora-Silverblue-ostree-ppc64le-Rawhide-20231212.n.0.iso
Image: Silverblue dvd-ostree aarch64
Path: 
Silverblue/aarch64/iso/Fedora-Silverblue-ostree-aarch64-Rawhide-20231212.n.0.iso

= DROPPED IMAGES =
Image: Python_Classroom raw-xz aarch64
Path: 
Labs/aarch64/images/Fedora-Python-Classroom-Rawhide-20231211.n.0.aarch64.raw.xz
Image: Onyx dvd-ostree x86_64
Path: Onyx/x86_64/iso/Fedora-Onyx-ostree-x86_64-Rawhide-20231211.n.0.iso
Image: i3 live aarch64
Path: Spins/aarch64/iso/Fedora-i3-Live-aarch64-Rawhide-20231211.n.0.iso
Image: Kinoite dvd-ostree aarch64
Path: Kinoite/aarch64/iso/Fedora-Kinoite-ostree-aarch64-Rawhide-20231211.n.0.iso
Image: Kinoite dvd-ostree x86_64
Path: Kinoite/x86_64/iso/Fedora-Kinoite-ostree-x86_64-Rawhide-20231211.n.0.iso
Image: Python_Classroom live x86_64
Path: 
Labs/x86_64/iso/Fedora-Python-Classroom-Live-x86_64-Rawhide-20231211.n.0.iso
Image: Security live x86_64
Path: Labs/x86_64/iso/Fedora-Security-Live-x86_64-Rawhide-20231211.n.0.iso

= ADDED PACKAGES =
Package: dotnet8.0-8.0.100-1.fc40
Summary: .NET Runtime and SDK
RPMs:aspnetcore-runtime-8.0 aspnetcore-targeting-pack-8.0 
dotnet-apphost-pack-8.0 dotnet-host dotnet-hostfxr-8.0 dotnet-runtime-8.0 
dotnet-sdk-8.0 dotnet-sdk-8.0-source-built-artifacts dotnet-targeting-pack-8.0 
dotnet-templates-8.0 netstandard-targeting-pack-2.1
Size:2.40 GiB

Package: rust-cachedir-0.3.1-1.fc40
Summary: Library to help interacting with cache directories and CACHEDIR.TAG 
files
RPMs:rust-cachedir+default-devel rust-cachedir-devel
Size:21.32 KiB

Package: rust-epoll-4.3.3-1.fc40
Summary: Safe epoll interface
RPMs:rust-epoll+default-devel rust-epoll-devel
Size:24.44 KiB

Package: rust-imperative-1.0.5-1.fc40
Summary: Check for imperative mood in text
RPMs:rust-imperative+default-devel rust-imperative-devel
Size:26.77 KiB

Package: rust-is-macro-0.3.1-1.fc40
Summary: Derive methods for using custom enums like Option / Result
RPMs:rust-is-macro+default-devel rust-is-macro-devel
Size:22.09 KiB

Package: rust-quick-junit-0.3.4-1.fc40
Summary: Data model and serializer for JUnit/XUnit XML
RPMs:rust-quick-junit+default-devel rust-quick-junit-devel
Size:31.31 KiB


= DROPPED PACKAGES =

= UPGRADED PACKAGES =
Package:  SDL_gfx-2.0.27-1.fc40
Old package:  SDL_gfx-2.0.26-10.fc39
Summary:  SDL graphics drawing primitives and other support functions
RPMs: SDL_gfx SDL_gfx-devel
Size: 379.26 KiB
Size change:  -170 B
Changelog:
  * Mon Dec 11 2023 Gwyn Ciesla  - 2.0.27-1
  - 2.0.27


Package:  annobin-12.33-1.fc40
Old package:  annobin-12.32-1.fc40
Summary:  Annotate and examine compiled binary files
RPMs: annobin-annocheck annobin-docs annobin-libannocheck 
annobin-plugin-clang annobin-plugin-gcc annobin-plugin-llvm
Size: 5.40 MiB
Size change:  -11.50 KiB
Changelog:
  * Mon Dec 11 2023 Nick Clifron   - 12.33-1
  - Tests: Fix implicit-values test so that it will compile with gcc 14+.


Package:  ansible-collection-netbox-netbox-3.16.0-1.fc40
Old package:  ansible-collection-netbox-netbox-3.9.0-2.fc38
Summary:  Netbox modules for Ansible
RPMs: ansible-collection-netbox-netbox
Size: 624.16 KiB
Size change:  18.09 KiB
Changelog:
  * Wed Jul 19 2023 Fedora Release Engineering  - 
3.9.0-3
  - Rebuilt for https://fedoraproject.org/wiki/Fedora_39_Mass_Rebuild

  * Tue Dec 12 2023 Maxwell G  - 3.16.0-1
  - Update to 3.16.0. Fixes rhbz#2143247.


Package:  ansible-core-2.16.2-1.fc40
Old package:  ansible-core-2.16.1-1.fc40
Summary:  A radically simple IT automation system
RPMs: ansible-core ansible-core-doc
Size: 5.14 MiB
Size change:  1.24 KiB
Changelog:
  * Mon Dec 11 2023 Maxwell G  - 2.16.2-1
  - Update to 2.16.2. Fixes rhbz#2254093.


Package:  bootc-0.1.4-3.fc40
Old package:  bootc-0.1.4-2.fc40
Summary:  Bootable container system
RPMs: bootc
Size: 7.32 MiB
Size change:  12.19 KiB
Changelog:
  * Mon Dec 11 2023 Colin Walters  - 0.1.4-3
  - ExcludeArch: %{ix86}


Package:  cbmc-5.95.1-1.fc40
Old package:  cbmc-5.50.0-6.fc39
Summary:  Bounded Model Checker for ANSI-C and C++ programs
RPMs: cbmc cbmc-doc cbmc-utils
Size: 271.74 MiB
Size change:  54.60 MiB
Changelog:
  * Tue Nov 21 2023 Luk Zaoral  - 5.95.1-1
  - Update to 5.95.1 (rhbz#2239079)


Package:  composer-2.6.6-1.fc40
Old package:  composer

Creation of new package repo failed, Invalid or expired token

[Felix Wang]

I opened an releng issue about this. [1] At the time of writing, I noticed that 
there is probably an similar issue of failure of package creation appeared. [2] 
Hope anyone can help me solve the problem, which maybe the cause of my personal 
issue, or other factors. Thanks in advance.

[1] https://pagure.io/releng/issue/11829
[2] https://pagure.io/releng/fedora-scm-requests/issue/58752
--
___
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

[Heads up]: biosig4c++ 2.5.2 coming to rawhide

[Sandro]

In one week (2023-12-19) or a little later I will update biosig4c++ to 
version 2.5.2 in rawhide. This will bring an soname bump. However, there 
are no consuming packages, making this a self contained change.


Cheers,

--
Sandro
FAS: gui1ty
IRC: Penguinpee
Elsewhere: [Pp]enguinpee
--
___
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: Making -Wmissing-include-dirs an error?

[Florian Weimer]

* Jonathan Wakely:

>> Missing an include directory isn't necessarily the problem though, it
>> is the missing headers that aren't present when they are included
>> that would be - and that should trigger a build error for the missing
>> file. What advantage does failing on this warning provide that the
>> failure on the include file missing doesn't?
>
> Typically, yes, I'd expect a failure. But it's possible for code to do:
>
> #if __has_include()
> # include 
> // use features in that header
> #else
> // roll your own inferior version
> #endif

I can see this might be a problem.

I wouldn't object if someone submitted a change proposal for this, but
they have to do the necessary work (full distribution rebuild to assess
the impact of the change, preferably with an instrumented/wrapped
toolchain to catch silently miscompiled autoconf probes).

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