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
42c106f0
Commit
42c106f0
authored
4 years ago
by
Justin Berthault
Committed by
Leo
4 years ago
Browse files
Options
Downloads
Patches
Plain Diff
main/rdiff-backup: upgrade to 2.0.3
parent
79f86f4a
No related branches found
Branches containing commit
No related tags found
Tags containing commit
1 merge request
!8033
main/rdiff-backup: upgrade to 2.0.3
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
main/rdiff-backup/APKBUILD
+2
-2
2 additions, 2 deletions
main/rdiff-backup/APKBUILD
with
2 additions
and
2 deletions
main/rdiff-backup/APKBUILD
+
2
−
2
View file @
42c106f0
# Contributor: Jeremy Thomerson <jeremy@thomersonfamily.com>
# Maintainer: Jeremy Thomerson <jeremy@thomersonfamily.com>
pkgname
=
rdiff-backup
pkgver
=
2.0.
0
pkgver
=
2.0.
3
pkgrel
=
0
pkgdesc
=
"Reverse differential backup tool"
options
=
"!check"
# Requires unpacakged 'xattr'
...
...
@@ -31,4 +31,4 @@ bashcomp() {
amove usr/share/bash-completion
}
sha512sums
=
"
0bf06d4eefffd41e86224d798e6ac6852ca0fd356be73d651ffaf63c37aaa043a6d22f8025619ab4a86e54f6e98e61f445ab68a6f87f4f2f48e635507ea110ec
rdiff-backup-2.0.
0
.tar.gz"
sha512sums
=
"
a4d517182ba1521195f46abde67e7963c7b44722b37d20a7f9afb446a1b90095deba1da9aaa940d174d5cf8dd01948619846d689e5675326b271141b355831fb
rdiff-backup-2.0.
3
.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