Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
aports
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Monitor
Service Desk
Analyze
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
alpine
aports
Commits
25617bb7
Commit
25617bb7
authored
4 years ago
by
Fabian Affolter
Committed by
Andy Postnikov
4 years ago
Browse files
Options
Downloads
Patches
Plain Diff
community/py3-pytest-mock: upgrade to 3.5.1
parent
0d571dc8
Loading
Loading
1 merge request
!16742
community/py3-pytest-mock: upgrade to 3.5.1
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
community/py3-pytest-mock/APKBUILD
+3
-3
3 additions, 3 deletions
community/py3-pytest-mock/APKBUILD
with
3 additions
and
3 deletions
community/py3-pytest-mock/APKBUILD
+
3
−
3
View file @
25617bb7
# Maintainer: Andy Postnikov <apostnikov@gmail.com>
pkgname
=
py3-pytest-mock
pkgver
=
3.
3
.1
pkgrel
=
1
pkgver
=
3.
5
.1
pkgrel
=
0
pkgdesc
=
"Thin-wrapper around the mock package for easier use with py.test"
options
=
"!check"
# Fails
url
=
"https://github.com/pytest-dev/pytest-mock"
...
...
@@ -33,4 +33,4 @@ package() {
python3 setup.py
install
--prefix
=
/usr
--root
=
"
$pkgdir
"
}
sha512sums
=
"
ffd53974f82f725cf3bdbe750c1deb568ad1a12a67532eca93ff28d80b1cbcd8ebf709985f5473717c9d54345b251c1627c0567821e9e8b9e102db5c16cf7421
pytest-mock-3.
3
.1.tar.gz"
sha512sums
=
"
28ab2f239d3dfee134dd4e4fd467109cf3c76cb60aeb537dbc0c21b9a7619d068d54737e33d98c585e9341588fdafba4737ea5f428af37796f55e61ec30373a7
pytest-mock-3.
5
.1.tar.gz"
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment