Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #266763 > unrolled thread
| Started by | Miroslav Skoric <skoric@uns.ac.rs> |
|---|---|
| First post | 2024-01-30 13:30 +0100 |
| Last post | 2024-01-31 00:50 +0100 |
| Articles | 17 — 7 participants |
Back to article view | Back to linux.debian.user
apt full-upgrade failed at marco-common package Miroslav Skoric <skoric@uns.ac.rs> - 2024-01-30 13:30 +0100
Re: apt full-upgrade failed at marco-common package Greg Wooledge <greg@wooledge.org> - 2024-01-30 13:50 +0100
Re: apt full-upgrade failed at marco-common package Miroslav Skoric <skoric@uns.ac.rs> - 2024-01-31 00:50 +0100
Re: apt full-upgrade failed at marco-common package Michael Kjörling <2695bd53d63c@ewoof.net> - 2024-01-30 13:50 +0100
Re: apt full-upgrade failed at marco-common package Miroslav Skoric <skoric@uns.ac.rs> - 2024-01-31 00:50 +0100
Wine in bullseye, which way to go? Miroslav Skoric <skoric@uns.ac.rs> - 2024-02-01 12:20 +0100
Re: Wine in bullseye, which way to go? Marco Moock <mm@dorfdsl.de> - 2024-02-01 15:10 +0100
Re: Wine in bullseye, which way to go? skoric@uns.ac.rs - 2024-02-01 16:40 +0100
Re: Wine in bullseye, which way to go? Marco Moock <mm@dorfdsl.de> - 2024-02-01 16:50 +0100
Re: Wine in bullseye, which way to go? skoric@uns.ac.rs - 2024-02-01 18:10 +0100
Re: Wine in bullseye, which way to go? Marco Moock <mm@dorfdsl.de> - 2024-02-02 21:00 +0100
Re: Wine in bullseye, which way to go? Greg Wooledge <greg@wooledge.org> - 2024-02-02 21:20 +0100
Re: Wine in bullseye, which way to go? Miroslav Skoric <skoric@uns.ac.rs> - 2024-02-03 12:40 +0100
Re: Wine in bullseye, which way to go? Marco Moock <mm@dorfdsl.de> - 2024-02-03 12:50 +0100
Re: Wine in bullseye, which way to go? Timothy M Butterworth <timothy.m.butterworth@gmail.com> - 2024-02-03 04:10 +0100
Re: apt full-upgrade failed at marco-common package The Wanderer <wanderer@fastmail.fm> - 2024-01-30 13:50 +0100
Re: apt full-upgrade failed at marco-common package Miroslav Skoric <skoric@uns.ac.rs> - 2024-01-31 00:50 +0100
| From | Miroslav Skoric <skoric@uns.ac.rs> |
|---|---|
| Date | 2024-01-30 13:30 +0100 |
| Subject | apt full-upgrade failed at marco-common package |
| Message-ID | <I1Vpv-6B8E-3@gated-at.bofh.it> |
Hi, I [partially] upgraded buster to bullseye according to official "Release Notes for Debian 11 (bullseye), 32-bit PC" (October 4, 2023). I did it in two sessions as suggested: "4.4.4 Minimal system upgrade" (# apt upgrade --without-new-pkgs). That part performed without any issue, and cat /etc/debian_version reported 11.8 (previously it was 10.x). "4.4.5 Upgrading the system" (# apt full-upgrade) ran also fine until some 20% or so, and then failed when handled marco-common package. Here are the few last lines of that session: ... Preparing to unpack .../6-mate-settings-daemon-common_1.24.1-1_all.deb ... Unpacking mate-settings-daemon-common (1.24.1-1) over (1.20.4-1) ... Preparing to unpack .../7-marco_1.24.1-3_i386.deb ... Unpacking marco (1.24.1-3) over (1.20.3-1) ... Preparing to unpack .../8-marco-common_1.24.1-3_all.deb ... Unpacking marco-common (1.24.1-3) over (1.20.3-1) ... .[1mdpkg:.[0m error processing archive /tmp/apt-dpkg-install-S65GMD/8-marco-common_1.24.1-3_all.deb (--unpack): trying to overwrite '/usr/share/themes/Gorilla/metacity-1/metacity-theme-1.xml', which is also in package gnome-themes-more 0.9.0.deb0.8 Errors were encountered while processing: /tmp/apt-dpkg-install-S65GMD/8-marco-common_1.24.1-3_all.deb A repeated # apt full-upgrade returned a list of unmet dependencies, including this one: marco : Depends: marco-common (= 1.24.1-3) but 1.20.3-1 is installed At the end of the list it suggested: Try 'apt --fix-broken install' with no packages (or specify a solution). I tried it and it seemed as if it tried to process again the above lines (unpacking, preparing), to no avail. What can I try to resolve that? After system reboot, I am able to reach the rescue mode as root and type commands. (Green 'OK' follow all parts of boot. GUI, startx fail. Shutdown, poweroff run properly.) Thank you. Misko
[toc] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2024-01-30 13:50 +0100 |
| Message-ID | <I1VIR-6Bfi-1@gated-at.bofh.it> |
| In reply to | #266763 |
On Tue, Jan 30, 2024 at 01:19:09PM +0100, Miroslav Skoric wrote: > Unpacking marco-common (1.24.1-3) over (1.20.3-1) ... > .[1mdpkg:.[0m error processing archive > /tmp/apt-dpkg-install-S65GMD/8-marco-common_1.24.1-3_all.deb (--unpack): > trying to overwrite > '/usr/share/themes/Gorilla/metacity-1/metacity-theme-1.xml', which is also > in package gnome-themes-more 0.9.0.deb0.8 These two packages can't coexist, so you're going to have to pick one to get rid of. I did an "apt-cache show marco", and it's a window manager intended to be used by MATE. I did "apt-cache show gnome-themes-more" and it doesn't exist in Debian 12 at all. It must have been removed at some point, or else it came from a third party source. (That "*deb0.8" version string looks a little odd to me, too.) So... figure out which of these two packages you can live without, get rid of it, and then retry the upgrade. Two packages both trying to supply the same file, without a Conflicts: line or something equivalent, should be considered a bug, if they're both Debian packages. If one of them's third-party, then of course all bets are off.
[toc] | [prev] | [next] | [standalone]
| From | Miroslav Skoric <skoric@uns.ac.rs> |
|---|---|
| Date | 2024-01-31 00:50 +0100 |
| Message-ID | <I261A-6HsA-9@gated-at.bofh.it> |
| In reply to | #266764 |
On 1/30/24 1:41 PM, Greg Wooledge wrote: > On Tue, Jan 30, 2024 at 01:19:09PM +0100, Miroslav Skoric wrote: >> Unpacking marco-common (1.24.1-3) over (1.20.3-1) ... >> .[1mdpkg:.[0m error processing archive >> /tmp/apt-dpkg-install-S65GMD/8-marco-common_1.24.1-3_all.deb (--unpack): >> trying to overwrite >> '/usr/share/themes/Gorilla/metacity-1/metacity-theme-1.xml', which is also >> in package gnome-themes-more 0.9.0.deb0.8 > > These two packages can't coexist, so you're going to have to pick > one to get rid of. > > I did an "apt-cache show marco", and it's a window manager intended > to be used by MATE. > > I did "apt-cache show gnome-themes-more" and it doesn't exist in > Debian 12 at all. It must have been removed at some point, or else > it came from a third party source. (That "*deb0.8" version string > looks a little odd to me, too.) > > So... figure out which of these two packages you can live without, > get rid of it, and then retry the upgrade. > > Two packages both trying to supply the same file, without a Conflicts: > line or something equivalent, should be considered a bug, if they're > both Debian packages. If one of them's third-party, then of course > all bets are off. > > Thank you. I removed gnome-themes-more as I mostly use MATE. (Did not check whether Gnome would suffer by any means :-)
[toc] | [prev] | [next] | [standalone]
| From | Michael Kjörling <2695bd53d63c@ewoof.net> |
|---|---|
| Date | 2024-01-30 13:50 +0100 |
| Message-ID | <I1VIR-6Bfi-3@gated-at.bofh.it> |
| In reply to | #266763 |
On 30 Jan 2024 13:19 +0100, from skoric@uns.ac.rs (Miroslav Skoric): > Preparing to unpack .../8-marco-common_1.24.1-3_all.deb ... > Unpacking marco-common (1.24.1-3) over (1.20.3-1) ... > .[1mdpkg:.[0m error processing archive > /tmp/apt-dpkg-install-S65GMD/8-marco-common_1.24.1-3_all.deb (--unpack): > trying to overwrite > '/usr/share/themes/Gorilla/metacity-1/metacity-theme-1.xml', which is also > in package gnome-themes-more 0.9.0.deb0.8 > Errors were encountered while processing: > /tmp/apt-dpkg-install-S65GMD/8-marco-common_1.24.1-3_all.deb https://www.debian.org/releases/bullseye/amd64/release-notes/ch-upgrading.en.html#file-conflicts should help. -- Michael Kjörling 🔗 https://michael.kjorling.se “Remember when, on the Internet, nobody cared that you were a dog?”
[toc] | [prev] | [next] | [standalone]
| From | Miroslav Skoric <skoric@uns.ac.rs> |
|---|---|
| Date | 2024-01-31 00:50 +0100 |
| Message-ID | <I261z-6HsA-3@gated-at.bofh.it> |
| In reply to | #266765 |
On 1/30/24 1:43 PM, Michael Kjörling wrote: > > https://www.debian.org/releases/bullseye/amd64/release-notes/ch-upgrading.en.html#file-conflicts > should help. > Sure. Thanks!
[toc] | [prev] | [next] | [standalone]
| From | Miroslav Skoric <skoric@uns.ac.rs> |
|---|---|
| Date | 2024-02-01 12:20 +0100 |
| Subject | Wine in bullseye, which way to go? |
| Message-ID | <I2DgR-73vd-5@gated-at.bofh.it> |
| In reply to | #266765 |
Hi! As I have some Windows software (for ham radio) that does not have adequate Linux versions, I wanted to install Wine and some related packages from the bullseye repository (wine, q4wine, winetricks, playonlinux, etc). By the way, I had Wine with buster earlier, and most Windows software worked more or less flawlessly, but I deinstalled all that software and Wine before I upgraded buster to bullseye. This time I was puzzled when noticed that Synaptic installed lots of amd64 packages even though my system is i386. Also, it removed some packages, and also reported few errors or like. Finally, no Windows software wanted to run, instead q4wine returned "Exit -1" or like. See bellow some details for particular packages installation: (Wine) Removing portaudio19-dev:i386 (19.6.0-1.1) ... Removing libjack-dev (1:0.125.0-3+b1) ... dpkg: libjack0:i386: dependency problems, but removing anyway as you requested: mpv depends on libjack-jackd2-0 (>= 1.9.10+20150825) | libjack-0.125; however: Package libjack-jackd2-0 is not installed. Package libjack-0.125 is not installed. Package libjack0:i386 which provides libjack-0.125 is to be removed. mplayer depends on libjack-jackd2-0 (>= 1.9.10+20150825) | libjack-0.125; however: Package libjack-jackd2-0 is not installed. Package libjack-0.125 is not installed. Package libjack0:i386 which provides libjack-0.125 is to be removed. libportaudio2:i386 depends on libjack-jackd2-0 (>= 1.9.10+20150825) | libjack-0.125; however: Package libjack-jackd2-0 is not installed. Package libjack-0.125 is not installed. Package libjack0:i386 which provides libjack-0.125 is to be removed. libfluidsynth2:i386 depends on libjack-jackd2-0 (>= 1.9.10+20150825) | libjack-0.125; however: Package libjack-jackd2-0 is not installed. Package libjack-0.125 is not installed. Package libjack0:i386 which provides libjack-0.125 is to be removed. libavdevice58:i386 depends on libjack-jackd2-0 (>= 1.9.10+20150825) | libjack-0.125; however: Package libjack-jackd2-0 is not installed. Package libjack-0.125 is not installed. Package libjack0:i386 which provides libjack-0.125 is to be removed. libasound2-plugins:i386 depends on libjack-jackd2-0 (>= 1.9.10+20150825) | libjack-0.125; however: Package libjack-jackd2-0 is not installed. Package libjack-0.125 is not installed. Package libjack0:i386 which provides libjack-0.125 is to be removed. gstreamer1.0-plugins-good:i386 depends on libjack-jackd2-0 (>= 1.9.10+20150825) | libjack-0.125; however: Package libjack-jackd2-0 is not installed. Package libjack-0.125 is not installed. Package libjack0:i386 which provides libjack-0.125 is to be removed. Removing libjack0:i386 (1:0.125.0-3+b1) ... Setting up gcc-10-base:amd64 (10.2.1-6) ... Setting up libgcc-s1:amd64 (10.2.1-6) ... Setting up libcrypt1:amd64 (1:4.4.18-4) ... Setting up libc6:amd64 (2.31-13+deb11u7) ... Setting up libgpg-error0:amd64 (1.38-2) ... Setting up libgcrypt20:amd64 (1.8.7-6) ... Setting up liblz4-1:amd64 (1.9.3-2) ... Setting up liblzma5:amd64 (5.2.5-2.1~deb11u1) ... Setting up libzstd1:amd64 (1.4.8+dfsg-2.1) ... Setting up libexpat1:amd64 (2.2.10-2+deb11u5) ... Setting up libgraphite2-3:amd64 (1.3.14-1) ... Setting up liblcms2-2:amd64 (2.12~rc1-2) ... Setting up libpixman-1-0:amd64 (0.40.0-1.1~deb11u1) ... Setting up libcdparanoia0:amd64 (3.10.2+debian-13.1) ... Setting up ipp-usb (0.9.17-3+b4) ... ipp-usb.service is a disabled or a static unit, not starting it. Setting up libvo-amrwbenc0:amd64 (0.1.3-2) ... Setting up libxau6:amd64 (1:1.0.9-1) ... Setting up libraw1394-11:amd64 (2.1.2-2) ... Setting up libkeyutils1:amd64 (1.6.1-2) ... Setting up libgpm2:amd64 (1.20.7-8) ... Setting up libmpg123-0:amd64 (1.26.4-1) ... Setting up libogg0:amd64 (1.3.4-0.1) ... Setting up libspeex1:amd64 (1.2~rc1.2-1.1) ... Setting up libshine3:amd64 (3.1.1-2) ... Setting up libtwolame0:amd64 (0.4.0-2) ... Setting up libdatrie1:amd64 (0.2.13-1) ... Setting up libgsm1:amd64 (1.0.18-2) ... Setting up libvisual-0.4-0:amd64 (0.4.0-17) ... Setting up libcapi20-3:amd64 (1:3.27-3+b1) ... Setting up libglvnd0:amd64 (1.3.2-1) ... Setting up libssl1.1:amd64 (1.1.1w-0+deb11u1) ... Setting up libaom0:amd64 (1.0.0.errata1-3+deb11u1) ... Setting up libbrotli1:amd64 (1.0.9-2+b2) ... Setting up libsqlite3-0:amd64 (3.34.1-3) ... Setting up libsasl2-modules:amd64 (2.1.27+dfsg-2.1+deb11u1) ... Setting up libffi7:amd64 (3.3-6) ... Setting up libvkd3d1:i386 (1.1-5) ... Setting up libnghttp2-14:amd64 (1.43.0-1+deb11u1) ... Setting up libunistring2:amd64 (0.9.10-4) ... Setting up libdeflate0:amd64 (1.7-1) ... Setting up zlib1g:amd64 (1:1.2.11.dfsg-2+deb11u2) ... Setting up libidn2-0:amd64 (2.3.0-5) ... Setting up libcom-err2:amd64 (1.46.2-2) ... Setting up libgomp1:amd64 (10.2.1-6) ... Setting up libxvidcore4:amd64 (2:1.3.7-1) ... Setting up libunwind8:amd64 (1.3.2-2) ... Setting up libx264-160:amd64 (2:0.160.3011+gitcde9a93-2.1) ... Setting up libjbig0:amd64 (2.1-3.1+b2) ... Setting up libsystemd0:amd64 (247.3-7+deb11u4) ... Setting up libcap2:amd64 (1:2.44-1) ... Setting up libflac8:amd64 (1.3.3-2+deb11u2) ... Setting up libkrb5support0:amd64 (1.18.3-6+deb11u4) ... Setting up fonts-wine (5.0.3-3) ... Setting up libthai0:amd64 (0.1.28-3) ... Setting up libopencore-amrwb0:amd64 (0.1.5-1) ... Setting up libpcre3:amd64 (2:8.39-13) ... Setting up libjpeg62-turbo:amd64 (1:2.0.6-4) ... Setting up libslang2:amd64 (2.3.2-5) ... Setting up libva2:amd64 (2.10.0-1) ... Setting up libnettle8:amd64 (3.7.3-1) ... Setting up libnspr4:amd64 (2:4.29-1) ... Setting up libgmp10:amd64 (2:6.2.1+dfsg-1+deb11u1) ... Setting up libcodec2-0.9:amd64 (0.9.2-4) ... Setting up libavahi-common-data:amd64 (0.8-5+deb11u2) ... Setting up libdbus-1-3:amd64 (1.12.28-0+deb11u1) ... Setting up libfribidi0:amd64 (1.0.8-2+deb11u1) ... Setting up libopus0:amd64 (1.3.1-0.1) ... Setting up libp11-kit0:amd64 (0.23.22-1) ... Setting up libexif12:amd64 (0.6.22-3) ... Setting up libstb0:amd64 (0.0~git20200713.b42009b+ds-1) ... Setting up libstb0:i386 (0.0~git20200713.b42009b+ds-1) ... Setting up libpng16-16:amd64 (1.6.37-3) ... Setting up libvorbis0a:amd64 (1.3.7-1) ... Setting up libuuid1:amd64 (2.36.1-8+deb11u1) ... Setting up liborc-0.4-0:amd64 (1:0.4.32-1) ... Setting up libwebp6:amd64 (0.6.1-2.1+deb11u2) ... Setting up libsensors5:amd64 (1:3.6.0-7) ... Setting up libpcre2-8-0:amd64 (10.36-2+deb11u1) ... Setting up libk5crypto3:amd64 (1.18.3-6+deb11u4) ... Setting up libltdl7:amd64 (2.4.6-15) ... Setting up libglapi-mesa:amd64 (20.3.5-1) ... Setting up libvulkan1:amd64 (1.2.162.0-1) ... Setting up libudev1:amd64 (247.3-7+deb11u4) ... Setting up libpci3:amd64 (1:3.7.0-5) ... Setting up libnuma1:amd64 (2.0.12-1+b1) ... Setting up libjack-jackd2-0:i386 (1.9.17~dfsg-1) ... Setting up libdrm2:amd64 (2.4.104-1) ... Setting up libmd0:amd64 (1.0.3-3) ... Setting up libva-drm2:amd64 (2.10.0-1) ... Setting up libdv4:amd64 (1.0.0-13) ... Setting up ocl-icd-libopencl1:amd64 (2.2.14-2) ... Setting up uuid-runtime (2.36.1-8+deb11u1) ... Created symlink /etc/systemd/system/sockets.target.wants/uuidd.socket → /lib/systemd/system/uuidd.socket. uuidd.service is a disabled or a static unit, not starting it. Setting up libasyncns0:amd64 (0.8-6+b2) ... Setting up libxshmfence1:amd64 (1.3-1) ... Setting up libvpx6:amd64 (1.9.0-1+deb11u2) ... Setting up libwavpack1:amd64 (5.4.0-1) ... Setting up libasound2:amd64 (1.2.4-1.1) ... Setting up libv4lconvert0:amd64 (1.20.0-2) ... Setting up libopencore-amrnb0:amd64 (0.1.5-1) ... Setting up libtasn1-6:amd64 (4.16.0-2+deb11u1) ... Setting up libdav1d4:amd64 (0.7.1-3) ... Setting up libopenjp2-7:amd64 (2.4.0-3) ... Setting up libssh2-1:amd64 (1.9.0-2) ... Setting up libkrb5-3:amd64 (1.18.3-6+deb11u4) ... Setting up libtiff5:amd64 (4.2.0-1+deb11u5) ... Setting up libwayland-egl1:amd64 (1.18.0-2~exp1.1) ... Setting up libusb-1.0-0:amd64 (2:1.0.24-3) ... Setting up libgphoto2-port12:amd64 (2.5.27-1) ... Setting up libieee1284-3:amd64 (0.2.11-14) ... Setting up libbz2-1.0:amd64 (1.0.8-4) ... Setting up libsamplerate0:amd64 (0.2.1+ds0-1) ... Setting up libwebpmux3:amd64 (0.6.1-2.1+deb11u2) ... Setting up libbsd0:amd64 (0.11.3-1+deb11u1) ... Setting up libelf1:amd64 (0.183-1) ... Setting up libdb5.3:amd64 (5.3.28+dfsg1-0.8) ... Setting up libblkid1:amd64 (2.36.1-8+deb11u1) ... Setting up libstdc++6:amd64 (10.2.1-6) ... Setting up libmp3lame0:amd64 (3.100-3) ... Setting up libvorbisenc2:amd64 (1.3.7-1) ... Setting up libgdbm6:amd64 (1.19-2) ... Setting up libtinfo6:amd64 (6.2+20201114-2+deb11u2) ... Setting up libiec61883-0:amd64 (1.2.0-4) ... Setting up libdrm-amdgpu1:amd64 (2.4.104-1) ... Setting up libosmesa6:i386 (20.3.5-1) ... Setting up libxkbcommon0:amd64 (1.0.3-2) ... Setting up libwayland-client0:amd64 (1.18.0-2~exp1.1) ... Setting up libavc1394-0:amd64 (0.5.4-5) ... Setting up libzvbi0:amd64 (0.2.35-18) ... Setting up libwayland-server0:amd64 (1.18.0-2~exp1.1) ... Setting up libpciaccess0:amd64 (0.16-1) ... Setting up libdw1:amd64 (0.183-1) ... Setting up libxdmcp6:amd64 (1:1.1.2-3) ... Setting up libproxy1v5:amd64 (0.4.17-1) ... Setting up libpsl5:amd64 (0.21.0-1.2) ... Setting up libdrm-nouveau2:amd64 (2.4.104-1) ... Setting up libxcb1:amd64 (1.14-3) ... Setting up libhogweed6:amd64 (3.7.3-1) ... Setting up libxcb-xfixes0:amd64 (1.14-3) ... Setting up libicu67:amd64 (67.1-7) ... Setting up libgbm1:amd64 (20.3.5-1) ... Setting up libxcb-render0:amd64 (1.14-3) ... Setting up libsoxr0:amd64 (0.1.3-4) ... Setting up libdrm-radeon1:amd64 (2.4.104-1) ... Setting up libxcb-glx0:amd64 (1.14-3) ... Setting up libedit2:amd64 (3.1-20191231-2+b1) ... Setting up libdrm-intel1:amd64 (2.4.104-1) ... Setting up libvkd3d1:amd64 (1.1-5) ... Setting up libavahi-common3:amd64 (0.8-5+deb11u2) ... Setting up libx265-192:amd64 (3.4-2) ... Setting up libnss3:amd64 (2:3.61-1+deb11u3) ... Setting up libxcb-shm0:amd64 (1.14-3) ... Setting up libaribb24-0:amd64 (1.0.3-2) ... Setting up libsnappy1v5:amd64 (1.1.8-1) ... Setting up libsasl2-modules-db:amd64 (2.1.27+dfsg-2.1+deb11u1) ... Setting up libxcb-present0:amd64 (1.14-3) ... Setting up libv4l-0:amd64 (1.20.0-2) ... Setting up libselinux1:amd64 (3.1-3) ... Setting up libz3-4:amd64 (4.8.10-1) ... Setting up libgnutls30:amd64 (3.7.1-5+deb11u3) ... Setting up libllvm11:amd64 (1:11.0.1-2) ... Setting up libfaudio0:i386 (21.02-1) ... Setting up libfreetype6:amd64 (2.10.4+dfsg-1+deb11u1) ... Setting up libpcap0.8:amd64 (1.10.0-2) ... Setting up libigdgmm11:amd64 (20.4.1+ds1-1) ... Setting up libxcb-sync1:amd64 (1.14-3) ... Setting up librtmp1:amd64 (2.4+20151223.gitfa8646d.1-2+b2) ... Setting up libncurses6:amd64 (6.2+20201114-2+deb11u2) ... Setting up intel-media-va-driver:amd64 (21.1.1+dfsg1-1) ... Setting up libgssapi-krb5-2:amd64 (1.18.3-6+deb11u4) ... Setting up libgdbm-compat4:amd64 (1.19-2) ... Setting up libodbc1:amd64 (2.3.6-0.1+b1) ... Setting up libncursesw6:amd64 (6.2+20201114-2+deb11u2) ... Setting up libperl5.32:amd64 (5.32.1-4+deb11u2) ... Setting up libsasl2-2:amd64 (2.1.27+dfsg-2.1+deb11u1) ... Setting up libsndio7.0:amd64 (1.5.0-3) ... Setting up libxcb-dri2-0:amd64 (1.14-3) ... Setting up libjack-jackd2-0:amd64 (1.9.17~dfsg-1) ... Setting up libmount1:amd64 (2.36.1-8+deb11u1) ... Setting up libwayland-cursor0:amd64 (1.18.0-2~exp1.1) ... Setting up libxcb-randr0:amd64 (1.14-3) ... Setting up libx11-6:amd64 (2:1.7.2-1+deb11u2) ... Setting up libfontconfig1:amd64 (2.13.1-4.2) ... Setting up libsndfile1:amd64 (1.0.31-2) ... Setting up libwine:i386 (5.0.3-3) ... Setting up libmfx1:amd64 (21.1.0-1) ... Setting up libxcomposite1:amd64 (1:0.4.5-1) ... Setting up libxml2:amd64 (2.9.10+dfsg-6.7+deb11u4) ... Setting up libavahi-client3:amd64 (0.8-5+deb11u2) ... Setting up i965-va-driver:amd64 (2.4.1+dfsg1-1) ... Setting up libaa1:amd64 (1.4p5-48) ... Setting up libosmesa6:amd64 (20.3.5-1) ... Setting up libtirpc3:amd64 (1.3.1-1+deb11u1) ... Setting up libxcb-dri3-0:amd64 (1.14-3) ... Setting up libx11-xcb1:amd64 (2:1.7.2-1+deb11u2) ... Setting up libtag1v5-vanilla:amd64 (1.11.1+dfsg.1-3) ... Setting up libxdamage1:amd64 (1:1.1.5-2) ... Setting up libcaca0:amd64 (0.99.beta19-2.2) ... Setting up libxpm4:amd64 (1:3.5.12-1.1+deb11u1) ... Setting up libxrender1:amd64 (1:0.9.10-1) ... Setting up libglib2.0-0:amd64 (2.66.8-1) ... /var/lib/dpkg/info/libglib2.0-0:amd64.postinst: 62: /usr/lib/x86_64-linux-gnu/glib-2.0/glib-compile-schemas: Exec format error /var/lib/dpkg/info/libglib2.0-0:amd64.postinst: 65: /usr/lib/x86_64-linux-gnu/glib-2.0/gio-querymodules: Exec format error Setting up libgl1-mesa-dri:amd64 (20.3.5-1) ... Setting up libxext6:amd64 (2:1.3.3-1.1) ... Setting up libldap-2.4-2:amd64 (2.4.57+dfsg-3+deb11u1) ... Setting up libcurl3-gnutls:amd64 (7.74.0-1.3+deb11u11) ... Setting up libopenal1:amd64 (1:1.19.1-2) ... Setting up wine32 (5.0.3-3) ... Setting up libcairo2:amd64 (1.16.0-5) ... Setting up libxxf86vm1:amd64 (1:1.1.4-1+b2) ... Setting up libxfixes3:amd64 (1:5.0.3-2) ... Setting up libxinerama1:amd64 (2:1.1.4-2) ... Setting up libgd3:amd64 (2.3.0-2) ... Setting up libxv1:amd64 (2:1.0.11-1) ... Setting up libxrandr2:amd64 (2:1.5.1-1) ... Setting up libcups2:amd64 (2.3.3op2-3+deb11u6) ... Setting up libtag1v5:amd64 (1.11.1+dfsg.1-3) ... Setting up libpoppler102:amd64 (20.09.0-3.1+deb11u1) ... Setting up libvdpau1:amd64 (1.4-3) ... Setting up libtheora0:amd64 (1.1.1+dfsg.1-15) ... Setting up libnsl2:amd64 (1.3.0-2) ... Setting up libxslt1.1:amd64 (1.1.34-4+deb11u1) ... Setting up libcurl4:amd64 (7.74.0-1.3+deb11u11) ... Setting up libxss1:amd64 (1:1.2.3-1) ... Setting up mesa-va-drivers:amd64 (20.3.5-1) ... Setting up libva-x11-2:amd64 (2.10.0-1) ... Setting up mesa-vulkan-drivers:amd64 (20.3.5-1) ... Setting up mesa-vdpau-drivers:amd64 (20.3.5-1) ... Setting up wine (5.0.3-3) ... Setting up libglx-mesa0:amd64 (20.3.5-1) ... Setting up libxi6:amd64 (2:1.7.10-1) ... Setting up libglx0:amd64 (1.3.2-1) ... Setting up libxcursor1:amd64 (1:1.2.0-2) ... Setting up libnss-nisplus:amd64 (1.3-4) ... Setting up libavutil56:amd64 (7:4.3.6-0+deb11u1) ... Setting up libgphoto2-6:amd64 (2.5.27-1) ... Setting up libgl1:amd64 (1.3.2-1) ... Setting up libwrap0:amd64 (7.6.q-31) ... Setting up libnss-nis:amd64 (3.1-4) ... Setting up va-driver-all:amd64 (2.10.0-1) ... Setting up libshout3:amd64 (2.4.5-1+b1) ... Setting up libglu1-mesa:amd64 (9.0.1-1) ... Setting up libvdpau-va-gl1:amd64 (0.4.2-1+b1) ... Setting up libpulse0:amd64 (14.2-2) ... Setting up libswresample3:amd64 (7:4.3.6-0+deb11u1) ... Setting up libavresample4:amd64 (7:4.3.6-0+deb11u1) ... Setting up libsnmp40:amd64 (5.9+dfsg-4+deb11u1) ... Setting up vdpau-driver-all:amd64 (1.4-3) ... Setting up libsdl2-2.0-0:amd64 (2.0.14+dfsg2-3+deb11u1) ... Processing triggers for udev (247.3-7+deb11u4) ... Processing triggers for hicolor-icon-theme (0.17-2) ... Processing triggers for libglib2.0-0:i386 (2.66.8-1) ... Processing triggers for libc-bin (2.31-13+deb11u7) ... Processing triggers for man-db (2.9.4-2) ... Setting up libharfbuzz0b:amd64 (2.7.4-1) ... Setting up libgdk-pixbuf-2.0-0:amd64 (2.42.2+dfsg-1+deb11u1) ... /var/lib/dpkg/info/libgdk-pixbuf-2.0-0:amd64.postinst: 30: /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders: Exec format error Setting up libcairo-gobject2:amd64 (1.16.0-5) ... Setting up glib-networking:amd64 (2.66.0-2) ... Setting up libgudev-1.0-0:amd64 (234-1) ... Setting up libgstreamer1.0-0:amd64 (1.18.4-2.1) ... Setcap worked! gst-ptp-helper is not suid! Setting up libpoppler-glib8:amd64 (20.09.0-3.1+deb11u1) ... Setting up libsoup2.4-1:amd64 (2.72.0-2) ... Setting up libpango-1.0-0:amd64 (1.46.2-3) ... Setting up libgstreamer-plugins-base1.0-0:amd64 (1.18.4-2+deb11u1) ... Setting up libsane1:amd64 (1.0.31-4.1) ... Setting up gstreamer1.0-plugins-base:amd64 (1.18.4-2+deb11u1) ... Setting up libfaudio0:amd64 (21.02-1) ... Setting up libwine:amd64 (5.0.3-3) ... Setting up libpangoft2-1.0-0:amd64 (1.46.2-3) ... Setting up libpangocairo-1.0-0:amd64 (1.46.2-3) ... Setting up gstreamer1.0-x:amd64 (1.18.4-2+deb11u1) ... Setting up gstreamer1.0-plugins-good:amd64 (1.18.4-2+deb11u2) ... Setting up wine64:amd64 (5.0.3-3) ... Setting up librsvg2-2:amd64 (2.50.3+dfsg-1+deb11u1) ... Setting up librsvg2-common:amd64 (2.50.3+dfsg-1+deb11u1) ... Setting up libavcodec-extra58:amd64 (7:4.3.6-0+deb11u1) ... Setting up libasound2-plugins:amd64 (1.2.2-2) ... Processing triggers for wine (5.0.3-3) ... Processing triggers for libc-bin (2.31-13+deb11u7) ... Processing triggers for libgdk-pixbuf-2.0-0:amd64 (2.42.2+dfsg-1+deb11u1) ... /var/lib/dpkg/info/libgdk-pixbuf-2.0-0:amd64.postinst: 16: /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders: Exec format error (Q4Wine) Setting up icoutils (0.32.3-3) ... Setting up q4wine (1.3.12-1) ... (Winetricks) Setting up fuseiso (20070708-3.2+b1) ... Setting up winetricks (0.0+20210206-2) ... (Wine32-preloader) Setting up wine32-preloader (5.0.3-3) ... (Wine64-preloader) Setting up wine64-preloader:amd64 (5.0.3-3) ... (PlayOnLinux) Setting up python3-natsort (7.1.0-1) ... Setting up libwxbase3.0-0v5:i386 (3.0.5.1+dfsg-2) ... Setting up libonig5:i386 (6.9.6-1.1) ... Setting up libjq1:i386 (1.6-2.1) ... Setting up libwxgtk3.0-gtk3-0v5:i386 (3.0.5.1+dfsg-2) ... Setting up jq (1.6-2.1) ... Setting up python3-wxgtk4.0 (4.0.7+dfsg-10) ... Setting up playonlinux (4.3.4-2) ... I also visited WineHQ site and noticed that they recommend some other ways to install Wine (not directly from bullseye repository). It makes me wonder what is the best approach. Thank you. Misko
[toc] | [prev] | [next] | [standalone]
| From | Marco Moock <mm@dorfdsl.de> |
|---|---|
| Date | 2024-02-01 15:10 +0100 |
| Subject | Re: Wine in bullseye, which way to go? |
| Message-ID | <I2FVo-75mH-3@gated-at.bofh.it> |
| In reply to | #266835 |
Am 01.02.2024 schrieb Miroslav Skoric <skoric@uns.ac.rs>: > This time I was puzzled when noticed that Synaptic installed lots of > amd64 packages even though my system is i386. Run uname -a lscpu and post it here. If your system is i386 only, amd64 software can't run on it. Remove that architecture from dpkg.
[toc] | [prev] | [next] | [standalone]
| From | skoric@uns.ac.rs |
|---|---|
| Date | 2024-02-01 16:40 +0100 |
| Subject | Re: Wine in bullseye, which way to go? |
| Message-ID | <I2Hkt-767d-5@gated-at.bofh.it> |
| In reply to | #266837 |
> Am 01.02.2024 schrieb Miroslav Skoric <skoric@uns.ac.rs>:
>
>> This time I was puzzled when noticed that Synaptic installed lots of
>> amd64 packages even though my system is i386.
>
> Run
> uname -a
> lscpu
>
> and post it here.
>
> If your system is i386 only, amd64 software can't run on it.
> Remove that architecture from dpkg.
>
>
uname -a
Linux localhost 5.10.0-27-686 #1 SMP Debian 5.10.205-2 (2023-12-31) i686
GNU/Linux
lscpu
Architecture: i686
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
Address sizes: 36 bits physical, 48 bits virtual
CPU(s): 2
On-line CPU(s) list: 0,1
Thread(s) per core: 1
Core(s) per socket: 2
Socket(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 23
Model name: Pentium(R) Dual-Core CPU T4500
@ 2.30
GHz
Stepping: 10
CPU MHz: 1316.130
CPU max MHz: 2300.0000
CPU min MHz: 1200.0000
BogoMIPS: 4588.77
L1d cache: 64 KiB
L1i cache: 64 KiB
L2 cache: 1 MiB
Vulnerability Gather data sampling: Not affected
Vulnerability Itlb multihit: KVM: Mitigation: VMX unsupported
Vulnerability L1tf: Vulnerable
Vulnerability Mds: Vulnerable: Clear CPU buffers
attempted, no
microcode; SMT disabled
Vulnerability Meltdown: Vulnerable
Vulnerability Mmio stale data: Unknown: No mitigations
Vulnerability Retbleed: Not affected
Vulnerability Spec rstack overflow: Not affected
Vulnerability Spec store bypass: Vulnerable
Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers
and __u
ser pointer sanitization
Vulnerability Spectre v2: Mitigation; Retpolines, STIBP
disabled, RSB
filling, PBRSB-eIBRS Not affected
Vulnerability Srbds: Not affected
Vulnerability Tsx async abort: Not affected
Flags: fpu vme de pse tsc msr pae mce cx8
apic sep
mtrr pge mca cmov pat pse36 clflush
dts acpi
mmx fxsr sse sse2 ht tm pbe nx lm
constant_
tsc arch_perfmon pebs bts cpuid
aperfmperf p
ni dtes64 monitor ds_cpl est tm2 ssse3
cx16
xtpr pdcm xsave lahf_lm dtherm
[toc] | [prev] | [next] | [standalone]
| From | Marco Moock <mm@dorfdsl.de> |
|---|---|
| Date | 2024-02-01 16:50 +0100 |
| Subject | Re: Wine in bullseye, which way to go? |
| Message-ID | <I2Hu9-76aB-11@gated-at.bofh.it> |
| In reply to | #266839 |
Am 01.02.2024 schrieb skoric@uns.ac.rs: > CPU op-mode(s): 32-bit, 64-bit Model name: Pentium(R) Dual-Core CPU T4500 That processor can run amd64 Debian, so install that architecture.
[toc] | [prev] | [next] | [standalone]
| From | skoric@uns.ac.rs |
|---|---|
| Date | 2024-02-01 18:10 +0100 |
| Subject | Re: Wine in bullseye, which way to go? |
| Message-ID | <I2IJA-777a-15@gated-at.bofh.it> |
| In reply to | #266840 |
> Am 01.02.2024 schrieb skoric@uns.ac.rs: > >> CPU op-mode(s): 32-bit, 64-bit > Model name: Pentium(R) Dual-Core CPU T4500 > > That processor can run amd64 Debian, so install that architecture. > > I am not sure what do you mean by "install that architecture". I have been using i386 versions of Debian, and I do not plan to reinstall it now just because the CPU may allow that. So instead, I ask whether it was expected and properly when Synaptic installed lots of 64-bit stuff during Wine installation from repo. Was it ok or not? Or shall I remove it and follow instructions from WineHQ website?
[toc] | [prev] | [next] | [standalone]
| From | Marco Moock <mm@dorfdsl.de> |
|---|---|
| Date | 2024-02-02 21:00 +0100 |
| Subject | Re: Wine in bullseye, which way to go? |
| Message-ID | <I37RE-7qX5-15@gated-at.bofh.it> |
| In reply to | #266844 |
Am 01.02.2024 um 18:03:47 Uhr schrieb skoric@uns.ac.rs: > I am not sure what do you mean by "install that architecture". I have > been using i386 versions of Debian, and I do not plan to reinstall it > now just because the CPU may allow that. So instead, I ask whether it > was expected and properly when Synaptic installed lots of 64-bit > stuff during Wine installation from repo. Was it ok or not? Or shall > I remove it and follow instructions from WineHQ website? According to documentation I found in the internet, it is possible to upgrade a Debian system to the amd64 architecture. Maybe do that, but do a full backup before. i386 is dead for Debian, the next release won't be available for i386. As long as you have a i386 kernel, you can't use amd64 software on it. -- Gruß Marco Spam und Werbung bitte an ichschickereklame@cartoonies.org
[toc] | [prev] | [next] | [standalone]
| From | Greg Wooledge <greg@wooledge.org> |
|---|---|
| Date | 2024-02-02 21:20 +0100 |
| Subject | Re: Wine in bullseye, which way to go? |
| Message-ID | <I38aZ-7riC-1@gated-at.bofh.it> |
| In reply to | #266889 |
On Fri, Feb 02, 2024 at 08:59:18PM +0100, Marco Moock wrote: > According to documentation I found in the internet, it is possible to > upgrade a Debian system to the amd64 architecture. That isn't an upgrade, and it isn't a supported operation. Some people have *done* it, but it's very much at-your-own-risk. > Maybe do that, but do a full backup before. I wouldn't recommend it, certainly not for someone who's operating with less than a full understanding of the situation. > i386 is dead for Debian, the next release won't be available for i386. It's dying, I would say. Not all the way dead just yet. The next release will not offer an *installer* for i386, but upgrades from Debian 12 i386 to Debian 13 i386 might continue to work. That bears its own risks. Support for i386 is likely to be less than full. Things will probably start breaking and not getting fixed, more and more often as the years roll on, until it's officially declared dead. > As long as you have a i386 kernel, you can't use amd64 software on it. This is true. > Am 01.02.2024 um 18:03:47 Uhr schrieb skoric@uns.ac.rs: > > > I am not sure what do you mean by "install that architecture". I have > > been using i386 versions of Debian, and I do not plan to reinstall it > > now just because the CPU may allow that. At some point, you will have to make a decision. i386 is going to stop being supported sooner or later.
[toc] | [prev] | [next] | [standalone]
| From | Miroslav Skoric <skoric@uns.ac.rs> |
|---|---|
| Date | 2024-02-03 12:40 +0100 |
| Subject | Re: Wine in bullseye, which way to go? |
| Message-ID | <I3mxj-7ApD-11@gated-at.bofh.it> |
| In reply to | #266890 |
On 2/2/24 9:10 PM, Greg Wooledge wrote: >> >>> I am not sure what do you mean by "install that architecture". I have >>> been using i386 versions of Debian, and I do not plan to reinstall it >>> now just because the CPU may allow that. > > At some point, you will have to make a decision. i386 is going to stop > being supported sooner or later. > > Yeah, I know that. Until then I will try to get the most out of this i386 installation as-is. In any case, I managed to get rid of some 250+ amd64 packages that came with pretty useless wine (5.0.3-3) installation from the bullseye repo. After deinstalling wine & related software (in Synaptic), I ran apt-get update, apt-get upgrade, and apt autoremove. It freed cca 1GB. After reboot, all was clean, so I decided to go with wine via WineHQ. I followed their published procedure for bullseye installation, and after a while it ended up with wine version 9, which for now seems functional. Will update the list in days to come ... Misko
[toc] | [prev] | [next] | [standalone]
| From | Marco Moock <mm@dorfdsl.de> |
|---|---|
| Date | 2024-02-03 12:50 +0100 |
| Subject | Re: Wine in bullseye, which way to go? |
| Message-ID | <I3mGZ-7Atn-3@gated-at.bofh.it> |
| In reply to | #266890 |
Am 02.02.2024 um 15:10:32 Uhr schrieb Greg Wooledge: > It's dying, I would say. Not all the way dead just yet. That's why I think it's time to change to amd64 before it is completely dead. > The next release will not offer an *installer* for i386, but upgrades > from Debian 12 i386 to Debian 13 i386 might continue to work. IIRC those packages will still exist for backwards compatibility for certain application, but I read the rumor that no current i386 kernel will be available. -- Gruß Marco Spam und Werbung bitte an ichschickereklame@cartoonies.org
[toc] | [prev] | [next] | [standalone]
| From | Timothy M Butterworth <timothy.m.butterworth@gmail.com> |
|---|---|
| Date | 2024-02-03 04:10 +0100 |
| Subject | Re: Wine in bullseye, which way to go? |
| Message-ID | <I3ezL-7vej-1@gated-at.bofh.it> |
| In reply to | #266889 |
[Multipart message — attachments visible in raw view] — view raw
On Fri, Feb 2, 2024 at 2:59 PM Marco Moock <mm@dorfdsl.de> wrote: > Am 01.02.2024 um 18:03:47 Uhr schrieb skoric@uns.ac.rs: > > > I am not sure what do you mean by "install that architecture". I have > > been using i386 versions of Debian, and I do not plan to reinstall it > > now just because the CPU may allow that. So instead, I ask whether it > > was expected and properly when Synaptic installed lots of 64-bit > > stuff during Wine installation from repo. Was it ok or not? Or shall > > I remove it and follow instructions from WineHQ website? > > According to documentation I found in the internet, it is possible to > upgrade a Debian system to the amd64 architecture. > Maybe do that, but do a full backup before. > > i386 is dead for Debian, the next release won't be available for i386. > It is about time i386 is killed off. 64bit processors have been in production for over 20 years now. I am all for getting the most out of hardware but considering you can get a Intel Core2 Laptop with 4GB of RAM for less that $100 refurbished there is no real reason to keep i386 around. As long as you have a i386 kernel, you can't use amd64 software on it. > > -- > Gruß > Marco > > Spam und Werbung bitte an ichschickereklame@cartoonies.org > > -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄⠀⠀
[toc] | [prev] | [next] | [standalone]
| From | The Wanderer <wanderer@fastmail.fm> |
|---|---|
| Date | 2024-01-30 13:50 +0100 |
| Message-ID | <I1VIR-6Bfi-5@gated-at.bofh.it> |
| In reply to | #266763 |
[Multipart message — attachments visible in raw view] — view raw
On 2024-01-30 at 07:19, Miroslav Skoric wrote: > Hi, > > I [partially] upgraded buster to bullseye according to official "Release > Notes for Debian 11 (bullseye), 32-bit PC" (October 4, 2023). I did it > in two sessions as suggested: > > "4.4.4 Minimal system upgrade" (# apt upgrade --without-new-pkgs). That > part performed without any issue, and cat /etc/debian_version reported > 11.8 (previously it was 10.x). > > "4.4.5 Upgrading the system" (# apt full-upgrade) ran also fine until > some 20% or so, and then failed when handled marco-common package. Here > are the few last lines of that session: > > ... > Preparing to unpack .../6-mate-settings-daemon-common_1.24.1-1_all.deb ... > Unpacking mate-settings-daemon-common (1.24.1-1) over (1.20.4-1) ... > Preparing to unpack .../7-marco_1.24.1-3_i386.deb ... > Unpacking marco (1.24.1-3) over (1.20.3-1) ... > Preparing to unpack .../8-marco-common_1.24.1-3_all.deb ... > Unpacking marco-common (1.24.1-3) over (1.20.3-1) ... > .[1mdpkg:.[0m error processing archive > /tmp/apt-dpkg-install-S65GMD/8-marco-common_1.24.1-3_all.deb (--unpack): > trying to overwrite > '/usr/share/themes/Gorilla/metacity-1/metacity-theme-1.xml', which is > also in package gnome-themes-more 0.9.0.deb0.8 Where do you get 'gnome-themes-more' from? At least as far as I can tell without more digging, it isn't in current stable or testing. It *is* available on archive.debian.org and snapshot.debian.org, with that version number, but based on the timestamps it doesn't seem to have been updated since 2010. > Errors were encountered while processing: > /tmp/apt-dpkg-install-S65GMD/8-marco-common_1.24.1-3_all.deb > > > A repeated # apt full-upgrade returned a list of unmet dependencies, > including this one: > > marco : Depends: marco-common (= 1.24.1-3) but 1.20.3-1 is installed > > At the end of the list it suggested: Try 'apt --fix-broken install' with > no packages (or specify a solution). I tried it and it seemed as if it > tried to process again the above lines (unpacking, preparing), to no avail. > > What can I try to resolve that? After system reboot, I am able to reach > the rescue mode as root and type commands. (Green 'OK' follow all parts > of boot. GUI, startx fail. Shutdown, poweroff run properly.) My first default would be to remove gnome-themes-more (possibly with apt, possibly directly with dpkg), then try the '--fix-broken' step again. Assuming that works, I'd then follow it up by repeating the full-upgrade step just to make sure, and then after that - if I really wanted gnome-themes-more - try to reinstall it (preferably using an updated package, if you can get your hands on one). I suspect that files have been moved between packages since that version was released, and (some of) the files which were previously in gnome-themes-more are now in marco-common. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
[toc] | [prev] | [next] | [standalone]
| From | Miroslav Skoric <skoric@uns.ac.rs> |
|---|---|
| Date | 2024-01-31 00:50 +0100 |
| Message-ID | <I261A-6HsA-7@gated-at.bofh.it> |
| In reply to | #266766 |
On 1/30/24 1:40 PM, The Wanderer wrote: > /tmp/apt-dpkg-install-S65GMD/8-marco-common_1.24.1-3_all.deb (--unpack): >> trying to overwrite >> '/usr/share/themes/Gorilla/metacity-1/metacity-theme-1.xml', which is >> also in package gnome-themes-more 0.9.0.deb0.8 > > Where do you get 'gnome-themes-more' from? At least as far as I can tell > without more digging, it isn't in current stable or testing. > > It *is* available on archive.debian.org and snapshot.debian.org, with > that version number, but based on the timestamps it doesn't seem to have > been updated since 2010. > Dunno ... probably it became orphaned after upgrading from some previous releases. I used apt-forktracer to get rid of some packages before upgrading to bullseye, but many packages were still listed there. I was cautious and did not want to remove all of those just like that ... > > My first default would be to remove gnome-themes-more (possibly with > apt, possibly directly with dpkg), then try the '--fix-broken' step > again. > > Assuming that works, I'd then follow it up by repeating the full-upgrade > step just to make sure, and then after that - if I really wanted > gnome-themes-more - try to reinstall it (preferably using an updated > package, if you can get your hands on one). > Thanks for advice. I tried to remove that package with apt at first, to no avail, but dpkg was successful. Then the '--fix-broken' step and the full-upgrade step performed without errors. Misko
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web