It is in the utilities development repository. This can be found when opening the link for the SLE installation instructions.
But next time better use a meaningfull thread title.
Qute from your github issue:
Should I try bugging the opensuse people about this…?
As this app is not in any official openSUSE repo, and the instructions on the github page come from the upstream devs, you need to bug the upstream devs. Their instructions are plain wrong. Nothing what any openSUSE folks could do about this.
Additionally the upstream devs decided to use a no longer maintained libpcre versions which got intentiomally removed from TW as it is insecure and outdated. So again you have to bug the upstream devs.
I mean, I woulda thought it’d be the kind of thing that would just be in the default repos already…
– ah, I just saw the bit you added about the libpcre versions it requires being outdated,
so I guess that would explain why I don’t remember having this problem the last time I did a OSTW setup a while ago…
Anyway, weird that the repos that provide the_silver_searcher apparently don’t also provide its required dependency libpcre1
(although they are “experimental”)
So I reported that to them
and
https://build.opensuse.org/package/show/utilities/the_silver_searcher#comment-2310741
- The ALP project has nothing to do with anything in this thread or the named package. Wrong recipient.
- As you can see in the OBS link, the package fails to build as libpcre is no longer available. That means, the upstream devs need to hurry up and work on the issue which is open since one year to move to libpcre2. libpcre2 got already released in 2015.
https://software.opensuse.org/package/the_silver_searcher?search_term=the_silver_searcher
it’s one of the 2 repos that provides the_silver_searcher to TW?
(and I think I had the same problem with both repos, if I’m remembering right…)
It is even worse. The upstream devs seem to ignore the requests to update the libpcre version, as there is an even older issue from 2024.
And in this issue you can also find the eplanation why this package got removed from Tumbleweed.
The_silver_searcher appears to be no longer actively developed or maintained upstream. The last code change/activity was in June 2020 and the last release from 2018. So the removal from Tumbleweed was well deserved.
huh, I just checked my tuxedo_os (ubuntu/debian) install, and:
$ apt-cache show silversearcher-ag
#=>
Package: silversearcher-ag
Architecture: amd64
Version: 2.2.0+git20200805-1.1
Priority: extra
Section: universe/utils
Origin: Ubuntu
Maintainer: Hajime Mizuno <mizuno-as@ubuntu.com>
Bugs: https://bugs.launchpad.net/ubuntu/+filebug
Installed-Size: 127
Depends: libc6 (>= 2.38), liblzma5 (>= 5.1.1alpha+20120614), libpcre2-8-0 (>= 10.22), zlib1g (>= 1:1.1.4)
Conflicts: python-ase (<< 3.8.1.3440)
Filename: pool/universe/s/silversearcher-ag/silversearcher-ag_2.2.0+git20200805-1.1_amd64.deb
Size: 42272
MD5sum: 6e8ee36fb391852ae7bad5debfd3a830
SHA1: 138a837e7b0d667e3a9712cf497a6e05c10ac448
SHA256: 2d779c13b7e19739dc028c88d3dc171565a4363be001fe95da151a59e92d03b6
SHA512: 8273f33143eeda20d29f76c19bff19a5d168792110118dbdc8e13a60bfacfbe9af206c9d06514410c95bc0f01451871b2d37ec5bb8f0e4b853ac192644e46d2c
Homepage: https://github.com/ggreer/the_silver_searcher
Description-en: very fast grep-like program, alternative to ack-grep
The Silver Searcher is grep-like program implemented by C.
An attempt to make something better than ack-grep.
.
It searches pattern about 3–5x faster than ack-grep.
It ignores file patterns from your .gitignore and .hgignore.
Description-md5: 41b379bfb630fb331cd51e1eec3f2e96
“Depends: […] libpcre2-8-0 (>= 10.22)”…
I guess they just… have a patched version?
Yes they patched the dead and unmaintained the_silver_searcher source code. The openSUSE devs decided against it and removed the package from TW instead.
@dwawlyn https://github.com/ggreer/the_silver_searcher/pull/1562
So many pulls waiting and issues…
… now I’m confused: why has nobody forked it yet?
Actually, given the version I have from the ubuntu repos on tuxedo_os…
is that technically a fork, or “just a patch”?
What would be the difference in this case…?
If you have a look at the github page…there were 1400! forks of this package. Only 22 of them had any code activity…this 22 barely “active” forks do also have no permanent and active maintainers. Some use AI as there is no other contributor and so on…
Ubuntu uses the unmaintained source and applied a patch to use pcre2 instead of pcre.
Ah, I see, thanks for explaining that.
Well, I just needed ag cuz I have a bunch of personal utility shell aliases that use it (fishshell functions)
and I can’t even remember where and why…
But after looking more carefully just now,
I just noticed that I wrote one of my aliases
(the most “upstream” one (I think, I hope))
to fall back on grep if which ag returned false,
but I just tweaked that to fall back on ack first instead…
And yeah, I tested some of my fishshell functions just now,
and the syntax seems to work as a drop-in replacement for at least the ones I know I use all the time,
at least the way I use them…
… also man, kinda off-topic, but I gotta say:
I just really like zypper!
– like, debugging the dependencies when I was trying to get ag installed and working felt annoying and confusing
(especiaily since I haven’t done anything in this context for ages)
but even so, using zypper just felt so NICE!
(
like, as opposed to the mess of apt, apt-get, apt-cache, and sometimes dpkg
– both choosing between them, and the way you interact with them individually
)
zypper just feels so well-designed, coherent and consistent, for user-friendly just-start-using-it-and-learn-as-you-go-ness…
That project is dead: Last code change 6 years ago.
And next time please don’t just post an URL, write some description what it’s all about.
Sorry, I was very tired and pushing myself to get stuff done before I crashed,
and I kinda expected it to do that automatic summary box thing that discourse forums do sometimes? (now I’m bit confused when it does and doesn’t do that…)