From: Stefan Mayr <stefan@mayr-stefan.de>
To: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>,
"Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH common 1/1] Fix #7175: remove deprecated timezone file
Date: Fri, 16 Jan 2026 22:32:30 +0100 [thread overview]
Message-ID: <9bc5eb01-dba4-4c23-bfd6-627d8924ce54@mayr-stefan.de> (raw)
In-Reply-To: <1768472434.54jhwbt78k.astroid@yuna.none>
Am 15.01.2026 um 11:26 schrieb Fabian Grünbichler:
> On December 29, 2025 1:03 pm, Maximiliano Sandoval wrote:
>> Stefan Mayr <stefan@mayr-stefan.de> writes:
>>
>> Thanks for submitting a patch.
>>
>> A comment below.
>>
>>> Suggested-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
>>> Signed-off-by: Stefan Mayr <stefan@mayr-stefan.de>
>>> ---
>>> src/PVE/INotify.pm | 29 -----------------------------
>>> 1 file changed, 29 deletions(-)
>>>
>>> diff --git a/src/PVE/INotify.pm b/src/PVE/INotify.pm
>>> index 62b3ca8..03c871c 100644
>>> --- a/src/PVE/INotify.pm
>>> +++ b/src/PVE/INotify.pm
>>> @@ -651,35 +651,6 @@ register_file(
>>> \&update_etc_resolv_conf,
>>> );
>>>
>>> -sub read_etc_timezone {
>>> - my ($filename, $fd) = @_;
>>> -
>>> - my $timezone = <$fd>;
>>> -
>>> - chomp $timezone;
>>> -
>>> - return $timezone;
>>> -}
>>> -
>>> -sub write_etc_timezone {
>>> - my ($filename, $fh, $timezone) = @_;
>>> -
>>> - my $tzinfo = "/usr/share/zoneinfo/$timezone";
>>> -
>>> - raise_param_exc({ 'timezone' => "No such timezone" })
>>> - if (!-f $tzinfo);
>>> -
>>> - ($timezone) = $timezone =~ m/^(.*)$/; # untaint
>>> -
>>> - print $fh "$timezone\n";
>>> -
>>> - unlink("/etc/localtime");
>>> - symlink("/usr/share/zoneinfo/$timezone", "/etc/localtime");
>>> -
>>> -}
>>> -
>>> -register_file('timezone', "/etc/timezone", \&read_etc_timezone, \&write_etc_timezone);
>>>
>>
>> At least pmg-api and pve-container use this. I would recommend to only
>> add a comment here instead of removing the helper since this is a shared
>> library. Alternatively, one could port all existing users to, e.g.
>> timedatectl.
>
> porting all callers and then dropping it would probably make the most
> sense, or we could introduce new helpers in pve-common that are usable
> for all existing callers..
That's why I've already sent multiple patches ...
>>
>>> -
>>> sub read_active_workers {
>>> my ($filename, $fh) = @_;
>>
>> --
>> Maximiliano
>>
>>
>> _______________________________________________
>> pve-devel mailing list
>> pve-devel@lists.proxmox.com
>> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>>
_______________________________________________
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:[~2026-01-16 21:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-25 8:05 [pve-devel] [PATCH manager/common 0/1] Fix #7175: switch API to timedatectl Stefan Mayr
2025-12-25 8:05 ` [pve-devel] [PATCH common 1/1] Fix #7175: remove deprecated timezone file Stefan Mayr
2025-12-29 12:03 ` Maximiliano Sandoval
2026-01-15 10:26 ` Fabian Grünbichler
2026-01-16 21:32 ` Stefan Mayr [this message]
2025-12-25 8:05 ` [pve-devel] [PATCH manager 1/1] Fix #7175: use timedatectl for timezone handling Stefan Mayr
2026-01-15 10:25 ` Fabian Grünbichler
2026-01-16 21:30 ` Stefan Mayr
2026-01-16 21:55 ` Stefan Mayr
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=9bc5eb01-dba4-4c23-bfd6-627d8924ce54@mayr-stefan.de \
--to=stefan@mayr-stefan.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox