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>,
	"Fabian Grünbichler" <f.gruenbichler@proxmox.com>
Subject: [pve-devel] applied: [PATCH zfsonlinux 2/2] d/control: add transitional zfs-dbg package
Date: Wed, 21 Jul 2021 11:12:20 +0200	[thread overview]
Message-ID: <7334bf8b-398d-f7dd-ec4c-b936cc7f7799@proxmox.com> (raw)
In-Reply-To: <20210721081246.1767859-2-f.gruenbichler@proxmox.com>

On 21.07.21 10:12, Fabian Grünbichler wrote:
> suggesting the new -dbgsym packages without having a strict dependency
> on a specific version of the library packages, like the old no longer
> built zfs-dbg package had.
> 
> this commit can be reverted after the package has been uploaded once, or
> kept for one release cycle if we might do the -dbgsym migration in
> oldstable as well to avoid the oldstable zfs-dbg package version
> overtaking the transitional one here.
> 
> Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
> ---
> 
> Notes:
>     it only suggests to avoid pulling in new, unneeded libraries via their -dbgsym
>     packages (e.g., libpam-zfs is not installed by default)
> 
>     tested with a downgrade to zfs 2.0.4-pve1 including zfs-dbg and then
>     upgrading.
> 
>  debian/control | 14 ++++++++++++++
>  1 file changed, 14 insertions(+)
> 
>

applied, thanks!




  reply	other threads:[~2021-07-21  9:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-21  8:12 [pve-devel] [PATCH zfsonlinux 1/2] build: switch upload target to bullseye Fabian Grünbichler
2021-07-21  8:12 ` [pve-devel] [PATCH zfsonlinux 2/2] d/control: add transitional zfs-dbg package Fabian Grünbichler
2021-07-21  9:12   ` Thomas Lamprecht [this message]
2021-07-21  9:12 ` [pve-devel] applied: [PATCH zfsonlinux 1/2] build: switch upload target to bullseye 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=7334bf8b-398d-f7dd-ec4c-b936cc7f7799@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=f.gruenbichler@proxmox.com \
    --cc=pve-devel@lists.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