Dependency hell

New to Debian (Or Linux in general)? Ask your questions here!

Re: Dependency hell

Postby L_V » 2019-12-19 17:27

There is no generic rule to your multiple questions, but you should know how ubuntu/trusty has been introduced in your system.
If previous command did not report anything, I don't see real problems.
You can consider your "Dependency hell" issue as solved.
L_V
 
Posts: 1270
Joined: 2007-03-19 09:04

Re: Dependency hell

Postby silas2 » 2019-12-19 17:44

Thank you so much for your help. Wow, I didn't think I'd ever miss the Windows Registry!

Sorry to labour this point but I've become really unsure about adding new apps now, but would you roughly say: "never include a non-Debian listing in your sources list, but if its a well-known publisher advertising a Debian download you would install"...?
silas2
 
Posts: 38
Joined: 2019-09-30 13:22

Re: Dependency hell

Postby L_V » 2019-12-19 17:48

I could roughly say this, but also insist on the "no generic rule".
L_V
 
Posts: 1270
Joined: 2007-03-19 09:04

Re: Dependency hell

Postby Head_on_a_Stick » 2019-12-19 18:00

L_V wrote:I don't see real problems

What about the long list of non-Debian packages?

The OP might be OK installing some things now but problems may crop up later. Upgrades between releases can be a particular issue with mixed package lists.
User avatar
Head_on_a_Stick
 
Posts: 11116
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Dependency hell

Postby silas2 » 2019-12-19 18:14

I can't quite get my head round this, if e.g. chrome or dbeaver is listed as a non-Debian package (and presumably all its dependencies) , whilst it came from a 'debian' download page won't there always be a large list of non-debian sourced apps?
silas2
 
Posts: 38
Joined: 2019-09-30 13:22

Re: Dependency hell

Postby Head_on_a_Stick » 2019-12-19 18:24

Use
Code: Select all
apt policy $package

To see the origin of any given $package.

You certainly shouldn't have bits of the graphics stack from a non-Debian origin.
User avatar
Head_on_a_Stick
 
Posts: 11116
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Dependency hell

Postby L_V » 2019-12-19 18:28

Head_on_a_Stick wrote:What about the long list of non-Debian packages ?
Which 'long' list ?
silas2 wrote:won't there always be a large list of non-debian sourced apps?
Not able to answer such question as there is no generic rule for apps installed outside Debian repository
L_V
 
Posts: 1270
Joined: 2007-03-19 09:04

Re: Dependency hell

Postby Head_on_a_Stick » 2019-12-19 18:30

L_V wrote:
Head_on_a_Stick wrote:What about the long list of non-Debian packages ?
Which 'long' list ?

viewtopic.php?p=712466#p712466
User avatar
Head_on_a_Stick
 
Posts: 11116
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Dependency hell

Postby L_V » 2019-12-19 18:37

There is a mix of i386 and amd64 packages which needs not some clarification.
If i386 packages are not used, simply remove them.
APT is not complaining about this.

+ check if dbeaver-ce amd64 has been installed
Code: Select all
apt list dbeaver-ce
L_V
 
Posts: 1270
Joined: 2007-03-19 09:04

Re: Dependency hell

Postby silas2 » 2019-12-19 18:42

You certainly shouldn't have bits of the graphics stack from a non-Debian origin.

But i still don't understand if Chrome can be listed in the non-Debian packages and if that is acceptable then surely all bets are off on the other listed packaged/dependencies ?
E.g. graphic drivers, I didn't put any specific graphics drivers on so they must have come with another package and why not dbeaver/chrome then (or OTB)?
silas2
 
Posts: 38
Joined: 2019-09-30 13:22

Re: Dependency hell

Postby Head_on_a_Stick » 2019-12-19 18:52

L_V makes a good point about 32-bit packages, the graphics stuff looks like it's for wine. Check:
Code: Select all
apt policy wine32:i386

Can you remove that package?
User avatar
Head_on_a_Stick
 
Posts: 11116
Joined: 2014-06-01 17:46
Location: /dev/chair

Re: Dependency hell

Postby L_V » 2019-12-19 18:54

silas2 wrote:
Code: Select all
silas@debian:~$ sudo apt install -fs
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
To summarize, your initial "Dependency hell" issue has been already solved. I don't see any hell anywhere.
You just need some time to learn that a "non Debian" package is a package your will not find here:
https://www.debian.org/distrib/packages
L_V
 
Posts: 1270
Joined: 2007-03-19 09:04

Re: Dependency hell

Postby silas2 » 2019-12-19 18:55

Sure, I couldn't get the app to work anyway.
silas2
 
Posts: 38
Joined: 2019-09-30 13:22

Re: Dependency hell

Postby silas2 » 2019-12-20 16:54

Sorry, can i just ask one more time, but would it be better to install everything like chrome etc which doesn't come in packages.org in my home directory? (this is a desktop dev pc not server)
Especially taking on board Head_on_a_Stick's caution that the stack is compromised as soon as non-native packages turn up.
silas2
 
Posts: 38
Joined: 2019-09-30 13:22

Re: Dependency hell

Postby Head_on_a_Stick » 2019-12-20 17:07

silas2 wrote:Head_on_a_Stick's caution that the stack is compromised as soon as non-native packages turn up.

I didn't notice that they were 32-bit packages, have you tried removing wine32?
Don't Break Debian wrote:Debian Stable should not be combined with other releases. If you're trying to install software that isn't available in the current Debian Stable release, it's not a good idea to add repositories for other Debian releases. The problems might not happen right away, but the next time you install updates.

https://wiki.debian.org/DontBreakDebian ... nkenDebian
User avatar
Head_on_a_Stick
 
Posts: 11116
Joined: 2014-06-01 17:46
Location: /dev/chair

PreviousNext

Return to Beginners Questions

Who is online

Users browsing this forum: No registered users and 11 guests

fashionable