From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] synergy: change upstream location to fix download issues
Date: Sun, 2 Sep 2018 22:45:05 +0200 [thread overview]
Message-ID: <20180902204505.30928-1-thomas.petazzoni@bootlin.com> (raw)
The Github repository at https://github.com/symless/synergy no longer
exists, it has apparently been moved to
https://github.com/symless/synergy-core.
On master as of 811734ef9044bbdfc067da76358153061fae2031, we use
v1.8.8, which fails to download from github.com, so we fallback to
sources.buildroot.net, which has the tarball.
However, on next as of 7da2748c9ef4e67a060ea7eb6ff23275da235daa, we
use v2.1.0, which completely fails to download, as we don't have a
backup tarball on sources.buildroot.net.
This commit fixes that by using the new upstream
location. Unfortunately, the hash changes, because the prefix in the
tarball is changed from synergy-1.8.8-stable/ to
synergy-core-1.8.8-stable/. There are no other changes. This means
that people having existing tarballs locally we'll see them being
re-downloaded because the hash has changed.
Fixes (once applied to next):
http://autobuild.buildroot.net/results/82ae9a378b70a3d27e78e1d80a63495b37329e16/
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
---
package/synergy/Config.in | 2 +-
package/synergy/synergy.hash | 2 +-
package/synergy/synergy.mk | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/package/synergy/Config.in b/package/synergy/Config.in
index 3bb8b8e98c..2f99cdf6fc 100644
--- a/package/synergy/Config.in
+++ b/package/synergy/Config.in
@@ -14,7 +14,7 @@ config BR2_PACKAGE_SYNERGY
operating systems, each with its own display,
without special hardware.
- https://github.com/symless/synergy/
+ https://github.com/symless/synergy-core/
comment "synergy needs a toolchain w/ C++, wchar"
depends on BR2_PACKAGE_XORG7
diff --git a/package/synergy/synergy.hash b/package/synergy/synergy.hash
index 52f9d74d6b..34d4b99050 100644
--- a/package/synergy/synergy.hash
+++ b/package/synergy/synergy.hash
@@ -1,2 +1,2 @@
# Locally computed:
-sha256 85c388f93881d741981ce3c675e840a52a76883cb2cea1da306c0c453c5d7d9b synergy-v1.8.8-stable.tar.gz
+sha256 9ee45aabf9f77925bfab6248e713ae5d9e6bfe6bc246e4a0a6304dc6a30f5f14 synergy-v1.8.8-stable.tar.gz
diff --git a/package/synergy/synergy.mk b/package/synergy/synergy.mk
index 76a4004f06..932a2ee9dc 100644
--- a/package/synergy/synergy.mk
+++ b/package/synergy/synergy.mk
@@ -5,7 +5,7 @@
################################################################################
SYNERGY_VERSION = v1.8.8-stable
-SYNERGY_SITE = $(call github,symless,synergy,$(SYNERGY_VERSION))
+SYNERGY_SITE = $(call github,symless,synergy-core,$(SYNERGY_VERSION))
SYNERGY_LICENSE = GPL-2.0
SYNERGY_LICENSE_FILES = LICENSE
SYNERGY_DEPENDENCIES = libcurl openssl xlib_libX11 xlib_libXtst
--
2.14.4
next reply other threads:[~2018-09-02 20:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-02 20:45 Thomas Petazzoni [this message]
2018-09-03 7:20 ` [Buildroot] [PATCH] synergy: change upstream location to fix download issues Peter Korsgaard
2018-09-03 8:26 ` Thomas Petazzoni
2018-09-03 8:54 ` Peter Korsgaard
2018-09-03 22:25 ` Arnout Vandecappelle
2018-09-04 8:03 ` Thomas Petazzoni
2018-09-04 8:52 ` Arnout Vandecappelle
2018-09-06 7:05 ` Peter Korsgaard
2018-09-08 20:41 ` Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180902204505.30928-1-thomas.petazzoni@bootlin.com \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox