FS#50152 - [deluge] 1.3.13 displaying as 1.3.13-dev0 via conn man

Attached to Project: Arch Linux
Opened by binhex (binhex) - Tuesday, 26 July 2016, 10:29 GMT
Last edited by Jan Alexander Steffens (heftig) - Tuesday, 04 October 2016, 17:06 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
The latest compiled version of Deluge from the official Arch Linux Repo (not AUR) is showing as a development build in Deluge Connection Manager (build 1.3.13-dev0), i believe this is due to incorrectly building from github master branch source and not building from the GitHub "release", link to forum post related to this issue from another user:-
http://forum.deluge-torrent.org/viewtopic.php?t=53717

For reference I have also posted the bug here on the forum:-
https://bbs.archlinux.org/viewtopic.php?pid=1643646#p1643646

Additional info:
* package version(s)
1.3.13-1

* config and/or log files etc.
N/A

Steps to reproduce:
Download the latest Deluge compiled package from Arch Linux Repo, install, start Deluge daemon and connect to the daemon using the Deluge webui, notice that Deluge Connection Manager is showing the version as 1.3.13-dev0.

I have marked this has High due to the fact it is causing issues with private trackers blocking the client, as they are marking it incorrectly as a development build.
This task depends upon

Closed by  Jan Alexander Steffens (heftig)
Tuesday, 04 October 2016, 17:06 GMT
Reason for closing:  Fixed
Additional comments about closing:  1.3.13+2
Comment by Giacomo (rjack) - Tuesday, 16 August 2016, 01:51 GMT
  • Field changed: Percent Complete (100% → 0%)
Hi Jan, this is not a cosmetic issue as it prevents users to run this client on some private trackers that have very strict rules on client versions. For example, a private tracker is blocking my deluge upgraded client with this error: https://s4.postimg.io/794h5ebvh/client_error.png Can you please re-open this issue?
Comment by Django Hilarious (buzz) - Tuesday, 04 October 2016, 16:39 GMT
Hey :)
any progress on this?
Comment by binhex (binhex) - Tuesday, 04 October 2016, 16:57 GMT
not sure if this is of help to anybody but i decided to go alone and fix this up myself, below is the code required to strip out .dev0 for deluge after installation:-

# manually remove .dev0 from compiled package name (is a result of pull commit from github)
mv "/usr/lib/python2.7/site-packages/deluge-1.3.13.dev0-py2.7.egg-info/" "/usr/lib/python2.7/site-packages/deluge-1.3.13-py2.7.egg-info/"
sed -i -e 's~\.dev0~~g' "/usr/lib/python2.7/site-packages/deluge-1.3.13-py2.7.egg-info/PKG-INFO" "/usr/bin/deluge" "/usr/bin/deluge-console" "/usr/bin/deluged" "/usr/bin/deluge-gtk" "/usr/bin/deluge-web"
Comment by Django Hilarious (buzz) - Tuesday, 04 October 2016, 17:03 GMT
I think this is actually an upstream bug?

The package maintainer is building this from git branch 1.3-stable. That is an official and supported way of installing deluge.
So the version string should not have -dev0 appended, right?

Loading...