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

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

Re: Installing chromium uninstalls runit-init

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

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Installing chromium uninstalls runit-init <tomas@tuxteam.de> - 2020-02-22 17:10 +0100
    Re: Installing chromium uninstalls runit-init Mark Raynsford <list+org.debian@io7m.com> - 2020-02-22 17:30 +0100
      Re: Installing chromium uninstalls runit-init Mark Raynsford <list+org.debian@io7m.com> - 2020-02-22 17:40 +0100
        Re: Installing chromium uninstalls runit-init Jonas Smedegaard <jonas@jones.dk> - 2020-02-22 19:00 +0100
      Re: Installing chromium uninstalls runit-init tomas@tuxteam.de - 2020-02-22 17:40 +0100
        Re: Installing chromium uninstalls runit-init Mark Raynsford <list+org.debian@io7m.com> - 2020-02-22 18:00 +0100
          Re: Installing chromium uninstalls runit-init tomas@tuxteam.de - 2020-02-22 18:10 +0100
      Re: Installing chromium uninstalls runit-init Jonas Smedegaard <jonas@jones.dk> - 2020-02-22 17:40 +0100

#219330 — Re: Installing chromium uninstalls runit-init

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

On Sat, Feb 22, 2020 at 04:02:16PM +0000, Mark Raynsford wrote:
> Hello!
> 
> Attempting to install chromium results in the following:
> 
> # apt install chromium

I had a similar situation with firefox wanting to install systemd.

Just for kicks, try

  apt install chromium sysvinit-core

If that works, you'd perhaps want to adapt your apt-preferences
(either pushing sysvinit-core or lowering systemd).

Cheers
-- tomás

[toc] | [next] | [standalone]

#219332

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

On 2020-02-22T17:08:48 +0100
<tomas@tuxteam.de> wrote:
> I had a similar situation with firefox wanting to install systemd.
> 
> Just for kicks, try
> 
>   apt install chromium sysvinit-core
> 
> If that works, you'd perhaps want to adapt your apt-preferences
> (either pushing sysvinit-core or lowering systemd).
> 
> Cheers
> -- tomás

No such luck, unfortunately:

# apt install chromium sysvinit-core
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:
 chromium : Depends: libgtk-3-0 (>= 3.9.10) but it is not going to be
installed E: Unable to correct problems, you have held broken packages.

-- 
Mark Raynsford | http://www.io7m.com

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

#219333

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

'Ello.

On 2020-02-22T17:32:59 +0100
Jonas Smedegaard <jonas@jones.dk> wrote:
>
> Maybe you have... held broken packages?
> 
> If you use aptitude instead of apt, then you can step through more 
> options, including options involving downgrading (which is unsupported 
> by Debian, but since your system is already broken I guess you prefer 
> "cheating" over reinstalling from scratch).

I haven't held any packages. This install is a few hours old and
I've barely touched any of the default settings... What gave you the
impression my system is broken?

I'm happy to try aptitude. I've been using apt elsewhere, but for no
particular reason.

--
Mark Raynsford | http://www.io7m.com

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

#219342

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

Quoting Mark Raynsford (2020-02-22 17:38:20)
> 'Ello.
> 
> On 2020-02-22T17:32:59 +0100
> Jonas Smedegaard <jonas@jones.dk> wrote:
> >
> > Maybe you have... held broken packages?
> > 
> > If you use aptitude instead of apt, then you can step through more 
> > options, including options involving downgrading (which is 
> > unsupported by Debian, but since your system is already broken I 
> > guess you prefer "cheating" over reinstalling from scratch).
> 
> I haven't held any packages. This install is a few hours old and I've 
> barely touched any of the default settings... What gave you the 
> impression my system is broken?
> 
> I'm happy to try aptitude. I've been using apt elsewhere, but for no 
> particular reason.

What gave me the impression was the error message that you snipped.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

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

#219334

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

