SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Well, I'm only managing three systems, but each has updated flawlessly with autoslackpkg since my original problem. I don't know yet what caused that blowup, but it has not repeated. Thank you, Chuck56, for posting such a helpful tool.
root@0.cosmos:~# installpkg autoslackpkg-0.8-noarch-1_SBo.tgz
Verifying package autoslackpkg-0.8-noarch-1_SBo.tgz.
Unable to install autoslackpkg-0.8-noarch-1_SBo.tgz: tar archive is corrupt (tar returned error code 2)
I tried on two different computers, downloaded it a second time, tried both again... always same result.
root@0.cosmos:~# installpkg autoslackpkg-0.8-noarch-1_SBo.tgz
Verifying package autoslackpkg-0.8-noarch-1_SBo.tgz.
Unable to install autoslackpkg-0.8-noarch-1_SBo.tgz: tar archive is corrupt (tar returned error code 2)
I tried on two different computers, downloaded it a second time, tried both again... always same result.
The problem is it's only a tar archive. It's not actually gzipped.
Code:
~: file autoslackpkg-0.8.tar.gz
autoslackpkg-0.8.tar.gz: POSIX tar archive (GNU)
Unable to install autoslackpkg-0.8-noarch-1_SBo.tgz: tar archive is corrupt (tar returned error code 2)
Sorry about the corrupt SBo.tgz. I rebuilt it and ran "file" against the new package:
Code:
me@server:$ file autoslackpkg-0.8-noarch-1_SBo.tgz
autoslackpkg-0.8-noarch-1_SBo.tgz: gzip compressed data, last modified: Thu Jan 9 15:07:05 2020, max compression, from Unix, original size 92160
I don't use "tools" like these, but I do like seeing people use their creative side and reading about what they are creating.
I have one comment, and it's not about your work, but I think that technically you're not supposed to use the _SBo $TAG on packages that you are distributing. I just don't want to see you get yelled at by Willy (J/K, Willy wouldn't yell at you). But I think that just to be on the safe side, you should probably change the $TAG in your script.
Keep Hacking!
Last edited by Skaendo; 01-09-2020 at 12:59 PM.
Reason: spelling
I have one comment, and it's not about your work, but I think that technically you're not supposed to use the _SBo $TAG on packages that you are distributing. I just don't want to see you get yelled at by Willy
I've never used GRUB so that makes it a bit tough for me to script. I'm not ruling it out just waiting to see if the script gains more traction and users.
I still got the same problem, which seemed to be I can't download from that site with a normal web browser... used wget, then the package worked. I ran autoslackpkg and it said too many arguments (but I had written zero of them)... default behaviour should be a sumamry... preferably also a manual (man) page. After typing 'autslackpkg --help' then more arguments, I'm just at a loss how to use it...
I still got the same problem, which seemed to be I can't download from that site with a normal web browser... used wget, then the package worked. I ran autoslackpkg and it said too many arguments (but I had written zero of them)... default behaviour should be a sumamry... preferably also a manual (man) page. After typing 'autslackpkg --help' then more arguments, I'm just at a loss how to use it...
My site is using mod_deflate and I didn't have the no-gzip setting for the downloads directory. It should be fixed now. Compressing already compressed files is bad form on my part.
Not sure what the "too many arguments" error is all about. Try: autoslackpkg -h overview
If that doesn't work maybe the wget download was wonky and needs a redo.
Not sure what the "too many arguments" error is all about. Try: autoslackpkg -h overview
I.e., when one only types 'autoslackpkg' (no arguments) zero arguments is not too many arguments so shouldn't say that rather than perhaps giving the overview--what almost all commands do (or otherwise kind of troll you by saying what to type for help then forcing you type that just to get an idea what it's about... it's good if they give an overview if there are no arguments and a longer overview if you add '-h' or '--help,' but overviews aren't going to be different there's no reason to make you type an argument than just make it the default output when you're not telling it to do anything.)
I wonder if there's something in your shell environment that might be in play.
I think you're right; sorry (got the normal output, you showed above, on my server; ) should've posted this full output I got on my laptop, actually.
Code:
root@0.microcosmos:~# autoslackpkg
/usr/sbin/autoslackpkg: line 114: [: too many arguments
/usr/sbin/autoslackpkg: line 124: DIALOG: unbound variable
However I haven't really started using it yet, because apparently the default is install packages one doesn't have installed--like X11 on a virtual private server (VPS, don't want them installed, unused, not always enough room)--and 'slackpkg clean-system'--which would remove everything I built from SlackBuilds.org/etc. I'd guess there's a way to disable/alter that behaviour.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.