public inbox for pve-devel@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: [pve-devel] applied-series: [PATCH manager 0/2] readd TARFILE environment variable in VZDump
Date: Tue, 14 Jul 2020 10:31:39 +0200	[thread overview]
Message-ID: <b76ebcb2-0e79-f4da-f01b-5d4a30db393a@proxmox.com> (raw)
In-Reply-To: <20200714080919.6713-1-s.ivanov@proxmox.com>

On 14.07.20 10:09, Stoiko Ivanov wrote:
> Reported in our community forum:
> https://forum.proxmox.com/threads/vzdump-hook-problem-after-last-update.72889/
> 
> The patchset changes the example hook-script and additionally reintroduces
> the variable TARFILE to not break existing scripts (with a note to drop this
> with PVE 7.0).
> 
> The second patch is there for a smoother experience of the existing users of
> hook-scripts - Maybe we could also just mention it explicitly in the changelog?
> 
> feel free to squash the patches if applying both.
> 
> Stoiko Ivanov (2):
>   vzdump-hook-script: rename TARFILE to TARGET
>   VZDump: add TARFILE to environment for hookscripts
> 
>  PVE/VZDump.pm         | 2 ++
>  vzdump-hook-script.pl | 8 ++++----
>  2 files changed, 6 insertions(+), 4 deletions(-)
> 



applied series, thanks!




      parent reply	other threads:[~2020-07-14  8:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-14  8:09 [pve-devel] " Stoiko Ivanov
2020-07-14  8:09 ` [pve-devel] [PATCH manager 1/2] vzdump-hook-script: rename TARFILE to TARGET Stoiko Ivanov
2020-07-14  8:09 ` [pve-devel] [PATCH manager 2/2] VZDump: add TARFILE to environment for hookscripts Stoiko Ivanov
2020-07-14  8:31 ` 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=b76ebcb2-0e79-f4da-f01b-5d4a30db393a@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal