Hi Ravi and all,
I am reporting the following as this may cause potential issues:
*File:* backend/manager/modules/enginesso/src/main/resources/messages
*Resource ID:* UNSUPPORTED_PARAMETER_IN_REQUEST
*String: *The request contains unsupported parameter value '%s' for
parameter '%s'.
*Question:
Hi Ravi and all,
Could you please help us with the following question?
*File: *backend/manager/modules/enginesso/src/main/resources/messages
*Resource ID: *loginpage.nextauth
*String: *Next Auth
*Question:* Is this string used for "Next authorization method"?
Thanks in advance.
Yuko
On 02/06/16 11:39 +0200, Tomáš Golembiovský wrote:
Hi,
for the last two weeks I've been getting lots of warnings about undelivered
mail from Gerrit. The importnat thing in the message being:
The original message was received at Wed, 1 Jun 2016 14:57:54 -0400
from gerrit.ovirt.org
Hi,
ovirt-engine-dashboard is currently built from master as well.
We should probably create a stable branch, e.g. ovirt-engine-dashboard-1.0.
For now, the nightly publisher configs:
jobs/confs/projects/ovirt/publish-rpms-nightly-{master,4.0}.yaml
both use ovirt-engine-dashboard "master"
- Original Message -
> From: "Eyal Edri"
> To: "Francesco Romani"
> Cc: "Simone Tiraboschi" , "Tal Nisan"
> , "Piotr Kliczewski"
> , "Dan Kenigsberg" , "Yaniv Bronheim"
example of what should have been done for vdsm:
https://gerrit.ovirt.org/#/c/59168/
any of the project maintainers should check if his project has build for
4.0 in addition to master and update the same file as needed.
On Tue, Jun 14, 2016 at 5:24 PM, Eyal Edri wrote:
> Its
Its relevant for projects who created branch for 4.0.
Do we have a list of those projects? if so we can compare it to the pkg in
the nightly 4.0 repo.
On Tue, Jun 14, 2016 at 4:14 PM, Simone Tiraboschi
wrote:
> All stable branch maintainers,
> I just noticed that our oVirt
All stable branch maintainers,
I just noticed that our oVirt 4.0 nightly repo (
http://resources.ovirt.org/pub/ovirt-4.0-snapshot/ ) still includes a
lot of packages from master branches.
Can you please ensure that our jenkins is building your project
packages in order to compose the 4.0 nightly
To build and install ovirt-engine execute the folllowing command:
$ make clean install-dev PREFIX="${PREFIX}"
What about installing it on Product Environment. Is the folllowing command
right?
$ make clean install PREFIX="${PREFIX}"
___
Devel mailing