On Sat, Feb 22, 2020 at 04:24:01PM +0000, Mark Raynsford wrote:
> On 2020-02-22T17:08:48 +0100
> <tomas@tuxteam.de> wrote:
> > I had a similar situation with firefox wanting to install systemd.
> > 
> > Just for kicks, try
> > 
> >   apt install chromium sysvinit-core
> > 
> > If that works, you'd perhaps want to adapt your apt-preferences
> > (either pushing sysvinit-core or lowering systemd).
> > 
> > Cheers
> > -- tomás
> 
> No such luck, unfortunately:
> 
> # apt install chromium sysvinit-core
> 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:
>  chromium : Depends: libgtk-3-0 (>= 3.9.10) but it is not going to be
> installed E: Unable to correct problems, you have held broken packages.

Not all is lost... for some reason your system thinks you don't want
to install libgtk-3.0 (I'm assuming you're "on" stable). Just add
that to your install list. If it doesn't conflict with something else,
that might work.

Cheers
-- t

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

#219338

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

On 2020-02-22T17:39:15 +0100
tomas@tuxteam.de wrote:
>
> Not all is lost... for some reason your system thinks you don't want
> to install libgtk-3.0 (I'm assuming you're "on" stable). Just add
> that to your install list. If it doesn't conflict with something else,
> that might work.
> 
> Cheers
> -- t

Thanks! I was about to try that, but it seems that aptitude found an
alternative solution. Firstly, "# aptitude install chromium" said:

The following packages have unmet dependencies:
 runit-init : Conflicts: systemd-sysv but 241-7~deb10u3 is to be
installed The following actions will resolve these dependencies:

     Remove the following packages:       
1)     runit-init [2.1.2-25 (now, stable)]

     Install the following packages:      
2)     runit-systemd [2.1.2-25 (stable)]  

Accept this solution? [Y/n/q/?] n

As I want to keep runit-init, I had to reject that solution. I was then
prompted with:

The following actions will resolve these dependencies:

     Install the following packages:                      
1)     dbus-x11 [1.12.16-1 (stable)]                      

     Keep the following packages at their current version:
2)     dbus-user-session [Not Installed]                  
3)     libpam-systemd [Not Installed]                     
4)     policykit-1 [Not Installed]                        
5)     systemd-sysv [Not Installed]                       

     Leave the following dependencies unresolved:         
6)     dbus-user-session recommends systemd-sysv          
7)     upower recommends policykit-1                      

Solution 6 looks to be the one I want. So...

