Hello,
this could be due to an incomplete fix for bug #999768 or maybe it
is caused by some other bug.

Anyway, I have:

  $ grep -n Ruby-Versions debian/control
  9:XS-Ruby-Versions: all
  16:XB-Ruby-Versions: ${ruby:Versions}

in my package ('apt-listbugs').

Running "lintian -EviIL +pedantic" on the .changes file generates
the following reports:

  N:
  W: apt-listbugs source: unknown-field Ruby-Versions
  N:
  N:   See the Policy Manual for a list of the possible fields in a package
  N:   control files.
  N:
  N:   Please refer to Binary package control files – DEBIAN/control (Section
  N:   5.3) in the Debian Policy Manual and Debian source control files – .dsc
  N:   (Section 5.4) in the Debian Policy Manual for details.
  N:
  N:   Visibility: warning
  N:   Show-Always: no
  N:   Check: fields/unknown
  N:   Renamed from: unknown-field-in-dsc unknown-field-in-control
  N:
  N:
  I: apt-listbugs source: adopted-extended-field (in section for apt-listbugs) XB-Ruby-Versions [debian/control:16]
  N:
  N:   A field in debian/control has an extension prefix but is also known
  N:   without it.
  N:
  N:   Extension prefixes like XS-* or XC-* allow experimental fields to
  N:   propagate to the right place when packages are built with dpkg. In this
  N:   case, however, the field is also known without the prefix. In all
  N:   likelihood the field was permanently adopted, and dpkg learned how to deal
  N:   with it.
  N:
  N:   Please consider removing the extension prefix for the field name.
  N:
  N:   Visibility: info
  N:   Show-Always: no
  N:   Check: debian/control/field/adopted
  N:   Renamed from: xc-package-type-in-debian-control
  N:   xs-testsuite-field-in-debian-control xs-vcs-field-in-debian-control
  N:


Both reports look wrong, since I have no plain 'Ruby-Versions'
field in my package source, and 'XB-Ruby-Versions' has not been
adopted, thus requiring the 'XB-' prefix.

Please fix this bug in lintian.
Thanks for your time and patience!

On Fri, 12 Aug 2022 18:03:50 +0200 Francesco Poli (wintermute) wrote:

[...]

This bug is still present in the lintian version currently in sid.
Please fix it.

On Sun, 9 Oct 2022 19:29:30 +0200 Francesco Poli wrote:

[...]

Hello again,
XS-Ruby-Versions and XB-Ruby-Versions are now deprecated, see the
changelog entry for package [gem2deb/2.1].

[gem2deb/2.1]: <https://tracker.debian.org/news/1392420/accepted-gem2deb-21-source-into-unstable/>

As a consequence, I think that lintian should no longer point out that
either of those two fields is adopted (which is not the case), but, if
anything, it should point out that those two fields are deprecated and
need to be dropped...

Do you agree? Please let me know.

Thanks for your time and patience.
Bye (and Season's Greetings!).

Hello,

The latest release tried to fix this completely. But even then, I can't see this with
older release either.

https://udd.debian.org/lintian-tag/unknown-field?affected=yes does not list even a single
package with Ruby-Versions.

I took an example of src:hiera package which has XB-Ruby-Versions declared and I do not
see this hint being emitted in the lintian run with version 2.138.0, at the time of
writing this mail.

See https://udd.debian.org/lintian/?email1=&email2=&email3=&packages=hiera&ignpackages=&format=html<_error=on<_warning=on<_information=on<_pedantic=on<_experimental=on<_overridden=on&lintian_tag=#all

So I think this got fixed at some point, unsure of the timeline. Hence, I am closing this bug.

If you are still able to reproduce this, please re-open this bug.

Thank you for reporting,
Nilesh

Control: found -1 lintian/2.138.0

Hi, thanks for following up on this bug report.

Maybe I am misinterpreting what you mean, but I see the complaint `adopted-extended-field` being emitted by `lintian/2.138.0` for package `src:hiera`.

And it seems to me that it is [emitted] for a number of other packages
having `XB-Ruby-Versions` set in their control file. For instance,
packages `batalert`, `bio-vcf`, `fontcustom`, many `ruby-*` package,
and so forth...

[emitted]: <https://udd.debian.org/lintian-tag/adopted-extended-field?affected=yes>

It seems that `lintian/2.138.0` runs are still able to emit the
complaint `adopted-extended-field`, when finding field
`XB-Ruby-Versions` in the control file.

As I [said], I think that lintian should now point out that the two
fields `XS-Ruby-Versions` and `XB-Ruby-Versions` are deprecated and
need to be dropped...

[said]: <https://bugs.debian.org/1017064#17>

Do you agree?

Control: reopen -1
Control: found -1 lintian/2.139.0

D'oh! You are indeed right. I did not look properly here and was looking at the wrong tag.
It is reproducible even in the latest upload. The attempt to unify
source and binary control fields is leading to all of this.

Yes, but please file a separate bug report for this.

Best,
Nilesh