Hi again,
I would like to thank you for your support and have another question. Using unstable to pull in the latest version of alsa-ucm-conf triggered the pull of some other packages (depencies) from unstable to my debian stable.
At the moment it seems like that all is working properly.
But I have disabled the sid repo again, to NOT pull sid in my stable during an apt upgrade. This means that all packages, installed from sid, are kept in the same version. A lot of packages:
As far as I know, this is generally no good idea.
What do you think about it? I am thinking especially about security-fixes, but this might also lead to some other problems, when I try to install stable packages which relate on specific versions of stablerepo, now are substituted by sid-packages.
Thanks!
I would like to thank you for your support and have another question. Using unstable to pull in the latest version of alsa-ucm-conf triggered the pull of some other packages (depencies) from unstable to my debian stable.
At the moment it seems like that all is working properly.
But I have disabled the sid repo again, to NOT pull sid in my stable during an apt upgrade. This means that all packages, installed from sid, are kept in the same version. A lot of packages:
Code:
Start-Date: 2024-05-16 22:13:49Commandline: apt-get install -t unstable alsa-ucm-confInstall: libsharpyuv0:amd64 (1.4.0-0.1, automatic), libsharpyuv0:i386 (1.4.0-0.1, automatic), libasound2t64:amd64 (1.2.11-1+b1, automatic), libasound2t64:i386 (1.2.11-1+b1, automatic), libavutil58:amd64 (7:6.1.1-4+b1, automatic), libavutil58:i386 (7:6.1.1-4+b1, automatic)Upgrade: libwebpmux3:amd64 (1.2.4-0.2+deb12u1, 1.4.0-0.1), libwebpmux3:i386 (1.2.4-0.2+deb12u1, 1.4.0-0.1), libvpl2:amd64 (2023.1.1-1, 2023.3.0-1), libx264-164:amd64 (2:0.164.3095+gitbaee400-3, 2:0.164.3108+git31e19f9-1), libx264-164:i386 (2:0.164.3095+gitbaee400-3, 2:0.164.3108+git31e19f9-1), alsa-ucm-conf:amd64 (1.2.8-1, 1.2.11-1.1), libmount1:amd64 (2.38.1-5+deb12u1, 2.40.1-1), libmount1:i386 (2.38.1-5+deb12u1, 2.40.1-1), libc6:amd64 (2.36-9+deb12u7, 2.38-11), libc6:i386 (2.36-9+deb12u7, 2.38-11), locales:amd64 (2.36-9+deb12u7, 2.38-11), libsnappy1v5:amd64 (1.1.9-3, 1.2.0-2), libsnappy1v5:i386 (1.1.9-3, 1.2.0-2), libwebp7:amd64 (1.2.4-0.2+deb12u1, 1.4.0-0.1), libwebp7:i386 (1.2.4-0.2+deb12u1, 1.4.0-0.1), libasound2-data:amd64 (1.2.8-1, 1.2.11-1), libc-dev-bin:amd64 (2.36-9+deb12u7, 2.38-11), libsdl2-2.0-0:amd64 (2.26.5+dfsg-1, 2.30.2+dfsg-1), libsdl2-2.0-0:i386 (2.26.5+dfsg-1, 2.30.2+dfsg-1), libc-l10n:amd64 (2.36-9+deb12u7, 2.38-11), libc-bin:amd64 (2.36-9+deb12u7, 2.38-11), libswresample4:amd64 (7:5.1.4-0+deb12u1, 7:6.1.1-4+b1), libswresample4:i386 (7:5.1.4-0+deb12u1, 7:6.1.1-4+b1), libc6-dev:amd64 (2.36-9+deb12u7, 2.38-11), libblkid1:amd64 (2.38.1-5+deb12u1, 2.40.1-1), libblkid1:i386 (2.38.1-5+deb12u1, 2.40.1-1)Remove: libasound2-plugins:i386 (1.2.7.1-1), libasound2:amd64 (1.2.8-1+b1), libasound2:i386 (1.2.8-1+b1), libavcodec59:i386 (7:5.1.4-0+deb12u1), libzvbi0:i386 (0.2.41-1)What do you think about it? I am thinking especially about security-fixes, but this might also lead to some other problems, when I try to install stable packages which relate on specific versions of stablerepo, now are substituted by sid-packages.
Thanks!
Statistics: Posted by mcdaniels — 2024-05-17 05:42
