Bug#903905: libconfig-model-dpkg-perl: Failure when d/config contains XS-Ruby-Versions
Dominique Dumont
dod at debian.org
Mon Jul 16 17:45:48 BST 2018
On Monday, 16 July 2018 15:13:05 CEST you wrote:
> Please find a way to deal with XS-Ruby-Versions
Currently, XS-Ruby-Versions is allowed if the Maintainer contains "Debian
Ruby" as in "Debian Ruby Team". It used to be when "section =~ /ruby". (see
#888949)
On one hand I'd like to avoid cluttering the gui of "cme dpkg edit" for non-
ruby packages. On the other hand, finding a sure way to identify that a
package is a ruby package is not so easy.
May be I should try something like
Maintainer =~ /Debian ruby/i or source =~ /^ruby-/
Other ideas are welcome. (except scanning the dependency list which is
difficult in Config::Model)
> (I have no idea about
> Ruby so I'm not sure whether this is a valid / necessary element).
See #713053
> I
> also wonder whether for instance Vcs fields and Standards-Version could
> be changed in any case (that's why I used cme) even if this kind of
> unknown fields are occuring.
Completely unknown fields are supported.
The problem is that you have a situation considered as an error by cme: having
a ruby specific parameter for a non-ruby package.
All the best
More information about the pkg-perl-maintainers
mailing list