Gyorgy Sarvari 0934de7a60
exiftool: upgrade 13.48 -> 13.52
Also fixes CVE-2026-3102

Changelog:

13.52:
  - Added a number of new XMP tags written by Adobe software
  - Added UTF-16 support for a few different metadata types in which only UCS-2
    was previously implemented
  - Added a few more Canon FlashModel values and decode FlashModel for the
    5DmkII
  - Added a new Canon LensType
  - Added some missing file attribute bits to two of the new LNK tags
  - Decode internal serial number for the 5DmkII
  - Decode another OwnerName for the 5DmkII
  - Decode some timed GPS for a couple of new DJI drones
  - Enable WindowsLongPath by default only if Win32::API is available
  - Renamed the Pentax K3III AFInfo tag to AFInfoK3III

13.51:
  - Added a new Nikon LensID
  - Decode more tags from Windows LNK files
  - Decode another LIGOGPSINFO variant
  - Decode some new Canon tags
  - Decode some new Nikon tags
  - Split decoding on Nikon BurstGroupID into separate tags
  - Fixed round-off error in GPSDateTime seconds for camm6 metadata in MP4
    videos introduced in 13.45
  - Fixed bug generating the default-language version of
    QuickTime:LocationInformation

13.50:
  - Added a few new Sony lenses
  - Added a couple of new Canon lenses
  - Decode another Samsung trailer tag
  - Decode BlackLevels from some Canon CRW files
  - Updated Sony maker note decoding for the ILCE-7M5
  - Patched potential MacOS security issue
  - Fixed -list options so reading image files beforehand doesn't add tags to
    the output when running multiple commands using the -execute feature

13.49:
  - Decode a couple of new Samsung trailer tags
  - Disabled decoding of MenuSettings for the Nikon Z6III firmware 2.0 until the
    changes can be worked through in detail
  - Fixed problem where Google Photos had problems displaying ExifTool-edited
    HEIC MotionPhoto images.  Files written by older versions of ExifTool may be
    repaired by re-writing with 13.49 or later

Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2026-03-17 13:25:15 -07:00
..
2026-01-22 22:01:05 -08:00
2026-03-17 13:25:13 -07:00
2026-03-02 19:25:50 -08:00

meta-oe

This layer depends on:

URI: git://github.com/openembedded/openembedded-core.git branch: master

luajit recipe requires host compiler to be able to generate 32bit code when target is 32bit e.g. arm, so ensure that $CC -m32 is functional on build host, if building this recipe, needed packages to fullfit this might have different names on different host distributions e.g. on archlinux based distributions install prerequisites like below

pacman -S lib32-gcc-libs lib32-glibc

Ubuntu sudo apt-get install gcc-multilib linux-libc-dev:i386

Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe]' in the subject'

When sending single patches, please use something like: 'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix="meta-oe][PATCH"'

You are encouraged to fork the mirror on GitHub https://github.com/openembedded/meta-openembedded to share your patches, this is preferred for patch sets consisting of more than one patch.

Note, it is discouraged to send patches via GitHub pull request system. Such patches get less attention from developers and can be mishandled or not reviewed properly. Please use emails instead. For exemple, you can use 'git request-pull' to generate an email referencing your git repository.

Other services like GitLab, repo.or.cz or self-hosted setups are of course accepted as well, 'git fetch ' works the same on all of them. We recommend GitHub because it is free, easy to use, has been proven to be reliable and has a really good web GUI.

Layer maintainer: Khem Raj raj.khem@gmail.com