On Tuesday, 21 June 2022 22:40:52 CEST gregor herrmann wrote:
> > Would that work out for you?
>
> Yup.
> I'm cc'ing dod as the Config::Model::* tsar to make sure I'm not
> missing anything.
All good. Thanks for the follow-up
> > If so: What are your requirements for such a transition? Do we
On Tue, 21 Jun 2022 19:35:42 +0200, Axel Beckert wrote:
> chiming in as the new Lintian maintainer. :-)
Thanks, both for caring about lintian and about
libconfig-model-dpkg-perl :)
> private/latest-policy-version also seems to be the current way, how
> libconfig-model-dpkg-perl interacts with
Hi,
chiming in as the new Lintian maintainer. :-)
Felix Lechner wrote:
> Your package is the only known consumer of Lintian's internal Perl
> modules. []
I haven't read all the discussion in this bug report, but I stumbled
upon it due to these lines in debian/lintian.install:
# the next line
On Wed, 08 Sep 2021 18:46:19 +0200, Dominique Dumont wrote:
> Back to gregoa's proposal...
:)
> > - I'd appreciate review from dod
> This regexp may be too strict:
> $std_ver =~ s|^(\d+\.\d+\.\d+)\.\d+$|$1|;
>
> I don't know if policy people are committed to used 4 digits version.
Good
Hi
Re-reading the thread of this bug, there's still the solution based on
debian-policy. Even though there's still no file that provide the policy
version, this one can be extracted from debian-policy changelog with something
like:
$ zcat /usr/share/doc/debian-policy/changelog.gz | head -1 |
Hi,
On Wed, Sep 8, 2021 at 8:49 AM gregor herrmann wrote:
>
> Implemented in git, but not uploaded because
Thanks for looking at it so promptly, and sorry I did not also submit
an MR like you had asked.
> Now of course we can strip off the fourth level ourselves
If Lintian becomes a data
On Tue, 07 Sep 2021 17:40:03 -0700, Felix Lechner wrote:
> As a courtesy to this package (and to the policy team) Lintian now
> ships an executable "/usr/share/lintian/private/latest-policy-version"
> that provides the latest policy information. [3] Please use that
> executable to obtain the
Hi,
On Fri, Dec 4, 2020 at 7:24 PM gregor herrmann wrote:
>
> Could we maybe wait for a fix for #968154 in debian-policy?
I'm not sure what the policy team's intentions are, but Lintian's Data
module no longer provides the policy information. [1] We now keep the
data in a JSON file that is more
On Thu, 03 Dec 2020 21:42:33 -0800, Felix Lechner wrote:
> Please have a look at this commit. It explains how to mitigate
> expected upcoming breakage in your package.
>
>
> https://salsa.debian.org/lintian/lintian/-/commit/d2f692f564ac725a0eb58a7d62abe57f66cdc753
>
> Please load the policy
Hi,
> On Saturday, 8 August 2020 23:40:51 CEST gregor herrmann wrote:
> > I think having the data provided by debian-policy (in the package,
> > and maybe-for other purposes-also on the website) would be an
> > excellent idea, thanks for the offer.
Please have a look at this commit. It explains
Control: clone -1 -2
Control: reassign -2 debian-policy
Control: retitle -2 debian-policy: please provide file with policy release
versions and dates
Control: severity -2 wishlist
Control: block -1 with -2
Control: affects -2 + libconfig-model-dpkg-perl
On Sun, 09 Aug 2020 20:36:16 +0200,
On Saturday, 8 August 2020 23:40:51 CEST gregor herrmann wrote:
> I think having the data provided by debian-policy (in the package,
> and maybe-for other purposes-also on the website) would be an
> excellent idea, thanks for the offer.
Agreed. It's better than hitting madison regularly to get
On Fri, 07 Aug 2020 17:14:30 -0700, Russ Allbery wrote:
> > What I'm wondering is:
> > - depending on debian-policy would be another dependency, and the
> > debian-policy only installs files to /usr/share/doc which is not
> >guaranteed to exist; and there's also no easily parsable file
gregor herrmann writes:
> Right, except that this also doesn't work at build time.
> But if we skip the test phase that would be ok.
> What I'm wondering is:
> - depending on debian-policy would be another dependency, and the
> debian-policy only installs files to /usr/share/doc which is not
On Thu, 06 Aug 2020 17:09:13 +0200, Dominique Dumont wrote:
> On jeudi 6 août 2020 16:56:17 CEST you wrote:
> > I figured. How about depending on debian-policy and using the
> > information in its changelog?
> Actually, I could use rmadison to get the latest version of debian-policy
> without
Hi Dominique,
On Thu, Aug 6, 2020 at 8:10 AM Dominique Dumont wrote:
>
> Please wait until the next release of libconfig-model-dpkg-perl.
No rush, please. We will keep shipping the modules until you close
this bug. Thank you!
Kind regards
Felix Lechner
On jeudi 6 août 2020 16:56:17 CEST you wrote:
> I figured. How about depending on debian-policy and using the
> information in its changelog?
Actually, I could use rmadison to get the latest version of debian-policy
without installing this package (like rmadison is used to get the version of
On jeudi 6 août 2020 16:11:22 CEST you wrote:
> Unless you advise otherwise, Lintian will stop shipping the modules in
> the system path in the next release.
Please wait until the next release of libconfig-model-dpkg-perl.
All the best
Hi gregor,
On Thu, Aug 6, 2020 at 7:28 AM gregor herrmann wrote:
>
> having the
> version in a file was the big advantage of using the lintian data.
I figured. How about depending on debian-policy and using the
information in its changelog?
Kind regards
Felix Lechner
On Thu, 06 Aug 2020 15:43:02 +0200, Dominique Dumont wrote:
> > 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
Hi Dominique,
On Thu, Aug 6, 2020 at 6:43 AM Dominique Dumont wrote:
>
> Does that sound reasonable ?
First of all, thanks for your swift reply!
I have no preference how the package gets the information. I suggested
a solution only in order to appear helpful. Thanks for addressing it
so
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
Package: libconfig-model-dpkg-perl
Severity: normal
Hi,
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. Here is another way to get the information you require.
Your package loads a default Lintian
23 matches
Mail list logo
