From: Dominik Csapak <d.csapak@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH eslint/manager/wt/pmg-gui/proxmox-backup] change eslint
Date: Thu, 22 Jun 2023 10:31:12 +0200 [thread overview]
Message-ID: <20230622083117.1823170-1-d.csapak@proxmox.com> (raw)
from 'eslint' to 'pve-eslint' to avoid a conflict with debians 'eslint'
package which ships the same binary
we have to bump the package and update the dev-dependency in the other
repositories
maybe we can/should also apply this on stable-7/2? so that on an
upgrade to 8.x/3.x it does not run into issues?
pve-eslint:
Dominik Csapak (1):
change binary name from 'eslint' to 'pve-eslint'
debian/links | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
pve-manager:
Dominik Csapak (1):
use 'pve-eslint' instead of 'eslint'
www/manager6/Makefile | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
proxmox-widget-toolkit:
Dominik Csapak (1):
use 'pve-eslint' instead of 'eslint'
src/Makefile | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
pmg-gui:
Dominik Csapak (1):
use 'pve-eslint' instead of 'eslint'
js/Makefile | 4 ++--
js/mobile/Makefile | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
proxmox-backup:
Dominik Csapak (1):
use 'pve-eslint' instead of 'eslint'
www/Makefile | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--
2.30.2
next reply other threads:[~2023-06-22 8:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 8:31 Dominik Csapak [this message]
2023-06-22 8:31 ` [pve-devel] [PATCH eslint 1/1] change binary name from 'eslint' to 'pve-eslint' Dominik Csapak
2023-06-22 8:31 ` [pve-devel] [PATCH manager 1/1] use 'pve-eslint' instead of 'eslint' Dominik Csapak
2023-06-22 8:31 ` [pve-devel] [PATCH widget-toolkit " Dominik Csapak
2023-06-22 8:31 ` [pve-devel] [PATCH pmg-gui " Dominik Csapak
2023-06-22 8:31 ` [pve-devel] [PATCH proxmox-backup " Dominik Csapak
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=20230622083117.1823170-1-d.csapak@proxmox.com \
--to=d.csapak@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