Uploaded image for project: 'Funtoo Linux'
  1. Funtoo Linux
  2. FL-10594

Metro/setup: Better error message on stage not found.

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Important (Ebuild) Important (Ebuild)
    • None
    • None
    • None
    • Hide
      run metro/scripts/setup

      In the curses interface, choose an architecture for which there is no tarball on https://build.funtoo.org/, for example: 1.4-release-std/x86-32bit/athlon-xp/.

      The script will exit with a cryptic error, which doesn't help the user to find out what the problem really was (missing tarball).
      Show
      run metro/scripts/setup In the curses interface, choose an architecture for which there is no tarball on https://build.funtoo.org/, for example: 1.4-release-std/x86-32bit/athlon-xp/. The script will exit with a cryptic error, which doesn't help the user to find out what the problem really was (missing tarball).
    • impacts metro usability (setup is a replacement for "autosetup")

      If you try to set up a build for an architecture which doesn't have a tarball available at https://build.funtoo.org/, the script will exit with the following message:

      Traceback (most recent call last):
        File "/root/metro/./scripts/setup", line 414, in <module>
          main()
        File "/root/metro/./scripts/setup", line 372, in main
          create_file(c_path.joinpath("version", "stage3"), mirror_path, latest_build, owner=owner, group=group, dirmode=dirmode, mode=mode)
        File "/root/metro/./scripts/setup", line 88, in create_file
          f.write(contents)
      TypeError: write() argument must be str, not None

      It would be better if the script at least issued a more informative message in this case, but ideally the user would get this message right in the curses interface and be allowed to choose a different architecture instead.

            drobbins drobbins
            adbosco adbosco
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: