Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #161910 > unrolled thread

How to get out of a "...but it is not going to be installed"-type situation with apt-get?

Back to article view | Back to linux.debian.user

Contents

  How to get out of a "...but it is not going to be installed"-type  situation with apt-get? Kynn Jones <kynnjo@gmail.com> - 2015-12-19 16:30 +0100
    Re: How to get out of a "...but it is not going to be installed"-type  situation with apt-get? The Wanderer <wanderer@fastmail.fm> - 2015-12-19 17:10 +0100
      Re: How to get out of a "...but it is not going to be installed"-type  situation with apt-get? Kynn Jones <kynnjo@gmail.com> - 2015-12-19 17:30 +0100
    Re: How to get out of a "...but it is not going to be installed"-type  situation with apt-get? Kynn Jones <kynnjo@gmail.com> - 2015-12-19 17:40 +0100
      Re: How to get out of a "...but it is not going to be installed"-type  situation with apt-get? Pascal Hambourg <pascal@plouf.fr.eu.org> - 2015-12-19 17:50 +0100
      Re: How to get out of a "...but it is not going to be installed"-type  situation with apt-get? The Wanderer <wanderer@fastmail.fm> - 2015-12-19 17:50 +0100
        Re: How to get out of a "...but it is not going to be installed"-type  situation with apt-get? Kynn Jones <kynnjo@gmail.com> - 2015-12-19 21:40 +0100

#161910 — How to get out of a "...but it is not going to be installed"-type situation with apt-get?

I apologize for all these apt-related questions.

I have rtfm'd on this ad nauseam.  For years, literally.

Still, I'm routinely rendered utterly helpless by this sort of thing:

    % sudo apt-get -qq update
    % sudo apt-get -qq upgrade
    % sudo apt-get -qq dist-upgrade
    % sudo apt-get install ffmpeg
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    Some packages could not be installed. This may mean that you have
    requested an impossible situation or if you are using the unstable
    distribution that some required packages have not yet been created
    or been moved out of Incoming.
    The following information may help to resolve the situation:

    The following packages have unmet dependencies:
     ffmpeg : Depends: libavcodec-ffmpeg56 (>= 7:2.7) but it is not
going to be installed or
                       libavcodec-ffmpeg-extra56 (>= 7:2.7) but it is
not going to be installed
              Depends: libavdevice-ffmpeg56 (>= 7:2.6) but it is not
going to be installed
              Depends: libavfilter-ffmpeg5 (>= 7:2.4) but it is not
going to be installed
              Depends: libavformat-ffmpeg56 (>= 7:2.6) but it is not
going to be installed
    E: Unable to correct problems, you have held broken packages.


Where does one begin troubleshooting out such problems?

Thanks in advance for any help.

kj


PS:

    # /etc/apt/apt.conf
    APT::Default-Release "jessie";

    # /etc/apt/preferences
    Package: /^r-/
    Pin: release n=stretch
    Pin-Priority: 995

    # /etc/apt/sources.list
    deb http://http.us.debian.org/debian jessie main contrib non-free
    deb http://http.us.debian.org/debian jessie-updates main contrib
    deb http://security.debian.org jessie/updates main contrib non-free
    deb-src http://http.us.debian.org/debian jessie main contrib
    deb-src http://http.us.debian.org/debian jessie-updates main contrib
    deb-src http://security.debian.org jessie/updates main contrib non-free

    deb http://http.us.debian.org/debian stretch main contrib non-free
    deb-src http://http.us.debian.org/debian stretch main contrib

    deb http://download.videolan.org/pub/debian/stable /  # needed for
libdvdcss2 (see http://www.videolan.org/developers/libdvdcss.html)

I have made no changes to my /etc/apt/apt.conf.d/,
/etc/apt/preferences.d, and /etc/apt/sources.list.d/ that I'm aware
of.  The last two of these directories are empty.  The first one
contains

    % ls -l /etc/apt/apt.conf.d
    -rw-rw-r-- 1 root root   82 Nov 22 13:45 00CDMountPoint
    -rw-rw-r-- 1 root root   40 Nov 22 13:45 00trustcdrom
    -rw-rw-r-- 1 root root  643 Nov 22 13:45 01autoremove
    -rw-r--r-- 1 root root  981 Dec 19 09:44 01autoremove-kernels
    -rw-rw-r-- 1 root root  243 Nov 22 13:45 20dbus
    -rw-rw-r-- 1 root root  141 Nov 22 13:45 20listchanges
    -rw-rw-r-- 1 root root 1040 Nov 22 13:45 20packagekit
    -rw-rw-r-- 1 root root 3945 Nov 22 13:45 50unattended-upgrades
    -rw-rw-r-- 1 root root  182 Nov 22 13:45 70debconf

[toc] | [next] | [standalone]

#161912

[Multipart message — attachments visible in raw view] — view raw

On 2015-12-19 at 10:24, Kynn Jones wrote:

> I apologize for all these apt-related questions.
> 
> I have rtfm'd on this ad nauseam.  For years, literally.
> 
> Still, I'm routinely rendered utterly helpless by this sort of thing:
> 
>     % sudo apt-get -qq update
>     % sudo apt-get -qq upgrade
>     % sudo apt-get -qq dist-upgrade
>     % sudo apt-get install ffmpeg
>     Reading package lists... Done
>     Building dependency tree
>     Reading state information... Done
>     Some packages could not be installed. This may mean that you have
>     requested an impossible situation or if you are using the unstable
>     distribution that some required packages have not yet been created
>     or been moved out of Incoming.
>     The following information may help to resolve the situation:
> 
>     The following packages have unmet dependencies:
>      ffmpeg : Depends: libavcodec-ffmpeg56 (>= 7:2.7) but it is not
> going to be installed or
>                        libavcodec-ffmpeg-extra56 (>= 7:2.7) but it is
> not going to be installed
>               Depends: libavdevice-ffmpeg56 (>= 7:2.6) but it is not
> going to be installed
>               Depends: libavfilter-ffmpeg5 (>= 7:2.4) but it is not
> going to be installed
>               Depends: libavformat-ffmpeg56 (>= 7:2.6) but it is not
> going to be installed
>     E: Unable to correct problems, you have held broken packages.
> 
> 
> Where does one begin troubleshooting out such problems?

Assuming you don't actually have any package holds (check 'apt-mark
showhold' to verify that), and since you've already confirmed that you
don't have any seemingly-applicable pins:

Append one or more of the listed packages to the 'apt-get install'
command line, and see what you get; repeat as necessary. (You may well
eventually end up having to specify all of them.)

In the end, you will probably wind up with an error stating that one
package's dependencies conflict with those of another; this most
commonly happens with versioned dependencies. From there, you can
specify install / remove actions for those two packages explicitly, in
order to break the dependency-resolution deadlock.

If you're lucky, you can often shortcut this by looking at the
dependency / conflict lists of the named packages directly, via
'apt-cache show' or similar.


Alternatively, if you know (or are willing to learn) how to use
aptitude's curses interface, it can do some of the work for you. Run
just 'aptitude' with no arguments, and refer to the program's internal
help documentation as needed; I'm only loosely familiar with it myself,
so I can't really guide you very well, but I've used it a few times to
track down and resolve such issues in the past.

There's a relatively steep learning curve to the aptitude curses
interface, or so it seems to me, but it does seem to be fairly powerful
once you've gotten your head far enough around it.

-- 
   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]

#161914

On Sat, Dec 19, 2015 at 11:00 AM, The Wanderer <wanderer@fastmail.fm> wrote:
> Assuming you don't actually have any package holds (check 'apt-mark
> showhold' to verify that), and since you've already confirmed that you
> don't have any seemingly-applicable pins:
>
> Append one or more of the listed packages to the 'apt-get install'
> command line, and see what you get; repeat as necessary. (You may well
> eventually end up having to specify all of them.)
>
> In the end, you will probably wind up with an error stating that one
> package's dependencies conflict with those of another; this most
> commonly happens with versioned dependencies. From there, you can
> specify install / remove actions for those two packages explicitly, in
> order to break the dependency-resolution deadlock.
>
> If you're lucky, you can often shortcut this by looking at the
> dependency / conflict lists of the named packages directly, via
> 'apt-cache show' or similar.
>
>
> Alternatively, if you know (or are willing to learn) how to use
> aptitude's curses interface, it can do some of the work for you. Run
> just 'aptitude' with no arguments, and refer to the program's internal
> help documentation as needed; I'm only loosely familiar with it myself,
> so I can't really guide you very well, but I've used it a few times to
> track down and resolve such issues in the past.
>
> There's a relatively steep learning curve to the aptitude curses
> interface, or so it seems to me, but it does seem to be fairly powerful
> once you've gotten your head far enough around it.


Thanks for the detailed response.  It gives me much to work with.

kj

[toc] | [prev] | [next] | [standalone]

#161916

