[pve-devel] [PATCH novnc v2 2/2] buildsys: ad BUILDDIR variable

allows easier reading --- no changes Makefile | 13 +++-- 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/Makefile b/Makefile index 537cd70..427ac9f 100644 --- a/Makefile +++ b/Makefile @@ -3,6 +3,7 @@ VER=0.6 PKGREL=4 SRCDIR=novnc +BUILDDIR=${SRCDIR}.tmp

[pve-devel] [PATCH novnc v2 1/2] buildsys: write actual checked out git revision to SOURCE

--- changes v1 -> v2: * do not export SOURCE_DATE_EPOCH, already done by /usr/share/dpkg/pkg-info.mk Makefile | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Makefile b/Makefile index 70d1925..537cd70 100644 --- a/Makefile +++ b/Makefile @@ -5,7 +5,8 @@ PKGREL=4

Re: [pve-devel] istgt in Debian Stretch

On Sun, Jan 21, 2018 at 1:14 PM, Gilberto Nunes wrote: > Why not using some server with Ubuntu 16.04 which is LTS 'till 2021?? > This Ubuntu bring iSCSI Enterprise Target (iscsitarget-dkms). > I have implemented this with some customers (iscsitarget + zfs), and work >

Re: [pve-devel] istgt in Debian Stretch

On Sun, Jan 21, 2018 at 2:19 PM, Gilberto Nunes wrote: > > Proxmox only accept COMSTAR, ISTGT and IET for ZFS over iSCSI backend. > That's right? > According to the source code, yes ___ pve-devel mailing list

[pve-devel] applied: avoid possible harmful <> pattern when reading from STDIN

applied all patches On Mon, Jan 22, 2018 at 10:52:10AM +0100, Thomas Lamprecht wrote: > Fixes problems in CLIHandler using the code pattern: > > while (my $line = <>) { > ... > } > > For why this causes only _now_ problems lets first look how <> > behaves: > > "The null filehandle <> is

[pve-devel] applied: [PATCH pve-common 1/2] read_file: replace $versions->{$filename} with $cver

applied both patches On Mon, Jan 22, 2018 at 12:12:40PM +0100, Dietmar Maurer wrote: > Signed-off-by: Dietmar Maurer > --- > src/PVE/INotify.pm | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/src/PVE/INotify.pm b/src/PVE/INotify.pm > index

[pve-devel] applied: [PATCH i18n] buildsys: call lintian only on the package we built

applied ___ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

[pve-devel] [PATCH i18n] buildsys: call lintian only on the package we built

Else we call lintian on both packages twice. Signed-off-by: Thomas Lamprecht --- Makefile | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/Makefile b/Makefile index 65127f1..44e7705 100644 --- a/Makefile +++ b/Makefile @@ -24,8 +24,7 @@ $(DEBS): |

[pve-devel] [PATCH manager] use pve-i18n package

Signed-off-by: Dominik Csapak --- PVE/Service/pveproxy.pm | 3 ++- debian/control | 1 + 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/PVE/Service/pveproxy.pm b/PVE/Service/pveproxy.pm index ec1eb9a5..77dfaef1 100755 --- a/PVE/Service/pveproxy.pm

[pve-devel] applied: [PATCH i18n 1/2] add missing langs from pve

applied ___ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

[pve-devel] applied: [PATCH i18n v2] make only one po file per language

applied, and also pushed directly the commit which delete the old po files and adds the po files from pve-manager ___ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

[pve-devel] [PATCH pve-common 1/2] read_file: replace $versions->{$filename} with $cver

Signed-off-by: Dietmar Maurer --- src/PVE/INotify.pm | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/PVE/INotify.pm b/src/PVE/INotify.pm index a383040..1e5687b 100644 --- a/src/PVE/INotify.pm +++ b/src/PVE/INotify.pm @@ -240,11 +240,11 @@ sub

[pve-devel] [PATCH pve-common 2/2] INotify.pm - new helper poll_changes

Useful to detect file changes. Signed-off-by: Dietmar Maurer --- src/PVE/INotify.pm | 16 +++- 1 file changed, 11 insertions(+), 5 deletions(-) diff --git a/src/PVE/INotify.pm b/src/PVE/INotify.pm index 1e5687b..445c034 100644 --- a/src/PVE/INotify.pm +++

[pve-devel] applied: [PATCH common] CLIHandler: use resolved command definition

applied On Mon, Jan 22, 2018 at 11:00:07AM +0100, Thomas Lamprecht wrote: > For sub commands we resolve the real $cmd, $def and its arguments, > thus we should also get the handler from the resolved $def, not the > global one. > > No change for normal (consisting of only the first argument) >

[pve-devel] [PATCH common] CLIHandler: use resolved command definition

For sub commands we resolve the real $cmd, $def and its arguments, thus we should also get the handler from the resolved $def, not the global one. No change for normal (consisting of only the first argument) commands, for them $cmddef == $def. This sneaked in in a respin/rebase of the series.

[pve-devel] [PATCH qemu-server] avoid harmful '<>' pattern, explicitly read from STDIN

Fixes problems in CLIHandler using the code pattern: while (my $line = <>) { ... } For why this causes only _now_ problems lets first look how <> behaves: "The null filehandle <> is special: [...] Input from <> comes either from standard input, or from each file listed on the command line.

[pve-devel] avoid possible harmful <> pattern when reading from STDIN

Fixes problems in CLIHandler using the code pattern: while (my $line = <>) { ... } For why this causes only _now_ problems lets first look how <> behaves: "The null filehandle <> is special: [...] Input from <> comes either from standard input, or from each file listed on the command line.

[pve-devel] [PATCH cluster] avoid harmful '<>' pattern, explicitly read from STDIN

Fixes problems in CLIHandler using the code pattern: while (my $line = <>) { ... } For why this causes only _now_ problems lets first look how <> behaves: "The null filehandle <> is special: [...] Input from <> comes either from standard input, or from each file listed on the command line.

[pve-devel] [PATCH apiclient] avoid harmful '<>' pattern, explicitly read from STDIN

Fixes problems in CLIHandler using the code pattern: while (my $line = <>) { ... } For why this causes only _now_ problems lets first look how <> behaves: "The null filehandle <> is special: [...] Input from <> comes either from standard input, or from each file listed on the command line.

Re: [pve-devel] proxmox 2018 : add support for "virtual" network and network plugins ?

Hi, we have done a POC at work, with vxlan + ebgp-vpn, and we have tested a very nice feature : anycast gateway. basicaly, each vmbrX of a specific tenant, have the same ipaddress/mac address. This ip is the default gateway of the vm. That mean that vm can be migrate across hosts :) (openstack