From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: pbs-devel@lists.proxmox.com, pve-devel@lists.proxmox.com,
Stoiko Ivanov <s.ivanov@proxmox.com>
Subject: [pve-devel] applied: [pbs-devel] [PATCH proxmox-backup/proxmox-backup-restore-image] update and adapt to ZFS 2.3 and kernel 6.14
Date: Tue, 3 Jun 2025 10:59:03 +0200 [thread overview]
Message-ID: <174894109324.475518.9980338030060022350.b4-ty@proxmox.com> (raw)
In-Reply-To: <20250602094756.519927-1-s.ivanov@proxmox.com>
On Mon, 02 Jun 2025 11:47:50 +0200, Stoiko Ivanov wrote:
> While checking our codebase for potential uses of non-usr-merged paths
> for ZFS I noticed the file-restore uses absolute paths for most commands.
>
> As the daemon runs in an isolated environment we provide sticking to
> absolute paths, instead of adding a PATH variable for Command::new to
> search seems a sensible option.
>
> [...]
Applied with a small (unrelated) fixup to unbreak building in sbuild, thanks!
[1/5] build initramfs: usr-merge initramfs
commit: 80f9c6bb6c0f57335e668dd0d00047ecb0208e3b
[2/5] update ZFS to 2.3.2
commit: 2e15f400e6cd1346eabd91173379c637656fb9f9
[3/5] build initramfs: remove additional ZFS scripts
commit: 981c292d479e972a215e564822c8b0b865acfd2d
[4/5] update ubuntu-kernel to Ubuntu-6.14.0-22.22
commit: e0e3f3a69b39cd9f6bdb5ba609fbcee3d147f315
[5/5] kernel: enable more filesystem options
commit: 1bab5440e4bf7744d3418ede065c56463d385933
Best regards,
--
Fabian Grünbichler <f.gruenbichler@proxmox.com>
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-06-03 8:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-02 9:47 [pve-devel] " Stoiko Ivanov
2025-06-02 9:47 ` [pve-devel] [PATCH proxmox-backup-restore-image 1/5] build initramfs: usr-merge initramfs Stoiko Ivanov
2025-06-02 9:47 ` [pve-devel] [PATCH proxmox-backup-restore-image 2/5] update ZFS to 2.3.2 Stoiko Ivanov
2025-06-02 9:47 ` [pve-devel] [PATCH proxmox-backup-restore-image 3/5] build initramfs: remove additional ZFS scripts Stoiko Ivanov
2025-06-02 9:47 ` [pve-devel] [PATCH proxmox-backup-restore-image 4/5] update ubuntu-kernel to Ubuntu-6.14.0-22.22 Stoiko Ivanov
2025-06-02 9:47 ` [pve-devel] [PATCH proxmox-backup-restore-image 5/5] kernel: enable more filesystem options Stoiko Ivanov
2025-06-02 9:47 ` [pve-devel] [PATCH proxmox-backup 1/1] restore-daemon: adapt to zpool output changes in 2.3 Stoiko Ivanov
2025-06-03 8:59 ` Fabian Grünbichler [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=174894109324.475518.9980338030060022350.b4-ty@proxmox.com \
--to=f.gruenbichler@proxmox.com \
--cc=pbs-devel@lists.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