[oe] [meta-webserver][PATCH] apache2: the download has been moved to the 'archives'

M. Asselstine asselsm at mcmaster.ca
Fri Dec 23 16:17:19 UTC 2016


On Fri, Dec 23, 2016 at 11:04 AM, Derek Straka <derek at asterius.io> wrote:
> It seems like we could always pull out of
> http://archive.apache.org/dist/httpd
> <http://archive.apache.org/dist/httpd/httpd-$%7BPV> in this case and avoid
> the maintenance headache Martin is alluding to.

Sounds good. I see your uprev RR so all is fine with me, glad to see
this corrected, on to other distractions.

Thanks,
MarkA


>
> On Fri, Dec 23, 2016 at 10:59 AM, Martin Jansa <martin.jansa at gmail.com>
> wrote:
>
>> Your original change was already supersedded by the upgrade sent by someone
>> else.
>>
>> On Fri, Dec 23, 2016 at 4:56 PM, M. Asselstine <asselsm at mcmaster.ca>
>> wrote:
>>
>> > On Fri, Dec 23, 2016 at 10:51 AM, Mark Hatle <mark.hatle at windriver.com>
>> > wrote:
>> > > On 12/21/16 4:26 PM, Christopher Larson wrote:
>> > >> On Wed, Dec 21, 2016 at 2:53 PM, Mark Asselstine <
>> > >> mark.asselstine at windriver.com> wrote:
>> > >>
>> > >>> This release of apache2 is no longer found in the main downloads area
>> > >>> but has been moved to the 'archives'. We should uprev apache2 but for
>> > >>> now this will at least get the builds working again.
>> > >>>
>> > >>> Signed-off-by: Mark Asselstine <mark.asselstine at windriver.com>
>> > >>>
>> > >>
>> > >> Wouldn’t it make sense to do a recipe-local addition to MIRRORS to
>> > >> automatically fall back to the apache archive?
>> > >>
>> > >
>> > > That seems wrong to me.  The recipe should point to the proper upstream
>> > location
>> > > for the archive.  If the archive moves, then the recipe should be
>> > updated to match.
>> > >
>> > > I know you can easily do local workarounds for mirrors and such, but I
>> > wouldn't
>> > > consider putting them into a recipe directly as a good approach as it
>> > will hide
>> > > problems from people and make it unclear where the official download
>> > location is.
>> > >
>> > > --Mark
>> >
>> > Agreed. I also think that the concept is a bad one as if our apache2
>> > recipe is so far behind that the upstream has moved it to archived
>> > that things should break just to give us a kick in the pants to get on
>> > top of things and complete and uprev. So rather than mess around to
>> > paper this over I hope my original change can be merged to allow
>> > builds to complete and I will look to getting a review out for an
>> > uprev after the holidays.
>> >
>> > MarkA
>> >
>> >
>> > > --
>> > > _______________________________________________
>> > > Openembedded-devel mailing list
>> > > Openembedded-devel at lists.openembedded.org
>> > > http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>> > --
>> > _______________________________________________
>> > Openembedded-devel mailing list
>> > Openembedded-devel at lists.openembedded.org
>> > http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>> >
>> --
>> _______________________________________________
>> Openembedded-devel mailing list
>> Openembedded-devel at lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>>
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel



More information about the Openembedded-devel mailing list