Page 28 of 36
Re: USM bug reports
Posted: 28 Feb 2017, 23:23
by Ed_P
And now via command line:
Code: Select all
root@porteus:/home/guest# usm -u ponce
Starting ponce database update
Downloading: vercheck.txt DONE
Downloading: CHECKSUMS.md5.gz DONE
Downloading: MANIFEST.bz2 DONE
Downloading: PACKAGES.TXT.gz DONE
Downloading: LIBS.TXT.gz -->
DONE
gzip: /var/usm/ponce/LIBS.TXT.gz: unexpected end of file
==============================================================================
WARNING! WARNING! WARNING! WARNING! WARNING!
==============================================================================
One or more errors occurred while usm was running:
FATAL ERROR!
usm update_database 309
Could not decompress: LIBS.TXT.gz
==============================================================================
root@porteus:/home/guest#
Re: USM bug reports
Posted: 01 Mar 2017, 02:14
by brokenman
I have no problem updating ponce.
Re: USM bug reports
Posted: 01 Mar 2017, 06:00
by Ed_P
brokenman wrote:I have no problem updating ponce.
Always showing off.
Actually I reran it and it worked.
Re: USM bug reports
Posted: 03 Mar 2017, 03:52
by rych
Porteus 3.2.2 64 XFCE
the following downloads a few files until it tries to download LIBS.TXT.gz. This one fails, the file has 0 size, hence the error:
Code: Select all
#usm -u all
...
...
Using proxy server: ...
Downloading: LIBS.TXT.gz DONE
File verification was good.
gzip: /var/usm/slackware/LIBS.TXT.gz: unexpected end of file
==============================================================================
WARNING! WARNING! WARNING! WARNING! WARNING!
==============================================================================
One or more errors occurred while usm was running:
FATAL ERROR!
usm update_database 309
Could not decompress: LIBS.TXT.gz
==============================================================================
I guess the question is where/how do I get LIBS.TXT.gz?
Re: USM bug reports
Posted: 03 Mar 2017, 04:23
by ncmprhnsbl
rych wrote:I guess the question is where/how do I get LIBS.TXT.gz?
good question... unfortunately i don't have a good answer ...
generally, these are intermittent problems and you just to 'try again later' ... eg. i just updated (usm database) with no problems..
Re: USM bug reports
Posted: 03 Mar 2017, 22:21
by brokenman
You can try opening the mirror file in mirrors-slackware.txt and uncommenting a different mirror.
Re: USM bug reports
Posted: 04 Mar 2017, 03:00
by Ed_P
brokenman wrote:You can try opening the mirror file in mirrors-slackware.txt and uncommenting a different mirror.
That would be the /etc/usm/mirrors-slackware.txt file for those considering doing it.
Re: USM bug reports
Posted: 25 May 2017, 15:09
by rchase
This recurring problem with LIBS.TXT seems very strange -- is this slackonly's way of deferring downloads until their database is ready? If so, it is a completely opaque and inefficient way of doing so; most of the data for the update downloads successfully, only LIBS.TXT is missing.
Re: USM bug reports
Posted: 25 May 2017, 22:26
by donald
Re: USM bug reports
Posted: 27 May 2017, 19:37
by Bogomips
pmppinho wrote:LIBS.TXT is somehow missing, although they do exist in the repositories.
Code: Select all
Processing: vlc-2.2.6-x86_64-1alien.txz
==============================================================================
WARNING! WARNING! WARNING! WARNING! WARNING!
==============================================================================
One or more errors occurred while usm was running:
FATAL ERROR!
resolve_deps 369
Please wait 6 hours for the next database update. Could not find: LIBS.TXT
==============================================================================
OK. After some digging it appears this error is somewhat misleading. The way I understand it, is that the entry for package in question has not been found in any of the LIBS.TXT, thereby indicating an out of sync error. Implication is that package does not exist in any of repositories, had once been there, but now probably superseded.
Re: USM bug reports
Posted: 27 May 2017, 21:50
by Ed_P
^ An interesting perspective
Bogomips. So basically the error msg needs to be changed. Something like this maybe:
Code: Select all
Could not find file(s) in any: LIBS.TXT
Please wait 6 hours for the next database update.
Who maintains the packages.txt and lib.txt files? Who maintains the packages in each repository? And then there are the mirrors. Sounds like a lot of work, unless the files are static.
Re: USM bug reports
Posted: 27 May 2017, 22:29
by Evan
I gave an example in the bugs thread of how USM can't download a common popular file directly (or even if you use the number menu option) even though it does exist on the repository, so why would it be any different for resolving dependencies , as if's it a separate problem?
If you can't get files by a direct command then how is a script going to resolve them for what is needed?
Re: USM bug reports
Posted: 27 May 2017, 23:28
by brokenman
So you have a better understanding of how it works, the USM database is an automated system.
Every 6 hours it updates the 5 slackware repositories locally. It then unpacks each and every slackware package and runs a check on which libraries are contained within after which it creates the file LIBS.TXT. If there is a mismatch between which packages actually exists on the slackware server and what USM believes exist on the server then some packages will give this error.
I will need to check the system tomorrow to see if there is a failure somewhere.
Re: USM bug reports
Posted: 28 May 2017, 00:12
by Evan
I don't have a better understanding , i have the understanding from the perspective of a frustrated user that USM is spitting out errors regardless if you have Libs.txt or not.
How many more months do we need to report the same problem and that is getting worse with examples for anyone to realize that waiting 6 hours does not fix anything?
Bogomips wanted to build a module reserve out of frustration of the same continuing problems back in February, did waiting 6 hours fix the problem?
The files exist on the repositories if you go there directly in a web browser but USM does not see them , doesn't logic and reason dictate that the problem is either with USM or the repositories have changed their format that it's no longer compatible with USM and needs to be addressed?
Re: USM bug reports
Posted: 28 May 2017, 00:30
by Ed_P
brokenman wrote:So you have a better understanding of how it works, the USM database is an automated system.
Every 6 hours it updates the 5 slackware repositories locally. It then unpacks each and every slackware package and runs a check on which libraries are contained within after which it creates the file LIBS.TXT.
Wow! I'm impressed. And happy to hear someone isn't doing it manually.
Evan wrote:The files exist on the repositories if you go there directly in a web browser but USM does not see them , doesn't logic and reason dictate that the problem is either with USM or the repositories have changed their format that it's no longer compatible with USM and needs to be addressed?
Isn't that what
brokenman said?
brokenman wrote: I will need to check the system tomorrow to see if there is a failure somewhere.