The following NEW packages will be installed:
  adwaita-icon-theme{a} at-spi2-core{a} chromium chromium-common{a} chromium-sandbox{a} dbus-x11{a} dconf-gsettings-backend{a} 
  dconf-service{a} fonts-liberation{a} glib-networking{a} glib-networking-common{a} glib-networking-services{a} 
  gsettings-desktop-schemas{a} gtk-update-icon-cache{a} hicolor-icon-theme{a} i965-va-driver{a} intel-media-va-driver{a} 
  libaacs0{a} libaom0{a} libasound2{a} libasound2-data{a} libasyncns0{a} libatk-bridge2.0-0{a} libatk1.0-0{a} libatk1.0-data{a} 
  libatomic1{a} libatspi2.0-0{a} libauthen-sasl-perl{a} libavahi-client3{a} libavahi-common-data{a} libavahi-common3{a} 
  libavcodec58{a} libavformat58{a} libavutil56{a} libbdplus0{a} libbluray2{a} libcairo-gobject2{a} libchromaprint1{a} 
  libcodec2-0.8.1{a} libcolord2{a} libcrystalhd3{a} libcups2{a} libdata-dump-perl{a} libdconf1{a} libepoxy0{a} 
  libfile-basedir-perl{a} libfile-desktopentry-perl{a} libfile-listing-perl{a} libfile-mimeinfo-perl{a} libflac8{a} 
  libfont-afm-perl{a} libgme0{a} libgomp1{a} libgsm1{a} libgtk-3-0{a} libgtk-3-bin{a} libgtk-3-common{a} libgudev-1.0-0{a} 
  libhtml-form-perl{a} libhtml-format-perl{a} libhtml-tree-perl{a} libhttp-cookies-perl{a} libhttp-daemon-perl{a} 
  libhttp-negotiate-perl{a} libigdgmm5{a} libimobiledevice6{a} libio-socket-ssl-perl{a} libio-stringy-perl{a} 
  libipc-system-simple-perl{a} libjson-glib-1.0-0{a} libjson-glib-1.0-common{a} libjsoncpp1{a} liblcms2-2{a} 
  liblwp-protocol-https-perl{a} libmailtools-perl{a} libminizip1{a} libmp3lame0{a} libmpg123-0{a} libnet-dbus-perl{a} 
  libnet-http-perl{a} libnet-smtp-ssl-perl{a} libnet-ssleay-perl{a} libnspr4{a} libnss3{a} libnuma1{a} libogg0{a} libopenjp2-7{a} 
  libopenmpt0{a} libopus0{a} libplist3{a} libproxy1v5{a} libpulse0{a} libre2-5{a} librest-0.7-0{a} libshine3{a} libsnappy1v5{a} 
  libsndfile1{a} libsoup-gnome2.4-1{a} libsoup2.4-1{a} libsoxr0{a} libspeex1{a} libssh-gcrypt-4{a} libswresample3{a} libtheora0{a} 
  libtie-ixhash-perl{a} libtry-tiny-perl{a} libtwolame0{a} libu2f-udev{a} libupower-glib3{a} libusb-1.0-0{a} libusbmuxd4{a} 
  libva-drm2{a} libva-x11-2{a} libva2{a} libvdpau-va-gl1{a} libvdpau1{a} libvorbis0a{a} libvorbisenc2{a} libvorbisfile3{a} 
  libvpx5{a} libwavpack1{a} libwayland-client0{a} libwayland-cursor0{a} libwayland-egl1{a} libwebpdemux2{a} libwebpmux3{a} 
  libwww-perl{a} libwww-robotrules-perl{a} libx11-protocol-perl{a} libx264-155{a} libx265-165{a} libxcb-xfixes0{a} libxkbcommon0{a} 
  libxml-parser-perl{a} libxml-twig-perl{a} libxml-xpathengine-perl{a} libxslt1.1{a} libxss1{a} libxvidcore4{a} libzvbi-common{a} 
  libzvbi0{a} mesa-va-drivers{a} mesa-vdpau-drivers{a} notification-daemon{a} perl-openssl-defaults{a} upower{a} usbmuxd{a} 
  va-driver-all{a} vdpau-driver-all{a} xdg-utils{a} 
The following packages are RECOMMENDED but will NOT be installed:
  policykit-1 
0 packages upgraded, 150 newly installed, 0 to remove and 0 not upgraded.
Need to get 104 MB of archives. After unpacking 404 MB will be used.

That looks a lot more like it!

Chromium appears to be running.

-- 
Mark Raynsford | http://www.io7m.com

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

#219341

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

On Sat, Feb 22, 2020 at 04:51:01PM +0000, Mark Raynsford wrote:
> On 2020-02-22T17:39:15 +0100
> tomas@tuxteam.de wrote:
> >
> > Not all is lost [...]

> Thanks! I was about to try that, but it seems that aptitude found an
> alternative solution. Firstly, "# aptitude install chromium" said:

Great you found a solution :-)

Cheers
-- t

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

#219336

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

Hi Mark,

Quoting Mark Raynsford (2020-02-22 17:24:01)
> On 2020-02-22T17:08:48 +0100
> <tomas@tuxteam.de> wrote:
> > I had a similar situation with firefox wanting to install systemd.
> > 
> > Just for kicks, try
> > 
> >   apt install chromium sysvinit-core
> > 
> > If that works, you'd perhaps want to adapt your apt-preferences
> > (either pushing sysvinit-core or lowering systemd).
> > 
> > Cheers
> > -- tomás
> 
> No such luck, unfortunately:
> 
> # apt install chromium sysvinit-core
> 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:
>  chromium : Depends: libgtk-3-0 (>= 3.9.10) but it is not going to be
> installed E: Unable to correct problems, you have held broken packages.

Maybe you have... held broken packages?

If you use aptitude instead of apt, then you can step through more 
options, including options involving downgrading (which is unsupported 
by Debian, but since your system is already broken I guess you prefer 
"cheating" over reinstalling from scratch).


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

[toc] | [prev] | [standalone]

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

csiph-web