flake-pilot-3.1.34-160000.1.1

- Bump version: 3.1.33 → 3.1.34

- Reverse showing progress logic
  So far the user had to pass %silent to the call to make
  the pilot stop showing progress information. The default
  behavior to show progress information caused a lot of
  confusion and breakage to script code calling an application
  as a flake. It is rather unexpected that such progress
  information is provided by default. This commit reverse the
  logic such that a user has to provide %progress to see
  the progress spinner while the pilot is working.
  This Fixes #80

- Update documentation

- Update documentation

- Fix typo in documentation

- Update documentation

- Add ECR container sources to appstore

- Bump version: 3.1.32 → 3.1.33

- Call tools from /usr/sbin with abspath
  Calling tools from /usr/sbin like mkfs.ext2 might not
  be found by the calling shell if the PATH does not contain
  /usr/sbin. Make sure to call these tools with an absolute
  path. Also make sure to cleanup a broken filesystem artifact
  when mkfs could not be called

- Update documentation
  Update examples and architecture diagram

- Bump version: 3.1.26 → 3.1.27

- Add support for --force option for remove
  Add support for podman remove --force mode. In this
  mode the referenced application will be force removed
  and no sanity checks if this is pointing to a flake
  registration will be done. Eventually missing files
  do not cause an error.

- Fix spec file
  Allow to build for Fedora, fix packager e-mail

- Bump version: 3.1.25 → 3.1.26

- Allow force registration with arbitrary data
  When using --force also register even if the eventually
  conflicting file does not belong to a flake registration

- Add --force option for register command
  Allow to force writing the registration even if a
  registration of the same name already exists. Also
  update the man pages.

- Bump version: 3.1.24 → 3.1.25

- Improve command debug log
  Make sure the command called is part of the log message
  and not only the arguments

- drop obsolete permission settings
  With the proper user vs. system wide setup there is no
  need for the hacky permission adaptions. This also
  improves the runtime performance

- Fixup flake lookup
  system wide first, then user specific

- Bump version: 3.1.21 → 3.1.22

- Fixes to use flakes as normal user
  Running a flake is a container based instance provisioning
  and startup. Some part of this process requires root permissions
  for example mounting the container instance store for the
  provisioning step. This commit fixes the required calls to
  be properly managed by sudo.

- Bump version: 3.1.20 → 3.1.21

- seed from entropy

- Fix assignment of random sequence number
  We should use a seed for the sequence as described in
  https://rust-random.github.io/book/guide-seeding.html#a-simple-number
  In addition the logic when a random sequence number should
  be used was wrong and needed a fix regarding resume and
  attach type flakes which must not use a random sequence

- Pass --init option for resume type flakes
  In resume mode a sleep command is used to keep the container
  open. However, without the --init option there is no signal
  handling available. This commit fixes it

- Revert "kill prior remove when using %remove flag"
  This reverts commit 06c7d4aa71f74865dfecba399fd08cc2fde2e1f2.
  no hard killing needed with the event loop entrypoint

- Fixed CVE-2025-55159 slab: incorrect bounds check
  Update to slab 0.4.11 to fix the mentioned CVE.
  This Fixes bsc#1248004

- Apply clippy fixes

- Create sequence number for the same invocation
  If a flake which is not a resume or attach flake is called twice
  with the same invocation arguments an error message is displayed
  to give this invocation a new name via the @NAME runtime option.
  This commit makes this more comfortable and automatically assigns
  a random sequence number for the call if no @NAME is given.

- Bump version: 3.1.18 → 3.1.19

- Fix CVE-2025-3416
  rebuild of the tool also inherits openssl in a version that
  fixes the above mentioned CVE. This fixes bsc#1242680

- Fix CVE-2025-5791
  Switch to uzers crate as actively maintained fork of the
  unmaintained users crate. This Fixes bsc#1244207

- Fix firecracker requirement
  Require firefracker only for TW as it exists in no
  other version of SUSE. In case the firecracker-pilot
  is installed on a system that has no firecracker it
  must be installed to this system in an alternative
  way which is easily possible because firefracker
  is also a rust application only depending on libc

- Bump version: 3.1.17 → 3.1.18

- Style fixes

- Fix error handling for container check methods
  The condition to setup permissions and redo the call
  was done when the exec of the call was not possible.
  But this is not the right place to check for a permission
  denied error. This commit fixes the evaluation of the
  error data

- Bump version: 3.1.16 → 3.1.17

- Don't use perform for bool status methods
  The perform() call checks the status code and raises an
  ExecutionError. This does not allow us to return a
  false boolean. Use output() call instead

- Bump version: 3.1.15 → 3.1.16