USM fails to update slackware patches [SOLVED]

Post#1 by **yldouright** » 16 Mar 2018, 12:30

Running Porteus 3.2.2 Mate, I typed usm -u all and noted that the slackware patches database fails continually wqith a "There was a problem..." general error. Looking into the "USM:Settings:Edit Database" menu command, I didn't not a listing for slackware patches. Help me understand what is going on here.

Post#2 by **Ed_P** » 16 Mar 2018, 15:37

I just ran a USM update and everything ran.

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# usm -u all
 Starting slackware database update 
Downloading: vercheck.txt  DONE
Downloading: CHECKSUMS.md5  DONE
Downloading: MANIFEST.bz2  DONE
Downloading: PACKAGES.TXT  DONE
Downloading: LIBS.TXT.gz  DONE
File verification was good.
Optimizing manifest
 slackware  database updated. 

Updating config file

 Starting slackwarepatches database update 
Downloading: CHECKSUMS.md5  DONE
Downloading: MANIFEST.bz2  DONE
Downloading: PACKAGES.TXT  DONE
Downloading: LIBS.TXT.gz  DONE
File verification was good.
Optimizing manifest
 slackwarepatches  database updated. 

 Starting slacky database update 
Downloading: CHECKSUMS.md5.gz  DONE
Downloading: MANIFEST.bz2  DONE
Downloading: PACKAGES.TXT.gz  DONE
Downloading: LIBS.TXT.gz  DONE
File verification was good.
Optimizing manifest
 slacky  database updated. 

 Starting salix database update 
Downloading: CHECKSUMS.md5  DONE
Downloading: PACKAGES.TXT  DONE
Downloading: LIBS.TXT.gz  DONE
Downloading: OPTIFEST.gz  DONE
 salix  database updated. 

 Starting alien database update 
Downloading: CHECKSUMS.md5.gz  DONE
Downloading: MANIFEST.bz2  DONE
Downloading: PACKAGES.TXT.gz  DONE
Downloading: LIBS.TXT.gz  DONE
File verification was good.
Optimizing manifest
 alien  database updated. 

 Starting ponce database update 
Downloading: CHECKSUMS.md5.gz  DONE
Downloading: MANIFEST.bz2  DONE
Downloading: PACKAGES.TXT.gz  DONE
Downloading: LIBS.TXT.gz  DONE
Optimizing manifest
 ponce  database updated. 

 Starting slackonly database update 
Downloading: CHECKSUMS.md5.gz  DONE
Downloading: MANIFEST.bz2  DONE
Downloading: PACKAGES.TXT.gz  DONE
Downloading: LIBS.TXT.gz  DONE
File verification was good.
Optimizing manifest
 slackonly  database updated. 

 Starting sbo database update 
SLACKBUILDS.TXT.gz
Downloading: SLACKBUILDS.TXT.gz  DONE
 sbo  database updated. 


Downloading: extra-deps.txt  DONE
Downloading: ignore-deps.txt  DONE

root@porteus:/home/guest#

Apparently the settings menu is missing the slackware patches entry.

Post#3 by **yldouright** » 16 Mar 2018, 17:42

@Ed_P
Yes, there is no entry for it in the USM:Settings menu. I was able to update the patches on my next try in the terminal. Very weird, still get no response from requests to update Salix.

Post#4 by **Ed_P** » 16 Mar 2018, 18:10

Post your results when you do this:

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# usm -u salix
 Starting salix database update 
Downloading: vercheck.txt  DONE
Downloading: CHECKSUMS.md5  DONE
Downloading: PACKAGES.TXT  DONE
Downloading: LIBS.TXT.gz  DONE
Downloading: OPTIFEST.gz  DONE
 salix  database updated. 


root@porteus:/home/guest#

Post#5 by **yldouright** » 18 Mar 2018, 19:57

With the manually updated mirrors, everything works as it should on 3.2.x but when you use those same repos in 3.1, we have some anomalys. I will list them:
1. There is no slackware patches database in Porteus 3.1 and trying to update it directly via usm fails.
2. The 3.1 i486 distro doesn't ship with the developer packages so you can't make anything (very inconveneint for this older distro).
3. Downloading and activating the Quantum module doesn't allow you to access it.

The three questions that these situations inspire are:
1. Do I need to manually add a "slackware patches" category source somewhere and if so, where to create this file?
2. What do I need to install on Porteus 3.1 XFCE to compile from source code?
3. How do I remove Firefox ESR 31.x from XFCE Porteus 3.1 so that a clean module of Quantum will work properly?

Post#6 by **Ed_P** » 18 Mar 2018, 23:32

1. No.

brokenman wrote: ↑
18 Mar 2018, 13:29
slackware-patches IS slackware.

2. No idea.

3. Probably need something like ISOMaster to edit the ISO.

Why are you using 3.1 rather than 3.2.2?

Post#7 by **yldouright** » 20 Mar 2018, 12:16

@Ed_P
I couldn't find a 32bit i686 build on the mirrors and the i586 runs like crap on a celeron P4. See this post for more details. Also, the 3.2.2 builds have kernel support for stuff I don't need so is much larger than it needs to be for me. I've been playing with the idea of a custom kernel for some time but haven't jumped in yet.

Post#8 by **Ed_P** » 20 Mar 2018, 18:05

Just not sure how insecure the older release is. If you don't use the system online you should be ok.