Project

General

Profile

Actions

User story #4899

closed

User story #4798: Upgrade to CFEngine 3.6 in rudder-agent

Upgrade to CFEngine 3.6.0rc2

Added by Jonathan CLARKE about 10 years ago. Updated about 9 years ago.

Status:
Released
Priority:
1
Category:
Packaging
Target version:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

CFEngine just released a rc2, so let's use that instead of rc1.

Actions #1

Updated by Jonathan CLARKE about 10 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Jonathan CLARKE to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder-packages/pull/328
Actions #2

Updated by Nicolas CHARLES about 10 years ago

i can't merge it as the tarball rc's are not published yet on www.normation.com

Actions #3

Updated by Matthieu CERDA about 10 years ago

  • Status changed from Pending technical review to In progress
  • Assignee changed from Nicolas CHARLES to Matthieu CERDA

I'm taking care of the changes :)

Actions #4

Updated by Matthieu CERDA about 10 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Matthieu CERDA to Nicolas CHARLES
  • Priority changed from N/A to 1
  • % Done changed from 0 to 100
  • Pull Request changed from https://github.com/Normation/rudder-packages/pull/328 to https://github.com/Normation/rudder-packages/pull/329

PR has been updated !

Actions #5

Updated by Matthieu CERDA about 10 years ago

  • Status changed from Pending technical review to Discussion
  • Assignee changed from Nicolas CHARLES to Jonathan CLARKE

So, I fixed the PR to use the "original" tarball names that we get directly from CFEngine's github. However, there is a catch: the name of the new cfengine tarballs, "core" (as in core-(version).tar.gz), is absolutely not clear as it does not describe what the tarball actually contains...

I see two options here:
  • Rename the tarball ourselves to use cfengine-core-(version) as suggested by Nicolas
    • The problem is that the directory inside the tarball will not have the same name (it would still be the same name as the original tarball), possibly leading to further confusion
  • Change the structure of http://www.normation.com/tarball to use subdirectories for each type of tarball, making it much tidier and in the process leading to a clearer access path
    • Example: tarball/cfengine/core-(version).tar.gz

I do prefer the second approach as we do not touch the original tarballs but still keep a clear idea of what's inside, plus it corresponds to the change cfengine made (it is the content of the "core" repository of the CFEngine account on github)

What do you think guys ?

Actions #6

Updated by Nicolas CHARLES about 10 years ago

I prefer the 2nd one, which is more industrializable, and understandable

Thank you Matthieu

Actions #7

Updated by Jonathan CLARKE about 10 years ago

  • Assignee changed from Jonathan CLARKE to Matthieu CERDA

+1 for the 2nd approach.

Actions #8

Updated by Matthieu CERDA about 10 years ago

  • Status changed from Discussion to Pending technical review
  • Assignee changed from Matthieu CERDA to Jonathan CLARKE

PR has been adjusted.

Actions #9

Updated by Jonathan CLARKE about 10 years ago

  • Status changed from Pending technical review to Pending release

Applied in changeset commit:c4e20217fc8c549ba6d309a25098b42237591396.

Actions #10

Updated by Jonathan CLARKE about 10 years ago

Applied in changeset commit:c33627bd83bad023f7b1c9e72b329a549150be00.

Actions #11

Updated by Vincent MEMBRÉ about 10 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.11.0~beta1 that was released yesterday.

Actions #12

Updated by Benoît PECCATTE over 9 years ago

  • Category set to Packaging
Actions #13

Updated by Benoît PECCATTE about 9 years ago

  • Tracker changed from 6 to User story
Actions

Also available in: Atom PDF