From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/monit: bump to version 5.16.1
Date: Mon, 22 Feb 2016 10:27:04 +0100 [thread overview]
Message-ID: <1456133224.27562.5.camel@embedded.rocks> (raw)
In-Reply-To: <20160221220537.05f829bd@free-electrons.com>
Dear Thomas,
On So, 2016-02-21 at 22:05 +0100, Thomas Petazzoni wrote:
> Dear J?rg Krause,
>
> On Tue,??9 Feb 2016 14:46:32 +0100, J?rg Krause wrote:
> >
> > Signed-off-by: J?rg Krause <joerg.krause@embedded.rocks>
> > ---
> > ?package/monit/monit.hash | 4 ++--
> > ?package/monit/monit.mk???| 2 +-
> > ?2 files changed, 3 insertions(+), 3 deletions(-)
> This doesn't build, as there is no 5.16.1 release upstream:
>
> >
> > >
> > > >
> > > > monit 5.16.1 Downloading
> --2016-02-21 21:54:17--??http://mmonit.com/monit/dist/monit-5.16.1.ta
> r.gz
> Resolving mmonit.com (mmonit.com)... 62.109.39.247
> Connecting to mmonit.com (mmonit.com)|62.109.39.247|:80... connected.
> HTTP request sent, awaiting response... 302 Found
> Location: https://mmonit.com/monit/dist/monit-5.16.1.tar.gz
> [following]
> --2016-02-21 21:54:17--??https://mmonit.com/monit/dist/monit-5.16.1.t
> ar.gz
> Connecting to mmonit.com (mmonit.com)|62.109.39.247|:443...
> connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2016-02-21 21:54:17 ERROR 404: Not Found.
>
> Looking at https://mmonit.com/monit/dist/, the last version is 5.16.
>
> How did you find a 5.16.1 version ?
Looks like it was removed meanwhile:
$ ls dl/monit-*.tar.gz
dl/monit-5.16.1.tar.gz
I'll prepare a new patch for this package.
Best regards
J?rg Krause
prev parent reply other threads:[~2016-02-22 9:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 13:46 [Buildroot] [PATCH] package/monit: bump to version 5.16.1 Jörg Krause
2016-02-21 21:05 ` Thomas Petazzoni
2016-02-22 9:27 ` Jörg Krause [this message]
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=1456133224.27562.5.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.