Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
|
04-16-2014, 01:32 AM
|
#256
|
Member
Registered: Oct 2009
Location: Italy
Distribution: Slackware
Posts: 983
|
sorry.
fixed in slackpkg+-1.3.1-noarch-2mt.txz
thankyou
|
|
1 members found this post helpful.
|
04-16-2014, 04:30 AM
|
#257
|
Senior Member
Registered: May 2006
Location: France
Distribution: Slackware
Posts: 1,052
|
Hello
@zerouno:
Following this thread, I'm wondering why the CHECKSUMS.md5 from slackware "repository" is blanked when the gpg verification of the CHECKSUM.md5 from any of the configured repositories fails ? (the code snippets below is from current stable slackpkg+)
Code:
203: if [ $(checkgpg ${TMPDIR}/CHECKSUMS.md5-$PREPO) -ne 1 ];then
204: echo
205: echo " !!! F A T A L !!!"
206: echo " Repository '$PREPO' FAILS the CHECKSUMS.md5 signature check"
207: echo " The file may be corrupted or the gpg key may be not valid."
208: echo " Remember to import keys by launching 'slackpkg update gpg'."
209: echo
210: sleep 5
211: echo > ${TMPDIR}/CHECKSUMS.md5
212: fi
When one of the configured 3rd party repository is down, this statement leads slackpkg to exit because the gpg of CHECKSUMS.md5 is wrong , so /var/lib/slackpkg/pkglist is not updated, even if all others repositories (even slackware mirror) are ok. The snippet below is from slackpkg (function updatefilelists lines #988-#1008) :
Code:
getfile ${SOURCE}CHECKSUMS.md5 ${TMPDIR}/CHECKSUMS.md5
getfile ${SOURCE}CHECKSUMS.md5.asc ${TMPDIR}/CHECKSUMS.md5.asc
if ! [ -e "${TMPDIR}/CHECKSUMS.md5" ]; then
echo -e "\
\n\t\tWARNING: Your mirror appears incomplete and is missing the\n\
\t\t CHECKSUMS.md5 file. We recommend you change your mirror\n\
\t\t so that package integrity can be verified against \n\
\t\t CHECKSUMS.md5.\n"
sleep 10
else
if [ "$CHECKGPG" = "on" ]; then
ISOK=$(checkgpg ${TMPDIR}/CHECKSUMS.md5)
if [ "$ISOK" = "0" ]; then
rm $TMPDIR/CHECKSUMS.md5
rm $TMPDIR/CHECKSUMS.md5.asc
echo -e "\
\n\t\tERROR: Verification of the gpg signature on CHECKSUMS.md5\n\
\t\t failed! This could mean that the file is out of date\n\
\t\t or has been tampered with.\n"
cleanup # <= this call leads slackpkg to exit
fi
ATM, to workaround this, users can run slackpkg -checkgpg=off update. But it would be better to reset only the CHECKSUMS.md5 of the unavailable repository, so that /var/lib/slackpkg/pkglist will be updated with data from the valid repositories. So, slackpkg+ must be updated this way :
Code:
203: if [ $(checkgpg ${TMPDIR}/CHECKSUMS.md5-$PREPO) -ne 1 ];then
204: echo
205: echo " !!! F A T A L !!!"
206: echo " Repository '$PREPO' FAILS the CHECKSUMS.md5 signature check"
207: echo " The file may be corrupted or the gpg key may be not valid."
208: echo " Remember to import keys by launching 'slackpkg update gpg'."
209: echo
210: sleep 5
211: echo > ${TMPDIR}/CHECKSUMS.md5-$PREPO
212: fi
Hope this helps.
Cheers.
--
SeB
|
|
|
04-17-2014, 05:06 AM
|
#258
|
Member
Registered: Oct 2009
Location: Italy
Distribution: Slackware
Posts: 983
|
fixed.
Now failed repository will be skipped in the update process.
|
|
1 members found this post helpful.
|
04-19-2014, 02:20 PM
|
#259
|
Senior Member
Registered: Oct 2005
Location: France
Distribution: Slackware 15.0 64bit
Posts: 1,171
|
@zerouno and @phenixia2003,
Have you noticed this thread Slackpkg, Slackpkg Plus, Slackware 14.1 x86_64 install.log delay or slow to write?
I have experienced the same problem on slackware 14.1 32bits.
I'm using package slackpkg+-1.3.1-noarch-3mt
Last edited by gegechris99; 04-19-2014 at 02:24 PM.
Reason: reference to my version of slackpkg+
|
|
|
04-20-2014, 04:17 AM
|
#260
|
Senior Member
Registered: May 2006
Location: France
Distribution: Slackware
Posts: 1,052
|
Hello,
Quote:
Originally Posted by gegechris99
|
As a temporary workaround you can use this patch slackpkgplus-1.3.1-3mt_20140420.patch.txt (for slackpkg+1.3.1-3mt) which disables the install.log update. I guess zerouno will provide a better solution ASAP:
Code:
$ su -
$ cd /usr/libexec/slackpkg/functions.d
$ patch -p0</path/to/slackpkgplus-1.3.1-3mt_20140420.patch.txt
Cheers.
--
SeB
Last edited by phenixia2003; 04-20-2014 at 04:18 AM.
|
|
1 members found this post helpful.
|
04-21-2014, 06:05 AM
|
#261
|
Senior Member
Registered: Mar 2005
Location: Kentucky
Distribution: Slackware64-current
Posts: 1,852
|
Thanks phenixia2003! Works much better now.
|
|
|
04-21-2014, 08:53 AM
|
#262
|
Member
Registered: Oct 2009
Location: Italy
Distribution: Slackware
Posts: 983
|
Really...
isn't very needed a full packages rescan at every update process, so I removed it.
But an install log may be useful to track (and remember in future) the installed packages so if you want a full install.log you only need to run /usr/libexec/slackpkg/makeinstlog.sh manually the first time you install slackpkg. After that slackpkg will update it (as incremental) ONLY in the install/upgrade/remove process.
However when I will apply the new upgrade-all method (when I will have a decent time to spend for slackpkg+), that may just deprecate the current install.log
The info.log and the 'not remove tmpdir' remains becouse they are used only in the highest verbose mode.
|
|
|
04-21-2014, 09:27 AM
|
#263
|
Senior Member
Registered: Oct 2005
Location: France
Distribution: Slackware 15.0 64bit
Posts: 1,171
|
Package slackpkg+-1.3.1-noarch-4mt solved the "slow to write" update issue for me.
Thanks phenixia2003 and zerouno for the quick fix.
|
|
|
04-22-2014, 11:19 AM
|
#264
|
Member
Registered: Sep 2013
Location: Mounds View MN
Distribution: Slackware64-14.2-Multilib XDM/FVWM3
Posts: 780
|
Thanks everyone for fixing the install.log slow write. My slackware 14.1 x86_64 with multilib is working great now. Thank you for the clue about what it was doing also. I'll have to keep this in mind the next time I install slackware on the four computers I'm switching over this month from WinXP to Slackware. For the future features: Is there a way for slackpkg+ to test if it is the first install or if the install.log already exists and then not attempt the install.log process?
Best Regards, Brian A in Minnesota
|
|
|
07-12-2014, 04:11 AM
|
#265
|
Member
Registered: Jul 2014
Distribution: Slackware64-Current, Slackware64-14.2
Posts: 33
Rep:
|
Hi!
I use this tool long time ago and it is wonderful...
The beginning of this year i start to building a repository for
me and my few friends and add few important packages from SBo.
Some time ago I learned about a new tool slackrepo:
https://idlemoor.github.io/slackrepo/index.html
Slackrepo is a highly automated SlackBuild package builder
and helps you to make a package repository.
Also use Alienbob gen_repos_files.sh script.
Now i have almost build all packages from SBo and upload to my repo:
http://slackonly.com/pub/packages/14.1-x86_64/
This repo is puplic and you can use it.
With slackpkg+ now is very easy to add new packages.
Thanks @zerouno and @idlemoor...
|
|
1 members found this post helpful.
|
07-13-2014, 10:21 AM
|
#266
|
Member
Registered: Oct 2009
Location: Italy
Distribution: Slackware
Posts: 983
|
Patched slackpkg+ to add $ROOT and $CONF support reflecting slackpkg-2.28.0-13
|
|
|
07-16-2014, 07:04 AM
|
#267
|
Member
Registered: Mar 2006
Location: Valadares, V.N.Gaia, Portugal
Distribution: Slackware
Posts: 531
|
Feature request
Is it possible to implement generate-template in slackpkg+ as well?
I tried using install-template and it works, but generate-template is restricted to official packages.
The templates are just text files with a list of package names which are easy enough to create with a script (how I do it now), but I would like to generate them with slackpkg+ if possible.
It is a very useful feature and I use it all the time: - Create a VM with a minimal install of slackware and then add the required packages for the task that machine will perform
- Make a template with slackpkg
- Remake slackware-minimal install media with new template added to /etc/slackpkg/templates/
- Boot new media on as many machines (or VMs) as needed and install minimal-slackware
- boot minimal-slackware and use slackpkg to install required template for the task (ie: slackpkg install-template webserver)
It saves me a lot of time
|
|
|
07-16-2014, 07:18 AM
|
#268
|
Member
Registered: Oct 2009
Location: Italy
Distribution: Slackware
Posts: 983
|
Code:
# slackpkg generate-template test
# grep slackpkg slackpkg test.template
slackpkg+
slackpkg
it currently works!
|
|
|
07-16-2014, 08:15 AM
|
#269
|
Member
Registered: Mar 2006
Location: Valadares, V.N.Gaia, Portugal
Distribution: Slackware
Posts: 531
|
Quote:
Originally Posted by zerouno
Code:
# slackpkg generate-template test
# grep slackpkg slackpkg test.template
slackpkg+
slackpkg
it currently works!
|
Again, my bad
I grep for a package that I usually install (vlc) but somehow was not present on this box
Sorry for the trouble
|
|
|
10-26-2014, 05:31 AM
|
#270
|
Senior Member
Registered: May 2006
Location: France
Distribution: Slackware
Posts: 1,052
|
Hello,
I think it would be good to apply the patch below (also in attachment) to prevent glibc-debug to be installed when running: slackpkg install multilib.
Code:
--- slackpkgplus.sh.org 2014-10-26 11:20:12.448186282 +0100
+++ slackpkgplus.sh.new 2014-10-26 11:20:44.568188316 +0100
@@ -918,9 +918,13 @@
echo "$pref" | grep -qi "multilib" && MLREPO_SELELECTED=true
- if $MLREPO_SELELECTED && [ "$CMD" == "remove" ] ; then
- internal_blacklist "glibc"
- internal_blacklist "gcc"
+ if $MLREPO_SELELECTED ; then
+ if [ "$CMD" == "install" ] ; then
+ internal_blacklist "glibc-debug"
+ elif [ "$CMD" == "remove" ] ; then
+ internal_blacklist "glibc"
+ internal_blacklist "gcc"
+ fi
fi
package="SLACKPKGPLUS_${pref}"
--
SeB
|
|
|
All times are GMT -5. The time now is 08:10 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|