Bug#798359: lintian: list of autopkgtest restrictions is not up-to-date

Package: lintian Version: 2.5.36.1 Hi! It seems that the list of known restrictions for debian/tests/control is not up-to-date. Several packages raise unknown-runtime-tests-restriction [1] despite using restrictions properly listed in the reference documentation [2]. [1]:

Bug#798359: lintian: list of autopkgtest restrictions is not up-to-date

* Axel Beckert , 2015-09-08, 20:33: P: cedar-backup2 source: unknown-runtime-tests-restriction allow-stderr, paragraph starting at line 18 But allow-stderr is in all Restrictions, not only in the one in line 18. So it seems the comma after "allow-stderr" which seems to

Bug#798359: lintian: list of autopkgtest restrictions is not up-to-date

Control: unmerge -1 Control: tag -1 + pending Hi again, Axel Beckert wrote: > > >P: cedar-backup2 source: unknown-runtime-tests-restriction allow-stderr, > > >paragraph starting at line 18 > > > > > >But allow-stderr is in all Restrictions, not only in the one in > > >line 18. So it seems the

Bug#798359: lintian: list of autopkgtest restrictions is not up-to-date

Control: retitle -1 lintian: unknown-runtime-tests-restriction reports comma-delimited known restrictions Hi again, Axel Beckert wrote: > Jérémy Bobbio wrote: > > It seems that the list of known restrictions for debian/tests/control is > > not up-to-date. > > > > Several packages raise

Bug#798359: lintian: list of autopkgtest restrictions is not up-to-date

Control: merge -1 792418 Hi Jakub, Jakub Wilk wrote: > * Axel Beckert , 2015-09-08, 20:33: > >P: cedar-backup2 source: unknown-runtime-tests-restriction allow-stderr, > >paragraph starting at line 18 > > > >But allow-stderr is in all Restrictions, not only in the one in > >line

Bug#798359: lintian: list of autopkgtest restrictions is not up-to-date

Hi Lunar, Jérémy Bobbio wrote: > It seems that the list of known restrictions for debian/tests/control is > not up-to-date. > > Several packages raise unknown-runtime-tests-restriction [1] despite > using restrictions properly listed in the reference documentation [2]. > > [1]: