• TwitterFacebookGoogle PlusLinkedInRSS FeedEmail

Install Mplayer Debian Wheezy Packages

19.09.2019 

Contrib Packages in this area are freely licensed by the copyright holder but depend on other software that is not free. Non-Free Packages in this area have some onerous license condition restricting use or redistribution of the software.

  1. Jessie

Note that same packages might appear in several distributions, but with different version numbers. This is the latest official release of the Debian distribution. This is stable and well tested software, which changes only if major security or usability fixes are incorporated. See the for more information. This area contains packages that are intended to become part of the next stable distribution. There are strict criteria a package in unstable (see below) must obey before it can be added to testing. Note that testing does not get the timely security updates.

Media players available in Debian such as VLC and Mplayer make use of. You may need to install a few extra packages. How to install.

Debian

See the for more information. This area contains the most recent packages in Debian.

  1. This manual also describes Debian policy as it relates to creating Debian packages. Having a separate package allows one to install the build-essential packages.
  2. Uninstall mplayer. To remove just mplayer package itself from Debian 7 (Wheezy) execute on terminal: sudo apt-get remove mplayer Uninstall mplayer and it's dependent.

Once a package has met our criterion for stability and quality of packaging, it will be included in testing. Unstable is also not supported.

Packages in unstable are the least tested and may contain problems severe enough to affect the stability of your system. Serial port monitor. Only experienced users should consider using this distribution. See the for more information.

Install Mplayer Debian Wheezy Packages

I want to install a single package (and its dependencies, but only to the extent those are not satisfiable in Wheezy) from Debian Jessie onto my Wheezy system, without upgrading 'everything and the kitchen sink' to the Jessie versions. Specifically, I'd like to install, which is available packaged in Jessie but not in Wheezy. Everything I've found indicates that I should add the Jessie repositories to my sources list, set pinning to keep everything at wheezy and only take the single package from jessie, and it'll pretty much just fall into place.

However, it isn't falling into place for me. If I create /etc/apt.d/sources.list.d/jessie.list with the following content: deb ftp://ftp.debian.org/debian/ jessie main deb-src ftp://ftp.debian.org/debian/ jessie main and then create /etc/apt/preferences.d/jessie with: Package:.

Pin: release a=wheezy Pin-Priority: 1001 Package: kpcli Pin: release a=jessie Pin-Priority: 450 and run apt-get -u update followed by apt-get -u install kpcli/jessie, then I expect apt-get to pull in kpcli and maybe a small handful of other packages from Jessie, and leave the remainder of my installed system untouched. (My system is a fully up to date installation of Wheezy.) Alternatively, if I got the pin priority too low, I'd expect it to do nothing. Rather, on my system, apt-get wants to upgrade several hundred packages.

What, exactly, is needed to install just this one single package of a Jessie version while leaving the remainder of my Wheezy system untouched? Note that in this particular case, the software is actually written in Perl so there's no compilation to binary or anything like that involved; however, there is a handful of Perl module dependencies. Hence, one possible alternative would be to install the.deb (downloaded manually) using something that only (1) allows specifying a single, local.deb archive that is to be installed, like dpkg -i, and (2) handles dependencies in an intelligent way, which plain dpkg -i doesn't.

However, for all the searching I've done on several occasions and failed to come up with a simple-to-follow guide for how to do this, a generic solution (one that works for binary, compiled packages as well) would be great. For each entry (stable, testing, unstable) you have pin-priority 500. You shouldn't use pin 1000. I use 1001 only when I want to downgrade something. I have testing+sid+experimental entries specified in /etc/apt/sources.list and the following /etc/apt/preferences file: Package:.

Pin: release o=Debian,a=testing Pin-Priority: 900 Package:. Pin: release o=Debian,a=experimental Pin-Priority: 130 The value 500 is default for unstable. So, let's try to check iceweasel: # apt-cache policy iceweasel iceweasel: Installed: (none) Candidate: 17.0.10esr-1deb7u1 Version table: 26.0-1 0 130 experimental/main amd64 Packages 24.2.0esr-1 0 500 sid/main amd64 Packages 17.0.10esr-1deb7u1 0 900 testing/main amd64 Packages So, if I tried to install iceweasel, it would be downloaded from the testing branch because it has the highest priority. Try to change the priorities to: Package:.

Pin: release a=wheezy Pin-Priority: 900 Package: kpcli Pin: release a=jessie Pin-Priority: 910. There's actually a way to do it without using pinning / priorities at all. Instead, you can specify what's the default release you'll install packages from, which will then be used unless otherwise specified by using the target release parameter. This works the same way if you only want to install selected packages from e.g. I'll show this for installing packages from Stretch into Jessie, as those are the current stable / testing, but it works the same way for installing Jessie packages in Wheezy like it was originally asked. First, add stretch as repository, e.g. In /etc/apt/sources.list.d/stretch.list: deb stretch main Then, to set the default release, create a file like /etc/apt/apt.conf.d/default-release containing: APT::Default-Release 'jessie'; (In Wheezy, I think apt.conf.d didn't exist and you'd need to put that snippet in /etc/apt/apt.conf).

Then, installing a package from testing is as simple as aptitude -t stretch install kpcli without you needing to worry about pinning priorities. Note: @amc pointed out in the comments that if you use apt instead of aptitude, you have to use 'stable' as Default-Release instead of 'jessie'.

Jessie

(Of course, you can use aptitude with that setting as well.).