FS#59563 - [python-pytorch] wrong version number 0.4.1

Attached to Project: Community Packages
Opened by Stefan Falkner (sfalkner) - Wednesday, 08 August 2018, 07:54 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Wednesday, 08 August 2018, 23:45 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
The latest python-pytorch package is listed as 0.4.1 in pacman, but after install it, I get the following information within IPython:

In [1]: import torch

In [2]: torch.__version__
Out[2]: '0.4.0a0+200fb22'


Looking into the PKGBUILD, it appears that the git commit for the build is _commit=200fb22, but the one for the release 0.4.1 on github is a24163a95edb193ff7b06e98cd69bf7cfd4c0d2f.
Maybe it would one could change the PKGBUILD to look for a tag instead of a specific commit?


Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:
Install python-pytorch or python-pytorch-cuda
start python
type: 'import torch; print(torch.__version__)'

expected output: 0.4.1
actual output : 0.4.0a0+200fb22
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Wednesday, 08 August 2018, 23:45 GMT
Reason for closing:  Fixed
Comment by Eli Schwartz (eschwartz) - Wednesday, 08 August 2018, 14:54 GMT
Okay, actually this is confusing me: https://git.archlinux.org/svntogit/community.git/commit/trunk?h=packages/python-pytorch&id=1dc82b7ddd850d3c5f8bef93bcc737a292f70c8c

Looks like the pkgver was bumped without bumping the pinned commit...
Comment by Sven-Hendrik Haase (Svenstaro) - Wednesday, 08 August 2018, 18:20 GMT
Well fuck me, this is what happens when you mindlessly update a package. Fixing.

Loading...