Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #266784
| From | Miroslav Skoric <skoric@uns.ac.rs> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: apt full-upgrade failed at marco-common package |
| Date | 2024-01-31 00:50 +0100 |
| Message-ID | <I261A-6HsA-7@gated-at.bofh.it> (permalink) |
| References | <I1Vpv-6B8E-3@gated-at.bofh.it> <I1VIR-6Bfi-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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
Back to linux.debian.user | Previous | Next — Previous in thread | Find similar | Unroll thread
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
csiph-web