Fedora 42 compose report: 20250220.n.0 changes

OLD: Fedora-42-20250219.n.0 NEW: Fedora-42-20250220.n.0 = SUMMARY = Added images:0 Dropped images: 0 Added packages: 0 Dropped packages:0 Upgraded packages: 0 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:0 B Size of upgraded

Heads-up: Updating python-aiohttp to 3.11.12 in F43/Rawhide and possibly F42/Branched

In one week, 2025-02-27, I plan to update python-aiohttp from 3.10.11 to 3.11.12 in F43/Rawhide[1]. I impact-checked this update in COPR and found no regressions, but it does have documented breaking changes, so I’m going through the announcement process. I would like to do the same update in

Fedora rawhide compose report: 20250220.n.0 changes

OLD: Fedora-Rawhide-20250219.n.0 NEW: Fedora-Rawhide-20250220.n.0 = SUMMARY = Added images:0 Dropped images: 7 Added packages: 8 Dropped packages:0 Upgraded packages: 115 Downgraded packages: 0 Size of added packages: 12.58 MiB Size of dropped packages:0

Fedora eln compose report: 20250221.n.0 changes

OLD: Fedora-eln-20250220.n.0 NEW: Fedora-eln-20250221.n.0 = SUMMARY = Added images:0 Dropped images: 0 Added packages: 0 Dropped packages:0 Upgraded packages: 2 Downgraded packages: 0 Size of added packages: 0 B Size of dropped packages:0 B Size of

Re: Heads-up: Updating python-aiohttp to 3.11.12 in F43/Rawhide and possibly F42/Branched

Neither python-yarl nor python-uvloop is currently in EPEL10, so these would fall under the normal EPEL package request process, https://docs.fedoraproject.org/en-US/epel/epel-package-request/. I do agree that EPEL10 branching should be based on the latest versions in Rawhide in these cases.

Re: Proposal: Allow all packagers to push empty commits to any package

On 20. 02. 25 14:02, Neal Gompa wrote: On Thu, Feb 20, 2025 at 7:59 AM Miro Hrončok wrote: On 20. 02. 25 13:51, Michael J Gruber wrote: With the wide adoption of %autorelease, such bump commits are empty, which should be easy to verify. Wide, well, ... Roughly 39% based on a simple grep fo

Re: Proposal: Allow all packagers to push empty commits to any package

On 2/20/25 8:02 AM, Neal Gompa wrote: What does that number look like when we exclude rust2rpm managed packages? $ rg -l '%\{?autorelease' | while read -r spec; do if ! grep -Fq 'Generated by rust2rpm' "${spec}"; then echo "${spec}"; fi; done | wc -l 6559 $ find . -name '*.spec' | while rea

Re: Proposal: Allow all packagers to push empty commits to any package

On 20. 02. 25 14:08, Dmitry Belyavskiy wrote: On Thu, Feb 20, 2025 at 1:17 PM Miro Hrončok > wrote: What if we allowed all packagers to push empty commit to any package? That should eliminate *some* need for provenpackager access. We would also communi

soname bump: mupdf 1.25.4 coming to f41

Hi there mupdf 1.25.4 is the latest version from the release branch. It collects several bugfixes but bumps soname as is typical with the way upstreams versions this. We (Ankur Sinha and me) have been going through updates of the girara/zathura/mupdf ecosystem for rawhide and F42 already, all upd

Re: Proposal: Allow all packagers to push empty commits to any package

On Thu, Feb 20, 2025 at 01:17:02PM +0100, Miro Hrončok wrote: > Hello. > > With the recent discussions about provenpackagers in Fedora, I > recently got an idea. > > One of the common needs for provenpackagers is to simply "bump and > rebuild" a set of dependencies. > > All packagers are already

Re: Proposal: Allow all packagers to push empty commits to any package

On 20. 02. 25 13:28, Richard W.M. Jones wrote: On Thu, Feb 20, 2025 at 01:17:02PM +0100, Miro Hrončok wrote: What if we allowed all packagers to push empty commit to any package? That should eliminate *some* need for provenpackager access. We would also communicate in our policies that such bump

