stable

wxGTK3-3.0.5.1-1.fc33

FEDORA-2020-35061137b7 created by swt2c 4 years ago for Fedora 33

Automatic update for wxGTK3-3.0.5.1-1.fc33.

Changelog
* Sun May 10 2020 Scott Talbert <swt@techie.net> - 3.0.5.1-1
- Update to new upstream release 3.0.5.1

How to install

Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:

sudo dnf upgrade --refresh --advisory=FEDORA-2020-35061137b7

This update was automatically created

4 years ago

This update's test gating status has been changed to 'waiting'.

4 years ago

This update's test gating status has been changed to 'ignored'.

4 years ago

This update can be pushed to stable now if the maintainer wishes

4 years ago

This update has been submitted for stable by bodhi

4 years ago

Why was there no 3.0.5 update for F32?

Because nobody asked for it? Do you have a need for it?

Well, nothing severe like known to fix bug X in Y. But I considered a F32 bugfix update as consistent with stable update policy, as F32 is a fresh release: "As a result, we should avoid major updates of packages within a stable release. Updates should aim to fix bugs, and not introduce features, particularly when those features would materially affect the user or developer experience. The update rate for any given release should drop off over time, approaching zero near release end-of-life; since updates are primarily bugfixes, fewer and fewer should be needed over time."

https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/

Yes, I believe it would be okay to update it per policy. However, I usually wait until there is some compelling reason (e.g., a bug that someone is affected by) before pushing an update to a package that I maintain.

In this case, I think updating to 3.0.5 in stable will also need to be coordinated with the dependent packages to ensure there are no breakages due to the change in wxDataView:

  • Potentially incompatible change: wxDataViewModel::Cleared() now works as documented cross-platform. Previously on wxGTK it just emptied the model rather than triggering a reload of the model. If you are working around the broken behaviour with wxGTK-specific code in your application you should check that your application works correctly with this change.

I have seen at least one application that has crashes on 3.0.5 and not 3.0.4 because of this change.

OK, understandable to stay on 3.0.4.


Please login to add feedback.

Metadata
Type
unspecified
Karma
0
Signed
Content Type
RPM
Test Gating
Settings
Unstable by Karma
-3
Stable by Karma
disabled
Stable by Time
0 days
Dates
submitted
4 years ago
in testing
4 years ago
in stable
4 years ago

Automated Test Results