agama/service
Josef Reidinger e9b4908a72
allow minimal installed system without libzypp (#2512)
## Problem

- follow-up to #2493
- https://trello.com/c/czY7e3c0

For SLES16 the minimal system can be without libzypp. If it is case
together with onlyRequires flag, then software service crashes when
trying to load zypp.conf.


## Solution

Add check if file exists and if not, just log it and continue.
Also change as agreed modification of zypp.conf to explicitly write
onlyRequires if user explicitly mention it in profile to not just use
libzypp default.


## Testing

- *Tested manually*


## Documentation

*Remember to look at it from the user's perspective. Yes you have made
the compiler happy.*
*But will the **humans** even know about your contribution? Sometimes
they cannot miss it,*
*other times they need advertisement and explanation.*

*Look for relevant sections and adjust:*
- The description parts of the [JSON schema][profile.schema.json]
- Is the CLI affected? See [cli.md][] for a complete overview,
  change the `///` comments (rust doc)
  and update the .md with `cargo xtask markdown`
- <https://agama-project.github.io/> ([source][gh.io])
- Run: `git ls-files '*.md'`

[cli.md]:
https://github.com/agama-project/agama-project.github.io/blob/main/docs/user/cli.md
[profile.schema.json]:
https://github.com/agama-project/agama/blob/master/rust/agama-lib/share/profile.schema.json
[gh.io]: https://github.com/agama-project/agama-project.github.io/

---------

Co-authored-by: Ladislav Slezák <lslezak@suse.com>
2025-06-26 14:00:41 +02:00
..
bin fix(ruby): disable AutoYaST XML validation in agama-autoyast 2025-02-10 16:39:13 +00:00
conf.d changes from review 2023-10-31 16:36:20 +01:00
etc adapt tests and in some case also prepare code 2023-10-26 21:53:22 +02:00
lib allow minimal installed system without libzypp (#2512) 2025-06-26 14:00:41 +02:00
package allow minimal installed system without libzypp (#2512) 2025-06-26 14:00:41 +02:00
po Update service PO files 2025-06-15 03:41:35 +00:00
share storage: fix tabs 2025-06-12 13:59:27 +01:00
test make test and rubocop happy 2025-06-24 14:19:22 +02:00
.editorconfig More D-Installer -> Agama renames 2023-04-18 17:56:43 +02:00
.gitignore rpm spec for the files independent of Ruby version 2024-11-05 17:28:36 +01:00
.rspec Add an RSpec configuration to simplify running tests 2022-04-22 16:48:00 +01:00
.rubocop.yml Add bootloader section to agama config (jsc#AGM-54) 2024-12-19 19:13:46 +01:00
agama-yast.gemspec chore: update spec files 2025-06-09 14:46:23 +01:00
agama-yast.spec.in chore: update spec files 2025-06-09 14:46:23 +01:00
Gemfile profile_itest: use a webrick http server 2025-05-22 10:00:09 +02:00
Gemfile.lock Merge branch 'master' into agama-config-generate 2025-06-10 11:38:16 +02:00
install.sh test/integration/profile_itest.rb: add agama autoyast 2025-04-01 13:23:37 +02:00
README.md docs: Fix broken links after moving content to web site 2024-12-02 16:07:05 -05:00
run_tests_in_container.sh Implement initial question to import certificate 2025-04-15 16:16:41 +02:00
TEXTDOMAIN Missing textdomain (#2415) 2025-05-28 16:32:43 +02:00

Agama YaST

According to Agama's architecture this project implements the following components:

  • The Agama YaST, the layer build on top of YaST functionality.

Testing Changes

The easiest way to test changes done to Ruby code on Agama live media is to build the gem with modified sources with gem build agama-yast. Then copy the resulting file to Agama live image. Then run this sequence of commands:

# ensure that only modified sources are installed
gem uninstall agama-yast
# install modified sources including proper binary names
gem install --no-doc --no-format-executable <path to gem>

If the changes modify the D-Bus part, then restart related D-Bus services.