Script 'mail_helper' called by obssrc
Hello community,
here is the log from the commit of package git-remote-gcrypt for
openSUSE:Factory checked in at 2022-08-22 11:05:09
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/git-remote-gcrypt (Old)
and /work/SRC/openSUSE:Factory/.git-remote-gcrypt.new.2083 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "git-remote-gcrypt"
Mon Aug 22 11:05:09 2022 rev:4 rq:998584 version:1.5
Changes:
--------
--- /work/SRC/openSUSE:Factory/git-remote-gcrypt/git-remote-gcrypt.changes
2021-01-22 21:52:52.737896303 +0100
+++
/work/SRC/openSUSE:Factory/.git-remote-gcrypt.new.2083/git-remote-gcrypt.changes
2022-08-22 11:05:14.321715489 +0200
@@ -1,0 +2,11 @@
+Mon Aug 22 08:36:40 UTC 2022 - Michael Vetter <[email protected]>
+
+- Update to 1.5:
+ * Pass --error-on-no-transfer to 'rclone copyto'.
+ * README.md:
+ - explain why the arbitrary <giturl> and sftp:// backends are
+ inappropriate for most git repositories
+ - use stronger language to say that one should use local or rsync://
+ instead, and also say it up in "Description".
+
+-------------------------------------------------------------------
Old:
----
1.4.tar.gz
New:
----
1.5.tar.gz
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ git-remote-gcrypt.spec ++++++
--- /var/tmp/diff_new_pack.bhOR4r/_old 2022-08-22 11:05:14.741716407 +0200
+++ /var/tmp/diff_new_pack.bhOR4r/_new 2022-08-22 11:05:14.745716417 +0200
@@ -1,7 +1,7 @@
#
# spec file for package git-remote-gcrypt
#
-# Copyright (c) 2021 SUSE LLC
+# Copyright (c) 2022 SUSE LLC
#
# All modifications and additions to the file contributed by third parties
# remain the property of their copyright owners, unless otherwise agreed
@@ -17,7 +17,7 @@
Name: git-remote-gcrypt
-Version: 1.4
+Version: 1.5
Release: 0
Summary: Encrypted git repositories
License: GPL-2.0-or-later
++++++ 1.4.tar.gz -> 1.5.tar.gz ++++++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/git-remote-gcrypt-1.4/README.rst
new/git-remote-gcrypt-1.5/README.rst
--- old/git-remote-gcrypt-1.4/README.rst 2021-01-22 02:46:47.000000000
+0100
+++ new/git-remote-gcrypt-1.5/README.rst 2022-08-21 23:39:13.000000000
+0200
@@ -18,8 +18,8 @@
Supported backends are `local`, `rsync://` and `sftp://`, where the
repository is stored as a set of files, or instead any `<giturl>`
where gcrypt will store the same representation in a git repository,
-bridged over arbitrary git transport. See "Performance" below for
-backends comparison.
+bridged over arbitrary git transport. Prefer `local` or `rsync://` if
+you can use one of those; see "Performance" below for discussion.
There is also an experimental `rclone://` backend for early adoptors
only (you have been warned).
@@ -156,11 +156,18 @@
Performance
Using an arbitrary `<giturl>` or an `sftp://` URI requires
- uploading the entire repository history with each push. If your
- repository history is large or you are pushing over a slow link,
- consider using the `rsync://` transport, which performs
- incremental pushes. Note that the latter won't work with a
- repository hosting service like Gitolite, GitHub or GitLab.
+ uploading the entire repository history with each push. This
+ means that pushes of your repository become slower over time, as
+ your git history becomes longer, and it can easily get to the
+ point that continued usage of git-remote-gcrypt is impractical.
+
+ Thus, you should use these backends only when you know that your
+ repository will not ever grow very large, not just that it's not
+ large now. This means that these backends are inappropriate for
+ most repositories, and likely suitable only for unusual cases,
+ such as small credential stores. Even then, use `rsync://` if you
+ can. Note, however, that `rsync://` won't work with a repository
+ hosting service like Gitolite, GitHub or GitLab.
rsync URIs
The URI format for the rsync backend is ``rsync://user@host/path``,
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/git-remote-gcrypt-1.4/debian/changelog
new/git-remote-gcrypt-1.5/debian/changelog
--- old/git-remote-gcrypt-1.4/debian/changelog 2021-01-22 02:46:47.000000000
+0100
+++ new/git-remote-gcrypt-1.5/debian/changelog 2022-08-21 23:39:13.000000000
+0200
@@ -1,3 +1,15 @@
+git-remote-gcrypt (1.5-1) unstable; urgency=medium
+
+ * Pass --error-on-no-transfer to 'rclone copyto'.
+ Thanks to Nathan Todd-Stone for the patch.
+ * README.md:
+ - explain why the arbitrary <giturl> and sftp:// backends are
+ inappropriate for most git repositories
+ - use stronger language to say that one should use local or rsync://
+ instead, and also say it up in "Description".
+
+ -- Sean Whitton <[email protected]> Sun, 21 Aug 2022 14:38:58 -0700
+
git-remote-gcrypt (1.4-1) unstable; urgency=medium
Upstream:
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore' old/git-remote-gcrypt-1.4/git-remote-gcrypt
new/git-remote-gcrypt-1.5/git-remote-gcrypt
--- old/git-remote-gcrypt-1.4/git-remote-gcrypt 2021-01-22 02:46:47.000000000
+0100
+++ new/git-remote-gcrypt-1.5/git-remote-gcrypt 2022-08-21 23:39:13.000000000
+0200
@@ -238,7 +238,7 @@
(exec 0>&-; rsync -I -W "$(rsynclocation "$1")"/"$2" "$3" >&2)
elif isurl rclone "$1"
then
- (exec 0>&-; rclone copyto "${1#rclone://}"/"$2" "$3" >&2)
+ (exec 0>&-; rclone copyto --error-on-no-transfer
"${1#rclone://}"/"$2" "$3" >&2)
elif islocalrepo "$1"
then
cat "$1/$2" > "$3"
@@ -258,7 +258,7 @@
rsync $Conf_rsync_put_flags -I -W "$3" "$(rsynclocation
"$1")"/"$2" >&2
elif isurl rclone "$1"
then
- rclone copyto "$3" "${1#rclone://}"/"$2" >&2
+ rclone copyto --error-on-no-transfer "$3" "${1#rclone://}"/"$2"
>&2
elif islocalrepo "$1"
then
cat >| "$1/$2" < "$3"
