DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
$ cat /etc/issue
Welcome to antiX. Powered by Debian Testing.
$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux jessie/sid"
NAME="Debian GNU/Linux"
ID=debian
ANSI_COLOR="1;31"
HOME_URL="http://www.debian.org/"
SUPPORT_URL="http://www.debian.org/support/"
BUG_REPORT_URL="http://bugs.debian.org/"
$ uname -a
Linux biker 3.7.10-antix.2-amd64-smp #1 SMP Sun Mar 3 19:33:00 EET 2013 x86_64 GNU/Linux
# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
libwayland0
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
I'm willing to believe that if you use aptitude and perform the commands that you state it may prevent auto-removal. Using apt-get, however, installing packages manually has no effect on their removal, or not, by dist-upgrading.
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
Posts: 7,680
Rep:
That's the version I'm trying to install -- it was removed during a dist-upgrade. I'm not sure whether the dependency issues are necessarily linked to mplayer -- they're libgl1-mesa libraries that are broken so I can't use apt-get to install anything right now on my desktop. I reinstalled mplayer on my netbook the day after it was autoremoved though.
That version of mplayer is from deb-multimedia. From experience, that repo can play havoc with distribution upgrades and it's better to just get rid of or replace everything it installs from the standard repos, upgrade and then reinstall it when you're done.
What you're experiencing is part and parcel of running unstable. If you started running it during the freeze, you were really running testing with a few newer packages... It might be better to stick with testing or a mixed testing/unstable system if you want some kind of stability.
You mesa issues may also be related to deb-multimedia, I'm sure that he packages some newer xorg and mesa libs.
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
Posts: 7,680
Rep:
Some of my packages have been updated to 8.0.5-4+b1 I went into Synaptic to see whether I can fix things as I sometimes have more luck than with apt, however it seems that some of the packages that need upgrading are broken.
Code:
E: /var/cache/apt/archives/libgl1-mesa-dri_8.0.5-4+b1_amd64.deb: trying to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from other instances of package libgl1-mesa-dri:amd64
E: /var/cache/apt/archives/libgl1-mesa-glx_8.0.5-4+b1_i386.deb: trying to overwrite shared '/usr/share/doc/libgl1-mesa-glx/changelog.Debian.gz', which is different from other instances of package libgl1-mesa-glx:i386
E: /var/cache/apt/archives/libglapi-mesa_8.0.5-4+b1_amd64.deb: trying to overwrite shared '/usr/share/doc/libglapi-mesa/changelog.Debian.gz', which is different from other instances of package libglapi-mesa:amd64
I've found what works best for me is to go from SID to testing a few days before the release of a new version, then stay at testing for a couple months before moving back to SID. Rarely do I encounter issues running it this way.
They seem to be from the main repo not deb-multimedia. I suspect that things will be fixed in a few days -- no point going back to testing when I've had pretty much the same type of issues with that also.
I don't really want to go purging them as it'll remove half my packages so I think I'll leave things as they are for now and only purge if things aren't fixed soon.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.