Kodi installation fails

vpincini · 2016-09-25 10:01:55

Hi everyone
I have just installed my laptop with BL and I was installing kodi.

I have backports enabled.

I have tried to install it from the command line (sudo apt-get -t jessie-backports install kodi) and from Synaptics with the same error.

Here is it:
"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:
kodi : Depends: kodi-bin (>= 16.1+dfsg1-1~bpo8+3) but it is not going to be installed
Depends: kodi-bin (< 16.1+dfsg1-1~bpo8+3.1~) but it is not going to be installed
E: Unable to correct problems, you have held broken packages."

Any clue?

Thanks in advance

V.P.

damo · 2016-09-25 10:16:08

Did you update your sources after enabling backports?

PS Would you use [ code ] tags for posting terminal output? It makes it much easier to read

EDIT: A quick google for your error message implies that it is a kodi package bug. I tried installing a specific package version, but then ran into further libav dependency issues.

$ sudo apt-get install  -t jessie-backports kodi=16.1+dfsg1-1~bpo8+3 kodi-bin=16.1+dfsg1-1~bpo8+3

EDIT 2: I think kodi is available from deb-multimedia, which should resolve the lib package problems. But BE WARNED that deb-multimedia maywill cause problems on your system further down the line. How about xbmc instead of kodi?

Last edited by damo (2016-09-25 10:30:29)

vpincini · 2016-09-25 12:55:51

Hi Damo, thanks for anserwering

Did you update your sources after enabling backports?

yes I did

PS Would you use [ code ] tags for posting terminal output? It makes it much easier to read

you are right, my bad, I apologize

EDIT: A quick google for your error message implies that it is a kodi package bug. I tried installing a specific package version, but then ran into further libav dependency issues.

Same thing I have found but it doesnot sound right.. I mean.. I have installed a laptop yesterday with a standard Debian 8.6 and I was able to install kodi from backports without any problem

EDIT 2: I think kodi is available from deb-multimedia, which should resolve the lib package problems. But BE WARNED that deb-multimedia maywill cause problems on your system further down the line. How about xbmc instead of kodi?

Use deb-multimedia in one of my system is not an option.. I don't trust them at all.. sorry
Xbmc is the older version of kodi.. I never take in consideration to install something when I now is outdated

Thanks

V.P.

Head_on_a_Stick · 2016-09-25 13:34:05

The libx265-79 package has not yet been backported and is needed for Kodi.

I'm sure if you wait a bit the backporting team will get it packaged

I would not advise using deb-multimedia.

Bearded_Blunder · 2016-09-25 13:41:03

vpincini wrote:

I never take in consideration to install something when I now is outdated

In a Debian stable based distro, you'll be spending an awful long time upgrading just about every package on the system then. The whole POINT of stable is it's "outdated" stuff that's been tested and pounded on by the whole world for some time. I prefer to think of it as "well tested" rather than "outdated" myself.

vpincini · 2016-09-25 13:59:22

You are totally right: run Debian stable is choosing outdated because stable and tested insted of last version.

But this is not the case..
Xbmc is part of the main archive and Kodi is part of the backports archive.
Since Debian 7 backports are Officially part of the Debian project aka "you shoul condider as good as main".
So I have both the old Xbmc and the backported Kodi available at the same time delivered with the usual Debian quality.
Why should I choose the most outdated one?
On top of this there is the fact I have installed it yesterday from backports on a standard Debian and it has worked.

Probably I sound polemic but I assure you I am not.. I am really puzzled

Thanks

V.P.

Head_on_a_Stick · 2016-09-25 14:02:13

vpincini wrote:

On top of this there is the fact I have installed it yesterday from backports on a standard Debian and it has worked.

The package situation has changed since yesterday, check the dependency chain for the backported kodi package and you will see that libx265-79 is marked as "not available" in jessie-backports and thus kodi is not currently installable in any Debian stable-based system.

As I said, give it a day or two -- the package maintainers are all volunteers and may have actual lives to be getting on with.

Bearded_Blunder · 2016-09-25 14:28:41

vpincini wrote:

Since Debian 7 backports are Officially part of the Debian project aka "you shoul condider as good as main".
So I have both the old Xbmc and the backported Kodi available at the same time delivered with the usual Debian quality.
Why should I choose the most outdated one?

backports.debian.org wrote:

Backports cannot be tested as extensively as Debian stable, and backports are provided on an as-is basis, with risk of incompatibilities with other components in Debian stable. Use with care!
It is therefore recommended to only select single backported packages that fit your needs, and not use all available backports.

Just saying, particularly the "not use all available backports" part & you've just run into an example of why using backported pagages "just because they're newer" is discouraged as general practice. HoaS has given you the reason for the current short-term breakage, and it will no doubt be fixed by waiting as he suggests.

vpincini wrote:

Why should I choose the most outdated one?

You don't have to, but choosing backports puts you at higher risk of borkage, you end up on no-mans-land between stable and testing, not saying never do it, I do myself occasionally when I need some feature an older version of something simply doesn't offer, the rest of the time I "choose the most outdated/more tested version".

HoaS wrote:

libx265-79 is marked as "not available" in jessie-backports and thus kodi is not currently installable in any Debian stable-based system.

^ unless you're up for backporting libx265-79 yourself, in order to do it, sounds like way more trouble and effort than waiting till the maintainers get time though.

stevep · 2016-09-25 23:43:10

It's quite easy to backport the 1.9 version of x265, which is what results in libx265-79, but you'll have to get the source or binaries from snapshots.debian.org, or from the MX 15 repo, since upstream Debian and jessie-backports went to the 2.0 version, which resulted in libx265-84--and the breaking of everything that depended on the -79, including the bottom of the Jenga stack: ffmpeg. But they can often be very slow in fixing something like this--I'll report it on the mailing list if nobody else has. Edit: ffmpeg was just reported as broken, but not everything that depended on it, so I mentioned that.

So everything needs to be rebuilt in jessie-backports that builds against the real ffmpeg libav* libraries; then they'll depend on the new -84 version. That has to be done manually, I think, or at least rebuilds have to be triggered somehow. Stuff like this is why we decided against including the backports repo for the MX 15 distro.

Anyway, I just reupped the jessie-backports Kodi in my own little multimedia repository: http://forums.debian.net/viewtopic.php?f=6&t=127574 I'm confident my repo won't break anything like deb-multimedia can.

I, like jessie-backports, also just added the newer x265. However, this is like pulling out the bottom of the Jenga stack, but the OBS automatically rebuilds everything for me that broke. So it'll go x265--> ffmpeg 3.1.3--> Kodi (hopefully), but will take a bit of time, since everything else in my repo that broke is also rebuilding at the same time--even the GIMP 2.9.5 packages I have in there. So wait an hour or two, and hopefully you can install Kodi 16.1 from there. If it fails, I'll revert to the older x265 and let everything rebuild.

If you want to check on the progress, you can look but not touch on the packages here: https://build.opensuse.org/project/show … evepassert

Edit: 32-bit Kodi is done, the 64-bit should be finished shortly. The newer x265 seems to have fit in smoothly.

Last edited by stevep (2016-09-26 01:08:35)

brontosaurusrex · 2016-09-26 06:02:06

Any special reasons why kodi would need latest x265 encoder? Just curious.

stevep · 2016-09-26 17:44:15

It doesn't really need the encoder, but it's built against the "real" ffmpeg libraries that use the external versioned libx265-XX library, so it ends up being a dependency anyway. You could get around this type of thing by building ffmpeg with libx265 and libx264 disabled, which is not a really popular option, or building Kodi to use its internal ffmpeg libraries, which goes against Debian policy (use system libs if at all possible)

FFmpeg uses its own built-in hevc (h.265) decoder for playback, and the external libx265 for encoding.

Kodi is being fixed in backports, due to this BL thread: https://lists.debian.org/debian-backpor … 00069.html

Last edited by stevep (2016-09-26 18:02:37)

#1 2016-09-25 10:01:55

Kodi installation fails

#2 2016-09-25 10:16:08

Re: Kodi installation fails

#3 2016-09-25 12:55:51

Re: Kodi installation fails

#4 2016-09-25 13:34:05

Re: Kodi installation fails

#5 2016-09-25 13:41:03

Re: Kodi installation fails

#6 2016-09-25 13:59:22

Re: Kodi installation fails

#7 2016-09-25 14:02:13

Re: Kodi installation fails

#8 2016-09-25 14:28:41

Re: Kodi installation fails

#9 2016-09-25 23:43:10

Re: Kodi installation fails

#10 2016-09-26 06:02:06

Re: Kodi installation fails

#11 2016-09-26 17:44:15

Re: Kodi installation fails

Board footer