meta-openembedded/meta-oe
Leon Anavi 374b784b22
exiftool: Upgrade 12.89 -> 13.42
Upgrade to release 13.42:

  - Added warning if tag arguments come before -csv= or -json= in
    a command
  - Added a new CanonModelID and RFLensType (thanks Norbert Wasser)
  - Added ability to read XML as a block from Sony MP4 videos
  - Added "EOS" to the R5 Mark II CanonModelID string
  - Decode ReEditData in Samsung trailer
  - Decode a couple more Sony rtmd tags from MP4 videos
  - Tolerate some types of trailer corruption as caused by Samsung
    Gallery
  - Restrict decoding of MetaImageSize to HEIC files only
  - Fixed issue writing Keys tags to Sony PMW-EX1R videos
  - Fixed behaviour of CSV/JSON import when specifying tags to import
    into an existing list, or when importing ValueConv values (ie.
    "TAG#"), or when specifying a group name of "All"

This work was sponsored by GOVCERT.LU.

Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-11-20 02:01:30 -08:00
..
classes meta-oe: image: optionally remove RAW image after sparse image creation 2025-09-15 09:55:16 -07:00
conf thrift: support reproducible builds 2025-11-19 21:20:52 -08:00
dynamic-layers rasdaemon: fix post-processing options 2025-11-20 02:01:29 -08:00
files static-passwd-meta-oe: add flatpak user 2025-04-19 14:36:07 -07:00
lib/oeqa/selftest/cases
licenses licenses: add licenses for ktx-software 2025-07-22 20:02:18 -07:00
recipes-benchmark iperf3: Upgrade 3.18 -> 3.20 2025-11-18 08:17:54 -08:00
recipes-bsp lmsensors: add UPSTREAM_CHECK_GITTAGREGEX 2025-11-12 09:38:59 -08:00
recipes-connectivity thrift: support reproducible builds 2025-11-19 21:20:52 -08:00
recipes-core packagegroup-meta-oe: Enable heaptrack on riscv64 2025-11-10 20:31:54 -08:00
recipes-crypto pkcs11-helper: upgrade 1.30.0 -> 1.31.0 2025-11-18 08:23:44 -08:00
recipes-dbs mariadb: skip failing test on musl 2025-11-19 12:01:14 -08:00
recipes-devtools exiftool: Upgrade 12.89 -> 13.42 2025-11-20 02:01:30 -08:00
recipes-extended libplist: fix ptest error 2025-11-19 22:00:55 -08:00
recipes-gnome pyxdg: update to latest revision 2025-11-08 09:08:02 -08:00
recipes-graphics graphviz: upgrade 14.0.2 -> 14.0.4 2025-11-18 08:23:43 -08:00
recipes-kernel libtracefs: support reproducible builds 2025-11-20 02:01:29 -08:00
recipes-multimedia audiofile: Fix build with clang++ 2025-11-14 07:36:56 -08:00
recipes-navigation proj: upgrade 9.6.2 -> 9.7.0 2025-11-18 08:17:55 -08:00
recipes-networking/cyrus-sasl meta-openembedded/all: adapt to UNPACKDIR changes 2025-06-25 06:44:52 -07:00
recipes-printing cups-filters: upgrade 2.0.0 -> 2.0.1 2025-10-12 22:39:09 -07:00
recipes-security kernel-hardening-checker: upgrade 0.6.10.2 -> 0.6.17.1 2025-11-11 10:19:41 -08:00
recipes-shells dash: upgrade 0.5.13 -> 0.5.13.1 2025-10-21 20:02:39 -07:00
recipes-support c-periphery: upgrade 2.4.3 -> 2.5.0 2025-11-19 09:41:30 -08:00
recipes-test cunit: inherit sourceforge-releases class 2025-11-12 09:38:58 -08:00
COPYING.MIT
README.md README.md: Change maintainer from Andreas to Khem for gnome, multimedia, xfce 2025-09-19 12:21:59 -07:00
SECURITY.md

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