Bug #17868
closed
Bad documentation leads to package build failing when building for armhf
Added by Nicolas Ecarnot over 4 years ago.
Updated over 1 year ago.
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Infrequent - complex configurations | third party integrations
Effort required:
Very Small
Description
After having read :
- https://docs.rudder.io/reference/6.0/reference/build.html#_building_the_rudder_agent
- https://issues.rudder.io/issues/10004
I tried to build the rudder-agent package for the 6.1 branch, using dpkg-buildpackage.
This verbose compilation is too long to detail what's going on, but it looks like it is compiling mostly correctly.
Alas, in the end, I get :
make1: * [Makefile:443: rudder-sources.tar.bz2] Error 22
make1: Leaving directory '/root/rudder-packages/rudder-agent/SOURCES'
make: * [debian/rules:157: install] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
The log is too verbose for my modest skill so I here provide the typescript (read it with less -r to get nice colors).
The only things I changed were debian/changelog SOURCES/Makefile in which I choose RUDDER_VERSION_TO_PACKAGE = 6.1
It looks like it's pretty close to success but what could I do more to get this final .deb ?
- Category changed from Packaging to Documentation
- Severity changed from Major - prevents use of part of Rudder | no simple workaround to Minor - inconvenience | misleading | easy workaround
- Effort required set to Very Small
- Priority changed from 41 to 50
So the bug is just adding in document to use the full version.
- Subject changed from Package build failing when building for armhf to Bad documentation leads to package build failing when building for armhf
- Target version changed from 6.1.2 to 6.1.3
- Target version changed from 6.1.3 to 6.1.4
- Target version changed from 6.1.4 to 6.1.5
- Target version changed from 6.1.5 to 6.1.6
- Priority changed from 50 to 49
- Target version changed from 6.1.6 to 6.1.7
- Priority changed from 49 to 48
- Target version changed from 6.1.7 to 6.1.8
- Priority changed from 48 to 47
- Target version changed from 6.1.8 to 6.1.9
- Priority changed from 47 to 46
- Target version changed from 6.1.9 to 6.1.10
- Target version changed from 6.1.10 to 6.1.11
- Priority changed from 46 to 45
- Target version changed from 6.1.11 to 6.1.12
- Priority changed from 45 to 44
- Target version changed from 6.1.12 to 6.1.13
- Target version changed from 6.1.13 to 6.1.14
- Priority changed from 44 to 43
- Target version changed from 6.1.14 to 6.1.15
- Priority changed from 43 to 42
- Target version changed from 6.1.15 to 6.1.16
- Target version changed from 6.1.16 to 6.1.17
- Target version changed from 6.1.17 to 6.1.18
- Target version changed from 6.1.18 to 6.1.19
- Target version changed from 6.1.19 to 6.1.20
- Target version changed from 6.1.20 to 6.1.21
- Target version changed from 6.1.21 to old 6.1 issues to relocate
- Target version changed from old 6.1 issues to relocate to 7.2.5
- Priority changed from 42 to 0
- Regression set to No
- Status changed from New to In progress
- Assignee set to Benoît PECCATTE
- Status changed from In progress to Pending technical review
- Assignee changed from Benoît PECCATTE to Alexis Mousset
- Pull Request set to https://github.com/Normation/rudder-doc/pull/965
- Status changed from Pending technical review to Pending release
- Fix check changed from To do to Checked
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.2.5 which was released today.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by