Jaime Melis jme...@opennebula.org writes:
Hmm, writing the question seems to gives my answer, it looks like the
cherry-picking of master commits on the one-version branches are the
reasons of the merge conflicts.
Yes... that's the way we usually do it: by cherry picking the commits.
Ok,
Hi,
Should I rebase[2] all my branches on master directly and then follow
the OpenNebula releases or is there a path to merge master and one-4.10?
Hmm, writing the question seems to gives my answer, it looks like the
cherry-picking of master commits on the one-version branches are the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Jamie and Daniel,
I perfectly understand the problems with Debian official packaging
guidelines.
I asked this, because at the moment I'm collaborating with Devuan, an
upcoming Debian fork which is aimed to not have systemd mandatory.
Could be
Jaime Melis jmelis@opennebula.systems writes:
Hi Alberto,
I can confirm what Daniel said. We have no current plans of updating the
offical Debian package of OpenNebula. Debian packaing guidelines are very
strict and as Daniel mentioned it's a very big job.
Daniel, I apologize, but somehow
Hello Alberto,
yes, of course. But due to resources we can only try and help out people
from the community like yourself or Daniel who want to collaborate in
creating these packages. We can assist and try to change this around in the
codebase to make things easier for package maintainers.
On
Alberto Zuin - Liste li...@albertozuin.eu writes:
Hello all,
Hello,
just for information, I know there is a pre-compiled version of
OpenNebula in your repository, but in the official Debian repository
there is only an old version of OpenNebula for Wheezy (3.4) and only
the
Daniel Dehennin daniel.dehen...@baby-gnu.org writes:
[...]
It's a big work, for now lintian is far from being happy[3]
[...]
[3] c.f. attachement
Missing attachement, sorry.
--
Daniel Dehennin
Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF
Fingerprint: 3E69 014E 5C23 50E8
