Starting test: generic_agent_test.c

test_load_masterfiles: Starting test
FAIL: generic_agent_test

I would like to assign this issue to Ted. I will mail the logs to the Debian-team.

Legacy debian cfengine packages have $(sys.workdir)/inputs symlinked to /etc/cfengine.

This needs to changed so that /etc/cfengine is a symlink to $(sys.workdir)/masterfiles Instead.

Todo:

• script to perform migration
• debconf dialogs for user

Anyone reading in data and expecting order lists, like EFL users, cannot use 3.6.1.

https://dev.cfengine.com/issues/6466

The man pages in community edition are in /var/cfengine/share/man/man8/.

I don't know yet if they're in the package and not in the right place, or missing entirely. I wanted to get this in while it was on my mind.

This issue will track overall progress on Lintian messages.

Current output:

N: Processing binary package cfengine3 (version 3.5.2-1+nmu1, arch amd64) ...
W: cfengine3: package-name-doesnt-match-sonames libpromises3
I: cfengine3: spelling-error-in-binary usr/lib/libpromises.so.3.0.5 deamon daemon
I: cfengine3: spelling-error-in-binary usr/lib/libpromises.so.3.0.5 Commerical Commercial
I: cfengine3: spelling-error-in-binary usr/lib/libpromises.so.3.0.5 avaiable available
W: cfengine3: hardening-no-relro usr/lib/libpromises.so.3.0.5
W: cfengine3: hardening-no-fortify-functions usr/lib/libpromises.so.3.0.5
W: cfengine3: hardening-no-relro usr/sbin/cf-agent
W: cfengine3: hardening-no-fortify-functions usr/sbin/cf-agent
W: cfengine3: hardening-no-relro usr/sbin/cf-execd
W: cfengine3: hardening-no-fortify-functions usr/sbin/cf-execd
W: cfengine3: hardening-no-relro usr/sbin/cf-key
W: cfengine3: hardening-no-fortify-functions usr/sbin/cf-key
W: cfengine3: hardening-no-relro usr/sbin/cf-monitord
W: cfengine3: hardening-no-fortify-functions usr/sbin/cf-monitord
W: cfengine3: hardening-no-relro usr/sbin/cf-promises
I: cfengine3: spelling-error-in-binary usr/sbin/cf-runagent overriden overridden
W: cfengine3: hardening-no-relro usr/sbin/cf-runagent
W: cfengine3: hardening-no-fortify-functions usr/sbin/cf-runagent
W: cfengine3: hardening-no-relro usr/sbin/cf-serverd
W: cfengine3: hardening-no-fortify-functions usr/sbin/cf-serverd
W: cfengine3: hardening-no-relro usr/sbin/rpmvercmp
W: cfengine3: binary-without-manpage usr/sbin/cf-agent
W: cfengine3: binary-without-manpage usr/sbin/cf-execd
W: cfengine3: binary-without-manpage usr/sbin/cf-key
W: cfengine3: binary-without-manpage usr/sbin/cf-monitord
W: cfengine3: binary-without-manpage usr/sbin/cf-promises
W: cfengine3: binary-without-manpage usr/sbin/cf-runagent
W: cfengine3: binary-without-manpage usr/sbin/cf-serverd
W: cfengine3: binary-without-manpage usr/sbin/rpmvercmp
W: cfengine3: non-dev-pkg-with-shlib-symlink usr/lib/libpromises.so.3.0.5 usr/lib/libpromises.so
I: cfengine3: no-symbols-control-file usr/lib/libpromises.so.3.0.5
N: 1 tag overridden (1 info)

debian/control
libxml2.dev should be libxml2-dev.
I will issue a pull request with a patch.

As it was decided by both Debian and Ubuntu to switch to Systemd init, we need a systemd-compliant init script.

I have issue with cf-* files, they doesn't exists in /var/lib/cfengine3/bin:

# cf-agent -B server.local
2013-10-15T05:04:57-0400    error: cf-promises needs to be installed in /var/lib/cfengine3/bin for pre-validation of full configuration
2013-10-15T05:04:58-0400   notice: R: This autonomous node assumes the role of voluntary client

In Bas' create-deb-package branch there is an incorrect option --with-acl. The correct option is --with-libacl.

See issue:

• https://cfengine.com/dev/issues/2921

The pull request is accepted in the master branch, but no applied to 3.5.2 or 3.5.X branch. This one effects me.

See cfengine/core#1024

In total, >600 files contain spelling mistakes. This will be kind of a pain to patch with quilt.

Please contact me on my email address.

I am preparing another Debian-team meeting and I want to include you

Martin

When using pbuilder for package build, as is the case with both the Debian and Ubuntu archives, a failed acceptance test produces just an notion that '1' test failed, without any hint as how many of the acceptance tests failed, with what error message or whatsoever.

A regular action of pbuilder, one that I could not find a way around is cleaning up the environment after build, no matter if it was successful or not. All the logs with information on what actually went wrong goes to hell an we have no benefit of using a CI environment to gather the build outputs.

We are dealing with build dependencies. We should have a clear picture of the dependencies that exist.

The following cases should work:

• cfengine3 bootstrap to itself
• cfengine3 bootstrap to cfengine3
• cfengine3 bootstrap to cfengine-community on Debian
• cfengine3 bootstrap to cfengine-community on RHEL/CentOS
• cfengine-community on Debian bootstrap to cfengine3
• cfengine-community on RHEL/CentOS bootstrap to cfengine3

The current setup contains faulty and missing compile options.

See cfengine/core#1010

The way we fixed datadir is not acceptable to cfengine/core. We need to reconcile with them.

CFengime autoconf scripts set hard path for doc directory and data directory. configure --help shows the options but they are useless. Will ask a cfengine developer what the intention is of those hard paths.

Hello, I have issue with incorrect perms on ppkeys:

Unpacking cfengine3 (from .../cfengine3_3.5.2-1~my+1_amd64.deb) ...
Setting up cfengine3 (3.5.2-1~my+1) ...
2013-10-15T05:17:11-0400    error: Fatal CFEngine error: UNTRUSTED: Private key directory /var/lib/cfengine3/ppkeys (mode 755) was not private!

dpkg: error processing cfengine3 (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 cfengine3
E: Sub-process /usr/bin/dpkg returned an error code (1)

This tests $(sys.flavor).

Jessie output:

$ sudo cf-agent -K -f ./tests/acceptance/00_basics/01_compiler/800.cf -D AUTO,DEBUG     
2013-10-13T01:30:10-0700   notice: R: Compared debian_jessie to debian_jessie/sid
2013-10-13T01:30:10-0700   notice: R: ./tests/acceptance/00_basics/01_compiler/800.cf FAIL

wheezy output:

$ sudo cf-agent -K -f ./tests/acceptance/00_basics/01_compiler/800.cf -D AUTO,DEBUG     
2013-10-13T01:33:02-0700   notice: R: Compared debian_7 to debian_7
2013-10-13T01:33:02-0700   notice: R: ./tests/acceptance/00_basics/01_compiler/800.cf Pass

This test may resolve itself when /etc/issue is updated to a version number for jessie release. However, with the current acceptance test it can never pass on testing or unstable. This needs to pass on testing/unstable otherwise it will always fail Debian builds on the official build system.

This one affects me directly, so I want to make sure it gets included.

The problem is that cfengine ignores some interfaces if it detects that they are virtual. I have a number of virtual machines in which all interfaces are detected as virtual and get ignored.

The upstream bug is https://cfengine.com/dev/issues/3420

There's a patch included in the bug that should address the issue, but may need to be ported in.