Package: devscripts
Version: 2.26.11
Severity: wishlist
X-Debbugs-Cc: [email protected]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
[This is similar to #1123859 but concerns different aspects.]
Salut Xavier !
During the MiniDebConf Winterthur I looked again into uscan version 5
and the Metacpan templates, and there are two issues around versions
I noticed:
1) I remember that you already somewhere in the code strip the ^v from
versions, which is great, but with --dehs they still appear:
Example: the ack package:
% uscan --report --dehs
Newest version of ack on remote site is 3.10.0, local version is 3.9.0
=> Newer package available from:
=> https://cpan.metacpan.org/authors/id/P/PE/PETDANCE/ack-v3.10.0.tar.gz
<dehs>
<package>ack</package>
<debian-uversion>3.9.0</debian-uversion>
<debian-mangled-uversion>3.9.0</debian-mangled-uversion>
<upstream-version>3.10.0</upstream-version>
<upstream-url>https://cpan.metacpan.org/authors/id/P/PE/PETDANCE/ack-v3.10.0.tar.gz</upstream-url>
<status>newer package available</status>
</dehs>
% uscan --update-watchfile
% uscan --report --dehs
Newest version of ack on remote site is v3.10.0, local version is 3.9.0
=> Newer package available from:
=> https://cpan.metacpan.org/authors/id/P/PE/PETDANCE/ack-v3.10.0.tar.gz
<dehs>
<package>ack</package>
<debian-uversion>3.9.0</debian-uversion>
<debian-mangled-uversion>3.9.0</debian-mangled-uversion>
<upstream-version>v3.10.0</upstream-version>
<upstream-url>https://cpan.metacpan.org/authors/id/P/PE/PETDANCE/ack-v3.10.0.tar.gz</upstream-url>
<status>newer package available</status>
</dehs>
Here the ^v is still there in the <upstream-version> tag. Do you
think it makes sense and is possible to get rid of it?
2) The other thing is development versions on the CPAN, i.e. versions
containing an '_'. It seems that with version 4 they are ignored
(good) -- maybe because the MetaCPAN website doesn't show them --,
with version 5 they appear. (In version 3 we explicitly excluded
them from the "default" regexp, IIRC.)
Example: the carton package:
% uscan --report --dehs
<dehs>
<package>carton</package>
<debian-uversion>1.0.35</debian-uversion>
<debian-mangled-uversion>1.0.35</debian-mangled-uversion>
<upstream-version>1.0.35</upstream-version>
<upstream-url>https://cpan.metacpan.org/authors/id/M/MI/MIYAGAWA/Carton-v1.0.35.tar.gz</upstream-url>
<status>up to date</status>
</dehs>
% uscan --update-watchfile
% uscan --report --dehs
Newest version of carton on remote site is v1.0.901, local version is 1.0.35
=> Newer package available from:
=>
https://cpan.metacpan.org/authors/id/M/MI/MIYAGAWA/Carton-v1.0.901-TRIAL.tar.gz
<dehs>
<package>carton</package>
<debian-uversion>1.0.35</debian-uversion>
<debian-mangled-uversion>1.0.35</debian-mangled-uversion>
<upstream-version>v1.0.901</upstream-version>
<upstream-url>https://cpan.metacpan.org/authors/id/M/MI/MIYAGAWA/Carton-v1.0.901-TRIAL.tar.gz</upstream-url>
<status>newer package available</status>
</dehs>
Ehm, no, that's not the example with '_' but with '-TRIAL'. Also not
helpful but I guess that's a MetaCPAN API issue?
Here we go: the feersum package:
% uscan --report --dehs
<dehs>
<package>feersum</package>
<debian-uversion>1.505</debian-uversion>
<debian-mangled-uversion>1.505</debian-mangled-uversion>
<upstream-version>1.505</upstream-version>
<upstream-url>https://cpan.metacpan.org/authors/id/E/EG/EGOR/Feersum-1.505.tar.gz</upstream-url>
<status>up to date</status>
</dehs>
% uscan --update-watchfile
% uscan --report --dehs
Newest version of feersum on remote site is 1.506_61, local version is 1.505
=> Newer package available from:
=>
https://cpan.metacpan.org/authors/id/E/EG/EGOR/Feersum-1.506_61.tar.gz
<dehs>
<package>feersum</package>
<debian-uversion>1.505</debian-uversion>
<debian-mangled-uversion>1.505</debian-mangled-uversion>
<upstream-version>1.506_61</upstream-version>
<upstream-url>https://cpan.metacpan.org/authors/id/E/EG/EGOR/Feersum-1.506_61.tar.gz</upstream-url>
<status>newer package available</status>
</dehs>
Would it be possible to ignore the "_" versions for the Metacpan
template / adjust the versions regex / the "versiontype" value there?
Cheers,
gregor
-----BEGIN PGP SIGNATURE-----
iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmqUqYtfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgY+TBAAgiNOpAEKEbjQXz8jXmEY7DixTauyztUBeZ/CLGOa2rytMbojYJT6dpos
KTdalb6D8/3pubu6v/j2nNvkhmSpHhBSyp3Y7PLykfLTy1LoiOU0qE3RYHOd2fcd
RF0UdILA30wUY4pvxy9+9R/0NQCbaiRUU+rX9d5IKCbpYMVz07uSIXOpudG1Z9Gl
s4WuJdlkZfG6T693EGcMpQ+1o8kYxUQeR3hVe4HXFTt52lAAWxM4VLCjD3VNiwdP
3f9aj6rB+4Goi4X/Ckz8Z9or9r+nKns0Ir+2AnW0MaIlrJeYo8aVeu6NuiG12Wk6
v2cdGw5XiZDwKebzRPfOyidm6U+J4qn+nkRCwyXRaRfTvaCmpPa5h3OdiKQDJAEF
FPMkb2HZ/4JExFzmNgusOnalPYxpyJNsoczA8iO5pME8A14+DHrTyT3vT8glKp/i
EPe09zxdtJuxFRj4N5nZEMTmgQgyAsjfNg5he1iQiGeiwsF1JFqQRfpKB4w8ClbU
FwINiJuEKYQhRDa6vF90vbqYaLgRnFQnBgHxTf4a0rnyadWFHJH728QqoqLnlThK
IcCF0HWryX/r1LYHWTBhDedvP9XYw2Xybc3lToGeWUMmo5ljAvPfTUpr8EbTwoGE
uLtn7gFtnJhHuH5QGxLBMW4xGIxowVVRIBnzyEQd2wNrFr1qV5k=
=YXt1
-----END PGP SIGNATURE-----
