[Bug 1882232] Re: install chromium-browser in a chroot fails

2020-06-05 Thread Dimitri John Ledkov
My debconf prompt is different and has options to retry abort skip, or
press ok.


My screen is larger, is there a scrollbar that is not visible? can you scroll 
down to skip and press skip?

Alternatively, can you use debconf pressed to pressed the answer to the
quesiton as Skip:


chromium-browserchromium-browser/snap-no-connectivity   select  Skip

** Attachment added: "debconf-prompt-groovy.png"
   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1882232/+attachment/5380668/+files/debconf-prompt-groovy.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882232

Title:
  install chromium-browser in a chroot fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1882232/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1882232] Re: install chromium-browser in a chroot fails

2020-06-05 Thread Jo K
Ansible use his own module to wrap apt command, and it uses non-
interactive way, not just "-y".

Anyway i confirm that this fails under a chroot :

$ DEBIAN_FRONTEND=noninteractive chroot /target apt-get -y install 
chromium-browser
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  liblzo2-2 snapd squashfs-tools
Suggested packages:
  zenity | kdialog
The following NEW packages will be installed:
  chromium-browser liblzo2-2 snapd squashfs-tools
Preconfiguring packages ...
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/23.4 MB of archives.
After this operation, 105 MB of additional disk space will be used.
Selecting previously unselected package liblzo2-2:amd64.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 72913 files and directories currently installed.)
Preparing to unpack .../liblzo2-2_2.10-2_amd64.deb ...
Unpacking liblzo2-2:amd64 (2.10-2) ...
Selecting previously unselected package squashfs-tools.
Preparing to unpack .../squashfs-tools_1%3a4.4-1_amd64.deb ...
Unpacking squashfs-tools (1:4.4-1) ...
Selecting previously unselected package snapd.
Preparing to unpack .../snapd_2.44.3+20.04_amd64.deb ...
Unpacking snapd (2.44.3+20.04) ...
Setting up liblzo2-2:amd64 (2.10-2) ...
Setting up squashfs-tools (1:4.4-1) ...
Setting up snapd (2.44.3+20.04) ...
Created symlink 
/etc/systemd/system/multi-user.target.wants/snapd.apparmor.service → 
/lib/systemd/system/snapd.apparmor.service.
Created symlink 
/etc/systemd/system/multi-user.target.wants/snapd.autoimport.service → 
/lib/systemd/system/snapd.autoimport.service.
Created symlink 
/etc/systemd/system/multi-user.target.wants/snapd.core-fixup.service → 
/lib/systemd/system/snapd.core-fixup.service.
Created symlink 
/etc/systemd/system/multi-user.target.wants/snapd.recovery-chooser-trigger.service
 → /lib/systemd/system/snapd.recovery-chooser-trigger.service.
Created symlink 
/etc/systemd/system/multi-user.target.wants/snapd.seeded.service → 
/lib/systemd/system/snapd.seeded.service.
Created symlink 
/etc/systemd/system/cloud-final.service.wants/snapd.seeded.service → 
/lib/systemd/system/snapd.seeded.service.
Created symlink /etc/systemd/system/multi-user.target.wants/snapd.service → 
/lib/systemd/system/snapd.service.
Created symlink /etc/systemd/system/timers.target.wants/snapd.snap-repair.timer 
→ /lib/systemd/system/snapd.snap-repair.timer.
Created symlink /etc/systemd/system/sockets.target.wants/snapd.socket → 
/lib/systemd/system/snapd.socket.
Created symlink 
/etc/systemd/system/final.target.wants/snapd.system-shutdown.service → 
/lib/systemd/system/snapd.system-shutdown.service.
Selecting previously unselected package chromium-browser.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 73011 files and directories currently installed.)
Preparing to unpack 
.../chromium-browser_81.0.4044.129-0ubuntu0.20.04.1_amd64.deb ...
=> Installing the chromium snap
==> Checking connectivity with the snap store
===> Unable to contact the store, trying every minute for the next 30 minutes

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882232

Title:
  install chromium-browser in a chroot fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1882232/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1882232] Re: install chromium-browser in a chroot fails

2020-06-05 Thread Dimitri John Ledkov
"-y" is not enough to install non-interactive under ansible.

Either specify debconf non-interactive frontened, or ask ansible to
preseed the debconf answer that you acknowledge the debconf note that
the package will provide.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882232

Title:
  install chromium-browser in a chroot fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1882232/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1882232] Re: install chromium-browser in a chroot fails

2020-06-05 Thread Jo K
To reproduce

apt install ansible -y
ansible localhost -m apt -a "name=chromium-browser"

You can try it in a container. That's not exactly a chroot but...

docker run --rm -it ubuntu:latest /bin/bash
apt update && apt install ansible -y
ansible localhost -m apt -a "name=chromium-browser"

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882232

Title:
  install chromium-browser in a chroot fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1882232/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1882232] Re: install chromium-browser in a chroot fails

2020-06-05 Thread Jo K
I did install with "apt install chromium-browser -y" for the demonstration.
In my specific case, i use ansible so it is non interactive.

That task fails.

- name: install browsers
  apt:
state: latest
name:
  - firefox
  - firefox-locale-fr
  - chromium-browser
  - chromium-browser-l10n
  - adobe-flashplugin

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882232

Title:
  install chromium-browser in a chroot fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1882232/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1882232] Re: install chromium-browser in a chroot fails

2020-06-05 Thread Dimitri John Ledkov
That's a debconf note. How did you invoke installation?

All package installation is interactive. If you want non-interactive
package installation one has to pass options to apt to "do not disturb
me" and accept defaults to any questions around installation or
upgrades.

DEBIAN_FRONTEND=noninteractive chroot $MY_CHROOT apt-get -y install
$packages

is the better way to install packages non-interactively. Does doing
something like that sufficient to complete chromium-browser package
installation?

** Changed in: chromium-browser (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882232

Title:
  install chromium-browser in a chroot fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1882232/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs