Re: Summary/Minutes from today's FESCo Meeting (2025-08-19)

On Tue, Aug 19, 2025 at 08:38:01PM +0200, Peter Boy Uni wrote: > > > > Am 19.08.2025 um 19:48 schrieb Zbigniew Jędrzejewski-Szmek > > : > > > > …. > > > > (Here we discussed the forge migration. tl;dr: we're getting > > close and FESCo could migrate in a week or two.) > > Do not such exclus

Re: py3_* macros deprecation and generated setup.py

I see, /usr/lib/rpm/redhat/pyproject_buildrequires.py really expects the project files already generated. Perhaps, the macros should allow some argument to tell it to "not run the detection logic, and just do its best for the kind of project" and let the maintainer define the additional build

Re: py3_* macros deprecation and generated setup.py

It definitely feels like the current macros didn't take into account these scenarios from the usability standpoint, which appears to be common. It requires the maintainer to workaround the detection logic and write counter intuitive code. Right now it is setup.py.in, but eventually could be pyp

Re: Review Request - new dependency of phosh-mobile-settings

On Sat, Aug 16 2025 at 16:57:07 -04:00:00, Neal Gompa wrote: Hey, phosh-mobile-settings gained new dependency on its v0.49.0 release, the dependency is called libcellbroadcastd. I packaged it and opened review request: I would apprec

Re: py3_* macros deprecation and generated setup.py

On 19. 08. 25 20:42, Michael J Gruber wrote: Miro Hrončok venit, vidit, dixit 2025-08-19 17:09:13: On 19. 08. 25 16:33, Carlos Rodriguez-Fernandez wrote: So, basically, don't use the following macros but write the BuildRequires? %generate_buildrequires %pyproject_buildrequires No, yo

Re: py3_* macros deprecation and generated setup.py

Miro Hrončok venit, vidit, dixit 2025-08-19 17:09:13: > On 19. 08. 25 16:33, Carlos Rodriguez-Fernandez wrote: > > So, basically, don't use the following macros but write the BuildRequires? > > > >%generate_buildrequires > >%pyproject_buildrequires > > No, you MUST use them. But ideally u

Re: Summary/Minutes from today's FESCo Meeting (2025-08-19)

> Am 19.08.2025 um 19:48 schrieb Zbigniew Jędrzejewski-Szmek > : > > …. > > (Here we discussed the forge migration. tl;dr: we're getting > close and FESCo could migrate in a week or two.) Do not such exclusive groups as Council and FESCo also have the opportunity to migrate soon (e.g., Ser

Summary/Minutes from today's FESCo Meeting (2025-08-19)

Text Log: https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-08-19/fesco.2025-08-19-17.00.log.txt HTML Log: https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-08-19/fesco.2025-08-19-17.00.log.html Text Minutes: https://meetbot.fedoraproject.org/meeting_m

Re: Rawhide: Heads Up: nfs-utils Being Refactored

On Thu, Aug 14, 2025 at 11:29:04AM -0400, Steve Dickson wrote: > Hello, > > I just wanted to give a heads up that > nfs-utils (in the near future) will be broken > up into the following sub packages with > new dependencies. Rawhide Only! > > * nfs-common-utils - Common utilities for both ser

Re: Summary/Minutes from today's FESCo Meeting (2025-08-12)

On Thu, Aug 14, 2025 at 10:11:54AM +0200, Vít Ondruch wrote: > > I know I can and after all I did, but isn't the purpose of email with > subject "summary" to provide summary? > > I have also seen some followup discussions kicked of due to this, so maybe > "ACTION" could mention here that no appro

Re: No emails for package updates

On Thu, Aug 14, 2025 at 01:17:55AM +0200, Michal Schorm wrote: > You should be able to set up theme here again: > https://notifications.fedoraproject.org/ > > And if I recall correctly, they were globally disabled for everyone > some time ago (a year? or two?), as a part of general cleanup of the

Re: py3_* macros deprecation and generated setup.py

On 19. 08. 25 16:33, Carlos Rodriguez-Fernandez wrote: So, basically, don't use the following macros but write the BuildRequires? %generate_buildrequires %pyproject_buildrequires No, you MUST use them. But ideally use them after *some* setup.py is generated. Either use setup.py.in as a

Re: py3_* macros deprecation and generated setup.py

So, basically, don't use the following macros but write the BuildRequires? %generate_buildrequires %pyproject_buildrequires The two packages I have attempted to migrate are libdnet[1] and strongswan[2] [1] https://src.fedoraproject.org/rpms/libdnet [2] https://src.fedoraproject.org/rpm

Schedule for Tuesday's FESCo Meeting (2025-08-19)

Following is the list of topics that will be discussed in the FESCo meeting Tuesday at 17:00 UTC in #meeting:fedoraproject.org on Matrix. To convert UTC to your local time, take a look at http://fedoraproject.org/wiki/UTCHowto or run: date -d '2025-08-19 17:00 UTC' Links to all issues to be

Re: Any package using systemd service for upgrade tasks?

On Tue, Jul 29, 2025 at 10:16:24AM +0100, Barry Scott wrote: > > > > On 29 Jul 2025, at 09:53, Neal Gompa wrote: > > > > Delayed execution of scriptlets by migrating them to systemd units > > also creates problems because it de-links the execution from the > > transaction. This means that the r

Inactive packagers for F43 cycle

In accordance with FESCo's Inactive Packager Policy[1], packagers that have been identified as inactive have a ticket in the find-inactive-packagers repo[2]. One week after the final release, packagers who remain inactive will be removed from the packager group. (Note that pagure.io is one of th

Re: py3_* macros deprecation and generated setup.py

On 19. 08. 25 7:52, Carlos Rodriguez-Fernandez wrote: Hi all, There are two packages I maintain from different upstream developers that the setup.py is generated during the build, so they are setup.py.in. However, the new buildrequires macros [1] are expecting the setup.py to already exist, or

Fedora 43 compose report: 20250819.n.0 changes

OLD: Fedora-43-20250818.n.0 NEW: Fedora-43-20250819.n.0 = SUMMARY = Added images:1 Dropped images: 0 Added packages: 2 Dropped packages:9 Upgraded packages: 144 Downgraded packages: 0 Size of added packages: 98.23 KiB Size of dropped packages:25.12 MiB

Re: What to do if VPN connection is broken in Fedora 43

Yes if you use capath= instead of ca=. Tom On 19/08/2025 08:42, Dmitry Belyavskiy wrote: Does OpenVPN support CADir format? On Mon, Aug 18, 2025 at 6:32 PM Michael Catanzaro > wrote: Hi, after upgrading to Fedora 43 I noticed my OpenVPN connection was br

Fedora rawhide compose report: 20250819.n.0 changes

OLD: Fedora-Rawhide-20250818.n.0 NEW: Fedora-Rawhide-20250819.n.0 = SUMMARY = Added images:0 Dropped images: 0 Added packages: 4 Dropped packages:9 Upgraded packages: 157 Downgraded packages: 0 Size of added packages: 45.77 MiB Size of dropped packages

Re: What to do if VPN connection is broken in Fedora 43

Does OpenVPN support CADir format? On Mon, Aug 18, 2025 at 6:32 PM Michael Catanzaro wrote: > Hi, after upgrading to Fedora 43 I noticed my OpenVPN connection was > broken due to > https://fedoraproject.org/wiki/Changes/droppingOfCertPemFile > > I see in my journal: > > nm-openvpn[32218]: DEPREC