From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Stoiko Ivanov <s.ivanov@proxmox.com>
Subject: [pve-devel] applied-series: [PATCH zfsonlinux 0/2] split out libpam-zfs and update copyright
Date: Thu, 11 Feb 2021 18:21:08 +0100 [thread overview]
Message-ID: <b3d49731-0257-35b2-f7b7-00d47522a515@proxmox.com> (raw)
In-Reply-To: <20210209184144.29177-1-s.ivanov@proxmox.com>
On 09.02.21 19:41, Stoiko Ivanov wrote:
> With ZFS 2.0.0 upstream ships a pam module, which uses an users login password
> to optionally decrypt their home dataset.
>
> Debian upstream ships the config in a separate package, which seems cleaner
> than adding it to zfsutil-linux.
>
> This patchset adapts the commit to our repo. While at it I noticed that
> our debian/copyright file got a bit out-of-sync with debian's and pulled
> their version in (additionally adding Proxmox for the files in debian/*)
>
> Thanks to Fabian for catching this and pointing me in the right direction!
>
> Stoiko Ivanov (2):
> buildsys: make libpam-zfs a separate package
> update debian/copyright
>
> debian/control | 14 +
> debian/copyright | 840 +++++++++++-----------------------
> debian/libpam-zfs.install | 2 +
> debian/libpam-zfs.postinst | 6 +
> debian/libpam-zfs.prerm | 8 +
> debian/zfsutils-linux.install | 2 -
> 6 files changed, 301 insertions(+), 571 deletions(-)
> create mode 100644 debian/libpam-zfs.install
> create mode 100644 debian/libpam-zfs.postinst
> create mode 100644 debian/libpam-zfs.prerm
>
applied series, thanks!
prev parent reply other threads:[~2021-02-11 17:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 18:41 [pve-devel] " Stoiko Ivanov
2021-02-09 18:41 ` [pve-devel] [PATCH zfsonlinux 1/2] buildsys: make libpam-zfs a separate package Stoiko Ivanov
2021-02-09 18:41 ` [pve-devel] [PATCH zfsonlinux 2/2] update debian/copyright Stoiko Ivanov
2021-02-11 17:21 ` Thomas Lamprecht [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=b3d49731-0257-35b2-f7b7-00d47522a515@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.ivanov@proxmox.com \
/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