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/4] match library package names with d.o. and minor cleanups
Date: Thu, 25 Feb 2021 12:14:59 +0100 [thread overview]
Message-ID: <f25ebf44-6aad-9350-b1fe-21772b506638@proxmox.com> (raw)
In-Reply-To: <20210224210802.8425-1-s.ivanov@proxmox.com>
On 24.02.21 22:07, Stoiko Ivanov wrote:
> I noticed that debian.org ships differently named packages for the zfs
> libraries. I overlooked the change from e.g. libnvpair2 to libnvpair3
> during the zfs-2.0.0 preparation somehow - sorry!
>
> In order to not cause even more confusion (by being the only distro that
> ships libnvpair2linux) the first patch aligns our package names with d.o
>
> the remaining patches are mostly cosmetic cleanups picked up while diffing
> d/rules with upstream. The added checkabi test seemed quick enough and
> potentially worth it.
>
> Stoiko Ivanov (4):
> d/control: match package names to debian-upstream
> d/rules: cosmetic cleanups minimize diff with d.o.
> d/rules: drop unneeded UDEB conditionals
> buildsys: validate ABI at build time
>
applied, thanks!
prev parent reply other threads:[~2021-02-25 11:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 21:07 [pve-devel] " Stoiko Ivanov
2021-02-24 21:07 ` [pve-devel] [PATCH zfsonlinux 1/4] d/control: match package names to debian-upstream Stoiko Ivanov
2021-02-24 21:08 ` [pve-devel] [PATCH zfsonlinux 2/4] d/rules: cosmetic cleanups minimize diff with d.o Stoiko Ivanov
2021-02-24 21:08 ` [pve-devel] [PATCH zfsonlinux 3/4] d/rules: drop unneeded UDEB conditionals Stoiko Ivanov
2021-02-24 21:08 ` [pve-devel] [PATCH zfsonlinux 4/4] buildsys: validate ABI at build time Stoiko Ivanov
2021-02-25 11:14 ` 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=f25ebf44-6aad-9350-b1fe-21772b506638@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.