Linux

5232 readers

123 users here now

A community for everything relating to the linux operating system

Also check out [email protected]

Original icon base courtesy of [email protected] and The GIMP

founded 1 year ago

MODERATORS

[email protected]

Predatory forcing of circular dependency? (programming.dev)

submitted 6 months ago* (last edited 6 months ago) by [email protected] to c/[email protected]

14 comments fedilink hide all child comments

I think ---DOCKER--- is doing this. I installed based, and userspace(7)-pilled liblxc and libvirt and then this asshole inserted a dependency when I tried to install from their Debian package with sudo dpkg -i. One of them was qemu-system, the other was docker-cli because they were forcing me to use Docker-Desktop, which I would not be caught dead using.

So is this accidental, or another predatory move by one of these 'ooh I wish I did not open source' companies (e.g. HashiCorp)? Why don't we all use LXC and ditch this piece of shit?

I could be misunderstanding how Debian-based packaging works. But this is too '''accidental'''. Correct me if I am wrong.

uname -a for context:

Linux pop-os 6.8.0-76060800daily20240311-generic #202403110203~1714077665~22.04~4c8e9a0 SMP PREEMPT_DYNAMIC Thu A x86_64 x86_64 x86_64 GNU/Linux

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 3 points 6 months ago (1 children)

Which version of Debian are you using?

What version was it before you did this update?

What action did you take that prompted this dependency?

[–] [email protected] 1 points 6 months ago (1 children)

I posted my uname -a, it's Pop_OS!, Debian-based but not Debian. My kernel is the latest version, I just did a fresh install and did a dist-upgrade (uname -r says 6.8.0-76060800daily20240311-generic).

Here's my entire command history since I installed this one a few days back (I got nuthing to hide!)

https://pastebin.com/biThVQME

So if you guys really think there's something fishy here, please do something!

[–] [email protected] 5 points 6 months ago (1 children)

Okay. Couple of things.

Pop_OS is not Debian and any issues should be raised with the maintainers of that distribution.
Doing a dist-upgrade is the only thing that can remove packages if a newer package has different dependencies.
I don't know why you did a dist-upgrade, but likely it was because some packages were held back, which was probably because they removed something.
You guys is you. If you want something to change, the first step is lodging and issue with the correct maintainers. If you were to lodge this issue in the Debian BTS, I'd be surprised if it survived 24 hours without being closed as being not related to Debian.
Your approach is unlikely to win you any sympathy or friends. For the most part, we're all volunteers here.

[–] [email protected] 1 points 6 months ago

I was mainly asking if this was even the case. If i go to the maintainers and say shit like this they b& me.