From: Martin Jansa <martin.jansa@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Koen Kooi <koen@dominion.thruhere.net>,
openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH] imagemagick: upgrade from 7.0.5 to 7.0.6p4
Date: Wed, 9 Aug 2017 10:17:44 +0200 [thread overview]
Message-ID: <20170809081744.GA3394@jama> (raw)
In-Reply-To: <CAMKF1spVbt=sEkrkrJbPjLJ=SRC7zAkPKy4A9xUK1OR=90pOMQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2235 bytes --]
On Tue, Aug 08, 2017 at 07:42:59PM -0700, Khem Raj wrote:
> On Tue, Aug 8, 2017 at 7:28 PM, Andreas Müller
> <schnitzeltony@googlemail.com> wrote:
> > On Wed, Aug 9, 2017 at 4:02 AM, Randy MacLeod
> > <randy.macleod@windriver.com> wrote:
> >> On 2017-08-08 08:42 PM, Khem Raj wrote:
> >>>
> >>> I am seeing
> >>>
> >>> downloads
> >>> 'http://www.imagemagick.org/download/releases/ImageMagick-7.0.6-4.tar.xz'
> >>> --progress=dot -v failed with exit code 8, output:
> >>> --2017-08-08 15:05:59--
> >>> http://www.imagemagick.org/download/releases/ImageMagick-7.0.6-4.tar.xz
> >>> Resolving www.imagemagick.org... 198.72.81.86
> >>> Connecting to www.imagemagick.org|198.72.81.86|:80... connected.
> >>> HTTP request sent, awaiting response... 404 Not Found
> >>> 2017-08-08 15:05:59 ERROR 404: Not Found.
> >>>
> >>>
> >>> ERROR: imagemagick-7.0.6-r0 do_fetch: Fetcher failure for URL:
> >>> 'http://www.imagemagick.org/download/releases/ImageMagick-7.0.6-4.tar.xz'.
> >>> Unable to fetch URL from any source.
> >>> ERROR: imagemagick-7.0.6-r0 do_fetch: Function failed: base_do_fetch
> >>> ERROR: Logfile of failure stored in:
> >>>
> >>> /mnt/a/oe/build/tmp/work/cortexa7t2hf-neon-vfpv4-bec-linux-gnueabi/imagemagick/7.0.6-r0/temp/log.do_fetch.17282
> >>
> >>
> >> Ugh, the imagemagick devs have moved on to:
> >> http://www.imagemagick.org/download/releases/ImageMagick-7.0.6-5.tar.gz
> >>
> >> and deleted the 7.0.6-4 tarball already!
> >> I'll send a patch in the morning and also talk to upstream about their
> >> archiving policy. I don't see a directory for that at the moment.
> >>
> >> Thanks for the heads up.
> >>
> >> ../Randy
> >>
> > Yes and they will do it again until 7-0.7.x comes up :(
>
> I think we should copy the tarballs to source.openembedded.org before
> accepting imagemagick updates.
That's what my jenkins builds do (or at least should do) once they build
this.
>
> >
> > Andreas
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]
next prev parent reply other threads:[~2017-08-09 8:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 17:01 [meta-oe][PATCH] imagemagick: upgrade from 7.0.5 to 7.0.6p4 Randy MacLeod
2017-08-01 19:52 ` Koen Kooi
2017-08-02 15:29 ` Randy MacLeod
2017-08-02 17:21 ` Koen Kooi
2017-08-02 19:57 ` Randy MacLeod
2017-08-09 0:42 ` Khem Raj
2017-08-09 2:02 ` Randy MacLeod
2017-08-09 2:28 ` Andreas Müller
2017-08-09 2:42 ` Khem Raj
2017-08-09 8:17 ` Martin Jansa [this message]
2017-08-09 16:55 ` Martin Jansa
2017-08-09 17:28 ` Randy MacLeod
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=20170809081744.GA3394@jama \
--to=martin.jansa@gmail.com \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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.