Sign Up
Log In
Log In
or
Sign Up
Places
All Projects
Status Monitor
Collapse sidebar
openSUSE:Leap:16.0:Staging:B
agama-auto
agama.obscpio
Overview
Repositories
Revisions
Requests
Users
Attributes
Meta
File agama.obscpio of Package agama-auto
07070100000000000081A400000000000000000000000166F076BC000046AC000000000000000000000000000000000000000E00000000agama/LICENSE GNU GENERAL PUBLIC LICENSE Version 2, June 1991 Copyright (C) 1989, 1991 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Lesser General Public License instead.) You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things. To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it. For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software. Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations. Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you". Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does. 1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee. 2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change. b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License. c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.) These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program. In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License. 3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following: a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.) The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code. 4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. 5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it. 6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License. 7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program. If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances. It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License. 8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License. 9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation. 10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. NO WARRANTY 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. END OF TERMS AND CONDITIONS How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. <one line to give the program's name and a brief idea of what it does.> Copyright (C) <year> <name of author> This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. Also add information on how to contact you by electronic and paper mail. If the program is interactive, make it output a short notice like this when it starts in an interactive mode: Gnomovision version 69, Copyright (C) year name of author Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items--whatever suits your program. You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names: Yoyodyne, Inc., hereby disclaims all copyright interest in the program `Gnomovision' (which makes passes at compilers) written by James Hacker. <signature of Ty Coon>, 1 April 1989 Ty Coon, President of Vice This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. 07070100000001000081A400000000000000000000000166F076BC0000222B000000000000000000000000000000000000001000000000agama/README.md# Auto-installation Support for Agama ## Two different approaches Agama offers two different approaches to unattended installation. On the one hand, the user can provide a file, known as a "profile", that includes a description of the system to install. This approach might sound familiar to AutoYaST users. On the other hand, Agama can accept just a plain shell script, enabling custom pre-installation workflows. Although Agama defines its own [profile format](../rust/agama-lib/share/profile.schema.json), it is able to partially handle AutoYaST profiles. Please, check the [AutoYaST support document](../doc/ autoyast.md) for further information. ## Profile-based installation A profile defines which options to use during installation: which product to install, localization settings, partitioning schema, etc. Although it sounds similar to AutoYaST, there are some essential differences: - Profiles are written in [Jsonnet](https://jsonnet.org/) instead of XML. Jsonnet is a superset of JSON (so you can use just plain JSON), which allows for writing more readable and concise profiles. - Dynamic profiles are achieved using Jsonnet itself instead of relying on _rules_ or _Embedded Ruby (ERB)_. Agama injects hardware information that can be processed using [Jsonnet standard library](https://jsonnet.org/ref/stdlib.html). You can check the [Tumbleweed installation profile](../rust/agama-lib/share/examples/profile_tw.json) included in the repository to get an impression of how a profile looks like. ### A simple example ```json { "l10n": { "languages": ["en_US.UTF-8"] }, "product": { "id": "Tumbleweed" }, "storage": { "bootDevice": "/dev/sda" }, "user": { "fullName": "Jane Doe", "password": "123456", "userName": "jane.doe" } } ``` ### Supported configuration values Check the [JSON Schema](../rust/agama-lib/share/profile.schema.json) to learn about the supported elements. ### Dynamic profiles The profile can be adapted at runtime depending on the system where the auto-installation is running. For such use cases, Agama injects the hardware information into the profile to be processed using Jsonnet. Please, check [the example profile](../rust/agama-lib/share/examples/profile.jsonnet) for further information. > [!NOTE] > You can inspect the available data by installing the `lshw` package and running the following > command: `lshw -json`. ### Validating and evaluating a profile Agama includes a handy command-line interface available in the `agama` package. Among many other things, it allows downloading, validating and evaluating profiles. For instance, we could check the result of the previous profile by running the following command: ``` $ sudo agama profile evaluate my-profile.jsonnet ``` > [!WARNING] You need to use `sudo` to access the hardware information. Do you want to check whether your profile is valid? `agama` have you covered. Bear in mind that you can only validate JSON profiles (a Jsonnet profile must be evaluated first). ``` $ agama profile validate my-profile.json ``` ### Generating a configuration file Writing the profile by hand is relatively easy. However, you might want to ask Agama to do it for you. You can boot the installation, use the web interface to tweak all the values and, from the terminal, generate the file by running the following command: ``` $ sudo agama config show > profile.json ``` ## Shell-based installation Instead of a profile, you can provide a shell script, having complete control of the process. In this scenario, it is expected to use the CLI to interact with Agama. In addition, you can rely on any other tool available in the installation media. What's more, when using the Live ISO, you could install your own tools. Below there is a minimal working example to install Tumbleweed: ```sh set -ex /usr/bin/agama profile import ftp://my.server/profile.json /usr/bin/agama install ``` You might want to have a look to [Agama's default script for inspiration](./scripts/auto.sh). Such a script comes into action when you provide a profile. ### Support for Custom Scripts The goal of this section is to document examples and use cases for additional scripting support in Agama auto-installation. #### Changes Before Installation ##### Hardware Activation In some cases it is necessary to activate tricky devices manually before starting the installation. An example is when you have two network cards, one for the external network and the other for the internal network. ```sh set -ex /usr/bin/agama download ftp://my.server/tricky_hardware_setup.sh > tricky_hardware_setup.sh sh tricky_hardware_setup.sh /usr/bin/agama profile import ftp://my.server/profile.json /usr/bin/agama install ``` ##### Modifying the Installation Profile Jsonnet may be unable to handle all of the profile changes that users wish to make. ``` set -ex /usr/bin/agama download ftp://my.server/profile.json > /root/profile.json # modify profile.json here /usr/bin/agama profile import file:///root/profile.json /usr/bin/agama install ``` #### After Partitioning Note: currently not supported (params to install is not implemented yet). ##### Partitioning Changes Sometimes there is a more complex partitioning that needs to be modified after partitioning done by Agama and before installing RPMs, such as changing the fstab and mount an extra partition. ```sh set -ex /usr/bin/agama profile import http://my.server/profile.json /usr/bin/agama install --until partitioning # install till the partitioning step # Place for specific changes to /dev /usr/bin/agama install # do the rest of the installation ``` #### After Deployment Note: not supported now (params to install is not implemented yet). ##### Setup Security If there is a need to modify the system before rebooting, e.g. to install mandatory security software for internal network, then it must be modified before umount. ```sh set -ex /usr/bin/agama download ftp://my.server/velociraptor.config /usr/bin/agama profile import http://my.server/profile.json /usr/bin/agama install --until deploy # do partitioning, rpm installation and configuration step # Example of enabling velociraptor zypper --root /mnt install velociraptor-client mkdir -p /mnt/etc/velociraptor cp velociraptor.config /mnt/etc/velociraptor/client.config systemctl --root /mnt enable velociraptor-client /usr/bin/agama install # do the rest of the installation - basically unmount and copy logs ``` ##### Tuning the Kernel Another scenario is when you need to make some changes required for a successful reboot, such as some kernel tuning or adding some remote storage that needs to be mounted during boot. ```sh set -ex /usr/bin/agama profile import http://my.server/profile.json /usr/bin/agama install --until deploy # do partitioning, rpm installation and configuration step # Do custom modification of /mnt including call to dracut /usr/bin/agama install # do the rest of the installation - basically unmount and copy logs ``` #### After Reboot Users usually do a lot of things with post installation scripts in AutoYaST e.g. calling zypper to install additional software, modify configuration files or manipulate with systemd services. This is done after the first reboot. If this is the case, Agama will simply delegate it to any other tool the user prefers for initial configuration, such as ignition/combustion. ## Starting the auto-installation The auto-installation is started by passing `agama.auto=<url>` on the kernel's command line. If you are using the Live media, you need to edit the Grub2 entry to add that option. Or you can use PXE if it fits better. For instance, `agama.auto=http://example.net/bedrock.jsonnet`. Using the correct extension in the file name is important: - `.jsonnet` enables dynamic content through Jsonnet. - `.json` assumes the profile is just a JSON file, so no dynamic content is expected. - `.xml`, `.erb` or a trailing slash (`/`) indicates that you want to import an AutoYaST profile. Check [autoyast.md](../doc/autoyast.doc) for further information. - `.sh` would be interpreted as a shell script. ## Caveats Auto-installation support is far from being complete, so you should have a few things into account: - Progress reporting through the command-line interface is limited, so you should watch the web interface, especially if the installation gets stuck. - If something goes wrong processing the profile, you will not notice because Agama does not report such problems yet. The only consequence is that the installation will not start. You can check the output of `journalctl -u agama-auto` for further information. - You need to manually reboot the system after installation. 07070100000002000041ED00000000000000000000000266F076BC00000000000000000000000000000000000000000000000A00000000agama/bin07070100000003000081ED00000000000000000000000166F076BC000001A9000000000000000000000000000000000000001500000000agama/bin/agama-auto#!/usr/bin/sh set -ex # Temporarily skip the AutoYaST XML validation export YAST_SKIP_XML_VALIDATION=1 if [ -z "$1" ] then url=$(awk -F 'agama.auto=' '{sub(/ .*$/, "", $2); print $2}' < /proc/cmdline) else url="$1" fi if [ -z "$url" ] then echo "no autoinstallation profile" exit 0 fi echo "Using the profile at $url" case "$url" in * ) /usr/bin/agama profile import "$url" /usr/bin/agama install;; esac 07070100000004000041ED00000000000000000000000266F076BC00000000000000000000000000000000000000000000000E00000000agama/package07070100000005000081A400000000000000000000000166F076BC00000329000000000000000000000000000000000000001700000000agama/package/_service<services> <service name="obs_scm" mode="manual"> <param name="url">https://github.com/openSUSE/agama.git</param> <param name="versionformat">@PARENT_TAG@+@TAG_OFFSET@</param> <param name="versionrewrite-pattern">v(.*)</param> <param name="scm">git</param> <param name="revision">master</param> <param name="subdir">autoinstallation</param> <param name="without-version">enable</param> <param name="extract">package/agama-auto.changes</param> <param name="extract">package/agama-auto.spec</param> </service> <service mode="buildtime" name="tar"> <param name="obsinfo">agama.obsinfo</param> <param name="filename">agama</param> </service> <service mode="buildtime" name="set_version"> <param name="basename">agama</param> </service> </services> 07070100000006000081A400000000000000000000000166F076BC00000649000000000000000000000000000000000000002100000000agama/package/agama-auto.changes------------------------------------------------------------------- Fri Sep 20 11:27:29 UTC 2024 - Imobach Gonzalez Sosa <igonzalezsosa@suse.com> - Change the license to GPL-2.0-or-later (gh#openSUSE/agama#1621). ------------------------------------------------------------------- Thu Aug 15 08:35:31 UTC 2024 - Josef Reidinger <jreidinger@suse.com> - change agama-auto systemd service depedencies to reflect changes in agama CLI communication and ensure that it runs when agama-auto runs (gh#openSUSE/agama#1539) ------------------------------------------------------------------- Wed Jul 3 15:24:48 UTC 2024 - Imobach Gonzalez Sosa <igonzalezsosa@suse.com> - Bring back the service scriptlets but using the right service name (gh#openSUSE/agama#1433). ------------------------------------------------------------------- Wed Jul 3 08:04:57 UTC 2024 - Imobach Gonzalez Sosa <igonzalezsosa@suse.com> - Add the %changelog section to the spec file (gh#openSUSE/agama#1431). ------------------------------------------------------------------- Wed Jul 3 07:14:39 UTC 2024 - Imobach Gonzalez Sosa <igonzalezsosa@suse.com> - Remove scriptlets section from the spec file (gh#openSUSE/agama#1430). ------------------------------------------------------------------- Thu Jun 27 13:58:17 UTC 2024 - Imobach Gonzalez Sosa <igonzalezsosa@suse.com> - Version 9 ------------------------------------------------------------------- Fri May 24 08:15:21 UTC 2024 - Imobach Gonzalez Sosa <igonzalezsosa@suse.com> - Initial package containing the agama-auto systemd service (gh#openSUSE/agama#1252). 07070100000007000081A400000000000000000000000166F076BC000006AF000000000000000000000000000000000000001E00000000agama/package/agama-auto.spec# # spec file for package agama-auto # # Copyright (c) 2024 SUSE LLC # # All modifications and additions to the file contributed by third parties # remain the property of their copyright owners, unless otherwise agreed # upon. The license for this file, and modifications and additions to the # file, is the same license as for the pristine package itself (unless the # license for the pristine package is not an Open Source License, in which # case the license is the MIT License). An "Open Source License" is a # license that conforms to the Open Source Definition (Version 1.9) # published by the Open Source Initiative. # Please submit bugfixes or comments via http://bugs.opensuse.org/ # Name: agama-auto # This will be set by osc services, that will run after this. Version: 0 Release: 0 Summary: Agama auto-installation service License: GPL-2.0-or-later Url: https://github.com/opensuse/agama Source0: agama.tar BuildArch: noarch Requires: agama-cli %description Agama is a service-based Linux installer. This package contains the auto-installation service. %prep %autosetup -a0 -n agama %install install -D -d -m 0755 %{buildroot}%{_bindir} install -m 0755 %{_builddir}/agama/bin/agama-auto %{buildroot}%{_bindir}/agama-auto install -D -m 0644 %{_builddir}/agama/systemd/agama-auto.service %{buildroot}%{_unitdir}/agama-auto.service %pre %service_add_pre agama-auto.service %post %service_add_post agama-auto.service %preun %service_del_preun agama-auto.service %postun %service_del_preun agama-auto.service %files %doc README.md %license LICENSE %{_bindir}/agama-auto %{_unitdir}/agama-auto.service %changelog 07070100000008000041ED00000000000000000000000266F076BC00000000000000000000000000000000000000000000000E00000000agama/systemd07070100000009000081A400000000000000000000000166F076BC00000198000000000000000000000000000000000000002100000000agama/systemd/agama-auto.service[Unit] Description=Agama automatic profile runner # it needs agama web service as it calls CLI which uses its API # other dependencies are transitive After=agama-web-server.service BindsTo=agama-web-server.service [Service] ExecStart=/usr/bin/agama-auto # it has to be simple and not one shot as install can take time and we need to # display web ui Type=simple User=root [Install] WantedBy=default.target 07070100000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000B00000000TRAILER!!!65 blocks
Locations
Projects
Search
Status Monitor
Help
OpenBuildService.org
Documentation
API Documentation
Code of Conduct
Contact
Support
@OBShq
Terms
openSUSE Build Service is sponsored by
The Open Build Service is an
openSUSE project
.
Sign Up
Log In
Places
Places
All Projects
Status Monitor
