all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Stoiko Ivanov <s.ivanov@proxmox.com>
Subject: Re: [pve-devel] [PATCH zfsonlinux] update submodule and patches for to zfs-0.8.5
Date: Wed, 7 Oct 2020 18:26:54 +0200	[thread overview]
Message-ID: <98e9a848-25e4-33db-a106-769fa2d63c82@proxmox.com> (raw)
In-Reply-To: <20201007142815.19925-1-s.ivanov@proxmox.com>

On 07.10.20 16:28, Stoiko Ivanov wrote:
> upstream commit 2d2ce04b9931927ffd045f9ebba3d39d4d31f7db changed the location
> for installing pkgconfig files to the architecture specific one in /lib
> instead of /usr/share - this patch reflects the change in
> 'debian/libzfslinux-dev.install'.
> 
> It follows the change from 9a04c500f17d8df20a017137211d0984cace98ff in
> debian's repository [0].
> 
> [0] https://salsa.debian.org/zfsonlinux-team/zfs.git
> 
> Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
> ---
> did some very rough tests in a VM (container snapshot+rollback) and am
> currently running it on my host.
> Most commits are to enable compilation with newer kernel versions and minor
> bugfixes
> 
>  debian/libzfslinux-dev.install | 2 +-
>  upstream                       | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/debian/libzfslinux-dev.install b/debian/libzfslinux-dev.install
> index efc2bc2b..1a74689a 100644
> --- a/debian/libzfslinux-dev.install
> +++ b/debian/libzfslinux-dev.install
> @@ -1,4 +1,4 @@
>  lib/*.a usr/lib/
>  usr/include
>  usr/lib/*.so
> -usr/share/pkgconfig/*.pc
> +lib/pkgconfig/*.pc usr/lib/pkgconfig/
> diff --git a/upstream b/upstream
> index 6b18d7df..55548516 160000
> --- a/upstream
> +++ b/upstream
> @@ -1 +1 @@
> -Subproject commit 6b18d7df3772cffa6469b00866d7eae585b912ae
> +Subproject commit 55548516595dee39906c747b73f5a2712a61aba8
> 

this is the wrong commit ref, probably one made before the actual release,
superseded with a newer one through a force push  (educated guess).

The actual one seems to be d2632f0cc196a685428115ab023bf4fe3d8e5806 [0][1]

[0]: https://github.com/openzfs/zfs/releases/tag/zfs-0.8.5
[1]: https://github.com/openzfs/zfs/commit/d2632f0cc196a685428115ab023bf4fe3d8e5806




  reply	other threads:[~2020-10-07 16:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-07 14:28 Stoiko Ivanov
2020-10-07 16:26 ` Thomas Lamprecht [this message]
2020-10-08  8:27 ` [pve-devel] applied: " Thomas Lamprecht

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=98e9a848-25e4-33db-a106-769fa2d63c82@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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal