Bug#756835: First steps towards source-only uploads
Package: debian-policy
Severity: wishlist
Version: 3.9.5.0
Le Fri, Aug 01, 2014 at 12:25:05PM +0200, Ansgar Burchardt a écrit :
> On 08/01/2014 12:17, martin f krafft wrote:
> > also sprach Paul Wise <pabs@debian.org> [2014-08-01 11:33 +0200]:
> >>>> * The source package includes a Package-List field that also has
> >>>> an arch=* column. dpkg (>= 1.17.7) will include this.
> >>>
> >>> Can we read up more on this somewhere?
> >>
> >> It is the default if you are using dpkg-dev from jessie and you don't
> >> need to do anything other than generating your .dsc with dpkg-source
> >> as per usual.
> >
> > I want to understand purpose and syntax of this new field.
>
> The field was originally discussed in https://bugs.debian.org/619131 to
> allow easier processing of packages that build arch-specific binaries
> such as src:linux[1].
>
> The architecture information was only (re)introduced later, as far as I
> know to help with bootstrapping, but it turns out that I also want this
> for source-only uploads to catch uploads introducing NEW binary packages.
Hi Ansgar, Martin, and Policy Editors,
here is a proposed update for the description of the Package-List field
in the Policy's section 5.6.27. (patch attached).
For the busy people, here is the current content of §5.6.27–8.
-----------------------------------------------------------------------------
5.6.27 Package-List
Multiline field listing all the packages that can be built from the source
package, considering every architecture. The first line of the field value is
empty. Each one of the next lines describes one binary package, by listing its
name, type, section and priority separated by spaces. Fifth and subsequent
space-separated items may be present and parsers must allow them. See the
Package-Type field for a list of package types.
5.6.28 Package-Type
Simple field containing a word indicating the type of package: deb for binary
packages and udeb for micro binary packages. Other types not defined here may
be indicated. In source package control files, the Package-Type field should be
omitted instead of giving it a value of deb, as this value is assumed for
paragraphs lacking this field.
-----------------------------------------------------------------------------
Everybody's suggestions are welcome !
Have a nice week-end, and big thank you to Ansgar and the other FTP Masters for
the source-only uploads !
--
Charles Plessy
Debian Med packaging team,
http://www.debian.org/devel/debian-med
Tsurumi, Kanagawa, Japan
>From b1aa1bf72723e4594557f9898da97afe23f0c900 Mon Sep 17 00:00:00 2001
From: Charles Plessy <plessy@debian.org>
Date: Sat, 2 Aug 2014 19:30:57 +0900
Subject: [PATCH] =?UTF-8?q?Document=20the=20=E2=80=98arch=E2=80=99=20and?=
=?UTF-8?q?=20=E2=80=98profile=E2=80=99=20options=20in=20the=20Package-Lis?=
=?UTF-8?q?t=20field.?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
---
policy.sgml | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/policy.sgml b/policy.sgml
index ae9d173..33c4f1a 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -3826,6 +3826,14 @@ Checksums-Sha256:
<qref id="f-Package-Type">Package-Type</qref> field for a list of
package types.
</p>
+ <p>
+ The optional fields currently in use add informations related to
+ architectures build profiles, with a syntax such as
+ <tt>name=value1,value2</tt> and names <tt>arch</tt> and
+ <tt>profile</tt><footnote>
+ They were introduced in <prgn>dpkg</prgn> version
+ <tt>1.17.7</tt> in <em>Jessie</em></footnote>.
+ </p>
</sect1>
<sect1 id="f-Package-Type">
--
2.0.1
Reply to: