Page 4 of 8

Porteus - USM error

Posted: 03 Mar 2018, 23:35
by brokenman
I know SourceForge is under a DoS attack but I thought all the Slackware files were stored on the mirrors' sites.
LIBS.TXT.gz is not a slackware file. It's the file that slackware does not have that USM creates in order to know dependencies. It is stored on sourceforge. I had assumed sourceforge would be a reliable platform to serve files from.

I would be interested in reliable alternatives.

Porteus - USM error

Posted: 04 Mar 2018, 01:54
by Ed_P
Well, according to this: https://twitter.com/sfnet_ops?ref_src=t ... r%5Eauthor SourceForge has been under attack since Feb 25th. I find it hard to believe they're still working on a DoS attack. I heard from another friend that they had moved their system to a new computer and were having technical problems. This has been going on for well over a week at this point.

As for an alternative, I suggest porteus.org for the LIBS.TXT.gz file. Its a very small file so I think the overhead would be minimal. And it could be set as a backup for SourceForge so when they are back up the impact on porteus.org would be negligible.

Porteus - USM error

Posted: 04 Mar 2018, 14:21
by Ed_P
My USM updated fine this morning. :celebrate3: And I am able to browse the SourceForge forums.

Re: Porteus - USM error

Posted: 08 Dec 2018, 11:06
by francois

Code: Select all

root@porteus:~# usm -u all
slackware was updated 310 seconds ago. Skipping.
 Starting slackwarepatches database update 
Downloading: vercheck.txt  DONE
Downloading: CHECKSUMS.md5  DONE
Downloading: MANIFEST.bz2  DONE
Downloading: PACKAGES.TXT  DONE
Downloading: LIBS.TXT.gz  DONE
 There was a problem downloading the file: 
What is there to do?
Thanks.

Porteus - USM error

Posted: 08 Dec 2018, 16:49
by Ed_P

Re: Porteus - USM error

Posted: 11 Dec 2018, 22:03
by Ed_P
Unable to download Thunderbird 60 with Resolve dependencies enabled. LIBS.TXT not found. USM updated, mirrors-slackwarepatches.txt changed from Brazil to Canada to US with same error.

Re: Porteus - USM error

Posted: 12 Dec 2018, 09:14
by francois
It works fine now.

Re: Porteus - USM error

Posted: 12 Dec 2018, 15:55
by Ed_P
Still not working here, even after updating all mirrors and restarting.

When you test francois be sure to check the Resolve Dependencies option. That is what causes the problem.

Re: Porteus - USM error

Posted: 12 Dec 2018, 21:11
by donald
Ed_P wrote:
11 Dec 2018, 22:03
Unable to download Thunderbird 60 with Resolve dependencies enabled. LIBS.TXT not found. USM updated, mirrors-slackwarepatches.txt changed from Brazil to Canada to US with same error.
Hi Ed
This error is misleading because the LIBS.TXT file is present, and it is indeed the
"resolve dependencies" option causing the error.

Why:
If you use USM in CLI mode
usm -s mozilla-thunder
it checks the PACKAGES.TXT file and there mozilla-thunderbird-60.3.3-x86_64-1_slack14.2.txz
is listed.

But when you try to get it
usm -g mozilla-thunderbird-60.3.3
you get a "nothing found for.." error because USM also checks the LIBS.TXT file (for dependencies),
and mozilla-thunderbird-60.3.3 is not listed, so USM throw the LIBS.TXT error.

If you like to test it yourself, copy mozilla-thunderbird-60.3.3-x86_64-1_slack14.2.txz
into the LIBS.TXT file (/var/usm/slackwarepatches/LIBS.TXT in this case) and the error is gone.
(FOR TESTING ONLY)

However, running porteus 4.0 LXDE, I fetched the mozilla-thunderbird-60.3.3-x86_64-1_slack14.2.txz
package, converted to xzm and it runs.
( if everything works like it should has not been tested; I do not use thunderbird and

Code: Select all

root@porteus:/home/guest# ldd /usr/lib64/thunderbird/thunderbird
	linux-vdso.so.1 (0x00007fffe0872000)
	libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f11c5aaa000)
	libdl.so.2 => /lib64/libdl.so.2 (0x00007f11c58a6000)
	libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f11c5528000)
	libm.so.6 => /lib64/libm.so.6 (0x00007f11c518d000)
	libgcc_s.so.1 => /usr/lib64/libgcc_s.so.1 (0x00007f11c4f76000)
	libc.so.6 => /lib64/libc.so.6 (0x00007f11c4b8c000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f11c5cc9000)
does not show that something is missing.)

btw
each repo has its own LIBS.TXT file -- it is not the fault of USM if they are malformed. ;)

Re: Porteus - USM error

Posted: 12 Dec 2018, 22:23
by Ed_P
Thank you donald for your detailed explanation of the problem. :beer:

So the error isn't that LIBS.TXT is missing, it is the module selected isn't in the LIBS.TXT file.
donald wrote:
12 Dec 2018, 21:11
each repo has its own LIBS.TXT file -- it is not the fault of USM if they are malformed. ;)
For clarity by "repo" I assume you mean mirror. How does one get LIBS.TXT problems corrected at the source?

Re: Porteus - USM error

Posted: 12 Dec 2018, 23:57
by donald
For clarity by "repo" I assume you mean mirror.
No, by repo (= short for repository) i meant the various packages provider like
salix,slackware,slacky,ponce etc.

So called mirrors contain the same files as the original (main) server.
They are, or better should be, in sync.
How does one get LIBS.TXT problems corrected at the source?
I have no idea..

Re: Porteus - USM error

Posted: 13 Dec 2018, 16:01
by Ed_P
donald wrote:
12 Dec 2018, 23:57
No, by repo (= short for repository) i meant the various packages provider like
salix,slackware,slacky,ponce etc.
Oh! Glad I asked. Thank you.

So maybe a USM tweak would help clarify the scenario for users. LIBS.TXT not found, Resolve dependencies not an option for this file.

Re: Porteus - USM error

Posted: 16 Dec 2018, 19:36
by Rava
Sorry currently I don't have the time to read all 4 pages if this bug got already addressed:

usm still has the guest/gvfs Permission denied bug:
root@porteus:/5/Porteus_modules# usm -u all
find: `/tmp/xdg-runtime-guest/gvfs': Permission denied
Starting slackware database update
The version was the one shipped with 4.0 I think:
root@porteus:/mnt/sda5/Porteus_modules# usm -v
find: `/tmp/xdg-runtime-guest/gvfs': Permission denied
You are using USM version: 3.2.0

root@porteus:/5/Porteus_modules# usm -u usm
find: `/tmp/xdg-runtime-guest/gvfs': Permission denied
Downloading: vercheck.txt DONE

You have the current USM version.
In my book, when fixed, this should be made into an update module, cause were I an user less knowledgeable about Linux and especially less knowledgeable about Port would consider usm as an integral part of Port.
I presume some users might see this error as a bug of Porteus and could turn them away from us. (Better save than sorry)
Just my 2 cents.

_________________________
Ed_P wrote:
13 Dec 2018, 16:01
donald wrote:
12 Dec 2018, 23:57
No, by repo (= short for repository) i meant the various packages provider like
salix,slackware,slacky,ponce etc.
Oh! Glad I asked. Thank you.

So maybe a USM tweak would help clarify the scenario for users. LIBS.TXT not found, Resolve dependencies not an option for this file.
--> "LIBS.TXT not found, resolving dependencies is not an option for this repository."

File is the wrong word here. (I think, not a native tongue myself)

Re: Porteus - USM error

Posted: 16 Dec 2018, 21:26
by Ed_P
See this posting for a

Code: Select all

find: `/tmp/xdg-runtime-guest/gvfs': Permission denied
report. There is something disturbing with usm
Rava wrote:
16 Dec 2018, 19:36
Ed_P wrote:
13 Dec 2018, 16:01
So maybe a USM tweak would help clarify the scenario for users. LIBS.TXT not found, Resolve dependencies not an option for this file.
--> "LIBS.TXT not found, resolving dependencies is not an option for this repository."

File is the wrong word here. (I think, not a native tongue myself)
A user searching for thunderbird that gets this error sees the name thunderbird under the heading labeled File not repository. And said user may not know what a repository is. And the error may not apply to all files in the repository. :happy62:

Re: Porteus - USM error

Posted: 16 Dec 2018, 21:45
by Rava
Ed_P wrote:
16 Dec 2018, 21:26
A user searching for thunderbird that gets this error sees the name thunderbird under the heading labeled File not repository. And said user may not know what a repository is. And the error may not apply to all files in the repository. :happy62:
Seems by just going with what was quoted I misunderstood stuff. My bad. :oops: