Hi Kevin,

Having a user with *ALLOBJ authority run the following command, it failed, please see the file attached

QSH CMD('touch -C 819 /tmp/bootstrap.log; /QOpenSys/usr/bin/ksh /tmp/bootstrap.sh > /tmp/bootstrap.log 2>&1')
Command ended normally with exit status 1.

--
Thank you,
Nihat


-----Özgün İleti-----
Kimden: Nihat Ezer
Tarih: Wednesday, August 12, 2020 8:22 PM
Kime: opensource@xxxxxxxxxxxxxxxxxx
Konu: YNT: [IBMiOSS] Directory checksum error

No, i do not actually as i thought i could, will let you know about the result

-----Özgün İleti-----
Kimden: OpenSource <opensource-bounces@xxxxxxxxxxxxxxxxxx> Yerine Kevin Adler
Tarih: Wednesday, August 12, 2020 7:44 PM
Kime: opensource@xxxxxxxxxxxxxxxxxx
Konu: Re: [IBMiOSS] Directory checksum error

DİKKAT: Bu e-posta kurum dışından gönderilmiştir. Zararlı dosya veya bağlantılar (link) içerebilir. Kaynağından emin olmadığınız dosyaları/bağlantıları (link) açarken veya e-postayı cevaplarken dikkatli olunuz.
________________________________

You cannot use the PASE version of tar to extract the bootstrap as it
requires GNU tar to contain paths that exceed the maximum allowed by PASE
tar. The error you encountered indicated that you didn't have authority to
run it. I don't think the script marks it executable after it's extracted
from the script, so you would need *ALLOBJ to run it. Arguably that's a
bug since binaries should be marked executable, but you need *ALLOBJ
anyway.

Do you have *ALLOBJ authority?


----- Original message -----
From: Nihat Ezer via OpenSource <opensource@xxxxxxxxxxxxxxxxxx>
Sent by: "OpenSource" <opensource-bounces@xxxxxxxxxxxxxxxxxx>
To: "opensource@xxxxxxxxxxxxxxxxxx" <opensource@xxxxxxxxxxxxxxxxxx>
Cc: Nihat Ezer <nihatezer@xxxxxxxxxxxxxxxxxxxxx>
Subject: [EXTERNAL] [IBMiOSS] Directory checksum error
Date: Wed, Aug 12, 2020 2:38 AM

Greetings,

Offline Install Instructions (without ACS)
[1]https://bitbucket.org/ibmi/opensource/src/master/docs/yum/#markdown-header-offline-install-instructions-without-acs

We are on IBM i 7.2 TR9 and following the link above, transferred the
bootstrap.sh and bootstrap.tar.Z files to /tmp directory in binary.

QSH CMD('touch -C 819 /tmp/bootstrap.log; /QOpenSys/usr/bin/ksh
/tmp/bootstrap.sh > /tmp/bootstrap.log 2>&1')

Giving a try to the command above, i have seen the following error
message in the /tmp/bootstrap.log file
/tmp/bootstrap.sh: /tmp/gtar: cannot execute
Bootstrap failed

I have then come across the link,
[2]https://www.ibm.com/support/pages/installation-open-source-products-using-rpm-method,
and run the following commands then failed again

> ls -la /tmp/bootstrap.tar
-rwxrwxrwx 1 sozl1025 0 511795200 12 Aug 08:09
/tmp/bootstrap.tar
$
> tar -xvf /tmp/bootstrap.tar
x ./QOpenSys
x ./QOpenSys/var
x ./QOpenSys/var/lib
x ./QOpenSys/var/lib/rpm
x ./QOpenSys/var/lib/rpm/Packages, 1818624 bytes, 3552 tape blocks
x ./QOpenSys/var/lib/rpm/Name, 32768 bytes, 64 tape blocks
x ./QOpenSys/var/lib/rpm/Basenames, 524288 bytes, 1024 tape blocks
x ./QOpenSys/var/lib/rpm/Group, 32768 bytes, 64 tape blocks
x ./QOpenSys/var/lib/rpm/Requirename, 32768 bytes, 64 tape blocks
x ./QOpenSys/var/lib/rpm/Providename, 393216 bytes, 768 tape blocks
x ./QOpenSys/var/lib/rpm/Conflictname, 32768 bytes, 64 tape blocks
..
..
..
./QOpenSys/var/lib/yum/yumdb/l/a0ed622d1a032fc601f07a4343634050b0ba5a29-libsqlite3-0-3.19.3-2-ppc64
linked to ./QOpenSys/var/lib/
yum/yumdb/l/87ebc55068ceb902da39a5a379ad83df2c26b8b4-libmagic1-5.32-6-ppc64/relea
x ././@LongLink, 108 bytes, 1 tape blocks
x ././@LongLink, 113 bytes, 1 tape blocks
./QOpenSys/var/lib/yum/yumdb/l/a0ed622d1a032fc601f07a4343634050b0ba5a29-libsqlite3-0-3.19.3-2-ppc64
linked to ./QOpenSys/var/lib/
yum/yumdb/l/87ebc55068ceb902da39a5a379ad83df2c26b8b4-libmagic1-5.32-6-ppc64/comma
x ././@LongLink, 109 bytes, 1 tape blocks
x ././@LongLink, 114 bytes, 1 tape blocks
./QOpenSys/var/lib/yum/yumdb/l/a0ed622d1a032fc601f07a4343634050b0ba5a29-libsqlite3-0-3.19.3-2-ppc64
linked to ./QOpenSys/var/lib/
yum/yumdb/l/87ebc55068ceb902da39a5a379ad83df2c26b8b4-libmagic1-5.32-6-ppc64/check
x ././@LongLink, 114 bytes, 1 tape blocks
x
./QOpenSys/var/lib/yum/yumdb/l/a0ed622d1a032fc601f07a4343634050b0ba5a29-libsqlite3-0-3.19.3-2-ppc64
tar: directory checksum error (4 != 4559)

Do you guys have come across such a kind of error with the
libsqlite3-0-3.19.3-2-ppc64 or have any idea on how to get rid of it?

--
Thank you,
Nihat

--
This is the IBMi Open Source Roundtable (OpenSource) mailing list
To post a message email: OpenSource@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: [3]https://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at [4]https://archive.midrange.com/opensource .

Help support midrange.com by shopping at amazon.com with our affiliate
link: [5]https://amazon.midrange.com




References

Visible links
1. https://bitbucket.org/ibmi/opensource/src/master/docs/yum/#markdown-header-offline-install-instructions-without-acs
2. https://www.ibm.com/support/pages/installation-open-source-products-using-rpm-method
3. https://lists.midrange.com/mailman/listinfo/opensource
4. https://archive.midrange.com/opensource
5. https://amazon.midrange.com/
--
This is the IBMi Open Source Roundtable (OpenSource) mailing list To post a message email: OpenSource@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/opensource
or email: OpenSource-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/opensource.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].