cip-dev.lists.cip-project.org archive mirror
 help / color / mirror / Atom feed
From: masashi.kudo@cybertrust.co.jp (masashi.kudo at cybertrust.co.jp)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [cip-core] Package Proposal #2 (Minimum base packages in Debian)
Date: Mon, 20 Jan 2020 00:18:08 +0000	[thread overview]
Message-ID: <OSBPR01MB5127312322C246858BDFBE6EA0320@OSBPR01MB5127.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <CAFa_k0h_716U9+OqYvhO4EBEYO=F6vh-VEvRQEKa+5OK8UQ8fQ@mail.gmail.com>

Hi, Kazu-san,

Agree on this proposal on behalf of Cybertrust.

BTW, libpam-runtime listed as a binary package of pam has a dependency on debconf. The debconf is shown twice. It does not affect the result, but if you have time, please double check the script..

Best regards,
--
M. Kudo

From: <kazuhiro3.hayashi@toshiba.co.jp<mailto:kazuhiro3.hayashi@toshiba.co.jp>>
Date: 2020?1?16?(?) 17:25
Subject: [cip-dev] [cip-core] Package Proposal #2 (Minimum base packages in Debian)
To: <cip-dev at lists.cip-project.org<mailto:cip-dev@lists.cip-project.org>>


Hello CIP Core members,

I created a simple package proposal for the packages that are installed in the "minimum base system" of Debian.
These packages are installed by
        $ debootstrap --variant=minbase buster ...

It consists of 58 source packages and 84 binary packages, including all run-time dependencies.

The common reason to propose:
"This package is included in the minimum base system of Debian (debootstrap --variant=minbase),
which is essential for all Debian binary package based systems"


I would like to start the "review" phase (Phase 2) of the attached package proposal.
https://gitlab.com/cip-project/cip-core/cip-pkglist/blob/master/doc/pdp.md#phase-2-proposal-review

Please reply with you opinion, agree or disagree.
If you cannot agree to add specific packages, please show the reasons as well.

Due Date: January 20th (The next TSC meeting)

We have only 2-3 working days for this review, but
I think it may be enough to agree or disagree the very simple reason above.
(We can extend this due date if more time required for reviews, please let me know if any requests)

Best regards,
Kazu
_______________________________________________
cip-dev mailing list
cip-dev at lists.cip-project.org<mailto:cip-dev@lists.cip-project.org>
https://lists.cip-project.org/mailman/listinfo/cip-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20200120/c7fb20ab/attachment.html>

  parent reply	other threads:[~2020-01-20  0:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-16  8:25 [cip-dev] [cip-core] Package Proposal #2 (Minimum base packages in Debian) kazuhiro3.hayashi at toshiba.co.jp
2020-01-19  8:25 ` Jan Kiszka
     [not found] ` <CAFa_k0h_716U9+OqYvhO4EBEYO=F6vh-VEvRQEKa+5OK8UQ8fQ@mail.gmail.com>
2020-01-20  0:18   ` masashi.kudo at cybertrust.co.jp [this message]
2020-01-20 14:24     ` kazuhiro3.hayashi at toshiba.co.jp
2020-01-21  0:52 ` kazuhiro3.hayashi at toshiba.co.jp
2020-01-23  8:07   ` Takehisa Katayama
2020-01-23 11:52     ` kazuhiro3.hayashi at toshiba.co.jp
2020-01-27  0:33       ` Laurence Urhegyi
2020-01-27 13:52       ` SZ Lin (林上智)
2020-01-31 14:44       ` SZ Lin (林上智)
2020-02-04 11:48       ` kazuhiro3.hayashi at toshiba.co.jp
2020-02-11  5:39         ` kazuhiro3.hayashi at toshiba.co.jp

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=OSBPR01MB5127312322C246858BDFBE6EA0320@OSBPR01MB5127.jpnprd01.prod.outlook.com \
    --to=masashi.kudo@cybertrust.co.jp \
    --cc=cip-dev@lists.cip-project.org \
    /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).