Raphael Hertzog hert...@debian.org writes:
On Wed, 30 Mar 2011, Goswin von Brederlow wrote:
Note also that the trigger activation is a no-op if the
qlustar-image-common is
not configured which means that you have to regenerate your image in the
configure of qlustar-image-common as well
Hi,
I have a little problem with file triggers.
I have a tool (qlustar-image-common) that builds a root filesystem image
from a set of modules. The tool has a file trigger on
/usr/lib/qlustar/modules. Now I have 2 modules: core and ha. The core
module contains a minimal bootable system and the
Hi,
On Wed, 30 Mar 2011, Goswin von Brederlow wrote:
Unpacking replacement qlustar-module-ha-lucid-amd64-7.4.1 ...
dpkg: dependency problems prevent configuration of
qlustar-module-ha-lucid-amd64-7.4.1:
qlustar-module-ha-lucid-amd64-7.4.1 depends on
qlustar-module-core-lucid-amd64-7.4.1 (=
Raphael Hertzog hert...@debian.org writes:
Hi,
On Wed, 30 Mar 2011, Goswin von Brederlow wrote:
Unpacking replacement qlustar-module-ha-lucid-amd64-7.4.1 ...
dpkg: dependency problems prevent configuration of
qlustar-module-ha-lucid-amd64-7.4.1:
qlustar-module-ha-lucid-amd64-7.4.1 depends
On Wed, 30 Mar 2011, Goswin von Brederlow wrote:
Note also that the trigger activation is a no-op if the
qlustar-image-common is
not configured which means that you have to regenerate your image in the
configure of qlustar-image-common as well as in the triggered case.
Is a package
5 matches
Mail list logo