Re: Package dependency problems

John G Heim <[email protected]>
Newsgroups gmane.linux.debian.fai
Message-ID <[email protected]>
An update ...

So my fai install was hung, waiting for 30 minutes trying to contact the 
snap store. I got onto the target machine, deleted /usr/bin/snap, made 
it a symlink to /bin/true, and the install got going again.

Geez, what a load of bullstuff.  Maybe I can add a hook to create that 
file before fai starts installing packages.

Just to be clear, I am not blaming this on fai. Not at all. Who's 
brilliant idea was it to make it impossible to install chromium in a 
chroot environment? There ought not be such a package in the 
debian/ubuntu repository.




On 1/10/20 1:52 PM, John G Heim wrote:
> Well, apt-rdepends says its gnome. I am going to check what happens if I 
> do not ask it to install gnome but I think it will be bad.
> 
> The problem is that when it tries to install the chromium-browser 
> package,  it tries to contact something called the "snap store". It 
> keeps trying for 30 minutes.  So its adding 30 minutes to every install. 
> From a typical software.log:
> 
> Installing the chromium snap
> Checking connectivity with the snap store
> Unable to contact the store, trying every minute for the next 30 minutes
> 
> 
> Apparently snaps are cross-platform package containers. You have to run 
> the snapd daemon to talk to the snap store but the daemon won't run in a 
> chroot environment.
> 
> # systemctl start snapd
> Running in chroot, ignoring request: start
> 
> So it looks as if there is no way to install chromium-browser in fai and 
> no way to avoid it either.
> 
> 
> 
> 
> 
> On 1/10/20 12:20 PM, Thomas Lange wrote:
>> apt-rdepends -r chromium-browser
>> will list the reverse dependencies.
>>
>> You can set the variable MAXPACKAGES to 1 so only one package and its
>> dependencies are installed at a time. By default we have this set in
>> class/FAIBASE.var
>>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.