From: Christian Ebner <c.ebner@proxmox.com>
To: Ciro Iriarte <cyruspy@gmail.com>, pbs-devel@lists.proxmox.com
Cc: Thomas Lamprecht <t.lamprecht@proxmox.com>
Subject: Re: Client package for non Debian clients
Date: Mon, 10 Aug 2026 09:08:49 +0200 [thread overview]
Message-ID: <a5f74127-5c8d-4ca5-bccf-d5a4409c374c@proxmox.com> (raw)
In-Reply-To: <CAEaLa5HhExXeL-uMgTEDxOL3nWs9h29Fb3VYS0QemWJLGuoh5w@mail.gmail.com>
Hi,
On 8/8/26 11:07 PM, Ciro Iriarte wrote:
> Hello!,
>
> I've been a long time PVE user but I'm just starting with PBS now.
> I've noticed that the documentation only mentions non-PVE client
> (regular/file clients) packages for Debian.
>
> I would like to package the client for other Linux distributions, is
> that something worth of being committed upstream somewhere or should I
> just keep it as an unofficial satellite repo?.
Proxmox currently provides a statically linked binary for the
proxmox-backup-client, which runs on most modern x86-64 Linux systems
[0]. The client is currently distributed as deb package only, can
however be easily extracted from that archive.
Currently there is no active work in providing other packaging formats,
this might however be something worth looking into, also with respect to
builds for other architectures.
However, this must be tightly integrated with our internal workflow and
pipelines, @Thomas opinions from your side?
> I plan to produce them using http://build.opensuse.org which provides
> a platform to create native packages for several distributions.
>
> Regards.
> CI.-
[0]
https://pbs.proxmox.com/docs/installation.html#install-statically-linked-proxmox-backup-client
prev parent reply other threads:[~2026-08-10 7:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-08 21:07 Client package for non Debian clients Ciro Iriarte
2026-08-10 7:08 ` Christian Ebner [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=a5f74127-5c8d-4ca5-bccf-d5a4409c374c@proxmox.com \
--to=c.ebner@proxmox.com \
--cc=cyruspy@gmail.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=t.lamprecht@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.