New pcakages: rpi-libcamera:20230303 and rpi-libcamera-apps-1.1.2

[strec007]

Testing the changes

• I tested the changes in this PR: YES

New package

• This new package conforms to the package requirements: YES

Local build testing

• I built this PR locally for these architectures (if supported. mark crossbuilds):
  • aarch64

[strec007]

int conversion issue has been fixed in v.1.1.2, now all builds work.

This package depends on rpi-libcamera which has not been integrated yet (PR #42574). Is it OK to create a dependent pull request like this? Thank you.

[classabbyamp]

put everything in 1 pull request

[strec007]

put everything in 1 pull request

In that case, this is the one pull request containing all changes. Including those from PR #42579, which I close. Thank you.

[paper42]

These are the same sonames as what the libcamera package has, so this won't work correctly once #41263 is merged.

PLEASE NOTE: when multiple packages provide the same SONAME, the first one (order top->bottom) is preferred over the next ones.

[strec007]

OK, so what's the solution of this? The user should be able to choose if they want libcamera, or rpi-libcamera (on Raspberry Pi). I understand that I should add the conflicts variable specifying libcamera package but how can we avoid the conflict in common/shlibs?

[github-actions]

Pull Requests become stale 90 days after last activity and are closed 14 days after that. If this pull request is still relevant bump it or assign it.