Q: Storeman complains about a not existing source - what can i do?

kan_ibal · 2 November 2023 10:18

The latest is 0.3.7 :).

kkoenders · 2 November 2023 10:31

I had the same issues: Storeman complaining about a non-existing source, storeman version 0.3.2 and no new updates (of Storeman, other apps downloaded with Storeman were updated regularly).
I uninstalled Storeman, downloaded the storeman-installer from openrepos.net (Storeman Installer | OpenRepos.net — Community Repository System) and ran it. Now I’m on version 0.3.7

kan_ibal · 2 November 2023 10:53

Maybe a repository of Storeman is missing in Storeman 3.2/3.3 (has it changed?) hence the error and lack of update?

Maguro28 · 2 November 2023 10:58

IMHO the Storeman OBS caused the message.

Seven.of.nine · 2 November 2023 14:53

My Storeman version is 0.3.7.

Then I’ll simply ignore it like until now and wail till it becomes better from itself. The app works, I can browse and install apps.

Seven.of.nine · 2 November 2023 16:09

The one-liner returns:

[defaultuser@VollaPhone ~]$ ssu lr | fgrep -v jolla | awk '/\.\.\./ {print $NF}' | while read line; do curl -I $line; done
WARNING: ssu.ini does not seem to be writable. Setting values might not work.
HTTP/1.1 301 Moved Permanently
Server: nginx/1.16.1
Date: Thu, 02 Nov 2023 16:06:26 GMT
Content-Type: text/html; charset=iso-8859-1
Connection: keep-alive
Location: https://repo.sailfishos.org/obs/nemo:/testing:/hw:/volla:/yggdrasil:/4.4.0.72/sailfish_4.4.0.72_aarch64/
Vary: Accept-Encoding

HTTP/1.1 200 OK
Server: nginx/1.16.1
Date: Thu, 02 Nov 2023 16:06:27 GMT
Content-Type: text/html;charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding

HTTP/1.1 200 OK
Server: nginx/1.16.1
Date: Thu, 02 Nov 2023 16:06:28 GMT
Content-Type: text/html;charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding

HTTP/1.1 301 Moved Permanently
Server: nginx
Date: Thu, 02 Nov 2023 15:58:20 GMT
Content-Type: text/html
Content-Length: 184
Connection: keep-alive
Location: http://sailfish.openrepos.net/247/personal/main/

HTTP/1.1 301 Moved Permanently
Server: nginx
Date: Thu, 02 Nov 2023 15:58:21 GMT
Content-Type: text/html
Content-Length: 184
Connection: keep-alive
Location: http://sailfish.openrepos.net/Polleke/personal/main/

HTTP/1.1 301 Moved Permanently
Server: nginx
Date: Thu, 02 Nov 2023 15:58:22 GMT
Content-Type: text/html
Content-Length: 184
Connection: keep-alive
Location: http://sailfish.openrepos.net/WerkWolf/personal/main/

HTTP/1.1 301 Moved Permanently
Server: nginx
Date: Thu, 02 Nov 2023 15:58:23 GMT
Content-Type: text/html
Content-Length: 184
Connection: keep-alive
Location: http://sailfish.openrepos.net/ade/personal/main/

HTTP/1.1 301 Moved Permanently
Server: nginx
Date: Thu, 02 Nov 2023 15:58:23 GMT
Content-Type: text/html
Content-Length: 184
Connection: keep-alive
Location: http://sailfish.openrepos.net/adel/personal/main/

HTTP/1.1 301 Moved Permanently
Server: nginx
Date: Thu, 02 Nov 2023 15:58:24 GMT
Content-Type: text/html
Content-Length: 184
Connection: keep-alive
Location: http://sailfish.openrepos.net/balta/personal/main/

HTTP/1.1 301 Moved Permanently
Server: nginx
Date: Thu, 02 Nov 2023 15:58:25 GMT
Content-Type: text/html
Content-Length: 184
Connection: keep-alive
Location: http://sailfish.openrepos.net/carmenfdezb/personal/main/

HTTP/1.1 301 Moved Permanently
Server: nginx
Date: Thu, 02 Nov 2023 15:58:26 GMT
Content-Type: text/html
Content-Length: 184
Connection: keep-alive
Location: http://sailfish.openrepos.net/kan/personal/main/

HTTP/1.1 301 Moved Permanently
Server: nginx
Date: Thu, 02 Nov 2023 15:58:26 GMT
Content-Type: text/html
Content-Length: 184
Connection: keep-alive
Location: http://sailfish.openrepos.net/llelectronics/personal/main/

HTTP/1.1 301 Moved Permanently
Server: nginx
Date: Thu, 02 Nov 2023 15:58:27 GMT
Content-Type: text/html
Content-Length: 184
Connection: keep-alive
Location: http://sailfish.openrepos.net/olf/personal/main/

HTTP/1.1 301 Moved Permanently
Server: nginx
Date: Thu, 02 Nov 2023 15:58:28 GMT
Content-Type: text/html
Content-Length: 184
Connection: keep-alive
Location: http://sailfish.openrepos.net/slava/personal/main/

HTTP/1.1 200 OK
Server: nginx/1.16.1
Date: Thu, 02 Nov 2023 16:06:37 GMT
Content-Type: text/html;charset=UTF-8
Connection: keep-alive
Vary: Accept-Encoding

[defaultuser@VollaPhone ~]$

and regarding your questions in post #11:
1: I didn’t change anything, only deinstalled and reinstalled.
2. Yes, it occured repeatedly, and ssh access to phone was broken.
3. Storeman complained only about one.

adekker · 2 November 2023 23:15

I was stuck at version 0.3.2 as well and disable/enable of the storeman repo gave a “Could’t find the specific repository”.
It turned out that the repo definition of “harbour-storeman-obs” was gone from /etc/ssu.ini for a unknown reason. De-installing Storeman and using the Storeman installer will restore the harbour-storeman-obs entry in ssu.ini and will install the latest version of Storeman.

olf · 4 November 2023 01:31

Many thanks to you all, @adekker, @Seven.of.nine, @kan_ibal, @Maguro28, @pherjung and @kkoenders, your messages are helpful.

Except for @Seven.of.nine’s “one liner”-output, everything points to the observation @adekker made:
ssu lr | grep '.-obs' (or equivalently
grep '.-obs' /etc/ssu/ssu.ini ) outputs nothing, i.e. Storeman’s own repo was deleted from the SSU repo config in /etc/ssu/ssu.ini . This explains why there were occasionally reports that Storeman’s self-updating did not work, resulting in being stuck on an old version, but this issue was never reproducible.

Now the more specific question is, what deletes Storeman’s OBS repo entry when (i.e. triggered by what)? Currently I have no idea.
But at least we now know how to easily test for (see paragraph above) and fix this specific issue (by removing Storeman and using the Storeman Installer). Thank you very much, Arno.

Side notes:

@Maguro28, the switch from Mentaljam’s SFOS-OBS repository to mine happened with the release of Storeman 0.2.12 on 2022-03-15, since then Storeman’s own repository for self-updating stayed the same.
Yes, this is a completely different server than OpenRepos, hence no software installed by Storeman is affected.

@Seven.of.nine’s “one liner”-output renders me puzzled: So many 301s (“Moved Permanently”) for OpenRepos repositories, which definitely exist (among them mine). I wonder, if there is still something wrong with your local network configuration. I assume you tested via WLAN; if so, please deactivate WLAN on your phone and try @nephros’ “one-liner” again, now via mobile network. Do you still see the same result (many 301s) or only 200s (“OK”)?

jenix · 4 November 2023 07:53

I’m experiencing the same issues (currently on Storeman 0.3.2). The HTTP 301 redirects occur as the url of the repos are configured with https and the webserver returns a 301 to the http location.
e.g.:
curl -I Index of /ade/personal/main/ → 301 to http://sailfish.openrepos.net/ade/personal/main
Is this intended?
Indeed it seems that the storeman OBS repo is missing for me as well. By uninstalling and then installing storeman-installer, it got added again:
harbour-storeman-obs … Index of /obs/home:/olf:/harbour-storeman/4.5.0.24_aarch64

I wonder if it would have been sufficient to simple add the obs repo to /etc/ssu/ssu.ini, but couldn’t test it as i couldn’t find the repo url.

Seven.of.nine · 4 November 2023 10:03

The One-liner seems to show the same if phone (Volla) is connected by cellular data and WLAN is off. Since I can’t c+p the content of the phones CLI, here’s a screenshot showing parts of the output.

It can’t be a basic network problem on my side, because it shows the first two and the last one entry as OK, while the 11 in the middle are shown as ‘moved permanently’.

The 3 working repos have no name. They all have
HTTP/1.1 200 OK + Server: nginx/1.16.1 + Connection: keep-alive, no Content-Length entry!

while the following not working repos have:
HTTP/1.1 301 Moved Permanently + Server: nginx (nothing else) + Connection: keep-alive (!) + Content-Length: 184

The 11 - edit: strange reporting - repos are:
247
Polleke
WerkWolf
ade
adel
balta
carmenfdezb
kan
llelectronics
olf
slava

OT: how can I copy the content of the CLI screen on the phone and paste it into a forum message?

adekker · 4 November 2023 11:01

@Seven.of.nine these messages do not say it is not working. It is just redirecting from http to https via nginx. I am sure my repo (ade) works fine. I get the same messages.

@jenix the entry in /etc/ssu/ssu.ini should be harbour-storeman-obs=https://repo.sailfishos.org/obs/home:/olf:/harbour-storeman/%(release)_%(arch)/

Seven.of.nine · 4 November 2023 11:50

Thanks for your reply!
Yes it works fine, I could successfully install InfraView a few minutes ago. Thanks for this app!!

ric9k · 4 November 2023 15:24

Do you mean: Copy the output of the CLI while ssh’ing on the PC, or on the phone’s terminal directly?

(I hope not to offend your existing knowledge. Just summerizing)
On the PC, it is CTRL + SHIFT + C, then you can paste where you want (telegram, mail…) or into a new text file on the phone.

On the phone, select copy instead of scroll into the Terminal preferences, then you can copy.
It is sometimes useful to paste into a note in otder to reorganize newlines.

Seven.of.nine · 4 November 2023 15:32

I mean on the phones SFOS CLI select the text on the terminal screen and then c+p whats there and paste it into a forum post i make on the phones browser.

While trying to connect Storeman via cellular data I can’t SSH into the phone from computer at the same time. On the phone’s CLI I found no way to select the terminal output and copy to clipboard.

ric9k · 4 November 2023 15:44

In terminal, press the three small lines up right.
You’ll have this menu:

On the right, into ‘Drag mode’, you can select ‘select’
Then, as usual in SFOS (alas no CTRL-c/p), the selected text will be into the clipboard.

Seven.of.nine · 4 November 2023 16:30

Thank you, now I understand. Sorry but I really didn’t find this before!
OT: Another question: How can I select if the intended selection is higher than the screen? Can I also mark a beginning-of-selection, then scroll down and mark an end-of-selection?

nephros · 4 November 2023 18:30

I can only describe that when using screen.

Use ctrl-a esc to enter ‘scroll back’ mode, navigate up to the start of what you want to select. Hit Space to mark the start. Move to the end of the selection, hit Space again.

Now you can use Ctrl-a ] (that’s closing-bracket) to paste.

olf · 4 November 2023 22:48

Oh, yes; I missed to see that late at night. The redirections solely alter the protocol prefix from ~~http: to https:~~ https: to http: .

~~So the question is now, how come that some OpenRepos repositories were subscribed with an http address and some with an https one?~~

Cross-check on my “production” device: I have not a single http: prefixed address in /etc/ssu/ssu.ini, they all use https: directly, regardless if they address a repository at OpenRepos (78) or not (6).

olf · 4 November 2023 22:57

On the phone
Without using the screen utility, the handling is a bit tricky: Scroll back until you have the beginning of the intended selection on the screen (in scroll mode, obviously), switch to select mode, put a finger at the start of the selection and pull it down to the bottom of the screen; move your finger a bit upwards from the lower edge of the screen to stop scrolling down. Lift you finger when you put the end of the selection at the right spot, then select Copy in fingerterm's / toeterm's menu.
On a computer, using ssh / slogin to access the phone
Depends on the terminal program used, but is usually much easier.

jenix · 5 November 2023 07:18

Thanks for the reply. It is indeed the other way around: the repo urls are saved with https in the ssu.ini, but the openrepo server downgrades them to http (which pose some security issues). That’s why I’m wondering if this is intentional. What’s the best way to address this issue separately, as it seems unrelated with the initial issue?