Bug#991533: Don't require Standards-Version field when only udebs Standards-Version for udeb packages

[Sean Whitton <spwhitton@spwhitton.name>]

Package: debian-policy

[resending to submit@; can't clone merged bug]

Hello,

On Thu 12 Aug 2021 at 11:47PM +02, Cyril Brulebois wrote:

> Sean Whitton <spwhitton@spwhitton.name> (2021-08-12):
>> On Tue 27 Jul 2021 at 08:41AM -06, Sam Hartman wrote:
>>
>> >
>> > So, it seems fairly obvious to me that Standards-Version is important
>> > for packages that produce both debs and udebs.
>> > I'm assuming the focus of our discussion then is on source packages that
>> > only produce udebs.
>> > Have I got that right?
>> >
>> > By definition, most of the policy that affects binary packages does not
>> > inherently apply to udebs.  As I understand it, that's kind of the point
>> > of udebs.
>>
>> Would you agree with this?  You're only asking to stop seeing warnings
>> about S-V for source packages which produce only udebs?
>
> Yes, that looks good to me: source packages (also) producing debs would
> deserve a rightful nag.

I believe that we failed to consider udebs when we made the change which
made S-V mandatory.  I propose we remove the requirement for S-V in
udebs and source packages producing only udebs, until and unless someone
provides a positive argument why S-V ought to be mandatory in these
cases too.

(Cloning the bug but not writing a patch right now; someone else should
feel free to.)

-- 
Sean Whitton