Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
slapos
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Yusei Tahara
slapos
Commits
656616f1
Commit
656616f1
authored
Aug 21, 2014
by
Kazuhiko Shiozaki
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
specify slapos.core version in stack/slapos.cfg.
parent
9e179c0c
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
2 additions
and
4 deletions
+2
-4
stack/erp5/buildout.cfg
stack/erp5/buildout.cfg
+0
-3
stack/slapos.cfg
stack/slapos.cfg
+2
-1
No files found.
stack/erp5/buildout.cfg
View file @
656616f1
...
...
@@ -585,9 +585,6 @@ rdiff-backup = 1.0.5
# use newest version of slapos.cookbook
slapos.cookbook =
# we need to define an explicit version of slapos.core that is propagated to instances
slapos.core = 1.1.3
# modified version that works fine for buildout installation
SOAPpy = 0.12.0nxd001
...
...
stack/slapos.cfg
View file @
656616f1
...
...
@@ -96,6 +96,8 @@ hexagonit.recipe.download = 1.7nxd002
setuptools = 5.5.1
# Official egg of prettytable has permission problems in EGG-INFO.
prettytable = 0.7.3-nxd001
# we need to define an explicit version of slapos.core that is propagated to instances
slapos.core = 1.2.1
Jinja2 = 2.7.3
MarkupSafe = 0.23
...
...
@@ -118,7 +120,6 @@ pytz = 2014.4
requests = 2.3.0
six = 1.7.3
slapos.cookbook = 0.87
slapos.core = 1.2.1
slapos.libnetworkcache = 0.14.1
slapos.recipe.cmmi = 0.2
stevedore = 0.15
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment