Please , can someone tell me if the pacman and mozilla repositories are now available for the new Leap 16 and in case, suggest me how to add them using either the new myrlin or cockpit ? Thanks.
It’s Packman, not pacman.
Packman:
Myrlyn----Extra----Repository----add----Community Repositories
Mozilla Repo:
https://download.opensuse.org/repositories/mozilla/16.0/
You can add this also there.
In principle yes, but the old Myrlyn version that was shipped with Leap 16.0 doesn’t have them yet; because the repos weren’t there yet on the server side. And with the new GitHub (instead of OBS) workflow, for a long time it wasn’t possible at all to submit any new versions to 16.0. Now it may be; I’ll try again in a few days.
Myrlyn-0.9.9 from one of the OBS home directories should work, though.
Newbie question:
Does it mean that an actual Leap 16.0 consists of a newer, working Myrlin?
Or will Leap 16.0 stay at it’s bad state - so better wait if 16.1 might be better?
Leap 16.0 is not “in a bad state”. As Stefan wrote, he was not able to update the Myrlyn version yet for Leap 16.0. This is due to the new Git workflow. The Myrlyn version in Leap 16.0 is fully operational, but lacks as example the predefined Community repos. But this is no problem, as they can be added in various other ways (adding the repo URL via Myrlyn manually or the usual zypper way).
The devel repo for Myrlyn provides the latest upstream version.
It is quite normal that fixed release distributions do not ship the latest package versions with the newest developements/features. For this, rolling release distributions exist.
I build a Repo only with myrlyn:
https://download.opensuse.org/repositories/home:/Sauerland:/myrlyn/16.0/
It’s a branch of system:packetmanager Repo.
On each openSUSE installation, each repo consists of a .repo file in /etc/zypp/repos.d/ that points to a mirror location for package management use, along with state data, such as type, whether enabled, and priority. Adding and removing repos consists of adding or removing .repo files. Tools such as myrlyn and zypper do so, but are not required to do so, if the repo itself provides a .repo file. Not all, but most optional repos, do so.
If you visit for example, download.opensuse.org/repositories/mozilla/16.0/ in your web browser, you will see a .repo file there named mozilla.repo. Downloading that file and placing it in /etc/zypp/repos.d/ is one method of adding that repo to your installation.
@mrmazda just use zypper?
zypper ar -gf https://download.opensuse.org/repositories/mozilla/16.0/mozilla.repo
Sure, when you know the precise URL required for a repo you seek.
But when you don’t, and instead search the mirrors for, and find, your repo of interest, it’s a simple file save from browser, or DND to your downloader - optional actions which don’t require a visit to man zypper or history to rediscover the required options to zypper ar.
This procedure can work for those with multiple computers too. Save once on one, then copy from there to each other having need. ![]()
Hm, when you browse the mirror with a browser…you have the URL for the repo in the URL bar ![]()
If you opened the .repo file in the browser, otherwise elsewhere.
I’m not always saving to the installation though. I often save to one computer for sharing with others on the LAN by copying, after renaming it to begin with a capital letter, to distinguish it from repos I didn’t put in /etc/zypp/repos.d/. ![]()
You can install the “repo” file, see malcolm’s post…
Nope. It’s quite some repo basics. No need to open the repo file.
But yeah. There are countless ways how to add a repo. The only impartant thing is that you know at least one way and a backup solution.
I see nothing there ending in .repo.
As there is no repo file needed to add a repo. If you add the URL via zypper or Myrlyn, the repo file gets created on your system.
You can easily test this yourself. Add a repo with an arbitrary name like “banana” via zypper. Inspect /etc/zypp/repos.d/ afterwards and you will find the newly created banana.repo file.
sudo zypper ar -gf https://download.opensuse.org/tumbleweed/repo/oss/ banana
It works in both ways. Add a repo file like you are used to do on your boxes. Or let zypper create them when adding a URL via Myrlyn/YaST/zypper.
That is because zypper knows different ways how to add a repo (which create the same result at the end).
addrepo (ar) [options] FILE.repo
addrepo (ar) [options] URI alias
@malcomlewis
thanks a lot, that was what I needed, all the rest of the discussion is like hieroglyphics for a simple user like me, could you be so kind to also tell me the command to add the packman repository so that I can load the codecs.?
sudo zypper addrepo -cfp 90 'https://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_$releasever/Essentials/' packman-essentials
@harlequin well the real question should be what codecs are needed, many are now in the distribution so should work OTB. Likewise what applications are you running that need codecs… I don’t use Packman, but I do use flatpaks like VLC as this is all bundled… and less chance of issues when things get out of date…
As Malcolm mentioned, using Flatpaks seem to be encouraged for desktop apps outside the standard RPM ecosystem. It really depends on your exact preferences or requirements.
For those that do use Flatpaks, Flatseal is recommended as a GUI permissions manager for Flatpaks software:
…and it can be user-iinstalled as a Flatpak itself:
flatpak --user install flathub com.github.tchx84.Flatseal
For the Packman route, best to stay with using “Packman Essentials” only (providing multimedia libraries/codecs and ffpmpeg, working Firefox / Chromium video, KDE / GNOME multimedia support). Add it with…
sudo zypper ar -cfp 90 https://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Leap_16.0/Essentials/ packman-essentials
Switch codec-related packages…
sudo zypper dup --from packman-essentials --allow-vendor-change
This can be used to install a minimal set of codecs + ffmpeg (multimedia backend and CLI utility)…
sudo zypper in ffmpeg libavcodec* gstreamer-plugins-*
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
