USM bug reports

Please reproduce your error on a second machine before posting, and check the error by running without saved changes or extra modules (See FAQ No. 13, "How to report a bug"). For unstable Porteus versions (alpha, beta, rc) please use the relevant thread in our "Development" section.
User avatar
Ed_P
Contributor
Contributor
Posts: 3070
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: USM bug reports

Post#406 by Ed_P » 28 Feb 2017, 23:23

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#
Ed

User avatar
brokenman
Site Admin
Site Admin
Posts: 5439
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: USM bug reports

Post#407 by brokenman » 01 Mar 2017, 02:14

I have no problem updating ponce.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
Ed_P
Contributor
Contributor
Posts: 3070
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: USM bug reports

Post#408 by Ed_P » 01 Mar 2017, 06:00

brokenman wrote:I have no problem updating ponce.
Always showing off. :bad:

Actually I reran it and it worked. :%)
Ed

rych
Black ninja
Black ninja
Posts: 49
Joined: 04 Jan 2014, 04:27
Distribution: Porteus 2.1 32-bit
Location: NZ

Re: USM bug reports

Post#409 by rych » 03 Mar 2017, 03:52

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?

User avatar
ncmprhnsbl
Full of knowledge
Full of knowledge
Posts: 793
Joined: 20 Mar 2012, 03:42
Distribution: 3.2.2-64bit xfce/openbox
Location: australia
Contact:

Re: USM bug reports

Post#410 by ncmprhnsbl » 03 Mar 2017, 04:23

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..
Forum Rules : http://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
brokenman
Site Admin
Site Admin
Posts: 5439
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: USM bug reports

Post#411 by brokenman » 03 Mar 2017, 22:21

You can try opening the mirror file in mirrors-slackware.txt and uncommenting a different mirror.
How do i become super user?
Wear your underpants on the outside and put on a cape.

User avatar
Ed_P
Contributor
Contributor
Posts: 3070
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: USM bug reports

Post#412 by Ed_P » 04 Mar 2017, 03:00

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. :)
Ed

rchase
Samurai
Samurai
Posts: 154
Joined: 10 Jan 2016, 17:26
Distribution: Porteus 3.2.2 xfce x64
Location: Denver, Colorado

Re: USM bug reports

Post#413 by rchase » 25 May 2017, 15:09

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.

donald
Full of knowledge
Full of knowledge
Posts: 1127
Joined: 17 Jun 2013, 13:17
Distribution: Porteus 3.2.2 XFCE 32bit
Location: Germany

Re: USM bug reports

Post#414 by donald » 25 May 2017, 22:26


Bogomips
Full of knowledge
Full of knowledge
Posts: 2522
Joined: 25 Jun 2014, 15:21
Distribution: 3.2.2 Cinnamon & KDE5
Location: London

Re: USM bug reports

Post#415 by Bogomips » 27 May 2017, 19:37

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.
Linux porteus 4.4.0-porteus #3 SMP PREEMPT Sat Jan 23 07:01:55 UTC 2016 i686 AMD Sempron(tm) 140 Processor AuthenticAMD GNU/Linux
NVIDIA Corporation C61 [GeForce 6150SE nForce 430] (rev a2) MemTotal: 901760 kB MemFree: 66752 kB

User avatar
Ed_P
Contributor
Contributor
Posts: 3070
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: USM bug reports

Post#416 by Ed_P » 27 May 2017, 21:50

^ 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.
Ed

Evan
Warlord
Warlord
Posts: 519
Joined: 11 Apr 2016, 09:00
Distribution: Anything Cinnamon
Location: London

Re: USM bug reports

Post#417 by Evan » 27 May 2017, 22:29

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? Image

If you can't get files by a direct command then how is a script going to resolve them for what is needed?

Image

User avatar
brokenman
Site Admin
Site Admin
Posts: 5439
Joined: 27 Dec 2010, 03:50
Distribution: Porteus v3.2rcX all desktops
Location: Brazil
Contact:

Re: USM bug reports

Post#418 by brokenman » 27 May 2017, 23:28

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.
How do i become super user?
Wear your underpants on the outside and put on a cape.

Evan
Warlord
Warlord
Posts: 519
Joined: 11 Apr 2016, 09:00
Distribution: Anything Cinnamon
Location: London

Re: USM bug reports

Post#419 by Evan » 28 May 2017, 00:12

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?
Last edited by Evan on 28 May 2017, 02:42, edited 1 time in total.

User avatar
Ed_P
Contributor
Contributor
Posts: 3070
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: USM bug reports

Post#420 by Ed_P » 28 May 2017, 00:30

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.
Ed

Post Reply