Page 29 of 36

Re: USM bug reports

Posted: 28 May 2017, 00:55
by Evan
I don't understand the reasoning?

Why wasn't system checked (tomorrow) months ago to see if there is a failure somewhere when the same USM errors were being reported that got to the point that Bogomips wanted a Module reserve that Brokenman was happy to go along with as a fix?

I'm completely dumbfounded and confused.... Image

Re: USM bug reports

Posted: 28 May 2017, 05:12
by Ed_P
Evan wrote:I'm completely dumbfounded and confused.... Image
I don't know about the dumbfounded but you have always been confused. :D

Re: USM bug reports

Posted: 30 May 2017, 01:11
by Bogomips
Been dabbling with heuristic fix/workaround of sync issue to get package. If anyone desperate enough to try/test, let us know, and I'll share in Intermediate/Advanced section. :wink:

flashplayer-plugin

Code: Select all

root@porteus:/home/guest# usm -g flashplayer
find: `/tmp/xdg-runtime-guest/gvfs': Permission denied

 The following items were found.
 Choose an number to confirm. 
 ctrl+c to quit

1) flashplayer-plugin-11.2.202.635-x86_64-2sl.txz
2) flashplayer-plugin-25.0.0.127-x86_64-1_slonly.txz
3) flashplayer-plugin-25.0.0.148-x86_64-1alien.txz
#? 3

Processing:   flashplayer-plugin-25.0.0.148-x86_64-1alien.txz
Ignored libraries: libkdeui.so,libkutils.so,libkdecore.so,libQt,

Libraries required:  22
Libraries found in system: 22
Libraries to resolve: 0



=============
HEURISTIC USM
=============

flashplayer-plugin-25.0.0.148-x86_64-1alien.txz superseded by flashplayer-plugin-25.0.0.171-x86_64-1alien.txz

 The following packages are required.
flashplayer-plugin-25.0.0.171-x86_64-1alien.txz [7180K] [upgrade]

Total size: 7 MB

 Press [r] to remove packages, [q] to quit, or enter to start downloading.
kodi

Code: Select all

kodi_2017-05-30_01:39:46
root@porteus:/home/guest# usm -g kodi
find: `/tmp/xdg-runtime-guest/gvfs': Permission denied

 The following items were found.
 Choose an number to confirm. 
 ctrl+c to quit

1) kodi-16.1-x86_64-1gv.txz
2) kodi-17.1-x86_64-1_slonly.txz
#? 2

Processing:   kodi-17.1-x86_64-1_slonly.txz 
Ignored libraries: 

Libraries required:  69
Libraries found in system: 64
Libraries to resolve: 5

Processing library: libcrossguid.so.0
Processing library: libmicrohttpd.so.10
Processing library: libmysqlclient.so.18

 More than one package contains:  libmysqlclient.so.18
mariadb-10.0.26-x86_64-1.txz            25836K  slackware
mariadb-10.0.30-x86_64-1_slack14.2.txz  25952K  slackwarepatches

 The following items were found.
 Choose an number to confirm. 
 ctrl+c to quit

1) mariadb-10.0.26-x86_64-1.txz
2) mariadb-10.0.30-x86_64-1_slack14.2.txz
#? 2
Processing library: libtinyxml.so.0
Processing library: libyajl.so.2


Processing:   crossguid-20160705-x86_64-1_slonly.txz 
Ignored libraries: 

Libraries required:  4
Libraries found in system: 4
Libraries to resolve: 0



Processing:   libmicrohttpd-0.9.42-x86_64-1_slonly.txz 
Ignored libraries: 

Libraries required:  15
Libraries found in system: 13
Libraries to resolve: 2

Processing library: libmicrospdy.so.0
Processing library: libsasl2.so.2


Processing:   mariadb-10.0.30-x86_64-1_slack14.2.txz 
Ignored libraries: 

Libraries required:  17
Libraries found in system: 16
Libraries to resolve: 1

Processing library: libJudy.so.1


Processing:   tinyxml-2.6.2-x86_64-2ponce.txz 
Ignored libraries: 

Libraries required:  3
Libraries found in system: 3
Libraries to resolve: 0



Processing:   yajl-2.1.0-x86_64-2ponce.txz 
Ignored libraries: 

Libraries required:  1
Libraries found in system: 1
Libraries to resolve: 0



Processing:   judy-1.0.5-x86_64-1.txz 

 WARNING: unresolved dependencies remain.
libsasl2.so.2

=============
HEURISTIC USM
=============

kodi-17.1-x86_64-1_slonly.txz superseded by kodi-17.3-x86_64-1_slonly.txz

 The following packages are required.
crossguid-20160705-x86_64-1_slonly.txz [12K] [not installed]
judy-1.0.5-x86_64-1.txz [132K] [not installed]
kodi-17.3-x86_64-1_slonly.txz [32860K] [not installed]
libmicrohttpd-0.9.42-x86_64-1_slonly.txz [224K] [not installed]
mariadb-10.0.30-x86_64-1_slack14.2.txz [25952K] [not installed]
tinyxml-2.6.2-x86_64-2ponce.txz [56K] [not installed]
yajl-2.1.0-x86_64-2ponce.txz [40K] [not installed]

Total size: 59 MB

 Multiple packages were detected.
 Would you like to merge the packages into one module? [y/n]
 Would you like to create a subfolder for the files? [y/n]
 Would you like to install the package/s? (custom paths are supported) [y/n]

 Press [r] to remove packages, [q] to quit, or enter to start downloading.

Re: USM bug reports

Posted: 30 May 2017, 05:16
by Evan

Code: Select all

usm -g flashplayer
flashplayer-plugin-25.0.0.148-x86_64-1alien.txz
alien Version 148

