software.opensource.org search not working for 15.4 ?
Hello, So, I wanted to check out the kernel version in OpenSuse Leap 15.4. I go to https://software.opensuse.org/ , select Leap 15.4, enter "kernel"... and it finds nothing. For 15.2 it works. I tried other searches (plasma, mc, python, bash) with 15.4 selected. Still nothing. Is this system now deprecated and if it is, what replaces it?.. -- Yours, Misha Ramendik Unless explicitly stated, all opinions in my mail are my own and do not reflect the views of any organization
Mikhail Ramendik composed on 2022-10-16 22:35 (UTC+0100):
So, I wanted to check out the kernel version in OpenSuse Leap 15.4. I go to https://software.opensuse.org/ , select Leap 15.4, enter "kernel"... and it finds nothing. For 15.2 it works.
It's been broken for Leap for over a year.
I tried other searches (plasma, mc, python, bash) with 15.4 selected. Still nothing.
Is this system now deprecated and if it is, what replaces it?..
Not officially deprecated, but nothing directly replaces it. No one who's tried has been able to come up with a fix. You can use opi if the version searched is of no import. You can visit http://download.opensuse.org/update/leap/15.4/sle/x86_64/ and see what versions are available from the Leap kernel's update channel. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 10/16/22 16:52, Felix Miata wrote:
Not officially deprecated, but nothing directly replaces it. No one who's tried has been able to come up with a fix. You can use opi if the version searched is of no import. You can visithttp://download.opensuse.org/update/leap/15.4/sle/x86_64/ and see what versions are available from the Leap kernel's update channel.
God I miss the old functional webpin that covered everything, distro, updates, all repos (including home) -- David C. Rankin, J.D.,P.E.
On Mon, Oct 17, 2022 at 7:38 AM David C. Rankin
On 10/16/22 16:52, Felix Miata wrote:
Not officially deprecated, but nothing directly replaces it. No one who's tried has been able to come up with a fix. You can use opi if the version searched is of no import. You can visithttp://download.opensuse.org/update/leap/15.4/sle/x86_64/ and see what versions are available from the Leap kernel's update channel.
God I miss the old functional webpin that covered everything, distro, updates, all repos (including home)
It's not just that the search doesn't show everything for all platforms. It is also that so many packages are built for only a subset of SUSE/openSUSE current releases. It cannot fathom how a build service does not try to build for current releases. I know that user repositories are perhaps different. I am referring to primary package repositories. I am guessing if the package is not in the list of critical/core packages, even though it is in perhaps the same repository as critical/core packages, it might not be built. I get the resources issue. I wonder how many packages have been branched by users only because they wanted it to be built for their platform? I know that I have done this. Is there a good description of the steps one should follow to branch a package, and then correctly notify the original maintainer that it can be built for a platform they don't have enabled? Preferable a description for doing this via the web interface to OBS? This should be at the level of the occasional OBS user. I would think that this information would result in quite a number of branched packages being merged back with the main package. Perhaps a link to this information on the web page of a branched package? Up where the 'Links to" information is.
-- David C. Rankin, J.D.,P.E.
-- Roger Oberholtzer
On 10/17/22 02:24, Roger Oberholtzer wrote:
Is there a good description of the steps one should follow to branch a package, and then correctly notify the original maintainer that it can be built for a platform they don't have enabled? Preferable a description for doing this via the web interface to OBS? This should be at the level of the occasional OBS user. I would think that this information would result in quite a number of branched packages being merged back with the main package. Perhaps a link to this information on the web page of a branched package? Up where the 'Links to" information is.
Unfortunately No, (or at least I haven't found one yet) I usually just login to my build service and search for the package I want to branch (this can be daunting because you will get multiple locations for any given package). I try and choose the primary repository that you would expect that package to come from and I branch from there. (there is just a button/link in the top-right menu that lets you "Branch Package") Once in your home build service, you can modify the package, add/remove patches, modify the .spec, etc... Build service has gotten really picky about making you document what you did in the change log (which is a good thing, but with no specific guide for datespec format, etc.. it can be frustrating). The nag-list is shown under the "RPM Lint" tab where the build results are listed on the right of the page. You can write comments about your changes as well. If I understand correctly, when you request a "merge" the original maintainer will be able to read the comments, so presumably if you added a build architecture, you should be able to communicate it that way. Now I screw up merges more times than they succeeded. How you have to stand on your left-foot while wiggling your right-ear to get the merge to go through is still a mystery to be. But, fear not, you will get an e-mail from one of the devs letting you know of the failed attempt. (those can be cryptic too) Ask here if you get stuck, Marcus or Andrei can usually figure out where the issue is. -- David C. Rankin, J.D.,P.E.
participants (4)
-
David C. Rankin -
Felix Miata -
Mikhail Ramendik -
Roger Oberholtzer