Although there is a codeblocks package ready for installation
k.nick@dellnew:~> zypper search codeblocks
Loading repository data...
Reading installed packages...
S | Name | Summary | Type
---+----------------------------+-------------------------------------------------------------+-----------
| codeblocks | Open source, cross platform, free C++ IDE | package
| codeblocks | Open source, cross platform, free C++ IDE | srcpackage
| codeblocks-contrib | Code::Blocks contrib plugins | package
| codeblocks-devel | Code::Blocks SDK | package
trying to do so results in a broken dependency error
k.nick@dellnew:~> sudo zypper install codeblocks
[sudo] password for root:
Loading repository data...
Reading installed packages...
Resolving package dependencies...
Problem: 1: nothing provides 'libwx_baseu-suse-nostl.so.15.0.0()(64bit)' needed by the to be installed codeblocks-25.03-1.2.x86_64
Solution 1: do not install codeblocks-25.03-1.2.x86_64
Solution 2: break codeblocks-25.03-1.2.x86_64 by ignoring some of its dependencies
Choose from above solutions by number or cancel [1/2/c/d/?] (c):
I’d like to understand why this is happening. I mean, the person who builds and provides that package has volunteered to take care of the dependencies, right?
What is the point of providing a package that cannot be installed?
Probably more important, what would be the proper way to help to rectify this situation?
As codeblocks is not available in any official openSUSE Tumbleweed repository, the maintainer did not volunteer for anything. Packages from home and developement repositories are not guaranteed to work.
As you did not provide the information from which repo you try to install this package, one can only guess (code:blocks look like the devel project). Basic checks on OBS show that codeblocks from the devel project does not build atm. Additionally (as described above) this package is not part of factory and therefore does not undergo any QA process…only packages which are available in the official distribution repos, undergo QA.
I’m still confused, I mean the maintainer puts in some effort into providing the package just for that effort go to waste as the package is unusable… So why put in that effort in the first place?
As you did not provide the information from which repo you try to install this package,
How do I get that info (I’m new to tumbleweed and zypper…)?
Home projects are for personal entertainment/needs/hobbies/whatever.
Devel projects MAY be used for incorporation into the official distribution. But codeblocks was not submitted to factory and is therfore not part of any openSUSE distribution.
It is repo number #2
But yeah, the package does not build and is not part of the distribution. You may want to branch the package and fix the spec or contact the maintainers. The package spec contains a dependency which is no longer available in Tumbleweed due to deprecation and security issues.
What’s the point of such a strong complain? Distribution dependency was changed and the (previously worked) package stopped to build.
It happens from time to time. Thanks to @hui for submitting the fix.
just complains about unresolved dependencies. If I force it to install anyway it does so and a (obviously build) binary package gets placed on my ssd.
So seemingly there is someone going through the trouble configuring, building and providing a package that turns out to be useless.
Everyone is free to use (or waste) their time at their own discretion, I’m not here to judge that.
But I’m still wondering about what could be the motivation for such actions. What is the purpose of such a defunct package? What am I missing here?
It did not build until i provided a fix. The fix got accepted and now it installs fine again. When a package no longer builds, Tumbleweed still moves on and old dependencies get removed from Tumbleweed.
You should read:
The fixed package installs now just fine:
test@testbox:~> LANG=C sudo zypper in codeblocks
Refreshing service 'openSUSE'.
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following package is recommended, but will not be installed due to conflicts or dependency issues:
codeblocks-contrib
The following 2 NEW packages are going to be installed:
codeblocks libcodeblocks0
2 new packages to install.
Package download size: 8.9 MiB
Package install size change:
| 25.3 MiB required by packages that will be installed
25.3 MiB | - 0 B released by packages that will be removed
Backend: classic_rpmtrans
Continue? [y/n/v/...? shows all options] (y):
Retrieving: libcodeblocks0-25.03-2.3.x86_64 (code) (1/2), 2.2 MiB
Retrieving: libcodeblocks0-25.03-2.3.x86_64.rpm ............................................................................................................................................................................................................[done (1.5 MiB/s)]
Retrieving: codeblocks-25.03-2.3.x86_64 (code) (2/2), 6.7 MiB
Retrieving: codeblocks-25.03-2.3.x86_64.rpm ................................................................................................................................................................................................................[done (6.3 MiB/s)]
Checking for file conflicts: ...........................................................................................................................................................................................................................................[done]
(1/2) Installing: libcodeblocks0-25.03-2.3.x86_64 ......................................................................................................................................................................................................................[done]
(2/2) Installing: codeblocks-25.03-2.3.x86_64 ..........................................................................................................................................................................................................................[done]
%transfiletriggerin(man-2.13.0-3.1.x86_64) script output:
Running %transfiletriggerin(man-2.13.0-3.1.x86_64)
Running post-transaction scripts .......................................................................................................................................................................................................................................[done]
test@testbox:~>
