From: Masahiro Yamada <masahiroy@kernel.org>
To: Guillem Jover <guillem@hadrons.org>
Cc: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ben Hutchings <ben@decadent.org.uk>
Subject: Re: [PATCH 0/7] builddeb: Improve Debian packaging
Date: Tue, 29 Sep 2020 00:21:41 +0900 [thread overview]
Message-ID: <CAK7LNAT_itc2RWzr5b3sSnYmJ9BhcqGyVDYUcF=K9S8RyM=GMA@mail.gmail.com> (raw)
In-Reply-To: <20200920222556.10002-1-guillem@hadrons.org>
(+CC Ben)
On Mon, Sep 21, 2020 at 7:48 AM Guillem Jover <guillem@hadrons.org> wrote:
>
> Hi!
>
> This series fixes some packaging issues and brings it closer to
> current standards.
I am not tracking the latest development in the Debian project.
Could you give me a little more context about
what you call "current standards" ?
(It is defined in Debian Policy, or accepted as DEP-*, etc.)
For example, as for "3/7: machine-readable debian/copyright",
it is DEP-5, and can be mentioned in the commit log
for clarification.
What is the rationale for "2/7: debian/upstream/metadata" ?
Ben:
If possible, could you take a look at this series?
> Thanks,
> Guillem
>
> Guillem Jover (7):
> builddeb: Pass -n to gzip for reproducible packages
> builddeb: Move upstream repository URL into the upstream metadata file
> builddeb: Switch to a machine readable copyright file
> builddeb: Add support for all required debian/rules targets
> builddeb: Enable rootless builds
> builddeb: Map rc versions to use an earlier than version scheme
> builddeb: Try to get the user full name from the GECOS field
>
> scripts/package/builddeb | 11 ++++++--
> scripts/package/mkdebian | 59 +++++++++++++++++++++++++++-------------
> 2 files changed, 48 insertions(+), 22 deletions(-)
>
> --
> 2.28.0.297.g1956fa8f8d
>
--
Best Regards
Masahiro Yamada
prev parent reply other threads:[~2020-09-28 15:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-20 22:25 [PATCH 0/7] builddeb: Improve Debian packaging Guillem Jover
2020-09-20 22:25 ` [PATCH 1/7] builddeb: Pass -n to gzip for reproducible packages Guillem Jover
2020-10-09 14:58 ` Masahiro Yamada
2020-09-20 22:25 ` [PATCH 2/7] builddeb: Move upstream repository URL into the upstream metadata file Guillem Jover
2020-09-20 22:25 ` [PATCH 3/7] builddeb: Switch to a machine readable copyright file Guillem Jover
2020-09-28 15:11 ` Masahiro Yamada
2020-09-20 22:25 ` [PATCH 4/7] builddeb: Add support for all required debian/rules targets Guillem Jover
2020-10-09 15:46 ` Masahiro Yamada
2020-09-20 22:25 ` [PATCH 5/7] builddeb: Enable rootless builds Guillem Jover
2020-10-09 15:46 ` Masahiro Yamada
2020-09-20 22:25 ` [PATCH 6/7] builddeb: Map rc versions to use an earlier than version scheme Guillem Jover
2020-09-20 22:25 ` [PATCH 7/7] builddeb: Try to get the user full name from the GECOS field Guillem Jover
2020-09-28 15:21 ` Masahiro Yamada [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAK7LNAT_itc2RWzr5b3sSnYmJ9BhcqGyVDYUcF=K9S8RyM=GMA@mail.gmail.com' \
--to=masahiroy@kernel.org \
--cc=ben@decadent.org.uk \
--cc=guillem@hadrons.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).