SliTaz SliTaz Forum

You are not logged in.

#1 2021-11-27 21:54:37

Ceel
Administrator
Registered: 2011-04-02
Posts: 1,424

Bug in tazdev?

The SliTaz Cook & Cooker documentation says:

"By default Tazdev creates a chroot in /home/slitaz/cooking/chroot but you can specify a custom path in the argument."

but it seems this doesn't work correctly:

# tazdev -gc --rootfs=/home/up/chroot
Generating new chroot in: /home/up/chroot
================================================================================
Mirror URL:                                                          [ Done ]
Installing: slitaz-base-files                                        [ Done ]
Installing: busybox                                                  [ Done ]
Installing: cookutils                                                [ Done ]
Installing: tazpkg                                                   [ Done ]
Installing: lzma                                                     [ Done ]
Creating resolv.conf...                                              [ Done ]
Creating TZ...                                                       [ Done ]
Restoring host packages list...                                      [ Done ]
================================================================================
Ready to chroot with: tazdev -c

# tazdev -c /home/up/chroot
Mounting virtual filesystems...
mount: /home/up/chroot/proc: mount point does not exist.
mount: /home/up/chroot/sys: mount point does not exist.
mount: /home/up/chroot/dev/pts: mount point does not exist.
mount: /home/up/chroot/dev/shm: mount point does not exist.
                                                                     [ Failed ]
Chrooting to: /home/up/chroot
chroot: can't execute '/bin/sh': No such file or directory

Unmounting virtual filesystems...umount: /home/up/chroot/dev/shm: no mount point specified.
umount: /home/up/chroot/dev/pts: no mount point specified.
umount: /home/up/chroot/sys: no mount point specified.
umount: /home/up/chroot/proc: no mount point specified.
                                                                     [ Done ]
The "chroot" installed by tazdev in [c]/home/up/chroot/[/c] looks like that:

etc/--+--slitaz/--+--slitaz.conf
      |           |
      |           +--tazpkg.conf
      |
      +--resolv.conf
      |
      +--slitaz-release
      |
      +--TZ

var/--+--cache/----tazpkg/-- (empty)
      |
      +--lib/---+--tazpkg/--installed/-- (empty)
      |         |
      |         +--blocked-packages-list
      |         |
      |         +--installed.info  (0 byte)
      |         |
      |         +--mirror
      |         |
      |         +--packages.info
      |         |
      |         +--packages.up
      |
      +--log/------slitaz/--tazpkg.log  (O byte)
and nothing else.

Tazdev doesn't find any URL for the mirror; I wonder what it installs and where.

Used without any arguments [c]tazdev -gc[/c] works as described in the doc.

Offline

#2 2021-11-30 13:23:44

Ceel
Administrator
Registered: 2011-04-02
Posts: 1,424

Re: Bug in tazdev?

I believed I found the solution using a non listed option in tazdev:

# tazdev -gc --mirror=https://mirror1.slitaz.org/packages/cooking/ --rootfs=/home/up/chroot

Generating new chroot in: /home/up/chroot
================================================================================
Mirror URL: https://mirror1.slitaz.org/packages/cooking/             [ Done ]
Installing: slitaz-base-files                                        [ Done ]
Installing: busybox                                                  [ Done ]
Installing: cookutils                                                [ Done ]
Installing: tazpkg                                                   [ Done ]
Installing: lzma                                                     [ Done ]
Creating resolv.conf...                                              [ Done ]
Creating TZ...                                                       [ Done ]
Restoring host packages list...                                      [ Done ]
================================================================================
Ready to chroot with: tazdev -c

but always only 2 directories created ([c]etc[/c] and [c]var[/c]) in [c]/home/up/chroot[/c].

It seems there is no other solution than installing manually the packages in the chroot.

Offline

#3 2021-12-05 17:15:12

mojo
Administrator
Registered: 2011-03-29
Posts: 2,174

Re: Bug in tazdev?

This problem is fixed now that the 5.0/cooking mirror is providing the proper index files to tazpkg again.

Root of problem:

https://forum.slitaz.org/topic/tazpkg-totally-broken-due-to-missing-bundletarlzma#post-50371

Offline

#4 2021-12-05 21:58:32

Ceel
Administrator
Registered: 2011-04-02
Posts: 1,424

Re: Bug in tazdev?

Unfortunatly no sad

Or maybe I don't understand correctly how tazdev works; now tazdev try to create (with the same success : only [c]/etc[/c] and [c]/var[/c])/mount a chroot in [c]/home/media/up/chroot/chroot[/c] and not in [c]/media/up/chroot[/c]

# tazdev -gc /media/up/chroot
Generating new chroot in: /home/slitaz//media/up/chroot/chroot
================================================================================
Mirror URL:                                                          [ Done ]
Installing: slitaz-base-files                                        [ Done ]
Installing: busybox                                                  [ Done ]
Installing: cookutils                                                [ Done ]
Installing: tazpkg                                                   [ Done ]
Installing: lzma                                                     [ Done ]
Creating resolv.conf...                                              [ Done ]
Creating TZ...                                                       [ Done ]
Restoring host packages list...                                      [ Done ]
================================================================================
Ready to chroot with: tazdev -c /media/up/chroot
[c]# tazdev -c /media/frugal/chroot
Mounting virtual filesystems...mount: <strong>/home/slitaz//media/frugal/chroot/chroot</strong>/proc: mount point does not exist.
...[/c]
Previously tazdev tried at least to create/mount the chroot at the good location.

This is not important, I created the chroot manually on my external disk but I'm affraid I have now to mount it manually too; I'll write a little script and I will forget tazdev.

Offline

Registered users online in this topic: 0, guests: 1
[Bot] ClaudeBot

Board footer

Powered by FluxBB
Modified by Visman

[ Generated in 0.017 seconds, 8 queries executed - Memory usage: 1.55 MiB (Peak: 1.77 MiB) ]