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

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

kodi and gnome-control-center conflict on bullseye

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

Contents

  kodi and gnome-control-center conflict on bullseye Tristan Miller <psychonaut@nothingisreal.com> - 2021-08-22 17:10 +0200
    Re: kodi and gnome-control-center conflict on bullseye The Wanderer <wanderer@fastmail.fm> - 2021-08-22 17:20 +0200
      Re: kodi and gnome-control-center conflict on bullseye Tristan Miller <psychonaut@nothingisreal.com> - 2021-08-22 18:00 +0200
        Re: kodi and gnome-control-center conflict on bullseye The Wanderer <wanderer@fastmail.fm> - 2021-08-22 18:10 +0200
          Re: kodi and gnome-control-center conflict on bullseye Tristan Miller <psychonaut@nothingisreal.com> - 2021-08-22 19:00 +0200
            Re: kodi and gnome-control-center conflict on bullseye The Wanderer <wanderer@fastmail.fm> - 2021-08-22 19:10 +0200
              Re: kodi and gnome-control-center conflict on bullseye Tristan Miller <psychonaut@nothingisreal.com> - 2021-08-22 20:00 +0200
              Manual vs Auto-Install in APT[ was : kodi and gnome-control-center  conflict on bullseye] Polyna-Maude Racicot-Summerside <debian@polynamaude.com> - 2021-08-22 20:10 +0200
        Re: kodi and gnome-control-center conflict on bullseye Greg Wooledge <greg@wooledge.org> - 2021-08-22 18:10 +0200
          Re: kodi and gnome-control-center conflict on bullseye Greg Wooledge <greg@wooledge.org> - 2021-08-22 18:10 +0200
          Re: kodi and gnome-control-center conflict on bullseye Tristan Miller <psychonaut@nothingisreal.com> - 2021-08-22 19:00 +0200

#239182 — kodi and gnome-control-center conflict on bullseye

Dear all,

On my bullseye system, it doesn't seem to be possible to install both 
kodi and gnome-control-center as they conflict with each other.  (See 
below for what happens when I've got kodi installed and then try to 
install gnome-control-center.)

Is this a known issue that affects others, or have I somehow borked my 
system configuration?  If the latter, help in diagnosing the problem 
would be appreciated.  In my /etc/apt/sources.list I have only the 
following three lines:

deb http://deb.debian.org/debian/ bullseye main contrib non-free
deb-src http://deb.debian.org/debian/ bullseye main contrib non-free
deb http://security.debian.org bullseye-security main contrib non-free

Regards,
Tristan


# apt install gnome-control-center
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer 
required:
   fonts-noto-hinted fonts-roboto-hinted fonts-roboto-unhinted 
javascript-common kodi-data
   kodi-visualization-shadertoy-data libaribb24-0 libcddb2 libcrossguid0 
libdouble-conversion3 libdvbpsi10 libebml5
   libenca0 libfmt7 libfstrcmp0 libimagequant0 libiso9660-11 libixml10 
libjs-iscroll libjs-jquery libkissfft-float131
   libmad0 libmatroska7 libmd4c0 libmicrohttpd12 libmng1 libmysofa1 
libnorm1 libopenmpt-modplug1 libpgm-5.3-0
   libplacebo72 libpocketsphinx3 libpostproc55 libprotobuf-lite23 
libqt5core5a libqt5dbus5 libqt5gui5 libqt5network5
   libqt5svg5 libqt5widgets5 libqt5x11extras5 librabbitmq4 
libresid-builder0c2a librubberband2 libsdl-image1.2
   libshairplay0 libsidplay2 libspatialaudio0 libsphinxbase3 
libssh-gcrypt-4 libtinyxml2.6.2v5 libupnp13 libva-wayland2
   libvidstab1.1 libvorbisidec1 libwayland-client++0 
libwayland-cursor++0 libwayland-egl++0 libwebm1 libxcb-xinerama0
   libxcb-xinput0 libzimg2 libzmq5 pocketsphinx-en-us python3-olefile 
python3-pil python3-pycryptodome vlc-bin vlc-data
   vlc-plugin-qt vlc-plugin-video-output
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
   apg cheese-common gir1.2-malcontent-0 gnome-control-center-data 
gstreamer1.0-plugins-bad libcheese-gtk25 libcheese8
   libcolord-gtk1 libde265-0 libflatpak0 libfluidsynth2 
libgupnp-igd-1.0-4 libinstpatch-1.0-2 libltc11
   libmalcontent-ui-0-0 libmjpegutils-2.1-0 libmms0 libmodplug1 
libmpeg2encpp-2.1-0 libmplex2-2.1-0 libnice10
   libnss-myhostname libofa0 libopenni2-0 libostree-1-1 libsbc1 
libsoundtouch1 libspandsp2 libsrt1.4-gnutls libsrtp2-1
   libvo-aacenc0 libvo-amrwbenc0 libwebrtc-audio-processing1 
libwildmidi2 libzbar0 malcontent malcontent-gui realmd
   timgm6mb-soundfont
Suggested packages:
   libcanberra-gtk-module frei0r-plugins libwildmidi-config 
fluid-soundfont-gm
Recommended packages:
   libcanberra-pulse pulseaudio-module-bluetooth
The following packages will be REMOVED:
   gstreamer1.0-libav kodi kodi-bin kodi-inputstream-adaptive 
kodi-visualization-fishbmc kodi-visualization-pictureit
   kodi-visualization-shadertoy kodi-visualization-spectrum 
kodi-visualization-waveform libavfilter7 libavformat58
   libsrt1-gnutls mplayer vlc vlc-plugin-base
The following NEW packages will be installed:
   apg cheese-common gir1.2-malcontent-0 gnome-control-center 
gnome-control-center-data gstreamer1.0-plugins-bad
   libcheese-gtk25 libcheese8 libcolord-gtk1 libde265-0 libflatpak0 
libfluidsynth2 libgupnp-igd-1.0-4 libinstpatch-1.0-2
   libltc11 libmalcontent-ui-0-0 libmjpegutils-2.1-0 libmms0 libmodplug1 
libmpeg2encpp-2.1-0 libmplex2-2.1-0 libnice10
   libnss-myhostname libofa0 libopenni2-0 libostree-1-1 libsbc1 
libsoundtouch1 libspandsp2 libsrt1.4-gnutls libsrtp2-1
   libvo-aacenc0 libvo-amrwbenc0 libwebrtc-audio-processing1 
libwildmidi2 libzbar0 malcontent malcontent-gui realmd
   timgm6mb-soundfont
0 upgraded, 40 newly installed, 15 to remove and 3 not upgraded.
Need to get 7,418 kB/20.0 MB of archives.
After this operation, 7,643 kB disk space will be freed.
Do you want to continue? [Y/n]


-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
                   Tristan Miller
Free Software developer, ferret herder, logologist
              https://logological.org/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

[toc] | [next] | [standalone]

#239183

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

On 2021-08-22 at 10:46, Tristan Miller wrote:

> Dear all,
> 
> On my bullseye system, it doesn't seem to be possible to install both 
> kodi and gnome-control-center as they conflict with each other.  (See 
> below for what happens when I've got kodi installed and then try to 
> install gnome-control-center.)

> # apt install gnome-control-center

> The following packages will be REMOVED:
>    gstreamer1.0-libav kodi kodi-bin kodi-inputstream-adaptive 

I don't have either package installed, but if I try to install both in
the same command line, I don't get a failure. As such, I'm guessing this
may just be a dependency-resolver issue.

What happens if you instead run

$ apt install kodi gnome-control-center

? You should either get a success (via different resolution of the
dependencies, which doesn't consider omitting either of the two to be an
acceptable solution) or an error which may help us narrow down the problem.

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

#239186

Greetings.

On 22/08/2021 17.20, The Wanderer wrote:
> On 2021-08-22 at 10:46, Tristan Miller wrote:
>> On my bullseye system, it doesn't seem to be possible to install both
>> kodi and gnome-control-center as they conflict with each other.  (See
>> below for what happens when I've got kodi installed and then try to
>> install gnome-control-center.)
> 
> What happens if you instead run
> 
> $ apt install kodi gnome-control-center
> 
> ? You should either get a success (via different resolution of the
> dependencies, which doesn't consider omitting either of the two to be an
> acceptable solution) or an error which may help us narrow down the problem.


Here's the output:

# apt install kodi gnome-control-center
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
kodi is already the newest version (2:19.1+dfsg2-2).
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 (>= 2:19.1+dfsg2-2) but it is not going to be 
installed
         Depends: kodi-bin (< 2:19.1+dfsg2-2.1~) but it is not going to 
be installed
E: Unable to correct problems, you have held broken packages.

Regards,
Tristan

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
                   Tristan Miller
Free Software developer, ferret herder, logologist
              https://logological.org/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

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

#239187

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

On 2021-08-22 at 11:37, Tristan Miller wrote:

> Greetings.
> 
> On 22/08/2021 17.20, The Wanderer wrote:
>> On 2021-08-22 at 10:46, Tristan Miller wrote:
>>> On my bullseye system, it doesn't seem to be possible to install both
>>> kodi and gnome-control-center as they conflict with each other.  (See
>>> below for what happens when I've got kodi installed and then try to
>>> install gnome-control-center.)
>> 
>> What happens if you instead run
>> 
>> $ apt install kodi gnome-control-center
>> 
>> ? You should either get a success (via different resolution of the
>> dependencies, which doesn't consider omitting either of the two to be an
>> acceptable solution) or an error which may help us narrow down the problem.
> 
> 
> Here's the output:
> 
> # apt install kodi gnome-control-center
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> kodi is already the newest version (2:19.1+dfsg2-2).
> 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 (>= 2:19.1+dfsg2-2) but it is not going to be 
> installed
>          Depends: kodi-bin (< 2:19.1+dfsg2-2.1~) but it is not going to 
> be installed
> E: Unable to correct problems, you have held broken packages.

Hmm.

This appears to mean either that something is resulting in a conflict
with that version of kodi-bin, or that that version of kodi-bin is not
available.

I have:

$ apt-cache policy gnome-control-center kodi kodi-bin
gnome-control-center:
  Installed: (none)
  Candidate: 1:3.38.4-1
  Version table:
     1:3.38.4-1 900
        800 http://ftp.us.debian.org/debian stable/main amd64 Packages
        900 http://ftp.us.debian.org/debian testing/main amd64 Packages
kodi:
  Installed: (none)
  Candidate: 2:19.1+dfsg2-2
  Version table:
     2:19.1+dfsg2-2 900
        800 http://ftp.us.debian.org/debian stable/main amd64 Packages
        900 http://ftp.us.debian.org/debian testing/main amd64 Packages
kodi-bin:
  Installed: (none)
  Candidate: 2:19.1+dfsg2-2
  Version table:
     2:19.1+dfsg2-2 900
        800 http://ftp.us.debian.org/debian stable/main amd64 Packages
        900 http://ftp.us.debian.org/debian testing/main amd64 Packages

What do you have available?


What I usually do in this type of situation is to start adding the
specified "is not going to be installed" packages to the command line,
with explicit version numbers included if necessary, until it stops just
saying "is not going to be installed" and starts telling me *why* some
particular package won't be installed. This is usually a Conflicts or
version-specific Depends or the like. From there, it's not usually
difficult to figure out what's causing the problem and what to do.

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

#239195

Greetings.

On 22/08/2021 18.10, The Wanderer wrote:
> This appears to mean either that something is resulting in a conflict
> with that version of kodi-bin, or that that version of kodi-bin is not
> available.
> 
> I have:
> 
> $ apt-cache policy gnome-control-center kodi kodi-bin
> gnome-control-center:
>    Installed: (none)
>    Candidate: 1:3.38.4-1
>    Version table:
>       1:3.38.4-1 900
>          800 http://ftp.us.debian.org/debian stable/main amd64 Packages
>          900 http://ftp.us.debian.org/debian testing/main amd64 Packages
> kodi:
>    Installed: (none)
>    Candidate: 2:19.1+dfsg2-2
>    Version table:
>       2:19.1+dfsg2-2 900
>          800 http://ftp.us.debian.org/debian stable/main amd64 Packages
>          900 http://ftp.us.debian.org/debian testing/main amd64 Packages
> kodi-bin:
>    Installed: (none)
>    Candidate: 2:19.1+dfsg2-2
>    Version table:
>       2:19.1+dfsg2-2 900
>          800 http://ftp.us.debian.org/debian stable/main amd64 Packages
>          900 http://ftp.us.debian.org/debian testing/main amd64 Packages
> 
> What do you have available?


Thanks. I get the following:

# apt-cache policy gnome-control-center kodi kodi-bin
gnome-control-center:
   Installed: (none)
   Candidate: 1:3.38.4-1
   Version table:
      1:3.38.4-1 500
         500 http://deb.debian.org/debian bullseye/main amd64 Packages
kodi:
   Installed: 2:19.1+dfsg2-2
   Candidate: 2:19.1+dfsg2-2
   Version table:
  *** 2:19.1+dfsg2-2 500
         500 http://deb.debian.org/debian bullseye/main amd64 Packages
         100 /var/lib/dpkg/status
kodi-bin:
   Installed: 2:19.1+dfsg2-2
   Candidate: 2:19.1+dfsg2-2
   Version table:
  *** 2:19.1+dfsg2-2 500
         500 http://deb.debian.org/debian bullseye/main amd64 Packages
         100 /var/lib/dpkg/status

> What I usually do in this type of situation is to start adding the
> specified "is not going to be installed" packages to the command line,
> with explicit version numbers included if necessary, until it stops just
> saying "is not going to be installed" and starts telling me *why* some
> particular package won't be installed. This is usually a Conflicts or
> version-specific Depends or the like. From there, it's not usually
> difficult to figure out what's causing the problem and what to do.


What explicit version number do you suggest that I try?  Running "apt 
install kodi gnome-control-center" tells me that

The following packages have unmet dependencies:
  kodi : Depends: kodi-bin (>= 2:19.1+dfsg2-2) but it is not going to be 
installed
         Depends: kodi-bin (< 2:19.1+dfsg2-2.1~) but it is not going to 
be installed

But if I run "apt install kodi-bin=2:19.1+dfsg2-2", I am told

kodi-bin is already the newest version (2:19.1+dfsg2-2).

Regards,
Tristan

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
                   Tristan Miller
Free Software developer, ferret herder, logologist
              https://logological.org/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

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

#239198

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

On 2021-08-22 at 12:39, Tristan Miller wrote:

> Greetings.
> 
> On 22/08/2021 18.10, The Wanderer wrote:
> 
>> This appears to mean either that something is resulting in a
>> conflict with that version of kodi-bin, or that that version of
>> kodi-bin is not available.
>> 
>> I have:
>> 
>> $ apt-cache policy gnome-control-center kodi kodi-bin

<snip>

>> What do you have available?
> 
> 
> Thanks. I get the following:
> 
> # apt-cache policy gnome-control-center kodi kodi-bin
> gnome-control-center:
>    Installed: (none)
>    Candidate: 1:3.38.4-1
>    Version table:
>       1:3.38.4-1 500
>          500 http://deb.debian.org/debian bullseye/main amd64 Packages
> kodi:
>    Installed: 2:19.1+dfsg2-2
>    Candidate: 2:19.1+dfsg2-2
>    Version table:
>   *** 2:19.1+dfsg2-2 500
>          500 http://deb.debian.org/debian bullseye/main amd64 Packages
>          100 /var/lib/dpkg/status
> kodi-bin:
>    Installed: 2:19.1+dfsg2-2
>    Candidate: 2:19.1+dfsg2-2
>    Version table:
>   *** 2:19.1+dfsg2-2 500
>          500 http://deb.debian.org/debian bullseye/main amd64 Packages
>          100 /var/lib/dpkg/status

These version numbers all match mine.

This confirms that kodi-bin at the needed version number is available.

>> What I usually do in this type of situation is to start adding the
>> specified "is not going to be installed" packages to the command line,
>> with explicit version numbers included if necessary, until it stops just
>> saying "is not going to be installed" and starts telling me *why* some
>> particular package won't be installed. This is usually a Conflicts or
>> version-specific Depends or the like. From there, it's not usually
>> difficult to figure out what's causing the problem and what to do.
> 
> What explicit version number do you suggest that I try?  Running "apt 
> install kodi gnome-control-center" tells me that
> 
> The following packages have unmet dependencies:
>   kodi : Depends: kodi-bin (>= 2:19.1+dfsg2-2) but it is not going to be 
> installed
>          Depends: kodi-bin (< 2:19.1+dfsg2-2.1~) but it is not going to 
> be installed
> 
> But if I run "apt install kodi-bin=2:19.1+dfsg2-2", I am told
> 
> kodi-bin is already the newest version (2:19.1+dfsg2-2).

You need to continue specifying all of the packages in the same command
line, and repeat with new packages as necessary until it tells you an
actual reason for the failure instead of just the generic "is not going
to be installed".

So,

# apt install gnome-control-center kodi kodi-bin

or

# apt install gnome-control-center kodi kodi-bin=2:19.1+dfsg2-2

and then if that just fails because of another package, add that one and
repeat.

(Based on your 'apt-cache policy' output, I don't think specifying the
explicit version number will be necessary in this case, but it may be in
some other cases.)


Note that if you eventually hit a command line which succeeds, you'll
probably wind up marking all the listed packages as manually installed,
which you may not want. It may be worth backing up your
"manually-installed packages" state (as reported by the command
'apt-mark showmanual') before starting, so that after the whole thing is
done with you can go back and mark specific packages as auto-installed.

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

#239199

Greetings.

On 22/08/2021 19.10, The Wanderer wrote:
>> What explicit version number do you suggest that I try?  Running "apt
>> install kodi gnome-control-center" tells me that
>>
>> The following packages have unmet dependencies:
>>    kodi : Depends: kodi-bin (>= 2:19.1+dfsg2-2) but it is not going to be
>> installed
>>           Depends: kodi-bin (< 2:19.1+dfsg2-2.1~) but it is not going to
>> be installed
>>
>> But if I run "apt install kodi-bin=2:19.1+dfsg2-2", I am told
>>
>> kodi-bin is already the newest version (2:19.1+dfsg2-2).
> 
> You need to continue specifying all of the packages in the same command
> line, and repeat with new packages as necessary until it tells you an
> actual reason for the failure instead of just the generic "is not going
> to be installed".


Thanks; following this procedure I was eventually able to get apt into a 
state where it offered to install all the necessary dependencies for 
both kodi and gnome-control-center.

Regards,
Tristan

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
                   Tristan Miller
Free Software developer, ferret herder, logologist
              https://logological.org/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

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

#239200 — Manual vs Auto-Install in APT[ was : kodi and gnome-control-center conflict on bullseye]

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

On 2021-08-22 1:09 p.m., The Wanderer wrote:

> Note that if you eventually hit a command line which succeeds, you'll
> probably wind up marking all the listed packages as manually installed,
> which you may not want. It may be worth backing up your
> "manually-installed packages" state (as reported by the command
> 'apt-mark showmanual') before starting, so that after the whole thing is
> done with you can go back and mark specific packages as auto-installed.
> 

That's a great reminded that applies to many situation.
Thanks
-- 
Polyna-Maude R.-Summerside
-Be smart, Be wise, Support opensource development

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

#239188

On Sun, Aug 22, 2021 at 05:37:52PM +0200, Tristan Miller wrote:
> # apt install kodi gnome-control-center
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> kodi is already the newest version (2:19.1+dfsg2-2).
> 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 (>= 2:19.1+dfsg2-2) but it is not going to be
> installed
>         Depends: kodi-bin (< 2:19.1+dfsg2-2.1~) but it is not going to be
> installed
> E: Unable to correct problems, you have held broken packages.

Do you have any packages on hold?  dpkg -l | grep ^h

Do you have any packages pinned, either manually, or by way of some
automatic action performed by apt-listbugs?  I'm not an expert in
pinning, but maybe start with:  grep -ri pin /etc/apt

If neither of these is the case, then I'd try:

apt-cache polisy kodi kodi-bin      # just to get some information

And if that looks OK, then:

apt install kodi kodi-bin

Or maybe:

apt -f install    # with no packages, just to try to fix what's broken


In all cases, be prepared to tell apt "No" if it asks you to do something
that looks undesirable, like removing stuff you care about.

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

#239189

On Sun, Aug 22, 2021 at 12:04:46PM -0400, Greg Wooledge wrote:
> If neither of these is the case, then I'd try:
> 
> apt-cache polisy kodi kodi-bin      # just to get some information

Wow, today must be Typoday.  "policy" of course.

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

#239196

Greetings.

On 22/08/2021 18.10, Greg Wooledge wrote:
> Do you have any packages on hold?  dpkg -l | grep ^h


No, no output from that command.

> Do you have any packages pinned, either manually, or by way of some
> automatic action performed by apt-listbugs?  I'm not an expert in
> pinning, but maybe start with:  grep -ri pin /etc/apt


No pins listed by that command, and apt-cache policy also doesn't list 
anything under "Pinned packages".

> If neither of these is the case, then I'd try:
> 
> apt-cache polisy kodi kodi-bin      # just to get some information


# apt-cache policy kodi kodi-bin
kodi:
   Installed: 2:19.1+dfsg2-2
   Candidate: 2:19.1+dfsg2-2
   Version table:
  *** 2:19.1+dfsg2-2 500
         500 http://deb.debian.org/debian bullseye/main amd64 Packages
         100 /var/lib/dpkg/status
kodi-bin:
   Installed: 2:19.1+dfsg2-2
   Candidate: 2:19.1+dfsg2-2
   Version table:
  *** 2:19.1+dfsg2-2 500
         500 http://deb.debian.org/debian bullseye/main amd64 Packages
         100 /var/lib/dpkg/status


> And if that looks OK, then:
> 
> apt install kodi kodi-bin


# apt install kodi kodi-bin
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
kodi is already the newest version (2:19.1+dfsg2-2).
kodi-bin is already the newest version (2:19.1+dfsg2-2).
kodi-bin set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.

> Or maybe:
> 
> apt -f install    # with no packages, just to try to fix what's broken


# apt -f install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.


So it looks like none of your commands turned up anything, or any 
problems, and yet it's still not possible for me to install 
gnome-control-center.

Regards,
Tristan

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
                   Tristan Miller
Free Software developer, ferret herder, logologist
              https://logological.org/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

[toc] | [prev] | [standalone]

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

csiph-web