On Sat, Dec 19, 2015 at 10:24 AM, Kynn Jones <kynnjo@gmail.com> wrote:
> I apologize for all these apt-related questions.
>
> I have rtfm'd on this ad nauseam.  For years, literally.
>
> Still, I'm routinely rendered utterly helpless by this sort of thing:
>
>     % sudo apt-get -qq update
>     % sudo apt-get -qq upgrade
>     % sudo apt-get -qq dist-upgrade
>     % sudo apt-get install ffmpeg
>     Reading package lists... Done
>     Building dependency tree
>     Reading state information... Done
>     Some packages could not be installed. This may mean that you have
>     requested an impossible situation or if you are using the unstable
>     distribution that some required packages have not yet been created
>     or been moved out of Incoming.
>     The following information may help to resolve the situation:
>
>     The following packages have unmet dependencies:
>      ffmpeg : Depends: libavcodec-ffmpeg56 (>= 7:2.7) but it is not
> going to be installed or
>                        libavcodec-ffmpeg-extra56 (>= 7:2.7) but it is
> not going to be installed
>               Depends: libavdevice-ffmpeg56 (>= 7:2.6) but it is not
> going to be installed
>               Depends: libavfilter-ffmpeg5 (>= 7:2.4) but it is not
> going to be installed
>               Depends: libavformat-ffmpeg56 (>= 7:2.6) but it is not
> going to be installed
>     E: Unable to correct problems, you have held broken packages.
>
>
> Where does one begin troubleshooting out such problems?
>
> Thanks in advance for any help.
>
> kj
>
>
> PS:
>
>     # /etc/apt/apt.conf
>     APT::Default-Release "jessie";
>
>     # /etc/apt/preferences
>     Package: /^r-/
>     Pin: release n=stretch
>     Pin-Priority: 995
>
>     # /etc/apt/sources.list
>     deb http://http.us.debian.org/debian jessie main contrib non-free
>     deb http://http.us.debian.org/debian jessie-updates main contrib
>     deb http://security.debian.org jessie/updates main contrib non-free
>     deb-src http://http.us.debian.org/debian jessie main contrib
>     deb-src http://http.us.debian.org/debian jessie-updates main contrib
>     deb-src http://security.debian.org jessie/updates main contrib non-free
>
>     deb http://http.us.debian.org/debian stretch main contrib non-free
>     deb-src http://http.us.debian.org/debian stretch main contrib
>
>     deb http://download.videolan.org/pub/debian/stable /  # needed for
> libdvdcss2 (see http://www.videolan.org/developers/libdvdcss.html)
>
> I have made no changes to my /etc/apt/apt.conf.d/,
> /etc/apt/preferences.d, and /etc/apt/sources.list.d/ that I'm aware
> of.  The last two of these directories are empty.  The first one
> contains
>
>     % ls -l /etc/apt/apt.conf.d
>     -rw-rw-r-- 1 root root   82 Nov 22 13:45 00CDMountPoint
>     -rw-rw-r-- 1 root root   40 Nov 22 13:45 00trustcdrom
>     -rw-rw-r-- 1 root root  643 Nov 22 13:45 01autoremove
>     -rw-r--r-- 1 root root  981 Dec 19 09:44 01autoremove-kernels
>     -rw-rw-r-- 1 root root  243 Nov 22 13:45 20dbus
>     -rw-rw-r-- 1 root root  141 Nov 22 13:45 20listchanges
>     -rw-rw-r-- 1 root root 1040 Nov 22 13:45 20packagekit
>     -rw-rw-r-- 1 root root 3945 Nov 22 13:45 50unattended-upgrades
>     -rw-rw-r-- 1 root root  182 Nov 22 13:45 70debconf



An additional detail I noticed after I posted the message above:

    % apt-cache policy ffmpeg
    ffmpeg:
      Installed: (none)
      Candidate: 7:2.8.3-1
      Version table:
         7:2.8.3-1 0
            500 http://http.us.debian.org/debian/ stretch/main amd64 Packages


I don't understand why the ffmpeg version from stretch comes out as
the best (and only remaining) candidate.

How can I find out why the ffmpeg version from jessie (whatever that
is) is not a candidate?


TIA,

kj

[toc] | [prev] | [next] | [standalone]

#161917

Kynn Jones a écrit :
> 
> I don't understand why the ffmpeg version from stretch comes out as
> the best (and only remaining) candidate.
> 
> How can I find out why the ffmpeg version from jessie (whatever that
> is) is not a candidate?

It appears that there is no ffmpeg package in Jessie.

[toc] | [prev] | [next] | [standalone]

#161918

[Multipart message — attachments visible in raw view] — view raw

On 2015-12-19 at 11:38, Kynn Jones wrote:

> An additional detail I noticed after I posted the message above:
> 
>     % apt-cache policy ffmpeg
>     ffmpeg:
>       Installed: (none)
>       Candidate: 7:2.8.3-1
>       Version table:
>          7:2.8.3-1 0
>             500 http://http.us.debian.org/debian/ stretch/main amd64 Packages
> 
> 
> I don't understand why the ffmpeg version from stretch comes out as
> the best (and only remaining) candidate.
> 
> How can I find out why the ffmpeg version from jessie (whatever that
> is) is not a candidate?

If you look at the package listing for ffmpeg on packages.debian.org:

https://packages.debian.org/search?keywords=ffmpeg

you will see that there is no ffmpeg package listed for jessie. (There's
one for jessie-backports, but that requires a separate sources.list entry.)

If I remember my timeline of events correctly, this is because there was
no ffmpeg package in jessie; the libav fork was present in its place. (I
thought libav had still been providing a ffmpeg dummy package, but I may
be remembering wrong.)

When ffmpeg itself was packaged for Debian again, apparently it didn't
make it in in time to be included in the jessie release, but it did get
added to stretch after jessie was released. (If I remember and interpret
matters correctly, libav has been removed from stretch.)

If you want the jessie-era libav* packages, try installing libav-tools
instead of ffmpeg. You won't get exactly the same commands or
functionality, but most of it should be similar enough for many purposes.

-- 
   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]

#161921

On Sat, Dec 19, 2015 at 11:47 AM, The Wanderer <wanderer@fastmail.fm> wrote:
> If I remember my timeline of events correctly, this is because there was
> no ffmpeg package in jessie; the libav fork was present in its place. (I
> thought libav had still been providing a ffmpeg dummy package, but I may
> be remembering wrong.)
>
> When ffmpeg itself was packaged for Debian again, apparently it didn't
> make it in in time to be included in the jessie release, but it did get
> added to stretch after jessie was released. (If I remember and interpret
> matters correctly, libav has been removed from stretch.)
>
> If you want the jessie-era libav* packages, try installing libav-tools
> instead of ffmpeg. You won't get exactly the same commands or
> functionality, but most of it should be similar enough for many purposes.


OK, it looks like I stepped into a truly crazy one today...

Thanks for the info!

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web