On 22/12/2025 11:13, Antonio Terceiro wrote:
This is part of your problem. Partially-upgraded systems are not really
supported by Debian. Even though we *try* to specify versioned
dependencies that force the required upgrades, the number of different
configurations in a partially-upgraded system is infinite and it's
impossible to catch all cases.
Surely it should still be possible to accurately transcribe upstream
dependencies into the debian/control file?
You cannot remove ruby and still expect schleuder to work at all. :)
I was listing all the packages that apt thinks depend on ruby. I didn't
type "yes" and actually remove ruby, I'm not a *complete* idiot. :)
This is the other half of your problem. Debian packages do not ship
*.gem files; this means these were all installed manually and could
cause dependency problems.
You'll notice that these are cached gems; they were most likely created
by running `gem pristine` to fix the earlier issues. I have never
manually installed a gem on this machine.
I suggest you:
- remove all gems. you want to basically:
- remove /var/lib/gems/3.3.0/* (but not /var/lib/gems/3.3.0 itself)
- remove everything under the following directories that are not
installed by a Debian package:
- /usr/share/rubygems-integration
- /usr/lib/x86_64-linux-gnu/rubygems-integration
- /usr/lib/ruby/gems/3.3.0
Everything *not* installed by some debian package? That sounds painful.
Is there a tool for that?
- fully upgrade your system to Debian stable
With that done, schleuder should just work.
I'll try this in the new year, when I'll have time to deal with the
knock-on breakage.
Thanks again,
A
