Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
slapos slapos
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Labels
    • Labels
  • Merge requests 122
    • Merge requests 122
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedi
  • slaposslapos
  • Merge requests
  • !314

Closed
Created Apr 09, 2018 by Jérome Perrin@jeromeOwner
  • Report abuse
Report abuse

ERP5 Software Release: Pin all git repositories

  • Overview 4
  • Commits 5
  • Changes 5

( for 1.0 branch )

Since !258 (merged) we configured buildout to only accept pinned eggs. In fact, it's still accepting installing develop eggs and when this develop eggs have a new dependency we realize (too late) that software release was not repeatable.

After f5fc6d6d we use master branch of cloudooo, when cloudooo got a new dependency to pyPdf in cloudooo@0ff799eb installation started to fail.

This MR is just about pinning the git repositories to stop the build from failing, I have not actually tried if these revisions where OK.

Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: 1.0
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7