Skip to content

Update rpmfusion current maintained version#1546

Merged
AMDmi3 merged 1 commit intorepology:masterfrom
kwizart:rpmfusion_2025
Nov 7, 2025
Merged

Update rpmfusion current maintained version#1546
AMDmi3 merged 1 commit intorepology:masterfrom
kwizart:rpmfusion_2025

Conversation

@kwizart
Copy link
Copy Markdown
Contributor

@kwizart kwizart commented Nov 5, 2025

No description provided.

@AMDmi3
Copy link
Copy Markdown
Member

AMDmi3 commented Nov 5, 2025

Our current policy is to remove repositories 2 years after their EoL date. Has 2 years passed for removed repos? Please provide EoL dates if possible.

@AMDmi3
Copy link
Copy Markdown
Member

AMDmi3 commented Nov 5, 2025

Also, before rpmfusion repos did not provide links to package sources, and this is a show stopper for adding new versions. I've added the links to https://github.com/rpmfusion/*, but not all of these are valid, for instance https://github.com/rpmfusion/lpf-mscore-tahoma-fonts/ lacks f40 branch, despite being present in rpmfusion f40

@kwizart
Copy link
Copy Markdown
Contributor Author

kwizart commented Nov 6, 2025

We've always provided source packages and repos in "distgit form" for packages. Github is the mirror that we advertise for public consumption, but the original git repos (also public) is where we contribute . Our script just doesn't sync branches if no new content is made. I just pushed a quick change to force the branch to be sync in this case.

@AMDmi3
Copy link
Copy Markdown
Member

AMDmi3 commented Nov 7, 2025

We've always provided source packages and repos in "distgit form" for packages.

Sure, but Repology's requirement is that valid links should be constructible out of package metadata. For instance, there's no knowing there's no f40 branch for e.g. freeguide, we construct link to e.g. https://github.com/rpmfusion/freeguide/blob/f40/freeguide.spec and it turns out to be broken, and repology uses will not be able to inspect a given package recipe.

Our script just doesn't sync branches if no new content is made. I just pushed a quick change to force the branch to be sync in this case.

Thanks! I guess you need to bump remaining packages, there's just a dozen of these (listing remaining broken links):

https://github.com/rpmfusion/freeguide/blob/f39/freeguide.spec
https://github.com/rpmfusion/freeguide/blob/f40/freeguide.spec
https://github.com/rpmfusion/freeguide/blob/f41/freeguide.spec
https://github.com/rpmfusion/freeguide/tree/f39
https://github.com/rpmfusion/freeguide/tree/f40
https://github.com/rpmfusion/freeguide/tree/f41
https://github.com/rpmfusion/gstreamer1-libav/blob/el9/gstreamer1-libav.spec
https://github.com/rpmfusion/libdca/blob/f39/libdca.spec
https://github.com/rpmfusion/libdca/tree/f39
https://github.com/rpmfusion/lpf-cleartype-fonts/blob/f40/lpf-cleartype-fonts.spec
https://github.com/rpmfusion/lpf-cleartype-fonts/blob/f41/lpf-cleartype-fonts.spec
https://github.com/rpmfusion/lpf-cleartype-fonts/tree/f40
https://github.com/rpmfusion/lpf-cleartype-fonts/tree/f41
https://github.com/rpmfusion/lpf-mscore-fonts/blob/f39/lpf-mscore-fonts.spec
https://github.com/rpmfusion/lpf-mscore-fonts/blob/f40/lpf-mscore-fonts.spec
https://github.com/rpmfusion/lpf-mscore-fonts/blob/f41/lpf-mscore-fonts.spec
https://github.com/rpmfusion/lpf-mscore-fonts/tree/f39
https://github.com/rpmfusion/lpf-mscore-fonts/tree/f40
https://github.com/rpmfusion/lpf-mscore-fonts/tree/f41
https://github.com/rpmfusion/lpf-mscore-tahoma-fonts/tree/f40
https://github.com/rpmfusion/mp3gain/blob/el7/mp3gain.spec
https://github.com/rpmfusion/rfpkg-minimal/blob/f40/rfpkg-minimal.spec
https://github.com/rpmfusion/rfpkg-minimal/blob/f41/rfpkg-minimal.spec
https://github.com/rpmfusion/rfpkg-minimal/tree/f40
https://github.com/rpmfusion/rfpkg-minimal/tree/f41
https://github.com/rpmfusion/rpmfusion-free-obsolete-packages/blob/f41/rpmfusion-free-obsolete-packages.spec
https://github.com/rpmfusion/rpmfusion-free-obsolete-packages/tree/f41
https://github.com/rpmfusion/rpmfusion-nonfree-obsolete-packages/blob/f39/rpmfusion-nonfree-obsolete-packages.spec
https://github.com/rpmfusion/rpmfusion-nonfree-obsolete-packages/blob/f40/rpmfusion-nonfree-obsolete-packages.spec
https://github.com/rpmfusion/rpmfusion-nonfree-obsolete-packages/blob/f41/rpmfusion-nonfree-obsolete-packages.spec
https://github.com/rpmfusion/rpmfusion-nonfree-obsolete-packages/tree/f39
https://github.com/rpmfusion/rpmfusion-nonfree-obsolete-packages/tree/f40
https://github.com/rpmfusion/rpmfusion-nonfree-obsolete-packages/tree/f41
https://github.com/rpmfusion/wormsofprey-data/blob/f39/wormsofprey-data.spec
https://github.com/rpmfusion/wormsofprey-data/blob/f40/wormsofprey-data.spec
https://github.com/rpmfusion/wormsofprey-data/blob/f41/wormsofprey-data.spec
https://github.com/rpmfusion/wormsofprey-data/tree/f39
https://github.com/rpmfusion/wormsofprey-data/tree/f40
https://github.com/rpmfusion/wormsofprey-data/tree/f41
https://github.com/rpmfusion/xine-plugin/blob/f39/xine-plugin.spec
https://github.com/rpmfusion/xine-plugin/blob/f40/xine-plugin.spec
https://github.com/rpmfusion/xine-plugin/blob/f41/xine-plugin.spec
https://github.com/rpmfusion/xine-plugin/tree/f39
https://github.com/rpmfusion/xine-plugin/tree/f40
https://github.com/rpmfusion/xine-plugin/tree/f41

