From: Fabian Ebner <f.ebner@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH/RFC-SERIES v2] APT repositories API/UI
Date: Fri, 26 Feb 2021 16:09:49 +0100 [thread overview]
Message-ID: <20210226150959.9518-1-f.ebner@proxmox.com> (raw)
List the configured repositories and have some basic checks for them.
Conceptual continuation of [0]. The plan is to use perlmod to make the Rust
implementation available for PVE+PMG as well.
There's still the question if introducing a digest is worth it. At the moment,
the warnings returned by the checkrepositories call might not match up with the
repositories returned previously, but that's a rather minor issue.
Should a digest be added now to be future-proof? Should it live in the
proxmox-apt crate and be file-level, or would it be enough to hash the result
from parsing in the PBS API call and use that? The latter seems like the
more pragmatic approach and avoids cluttering the APT backend.
Changes from v1:
* Perl -> Rust
* PVE -> PBS
* Don't rely on regexes for parsing.
* Add writer and tests.
* UI: pin warnings to the repository they're for.
* Keep order of options consistent with configuration.
* Smaller things noted on the individual patches.
Still missing:
* Upgrade suite/distribuiton button to be used before major release
upgrades (but it's really simply to add that now).
* perlmod magic and integration in PVE and PMG.
[0]: https://lists.proxmox.com/pipermail/pve-devel/2021-January/046726.html
proxmox-apt:
Fabian Ebner (4):
initial commit
add files for Debian packaging
add functions to check for Proxmox repositories
add check_repositories function
widget-toolkit:
Fabian Ebner (2):
add UI for APT repositories
add warnings
src/Makefile | 1 +
src/node/APTRepositories.js | 259 ++++++++++++++++++++++++++++++++++++
2 files changed, 260 insertions(+)
create mode 100644 src/node/APTRepositories.js
proxmox-backup:
Fabian Ebner (4):
depend on new proxmox-apt crate
api: apt: add repositories call
ui: add repositories
add check_repositories_call
Cargo.toml | 1 +
src/api2/node/apt.rs | 78 +++++++++++++++++++++++++++++++++++++
www/ServerAdministration.js | 7 ++++
3 files changed, 86 insertions(+)
--
2.20.1
next reply other threads:[~2021-02-26 15:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 15:09 Fabian Ebner [this message]
2021-02-26 15:09 ` [pbs-devel] [PATCH v2 proxmox-apt 01/10] initial commit Fabian Ebner
2021-03-10 15:14 ` Wolfgang Bumiller
2021-02-26 15:09 ` [pbs-devel] [PATCH v2 proxmox-apt 02/10] add files for Debian packaging Fabian Ebner
2021-02-26 15:09 ` [pbs-devel] [PATCH v2 proxmox-apt 03/10] add functions to check for Proxmox repositories Fabian Ebner
2021-02-26 15:09 ` [pbs-devel] [PATCH v2 proxmox-apt 04/10] add check_repositories function Fabian Ebner
2021-03-10 15:17 ` Wolfgang Bumiller
2021-02-26 15:09 ` [pbs-devel] [PATCH v2 proxmox-backup 05/10] cargo: depend on new proxmox-apt crate Fabian Ebner
2021-02-26 15:09 ` [pbs-devel] [PATCH v2 proxmox-backup 06/10] api: apt: add repositories call Fabian Ebner
2021-02-26 15:09 ` [pbs-devel] [PATCH v2 widget-toolkit 07/10] add UI for APT repositories Fabian Ebner
2021-02-26 15:09 ` [pbs-devel] [PATCH v2 proxmox-backup 08/10] ui: add grid " Fabian Ebner
2021-02-26 15:09 ` [pbs-devel] [RFC v2 proxmox-backup 09/10] api: apt: add check_repositories_call Fabian Ebner
2021-02-26 15:09 ` [pbs-devel] [RFC v2 widget-toolkit 10/10] APT: show warnings for repositories Fabian Ebner
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=20210226150959.9518-1-f.ebner@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=pbs-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