Le 08/11/2020 à 08:05, Xavier a écrit :
> Le 07/11/2020 à 21:44, Gordon Ball a écrit :
>> On Sat, Nov 07, 2020 at 09:17:58AM +0100, Xavier wrote:
>>> Hi,
>>>
>>> I updated codemirror-js (missing @types/tern and
>>> debian/nodejs/root_modules) and mad a lot of changes in
>>> debian/copyright. Please review before uploading.
>>>
>> Thanks for taking a look. This was the first multi-tarball package I'd
>> prepared, so having a second eye on it is useful. The result looks fine
>> compared to previous versions and I'll probably upload it soon.
>>
>> Unfortunately at least a couple of these changes duplicate local ones I
>> had (d/nodejs/root_modules, etc), but I guess I should have pushed them
>> sooner. I'd missed the follow-on dependency on @types/tern though, and
>> evidently the copyright file needed a wider refresh.
>>
>> One question - can you point me to any documentation on how the
>> ~cs0.23.101-1 component version is derived?
>
> Hi,
>
> from uscan(1):
>
> version restricts the upstream tarball which may be downloaded. The
> newest available version is chosen in each case.
> • debian (default) requires the downloading upstream tarball to be
> newer than the version obtained from debian/changelog.
> • version-number such as 12.5 requires the upstream tarball to be
> newer than the version-number.
> • same requires the downloaded version of the secondary tarballs to
> be exactly the same as the one for the first upstream tarball
> downloaded. (Useful only for MUT)
> • previous restricts the version of the signature file. (Used with
> pgpmode=previous)
> • ignore does not restrict the version of the secondary tarballs.
> (Maybe useful for MUT)
> • group requires the downloading upstream tarball to be newer than
> the version obtained from debian/changelog. Package version is the
> concatenation of all "group" upstream version.
> • checksum requires the downloading upstream tarball to be newer than
> the version obtained from debian/changelog. Package version is the
> concatenation of the version of the main tarball, followed by a
> checksum of all the tarballs using the "checksum" version system.
> At least the main upstream source has to be declared as "group".
>
> Then 1.0.2+~0.1.2+~4.7.1 gives: 1.0.2+~cs4.8.3
>
> Cheers
More uscan(1):
To avoid having a too long version, the "checksum" method can be used.
In this case, the main source has to be declared as "group":
version=4
opts="searchmode=plain,pgpmode=none" \
https://registry.npmjs.org/mongodb \
https://registry.npmjs.org/mongodb/-/mongodb-(\d[\d\.]*)@ARCHIVE_EXT@ group
opts="searchmode=plain,pgpmode=none,component=bson" \
https://registry.npmjs.org/bson \
https://registry.npmjs.org/bson/-/bson-(\d[\d\.]*)@ARCHIVE_EXT@ checksum
opts="searchmode=plain,pgpmode=none,component=mongodb-core" \
https://registry.npmjs.org/mongodb-core \
https://registry.npmjs.org/mongodb-core/-/mongodb-core-(\d[\d\.]*)@ARCHIVE_EXT@
checksum
opts="searchmode=plain,pgpmode=none,component=requireoptional" \
https://registry.npmjs.org/require_optional \
https://registry.npmjs.org/require_optional/-/require_optional-(\d[\d\.]*)@ARCHIVE_EXT@
checksum
The "checksum" is made up of the separate sum of each number composing
the component versions. Following is an example with 3 components whose
versions are "1.2.4", "2.0.1" and "10.0", with the main tarball having
version "2.0.6":
Main: 2.0.6
Comp1: 1 . 2 . 4
Comp2: 2 . 0 . 1
Comp3: 10 . 0
================================
Result : 1+2.10 . 2+0+0 . 4+1
Checksum: 13 . 2 . 5
================================
Final Version: 2.0.6+~cs13.2.5
uscan will also display the original version string before being encoded
into the checksum, which can for example be used in a debian/changelog
entry to easily follow the changes:
2.0.6+~1.2.4+~2.0.1+~10.0
Note: This feature currently accepts only versions composed of digits
and full stops (`.`).
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
