Skip to contentSkip to conversation

apache2: the download has been moved to the 'archives'

PATCH In review Mark Asselstine 6 participants 9 messages Dec 21, 2016 – Dec 23, 2016

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 apache2: the download has been moved to the 'archives'

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.

---
 meta-webserver/recipes-httpd/apache2/apache2-native_2.4.23.bb | 2 +-
 meta-webserver/recipes-httpd/apache2/apache2_2.4.23.bb        | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
meta-webserver/recipes-httpd/apache2/apache2-native_2.4.23.bb +1 -1
index b227f19..aa26cc7 100644
@@ -8,7 +8,7 @@ LICENSE = "Apache-2.0"
 
 inherit autotools pkgconfig native
 
-SRC_URI = "http://www.apache.org/dist/httpd/httpd-${PV}.tar.bz2 \
+SRC_URI = "http://archive.apache.org/dist/httpd/httpd-${PV}.tar.bz2 \
            file://0001-configure-use-pkg-config-for-PCRE-detection.patch \
           "
 
meta-webserver/recipes-httpd/apache2/apache2_2.4.23.bb +1 -1
index b78ff51..79f6295 100644
@@ -6,7 +6,7 @@ DEPENDS = "libtool-native apache2-native openssl expat pcre apr apr-util"
 SECTION = "net"
 LICENSE = "Apache-2.0"
 
-SRC_URI = "http://www.apache.org/dist/httpd/httpd-${PV}.tar.bz2 \
+SRC_URI = "http://archive.apache.org/dist/httpd/httpd-${PV}.tar.bz2 \
            file://server-makefile.patch \
            file://httpd-2.4.1-corelimit.patch \
            file://httpd-2.4.4-export.patch \
Signature · 1 line
2.7.4
#1 lore raw
Quoted 6 lines · Mark Asselstine

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.

Wouldn’t it make sense to do a recipe-local addition to MIRRORS to automatically fall back to the apache archive?

Signature · 5 lines
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
#2 lore raw
Quoted 7 lines · Christopher Larson
Quoted 4 lines · Mark Asselstine

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.

Quoted 5 lines
Quoted 2 lines

Wouldn’t it make sense to do a recipe-local addition to MIRRORS to automatically fall back to the apache archive?

Not something I thought about but as long as I can find an example I am fine adjusting my approach.

Mark

Quoted 11 lines

--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
--
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

#3 lore raw
In reply to Christopher Larson
Quoted 7 lines · Christopher Larson
Quoted 4 lines · Mark Asselstine

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.

Quoted 6 lines
Quoted 2 lines

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

#4 lore raw
Quoted 15 lines · Mark Hatle
Quoted 7 lines · Christopher Larson
Quoted 4 lines · Mark Asselstine

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.

Quoted 6 lines
Quoted 2 lines

Wouldn’t it make sense to do a recipe-local addition to MIRRORS to automatically fall back to the apache archive?

Quoted 8 lines

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

Quoted 5 lines

--
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

#5 lore raw

Your original change was already supersedded by the upgrade sent by someone else.

Quoted 53 lines · M. Asselstine
Quoted 8 lines · Mark Hatle
Quoted 7 lines · Christopher Larson
Quoted 4 lines · Mark Asselstine

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.

Quoted 8 lines
Quoted 6 lines
Quoted 2 lines

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

Quoted 1 line

for the archive. If the archive moves, then the recipe should be

updated to match.

Quoted 2 lines

I know you can easily do local workarounds for mirrors and such, but I

wouldn't

Quoted 1 line

consider putting them into a recipe directly as a good approach as it

will hide

Quoted 1 line

problems from people and make it unclear where the official download

location is.

Quoted 2 lines

--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

Quoted 5 lines

--
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

--
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

#6 lore raw

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.

Quoted 65 lines · Martin Jansa

Your original change was already supersedded by the upgrade sent by someone else.

Quoted 47 lines · M. Asselstine
Quoted 8 lines · Mark Hatle
Quoted 7 lines · Christopher Larson
Quoted 4 lines · Mark Asselstine

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.

Quoted 8 lines
Quoted 6 lines
Quoted 2 lines

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

Quoted 1 line

for the archive. If the archive moves, then the recipe should be

updated to match.

Quoted 2 lines

I know you can easily do local workarounds for mirrors and such, but I

wouldn't

Quoted 1 line

consider putting them into a recipe directly as a good approach as it

will hide

Quoted 1 line

problems from people and make it unclear where the official download

location is.

Quoted 2 lines

--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

Quoted 5 lines

--
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

Quoted 6 lines

--
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

--
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

#7 lore raw
Quoted 4 lines · Derek Straka

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

Quoted 74 lines
Quoted 59 lines · Martin Jansa

Your original change was already supersedded by the upgrade sent by someone else.

Quoted 47 lines · M. Asselstine
Quoted 8 lines · Mark Hatle
Quoted 7 lines · Christopher Larson
Quoted 4 lines · Mark Asselstine

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.

Quoted 8 lines
Quoted 6 lines
Quoted 2 lines

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

Quoted 1 line

for the archive. If the archive moves, then the recipe should be

updated to match.

Quoted 2 lines

I know you can easily do local workarounds for mirrors and such, but I

wouldn't

Quoted 1 line

consider putting them into a recipe directly as a good approach as it

will hide

Quoted 1 line

problems from people and make it unclear where the official download

location is.

Quoted 2 lines

--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

Quoted 5 lines

--
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

Quoted 6 lines

--
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

Quoted 6 lines

--
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

--
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

#8 lore raw
In reply to Mark Hatle

In this case (and all where the source is moved to archive subdirectory or site as soon as there is newer release available) I think it's OK, especially when it's local for just the recipe.

Otherwise the "proper upstream location" can disappear at any time, like just after we release the metadata - and nobody will go back to morty, krogoth, jethro, dizzy to check how many apache2 archives were affected to fix all the SRC_URIs in recipes.

Quoted 34 lines · Mark Hatle
Quoted 7 lines · Christopher Larson
Quoted 4 lines · Mark Asselstine

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.

Quoted 6 lines
Quoted 2 lines

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
--
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-devel