el7 link may be ignored if we are really going to remove the repository.

So, what about EoL dates?

And another question, do I understand correctly that rpm fusion fedora rawhide correspond to master branches in package repositories?

@kwizart
Copy link
Copy Markdown
Contributor Author

kwizart commented Nov 7, 2025

I think to have fixed all issue. Please confirm.

The only remaining issue is likely gstreamer1-libav on el9, but this package is already retired in our git repo and will be removed from the package repository on the next push. (It will occur over the week-end).

So, what about EoL dates?

centos 7 was EOL on 2024/06 https://endoflife.date/centos
But still advertising it is a problem as we are likely going to move the packages elsewhere

Same for Fedora https://endoflife.date/fedora.

Also no updates are expected to be made, that's what's EOL means. So having theses releases displayed along supported ones is problematic IMHO.

And another question, do I understand correctly that rpm fusion fedora rawhide correspond to master branches in package repositories?

Yes

@AMDmi3
Copy link
Copy Markdown
Member

AMDmi3 commented Nov 7, 2025

I think to have fixed all issue. Please confirm.

xine-plugin is the only one remaining. Probably a retired package too.

But still advertising it is a problem as we are likely going to move the packages elsewhere

That's not a problem, I'll just remove the repositories as soon as the data is gone.

Also no updates are expected to be made, that's what's EOL means. So having theses releases displayed along supported ones is problematic IMHO.

We keep EoLed repos for historical purposes and to to keep people still using these aware of how outdated, vulnerable and incompatible these are. Before recently, we were keeping these indefinitely, #1499 for more info. So let's drop removals from this PR and it's good to go. I'll add EoL dates then and clean up old repos on general EoL+2y || data is gone policy.

@kwizart
Copy link
Copy Markdown
Contributor Author

kwizart commented Nov 7, 2025

xine-plugin is the only one remaining. Probably a retired package too.

Fixed, thanks.

we were keeping these indefinitely, #1499 for more info.

About centos EOL, the RHEL 6 ELS only really applies to a very limited list of packages:

https://access.redhat.com/support/policy/updates/errata
https://access.redhat.com/articles/4997301

So I don't think this applies for general distro, and it specially not apply to our rpmfusion content.

But anyway, I will leave the older ones so they are discarded as your discretion.

Fixup....

@AMDmi3 AMDmi3 merged commit 21f3a6a into repology:master Nov 7, 2025
1 check passed
AMDmi3 added a commit that referenced this pull request Nov 7, 2025
@AMDmi3
Copy link
Copy Markdown
Member

AMDmi3 commented Nov 7, 2025

FYI, xine-plugin still misses f41

@AMDmi3
Copy link
Copy Markdown
Member

AMDmi3 commented Nov 10, 2025

@kwizart there's also a lot of broken links from new repos https://gist.github.com/AMDmi3/9d400486086a7acdb01b096b653d5a07, can these be fixed asap?

@kwizart
Copy link
Copy Markdown
Contributor Author

kwizart commented Nov 11, 2025

I've fixed xine-plugin and the new list. If anything remains please let me know.
Thanks

@AMDmi3
Copy link
Copy Markdown
Member

AMDmi3 commented Nov 11, 2025

Thank you! Only 8 urls remain

https://github.com/rpmfusion/ivsc-firmware/blob/f42/ivsc-firmware.spec
https://github.com/rpmfusion/ivsc-firmware/blob/f43/ivsc-firmware.spec
https://github.com/rpmfusion/ivsc-firmware/blob/master/ivsc-firmware.spec
https://github.com/rpmfusion/ivsc-firmware/tree/f42
https://github.com/rpmfusion/ivsc-firmware/tree/f43
https://github.com/rpmfusion/kffmpegthumbnailer/blob/f43/kffmpegthumbnailer.spec
https://github.com/rpmfusion/kffmpegthumbnailer/tree/f43
https://github.com/rpmfusion/ripcord/blob/master/ripcord.spec

@kwizart
Copy link
Copy Markdown
Contributor Author

kwizart commented Nov 12, 2025

Fixed, the remaining master branches will be fixed on the next push (by the end of the week). theses components were not properly retired.

@AMDmi3
Copy link
Copy Markdown
Member

AMDmi3 commented Nov 12, 2025

Thank you so much! Everything is resolved now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants