All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCHv2] db: Upgrade to 6.0.35
@ 2016-09-28 16:06 Aníbal Limón
  2016-09-28 16:24 ` Burton, Ross
  0 siblings, 1 reply; 7+ messages in thread
From: Aníbal Limón @ 2016-09-28 16:06 UTC (permalink / raw)
  To: openembedded-core; +Cc: 00moses.alexander00

The SRC_URI was changed to point gentoo distfiles because now Oracle
request authorization for download the source code [1], there are no changes
in the LICENSE since version 6.0.20 when the LICENSE changes to AGPL-3
[2], also the md5sum was review to be sure that is the same.

This minor upgrade fix an issue related to multiple rpm instances querying
the database [3].

The bugfixes related are,

- Fixed a bug that may lead to a crash when opening multiple environments
in a multi-threaded program.
- Fixed a bug where closing a panic environment raised access violation
  and crashed the program.

For see the complete list of changes mostly bugfixes between 6.0.30 and 6.0.35 [4].

[1] http://download.oracle.com/otn/berkeley-db/db-6.0.35.tar.gz
[2] http://download.oracle.com/otndocs/products/berkeleydb/html/changelog_6_0.html#idp509784
[3] https://bugzilla.yoctoproject.org/show_bug.cgi?id=10157#c0
[4] http://download.oracle.com/otndocs/products/berkeleydb/html/changelog_6_0.html#idp503384

[YOCTO #10157]

Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com>
---
 meta/recipes-support/db/{db_6.0.30.bb => db_6.0.35.bb} | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)
 rename meta/recipes-support/db/{db_6.0.30.bb => db_6.0.35.bb} (95%)

diff --git a/meta/recipes-support/db/db_6.0.30.bb b/meta/recipes-support/db/db_6.0.35.bb
similarity index 95%
rename from meta/recipes-support/db/db_6.0.30.bb
rename to meta/recipes-support/db/db_6.0.35.bb
index 072cbdf..32afbe8 100644
--- a/meta/recipes-support/db/db_6.0.30.bb
+++ b/meta/recipes-support/db/db_6.0.35.bb
@@ -18,16 +18,15 @@ RCONFLICTS_${PN} = "db3"
 PR = "r1"
 
 # 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 \
+SRC_URI = "http://distfiles.gentoo.org/distfiles/db-${PV}.tar.gz \
            file://arm-thumb-mutex_db5.patch \
            file://fix-parallel-build.patch \
            file://Makefile-let-libso_target-depend-on-bt_rec.patch \
            file://Makefile-let-libdb-6.0.la-depend-os_map.l.patch \
            "
 
-SRC_URI[md5sum] = "ad28eb86ad3203b5422844db179c585b"
-SRC_URI[sha256sum] = "608e4b1cf390e9bf54c0ef00c5bd9ca76d36e2261b9f4d33d54516f3f6a20fd2"
+SRC_URI[md5sum] = "c65a4d3e930a116abaaf69edfc697f25"
+SRC_URI[sha256sum] = "24421affa8ae436fe427ae4f5f2d1634da83d3d55a5ad6354a98eeedb825de55"
 
 # Exclude NC versions which lack AES encryption
 UPSTREAM_CHECK_REGEX = "db-(?P<pver>\d+\.\d+(\.\d+)?).tar"
-- 
2.1.4



^ permalink raw reply related	[flat|nested] 7+ messages in thread

* Re: [PATCHv2] db: Upgrade to 6.0.35
  2016-09-28 16:06 [PATCHv2] db: Upgrade to 6.0.35 Aníbal Limón
@ 2016-09-28 16:24 ` Burton, Ross
  2016-09-28 16:30   ` Julien Gueytat
  2016-09-28 17:19   ` Aníbal Limón
  0 siblings, 2 replies; 7+ messages in thread
From: Burton, Ross @ 2016-09-28 16:24 UTC (permalink / raw)
  To: Aníbal Limón; +Cc: 00moses.alexander00, OE-core

