Bug#1042463: lintian does not accept overrides in the syntax used on ftp-master
Control: tag -1 + moreinfo
Hi Julian,
Julian Andres Klode wrote:
> lintian in the archive needs to restore support for the old override
> format, or ftpmaster needs to be updated to the new lintian.
We had a lengthy discussion about the override format changes made by
Felix (see https://bugs.debian.org/1007002) and there's no way back
(including "backwards compatibility") unless someone volunteers to
implement a fix for this. (I won't do that as mentioned in this
thread. See also below for some reasoning.)
> Normal source-only uploads do not trigger the issue usually, but
> there surely have been people adopting their overrides to the new
> format who now get stuck (like me) at binary-NEW with a reject when
> having to do a binary upload.
Please give an explicit example. I'm not sure if you and me think of
the same "new" and "old" format. → Tagged as "moreinfo".
As mentioned in #1007002 there's a script in the migrate-overrides
branch of https://salsa.debian.org/lintian/lintian/ which can
automatically migrate tags in override files.
But so far it only knows a few of the very annoying tags — which is also
the reason it's not in the package yet.
But I'm willing to extend that script and maybe even implement a mode
for ftp-masters if I get an example of a file which needs to be
migrated (including file name and maybe default path).
But for that I need old real-life examples. (Maybe ftp-masters can
give me the file/list Julian mentioned or tell me where to find it?)
> For an orderly transition, lintian needs to […]
Please tell this the previous lintian lead developer who decided and
implemented this inmidst of tons of other invasive changes (like
rewriting Lintian's internal module structure) without doing a release
for months or doing a release after one of these invasive changes.
It's anything but a simple "git revert" to get the old format back.
And a compatibility mode would require implementing the old override
format in the new framework from scratch.
Short said: IMHO we should do a forward escape instead of trying to
implement a very work-intensive backwards compatibility. For which we
don't seem to have the resources anyway unless someone volunteers.
Regards, Axel
--
,''`. | Axel Beckert <abe@debian.org>, https://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Reply to: