Bug#994008: debian-policy: Clarify relationship between source and binary packages' archive areas

On Thu, 2021-09-09 at 12:48 -0700, Sean Whitton wrote: > > But source packages in main must also produce at least one binary > > package in main[1]. > > Let's include that point in Policy. > > > [1]: Probably with the default build profile if we care about corner > >    cases. > > Are we sur

Bug#994008: debian-policy: Clarify relationship between source and binary packages' archive areas

Hello, On Thu 09 Sep 2021 at 09:15PM +02, Ansgar wrote: > On Thu, 2021-09-09 at 17:39 +0100, Simon McVittie wrote: >> >> ftp team: is this correct? > > Yes. Indeed. > But source packages in main must also produce at least one binary > package in main[1]. Let's include that point in Policy. >

Bug#994008: debian-policy: Clarify relationship between source and binary packages' archive areas

Hi, On Thu, 2021-09-09 at 17:39 +0100, Simon McVittie wrote: > In the form of a table, the allowed source/binary combinations are: > >   |    binary   | >   | main  contrib  non-free | > -|-| >   

Bug#994008: debian-policy: Clarify relationship between source and binary packages' archive areas

Package: debian-policy Version: 4.6.0.1 Severity: wishlist Tags: patch X-Debbugs-Cc: ftpmas...@debian.org If you have an upstream project consisting of Free source code with a mixture of Free and non-Free dependencies, it isn't currently clear how that should be packaged. For example, if gnome-so