Setup yast repository

It allows the transfer of data to a disconnected RMT server, for example to provide updates to computers in an air-gapped network. Export the list of enabled repositories. The exported file is required for exporting the repositories in the next step. Export mirrored RPM packages. Depending on the size of mirrored repositories, this can take a long time.

Unmount and unplug the disk from sun and go to sirius. Import mirrored RPM packages. Enable repositories as required on the sirius. For details, see Section 3. If your air-gapped server sirius has many enabled repositories, or if the enabled repositories change frequently, we recommend to export the repository settings from this server.

This ensures that sun downloads all data required by sirius. Use this approach only if your setup benefits from it and only in a trusted environment where security is not crucial. Provide the required information with boot parameters. See Section 4. Configure the clients using an AutoYaST profile.

Use the rmt-client-setup command. Use the YaST registration module during installation or later. Any client can be configured to use RMT by providing the regurl parameter during machine boot. Make sure the values you enter are correct. If regurl has not been specified correctly, the registration of the update source will fail. YaST displays a dialog for importing a new certificate.

If you confirm importing the new certificate, the old one is replaced with the new one. In this section, only RMT specific configuration is described. From a command line, you can start the graphical AutoYaST front-end with the yast2 autoyast command.

An overview of the current configuration is shown. The possible values for the server URL are the same as for the kernel parameter regurl. Perform all other configuration needed for the systems to be deployed, then click Finish to return to the main screen. This script allows you to configure a client machine to use an RMT server.

It can also be used to reconfigure an existing client to use a different RMT server. To configure a client machine to use RMT with rmt-client-setup , follow these steps:. Alternatively, you can specify the correct fingerprint or path to the server certificate. For details, see sh rmt-client-setup --help.

The script downloads the server's CA certificate. Accept it by pressing Y. The tool now performs all necessary modifications on the client. On the client, the credentials are not necessary and you may leave the relevant fields empty. Then click Next until the exit from the module. If you created a custom stand-alone repository on the RMT server, it will not be registered on client machines with SUSEConnect because it has no parent product. Before starting the migration, make sure that RMT has the required products available and mirrored.

This chapter describes the most important scripts, configuration files and certificates shipped with RMT. The rmt-cli command and its sub-commands are used to manage the mirroring of repositories, registration of clients, and reporting. The rmt-cli command should be used together with the sub-commands described in this section. If the rmt-cli command is used alone, it prints a list of all available sub-commands.

To get help for individual sub-commands, use man rmt-cli or rmt-cli help [subcommand]. The command has no further options.

Synchronization is also triggered each night by the systemd timer rmt-server-sync. This command for example updates local product definitions and repository data. Lists the products that are enabled for mirroring. Use the --all flag to list all available products.

Use the --csv flag to output the list in CSV format. Enables mandatory repositories of a product by its ID or product string.

The --all-modules flag enables all modules of a product instead of only the recommended ones. Lists the repositories that are enabled for mirroring.

Use the --all flag to list all available repositories. This command removes locally mirrored files of repositories which are not marked to be mirrored. Lists all your custom repositories. Adds a new custom repository. Use the --id flag to specify a custom alphanumeric ID. This command removes a system from RMT as identified by the Login column of the output of the rmt-cli systems list command. This command is required for the offline mode. Run this on the offline RMT to save the settings for enabled repositories at a given path as repos.

Run this regularly on the online RMT to mirror the set of repositories specified in the repos. The mirrored repository files will be stored in subdirectories of the same path. You can manage RMT-related services with the standard systemd commands. The RMT server has the following services and timers:. This service migrates the database to the newest schema, if required. There is no need to manually interact with this service.

The only supported way of doing the initial configuration is with yast2 rmt as described in Section 1. Only the proxy configuration has to be entered manually.

The other configuration parameters are documented for reference. Decides whether to mirror source RPM packages architecture is src. Creates hard links during mirroring when set to hardlink.

If the file system does not support hard links, it can be set to copy instead. Possible values: hardlink , copy. This setting determines the proxy authentication mechanism. To obtain your mirroring credentials, see Section 3. YaST RMT module generates a custom certificate authority which is used to sign HTTPS certificates, which means that to register, this certificate authority must be trusted by the client machines:.

For registrations during installation from the media or with YaST Registration module, a message will appear, prompting to trust the server certificate. For registering a client system on the command line, use the rmt-client-setup script.

For details, see Section 4. This procedure details how to create a full backup of your RMT server. Create a file containing a dump of your SQL database. You need to provide the password you set for the rmt database user during the installation. This procedure details how to restore your RMT server from a backup created in Section 6. It is also assumed that you are restoring the server on a newly installed SLES.

Use mysql to remove the newly created database and import the data. HTTPS certificates should be regenerated before they expire or to include additional common alternative names. Run the yast rmt module as described in Section 1. This can be done by running the rmt-client-setup script on the client machines as described in Section 4.

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. The purpose of this License is to make a manual, textbook, or other functional and useful document "free" in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or non-commercially.

Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others. This License is a kind of "copyleft", which means that derivative works of the document must themselves be free in the same sense.

We have designed this License to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference.

This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you". You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law.

A "Secondary Section" is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject or to related matters and contains nothing that could fall directly within that overall subject. Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.

The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them. The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant.

The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none. The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document straightforwardly with generic text editors or for images composed of pixels generic paint programs or for drawings some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters.

A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text.

A copy that is not "Transparent" is called "Opaque". The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, "Title Page" means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text.

To "Preserve the Title" of such a section when you modify the Document means that it remains a section "Entitled XYZ" according to this definition.

Latex is pretty extensive. You'll need texlive plugins for matplot, maybe others Code:. So the installation of iminuit worked - thank you! And thanks for your detailed explanation. That was great, really. I already got all those other requirements including quite a lot of texlive which I think should be enough , I just needed iminuit to work. As for Qt4 I'm not sure though. Hope it's there. When trying to install kafe, this is what I get: Collecting kafe Could not find a version that satisfies the requirement kafe from versions: No matching distribution found for kafe.

But, if I were to hazard a wild guess, the requirements file that is supposed to automatically download dependencies may be just plain faulty, name packages found in other distributions or simply can't understand an openSUSE system. Someone would have to look at that in detail to know for sure. If your referenced page for kafe is correct and complete, it should provide enough info to get kafe installed.

But, documentation and what goes through the minds of Developers can sometimes be strange and parochial. For those situations, for instance if I see Ubuntu instructions listed first as in the kafe documentation or other OS, then I'll fire up a virtual machine and test whether one of the distros the Developers are clearly favoring works I've used kafe on openSuse before obviously not on my computer though which is why I expected it to work ; I have no idea who installed it there but maybe somehow I'll be able to find out and ask about it.

So far thank you so much for your help - this was way better than anything I expected and I feel like I've learned a lot in general, not just about my particular problem.

Re: YAST - add repository to be noted: kafe appears to be python 2 only package. Page 1 of 2 1 2 Last Jump to page:. Bookmarks Bookmarks Digg del. All times are GMT However, you may wish to add the correct display driver to allow desktop effects, or KDE to get the latest desktop environment.

Available here: Additional package repositories. Repositories may be added and removed, enabled or disabled, or their priority may be changed, to ensure software available from more than one repository is downloaded from the desired one. Details of adding and removing repositories is available from Add package repositories.