USM bug reports

[Rava]

And another update

Silly my was wrong, http://sourceforge.net/projects/usm/files/ does indeed give sha1 and md5 checksum info, and I confirmed that both the md5sums of my local txz or xzm are okay, same as on sourceforge:

Code: Select all

c3a445d65751f0ef9a32aa6c466d4e20  usm-latest-0.0-noarch-1.txz
280a9db46ee87397d44a293a2731394f  usm-latest-0.0-noarch-1.xzm

[Rava]

So, I started up another system and removed my local settings prior starting and updating usm, and alas! all worked as it should, I was finally able to download graphicsmagix with all dependencies. The strange thing, I don't have a single setup file related to usm in my local settings, so a random other setting must somehow mess up usm's behaviour, but I cannot figure out what that can be...

[Ed_P]

so a random other setting must somehow mess up usm's behaviour, but I cannot figure out what that can be...

In some versions of USM there were problems with "white" files. Maybe your settings have some.

http://forum.porteus.org/viewtopic.php? ... 182#p25178
http://forum.porteus.org/viewtopic.php? ... 151#p25162
http://forum.porteus.org/viewtopic.php? ... 151#p25178

They can be manually deleted.

[brokenman]

In some versions of USM there were problems with "white" files.

This is misinformation. USM has nothing to do with whiteout files. If the problem is related to whiteout files then the version of USM is irrelevant.

[Rava]

Ed_P, I don't use any save.dat, so that cannot be the issue.
I checked: not a single '.wh.*' file in my local settings module,

Brokenman, how do you suggest I narrow down my issue? I don't want to have to remove my local settings, and only apply one changed file at a time, checking if usm still works okay after that, and then apply the next of my local settings, cause that would take days to accomplish...

[brokenman]

I don't want to have to remove my local settings, and only apply one changed file at a time, checking if usm still works okay after that, and then apply the next of my local settings, cause that would take days to accomplish.

I can't think of another way to find out what is causing the trouble. It is exactly what I do all the time to track down problems. Not always one by one. You can group changes and then isolate the problem in a matter of hours.

[Slaxmax]

I have updated usm database but
In http://mirrors.slackware.com/slackware/ ... slackware/
exist packages available that do not appear in usm

for example in repo exist mesa-11.1.1-i586-1.txz

but in usm

Code: Select all

root@porteus:/home/guest# usm -s mesa

mesa-9.1.7-i486-1.txz was found in slackware [downgrade]
Packages found:   1 

Use:   usm -i <package>  for more info
Use:   usm -g <package>  to download

mesa 9.1.7?

[Bogomips]

^ Link is Slackwar Current, is it not? AFAIK usm only does up to 14.1

[Slaxmax]

you are correct

[Ed_P]

Could not find, when attempting to download alien flashplayer update.

[Ed_P]

May not matter. Current flashplayer for Linux is 643 and the highest USM has is only 637. A dying system.

[rchase]

May not matter. Current flashplayer for Linux is 643 and the highest USM has is only 637. A dying system.

I certainly hope that Flash is dying!

[Ed_P]

from=/ISOs/Porteus-RazorQT-v3.0.1-i486-nu.iso

Code: Select all

sh-4.2# usm -u all
 Starting alien 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/alien/CHECKSUMS.md5.gz: not in gzip format
          

==============================================================================
WARNING!        WARNING!        WARNING!        WARNING!        WARNING!
==============================================================================
One or more errors occurred while usm was running:                       
 
FATAL ERROR!
usm update_database 213
Could not decompress: CHECKSUMS.md5.gz
 
============================================================================== 


sh-4.2# 

[Rava]

from=/ISOs/Porteus-RazorQT-v3.0.1-i486-nu.iso

Code: Select all

Could not decompress: CHECKSUMS.md5.gz
 

Please find this CHECKSUMS.md5.gz and use file CHECKSUMS.md5.gz and tell us what kind of file that really is.

I had this error as well in the past, turned out that the file was not really gzipped, but either not compressed or used a different compressor and had the wrong file ending.

It would help when you could tell what kind of file we deal with.

@brokenman:
When any file error occurs, it should be easily implemented to have a error function, that executes e.g. "file $ERROR-FILENAME" and the user would get an useful info what kind of file that really was, and when he posts the screenshot you would get the info ASAP as well...

[brokenman]

What would you suggest?

The information given is sufficient for me to understand. Perhaps not so for a user.

Code: Select all

gzip: /var/usm/alien/CHECKSUMS.md5.gz: not in gzip format
FATAL ERROR!
usm update_database 213
Could not decompress: CHECKSUMS.md5.gz

Either the file format changed or the download was interrupted resulting in a file that is corrupt.