Bug 1767974 - Version 0.4.0 is available
Summary: Version 0.4.0 is available
Keywords:
Status: CLOSED DUPLICATE of bug 1780007
Alias: None
Product: Fedora
Classification: Fedora
Component: twolame
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Simone Caronni
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-01 18:54 UTC by barsnick
Modified: 2020-01-14 13:24 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-01-14 13:24:27 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
ABI compliance report 0.3.13 vs 0.4.0 (94.01 KB, text/html)
2019-12-02 16:07 UTC, barsnick
no flags Details

Description barsnick 2019-11-01 18:54:41 UTC
Description of problem:
A new upstream version 0.4.0 is available.

Version-Release number of selected component (if applicable):
0.3.13-14

Additional info:
Another one of those cases where Upstream Release Monitoring failed to notify Bugzilla.
https://release-monitoring.org/project/12524/

The soname version didn't change, and from the Changelog, there were only additions to the API, so in theory, this update should be compatible with all versions of Fedora, not just made for RawHide. I didn't check ABI compliance though.

Comment 1 barsnick 2019-12-02 16:07:49 UTC
Created attachment 1641446 [details]
ABI compliance report 0.3.13 vs 0.4.0

Comment 2 barsnick 2019-12-02 16:08:08 UTC
I ran an ABI compliance check, and it doesn't look good. The changelog (NEWS.md) hints at incompatibilities, but this proves it.

Unfortunately, upstream doesn't maintain an soname and didn't bump the version, so (AFAICT) the new version can only be introduced into Rawhide, with a careful rebuild of all dependencies. Or better/words, bump the version in the soname locally, and complain upstream.

ABI report attached.

Comment 3 barsnick 2020-01-14 13:24:27 UTC
34 days later, Upstream Release Monitoring has caught up. :-P See #1780007.

My comments are still valid though.

*** This bug has been marked as a duplicate of bug 1780007 ***


Note You need to log in before you can comment on or make changes to this bug.