From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH manager] network-interface-pinning: fix creating directory when '/usr/local/lib' does not exist
Date: Mon, 17 Nov 2025 11:40:37 +0100 [thread overview]
Message-ID: <f46738e2-a481-4748-948a-e0aebebfee41@proxmox.com> (raw)
In-Reply-To: <38ec0df7-dc52-4405-ae83-7a6e7b7ded59@proxmox.com>
Ping
Am 14.10.25 um 3:00 PM schrieb Fiona Ebner:
> Ping
>
> Am 15.09.25 um 2:38 PM schrieb Fiona Ebner:
>> Am 15.09.25 um 2:29 PM schrieb Fiona Ebner:
>>> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
>>> ---
>>
>> Intended for both, master and stable-8.
>>
>>> PVE/CLI/pve_network_interface_pinning.pm | 4 ++--
>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/PVE/CLI/pve_network_interface_pinning.pm b/PVE/CLI/pve_network_interface_pinning.pm
>>> index fe803f33..a99fdafe 100644
>>> --- a/PVE/CLI/pve_network_interface_pinning.pm
>>> +++ b/PVE/CLI/pve_network_interface_pinning.pm
>>> @@ -3,6 +3,7 @@ package PVE::CLI::pve_network_interface_pinning;
>>> use v5.36;
>>>
>>> use File::Copy;
>>> +use File::Path qw(make_path);
>>> use POSIX qw(:errno_h);
>>> use Storable qw(dclone);
>>>
>>> @@ -176,8 +177,7 @@ my sub parse_link_file {
>>> my $LINK_DIRECTORY = "/usr/local/lib/systemd/network/";
>>>
>>> sub ensure_link_directory_exists {
>>> - mkdir '/usr/local/lib/systemd' if !-d '/usr/local/lib/systemd';
>>> - mkdir $LINK_DIRECTORY if !-d $LINK_DIRECTORY;
>>> + make_path($LINK_DIRECTORY);
>>> }
>>>
>>> my sub get_pinned {
>>
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-11-17 10:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-15 12:28 Fiona Ebner
2025-09-15 12:38 ` Fiona Ebner
2025-10-14 13:00 ` Fiona Ebner
2025-11-17 10:40 ` Fiona Ebner [this message]
2025-11-17 17:04 ` [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=f46738e2-a481-4748-948a-e0aebebfee41@proxmox.com \
--to=f.ebner@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox