Bug#968000: libconfig-model-dpkg-perl: Get policy release dates in another way

Dominique Dumont dod at debian.org
Thu Aug 6 14:43:02 BST 2020


On jeudi 6 août 2020 14:26:13 CEST you wrote:
> Your package is the only known consumer of Lintian's internal Perl
> modules. We would like to stop shipping our modules in the Perl system
> path. 

ok.

> Your package loads a default Lintian profile [1] and uses the
> Lintian::Data mechanism to get the policy release dates from
> data/standard-version/release-dates [2]. 

Actually, only the latest policy number is used by cme (currently 4.5.0)

> It may be tempting to use a
> simpler parser, but please consider that the information actually
> originates somewhere else.

I don't really understand your point there, but it may not matter much (see 
below)

> Attached is a script that extracts the release dates from the policy
> changelog. It uses the network. The data will always be current.

If the source of information is Salsa, I'd rather use gitlab API to extract 
the latest policy version from the tags with something like:

mojo get -r https://salsa.debian.org/api/v4/projects/234/repository/tags \
  /0/name | perl -n -E '/(\d+\.\d+\.\d+)/; say $1;'

Since the data returned by gitlab is JSON, parsing is not much of an issue.

Does that sound reasonable ?

All the best



More information about the pkg-perl-maintainers mailing list