Hi @leigh123linux, thanks for the heads up. Do you know if the version mismatch could cause any problems? And also, do you known their reason for waiting a week? I'm not familiar with RPM fusion's release calendar, so I'm not sure if this is the usual schedule or an exception .
Due to limited free time, rpmfusion pushes are run once a week, the last push was yesterday, the next will be Wednesday.
The version mismatch should prevent the update from completing.
Nearly every mesa update causes dnf transaction failure for users using mesa-freeworld, it would be cool if future fedora mesa updates were submitted with auto-push disabled.
I could then coordinate both so they are pushed together, my proven-packager rights should enable me to push the fedora mesa updates.
Hey @leigh123linux, that's good to know, I wasn't aware of the RPM Fusion schedule.
Since this release doesn't fix any urgent bug reported to the Fedora bug tracker, I disabled karma auto-push so you can coordinate both releases next week.
Lately, I'm handling the Fedora mesa updates. It'd be nice to coordinate and avoid issues to RPM Fusion users. Let me know if this works for you.
It'd be nice if we could work together to avoid issues to the RPM Fusion users. At least when there are no urgent bugs that require a mesa release as soon as possible.
@arcivanov "still a problem" is not a reason for downvoting. -1 karma should only be used for new regressions. If the problem is already in stable repos and the new build doesn't make it worse, there's no reason to block it from going stable.
@kparal it was reported by me in the .5->.6 upgrade after .6 was already stable. I was asked to test .7 in testing so, technically, in the testing lifecycle it's a new regression - the first opportunity to report it in testing.
Thanks for testing. Still no reason to downvote it, see my explanation. Always think about "does stopping this update make the situation better?". In this case, it doesn't. We even have some guidelines written for bodhi karma somewhere, I just can't find it right now :)
This update has been submitted for testing by jexposit.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
The mesa-freeworld package isn't going to be push to the repo until next Wednesday.
Hi @leigh123linux, thanks for the heads up. Do you know if the version mismatch could cause any problems? And also, do you known their reason for waiting a week? I'm not familiar with RPM fusion's release calendar, so I'm not sure if this is the usual schedule or an exception .
Hi @jexposit
Due to limited free time, rpmfusion pushes are run once a week, the last push was yesterday, the next will be Wednesday. The version mismatch should prevent the update from completing. Nearly every mesa update causes dnf transaction failure for users using mesa-freeworld, it would be cool if future fedora mesa updates were submitted with auto-push disabled. I could then coordinate both so they are pushed together, my proven-packager rights should enable me to push the fedora mesa updates.
Regards, Leigh (rpmfusion admin).
jexposit edited this update.
jexposit edited this update.
Hey @leigh123linux, that's good to know, I wasn't aware of the RPM Fusion schedule.
Since this release doesn't fix any urgent bug reported to the Fedora bug tracker, I disabled karma auto-push so you can coordinate both releases next week.
Lately, I'm handling the Fedora mesa updates. It'd be nice to coordinate and avoid issues to RPM Fusion users. Let me know if this works for you.
It'd be nice if we could work together to avoid issues to the RPM Fusion users. At least when there are no urgent bugs that require a mesa release as soon as possible.
Hi @jexposit
That works for me, thanks.
This update has been pushed to testing.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
Works.
This update can be pushed to stable now if the maintainer wishes
Works
No issues spotted and Once Human black artifact issue is resolved indeed
no problems on Thinkpad P1 Gen4 (TigerLake-H GT1 [UHD Graphics] [8086:9a60])
https://bugzilla.redhat.com/show_bug.cgi?id=2307607 is still a problem
This update has been submitted for stable by leigh123linux.
@arcivanov "still a problem" is not a reason for downvoting. -1 karma should only be used for new regressions. If the problem is already in stable repos and the new build doesn't make it worse, there's no reason to block it from going stable.
@kparal it was reported by me in the .5->.6 upgrade after .6 was already stable. I was asked to test .7 in testing so, technically, in the testing lifecycle it's a new regression - the first opportunity to report it in testing.
Thanks for testing. Still no reason to downvote it, see my explanation. Always think about "does stopping this update make the situation better?". In this case, it doesn't. We even have some guidelines written for bodhi karma somewhere, I just can't find it right now :)
Operating System: Fedora Linux 40
WORKS
This update has been pushed to stable.