Urgent warning! Repo broken DO NOT UPDATE [Solved]

[kmathern]

A couple days before the mesa update in our ahs repos I upgraded mesa from backports (the 25.0.4-1~bpo12+1 version).
The upgrade from backports didn't require any wayland upgrades.

Code: Select all

Package: mesa-vulkan-drivers
Source: mesa
Version: 25.0.4-1~bpo12+1
Installed-Size: 64537
Maintainer: Debian X Strike Force <debian-x@lists.debian.org>
Architecture: amd64
Provides: vulkan-icd
Depends: libvulkan1, libc6 (>= 2.34), libdrm-amdgpu1 (>= 2.4.121), libdrm2 (>= 2.4.121), libelf1 (>= 0.142), libexpat1 (>= 2.0.1), libgcc-s1 (>= 3.4), libllvm15, libstdc++6 (>= 11), libwayland-client0 (>= 1.20.0), libx11-xcb1 (>= 2:1.8.4), libxcb-dri3-0 (>= 1.13), libxcb-present0, libxcb-randr0 (>= 1.13), libxcb-shm0, libxcb-sync1, libxcb-xfixes0, libxcb1 (>= 1.9.2), libxshmfence1, libzstd1 (>= 1.5.2), zlib1g (>= 1:1.1.4)

Code: Select all

Package: libegl-mesa0
Source: mesa
Version: 25.0.4-1~bpo12+1
Installed-Size: 414
Maintainer: Debian X Strike Force <debian-x@lists.debian.org>
Architecture: amd64
Provides: libegl-vendor
Depends: libc6 (>= 2.34), libdrm2 (>= 2.4.121), libexpat1 (>= 2.0.1), libgbm1 (= 25.0.4-1~bpo12+1), libgcc-s1 (>= 3.4), libwayland-client0 (>= 1.20.0), libwayland-server0 (>= 1.15.0), libx11-xcb1 (>= 2:1.8.4), libxcb-dri3-0 (>= 1.13), libxcb-present0, libxcb-randr0 (>= 1.3), libxcb-shm0, libxcb-xfixes0, libxcb1 (>= 1.6), mesa-libgallium (= 25.0.4-1~bpo12+1)

[dolphin_oracle]

A couple days before the mesa update in our ahs repos I upgraded mesa from backports (the 25.0.4-1~bpo12+1 version).
The upgrade from backports didn't require any wayland upgrades.

yeah backports may have built it a little differently. looks like it still has a depend on the earlier version of libwayland-client0 (1.21)

[Adrian]

I having seen any errors on a number of machines, I think I was luck and didn't catch things in between upgrades, I tried now with a clean install in a VM and updated everything OK.

[chrispop99]

I having seen any errors on a number of machines, I think I was luck and didn't catch things in between upgrades, I tried now with a clean install in a VM and updated everything OK.

The problem still exists here, as of 5 minutes ago.

Chris

[dolphin_oracle]

I having seen any errors on a number of machines, I think I was luck and didn't catch things in between upgrades, I tried now with a clean install in a VM and updated everything OK.

can you post the apt-history from that update? I'm presuming the KDE iso?

**edit*** ok the KDE iso lib mix is a little different, the upgrade goes thru holding the mesa packages back. this is not the case for the Xfce release.

Code: Select all

The following NEW packages will be installed:
  easy-rsa isa-support libqt6opengl6 libqt6positioning6 libqt6printsupport6 libqt6qml6 libqt6qmlmodels6
  libqt6quick6 libqt6quickwidgets6 libqt6webchannel6 libqt6webengine6-data libqt6webenginecore6
  libqt6webenginecore6-bin libqt6webenginewidgets6 libqt6xml6 sse3-support
The following packages have been kept back:
  libegl-mesa0 libgbm1 libgl1-mesa-dri libglx-mesa0 mesa-libgallium mesa-va-drivers mesa-vulkan-drivers
The following packages will be upgraded:
  catdoc ddm-mx djvulibre-bin firefox gir1.2-gdkpixbuf-2.0 konsole konsole-kpart libblockdev-crypto2
  libblockdev-fs2 libblockdev-loop2 libblockdev-part-err2 libblockdev-part2 libblockdev-swap2
  libblockdev-utils2 libblockdev2 libdjvulibre-text libdjvulibre21 libgdk-pixbuf-2.0-0
  libgdk-pixbuf2.0-common libicu72 libjxl0.7 libudisks2-0 libxatracker2 libxml2 libxml2-utils linux-base
  linux-libc-dev lo-main-helper mesa-vdpau-drivers mx-bootrepair mx-cleanup mx-packageinstaller
  mx-packageinstaller-pkglist mx-viewer openvpn plymouth-modified-init sudo thunderbird udisks2 uefi-manager
  xserver-common xserver-xorg-core xserver-xorg-legacy
43 upgraded, 16 newly installed, 0 to remove and 7 not upgraded.

[Nokkaelaein]

**edit*** ok the KDE iso lib mix is a little different, the upgrade goes thru holding the mesa packages back. this is not the case for the Xfce release.

Yeah it's specifically the AHS release using Xfce that uninstalls the whole xorg (among other things) if hitting this update.

[CharlesV]

**edit*** ok the KDE iso lib mix is a little different, the upgrade goes thru holding the mesa packages back. this is not the case for the Xfce release.

Yeah it's specifically the AHS release using Xfce that uninstalls the whole xorg (among other things) if hitting this update.

There is something more going on here though. I updated last night approx 945 pst and I noticed some oddities, but it didnt take my machine down. ( xfce, using ahs repo's )

Code: Select all

2025-07-14  21:44:44  upgrade  mesa-vdpau-drivers                                  amd64  24.2.8-1mx23ahs                  25.0.4-1~mx23ahs
2025-07-14  21:44:44  upgrade  libxatracker2                                       amd64  24.2.8-1mx23ahs         

[anticapitalista]

@dolphin_oracle @Eadwine Rose @anticapitalista

Just keying in a few in case and the Antix crew just in case they are affected. This is URGENT

EDIT

Sorry for the low volume in the recording. My wife's running Xfce but with KDE Elements. Had she updated, she would have lost the ability to use her Laptop. I just had to get this out there.

Just to point out that antiX is not affected.

[Stevo]

Maybe if you're using nala as a frontend to apt or as a backend to MX updater, it will not nuke your system, since autoremove is disabled on it.

Anyway, I'm rebuilding Mesa without the newer wayland, just the newer wayland-protocols, which I hope will duplicate backports.

[Nokkaelaein]

There is something more going on here though. I updated last night approx 945 pst and I noticed some oddities, but it didnt take my machine down.

Maybe this, also:

people that updated before we pulled the wayland packages won't be affected.

Don't know when exactly they were pulled, though.