But ...
Have you searched for packages using *-devel?*
* maybe not enough Joe? 8^P

Guilty as charged my friend! No I haven't, I blithely try to pretend there's no redhat in my system and ignore anything that says otherwise.

hplip-3.25.8.run --debug

So much for, and I reiterate with more emphasis:

@deepforest If you're going to install software from outside the repos, on a distro that upstream doesn't even claim to support (note Debian being "present in supported distros" does not mean it will detect Devuan successfully), you get to keep all the pieces. Even if you get this to install, it will louse up your system with untracked files in unusual locations, just as the wiki warns.

We might be inclined to help, but if you want to do unsupported, not-recommended, oft-warned-against things to your system, you need to put in more effort than "Why do not want to install" - starting with at least a cursory investigation of how the installer works and gathering useful debug output.
This is not Windows, we do not run executable installers from manufacturer websites. Installing software from the stable repositories is "easy mode", running (or porting from) unstable, building from source, or using third-party scripts is "expert mode" and comes with the expectation that you are able and willing to put energy into solving your own problems.

Riiight, so, people not wanting to do your homework for you or run unknown install scripts for software they don't need is "lazy"... Guess I'll be "lazy" too then, good luck.

foo-devel is a RedHat thing, the script knows nothing about Devuan and it's a near-certainty that it's just misdetecting the distro... Which, again, had deepforest provided the output of hplip-install --debug we would know rather than have to take educated guesses at.

I mean, it took me all of about a minute to extract the install script and see it had a debug flag, surely Mr. "runs unstable and installs things from SourceForge" could have done that too

*Aside, if anyone is wondering why I'm not spoon-feeding the answer (besides just generally being a bastard OFC), it's right here in the attitude:

Same here.

But ...
Have you searched for packages using *-devel?*
* maybe not enough Joe? 8^P

My TimeShift snapshots stash say my system had these two years ago:

$ locate *-devel
/2024-03-09_07-37-32/localhost/usr/share/doc/libfontconfig1-dev/fontconfig-devel
/2024-03-09_07-37-32/localhost/usr/share/doc-base/fontconfig-devel
/2024-03-15_08-30-04/localhost/usr/share/doc/libfontconfig1-dev/fontconfig-devel
/2024-03-15_08-30-04/localhost/usr/share/doc-base/fontconfig-devel
/2024-05-23_08-50-02/localhost/usr/share/doc/libfontconfig1-dev/fontconfig-devel
/2024-05-23_08-50-02/localhost/usr/share/doc-base/fontconfig-devel
$ 

That said, my present Daedalus system has nothing with *-devel in the name.

A very quick look at the web (whatever that is these days) found that -dev is Debian/Ubuntu ware and -devel is RedHat/CentOS/Fedora ware. Take it with a few grains of low sodium salt.

Best,

A.

Also, most development packages in debian/devuan end in -dev, not -devel.

yeah that pegged my WTH meter too, I have a metric-ton of dev packages on my system and none end in ".devel".

Package-Name         Component            Required/Optional   
libtool              base                 REQUIRED            
cups-devel           base                 REQUIRED            
cups-image           base                 REQUIRED            
libusb               base                 REQUIRED            
python3-pyqt4-dbus   gui_qt4              OPTIONAL            
python3-pyqt4        gui_qt4              REQUIRED            
python3-devel        base                 REQUIRED            

The only package in that list that I could find in excalibur is libtool. Either they are looking for a specific version, or they don't know where to find libtool in a debian system. There is a libusb-0.1.4 and a libusb-1.0.0 in excalibur, but those either don't match the script's search pattern or they are the wrong version. Or again, maybe they don't know where to look. The others don't exist.

Also, most development packages in debian/devuan end in -dev, not -devel. There are a few libcups*-dev packages. Whoever wrote that script doesn't know that.

Why is it on sourceforge instead of some HP website?

No, I'm afraid you have not understood.

and i am afraid you not undestand my question,
"How install hplip-3.25.8?" or why installation brakes at dependencies stage?
if you cant answer stop offtopic

do not be lazy, run hplip script and you see that Debian is present in supported distros

No, I'm afraid you have not understood.

Maybe it is a language problem, the answers posted somehow lost in translation?
No idea.

The answer to your question is really quite simple:

If you want to know why the hplip-3.25.8 package you downloaded (which is not a *.deb file) will not "install at Devuan" you will have to ask the maintainers:

https://sourceforge.net/projects/hplip/ … ip/3.25.8/

To be able to do that you have to join the sourceforge.org mailing list:

https://sourceforge.net/projects/hplip/lists/hplip-help

Once you have joined, you can log-in:

https://sourceforge.net/auth/

And post the question:

https://sourceforge.net/p/hplip/mailman/hplip-help/

Your argument [... debian repos always have unfresh old software.] is quite clearly not a valid one.
The hplip package in the Devuan repositories works as intended and (for the moment) is the only one available for Devuan.

I hope I have cleared up your doubts.

Best,

A.

You might be happier on a distro like Artix because it's also systemd-free, XLibre, and built Arch.

Devuan is not going to change from it's stated purpose and goals to accommodate one user with unrealistic expectations.

HP site refers to this

Over and over again you ignore this advice, then when things inevitably break, you go and post a bunch of off-topic "Linux is buggy" comments in random threads.

If you must have the latest hplip from unofficial sources, either fix the installer or build it from source. The latter might be as easy as a 'uupdate' against the existing Debian/Devuan sources with a new upstream tarball. Whining about things not working when all the documentation warns you about exactly that achieves nothing.

"Why would anyone here know (or care) about some random executable "installer"?"

HP site refers to this, so its not "random"
https://sourceforge.net/projects/hplip/ … ip/3.25.8/

Why lasted hplip installation interrupts at dependencies stage? Devuan here already have most part of needed dependencies but hplip 3.25.8 do not recognize

Why would anyone here know (or care) about some random executable "installer"? As already stated (more than once) the packages in the repos work fine, and that's what people who don't want a broken system use.
If you really want to know, ask whoever provided that .run file - or extract it and look at whatever pre-install checks it's doing yourself, since it's probably just a bunch of shell concatenated with a compressed archive. My bet is that it's looking for Ubuntu package names or specific versions, but that's for you to determine if you insist on installing "fresh" software in weird formats.

A Debian based system is never going to give you that

My question in first post of this topic - Why lasted hplip installation interrupts at dependencies stage? Devuan here already have most part of needed dependencies but hplip 3.25.8 do not recognize it?