Jump to content

I've been messing about with a Debian installation to allow certain sid sources, such as the libs required for mesa 19.3.3. I added pinning in /etc/apt/preferences so it will only update certain libs instead of making every file on the system be from the unstable repo. It worked pretty well for the amd64 side of things, but the i386 libs don't seem to be using the sid repo. For example, I have this in the preferences:

Package: *
Pin: release a=stable
Pin-Priority: 1000

Package: *
Pin: release a=unstable
Pin-Priority: 2

Package: libdrm2
Pin: release a=unstable
Pin-Priority: 1001

This worked to make libdrm2 update to 2.4.100-4, though it doesn't make the i386 lib update, and it remains on 2.4.97-1. I already tried stuff like adding libdrm2* and libdrm2:i386, but it still doesn't seem to update. This happens with all i386 libs I've tested it on, they don't seem to be finding the newer sources from when I run apt update and apt upgrade, even though they're in the pin. Is there something else that needs to be added to the pin for i386?

 

This is what happens when I try tell libdrm2:i386 to upgrade because of it:

The following packages have unmet dependencies:
 libdrm2 : Breaks: libdrm2:i386 (!= 2.4.100-4) but 2.4.97-1 is to be installed
 libdrm2:i386 : Breaks: libdrm2 (!= 2.4.97-1) but 2.4.100-4 is to be installed
E: Broken packages

Since the i386 packages won't update, it breaks things, as the 32 and 64 bit libs aren't the same versions. Does anyone know if there's a way to add i386 libs to the pin?

OS: LFS, Arch, Gentoo | CPU: AMD Ryzen 3700X | Motherboard: ASUS ROG STRIX B550-F | RAM: 16GB HyperX @ 3600MHz (OC)

GPU: XFX Thicc III Ultra RX 5700 XT | Case: Fractal Meshify C | Storage: 250GB Samsung 970 EVO NVMe, 500GB SATA SSD, 2TB HDD, 1TB HDD

PSU: BeQuiet 530W | Cooling: Arctic Liquid Freezer 240

Link to comment
https://linustechtips.com/topic/1162029-debian-i386-pinning/
Share on other sites

Link to post
Share on other sites

I would be weary of updating only a specific package (or two) while leaving the rest of the system untouched - this often leads to dependency hell.

 

With that said, first of all I would try removing the package and reinstalling it - it's possible the i386 version was updated later in the repositories and was causing a versioning conflict.

Don't ask to ask, just ask... please 🤨

sudo chmod -R 000 /*

Link to comment
https://linustechtips.com/topic/1162029-debian-i386-pinning/#findComment-13349004
Share on other sites

Link to post
Share on other sites

I've had this issue before with dependency hell, so I don't know if it's almost easier to just upgrade all the packages despite it being the unstable repo. I know there's the Bullseye (testing) repo, but it was mentioned that there's no security updates for testing.


EDIT: I used deb files for the i386 packages for now. I don't even mind if I break something, I'm mainly just experimenting with the idea of having a 5700XT work on Debian, and I still have Arch installed as my main OS. Debian ships with Mesa 18.3.6, but 19.3.0 is needed for Navi iirc.

OS: LFS, Arch, Gentoo | CPU: AMD Ryzen 3700X | Motherboard: ASUS ROG STRIX B550-F | RAM: 16GB HyperX @ 3600MHz (OC)

GPU: XFX Thicc III Ultra RX 5700 XT | Case: Fractal Meshify C | Storage: 250GB Samsung 970 EVO NVMe, 500GB SATA SSD, 2TB HDD, 1TB HDD

PSU: BeQuiet 530W | Cooling: Arctic Liquid Freezer 240

Link to comment
https://linustechtips.com/topic/1162029-debian-i386-pinning/#findComment-13349019
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×