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
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Léo-Paul Géneau
slapos
Commits
9320f1a9
Commit
9320f1a9
authored
Jul 27, 2018
by
Julien Muchembled
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
NEO: add 'coverage' egg for tests + version up for ERP5
This is a follow-up of commit
30c5367a
parent
49558e2f
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
2 additions
and
1 deletion
+2
-1
software/neoppod/software-common.cfg
software/neoppod/software-common.cfg
+2
-0
stack/erp5/buildout.cfg
stack/erp5/buildout.cfg
+0
-1
No files found.
software/neoppod/software-common.cfg
View file @
9320f1a9
...
...
@@ -50,6 +50,7 @@ eggs = neoppod[admin, ctl, master, storage-mysqldb]
ZODB
zope.testing
zodbtools
coverage
setproctitle
patch-binary = ${patch:location}/bin/patch
ZEO-patch-options = -p1
...
...
@@ -117,6 +118,7 @@ md5sum = 87d18c7021e4d43756813a83c9da5e97
BTrees = 4.4.1
ZODB = 4.4.5
apache-libcloud = 1.5.0
coverage = 4.5.1
ecdsa = 0.13
gitdb2 = 2.0.0
msgpack = 0.5.6
...
...
stack/erp5/buildout.cfg
View file @
9320f1a9
...
...
@@ -635,7 +635,6 @@ python-magic = 0.4.12+SlapOSPatched001
# use newer version than specified in ZTK
PasteDeploy = 1.5.2
argparse = 1.4.0
coverage = 4.3.4
zope.dottedname = 4.1.0
# test_UserManagerInterfaces in testERP5Security fails with 1.10.0.
...
...
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