Code: Select all

usm -s flashplayer
flashplayer-plugin-25.0.0.171-x86_64-1alien.txz
alien Version 171

< -g and -s >

Commands shows different package numbers when using the mirrors.

Re: USM bug reports

Posted: 31 May 2017, 10:42
by Bogomips
^ Old hat. That was what brokenman was trying to fix on Sunday.

Re: USM bug reports

Posted: 31 May 2017, 10:51
by Evan
I wasn't putting it forward as a new bug , it was in regards to you using -g for the heuristic fix.

Re: USM bug reports

Posted: 31 May 2017, 15:48
by Bogomips
^ Doesn't matter. Comes out in the wash. :)

Re: USM bug reports

Posted: 31 May 2017, 21:34
by Ed_P
Bogomips wrote:Been dabbling with heuristic fix/workaround of sync issue to get package. If anyone desperate enough to try/test, let us know, and I'll share in Intermediate/Advanced section. :wink:
https://forum.porteus.org/viewtopic.php ... 568#p55562

Re: USM bug reports

Posted: 01 Jun 2017, 02:11
by brokenman
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?
Yes it certainly does. As I said I will fix it when I get around to it. If this time frame is not to your liking then you'd best find another package manager. At this moment in my life, the priority is putting food on the table. My real life job does this and my free unpaid hobby does not. Make a nice donation to Porteus and I could consider shuffling my priorities a little, otherwise have patience. Complaining in the manner that you are currently doing does little to motivate me.
Why wasn't system checked (tomorrow) months ago to see if there is a failure somewhere when the same USM errors were being reported that got to the point that Bogomips wanted a Module reserve that Brokenman was happy to go along with as a fix?
You sound like a paying customer that has a problem with his car that is still under warranty. I ask for a little patience at this time. This half of this year was a big one for me. Things will get better for me, but until they do I have to prioritize my activities.

PS:
I'd like to add that USM is quite a complex set of scripts (for my meager abilities). It takes time to dig through, which I have been doing in the early hours of the morning since Sunday, and reading the above just sucked the wind out of my sails.

Re: USM bug reports

Posted: 01 Jun 2017, 05:02
by Ed_P
Don't be down brokenman. :( Evan was probably just frustrated when he wrote that. It's not uncommon for frustrated users to make demanding statements. We understand that this is an unpaid hobby for you and real life takes priority over it. And we have faith that you will find the problem and fix it as soon as you can. And know that you have members willing to test whatever fix you may find for you. :)

Re: USM bug reports

Posted: 01 Jun 2017, 05:22
by Evan
@Brokenman

WTF!!! :shock: Image
Ed_P wrote:
Evan wrote:I'm completely dumbfounded and confused.... Image
I don't know about the dumbfounded but you have always been confused. :D
This , and what Ed said ---------------^

An attempt to understand weeks/months of silence through observational questions is neither a complaint or any type of demand, Its just a desire to understand , be less confused and that someone on here can help make sense of it all.

There is nothing i need from USM so it makes no actual difference to me if or when the issue is resolved , it is however frustrating when there is an issues that doesn't seem to be acknowledged and the blame is put elsewhere...........

I happen to care about your free project and you have effectively thrown that caring in my face.

Re: USM bug reports

Posted: 01 Jun 2017, 12:10
by Ed_P
Alright guys, no more postings after 11pm. People are too tired, emotions too thin. :(
Evan wrote:This , and what Ed said ---------------^
I was KIDDING!! TEASING. Joking. Good grief. We're friends so I was certainly not trying to insult you.

Re: USM bug reports

Posted: 01 Jun 2017, 12:22
by Evan
Either you misunderstood my post or i'm not very good at articulating myself , i'm guessing the latter. :D

You never insulted me Buddy , it amused as it was intended , i was agreeing with your joking and your previous posts for the fact that there is some truth in it. :wink: :friends:

And you're right again about not posting when late and tired , this is like a lovers tiff , maybe i should sleep on the couch. :)

:good:

Re: USM bug reports

Posted: 01 Jun 2017, 17:46
by Bogomips
Evan wrote:this is like a lovers tiff , maybe i should sleep on the couch. :)
And rightly so! :twisted: Not pulling your weight? Sleep on couch! :x

Re: USM bug reports

Posted: 04 Jun 2017, 18:14
by brokenman
In direct reply to my post you wrote:
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?
Does this NOT seem a little aggressive to you? I have been working non-stop on Porteus for something like 10 years. Many hours per day. That epoc of my life has changed and now I must spend between 11pm and 3am working on it. This pause began 6 months ago. Put yourself in my shoes. You spend that much time of your life giving something free and you are faced with the above reply. And you say I threw something in your face? Please.

Then you wrote:
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 latest version was only released in December/January. The system for a module repository has already been implemented for the last two versions of Porteus. I also made a call to action for people to start populating the repository with "Bundles" which never eventuated, and yes waiting 6 hours DID fix the problem in February. The current problems started in April according to my logs and should now be fixed (I think I located the problem).

Then you wrote:
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?
So I am ignoring all logic and reason? I acknowledged the problem. Fixing it was something that would take time. Have you ever tried to dig through the code?

Then you wrote:
An attempt to understand weeks/months of silence through observational questions is neither a complaint or any type of demand, Its just a desire to understand , be less confused and that someone on here can help make sense of it all.
It sure comes across as a major complaint.

Then you wrote:
There is nothing i need from USM so it makes no actual difference to me if or when the issue is resolved
If it means nothing to you why are you so vocal about it?

--------

So, that's my rant. It's off my chest and hold no grudges. I just ask for a little patience for this relatively short pause in maintenance. :beer:
If someone could check that the LIBS.TXT error is gone I would appreciate it.