From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 514791FF140 for ; Fri, 24 Apr 2026 21:10:38 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 2B0211EE40; Fri, 24 Apr 2026 21:10:38 +0200 (CEST) From: Thomas Lamprecht To: pbs-devel@lists.proxmox.com, Hannes Laimer Subject: applied: [PATCH proxmox-backup] api: create target namespace when moving and it doesn't exist yet Date: Fri, 24 Apr 2026 21:06:50 +0200 Message-ID: <177705760883.3360887.11910404636789148584.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260424112420.207317-1-h.laimer@proxmox.com> References: <20260424112420.207317-1-h.laimer@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1777057742693 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.002 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: BOGOTYZBRZXD2OOS5A2RZVVFB4JRAT6Z X-Message-ID-Hash: BOGOTYZBRZXD2OOS5A2RZVVFB4JRAT6Z X-MailFrom: t.lamprecht@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox Backup Server development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Fri, 24 Apr 2026 13:24:20 +0200, Hannes Laimer wrote: > So the behaviour is the same what a normal `mv` would do. What still > stays required is the existance of the parent to which the namespace is > moved. Applied, thanks! [1/1] api: create target namespace when moving and it doesn't exist yet commit: 6c64dc4922b0b541bb01167d50610965ea234717