It’s been a “learning experience” getting a few distros installed to my new home built machine . . . . Ran the install of Leap 15.6 last week and the machine could not boot it, even though it was showing as an option in grub. Finally with the help of @karlmistelberger the solution to “disable secure boot in the mobo” was suggested, and voila . . . grub menu back to work.
So, today I booted to Leap 15.6, which I had wanted to be 16, checked “Main repo” and disabled all the others, ran zypper and that pulled in 2218 packages to upgrade. That went through fine.
I didn’t add Packman in 15.6, because I thought it would be easy to add it after the upgrade to 16. However, when I tried to add it in YaSt repositories, as I have done numerous times, today that brought an error: “Adding repository Packman Repository failed”??? I tried to twice to see if it would change its mind. It did not.
Any way to get YaSt to add Packman in the new install of 15.6, upgraded via editing the Main repo to “16”???
> sudo zypper repos
Repository priorities are without effect. All enabled repositories share the same priority.
# | Alias | Name | Enabled | GPG Check | Refresh
--+-----------------------------+----------------+---------+-----------+--------
1 | openSUSE-Leap-15.6-1 | openSUSE-Lea-> | No | ---- | ----
2 | openSUSE:repo-non-oss | repo-non-oss-> | No | ---- | ----
3 | openSUSE:repo-non-oss-debug | repo-non-oss-> | No | ---- | ----
4 | openSUSE:repo-openh264 | repo-openh26-> | Yes | ( p) Yes | Yes
5 | openSUSE:repo-oss | repo-oss (16-> | Yes | ( p) Yes | Yes
6 | openSUSE:repo-oss-debug | repo-oss-deb-> | No | ---- | ----
7 | openSUSE:repo-oss-source | repo-oss-sou-> | No | ---- | ----
Understood. But I have Packman installed on my older Mac Pro running 16, that was previously 15.6 . . . and that Packman is “15_6” . . . .
I think I unchecked it when I edited the Main repo, as now I just have two repos enabled on that install, the Main & Packman. The hope was I could make the same move, but I didn’t know Packman couldn’t get freshly added, only “re-enabled”??
You can add the Packman repo from Leap 15.6 repo to Leap 16. But it is use- and senseless, as you can’t perform the vendor switch. It is simply a question of missing and changed dependencies. The packages in the Leap 15.6 Packman repo are built for Leap 15.6 and can’t be used on Leap 16.
If you try to install the Leap 15.6 Packman packages on Leap 16, it will remove several hundreds of main packages and your system is broken.
You need to wait until Leap 16 is released. Then the packman repo will provide packages for it.
OK, thanks for the details on it. It’s not a show-stopper at this point. But, as mentioned, on my Mac Pro I was able to upgrade to 16 and “make the vendor switch” from 16 . . . and video is working, etc.
I guess that is because it was already installed??? Anyway, the arrow has been loosed, 16 is flying . . . Packman is not.
OK, well, end user . . . I like using the newest stuff that will run . . . it’s “Leap” but it’s “Beta . . . man . . . .”
I have run “alpha” and “beta” in Leap for a number of past iterations, largely even alpha runs well . . . nothing else to know about it. 16 seems to have had some “alpha” issues . . . so I delayed going to it until it went Beta. For a daily driver, being able to check some videos is key point . . . to achieve.
Here are the repos in my upgraded from 15.6 to 16 by editing the repos on my '12 Mac Pro . . . which in YaSt it shows the Packman repo as “15_6”??? But, in the console “zypper repo” it shows as “16”??
> sudo zypper repos
[sudo] password for root:
Repository priorities in effect: (See 'zypper lr -P' for details)
30 (raised priority) : 1 repository
99 (default priority) : 1 repository
# | Alias | Name | Enabled | GPG Check | Refresh
---+--------------------------------------------------+----------------------------------------------------------------------+---------+-----------+--------
1 | ftp.gwdg.de-openSUSE_Leap_16.0 | Packman Repository | Yes | ( p) Yes | Yes
2 | repo-backports-debug-update | Update repository of openSUSE Backports (Debug) | No | ---- | ----
3 | repo-backports-update | Update repository of openSUSE Backports | No | ---- | ----
4 | repo-non-oss | Non-OSS Repository | No | ---- | ----
5 | repo-oss | Main Repository | Yes | ( p) Yes | Yes
6 | repo-sle-debug-update | Update repository with updates from SUSE Linux Enterprise 15 (Debug) | No | ---- | ----
7 | repo-sle-update | Update repository with updates from SUSE Linux Enterprise 15 | No | ---- | ----
8 | repo-update | Main Update Repository | No | ---- | ----
9 | repo-update-non-oss | Update Repository (Non-Oss) | No | ---- | ----
10 | repositoriesKernel:stable:Backportstandardx86_64 | repositories/Kernel:/stable:/Backport/standard/x86_64/ | No | ---- | ----
You should already know that a repo list without URLs is useless. Always use following command to show your repo list: zypper lr -d
And having repo does not mean anything until you have installed packages from it. To find out which packages are installed from the Packman repo, use zypper se -r 1 -si
This installation seems quite broken, as you now have outdated Mesa versions. And by installing ffmpeg from Packman, other dependencies are also broken and outdated.
Much like myself . . . a broken man who somehow manages to carry on with it . . . .
Not sure what to say, Leap 16 boots and runs fine, videos can be watched . . . . The dmesg data on boot shows all “OK” . . . no errors, etc.
I don’t know enough to know if your requested command is correct in syntax, and I have “no system release version” or, there needs to be another item in the command?
sudo cat /etc/release
[sudo] password for root:
cat: /etc/release: No such file or directory
Like others have said, all results reported here are invalid. Since you 1 installed a 3rd party repo, and 2 that being from a different version. Any bugreport ditto.
I don’t understand what you are talking about . . . “ALL results are invalid” ??? I simply posted the data that was requested by hui from a working edition of Leap 16 that has a working Packman repo. What “bug report”??
You added Packman for Leap 15.6 to your Leap 16-beta. Since that is an absolutely unsupported method, whatever you report about it has no value. Filing bug reports about the issues it causes, is just a useless waste of devs time.
@non_space Your not testing anything, your just using, which is out of scope since it’s a beta product… seems pointless to assist on an unsupported setup?
Is not everything in openSUSE being “tested” and any issues or bug reports filed are contributions to the product?
To be clear, the new machine, now running plain jane Leap 16 does NOT have Packman installed, because it errored out. So possibly that machine, if there is something problematic to mention, would receive proper attention from the forum?? There would be a “point” to it??
The older '12 Mac Pro had the Leap 15.6 Packman repo installed and has been upgraded to Leap 16 . . . the data (invalid) for that machine was provided here to show that (somehow) Packman can be persuaded to run in a 16 environment.
No help has been requested for the Mac Pro . . . because in using it, no problems have occurred in spite of hui’s asessment that “it is broken.” The request in this thread was to ask if there is a way to get Packman running in 16 . . . ??? Always interesting to see the responses.
@non_space no, there isn’t. I suggest you ask the Packman folks to see if/when they will add, it’s nothing to do with the openSUSE Project, they are a third party provider…