Related to the db recipe. There are also the patches that needs to be
regenerated as the same patches are applied for the two current versions.
At least on Ubuntu 16.06 the same patch can't be applied anymore on the
two versions as the lines where to apply the patches differs too much.
Le 28/09/2016 18:24, Burton, Ross a écrit :
On 28 September 2016 at 17:06, Aníbal Limón
<[email protected] <mailto:[email protected]>>
wrote:
@@ -18,16 +18,15 @@ RCONFLICTS_${PN} = "db3"
PR = "r1"
Remove this PR please.
# Note, when upgraded to 6.1.x, a patch in RPM will need to be
removed to activate db 6.1 support.
-
-SRC_URI = "http://download.oracle.com/berkeley-db/db-${PV}.tar.gz
<http://download.oracle.com/berkeley-db/db-$%7BPV%7D.tar.gz> \
+SRC_URI = "http://distfiles.gentoo.org/distfiles/db-${PV}.tar.gz
<http://distfiles.gentoo.org/distfiles/db-$%7BPV%7D.tar.gz> \
What is distfiles.gentoo.org <http://distfiles.gentoo.org>'s policy
when db-6.0.36 is released? Could the tarball be deleted the day
after we release? In general we've been either using
snapshot.debian.org <http://snapshot.debian.org> or pointing directly
at the yoctoproject.org <http://yoctoproject.org> source mirror for
tarballs we can't rely upon over time.
Ross
--
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core
