[SOLVED] Can't install nvidia-driver-libs:i386 in devuan freia

sysv_penguin · Yesterday 06:15:39

Hello guys. I'm here again and this time, apparently I can't install this library on my system.

This time https://pkginfo.devuan.org/ CAN actually find the package for devuan freia but my package manager says that its not available. I think it's not configured properly but I couldn't figure it out.

I only ran sudo dpkg --add-architecture i386 to add 32bit support. (Do I need to add anything to devuan.sources?)

This is the output of dpkg

~ $ dpkg --print-foreign-architectures 
i386

and apt

$ sudo apt install nvidia-driver-libs:i386
[sudo] password for mypc: 
Package nvidia-driver-libs:i386 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Error: Package 'nvidia-driver-libs:i386' has no installation candidate

and this is my devuan.sources:

~ $ cat /etc/apt/sources.list.d/devuan.sources 
## Devuan 7 freia
## The new style method of using repositories to install software.
## This /etc/apt/sources.list.d/devuan.sources is new style and location file
## The /etc/apt/old.style.sources.list contains the same as this.
## https://linuxconfig.org/ubuntus-repository-configuration-ubuntu-sources-have-moved-to-etc-apt-sources-list-d-ubuntu-sources

## Normal freia sources
Types: deb
URIs: http://deb.devuan.org/merged
Suites: freia 
#freia-backports freia-proposed-updates  freia-updates
Components: main non-free contrib non-free-firmware
Enabled: yes
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg
Architectures: amd64

## freia security sources
Types: deb
URIs: http://deb.devuan.org/merged
Suites: freia-security
Components: main non-free contrib non-free-firmware
Enabled: no
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg
Architectures: amd64

Last edited by sysv_penguin (Yesterday 08:50:18)

ralph.ronnquist · Yesterday 08:04:37

After modifying the architecture set, you must run

# apt-get update

so as to update your local meta-data database. And if you are working with freia you should relly make a habit of updating your local meta-data database every time before other apt commands.

sysv_penguin · Yesterday 09:01:16

I already have run sudo apt-get update. Unfortunately it still gives me the same error message.

~ $ sudo apt-get update 
Hit:1 https://nvidia.github.io/libnvidia-container/stable/deb/amd64  InRelease                                                                                                                                                        
Get:2 http://deb.devuan.org/merged freia InRelease [43.4 kB]                                                                    
Hit:3 https://dl.winehq.org/wine-builds/debian forky InRelease
Fetched 43.4 kB in 2s (25.2 kB/s)                         
Reading package lists... Done

~ $ sudo apt install nvidia-driver-libs:i386
Package nvidia-driver-libs:i386 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Error: Package 'nvidia-driver-libs:i386' has no installation candidate

Last edited by sysv_penguin (Yesterday 09:02:20)

ralph.ronnquist · Yesterday 09:27:13

https://pkginfo.devuan.org/cgi-bin/poli … 6&x=submit

As you may see, it's a non-free package.

rolfie · Yesterday 11:24:25

Well, the devuan.sources as shown in post #1 does only contain amd64 as architecture. There is no i386. While non-free is in there.

sysv_penguin · Yesterday 14:11:58

Thank you so much for replying.

As you may see, it's a non-free package.

Yes I have non-free repos enabled in my devuan.sources as shown in post #1. However the Architectures: entry is amd64 is this the issue?

Well, the devuan.sources as shown in post #1 does only contain amd64 as architecture. There is no i386. While non-free is in there.

So should I add the i386 architecture to devuan.sources?
Could you please elaborate how can I add it?

Do I need to add it like that?
Could you please check if this is ok:

## 32-bit freia sources
Types: deb
URIs: http://deb.devuan.org/merged
Suites: freia 
#freia-backports freia-proposed-updates  freia-updates
Components: main non-free contrib non-free-firmware
Enabled: yes
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg
Architectures: i386

rolfie · Yesterday 14:39:40

Make it look like this:

Architectures: amd64 i386

AFAIK that shoud work. I am wondering why your sudo dpkg --add-architecture i386 did not add that entry. Maybe dpkg can't deal with the deb822 sources?
Make a check:

# dpkg –print-foreign-architectures

ralph.ronnquist · Yesterday 14:46:11

Good catch.

Yes, there is a difference in declaring which architectures apt wants to use, and specifying which arcitecture(s) a particular source declaration is targeted for. In fact, you may remove the Architecture: ... restriction from the source point declaration, which would make it (them) applicable for all architectures that you may setup apt to want.

sysv_penguin · Yesterday 16:35:55

Thanks everyone , I removed the Architecture: ... line plus updated my system and finally the 32bit juice is started flowing. 😋

This is how devuan.sources looks like now:

## Devuan 7 freia
## The new style method of using repositories to install software.
## This /etc/apt/sources.list.d/devuan.sources is new style and location file
## The /etc/apt/old.style.sources.list contains the same as this.
## https://linuxconfig.org/ubuntus-repository-configuration-ubuntu-sources-have-moved-to-etc-apt-sources-list-d-ubuntu-sources

## Normal freia sources
Types: deb
URIs: http://deb.devuan.org/merged
Suites: freia 
#freia-backports freia-proposed-updates  freia-updates
Components: main non-free contrib non-free-firmware
Enabled: yes
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg

## freia security sources
Types: deb
URIs: http://deb.devuan.org/merged
Suites: freia-security
Components: main non-free contrib non-free-firmware
Enabled: no
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg

Maybe dpkg can't deal with the deb822 sources?

I was wondering the same. I've never seen anything like this in any debian-based system. adding 32-bit support is usually a one-liner. As you said, Probably dpkg can't deal with deb822 cause it's outdated or something.

Regards and have a nice day.

rolfie · Yesterday 16:46:10

Well you have used the simple way. Why haven't you extended the Architectures: line as proposed by me?

kapqa · Yesterday 18:50:55

hello , please forgive te hijack,

took the liberty to look up the sources.list ,

could you please tell me if this is ok for the laptop or if i should remove some of those lines (there seem to be 3 different distro involved)

# Modernized from /etc/apt/sources.list
Types: deb
URIs: http://deb.devuan.org/merged/
Suites: freia
Components: main  non-free-firmware non-free contrib
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg

# Modernized from /etc/apt/sources.list
Types: deb
URIs: http://deb.devuan.org/merged/
Suites: testing
Components: main  non-free-firmware non-free contrib
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg

# Modernized from /etc/apt/sources.list
Types: deb
URIs: http://deb.devuan.org/merged/
Suites: unstable
Components: main  non-free-firmware non-free contrib
Signed-By: /usr/share/keyrings/devuan-archive-keyring.gpg

thank you very much.

ralph.ronnquist · Today 04:43:36

Yes you should remove the stanzas for testing and unstable.
Possibly add one for ceres.

Suite freia is currently in "testing mode" and testing is merely a symbolic link in the remote repository to freia to indicate that. You don't declare testing as a package repository. There's a great big bag of confusion lingering in using it as source point even when it perhaps seems to work fine right now.

Suite ceres, which you don''t have a stanza for, is now and always in "unstable mode" and unstable is merely a symbolic link in the repository repository to ceres. You don't declare unstable as package repository. The lingering confusion bag is somewhat smaller, but still, don't.

Note that "unstable mode" means that there is no dust of promise that the collective of package versions work together. Perhaps often they do, and where it's discovered they don't, it called a bug and it causes a flurry of activities for the package developers attempting to deal with it.

The officially official Devuan Forum!

#1 Yesterday 06:15:39

[SOLVED] Can't install nvidia-driver-libs:i386 in devuan freia

#2 Yesterday 08:04:37

Re: [SOLVED] Can't install nvidia-driver-libs:i386 in devuan freia

#3 Yesterday 09:01:16

Re: [SOLVED] Can't install nvidia-driver-libs:i386 in devuan freia

#4 Yesterday 09:27:13

Re: [SOLVED] Can't install nvidia-driver-libs:i386 in devuan freia

#5 Yesterday 11:24:25

Re: [SOLVED] Can't install nvidia-driver-libs:i386 in devuan freia

#6 Yesterday 14:11:58

Re: [SOLVED] Can't install nvidia-driver-libs:i386 in devuan freia

#7 Yesterday 14:39:40

Re: [SOLVED] Can't install nvidia-driver-libs:i386 in devuan freia

#8 Yesterday 14:46:11

Re: [SOLVED] Can't install nvidia-driver-libs:i386 in devuan freia

#9 Yesterday 16:35:55

Re: [SOLVED] Can't install nvidia-driver-libs:i386 in devuan freia

#10 Yesterday 16:46:10

Re: [SOLVED] Can't install nvidia-driver-libs:i386 in devuan freia

#11 Yesterday 18:50:55

Re: [SOLVED] Can't install nvidia-driver-libs:i386 in devuan freia

#12 Today 04:43:36

Re: [SOLVED] Can't install nvidia-driver-libs:i386 in devuan freia

Board footer