From: Christian Ebner <c.ebner@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>,
Robert Obkircher <r.obkircher@proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup 1/3] api: syncjob: correctly update/delete 'unmount-on-done' field
Date: Wed, 29 Oct 2025 14:50:04 +0100 [thread overview]
Message-ID: <e8a93c1d-46ea-4d05-a9ff-ea42d34120ac@proxmox.com> (raw)
In-Reply-To: <d058b356-032c-40b1-a807-a8bd33e6f698@proxmox.com>
On 10/29/25 2:37 PM, Christian Ebner wrote:
> Hi,
>
> On 10/29/25 2:23 PM, Robert Obkircher wrote:
>>
>> On 10/14/25 13:53, Hannes Laimer wrote:
>>> Signed-off-by: Hannes Laimer <h.laimer@proxmox.com>
>>> ---
>>> src/api2/config/sync.rs | 8 ++++++++
>>> 1 file changed, 8 insertions(+)
>>>
>>> diff --git a/src/api2/config/sync.rs b/src/api2/config/sync.rs
>>> index 358409b5..ab68391c 100644
>>> --- a/src/api2/config/sync.rs
>>> +++ b/src/api2/config/sync.rs
>>> @@ -341,6 +341,8 @@ pub enum DeletableProperty {
>>> VerifiedOnly,
>>> /// Delete the run_on_mount property,
>>> RunOnMount,
>>> + /// Delete the unmount_on_done property,
>>> + UnmountOnDone,
>>> /// Delete the sync_direction property,
>>> SyncDirection,
>>> }
>>> @@ -463,6 +465,9 @@ pub fn update_sync_job(
>>> DeletableProperty::RunOnMount => {
>>> data.run_on_mount = None;
>>> }
>>> + DeletableProperty::UnmountOnDone => {
>>> + data.unmount_on_done = None;
>>> + }
>>> DeletableProperty::SyncDirection => {
>>> data.sync_direction = None;
>>> }
>>> @@ -515,6 +520,9 @@ pub fn update_sync_job(
>>> if let Some(run_on_mount) = update.run_on_mount {
>>> data.run_on_mount = Some(run_on_mount);
>>> }
>>> + if let Some(unmount_on_done) = update.unmount_on_done {
>>> + data.unmount_on_done = Some(unmount_on_done);
>>> + }
>>> if let Some(sync_direction) = update.sync_direction {
>>> data.sync_direction = Some(sync_direction);
>>> }
>> Make deb failed with an error in this file:
>>
>> error[E0063]: missing field `unmount_on_done` in initializer of
>> `SyncJobConfig`
>> --> src/api2/config/sync.rs:684:19
>> |
>> 684 | let mut job = SyncJobConfig {
>> | ^^^^^^^^^^^^^ missing `unmount_on_done`
> Did you correctly install the changes to the pbs-api-types dependency
> first?
>
> The `SyncJobConfig` is part of the `pbs-api-types` crate, which is
> located in the `proxmox` repo.
>
> Therefore, you can apply the first patch of the series there and build a
> deb package via `make pbs-api-types-deb` from the repo base folder (or
> in general `make <crate>-deb`). The install it via `dpkg -i build/
> <pkg>.deb`.
>
> And in the `proxmox-backup` repo make sure to run a `cargo clean` after
> that.
Never mind, I see the build failing here with the same error as well.
Sorry for the noise!
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next prev parent reply other threads:[~2025-10-29 13:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 11:53 [pbs-devel] [PATCH proxmox{, -backup} 0/4] unmount datastores after sync job Hannes Laimer
2025-10-14 11:53 ` [pbs-devel] [PATCH proxmox 1/1] pbs-api-types: add 'unmount-on-done' field to sync job config Hannes Laimer
2025-10-14 11:53 ` [pbs-devel] [PATCH proxmox-backup 1/3] api: syncjob: correctly update/delete 'unmount-on-done' field Hannes Laimer
2025-10-29 13:24 ` Robert Obkircher
2025-10-29 13:37 ` Christian Ebner
2025-10-29 13:50 ` Christian Ebner [this message]
2025-10-29 13:51 ` Hannes Laimer
2025-10-14 11:53 ` [pbs-devel] [PATCH proxmox-backup 2/3] api: datastore: unmount datastore after sync if configured Hannes Laimer
2025-10-14 15:31 ` Shannon Sterz
2025-10-14 11:53 ` [pbs-devel] [PATCH proxmox-backup 3/3] ui: add 'unmount-on-done' field to SyncJobEdit window Hannes Laimer
2025-10-14 15:31 ` Shannon Sterz
2025-10-29 16:02 ` [pbs-devel] superseded: [PATCH proxmox{, -backup} 0/4] unmount datastores after sync job Hannes Laimer
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=e8a93c1d-46ea-4d05-a9ff-ea42d34120ac@proxmox.com \
--to=c.ebner@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=r.obkircher@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.