libserialport-0.1.1-0.fc23 libsigrok-0.4.0-1.fc23 libsigrokdecode-0.4.0-0.fc23 pulseview-0.3.0-1.fc23 sigrok-cli-0.6.0-0.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2016-25730450b6

libserialport-0.1.1-0.fc23, libsigrok-0.4.0-1.fc23, libsigrokdecode-0.4.0-0.fc23, pulseview-0.3.0-1.fc23, sigrok-cli-0.6.0-0.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-25730450b6

libserialport-0.1.1-0.fc23, libsigrok-0.4.0-1.fc23, libsigrokdecode-0.4.0-0.fc23, pulseview-0.3.0-1.fc23, sigrok-cli-0.6.0-0.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.

This is not fixed in libsigrok.x86_64 0.4.0-1.fc23

Created attachment 1162480 [details]
add missing requires to libsigrok

this patch might fix this bug

I see what the problem is, same soname, but new APIs added and being used by ligsigrok. The proper solution would be to use symbol versioning in libserialport.

Let me look into this, but I'm leaning on adding a Requires. Though I would have expected this to be a no-issue, as libserialport-devel requirement is already >= 0.1.1

Created attachment 1162508 [details]
add version info to libserialport

The problem is with the runtime dependency, the library in both 0.1.0 and 0.1.1 versions is identified by "libserialport.so.0" as soname, so the package mgmt tools think it's up-to-date. So either an explicit Requires or a fix in libserialport (as the proposed patch) is needed.

This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.