[OE-core] [PATCH 2/2] mpfr: Upgrade to 4.0.2 release

[Richard Purdie]

On Mon, 2019-02-04 at 16:36 -0800, Khem Raj wrote:
> --- /dev/null
> +++ b/meta/recipes-support/mpfr/mpfr_4.0.2.bb
> @@ -0,0 +1,94 @@
> +# FIXME: the LIC_FILES_CHKSUM values have been updated by 'devtool
> upgrade'.
> +# The following is the difference between the old and the new
> license text.
> +# Please update the LICENSE value if needed, and summarize the
> changes in
> +# the commit message via 'License-Update:' tag.
> +# (example: 'License-Update: copyright years updated.')
> +#
> +# The changes:
> +#
> +# --- COPYING
> +# +++ COPYING
> +# @@ -1,7 +1,7 @@
> +#                      GNU GENERAL PUBLIC LICENSE
> +#                         Version 3, 29 June 2007
> +#  
> +# - Copyright (C) 2007 Free Software Foundation, Inc. <
> http://fsf.org/>
> +# + Copyright (C) 2007 Free Software Foundation, Inc. <
> https://fsf.org/>
> +#   Everyone is permitted to copy and distribute verbatim copies
> +#   of this license document, but changing it is not allowed.
> +#  
> +# @@ -645,7 +645,7 @@
> +#      GNU General Public License for more details.
> +#  
> +#      You should have received a copy of the GNU General Public
> License
> +# -    along with this program.  If not, see <
> http://www.gnu.org/licenses/>;.
> +# +    along with this program.  If not, see <
> https://www.gnu.org/licenses/>;.
> +#  
> +#  Also add information on how to contact you by electronic and
> paper mail.
> +#  
> +# @@ -664,11 +664,11 @@
> +#    You should also get your employer (if you work as a programmer)
> or school,
> +#  if any, to sign a "copyright disclaimer" for the program, if
> necessary.
> +#  For more information on this, and how to apply and follow the GNU
> GPL, see
> +# -<http://www.gnu.org/licenses/>;.
> +# +<https://www.gnu.org/licenses/>;.
> +#  
> +#    The GNU General Public License does not permit incorporating
> your program
> +#  into proprietary programs.  If your program is a subroutine
> library, you
> +#  may consider it more useful to permit linking proprietary
> applications with
> +#  the library.  If this is what you want to do, use the GNU Lesser
> General
> +#  Public License instead of this License.  But first, please read
> +# -<http://www.gnu.org/philosophy/why-not-lgpl.html>;.
> +# +<https://www.gnu.org/licenses/why-not-lgpl.html>;.
> +# --- COPYING.LESSER
> +# +++ COPYING.LESSER
> +# @@ -1,7 +1,7 @@
> +# -		   GNU LESSER GENERAL PUBLIC LICENSE
> +# +                   GNU LESSER GENERAL PUBLIC LICENSE
> +#                         Version 3, 29 June 2007
> +#  
> +# - Copyright (C) 2007 Free Software Foundation, Inc. <
> http://fsf.org/>
> +# + Copyright (C) 2007 Free Software Foundation, Inc. <
> https://fsf.org/>
> +#   Everyone is permitted to copy and distribute verbatim copies
> +#   of this license document, but changing it is not allowed.
> +#  
> +# @@ -10,7 +10,7 @@
> +#  the terms and conditions of version 3 of the GNU General Public
> +#  License, supplemented by the additional permissions listed below.
> +#  
> +# -  0. Additional Definitions. 
> +# +  0. Additional Definitions.
> +#  
> +#    As used herein, "this License" refers to version 3 of the GNU
> Lesser
> +#  General Public License, and the "GNU GPL" refers to version 3 of
> the GNU
> +# @@ -111,7 +111,7 @@
> +#         a copy of the Library already present on the user's
> computer
> +#         system, and (b) will operate properly with a modified
> version
> +#         of the Library that is interface-compatible with the
> Linked
> +# -       Version. 
> +# +       Version.
> +#  
> +#     e) Provide Installation Information, but only if you would
> otherwise
> +#     be required to provide such information under section 6 of the
> +# 
> +#

Could we fix the FIXME please? :)

Cheers,

Richard