Re: Proposal: Allow all packagers to push empty commits to any package

Hello, On Thu, Feb 20, 2025 at 2:27 PM Miro Hrončok wrote: > On 20. 02. 25 14:08, Dmitry Belyavskiy wrote: > > > > > > On Thu, Feb 20, 2025 at 1:17 PM Miro Hrončok > > wrote: > > > > > > What if we allowed all packagers to push empty commit to any > package? That

Re: Orphaning java-diff-utils

As far as I know, java-diff utils can work happily without jgit. Only they will miss one diff algorithm. I had excluded it in past - https://src.fedoraproject.org/rpms/java-diff-utils/c/38304b943ffba9cdb0b83a062b1c95d6c2c2d09e?branch=epel9 Btw I seesm to be owner of that package. So please, do

Re: Proposal: Allow all packagers to push empty commits to any package

On 20. 02. 25 13:51, Michael J Gruber wrote: With the wide adoption of %autorelease, such bump commits are empty, which should be easy to verify. Wide, well, ... Roughly 39% based on a simple grep for %\{?autorelease -- Miro Hrončok -- Phone: +420777974800 Fedora Matrix: mhroncok --

Re: Proposal: Allow all packagers to push empty commits to any package

Note that as long as we’re on Pagure, it’s impossible to make a PR for an empty commit. On 2/20/25 8:51 AM, Cristian Le via devel wrote: On 2025/02/20 13:17, Miro Hrončok wrote: What if we allowed all packagers to push empty commit to any package? That should eliminate *some* need for proven

Re: Proposal: Allow all packagers to push empty commits to any package

On 2025/02/20 14:54, Ben Beasley wrote: Note that as long as we’re on Pagure, it’s impossible to make a PR for an empty commit. Right, that is indeed a nuisance. There is a dirty hack to it [1]: 1. Try to create the PR as normal and be greeted by a disabled "Create Pull Request" 2. Enter de

Re: Proposal: Allow all packagers to push empty commits to any package

I would also point out that incompatible updates are still supposed to be announced a week in advance, with all impacted packages’ maintainers CC’ed or BCC’ed. This allows a week for someone to read their email and speak up about any special circumstances. For updates with more than a handful

Re: copy-jdk-configs

Yes, nothing seems to require it anymore. On 2/20/25 05:22, Jiri Vanek wrote: Right, Orion, may you confirm? I;m quite surprised you hit it, as it was done before f43 forked, and all jdks in f42 got the support already removed. I had also did some builds in koji since that time, and tehy look

Re: Guidelines for packaging icons for other themes?

On 2/20/25 00:49, Miro Hrončok wrote: On 20. 02. 25 3:37, Orion Poplawski wrote: While poking at f3d 3.0.0 I see that it installs: /usr/share/icons/HighContrast/scalable/apps/f3d.svg How are we supposed to handle this?  require highcontrast-icon-theme? I would handle that as a general case:

Re: tree-sitter build broke Emacs

On Wed, Jan 15, 2025 at 2:31 PM Jerry James wrote: > Thank you. Would you please update tree-sitter, emacs, etc. in a side > tag next time? Except you didn't. Emacs is again broken in Rawhide due to a tree-sitter update. Meaning I can't do the work I was planning to do this morning because the

Re: Proposal: Allow all packagers to push empty commits to any package

Il 20/02/25 13:17, Miro Hrončok ha scritto: > Hello. > > With the recent discussions about provenpackagers in Fedora, I recently got an > idea. > > One of the common needs for provenpackagers is to simply "bump and rebuild" a > set of dependencies. > > All packagers are already able to build anythi

Re: Proposal: Allow all packagers to push empty commits to any package

On Thu, Feb 20, 2025 at 01:17:02PM +0100, Miro Hrončok wrote: > Hello. > > With the recent discussions about provenpackagers in Fedora, I recently got > an idea. > > One of the common needs for provenpackagers is to simply "bump and rebuild" > a set of dependencies. I guess this "common need" is

Re: tree-sitter build broke Emacs

On Thu, 20 Feb 2025, Jerry James wrote: Except you didn't. We did. https://bodhi.fedoraproject.org/updates/FEDORA-2025-52be0b6b4f Do you not understand how to use a side tag? It turns out that I did not. Apologies. I'm happy to walk you through the answers to either question if lack of

dnf: terminate called after throwing an instance of 'std::length_error'

Hi all, My CI has been failing for the last 24h with: [ 4/48] Installing fwupd-0:2.0.7-0.1alpha.fc41.x86_64 100% | 39.9 MiB terminate called after throwing an instance of 'std::length_error' what(): basic_string::_M_replace_aux contrib/ci/fedora-test.sh: line 3: 7 Aborted

Re: Proposal: Allow all packagers to push empty commits to any package

On 20. 02. 25 17:59, Mattia Verga via devel wrote: Example: the package maintainer applies changes to the spec file, but doesn't build the package because they're still tweaking it (or just because they're building it in a side tag with other pieces). Now any packager can jump in, trigger an empt

Re: Orphaning java-diff-utils

Hi, Good to hear that it works without jgit, and that you adopted java-diff-utils :) Best, Christiano On 20/02/2025 13:25, Jiri Vanek wrote: As far as I know, java-diff utils can work happily without jgit. Only they will miss one diff algorithm. I had excluded it in past - https://src.fedor

ELN SIG meeting minutes for 20 Feb

Text Log: https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-02-20/eln.2025-02-20-20.00.log.txt HTML Log: https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-02-20/eln.2025-02-20-20.00.log.html Text Minutes: https://meetbot.fedoraproject.org/meeting_matri

Re: Heads-up: Updating python-aiohttp to 3.11.12 in F43/Rawhide and possibly F42/Branched

Hi Ben, I am not maintainer/co-maintainer for any of these packages so I cannot give you any consent. On my side I had submitted the pytho-yarl & python-uvloop upgrades in anticipation of their branching in EPEL 10, as I would need these dependencies (and python-aiohttp) in RHEL 10. So would i

Re: copy-jdk-configs

Right, Orion, may you confirm? I;m quite surprised you hit it, as it was done before f43 forked, and all jdks in f42 got the support already removed. I had also did some builds in koji since that time, and tehy looks corrreclty copy-jdk-configs-free. TY!!! J. On 2/5/25 2:52 PM, Mikolaj Izdeb

Re: Proposal: Allow all packagers to push empty commits to any package

Am Do., 20. Feb. 2025 um 13:28 Uhr schrieb Richard W.M. Jones : > > On Thu, Feb 20, 2025 at 01:17:02PM +0100, Miro Hrončok wrote: > > Hello. > > > > With the recent discussions about provenpackagers in Fedora, I > > recently got an idea. > > > > One of the common needs for provenpackagers is to sim

Re: Proposal: Allow all packagers to push empty commits to any package

On Thu, Feb 20, 2025 at 7:59 AM Miro Hrončok wrote: > > On 20. 02. 25 13:51, Michael J Gruber wrote: > >>> With the wide adoption of %autorelease, such bump commits are empty, > >>> which should be easy to verify. > > Wide, well, ... > > Roughly 39% based on a simple grep for %\{?autorelease > Wh

Re: Proposal: Allow all packagers to push empty commits to any package

On Thu, Feb 20, 2025 at 1:17 PM Miro Hrončok wrote: > > What if we allowed all packagers to push empty commit to any package? That > should eliminate *some* need for provenpackager access. We would also > communicate in our policies that such bumps do not require prior agreement > with > the main

Proposal: Allow all packagers to push empty commits to any package

Hello. With the recent discussions about provenpackagers in Fedora, I recently got an idea. One of the common needs for provenpackagers is to simply "bump and rebuild" a set of dependencies. All packagers are already able to build anything (except a very specific and small set of specially

Re: Proposal: Allow all packagers to push empty commits to any package

On 2025/02/20 13:17, Miro Hrončok wrote: What if we allowed all packagers to push empty commit to any package? That should eliminate *some* need for provenpackager access. We would also communicate in our policies that such bumps do not require prior agreement with the maintainers to avoid con