FS#32322 - [transmission-cli] Package version 2.73, but binary version 2.72

Attached to Project: Arch Linux
Opened by Polo (lihato) - Wednesday, 31 October 2012, 12:36 GMT
Last edited by Ionut Biru (wonder) - Wednesday, 31 October 2012, 13:42 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

The package transmission-cli is version 2.73 in the repo, but the binary is version 2.72:


$ pacman -Qs transmission
local/transmission-cli 2.73-1

$ transmission-daemon --version
transmission-daemon 2.72 (13582)

Upstream the laste stable is 2.73

It is a problem because some trackers don't allow transmission 2.72.
This task depends upon

Closed by  Ionut Biru (wonder)
Wednesday, 31 October 2012, 13:42 GMT
Reason for closing:  Fixed
Comment by Ionut Biru (wonder) - Wednesday, 31 October 2012, 12:42 GMT
tell that upstream because they screwed 2.73 release.
Comment by Polo (lihato) - Wednesday, 31 October 2012, 12:43 GMT
I downloaded the tarball and compiled it, I get transmission-daemon 2.73 (13592)

I think the problem is in the PKGBUILD, line 17: cd "$pkgbase-2.72"
https://projects.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/transmission
Comment by Ionut Biru (wonder) - Wednesday, 31 October 2012, 13:14 GMT
maybe they fixed it. i guess md5 doesn't match anymore right?
Comment by Polo (lihato) - Wednesday, 31 October 2012, 13:18 GMT
You are right they don't match anymore. The new one is fae00b13a7b18f9dc16edef020edea85

The md5 that is in the PKGBUILD matches the 2.72 tarball.
Comment by Ionut Biru (wonder) - Wednesday, 31 October 2012, 13:20 GMT
nice one. i wonder why they didn't release 2.74 instead. they had that broken tarball couples of days
Comment by Polo (lihato) - Wednesday, 31 October 2012, 13:22 GMT
I still think there is a problem in the PKGBUILD. It downloads the 2.73 tarball, check with the 2.72 md5, and cd into a 2.72 version.
Comment by Ionut Biru (wonder) - Wednesday, 31 October 2012, 13:23 GMT
the tarball was 2.73 but after extracting, it had a 2.72 directory. that's why i'm saying that they had a broken tarball.

Loading...