Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] xinetd: change to snapshot.debian.org and add hash
Date: Sat, 1 Nov 2014 17:43:16 +0100	[thread overview]
Message-ID: <20141101164316.GB10189@free.fr> (raw)
In-Reply-To: <1414859755-33664-1-git-send-email-kaszak@gmail.com>

Karoly, All,

On 2014-11-01 17:35 +0100, Karoly Kasza spake thusly:
> xinetd.org seems down quite some time, so change to snapshot.debian.org.

Indeed, it's down from here, too... :-(

> Also add hash.

Manually downloaded and verified the two hashes.

> Signed-off-by: Karoly Kasza <kaszak@gmail.com>

Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr>

Regards,
Yann E. MORIN.

> ---
>  package/xinetd/xinetd.hash |    4 ++++
>  package/xinetd/xinetd.mk   |    3 ++-
>  2 files changed, 6 insertions(+), 1 deletion(-)
>  create mode 100644 package/xinetd/xinetd.hash
> 
> diff --git a/package/xinetd/xinetd.hash b/package/xinetd/xinetd.hash
> new file mode 100644
> index 0000000..f656422
> --- /dev/null
> +++ b/package/xinetd/xinetd.hash
> @@ -0,0 +1,4 @@
> +# From snapshot.debian.org dsc file
> +sha1	168d54aeb181e271e68f4c53847c3e6b2574dba6				xinetd_2.3.15.orig.tar.gz
> +sha256	bf4e060411c75605e4dcbdf2ac57c6bd9e1904470a2f91e01ba31b50a80a5be3	xinetd_2.3.15.orig.tar.gz
> +
> diff --git a/package/xinetd/xinetd.mk b/package/xinetd/xinetd.mk
> index 1fb91b5..7060f0c 100644
> --- a/package/xinetd/xinetd.mk
> +++ b/package/xinetd/xinetd.mk
> @@ -5,7 +5,8 @@
>  ################################################################################
>  
>  XINETD_VERSION = 2.3.15
> -XINETD_SITE = http://www.xinetd.org
> +XINETD_SOURCE = xinetd_$(XINETD_VERSION).orig.tar.gz
> +XINETD_SITE = http://snapshot.debian.org/archive/debian/20141023T043132Z/pool/main/x/xinetd
>  XINETD_LICENSE = xinetd license
>  XINETD_LICENSE_FILES = COPYRIGHT
>  
> -- 
> 1.7.10.4
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20141101/266b2e49/attachment.asc>

  reply	other threads:[~2014-11-01 16:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-01 16:35 [Buildroot] [PATCH 1/1] xinetd: change to snapshot.debian.org and add hash Karoly Kasza
2014-11-01 16:43 ` Yann E. MORIN [this message]
2014-11-01 17:02 ` Thomas Petazzoni
2014-11-01 17:06   ` Károly Kasza
2014-11-01 17:12     ` Károly Kasza
2014-11-01 17:20     ` Yann E. MORIN
2014-11-01 17:22       ` Károly Kasza

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=20141101164316.GB10189@free.fr \
    --to=yann.morin.1998@free.fr \
    --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