Re: Feedback wanted for a proposed improvement to RPM's ELF dependency generator

[Gordon Messmer]

On  2023-02-17 20:14, John Reiser wrote:

On 2023-02-18 @ 03:03 UTC, Gordon Messmer wrote:
use libtool-style versions collected from library filenames to provide 
versioned library requirements


How does this affect the output from  "readelf --symbols --version-info 
foo.o"
which displays symbols and symbol versions?  How much more space is 
required

in an ET_REL file?


This feature wouldn't change the contents of any ELF files, it just 
improves the rpm dependencies, e.g "Provides: libnghttp2.so.14()(64bit) 
= 14.24.1" and "Requires: libnghttp2.so.14()(64bit) >= 14.24.1"


Packages built on a system where the _elf_require_fallback_versions 
macro was enabled would not be usable on a system that was built 
without the _elf_provide_fallback_versions macro enabled.
Packages built on a system without the _elf_provide_fallback_versions 
could not be used on Fedora as replacements or alternatives to Fedora 
dependencies, after the _elf_require_fallback_versions macro was 
enabled in Fedora. 


That sounds to me like "not compatible in any way."  That is, any 
attempt at using

both old packages and new packages together, will fail.  I don't like that.
That means that nobody can interact with Fedora packages unless they adopt
the proposed change; and that is very unfriendly.


It's not quite like that.  Fedora packages will both provide and require 
versioned libraries.


Old leaf packages and third-party leaf packages that don't adopt the new 
feature would still be usable with their Fedora dependencies, since they 
wouldn't have versioned Requirements that would create any conflict.


The point where compatibility becomes an issue is the use of old 
packages or third-party packages that don't Provide versioned virtual 
packages to fulfill the requirements of Fedora packages.  Because Fedora 
package dependencies must be fulfilled entirely by other Fedora packages 
as a matter of policy, this potential incompatibility really only 
affects packages that are intended to replace a Fedora package.  Those 
would need to be built with the improved ELF dependency generator in 
order to satisfy the requirements of Fedora packages.

___
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: Feedback wanted for a proposed improvement to RPM's ELF dependency generator

[John Reiser]

On 2023-02-18 @ 03:03 UTC, Gordon Messmer wrote:

use libtool-style versions collected from library filenames to provide 
versioned library requirements


How does this affect the output from  "readelf --symbols --version-info foo.o"
which displays symbols and symbol versions?  How much more space is required
in an ET_REL file?  Suppose there is an .rpm package 
"hello_world-1.0.f40.x86_64.rpm"
for   printf("Hello world!\n")  which delivers an ET_DYN main program and an 
ET_DYN .so
shared library.  Please show explicitly the literal differences in 
corresponding files
(.spec, .rpm, .so, a.elf, .o) before and after implementing the proposed 
improvement.


Packages built on a system where the _elf_require_fallback_versions macro was 
enabled would not be usable on a system that was built without the 
_elf_provide_fallback_versions macro enabled.
Packages built on a system without the _elf_provide_fallback_versions could not be used on Fedora as replacements or alternatives to Fedora dependencies, after the _elf_require_fallback_versions macro was enabled in Fedora. 


That sounds to me like "not compatible in any way."  That is, any attempt at 
using
both old packages and new packages together, will fail.  I don't like that.
That means that nobody can interact with Fedora packages unless they adopt
the proposed change; and that is very unfriendly.
___
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

Feedback wanted for a proposed improvement to RPM's ELF dependency generator

[Gordon Messmer]

Following a recent thread discussing a reproducible failure caused by 
mismatched library interfaces, I proposed a change to the RPM ELF 
dependency generator.  After discussion in the PR, I've provided an 
implementation suggested by keszybz@ which would use libtool-style 
versions collected from library filenames to provide versioned library 
requirements.  Before merging that feature, RPM's maintainers are 
interested in feedback from a wider audience.


Links to the earlier thread and to the PR, as well as details in the 
form of a mostly-complete change proposal in wiki format follow:


https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/WE5UTPZ6EIMTSNUX6ILODAHRYNH6J6TM/

https://github.com/rpm-software-management/rpm/pull/2372


= Enable RPM's fallback version generator for ELF dependencies =

{{Change_Proposal_Banner}}

== Summary ==

This change will, over the course of two releases, enable a new feature 
in RPM's dependency generator which provides a version number for ELF 
shared objects which provide a libtool-style version, but don't provide 
versioned symbols.  This additional information may cause dependencies 
to update when a package that depends on them is installed or updated.


== Detailed Description ==

The current ELF dependency generator examines ELF binaries and prints a 
list of virtual packages that represent the libraries required in order 
to run the binary.  For libraries that use versioned symbols, the 
dependency generator provides information about the symbol versions 
required, ensuring that all of the required interfaces are present in 
dependencies during package installation.  However, for libraries that 
do not provide versioned symbols, the resulting dependencies express 
effectively only the major version of the interface.  That limitation 
can result in rpm installing a package set that meets all of the rpm 
dependencies of each package, but attempts to run the installed binaries 
will fail.


For example, Fedora 37 was released with libnghttp2-1.49.0, and later 
updated to libnghttp2-1.51.0.  The latter release introduced a new 
interface and increased its libtool version appropriately. After that 
update, libsoup3 was rebuilt, and gained a dependency on the new 
interface.  However, because the soname was the same, rpm had no way to 
represent the new dependency, so both the old and new build of libsoup3 
required "libnghttp2.so.14()(64bit)". One way this could cause a 
reproducible failure is to construct a system from the Fedora 37 release 
media (or start a Fedora 37 container).  libnghttp2 is installed by 
default, as a dependency of curl, but libsoup3 is not.  If you then 
install any package that uses libsoup3 (e.g. chezdav), the binaries 
provided by that package will fail to start, because the runtime linker 
cannot resolve all symbols.


The curl package appears to have had this problem more than once, and 
addresses it by querying the package version of selected dependencies 
and creating additional dependency statements based on their package 
version.  However, the versioned dependency on libnghttp2 was added 
after the release of Fedora 37.


Another failure case, and one that affected real users, was to install 
Fedora 37 Workstation and enable the node14 modular repo. That repo 
provided a build of libnghttp2 of its own which wasn't updated when 
Fedora updated its primary libnghttp2 package to 1.51.0.  Because 
modular repos filter their package sets out of other repos, updating the 
system as a whole would not update libnghttp2, but would update 
libsoup3.  That update would break gdm, leaving users unable to log in 
to the graphical interface.


This change would make manual, selected versioned dependencies 
unnecessary by generating them automatically for any package that 
provides libtool-style versioned shared objects.  (Though, again, 
objects that provide versioned symbols are excluded, because versioned 
symbols are already handled properly, and are the preferred mechanism.)


== Feedback ==

== Benefit to Fedora ==

This change will make package updates and installation more reliable, 
reducing the risk that selectively installing an update (as in the case 
of users who use "dnf update --security") or installing a single new 
package will result in binaries that do not work.  It will also make the 
use of modular repos more reliable, by preventing packages from updating 
if one of their dependencies is likely to lack symbols needed by 
packages which are not provided by a modular repo.


== Scope ==

* Proposal owners:

In order to complete this change, the "_elf_provide_fallback_versions" 
macro must be enabled, and all packages must be rebuilt in order to 
"provide" versioned libraries.  In a subsequent release, the 
"_elf_require_fallback_versions" macro must be enabled, and all packages 
must be rebuilt in order to "require" versioned libraries.


* Other developers:

Other developers are not expected to 

[Bug 2169950] perl-Date-Holidays-DE-2.06 is available

[bugzilla]

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



--- Comment #4 from Fedora Update System  ---
FEDORA-2023-637174bcd6 has been submitted as an update to Fedora 37.
https://bodhi.fedoraproject.org/updates/FEDORA-2023-637174bcd6


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2169950
___
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 2169950] perl-Date-Holidays-DE-2.06 is available

[bugzilla]

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



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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2169950
___
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 2169950] perl-Date-Holidays-DE-2.06 is available

[bugzilla]

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



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


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2169950
___
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 2169950] perl-Date-Holidays-DE-2.06 is available

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|NEW |MODIFIED



--- Comment #1 from Fedora Update System  ---
FEDORA-EPEL-2023-cc9f0663c5 has been submitted as an update to Fedora EPEL 8.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-cc9f0663c5


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2169950
___
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 2168141] Add perl-Cairo to EPEL9

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Resolution|--- |ERRATA
   Fixed In Version||perl-Cairo-1.109-8.el9.1
 Status|ON_QA   |CLOSED
Last Closed||2023-02-18 00:39:17



--- Comment #5 from Fedora Update System  ---
FEDORA-EPEL-2023-526d25e3d7 has been pushed to the Fedora EPEL 9 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=2168141
___
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 2168132] Add perl-Set-IntSpan to EPEL9

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Resolution|--- |ERRATA
 Status|ON_QA   |CLOSED
Last Closed||2023-02-18 00:39:23



--- Comment #5 from Fedora Update System  ---
FEDORA-EPEL-2023-2e88374024 has been pushed to the Fedora EPEL 9 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=2168132
___
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 2125015] perl-Gtk3 EPEL9

[bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=2125015
Bug 2125015 depends on bug 2168141, which changed state.

Bug 2168141 Summary: Add perl-Cairo to EPEL9
https://bugzilla.redhat.com/show_bug.cgi?id=2168141

   What|Removed |Added

 Status|ON_QA   |CLOSED
 Resolution|--- |ERRATA




-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2125015
___
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 2125015] perl-Gtk3 EPEL9

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Resolution|--- |ERRATA
 Status|MODIFIED|CLOSED
   Fixed In Version||perl-Gtk3-0.038-7.el9.1
Last Closed||2023-02-18 00:39:13



--- Comment #8 from Fedora Update System  ---
FEDORA-EPEL-2023-526d25e3d7 has been pushed to the Fedora EPEL 9 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=2125015
___
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: Fedora Linux 38 blocker status summary

[Adam Williamson]

On Fri, 2023-02-17 at 14:45 -0500, Ben Cotton wrote:
> The F38 Beta freeze begins on 21 February. The current target release
> date is the early target date (2023-03-14).
> 
> Action summary
> 
> 
> Accepted blockers
> -
> 
> 1. distribution — Workstation boot x86_64 image exceeds maximum size — 
> ASSIGNED
> ACTION: Workstation WG to reduce image size or increase the limit

This went under the limit for like two days when the linux-firmware
change landed, but then bounced back over it recently. I didn't yet get
time to check out why, too much fire.

> 
> Proposed blockers
> -
> 
> 1. glusterfs — libglusterd0 prevents upgrades to Fedora 38 — NEW
> ACTION: Maintainer to diagnose issue

I actually fixed this a few days ago, we can probably close it. I've
done that.
-- 
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org
https://www.happyassassin.net



___
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 Linux 38 blocker status summary

[Ben Cotton]

The F38 Beta freeze begins on 21 February. The current target release
date is the early target date (2023-03-14).

Action summary


Accepted blockers
-

1. distribution — Workstation boot x86_64 image exceeds maximum size — ASSIGNED
ACTION: Workstation WG to reduce image size or increase the limit

Proposed blockers
-

1. glusterfs — libglusterd0 prevents upgrades to Fedora 38 — NEW
ACTION: Maintainer to diagnose issue

2. kwin — kwin_wayland often crashed when used as the sddm Wayland
compositor and logging out of Plasma resulting in a black screen — NEW
ACTION: Maintainer to diagnose issue


Bug-by-bug detail
=

Accepted blockers
-

1. distribution — https://bugzilla.redhat.com/show_bug.cgi?id=2149246 — ASSIGNED
Workstation boot x86_64 image exceeds maximum size

Changes to linux-firmware briefly brought the Worktation image below
the limit. However, the Fedora-38-20230216.n.0 went above the limit
again.


Proposed blockers
-

1. glusterfs — https://bugzilla.redhat.com/show_bug.cgi?id=2169401 — NEW
libglusterd0 prevents upgrades to Fedora 38

libglusterd0, which is preinstalled in F37 Workstation, is not
provided by anything in the F38 repos, so upgrades fail.

2. kwin — https://bugzilla.redhat.com/show_bug.cgi?id=2168034 — NEW
kwin_wayland often crashed when used as the sddm Wayland compositor
and logging out of Plasma resulting in a black screen

Logging out of Plasma sometimes triggers a kwin crash. This may be
limited to running in a virtual machine.


-- 
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
___
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: Willing to unretire package: rust-starship

[Nico Kadel-Garcia]

On Fri, Feb 17, 2023 at 10:17 AM Maxwell G  wrote:
>
> On Fri Feb 17, 2023 at 08:37 -0500, Nico Kadel-Garcia wrote:
> > On Fri, Feb 17, 2023 at 7:51 AM Andreas Schneider  wrote:
> > > It downloads packages from the internet and doesn't use system rust 
> > > packages.
>
> > ansible-core and awscli also install internal versions of what should
> > be separately published python modules,
>
> To be clear, it's RHEL/CentOS Stream's ansible-core package that does
> this. They include sdists of jinja2, markupsafe (neeeded by jinja2),
> packaging, pyparsing (needed by packaging), and resolvelib in the SRPM
> and build/install them into a special vendor directory that ansible adds
> to sys.path :(. Fedora's ansible-core's package does not do this, and I
> very much am not a fan of the practice.

Also "straightplugin".  I see your name in the %changelog for
ansible-core in Fedora, thanks for your work there. I based my
published SRPM code on Fedora. If you've successfully navigated the
Fedora submission process, which I've never managed, despite a few
attempts. Would you care to help me walk through them? Or can I
feed you the needed .spec files  to get them into EPEL and possibly
help clean up the RHEL backports? I've some significant speedups and
improvements for the "ansible" package, as well, and I see your name
in the %changelog for that as well.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

[Test-Announce] Fedora-IoT 38 RC 20230217.2 nightly compose nominated for testing

[rawhide]

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

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

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

https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_38_RC_20230217.2_Summary

The individual test result pages are:

https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_38_RC_20230217.2_General

Thank you for testing!
-- 
Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer
___
test-announce mailing list -- test-annou...@lists.fedoraproject.org
To unsubscribe send an email to test-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/test-annou...@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Upcoming libcmocka 1.1.6 update requires fixing packages using cmake

[Andreas Schneider]

Hi,

I would like to update libcmocka [1] to version 1.1.6. This autogenerates the 
find_package() files for CONFIG mode now.

This means the projects which don't have their on FindCMocka.cmake module but 
rely on the CONFIG mode, need 3 lines of code to still compile with 1.1.6. You 
need to add the following code after find_package(cmocka):

if (TARGET cmocka::cmocka)
  set(CMOCKA_LIBRARY cmocka::cmocka)
endif()

I did some repoquery and the following packages which use cmake and libcmocka 
might need fixing:

drpm
freecell-solver
libavtp
libssh (maintained by me)
libyang
netdata
nss_wrapper (maintained by me)
openscap
pam_wrapper (maintained by me)
priv_wrapper (maintained by me)
resolv_wrapper (maintained by me)
socket_wrapper (maintained by me)
sysrepo
termy-server
uid_wrapper (maintained by me)


I will try to look into them in the next weeks, but if you're the maintainer 
of the package and read this I would appreciate if you could fix it.

Thanks!


Best regards


Andreas


[1] https://cmocka.org/

___
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: Inactive packager check for F38

[Ben Cotton]

On Fri, Feb 17, 2023 at 1:48 AM Mattia Verga via devel
 wrote:
>
> During the weekend I can write down a script reusing partial code from
> the find_inactive_packagers script and purge the ticket list from users
> that showed activity in RH bugzilla, let me know if you want me to
> proceed. Or I can provide a list of users, but I think that will be a
> long list for manual processing...

People who were active in Bugzilla will get noticed on the step-two
run and not removed, so I don't think it's necessary to go through and
clean those up now unless you really want to.

-- 
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
___
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

[rpms/perl-Coro] PR #4: Fedora don't support arm32, we could use fortify for all architectures

[Michal Josef Špaček]

mspacek merged a pull-request against the project: `perl-Coro` that you are 
following.

Merged pull-request:

``
Fedora don't support arm32, we could use fortify for all architectures
``

https://src.fedoraproject.org/rpms/perl-Coro/pull-request/4
___
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

[rpms/perl-Coro] PR #4: Fedora don't support arm32, we could use fortify for all architectures

[Michal Josef Špaček]

mspacek opened a new pull-request against the project: `perl-Coro` that you are 
following:
``
Fedora don't support arm32, we could use fortify for all architectures
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Coro/pull-request/4
___
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: Willing to unretire package: rust-starship

[Maxwell G]

On Fri Feb 17, 2023 at 08:37 -0500, Nico Kadel-Garcia wrote:
> On Fri, Feb 17, 2023 at 7:51 AM Andreas Schneider  wrote:
> > It downloads packages from the internet and doesn't use system rust 
> > packages.

> ansible-core and awscli also install internal versions of what should
> be separately published python modules,

To be clear, it's RHEL/CentOS Stream's ansible-core package that does
this. They include sdists of jinja2, markupsafe (neeeded by jinja2),
packaging, pyparsing (needed by packaging), and resolvelib in the SRPM
and build/install them into a special vendor directory that ansible adds
to sys.path :(. Fedora's ansible-core's package does not do this, and I
very much am not a fan of the practice.


--
Maxwell G (@gotmax23)
Pronouns: He/They


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: Fedora 38 mass rebuild is finished

[Miro Hrončok]

On 07. 02. 23 15:12, Miro Hrončok wrote:

On 23. 01. 23 17:44, Tomas Hrcka wrote:

FTBFS bugs will be filed shortly.


Is there an estimated date when this will happen?


There is now a ticket with the same question:

https://pagure.io/releng/issue/11295

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

Packaging python3-*-devel subpackages

[Miro Hrončok]

Hello Pythonistats and packaging folks.

Tomáš (CCed) approached me today with an interesting question.
A Python package he is packaging into RPM (python3-rapidfuzz) installs some 
development files (.h and .pxd).


Tomáš queried upstream about those files to figure out if they should be 
installed or if they are only needed to build the package itself. Upstream 
responded:


> rapidfuzz.h and __init__.pxd provide a capi for rapidfuzz, which allows users
> to write their own similarity metrics in C/C++/Cython, which can be called by
> rapidfuzz in a more performant way through this C-API.
> For this reason the header file should be part of the installation as well.

OK, we want to ship them. Our packaging guidelines however say:

https://docs.fedoraproject.org/en-US/packaging-guidelines/#_devel_packages

> Specifically, -devel packages must be used to contain files which are
> intended solely for development or needed only at build-time. This is done to
> minimize the install footprint for users. There are some types of files which
> almost always belong in a -devel package:
>  - Header files...

So from our guidelines perspective, the files would go to 
python3-rapidfuzz-devel. The way we packaged Python in 201x, this would be the 
end of it.


However, in this decade with automatic Python BuildRequires, we could easily 
end up in this situation:


 1. a Python package lists rapidfuzz as a build requirement
 2. %pyproject_buildrequires generates a dependency on python3dist(rapidfuzz)
 3. only python3-rapidfuzz is pulled
 4. %build wants to use rapidfuzz.h
 5. packager needs to manually BuildRequire python3-rapidfuzz-devel

To avoid (5), my suggestion was to add the following requirement to 
python3-rapidfuzz:


  Requires: (python3-rapidfuzz-devel%{?_isa} =
 %{?epoch:%{epoch}:}%{version}-%{release} if python3-devel)

That way, application packages that pull in pytohn3-rapidfuzz as a runtime 
dependency won't get it (we are minimizing the install footprint for users), 
but users who build stuff (including RPM packages) will get it (we make 
automatically generated dependencies work as intended).


(Of course, users who have python3-devel installed for reasons other than 
rapidfuxx will still get the files, but the assumption here is that users who 
install -devel packages intent to /generally/ build stuff.)


Is that a good suggestion? And if so, should it be a general recommendation for 
such cases?


--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-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/python-devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Intending to unretire arptools

[Artur Frenszek-Iwicki]

Hi all,

I intend to un-retire arptools, which is a small collection of Ethernet ARP 
tools.
The package used to be in Fedora repos, but was retired somewhere between F31 
and F32 due to being orphaned.
https://src.fedoraproject.org/rpms/arptools

I looked through the devel list, but couldn't find any info regarding *why* 
it's been orphaned;
either way, it builds and works fine on my machine.

In case anyone's in the mood for a package review, here's the link:
https://bugzilla.redhat.com/show_bug.cgi?id=2170875

I can review some C / C++ / Pascal / PHP / shell stuff in exchange.

A.FI.
___
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: Willing to unretire package: rust-starship

[Nico Kadel-Garcia]

On Fri, Feb 17, 2023 at 7:51 AM Andreas Schneider  wrote:
>
> On Wednesday, 30 November 2022 18:43:50 CET Mauricio Teixeira wrote:
> > Fabio,
>
> Hi Fabio,
>
> > What is so bad about the COPR package that can't be used in the main repo?
>
> It downloads packages from the internet and doesn't use system rust packages.

There are a lot of tools that do this. I just noticed that the
docker-ce SRPMs over at www.docker.com do this. ansible-core and
awscli also install internal versions of what should be separately
published python modules, it's an ongoing issue, and one of the
reasons to build things in "mock" or "koji" to prevent just that sort
of reaching out to thard party web sites during package compilation.
It's just the sort of off-site requirement that broke nodejs for a
*lot* of people for a while,
___
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: Willing to unretire package: rust-starship

[Andreas Schneider]

On Wednesday, 30 November 2022 18:43:50 CET Mauricio Teixeira wrote:
> Fabio,

Hi Fabio,

> What is so bad about the COPR package that can't be used in the main repo?

It downloads packages from the internet and doesn't use system rust packages.

___
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 38 compose report: 20230217.n.0 changes

[Fedora Rawhide Report]

OLD: Fedora-38-20230216.n.1
NEW: Fedora-38-20230217.n.0

= SUMMARY =
Added images:2
Dropped images:  3
Added packages:  2
Dropped packages:0
Upgraded packages:   19
Downgraded packages: 0

Size of added packages:  10.63 MiB
Size of dropped packages:0 B
Size of upgraded packages:   206.40 MiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   371.63 KiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =
Image: Cloud_Base raw-xz ppc64le
Path: Cloud/ppc64le/images/Fedora-Cloud-Base-38-20230217.n.0.ppc64le.raw.xz
Image: Cloud_Base qcow2 ppc64le
Path: Cloud/ppc64le/images/Fedora-Cloud-Base-38-20230217.n.0.ppc64le.qcow2

= DROPPED IMAGES =
Image: Phosh raw-xz aarch64
Path: Spins/aarch64/images/Fedora-Phosh-38-20230216.n.1.aarch64.raw.xz
Image: LXQt raw-xz aarch64
Path: Spins/aarch64/images/Fedora-LXQt-38-20230216.n.1.aarch64.raw.xz
Image: Silverblue dvd-ostree ppc64le
Path: 
Silverblue/ppc64le/iso/Fedora-Silverblue-ostree-ppc64le-38-20230216.n.1.iso

= ADDED PACKAGES =
Package: libdisplay-info-0.1.1-1.fc38
Summary: EDID and DisplayID library
RPMs:libdisplay-info libdisplay-info-devel libdisplay-info-tools
Size:636.35 KiB

Package: moarvm-2022.12-1.fc38
Summary: Metamodel On A Runtime Virtual Machine
RPMs:moarvm moarvm-devel
Size:10.01 MiB


= DROPPED PACKAGES =

= UPGRADED PACKAGES =
Package:  apachetop-0.23.2-1.fc38
Old package:  apachetop-0.19.7-9.fc38
Summary:  Top-like display of Apache logs
RPMs: apachetop
Size: 160.06 KiB
Size change:  3.96 KiB
Changelog:
  * Fri Feb 17 2023 Robert Scheck  - 0.23.2-1
  - Upgrade to 0.23.2
  - Switch from deprecated pcre to pcre2 (#2128271)


Package:  cinnamon-5.6.7-1.fc38
Old package:  cinnamon-5.6.5-2.fc38
Summary:  Window management and application launching for GNOME
RPMs: cinnamon cinnamon-calendar-server cinnamon-devel-doc
Size: 9.31 MiB
Size change:  -15.41 KiB
Changelog:
  * Thu Feb 16 2023 Leigh Scott  - 5.6.7-1
  - Update to 5.6.7 release


Package:  editorconfig-0.12.6-1.fc38
Old package:  editorconfig-0.12.5-5.fc38
Summary:  Parser for EditorConfig files written in C
RPMs: editorconfig editorconfig-devel editorconfig-libs
Size: 296.49 KiB
Size change:  4.36 KiB
Changelog:
  * Sun Jan 22 2023 Benjamin A. Beasley  - 0.12.6-1
  - Update to 0.12.6 (close RHBZ#2162811)
  - Update License to SPDX
  - Document and/or unbundle all bundled libraries


Package:  libgpiod-2.0-0.3.rc2.fc38
Old package:  libgpiod-2.0-0.2.rc1.fc38
Summary:  C library and tools for interacting with linux GPIO char device
RPMs: libgpiod libgpiod-c++ libgpiod-devel libgpiod-utils 
python3-libgpiod
Size: 1.02 MiB
Size change:  1.88 KiB
Changelog:
  * Thu Feb 16 2023 Peter Robinson  - 2.0-0.3.rc2
  - libgpiod 2.0 RC2


Package:  libldb-2.7.1-1.fc38
Old package:  libldb-2.7.0-2.fc38
Summary:  A schema-less, ldap like, API and database
RPMs: ldb-tools libldb libldb-devel python-ldb-devel-common python3-ldb 
python3-ldb-devel
Size: 1.90 MiB
Size change:  -765 B
Changelog:
  * Thu Feb 16 2023 Guenther Deschner  - 2.7.1-1
  - rhbz#2167440 - libldb-2.7.1 is available


Package:  libtevent-0.14.1-1.fc38
Old package:  libtevent-0.14.0-1.fc38
Summary:  The tevent library
RPMs: libtevent libtevent-devel python3-tevent
Size: 601.35 KiB
Size change:  -112 B
Changelog:
  * Thu Feb 16 2023 Guenther Deschner  - 0.14.1-1
  - rhbz#2166867 - libtevent-0.14.1 is available


Package:  lorax-38.6-3.fc38
Old package:  lorax-38.6-2.fc38
Summary:  Tool for creating the anaconda install images
RPMs: lorax lorax-docs lorax-lmc-novirt lorax-lmc-virt 
lorax-templates-generic
Size: 2.51 MiB
Size change:  1.94 KiB
Changelog:
  * Thu Feb 16 2023 Adam Williamson  - 38.6-3
  - Backport PR #1310 to disable persistence again, it's busted (#2170544)


Package:  m1n1-1.2.4-1.fc38
Old package:  m1n1-1.2.3-3.fc38
Summary:  Bootloader and experimentation playground for Apple Silicon
RPMs: m1n1 m1n1-tools
Size: 922.46 KiB
Size change:  13.50 KiB
Changelog:
  * Thu Feb 16 2023 Davide Cavalca  - 1.2.4-1
  - Update to 1.2.4; Fixes: RHBZ#2164030


Package:  magic-8.3.366-1.fc38
Old package:  magic-8.3.365-1.fc38
Summary:  A very capable VLSI layout tool
RPMs: magic magic-doc
Size: 7.96 MiB
Size change:  -716 B
Changelog:
  * Fri Feb 17 2023 Mamoru TASAKA  - 8.3.366-1
  - 8.3.366


Package:  ovn-22.12.0-25.fc38
Old package:  ovn-22.12.0-1.fc38
Summary:  Open Virtual Network support
RPMs: ovn ovn-central ovn-host ovn-vtep
Size: 10.81 MiB
Size change:  15.63 KiB
Changelog:
  * Thu Feb 16 2023 Numan Siddique  - 22.12.0-25
  - Sync to upstream OVN branch-22.12. Below are the commits
  since last update (22.12.0-1)
  
  - lb: northd: Properly format IPv6 SB load balancer VIPs.
  [Upstream

Fedora rawhide compose report: 20230217.n.1 changes

[Fedora Rawhide Report]

OLD: Fedora-Rawhide-20230216.n.3
NEW: Fedora-Rawhide-20230217.n.1

= SUMMARY =
Added images:3
Dropped images:  1
Added packages:  3
Dropped packages:0
Upgraded packages:   32
Downgraded packages: 0

Size of added packages:  16.91 MiB
Size of dropped packages:0 B
Size of upgraded packages:   101.74 MiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   334.65 KiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =
Image: Budgie live x86_64
Path: Spins/x86_64/iso/Fedora-Budgie-Live-x86_64-Rawhide-20230217.n.1.iso
Image: KDE raw-xz aarch64
Path: Spins/aarch64/images/Fedora-KDE-Rawhide-20230217.n.1.aarch64.raw.xz
Image: Container_Minimal_Base docker aarch64
Path: 
Container/aarch64/images/Fedora-Container-Minimal-Base-Rawhide-20230217.n.1.aarch64.tar.xz

= DROPPED IMAGES =
Image: Xfce raw-xz aarch64
Path: Spins/aarch64/images/Fedora-Xfce-Rawhide-20230216.n.3.aarch64.raw.xz

= ADDED PACKAGES =
Package: swig-4.1.1-4.module_f39+16108+738602b3
Summary: Connects C/C++/Objective C to some high-level programming languages
RPMs:ccache-swig swig swig-doc swig-gdb
Size:10.12 MiB

Package: varnish-6.0.11-1.module_f39+16117+8adad8d8
Summary: High-performance HTTP accelerator
RPMs:varnish varnish-devel varnish-docs
Size:6.47 MiB

Package: varnish-modules-0.15.0-13.module_f39+16117+8adad8d8
Summary: A collection of modules ("vmods") extending Varnish VCL
RPMs:varnish-modules
Size:329.86 KiB


= DROPPED PACKAGES =

= UPGRADED PACKAGES =
Package:  apachetop-0.23.2-1.fc39
Old package:  apachetop-0.19.7-9.fc38
Summary:  Top-like display of Apache logs
RPMs: apachetop
Size: 160.07 KiB
Size change:  3.98 KiB
Changelog:
  * Fri Feb 17 2023 Robert Scheck  - 0.23.2-1
  - Upgrade to 0.23.2
  - Switch from deprecated pcre to pcre2 (#2128271)


Package:  apiguardian-1.1.2-6.fc39
Old package:  apiguardian-1.1.2-5.fc38
Summary:  API Guardian Java annotation
RPMs: apiguardian apiguardian-javadoc
Size: 107.29 KiB
Size change:  2.18 KiB
Changelog:
  * Wed Feb 15 2023 Marian Koncek  - 1.1.2-6
  - Build with module-info


Package:  awscli-1.27.73-1.fc39
Old package:  awscli-1.27.72-1.fc39
Summary:  Universal Command Line Environment for AWS
RPMs: awscli
Size: 3.28 MiB
Size change:  479 B
Changelog:
  * Thu Feb 16 2023 Gwyn Ciesla  - 1.27.73-1
  - 1.27.73


Package:  budgie-desktop-10.7-2.fc39
Old package:  budgie-desktop-10.7-1.fc38
Summary:  A feature-rich, modern desktop designed to keep out the way of 
the user
RPMs: budgie-desktop budgie-desktop-devel budgie-desktop-docs
Size: 12.78 MiB
Size change:  -29.97 KiB
Changelog:
  * Thu Feb 16 2023 Joshua Strobl  - 10.7-2
  - Add preliminary mutter 12 ABI support patch


Package:  cargo2rpm-0.1.2-1.fc39
Old package:  cargo2rpm-0.1.1-2.fc39
Summary:  Translation layer between cargo and RPM
RPMs: cargo2rpm
Size: 84.90 KiB
Size change:  495 B
Changelog:
  * Thu Feb 16 2023 Fabio Valentini  - 0.1.2-1
  - Update to version 0.1.2


Package:  cinnamon-5.6.7-1.fc39
Old package:  cinnamon-5.6.5-2.fc38
Summary:  Window management and application launching for GNOME
RPMs: cinnamon cinnamon-calendar-server cinnamon-devel-doc
Size: 9.31 MiB
Size change:  -14.85 KiB
Changelog:
  * Thu Feb 16 2023 Leigh Scott  - 5.6.7-1
  - Update to 5.6.7 release


Package:  editorconfig-0.12.6-1.fc39
Old package:  editorconfig-0.12.5-5.fc38
Summary:  Parser for EditorConfig files written in C
RPMs: editorconfig editorconfig-devel editorconfig-libs
Size: 296.57 KiB
Size change:  4.44 KiB
Changelog:
  * Sun Jan 22 2023 Benjamin A. Beasley  - 0.12.6-1
  - Update to 0.12.6 (close RHBZ#2162811)
  - Update License to SPDX
  - Document and/or unbundle all bundled libraries


Package:  lorax-38.6-3.fc39
Old package:  lorax-38.6-2.fc39
Summary:  Tool for creating the anaconda install images
RPMs: lorax lorax-docs lorax-lmc-novirt lorax-lmc-virt 
lorax-templates-generic
Size: 2.51 MiB
Size change:  1.91 KiB
Changelog:
  * Thu Feb 16 2023 Adam Williamson  - 38.6-3
  - Backport PR #1310 to disable persistence again, it's busted (#2170544)


Package:  mock-core-configs-38.2-1.fc39
Old package:  mock-core-configs-38.1-1.fc38
Summary:  Mock core config files basic chroots
RPMs: mock-core-configs
Size: 140.59 KiB
Size change:  -506 B
Changelog:
  * Fri Feb 17 2023 Pavel Raiskup  38.2-1
  - update gpg keys for Tumbleweed (msu...@redhat.com)


Package:  opentest4j-1.2.0-12.fc39
Old package:  opentest4j-1.2.0-12.fc38
Summary:  Open Test Alliance for the JVM
RPMs: opentest4j opentest4j-javadoc
Size: 120.26 KiB
Size change:  16 B

Package:  ovn-22.12.0-25.fc39
Old package:  ovn-22.12.0-1.fc38
Summary:  Open Virtual Network support
RPMs: ovn ovn-central ovn-hos

[Bug 2125015] perl-Gtk3 EPEL9

[bugzilla]

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



--- Comment #7 from Sergio Basto  ---
(In reply to Fedora Update System from comment #6)
> FEDORA-EPEL-2023-24188f7578 has been submitted as an update to Fedora EPEL
> 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-24188f7578

revoked


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2125015
___
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 2125015] perl-Gtk3 EPEL9

[bugzilla]

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

Fedora Update System  changed:

   What|Removed |Added

 Status|ON_QA   |MODIFIED



--- Comment #6 from Fedora Update System  ---
FEDORA-EPEL-2023-24188f7578 has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-24188f7578


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2125015
___
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 2168132] Add perl-Set-IntSpan to EPEL9

[bugzilla]

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

Petr Pisar  changed:

   What|Removed |Added

Product|Fedora  |Fedora EPEL
 CC||ppi...@redhat.com
Version|rawhide |epel9
  Component|perl-Set-IntSpan|perl-Set-IntSpan
 QA Contact|extras...@fedoraproject.org |




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

[Peter Robinson]

On Fri, Feb 17, 2023 at 9:04 AM Petr Pisar  wrote:
>
> V Thu, Feb 16, 2023 at 07:29:07PM +, Kenneth Goldman napsal(a):
> > I think I followed all those steps - identifying the package, announcing 
> > that
> > I want to be the packager, making an account, etc.
> >
> > What's next?
>
> Submit an updated tss2 package for a package review. As far as I can see,
> there is no review opened for tss2 now

It was only retired on Jan 9th so should not need a re-review.

I think the process needs to be:
1) get a package sponsor. If you don't have one I can possibly do it
as I co-maintain the intel tpm2 packages
2) request ownership and unblocking of the package
3) build new versions as follow the process.

> .
> How to do it is described at
> .
> Especially pay attention to:
>
> If you are not member of the packager group, you need a sponsor. Add
> FE-NEEDSPONSOR to the bugs being blocked by your review request.
>
> > Does someone approve me?
>
> Based on the FE-NEEDSPONSOR blocker someone from sponsors should notice your
> review request and start to communicate with you in the review request in
> Bugzilla. (If that does not happen, approach you a sponsor of your choice as
> recommended at
> )
>
> Once the sponsor finds your package looks good and you understand how to
> maintain a package, he/she will sponsor you, i.e. adds you into a packagers
> group. Then you will be able to continue from this item on the
> Package_Review_Process document:
>
> When your package passes the review you should use fedpkg to request a Git
> repository for it.
>
> > Move a git repo somewhere?
>
> For the purpose of the package review, you need to publish the spec file and
> the SRPM file somewhere on the Internet. (Once you become a packager, you can
> also use  server for that purpose.)
>
> Once the package review passes, the offical git repository (called dist-git in
> Fedora) for the tss2 package will be reopened with completing this item:
>
> Request a Git repository for the package
>
> Then you will commit the new spec file into the reopen dist-git repository.
>
> -- Petr
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: TSS maintainer volunteer

[Petr Pisar]

V Thu, Feb 16, 2023 at 07:29:07PM +, Kenneth Goldman napsal(a):
> I think I followed all those steps - identifying the package, announcing that 
> I want to be the packager, making an account, etc.
> 
> What's next?

Submit an updated tss2 package for a package review. As far as I can see,
there is no review opened for tss2 now
.
How to do it is described at
.
Especially pay attention to:

If you are not member of the packager group, you need a sponsor. Add
FE-NEEDSPONSOR to the bugs being blocked by your review request.

> Does someone approve me?

Based on the FE-NEEDSPONSOR blocker someone from sponsors should notice your
review request and start to communicate with you in the review request in
Bugzilla. (If that does not happen, approach you a sponsor of your choice as
recommended at
)

Once the sponsor finds your package looks good and you understand how to
maintain a package, he/she will sponsor you, i.e. adds you into a packagers
group. Then you will be able to continue from this item on the
Package_Review_Process document:

When your package passes the review you should use fedpkg to request a Git
repository for it.

> Move a git repo somewhere?

For the purpose of the package review, you need to publish the spec file and
the SRPM file somewhere on the Internet. (Once you become a packager, you can
also use  server for that purpose.)

Once the package review passes, the offical git repository (called dist-git in
Fedora) for the tss2 package will be reopened with completing this item:

Request a Git repository for the package

Then you will commit the new spec file into the reopen dist-git repository.

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