search

drinkcat / chroagh

Chromium OS Archlinux Chroot Environment
BSD 3-Clause "New" or "Revised" License
241 stars 27 forks source link

grep, pacman and glib: Not found in archive #111

Open karudedios opened 8 years ago

karudedios commented 8 years ago

Hello, I'm pretty new at this and I'm trying to install arch First, it fails to install grep, pacman and glib. It also doesn't go past libncursesw.so.

Command: sudo sh -e installer/main.sh -r arch -t xfce

The whole installation log is:

Installing arch-x86_64 chroot to /usr/local/chroots/arch
Fetching repository packages list...
Fetching core...
######################################################################## 100.0%
Fetching community...
######################################################################## 100.0%
Fetching extra...
######################################################################## 100.0%
Downloading and extracting packages...
Downloading and installing bash...
######################################################################## 100.0%
Downloading and installing gawk...
######################################################################## 100.0%
Downloading and installing grep...
######################################################################## 100.0%
tar: grep-2.24-1/depends: Not found in archive
tar: Exiting with failure status due to previous errors
tar: grep-2.24-1/depends: Not found in archive
tar: Exiting with failure status due to previous errors
Downloading and installing pacman...
######################################################################## 100.0%
tar: pacman-5.0.1-2/depends: Not found in archive
tar: Exiting with failure status due to previous errors
tar: pacman-5.0.1-2/depends: Not found in archive
tar: Exiting with failure status due to previous errors
Downloading and installing sed...
######################################################################## 100.0%
Downloading and installing util-linux...
######################################################################## 100.0%
Downloading and installing readline...
######################################################################## 100.0%
Downloading and installing glibc...
######################################################################## 100.0%
tar: glibc-2.23-1/depends: Not found in archive
tar: Exiting with failure status due to previous errors
tar: glibc-2.23-1/depends: Not found in archive
tar: Exiting with failure status due to previous errors
Downloading and installing ncurses...
######################################################################## 100.0%
Downloading and installing libncursesw.so...
karudedios commented 8 years ago

I managed to fix the Not found in archive issue this by following this answer to #110

And for the lbncursesw.so I resolved this by following #100.

So far it's installing everything, will update if anything is found.

Custodia commented 8 years ago

I had the same problems and the solutions linked worked. Also if it seemingly stops midway to: Not unmounting /mnt/stateful_partition/crouton/chroots/arch as another instance is using it.

Entering the chroot and when asked continuing the install script fixes that.

ghost commented 8 years ago

Entering the chroot and when asked continuing the install script fixes that.

It doesn't for me unfortuantely. It stops with

cc1: all warnings being treated as errors Failed to complete chroot setup. The chroot setup script may be broken. Your chroot is not fully configured. Removing the chroot setup script. You may want to update your chroot again. UID 1000 not found in arch Not unmounting /mnt/stateful_partition/crouton/chroots/arch as another instance is using it.

What exact steps did you follow in the linked solutions? I did this an this. What else may be different? I'm running a Pixel 2015 with Chrome Dev 52. Can the version of Chrome make any difference?

Custodia commented 8 years ago

@Duxon I got mine working after that and gave up when a fix for a bug that kept killing my xorg thats fixed in crouton wasn't in groach yet 😅

That said you should probably open your own issue with the full output, that looks like a completely different problem.

Personally I'm waiting for the next rebase, that will propably fix a lot of issues.