Skip to content

Bunch of error messages while building and creating ISO #5

@adnan360

Description

@adnan360

Building

Running ./08-Service.sh world 64, at some point it shows these...

1: mv: cannot stat '../01-Core64-removed/devel/usr/include/python2.7': No such file or directory

...
Executing install script for zstd-1.3.2-x86_64-1.txz.
Package zstd-1.3.2-x86_64-1.txz installed.

Starting the core cleanup procedure ... smen ;)
mv: cannot stat '../01-Core64-removed/devel/usr/include/python2.7': No such file or directory

Later found out there are many other packages that were updated, not only python2.7. Their filenames changed, so it doesn't work.

2: ...flashplayer-plugin-32.0.0.101-x86_64-1alien.txz...ERROR 404: Not Found.

...
2020-04-22 15:18:10 (57.8 KB/s) - ‘gslapt-0.5.4a-x86_64-1.tgz’ saved [171137/171137]

--2020-04-22 15:18:10--  http://www.slackware.com/~alien/slackbuilds/flashplayer-plugin/pkg64/current/flashplayer-plugin-32.0.0.101-x86_64-1alien.txz
Resolving www.slackware.com (www.slackware.com)... 23.57.76.150, 23.57.76.69, 2600:140f:7::1739:4c96, ...
Connecting to www.slackware.com (www.slackware.com)|23.57.76.150|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2020-04-22 15:18:17 ERROR 404: Not Found.

Same case, package version updated.

3: ./05-KDE.sh: line 4: .ftp-credentials: No such file or directory

4: ./07-Devel.sh: line 5: .ftp-credentials: No such file or directory

5: ./10-Virtual.sh: line 5: .ftp-credentials: No such file or directory

6: No such file ‘gobject-introspection-1.58.3-x86_64-1.txz’. and more...

When building ISO

7: rsync...No such file or directory (2)

When running:

./08-Service.sh small-world 64

EDIT: Changed command

For me, even after installing grub and xorriso, I saw this error:

rsync: mkdir "/path/to/nimblex-master/ISO-test64/nimblex64" failed: No such file or directory (2)

So I did something like: mkdir ISO-test64 then it worked.

8: rsync -av ... $REMOTE causes errors

Again I got rsync error that it can't connect to seif something. So I commented the rsync -av ... $REMOTE block. (Maybe keeping this commented by default would be a good idea? or maybe a config file for username/pass? then it can run only when that file is there?)

Then ran again and this time it finally created an iso. (Spoiler: It didn't boot. It got stuck at grub shell. No grub.cfg was produced. Any help would be appreciated.) At the end the whole project folder was around 14GB. It took me 2.5 days to figure everything out.

After all this I think it would be a good idea to have at least a reference ISO available in this repo Releases section (hosted on GitHub).

After trying, failing and trying again, I made some edits to the files to make it build it. Especially to update to newer version of packages which were non existent now. Plus, some other issues. I was thinking I will push a PR with my changes.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions