LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 12-24-2019, 03:24 PM   #31
TSquaredF
Member
 
Registered: Dec 2005
Location: "The South Coast of Texas"
Distribution: Slackware64-current
Posts: 540

Rep: Reputation: Disabled

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.
 
1 members found this post helpful.
Old 01-09-2020, 03:44 AM   #32
dchmelik
Member
 
Registered: Nov 2008
Location: Washington state, USA
Distribution: BSD, Slackware, Devuan, RedHat, SUSE, Artix, Gentoo, Kubuntu, Raspbian, FreeDOS, Android, Replicant
Posts: 412

Rep: Reputation: 46
I'd like to try it, but...

Code:
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.
 
Old 01-09-2020, 05:37 AM   #33
individual
Member
 
Registered: Jul 2018
Posts: 261
Blog Entries: 1

Rep: Reputation: 207Reputation: 207Reputation: 207
Quote:
Originally Posted by dchmelik View Post
I'd like to try it, but...

Code:
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)
 
Old 01-09-2020, 10:19 AM   #34
Chuck56
Member
 
Registered: Dec 2006
Location: Colorado
Distribution: Slackware
Posts: 585

Original Poster
Rep: Reputation: 185Reputation: 185
Quote:
Originally Posted by dchmelik View Post
Code:
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 reposted the SBo file at: https://www.go4it2day.com/downloads/...arch-1_SBo.tgz

Hope that works better. I'm headed out for the morning for some fun in the snow and will check back later this afternoon.
 
Old 01-09-2020, 12:57 PM   #35
Skaendo
Senior Member
 
Registered: Dec 2014
Location: West Texas, USA
Distribution: Slackware64-14.2
Posts: 1,181

Rep: Reputation: Disabled
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
 
1 members found this post helpful.
Old 01-09-2020, 01:06 PM   #36
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 1,644

Rep: Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269
Quote:
Originally Posted by Skaendo View Post
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
Lawsuit incoming!
 
1 members found this post helpful.
Old 01-09-2020, 02:56 PM   #37
Tonus
Member
 
Registered: Jan 2007
Location: Paris, France
Distribution: Slackware-current
Posts: 584
Blog Entries: 3

Rep: Reputation: 152Reputation: 152
autoslackpkg - a way to automate slackpkg

Hi there, any plans for grub?
Since it takes whatever kernels are installed, it could be as simple as
Code:
grub-mkconfig -o /boot/grub/grub.cfg
Saying the target might have to be configured.

That's how it works here. Perhaps more experts folks could step in and add hints?
 
Old 01-09-2020, 08:43 PM   #38
Chuck56
Member
 
Registered: Dec 2006
Location: Colorado
Distribution: Slackware
Posts: 585

Original Poster
Rep: Reputation: 185Reputation: 185
Quote:
Originally Posted by Tonus View Post
Hi there, any plans for grub? ...
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.
 
Old 01-09-2020, 08:45 PM   #39
Chuck56
Member
 
Registered: Dec 2006
Location: Colorado
Distribution: Slackware
Posts: 585

Original Poster
Rep: Reputation: 185Reputation: 185
Quote:
Originally Posted by Skaendo View Post
...I think that technically you're not supposed to use the _SBo $TAG on packages that you are distributing...
You're right! I plan to submit the script to SBo, eventually.
 
1 members found this post helpful.
Old 01-10-2020, 02:18 AM   #40
dchmelik
Member
 
Registered: Nov 2008
Location: Washington state, USA
Distribution: BSD, Slackware, Devuan, RedHat, SUSE, Artix, Gentoo, Kubuntu, Raspbian, FreeDOS, Android, Replicant
Posts: 412

Rep: Reputation: 46
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...
 
Old 01-10-2020, 10:28 PM   #41
Chuck56
Member
 
Registered: Dec 2006
Location: Colorado
Distribution: Slackware
Posts: 585

Original Poster
Rep: Reputation: 185Reputation: 185
Quote:
Originally Posted by dchmelik View Post
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.
 
Old 01-10-2020, 10:41 PM   #42
dchmelik
Member
 
Registered: Nov 2008
Location: Washington state, USA
Distribution: BSD, Slackware, Devuan, RedHat, SUSE, Artix, Gentoo, Kubuntu, Raspbian, FreeDOS, Android, Replicant
Posts: 412

Rep: Reputation: 46
Quote:
Originally Posted by Chuck56 View Post
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.)
 
Old 01-10-2020, 10:46 PM   #43
Chuck56
Member
 
Registered: Dec 2006
Location: Colorado
Distribution: Slackware
Posts: 585

Original Poster
Rep: Reputation: 185Reputation: 185
I wonder if there's something in your shell environment that might be in play. Here's what I see when I enter "autoslackpkg"

Code:
root@desktop:~# autoslackpkg

Usage: autoslackpkg [-h|m|s|v] [argument]
  [-h] help    - requires argument
                 overview | blacklist | elilo | lilo | mkinitrd
  [-m] mode    - requires argument
                 dialog | batch
  [-s] section - requires argument
                 update | install-new | upgrade-all | install-kernel
                 | clean-system | remove-kernel | new-config
  [-v] version - release version
 
Old 01-10-2020, 10:56 PM   #44
dchmelik
Member
 
Registered: Nov 2008
Location: Washington state, USA
Distribution: BSD, Slackware, Devuan, RedHat, SUSE, Artix, Gentoo, Kubuntu, Raspbian, FreeDOS, Android, Replicant
Posts: 412

Rep: Reputation: 46
Quote:
Originally Posted by Chuck56 View Post
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.

Last edited by dchmelik; 01-10-2020 at 10:57 PM.
 
Old 01-10-2020, 11:05 PM   #45
Chuck56
Member
 
Registered: Dec 2006
Location: Colorado
Distribution: Slackware
Posts: 585

Original Poster
Rep: Reputation: 185Reputation: 185
That's where your /etc/slackpkg/blacklist comes into play. You can exclude X11 files, SBo files and others from consideration.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
having trouble after upgrading 14.1 slackware using slackpkg and slackpkg+ [solved] slackartist Slackware 1 12-28-2015 08:28 AM
[SOLVED] Slackpkg, Slackpkg Plus, Slackware 14.1 x86_64 install.log delay or slow to write bamunds Slackware 7 04-22-2014 12:12 PM
[SOLVED] typos in latest /etc/slackpkg/mirrors(.new) [slackpkg-2.82.0-noarch-8.tgz] wailingwailer Slackware 4 09-22-2012 05:04 AM
Slackpkg: missing something in /usr/libexec/slackpkg/functions.d/dialog-functions.sh michelino Slackware 4 03-20-2007 01:22 PM
LXer: Speaking Unix, Part 6: Automate, automate, automate! LXer Syndicated Linux News 0 01-04-2007 10:54 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 02:46 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration