Finding correspondent debian packages in openSUSE

Hello, everyone. I’m a complete newbie to OpenSUSE and would like some help in finding some Debian alternative packages.

This is the string of packages I was sent to install:


sudo apt-get install -y build-essential libssl-dev zlib1g-dev libbz2-dev \
libreadline-dev libsqlite3-dev wget curl llvm libncurses5-dev libncursesw5-dev \ 
xz-utils tk-dev libffi-dev liblzma-dev python-openssl git

A rather silly tentative was to change apt-get to zypper, but most of them failed. Is there any way to get alternatives?

Hi and welcome to the Forum :slight_smile:
It a lot of cases, just changing dev to devel will work, but better to use zypper se to see the full development package name, or maybe a portion, eg zypper se ncurses. Some development packages don’t have the lib portion in the name either.

What is the package name, maybe what your after is already built as an rpm on the openSUSE Build Service, perhaps in a development repository?

Hi, thank you for your greetings and for your suggestion!

I’m still struggling to find the packages using zypper se, because while I found packages with similar names, I’m not sure if I have they’re equivalent to what I need.

My real problem is an error while trying to install pycurl for a work project. After some googling, I found out that I am missing some packages and in the project install instructions, they told me to install the packages that are listed below:

libssl-dev zlib1g-dev libbz2-dev libreadline-dev libsqlite3-dev llvm libncurses5-dev libncursesw5-dev xz-utils tk-dev libffi-dev liblzma-dev python-openssl

That’s why I’m looking for the correspondent alternatives to them for OpenSUSE. Any help would be appreciated!

Hi
The default python on Tumbleweed at present is 3.8, so just zypper in python38-pycurl ?


ls -la `which python3`
lrwxrwxrwx 1 root root 9 Feb 23 09:40 /usr/bin/python3 -> python3.8

zypper in python38-pycurl

xxx-dev in Debian is xxx-devel in openSUSE.
But openSUSE often uses xxx-devel instead of libxxxx-devel as Debian uses libxxx-dev.

libssl-dev is in openSUSE libopenssl-devel

openSUSE uses openssl for naming and this is named libopenssl-devel as in Debian…

For zlib:

zypper se -s zlib
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...

S | Name                       | Type       | Version            | Arch   | Repository
--+----------------------------+------------+--------------------+--------+-------------------------------------------------------------
  | gambas3-gb-compress-bzlib2 | Paket      | 3.14.3-bp153.1.25  | x86_64 | Main Repository
  | gambas3-gb-compress-zlib   | Paket      | 3.14.3-bp153.1.25  | x86_64 | Main Repository
  | ghc-zlib                   | Paket      | 0.6.2.1-bp153.1.20 | x86_64 | Main Repository
  | ghc-zlib-devel             | Paket      | 0.6.2.1-bp153.1.20 | x86_64 | Main Repository
  | jzlib                      | Paket      | 1.1.3-9.63         | noarch | Main Repository
  | jzlib-demo                 | Paket      | 1.1.3-9.63         | noarch | Main Repository
  | jzlib-javadoc              | Paket      | 1.1.3-9.63         | noarch | Main Repository
  | lua51-zlib                 | Paket      | 1.1-bp153.1.16     | x86_64 | Main Repository
  | lua53-zlib                 | Paket      | 1.1-bp153.1.16     | x86_64 | Main Repository
  | lzlib-devel                | Paket      | 1.10-bp153.1.15    | x86_64 | Main Repository
  | mingw64-zlib-debug         | Paket      | 1.2.11-bp153.1.81  | noarch | Main Repository
  | mingw64-zlib-devel         | Paket      | 1.2.11-bp153.1.81  | noarch | Main Repository
  | mingw64-zlib1              | Paket      | 1.2.11-bp153.1.81  | noarch | Main Repository
  | php7-zlib                  | Paket      | 7.4.6-3.32.1       | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
  | php7-zlib                  | Paket      | 7.4.6-3.29.1       | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
  | php7-zlib                  | Paket      | 7.4.6-3.22.1       | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
  | php7-zlib                  | Paket      | 7.4.6-3.17.1       | x86_64 | Main Repository
  | zlib                       | Quellpaket | 1.2.11-3.24.1      | noarch | Update repository with updates from SUSE Linux Enterprise 15
i | zlib-devel                 | Paket      | 1.2.11-3.24.1      | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
v | zlib-devel                 | Paket      | 1.2.11-3.21.1      | x86_64 | Main Repository
  | zlib-devel-32bit           | Paket      | 1.2.11-3.24.1      | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
  | zlib-devel-32bit           | Paket      | 1.2.11-3.21.1      | x86_64 | Main Repository
  | zlib-devel-static          | Paket      | 1.2.11-3.24.1      | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
  | zlib-devel-static          | Paket      | 1.2.11-3.21.1      | x86_64 | Main Repository
  | zlib-devel-static-32bit    | Paket      | 1.2.11-3.24.1      | x86_64 | Update repository with updates from SUSE Linux Enterprise 15
  | zlib-devel-static-32bit    | Paket      | 1.2.11-3.21.1      | x86_64 | Main Repository
  | zlibrary-data              | Paket      | 0.99.4-bp153.1.16  | noarch | Main Repository
  | zlibrary-devel             | Paket      | 0.99.4-bp153.1.16  | x86_64 | Main Repository
  | zlibrary0_99               | Paket      | 0.99.4-bp153.1.16  | x86_64 | Main Repository

Its often not trivial…

For build-essentials equivalent search patterns-devel-c-c++…

Thank you all for the continued support! I’m learning a lot and growing to love this Distro. I was able to make some progress and while I still haven’t gotten where I wanted, at least I’m getting a different error :stuck_out_tongue:

Should I make a new post with my new-found errors, or is this a good place to continue?

What does the S column and its letters mean?

The S column means “status”. You can check it in the zypper’s man page:

**Query Commands**
       **search **(**se**) [options] [querystring|capability]... 
           Search for packages matching any of the given search strings. *** **and **? **wildcard characters can be used within search strings. If the search string is enclosed in **/  **(e.g. **/^k.*e$/**) it’s interpreted as a regularexpression. See the **install **command 
           for details about how to specify a capability. 

           Results of the search are printed in a table with columns **S**tatus, **Name**, **Summary **and **Type **of package. 

           In the detailed view (**se -s**) all available instances of matching packages are shown; each version in each repository on a separate line, with columns **S**tatus, **Name**, **Type**, **Version**, **Arch**itecture and **Repository**. For installed packages **Repository**
           shows either a repository that provides exactly the installed version of the package, or, if the exact version is not provided by any known repo, **(System Packages) **(or **@System**). Those installed packages not provided by any repo are often denoted 
           as being unwanted, orphaned or dropped. 

           The **S**tatus column can contain the following values: 

               **i+**
                   installed by user request 

               **i**
                   installed automatically (by the resolver, see section **Automatically installed packages**) 

               **v**
                   a different version is installed 

               empty
                   neither of the above cases 

               **!**
                   a patch in **needed **state 

               .**l**
                   is shown in the 2nd column if the item is locked (see section **Package Locks Management**) 

               .**P**
                   is shown in the 2nd column if the item is part of a PTF (A program temporary fix which must be explicitly selected and will otherwise not be considered in dependency resolution). 

               .**R**
                   is shown in the 2nd column if the item has been retracted (see **patch **in section **Package Types**) 

           The **v **status is only shown if the version or the repository matters (see **--details **or **--repo**), and the installed instance differs from the one listed in version or repository.