package/exiv2: cleanup options and licenses
PATCH 1/1 package/exiv2: cleanup options and licenses
The current version of exiv2 no longer requires a commercial option for lens database integration.
Add the dedicated licence file for CMake script.
--- package/exiv2/Config.in | 19 ++----------------- package/exiv2/exiv2.hash | 1 + package/exiv2/exiv2.mk | 16 +++++----------- 3 files changed, 8 insertions(+), 28 deletions(-)
package/exiv2/Config.in +2 -17
@@ -23,17 +23,6 @@ config BR2_PACKAGE_EXIV2 if BR2_PACKAGE_EXIV2 -config BR2_PACKAGE_EXIV2_COMMERCIAL - bool "Enable commercial" - help - Build the commercial version for closed source project. - - The Nikon lens name database and the NLS support is disabled - for copyright reasons. - - A commercial license request is needed. - http://www.exiv2.org/download.html#license - config BR2_PACKAGE_EXIV2_PNG bool "PNG image support" select BR2_PACKAGE_ZLIB
@@ -47,12 +36,8 @@ config BR2_PACKAGE_EXIV2_XMP Build with XMP support config BR2_PACKAGE_EXIV2_LENSDATA - bool "Nikon lens name database" - depends on !BR2_PACKAGE_EXIV2_COMMERCIAL + bool "Include lens data" help - Integrate Nikon lens name database. - - This database is integrated but comes from a thirdparty: - http://www.rottmerhusen.com/objektives/lensid/thirdparty.html. + Build with lens data endif
package/exiv2/exiv2.hash +1 -0
@@ -1,3 +1,4 @@ # Locally calculated sha256 1b3766b2c203ce213a4195de14d61694017ec1a69d15d4575bccecef130990fe exiv2-0.27.1.tar.gz sha256 a7ba75cb966aca374711e2af49e5f3aea6a4443a803440f5d93e73a5a1222f66 COPYING +sha256 46cde7dc11e64c78d650b4851b88f6704b4665ff60f22a1caf68ceb15e217e5b COPYING-CMAKE-SCRIPTS
package/exiv2/exiv2.mk +5 -11
@@ -7,6 +7,8 @@ EXIV2_VERSION = 0.27.1 EXIV2_SITE = $(call github,Exiv2,exiv2,$(EXIV2_VERSION)) EXIV2_INSTALL_STAGING = YES +EXIV2_LICENSE = GPL-2.0+ +EXIV2_LICENSE_FILES = COPYING COPYING-CMAKE-SCRIPTS EXIV2_CONF_OPTS += -DEXIV2_ENABLE_BUILD_SAMPLES=OFF
@@ -14,18 +16,10 @@ EXIV2_CONF_OPTS += -DEXIV2_ENABLE_BUILD_SAMPLES=OFF # test which is not allowed when cross-compiling. EXIV2_CONF_OPTS += -DTHREADS_PTHREAD_ARG=OFF -ifeq ($(BR2_PACKAGE_EXIV2_LENSDATA),) -EXIV2_CONF_OPTS += -DEXIV2_ENABLE_LENSDATA=OFF -endif - -ifeq ($(BR2_PACKAGE_EXIV2_COMMERCIAL),y) -EXIV2_LICENSE = commercial -# NLS support is disabled in commercial version due to the copyright -# of the translated texts. -EXIV2_CONF_OPTS += -DEXIV2_ENABLE_COMMERCIAL=ON -DEXIV2_ENABLE_NLS=OFF +ifeq ($(BR2_PACKAGE_EXIV2_LENSDATA),y) +EXIV2_CONF_OPTS += -DEXIV2_ENABLE_LENSDATA=ON else -EXIV2_LICENSE = GPL-2.0+ -EXIV2_LICENSE_FILES = COPYING +EXIV2_CONF_OPTS += -DEXIV2_ENABLE_LENSDATA=OFF endif ifeq ($(BR2_PACKAGE_EXIV2_PNG),y)
Signature · 1 line
2.21.0
PATCH 1/1 package/exiv2: cleanup options and licenses
Quoted 2 lines · Nicolas Serafini
The current version of exiv2 no longer requires a commercial option for lens database integration.
Since when is this (IOW, should it be backported to 2019.02.x or not)?
Quoted 15 lines
Add the dedicated licence file for CMake script.
Signed-off-by Nicolas Serafini <[email protected]>--- package/exiv2/Config.in | 19 ++----------------- package/exiv2/exiv2.hash | 1 + package/exiv2/exiv2.mk | 16 +++++----------- 3 files changed, 8 insertions(+), 28 deletions(-)package/exiv2/Config.in +0
-0
package/exiv2/Config.in config BR2_PACKAGE_EXIV2 · line 26
Quoted 4 lines
package/exiv2/Config.in +0
-1@@ -23,17 +23,6 @@ config BR2_PACKAGE_EXIV2 if BR2_PACKAGE_EXIV2 -config BR2_PACKAGE_EXIV2_COMMERCIAL
We normally add Config.in.legacy entries when an option is removed. In this
case, however, the option is turned into always-enabled, so the legacy handling doesn't do much good. So your patch is OK here.
Quoted 14 lines
package/exiv2/Config.in +0
-10- bool "Enable commercial" - help - Build the commercial version for closed source project. - - The Nikon lens name database and the NLS support is disabled - for copyright reasons. - - A commercial license request is needed. - http://www.exiv2.org/download.html#license - config BR2_PACKAGE_EXIV2_PNG bool "PNG image support" select BR2_PACKAGE_ZLIB
package/exiv2/Config.in config BR2_PACKAGE_EXIV2_XMP · line 39
Quoted 6 lines
package/exiv2/Config.in +1
-2@@ -47,12 +36,8 @@ config BR2_PACKAGE_EXIV2_XMP Build with XMP support config BR2_PACKAGE_EXIV2_LENSDATA - bool "Nikon lens name database" - depends on !BR2_PACKAGE_EXIV2_COMMERCIAL + bool "Include lens data"
How big is this lens data? Is it worth keeping an option for it?
Quoted 22 lines
package/exiv2/Config.in +1
-4help - Integrate Nikon lens name database. - - This database is integrated but comes from a thirdparty: - http://www.rottmerhusen.com/objektives/lensid/thirdparty.html. + Build with lens data endifpackage/exiv2/exiv2.hash +1
-0@@ -1,3 +1,4 @@ # Locally calculated sha256 1b3766b2c203ce213a4195de14d61694017ec1a69d15d4575bccecef130990fe exiv2-0.27.1.tar.gz sha256 a7ba75cb966aca374711e2af49e5f3aea6a4443a803440f5d93e73a5a1222f66 COPYING +sha256 46cde7dc11e64c78d650b4851b88f6704b4665ff60f22a1caf68ceb15e217e5b COPYING-CMAKE-SCRIPTSpackage/exiv2/exiv2.mk +0
-0
package/exiv2/exiv2.mk line 11
Quoted 5 lines
package/exiv2/exiv2.mk +2
-0@@ -7,6 +7,8 @@ EXIV2_VERSION = 0.27.1 EXIV2_SITE = $(call github,Exiv2,exiv2,$(EXIV2_VERSION)) EXIV2_INSTALL_STAGING = YES +EXIV2_LICENSE = GPL-2.0+ +EXIV2_LICENSE_FILES = COPYING COPYING-CMAKE-SCRIPTS
What is in this additional license file?
Regards,
Arnout
Quoted 26 lines
package/exiv2/exiv2.mk +3
-11EXIV2_CONF_OPTS += -DEXIV2_ENABLE_BUILD_SAMPLES=OFF@@ -14,18 +16,10 @@ EXIV2_CONF_OPTS += -DEXIV2_ENABLE_BUILD_SAMPLES=OFF # test which is not allowed when cross-compiling. EXIV2_CONF_OPTS += -DTHREADS_PTHREAD_ARG=OFF -ifeq ($(BR2_PACKAGE_EXIV2_LENSDATA),) -EXIV2_CONF_OPTS += -DEXIV2_ENABLE_LENSDATA=OFF -endif - -ifeq ($(BR2_PACKAGE_EXIV2_COMMERCIAL),y) -EXIV2_LICENSE = commercial -# NLS support is disabled in commercial version due to the copyright -# of the translated texts. -EXIV2_CONF_OPTS += -DEXIV2_ENABLE_COMMERCIAL=ON -DEXIV2_ENABLE_NLS=OFF +ifeq ($(BR2_PACKAGE_EXIV2_LENSDATA),y) +EXIV2_CONF_OPTS += -DEXIV2_ENABLE_LENSDATA=ON else -EXIV2_LICENSE = GPL-2.0+ -EXIV2_LICENSE_FILES = COPYING +EXIV2_CONF_OPTS += -DEXIV2_ENABLE_LENSDATA=OFF endif ifeq ($(BR2_PACKAGE_EXIV2_PNG),y)
PATCH 1/1 package/exiv2: cleanup options and licenses
Quoted 7 lines · On Wed, 8 May 2019 00:31:13 +0200 Arnout Vandecappelle <[email protected]> wrote:
Quoted 2 lines · Nicolas Serafini
The current version of exiv2 no longer requires a commercial option for lens database integration.
Since when is this (IOW, should it be backported to 2019.02.x or not)?
The commit on which the 2019.02.x is based is before the change so no need to backport. The 0.27 is the first release without the commercial option.
Quoted 43 lines
Quoted 16 lines
Add the dedicated licence file for CMake script.
Signed-off-by Nicolas Serafini <[email protected]>--- package/exiv2/Config.in | 19 ++----------------- package/exiv2/exiv2.hash | 1 + package/exiv2/exiv2.mk | 16 +++++----------- 3 files changed, 8 insertions(+), 28 deletions(-)package/exiv2/Config.in +0
-0package/exiv2/Config.in config BR2_PACKAGE_EXIV2 · line 26
Quoted 4 lines
package/exiv2/Config.in +0
-1@@ -23,17 +23,6 @@ config BR2_PACKAGE_EXIV2 if BR2_PACKAGE_EXIV2 -config BR2_PACKAGE_EXIV2_COMMERCIALWe normally add Config.in.legacy entries when an option is removed. In this
case, however, the option is turned into always-enabled, so the legacy handling doesn't do much good. So your patch is OK here.Quoted 17 lines
package/exiv2/Config.in +0
-5- bool "Enable commercial" - help - Build the commercial version for closed source project. - - The Nikon lens name database and the NLS support isdisabled
package/exiv2/Config.in +0
-4- for copyright reasons. - - A commercial license request is needed. -package/exiv2/Config.in +0
-0bool "PNG image support" select BR2_PACKAGE_ZLIB@@ -47,12 +36,8 @@ config BR2_PACKAGE_EXIV2_XMP Build with XMP support
Quoted 6 lines
package/exiv2/Config.in config BR2_PACKAGE_EXIV2_XMP · line 39
Quoted 4 lines
package/exiv2/Config.in +1
-2config BR2_PACKAGE_EXIV2_LENSDATA - bool "Nikon lens name database" - depends on !BR2_PACKAGE_EXIV2_COMMERCIAL + bool "Include lens data"How big is this lens data? Is it worth keeping an option for it?
Yes you are right we can remove it. The binary is only 80KB less with the lensdata option disabled.
Do I need to add a Config.in.legacy option if I remove it. The default state in exiv2 CMakeList is enabled.
Quoted 23 lines
Quoted 23 lines
package/exiv2/Config.in +0
-4help - Integrate Nikon lens name database. - - This database is integrated but comes from a thirdparty: -package/exiv2/Config.in +1
-0+ Build with lens data endifpackage/exiv2/exiv2.hash +0
-0@@ -1,3 +1,4 @@ # Locally calculated sha256
1b3766b2c203ce213a4195de14d61694017ec1a69d15d4575bccecef130990feexiv2-0.27.1.tar.gz sha256a7ba75cb966aca374711e2af49e5f3aea6a4443a803440f5d93e73a5a1222f66COPYING +sha25646cde7dc11e64c78d650b4851b88f6704b4665ff60f22a1caf68ceb15e217e5bCOPYING-CMAKE-SCRIPTS diff --gita/package/exiv2/exiv2.mk
Quoted 8 lines
package/exiv2/exiv2.hash
Quoted 6 lines
b/package/exiv2/exiv2.mkindexba9d9b7303..3aa2a9e088100644 ---a/package/exiv2/exiv2.mk+++b/package/exiv2/exiv2.mk@@ -7,6 +7,8 @@EXIV2_VERSION= 0.27.1EXIV2_SITE= $(call github,Exiv2,exiv2,$(EXIV2_VERSION))EXIV2_INSTALL_STAGING= YESpackage/exiv2/exiv2.hash +2
-0+EXIV2_LICENSE = GPL-2.0+ +EXIV2_LICENSE_FILES = COPYING COPYING-CMAKE-SCRIPTSWhat is in this additional license file?
It's the the BSD-3-Clause licence for CMakeLists.txt, config/FindEXPAT.cmake and config/FindMSGFMT.cmake files. I have to add the BSD-3-Clause to EXIV2_LICENCE.
Thanks for your review.
Regards,
Nicolas
Quoted 30 lines
Regards,
ArnoutQuoted 26 lines
EXIV2_CONF_OPTS+= -DEXIV2_ENABLE_BUILD_SAMPLES=OFFpackage/exiv2/exiv2.hash +0
-1@@ -14,18 +16,10 @@ EXIV2_CONF_OPTS += -DEXIV2_ENABLE_BUILD_SAMPLES=OFF # test which is not allowed whencross-compiling.
EXIV2_CONF_OPTS+= -DTHREADS_PTHREAD_ARG=OFFpackage/exiv2/exiv2.hash +2
-12-ifeq ($(BR2_PACKAGE_EXIV2_LENSDATA),) -EXIV2_CONF_OPTS += -DEXIV2_ENABLE_LENSDATA=OFF -endif - -ifeq ($(BR2_PACKAGE_EXIV2_COMMERCIAL),y) -EXIV2_LICENSE = commercial -# NLS support is disabled in commercial version due to the copyright -# of the translated texts. -EXIV2_CONF_OPTS += -DEXIV2_ENABLE_COMMERCIAL=ON -DEXIV2_ENABLE_NLS=OFF +ifeq ($(BR2_PACKAGE_EXIV2_LENSDATA),y) +EXIV2_CONF_OPTS += -DEXIV2_ENABLE_LENSDATA=ON else -EXIV2_LICENSE = GPL-2.0+ -EXIV2_LICENSE_FILES = COPYING +EXIV2_CONF_OPTS += -DEXIV2_ENABLE_LENSDATA=OFF endif ifeq ($(BR2_PACKAGE_EXIV2_PNG),y)
PATCH 1/1 package/exiv2: cleanup options and licenses
Quoted 9 lines · Nicolas Serafini
Quoted 5 lines
package/exiv2/Config.in config BR2_PACKAGE_EXIV2_XMP · line 39
Quoted 4 lines
config
BR2_PACKAGE_EXIV2_LENSDATApackage/exiv2/Config.in +1
-2- bool "Nikon lens name database" - depends on !BR2_PACKAGE_EXIV2_COMMERCIAL + bool "Include lens data"How big is this lens data? Is it worth keeping an option for it?
Yes you are right we can remove it. The binary is only 80KB less with the lensdata option disabled.
Do I need to add a Config.in.legacy option if I remove it.
No, same as for the _COMMERCIAL option. The legacy handling is there to make
sure that people who update Buildroot and had some option enabled will be able to do whatever is needed to keep the same behaviour.
It is useful to mention explicitly in the commit message why legacy handling is
skipped. Something like: "Legacy handling for the removed options _COMMERCIAL and _LENSDATA is not needed, since now they are always enabled."
Quoted 2 lines
The default
state in exiv2 CMakeList is enabled.
It is a good idea to still add the -D...=ON explicitly, because:
- it makes sure that the same behaviour is kept if the default changes; and
- if the option changes name, is removed, ... there is a warning in the configure step, so there's a better chance that whoever is doing the bump will notice it.
Regards,
Arnout
PATCH 1/1 package/exiv2: cleanup options and licenses
Hello Arnout, Nicolas,
Quoted 11 lines · Arnout Vandecappelle
Quoted 9 lines · Nicolas Serafini
Quoted 5 lines
package/exiv2/Config.in config BR2_PACKAGE_EXIV2_XMP · line 39
Quoted 4 lines
config
BR2_PACKAGE_EXIV2_LENSDATApackage/exiv2/Config.in +1
-2- bool "Nikon lens name database" - depends on !BR2_PACKAGE_EXIV2_COMMERCIAL + bool "Include lens data"How big is this lens data? Is it worth keeping an option for it?
Yes you are right we can remove it. The binary is only 80KB less with the lensdata option disabled.
Do I need to add a Config.in.legacy option if I remove it.
Quoted 7 lines
No, same as for the
_COMMERCIALoption. The legacy handling is there to make
sure that people who update Buildroot and had some option enabled will be able to do whatever is needed to keep the same behaviour.It is useful to mention explicitly in the commit message why legacy handling is
skipped. Something like: "Legacy handling for the removed options_COMMERCIALand_LENSDATAis not needed, since now they are always enabled."
Disagree with this reasoning, o.k. for the enable-_LENSDATA option, NAK for the _COMMERCIAL one (users who selected _COMMERCIAL before will now get GPL-2.0+ without warning/notice)...
Regards,
Peter
Quoted 16 lines
Quoted 3 lines
The default
state in exiv2 CMakeList is enabled.It is a good idea to still add the -D...=ON explicitly, because:
- it makes sure that the same behaviour is kept if the default changes; and
- if the option changes name, is removed, ... there is a warning in the configure step, so there's a better chance that whoever is doing the bump will notice it.Regards,
Arnout
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
PATCH 1/1 package/exiv2: cleanup options and licenses
Quoted 19 lines · Peter Seiderer
Hello Arnout, Nicolas,
Quoted 15 lines · Arnout Vandecappelle
Quoted 9 lines · Nicolas Serafini
Quoted 5 lines
package/exiv2/Config.in config BR2_PACKAGE_EXIV2_XMP · line 39
Quoted 4 lines
config
BR2_PACKAGE_EXIV2_LENSDATApackage/exiv2/Config.in +1
-2- bool "Nikon lens name database" - depends on !BR2_PACKAGE_EXIV2_COMMERCIAL + bool "Include lens data"How big is this lens data? Is it worth keeping an option for it?
Yes you are right we can remove it. The binary is only 80KB less with the lensdata option disabled.
Do I need to add a Config.in.legacy option if I remove it.
No, same as for the
_COMMERCIALoption. The legacy handling is there to make
sure that people who update Buildroot and had some option enabled will be able to do whatever is needed to keep the same behaviour.
Quoted 7 lines
Quoted 3 lines
It is useful to mention explicitly in the commit message why legacy handling is
skipped. Something like: "Legacy handling for the removed options_COMMERCIALand_LENSDATAis not needed, since now they are always enabled."Disagree with this reasoning, o.k. for the enable-_LENSDATA option, NAK for the
_COMMERCIALone (users who selected_COMMERCIALbefore will now get GPL-2.0+ without warning/notice)...
OK, so I studied this in a bit more detail, and it's actually more complicated
than that...
The Nikon lens data has a different license, which is this:
// Free use in non-commercial, GPL or open source software only! // Please contact me for adding lenses or use in commercial software.
So the problem is not so much that you force GPL; it is that you are not
allowed to use this in commercial software.
So, at first sight, we should keep the LENSDATA option as an option, mention in
the help text that it cannot be used for commercial use, and if the option is selected update EXIV2_LICENSE with something like "Rottmerhusen non-commercial license" and add src/nikonmn_int.cpp to EXIV2_LICENSE_FILES.
However, I wonder about the validity of this thing. First, the piece of code is
just a database - in principle, it's not copyrightable. Second, the same database is also included in exiftool, and that source code doesn't have a similar clause (exiftool is Artistic-licensed). Third, I tried to look up the real source (http://rottmerhusen.com) but that site has gone down and the wayback machine doesn't give me anything with such a license.
If we would package exiv2 now, we probably never would have noticed this
license issue...
So, let's go for the simple and pragmatic solution: keep the _LENSDATA option,
maybe mention in the help text something about the non-commercial use.
Which is, essentially, v1 of this patch...
Nicolas, sorry for the back-and-forth, and thank you for your patience.
Peter, thanks for finding this issue.
Regards,
Arnout
Quoted 21 lines
Regards,
PeterQuoted 16 lines
Quoted 3 lines
The default
state in exiv2 CMakeList is enabled.It is a good idea to still add the -D...=ON explicitly, because:
- it makes sure that the same behaviour is kept if the default changes; and
- if the option changes name, is removed, ... there is a warning in the configure step, so there's a better chance that whoever is doing the bump will notice it.Regards,
Arnout
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot
PATCH 1/1 package/exiv2: cleanup options and licenses
Hello Arnout, Peter,
Quoted 65 lines · On Wed, 5 Jun 2019 00:59:03 +0200 Arnout Vandecappelle <[email protected]> wrote:
Quoted 20 lines · Peter Seiderer
Hello Arnout, Nicolas,
Quoted 16 lines · Arnout Vandecappelle
Quoted 9 lines · Nicolas Serafini
Quoted 5 lines
package/exiv2/Config.in config BR2_PACKAGE_EXIV2_XMP · line 39
Quoted 4 lines
config
BR2_PACKAGE_EXIV2_LENSDATApackage/exiv2/Config.in +1
-2- bool "Nikon lens name database" - depends on !BR2_PACKAGE_EXIV2_COMMERCIAL + bool "Include lens data"How big is this lens data? Is it worth keeping an option for it?
Yes you are right we can remove it. The binary is only 80KB less with the lensdata option disabled.
Do I need to add a Config.in.legacy option if I remove it.
No, same as for the
_COMMERCIALoption. The legacy handling is
there to make sure that people who update Buildroot and had some option enabled will be able to do whatever is needed to keep the same behaviour.Quoted 8 lines
Quoted 4 lines
It is useful to mention explicitly in the commit message why
legacy handling is skipped. Something like: "Legacy handling for the removed options_COMMERCIALand_LENSDATAis not needed, since now they are always enabled."Disagree with this reasoning, o.k. for the enable-_LENSDATA option, NAK for the
_COMMERCIALone (users who selected_COMMERCIALbefore will now get GPL-2.0+ without warning/notice)...OK, so I studied this in a bit more detail, and it's actually more complicated
than that...The Nikon lens data has a different license, which is this:
// Free use in non-commercial, GPL or open source software only! // Please contact me for adding lenses or use in commercial software.
So the problem is not so much that you force GPL; it is that you are not
allowed to use this in commercial software.So, at first sight, we should keep the LENSDATA option as an option, mention in
the help text that it cannot be used for commercial use, and if the option is selected updateEXIV2_LICENSEwith something like "Rottmerhusen non-commercial license" and add src/nikonmn_int.cpp toEXIV2_LICENSE_FILES.However, I wonder about the validity of this thing. First, the piece of code is
just a database - in principle, it's not copyrightable. Second, the same database is also included in exiftool, and that source code doesn't have a similar clause (exiftool is Artistic-licensed). Third, I tried to look up the real source
(https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Frottmerhusen.com&data=02%7C01%7Cnicolas.serafini%40sensefly.com%7C59de32933c1d477ebd4208d6e9403ee9%7Cff7d991b392248038418ab806a3414a6%7C1%7C0%7C636952859484138627&sdata=Y69lDoAl88GHxTx5uQh9jybvxYENiDudLZ2d2QUNw5U%3D&reserved=0)
but that site has gone down and the wayback machine doesn't give me anything with such a license.If we would package exiv2 now, we probably never would have noticed this
license issue...
Quoted 8 lines
So, let's go for the simple and pragmatic solution: keep the
_LENSDATAoption,
maybe mention in the help text something about the non-commercial use.Which is, essentially, v1 of this patch...
Nicolas, sorry for the back-and-forth, and thank you for your patience.
Thanks for your feedback I prepare a patch v4.
Quoted 28 lines
Peter, thanks for finding this issue.
Regards,
ArnoutQuoted 22 lines
Regards,
PeterQuoted 17 lines
Quoted 3 lines
The default
state in exiv2 CMakeList is enabled.It is a good idea to still add the -D...=ON explicitly, because:
- it makes sure that the same behaviour is kept if the default changes; and
- if the option changes name, is removed, ... there is a warning in the configure step, so there's a better chance that whoever is doing the bump will notice it.Regards,
Arnout
_______________________________________________
buildroot mailing list
buildroot at busybox.net
https://eur02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.busybox.net%2Fmailman%2Flistinfo%2Fbuildroot&data=02%7C01%7Cnicolas.serafini%40sensefly.com%7C59de32933c1d477ebd4208d6e9403ee9%7Cff7d991b392248038418ab806a3414a6%7C1%7C0%7C636952859484148621&sdata=HU4Z4xAyVjW3V001nozXz7wRd8wgaNq%2F0JXzjj1Ttos%3D&reserved=0