[-- Attachment #1: Type: text/plain, Size: 734 bytes --]

On 28 September 2016 at 17:06, Aníbal Limón <anibal.limon@linux.intel.com>
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 \
> +SRC_URI = "http://distfiles.gentoo.org/distfiles/db-${PV}.tar.gz \
>

What is 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 or pointing directly at the
yoctoproject.org source mirror for tarballs we can't rely upon over time.

Ross

[-- Attachment #2: Type: text/html, Size: 1732 bytes --]

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [PATCHv2] db: Upgrade to 6.0.35
  2016-09-28 16:24 ` Burton, Ross
@ 2016-09-28 16:30   ` Julien Gueytat
  2016-09-28 16:58     ` Aníbal Limón
  2016-09-28 17:19   ` Aníbal Limón
  1 sibling, 1 reply; 7+ messages in thread
From: Julien Gueytat @ 2016-09-28 16:30 UTC (permalink / raw)
  To: Burton, Ross, Aníbal Limón; +Cc: 00moses.alexander00, OE-core

[-- Attachment #1: Type: text/plain, Size: 1409 bytes --]

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 
> <anibal.limon@linux.intel.com <mailto:anibal.limon@linux.intel.com>> 
> 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
>
>


[-- Attachment #2: Type: text/html, Size: 3362 bytes --]

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [PATCHv2] db: Upgrade to 6.0.35
  2016-09-28 16:30   ` Julien Gueytat
@ 2016-09-28 16:58     ` Aníbal Limón
  0 siblings, 0 replies; 7+ messages in thread
From: Aníbal Limón @ 2016-09-28 16:58 UTC (permalink / raw)
  To: Julien Gueytat, Burton, Ross; +Cc: 00moses.alexander00, OE-core

[-- Attachment #1: Type: text/plain, Size: 1698 bytes --]



On 09/28/2016 11:30 AM, Julien Gueytat wrote:
> 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.

This is a quite strange, i'm wondering why can't be applied, i expect if
a patch fails in configure/compile stages not at patch apply.

Could you put here the error log please?

	alimon

>
> 
> Le 28/09/2016 18:24, Burton, Ross a écrit :
>>
>> On 28 September 2016 at 17:06, Aníbal Limón
>> <anibal.limon@linux.intel.com <mailto:anibal.limon@linux.intel.com>>
>> 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
>>
>>
> 
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [PATCHv2] db: Upgrade to 6.0.35
  2016-09-28 16:24 ` Burton, Ross
  2016-09-28 16:30   ` Julien Gueytat
@ 2016-09-28 17:19   ` Aníbal Limón
  1 sibling, 0 replies; 7+ messages in thread
From: Aníbal Limón @ 2016-09-28 17:19 UTC (permalink / raw)
  To: Burton, Ross; +Cc: 00moses.alexander00, OE-core

[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]



On 09/28/2016 11:24 AM, Burton, Ross wrote:
> On 28 September 2016 at 17:06, Aníbal Limón <anibal.limon@linux.intel.com>
> 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 \
>> +SRC_URI = "http://distfiles.gentoo.org/distfiles/db-${PV}.tar.gz \
>>
> 
> What is 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 or pointing directly at the
> yoctoproject.org source mirror for tarballs we can't rely upon over time.

The gentoo distfiles source mirror has older versions of Berkeley DB
hosted so i don't think they will remove the tarballs.

Also if the get fails using gentoo source mirror the next step will be
use yp source mirror that is default enabled.

Cheers,
	alimon


> 
> Ross
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [PATCHv2] db: Upgrade to 6.0.35
       [not found] <20160928172641.ABBC660017@mail.openembedded.org>
@ 2016-09-28 22:55 ` Julien Gueytat
  0 siblings, 0 replies; 7+ messages in thread
From: Julien Gueytat @ 2016-09-28 22:55 UTC (permalink / raw)
  To: openembedded-core

[-- Attachment #1: Type: text/plain, Size: 5159 bytes --]

$ bitbake -c patch db-native

WARNING: Host distribution "Ubuntu-16.04" has not been validated with 
this version of the build system; you may possibly experience unexpected 
failures. It is recommended that you use a tested distribution.

Loading cache: 100% 
|#############################################################################################################| 
ETA:  00:00:00
Loaded 2112 entries from dependency cache.
Parsing recipes: 100% 
|###########################################################################################################| 
Time: 00:00:03
Parsing of 1584 .bb files complete (1581 cached, 3 parsed). 2113 
targets, 348 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION        = "1.30.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "universal"
TARGET_SYS        = "arm-poky-linux-gnueabi"
MACHINE           = "lightpixels"
DISTRO            = "poky"
DISTRO_VERSION    = "2.1.1"
TUNE_FEATURES     = "arm armv7ve vfp thumb neon vfpv4 
callconvention-hard cortexa7"
TARGET_FPU        = "hard"
meta
meta-poky
meta-yocto-bsp    = "krogoth:d8582b7a00129175ab11f6f813552ce1a56fc7d7"
meta-raspberrypi  = "master:4817e2c087097c02755d6309304878e42cf61d3c"
meta-qt5          = "krogoth:1ec776771f5f09c97917d3839d8140f9a7668c4a"
meta-oe           = "krogoth:895b25b387cae428c38990f4d2747603ee9dc92d"
meta-lightpixels  = "krogoth:9574f1a4f48c6d057e56e6b471dd65567102de2e"

NOTE: Preparing RunQueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks

ERROR: db-native-6.0.30-r0 do_patch: Command Error: 'quilt --quiltrc 
/media/jgueytat/Projects/LightPixels/LightPixels-OperatingSystem/build/tmp/sysroots/x86_64-linux/etc/quiltrc 
push' exited with 1  Output:

Applying patch fix-parallel-build.patch

patching file Makefile.in
Hunk #1 FAILED at 1034.
1 out of 1 hunk FAILED -- rejects in file Makefile.in

Patch fix-parallel-build.patch can be reverse-applied
ERROR: db-native-6.0.30-r0 do_patch: Function failed: patch_do_patch
ERROR: Logfile of failure stored in: 
/media/jgueytat/Projects/LightPixels/LightPixels-OperatingSystem/build/tmp/work/x86_64-linux/db-native/6.0.30-r0/temp/log.do_patch.17684
ERROR: Task 1 
(virtual:native:/media/jgueytat/Projects/LightPixels/LightPixels-OperatingSystem/poky/meta/recipes-support/db/db_6.0.30.bb, 
do_patch) failed with exit code '1'

***********

By applying the patches manually with the patch command it's getting 
better but still:

jgueytat@Happy:~/Sandbox-db/db-6.0.35$ patch -p1 < 
arm-thumb-mutex_db5.patch
patching file src/dbinc/mutex_int.h
jgueytat@Happy:~/Sandbox-db/db-6.0.35$ patch -p0 < fix-parallel-build.patch
patching file dist/Makefile.in
Hunk #1 succeeded at 1041 (offset 7 lines).

#######

It's seems like the patch command accepts the patch even if the offset 
is not respected but not the way it is done during the bitbake -c patch 
db-native command.


=> I thought that two set of patches were needed to respect more 
carefully the line numbers where the changes have to be done.



Le 28/09/2016 à 19:26, Julien Gueytat a écrit :
> Alright! I'm giving you that quickly.
>
> Sent from my WIKO RAINBOW LITE 4GLe 28 sept. 2016 18:58, Aníbal Limón <anibal.limon@linux.intel.com> a écrit :
>>
>>
>> On 09/28/2016 11:30 AM, Julien Gueytat wrote:
>>> 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.
>> This is a quite strange, i'm wondering why can't be applied, i expect if
>> a patch fails in configure/compile stages not at patch apply.
>>
>> Could you put here the error log please?
>>
>> alimon
>>
>>>
>>> Le 28/09/2016 18:24, Burton, Ross a écrit :
>>>> On 28 September 2016 at 17:06, Aníbal Limón
>>>> <anibal.limon@linux.intel.com <mailto:anibal.limon@linux.intel.com>>
>>>> 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
>>>>
>>>>
>>>


[-- Attachment #2: Type: text/html, Size: 7898 bytes --]

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [PATCHv2] db: Upgrade to 6.0.35
@ 2016-09-28 17:26 Julien Gueytat
  0 siblings, 0 replies; 7+ messages in thread
From: Julien Gueytat @ 2016-09-28 17:26 UTC (permalink / raw)
  To: Aníbal Limón; +Cc: 00moses.alexander00, OE-core

Alright! I'm giving you that quickly.

Sent from my WIKO RAINBOW LITE 4GLe 28 sept. 2016 18:58, Aníbal Limón <anibal.limon@linux.intel.com> a écrit :
>
>
>
> On 09/28/2016 11:30 AM, Julien Gueytat wrote: 
> > 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. 
>
> This is a quite strange, i'm wondering why can't be applied, i expect if 
> a patch fails in configure/compile stages not at patch apply. 
>
> Could you put here the error log please? 
>
> alimon 
>
> > 
> > 
> > Le 28/09/2016 18:24, Burton, Ross a écrit : 
> >> 
> >> On 28 September 2016 at 17:06, Aníbal Limón 
> >> <anibal.limon@linux.intel.com <mailto:anibal.limon@linux.intel.com>> 
> >> 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 
> >> 
> >> 
> > 
> > 
>

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2016-09-28 22:55 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-09-28 16:06 [PATCHv2] db: Upgrade to 6.0.35 Aníbal Limón
2016-09-28 16:24 ` Burton, Ross
2016-09-28 16:30   ` Julien Gueytat
2016-09-28 16:58     ` Aníbal Limón
2016-09-28 17:19   ` Aníbal Limón
2016-09-28 17:26 Julien Gueytat
     [not found] <20160928172641.ABBC660017@mail.openembedded.org>
2016-09-28 22:55 ` Julien Gueytat

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.