Bug 1634321 - RFE Drop check for mismatch of versions / Be nice to clients with older version of libotr
Summary: RFE Drop check for mismatch of versions / Be nice to clients with older versi...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libotr
Version: rawhide
Hardware: All
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Paul Wouters
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-29 21:40 UTC by Raphael Groner
Modified: 2021-05-31 20:26 UTC (History)
2 users (show)

Fixed In Version: libotr-4.1.1-12.fc33 libotr-4.1.1-12.fc34
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-28 01:10:46 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
Patch stolen from debian (1.58 KB, patch)
2018-09-29 21:42 UTC, Raphael Groner 		no flags Details | Diff
View All

Description Raphael Groner 2018-09-29 21:40:41 UTC 
Description of problem:
libotr gives an error when version of a client is not acurate.

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

How reproducible:
maybe

Steps to Reproduce:
1. dnf install psi-plus
2. login into your jabber
3. try to use encryption with a client built against newer version of libotr

Actual results:
error

Expected results:
no error

Additional info:
https://github.com/psi-im/plugins/issues/7#issuecomment-423048948
Comment 1 Raphael Groner 2018-09-29 21:42:30 UTC 
Created attachment 1488451 [details]
Patch stolen from debian

Do not error out when an application is run against an older libotr than the one it was built against
Comment 2 Fedora Admin user for bugzilla script actions 2021-04-26 12:27:45 UTC 
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.
Comment 3 Raphael Groner 2021-04-26 15:07:47 UTC 
Thanks for new maintainer. Well, any news here? Could you apply proposed debian patch or should I file a pull request?
Comment 4 Fedora Update System 2021-05-19 01:04:27 UTC 
FEDORA-2021-e8fa85f135 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-e8fa85f135
Comment 5 Fedora Update System 2021-05-19 01:38:18 UTC 
FEDORA-2021-c49e0345c2 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-c49e0345c2
Comment 6 Fedora Update System 2021-05-20 02:25:08 UTC 
FEDORA-2021-c49e0345c2 has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-c49e0345c2`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-c49e0345c2

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 7 Fedora Update System 2021-05-21 01:34:55 UTC 
FEDORA-2021-e8fa85f135 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-e8fa85f135`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-e8fa85f135

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 8 Fedora Update System 2021-05-28 01:10:46 UTC 
FEDORA-2021-c49e0345c2 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 9 Fedora Update System 2021-05-29 01:04:10 UTC 
FEDORA-2021-e8fa85f135 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.