Page MenuHome GnuPG
Create Task
Maniphest T4903

Github sources are difficult to test
Closed, InvalidPublic
Actions

Description

This is an observation while trying to test GnuPG suite using Github sources.

Trying to test all the packages is difficult at best. I cannot clone a repo, change directories and simply run ./configure. The engineering problems start with --enable-maintainer-mode. I'm not a maintainer and I could not give a crap about building a package or the docs. I'm a user that needs to acceptance test the suite. I only care about the code.

The suite needs to offer --enable-qa-mode in addition to a --disable-docs. Four hours into the process and I still can't build the suite. Each attempt results in useless errors, like fig2dev or gs is not installed. I'm also fighting with the projects choice of bleeding edge components. There is no reason someone should not be able to walk up to a Ubuntu 18.04 machine and things "just work". Complaining gettext is too old in a LTS release is just plain wrong.

I still can't get beyond this error. I have no idea what is needed to clear it:

make[1]: Entering directory '/home/travis/build/noloader/gnupg/doc'
convert `test -f 'gnupg-module-overview.svg' || echo './'`gnupg-module-overview.svg gnupg-module-overview.pdf
convert-im6.q16: unable to read font `(null)' @ error/annotate.c/RenderFreetype/1367.
convert-im6.q16: non-conforming drawing primitive definition `text' @ error/draw.c/DrawImage/3265.
convert-im6.q16: unable to read font `(null)' @ error/annotate.c/RenderFreetype/1367.
convert-im6.q16: non-conforming drawing primitive definition `text' @ error/draw.c/DrawImage/3265.
convert-im6.q16: not authorized `gnupg-module-overview.pdf' @ error/constitute.c/WriteImage/1037.
Makefile:1188: recipe for target 'gnupg-module-overview.pdf' failed

I'm fairly certain the inability to easily test the suite from Github master is a defect in GnuPG's engineering processes. The problems with the processes means users are not helping test before a release (does anyone besides a handful of project developers perform release testing?). It also makes it difficult to setup a CI pipeline (have your tried to put these bleeding edge components on a CI image?). I'm guessing that's why there are no CI pipelines setup.

Details

Version
git-master

Event Timeline

JW created this task.Apr 1 2020, 1:26 PM
JW created this object in space S1 Public.
JW updated the task description. (Show Details)Apr 1 2020, 3:48 PM
JW added a comment.EditedApr 1 2020, 5:00 PM

Also see Issue #10, Add Travis testing in the GnuPG GitHub. The PR adds Travis testing to the entire GnuPG suite.

--enable-maintainer-mode has literally broken every one of your builds.

• werner closed this task as Invalid.Apr 1 2020, 8:44 PM
• werner added a subscriber: • werner.

Sorry, if you use your own copy of GnuPG on GitHub, it is all up to you. We do not use Github.

JW added a comment.EditedApr 2 2020, 12:12 AM

We do not use Github.

Then someone has squatted the GnuPG name: The GNU Privacy Guard. You should contact GitHub support and have the account removed so unsuspecting users don't stumble across it. (q.v.).

Sorry, if you use your own copy of GnuPG on GitHub, it is all up to you.

I forked the project. I'm following the README.git.

The project really should improve its processes. Thorough testing will void testing results like this. Users should not be encountering these errors for a mature project.