From: Martin Jansa <martin.jansa@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH] libmikmod: fix SRC_URI
Date: Sat, 25 May 2019 02:41:18 +0200 [thread overview]
Message-ID: <CA+chaQdjacqx2W6tLZzPYL7kV9LBo24C19Y+PX5jUHTerfsW0Q@mail.gmail.com> (raw)
In-Reply-To: <CAMKF1sr0TFOdj0=mTSQ9ixBup8K_QjsSPBTqd4kL7rS23b+NXw@mail.gmail.com>
You mean like in:
http://git.openembedded.org/meta-openembedded-contrib/commit/?h=jansa/master&id=5a1a79dcdfbf4f9ba22c93ded2ad2537ece02e23
?
Because that will be sent later when it's better tested and the upgrade
probably won't be backported to warrior/thud.
BTW: All versions except last one in 3.1 and 3.3 series (both from 2017)
were moved to outdated_versions.
Similarly now e.g. mesa 17.* is moved to archive/older-versions/17.x/ and
only 18.* is kept in archive/..
Luckily all these archives are on sources.oe.org, so people using that
won't see the issues.
On Sat, May 25, 2019 at 2:16 AM Khem Raj <raj.khem@gmail.com> wrote:
>
>
> On Fri, May 24, 2019 at 4:40 PM Martin Jansa <martin.jansa@gmail.com>
> wrote:
>
>> * it was moved to outdated_versions directory
>>
>
> Why not update to a version which is not outdated
>
>>
>> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
>> ---
>> meta-oe/recipes-multimedia/mikmod/libmikmod_3.3.6.bb | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/meta-oe/recipes-multimedia/mikmod/libmikmod_3.3.6.bb
>> b/meta-oe/recipes-multimedia/mikmod/libmikmod_3.3.6.bb
>> index d53dff6a07..bbf58f9540 100644
>> --- a/meta-oe/recipes-multimedia/mikmod/libmikmod_3.3.6.bb
>> +++ b/meta-oe/recipes-multimedia/mikmod/libmikmod_3.3.6.bb
>> @@ -6,7 +6,7 @@ LIC_FILES_CHKSUM =
>> "file://COPYING.LESSER;md5=4fbd65380cdd255951079008b364516c"
>> DEPENDS = "alsa-lib texinfo"
>>
>> SRC_URI = "\
>> -
>> ${SOURCEFORGE_MIRROR}/project/mikmod/${BPN}/${PV}/${BPN}-${PV}.tar.gz \
>> +
>> ${SOURCEFORGE_MIRROR}/project/mikmod/outdated_versions/${BPN}/${PV}/${BPN}-${PV}.tar.gz
>> \
>> "
>> SRC_URI[md5sum] = "9dd9bed30c6f7607a55480234606071b"
>> SRC_URI[sha256sum] =
>> "3f363e03f7b1db75b9b6602841bbd440ed275a548e53545f980df8155de4d330"
>> --
>> 2.17.1
>>
>> --
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>>
>
next prev parent reply other threads:[~2019-05-25 0:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 23:39 [meta-oe][PATCH] libmikmod: fix SRC_URI Martin Jansa
2019-05-25 0:16 ` Khem Raj
2019-05-25 0:41 ` Martin Jansa [this message]
2019-05-25 0:59 ` Khem Raj
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=CA+chaQdjacqx2W6tLZzPYL7kV9LBo24C19Y+PX5jUHTerfsW0Q@mail.gmail.com \
--to=martin.jansa@gmail.com \
--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.