Bug 1536276 - ktorrent reports wrong client ID
Summary: ktorrent reports wrong client ID
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: ktorrent
Version: 27
Hardware: i686
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Roland Wolters
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-19 02:56 UTC by Steve
Modified: 2018-01-30 18:04 UTC (History)
4 users (show)

Fixed In Version: ktorrent-5.1.0-3.fc27
Clone Of:
Environment:
Last Closed: 2018-01-30 18:04:01 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
Patch to fix bug (616 bytes, patch)
2018-01-19 02:56 UTC, Steve 		no flags Details | Diff
View All

Description Steve 2018-01-19 02:56:47 UTC 
Created attachment 1383127 [details]
Patch to fix bug

Description of problem:
ktorrent reports the wrong client ID.
Even though it's version 5.1.0 release, it's reporting itself as 5.0.1 development.
Some torrent-trackers whitelist torrent-clients.

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

Additional info:

Enclosed is a patch that fixes the problem.
Comment 1 Fedora Update System 2018-01-19 16:01:29 UTC 
ktorrent-5.1.0-3.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-c3766f52a2
Comment 2 Fedora Update System 2018-01-21 10:40:37 UTC 
ktorrent-5.1.0-3.fc27 has been pushed to the Fedora 27 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-2018-c3766f52a2
Comment 3 Steve 2018-01-24 02:29:33 UTC 
Thanks for the quick response on this!
Comment 4 Fedora Update System 2018-01-30 18:04:01 UTC 
ktorrent-5.1.0-3.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, 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.