all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Fabian Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH-SERIES apt/widget-toolkit/manager] small refinements for APT repositories
Date: Mon,  5 Jul 2021 15:50:27 +0200	[thread overview]
Message-ID: <20210705135033.101390-1-f.ebner@proxmox.com> (raw)

Limit some checks to Proxmox (and Debian) repositories where
appropriate, and some other tiny improvements thrown in.

The RFCs (apt patch #3 and widget-toolkit patch #2) form a logcial
unit. The RFCs are also the only things requiring dependency bumps:

1. widget-toolkit patch #2 expects the new warnings from proxmox-apt

2. To avoid an (although soft) breaks, pve-manager needs to depend on
the new proxmox-apt (via pve-rs) at the same time as it depends on the
new widget-toolkit, because old widget-toolkit can end up showing
warnings without message for the 'Suites' column (see widget-tookit
patch #1 for the details/fix).


proxmox-apt:

Fabian Ebner (3):
  code cleanup: use contains()
  repository check: limit 'stable' to Proxmox and Debian origin
  repository check: check components for Proxmox repositories

 src/repositories/file.rs               | 87 +++++++++++++++-----------
 src/repositories/mod.rs                | 12 ++--
 tests/repositories.rs                  | 23 ++++++-
 tests/sources.list.d.expected/pve.list |  2 +
 tests/sources.list.d/pve.list          |  1 +
 5 files changed, 79 insertions(+), 46 deletions(-)


proxmox-widget-toolkit:

Fabian Ebner (2):
  node: repos: properly ignore warnings for other properties
  node: repos: show components warnings from the backend

 src/node/APTRepositories.js | 46 +++++++++++++++++++++----------------
 1 file changed, 26 insertions(+), 20 deletions(-)


pve-manager:

Fabian Ebner (1):
  api: apt: repositories: add description to return schema

 PVE/API2/APT.pm | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

-- 
2.30.2





             reply	other threads:[~2021-07-05 13:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-05 13:50 Fabian Ebner [this message]
2021-07-05 13:50 ` [pve-devel] [PATCH proxmox-apt 1/3] code cleanup: use contains() Fabian Ebner
2021-07-16 14:19   ` [pve-devel] applied: " Thomas Lamprecht
2021-07-05 13:50 ` [pve-devel] [PATCH proxmox-apt 2/3] repository check: limit 'stable' to Proxmox and Debian origin Fabian Ebner
2021-07-05 13:50 ` [pve-devel] [RFC proxmox-apt 3/3] repository check: check components for Proxmox repositories Fabian Ebner
2021-07-05 13:50 ` [pve-devel] [PATCH proxmox-widget-toolkit 1/2] node: repos: properly ignore warnings for other properties Fabian Ebner
2021-07-05 13:50 ` [pve-devel] [RFC proxmox-widget-toolkit 2/2] node: repos: show components warnings from the backend Fabian Ebner
2021-07-05 13:50 ` [pve-devel] [PATCH manager 1/1] api: apt: repositories: add description to return schema 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=20210705135033.101390-1-f.ebner@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 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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal