On 26/07/2019 23.38, Knurpht-openSUSE wrote:

Op vrijdag 26 juli 2019 23:34:35 CEST schreef Carlos E. R.:

...

On 26/07/2019 23.07, Knurpht-openSUSE wrote:

...

Try zypper in opi

Then f.e. opi dog

Notice that the post to which you are replying to is not visible to us, or the threading headers are missing.

No, my mistake. I put the 'Re:' there ....... But you have your webpin replacement

Ah, that's very nice! :-D

Op vrijdag 26 juli 2019 23:38:01 CEST schreef Dave Howorth:

On Fri, 26 Jul 2019 23:07:30 +0200

Knurpht-openSUSE knurpht@opensuse.org wrote:

...

Try zypper in opi

Then f.e. opi dog

FWIW, I just did that. Here's the result:

# zypper in opi Loading repository data... Warning: Repository 'openSUSE-Leap-15.0-Update-Debug-Non-Oss' appears to be outdated. Consider using a different mirror or server. Warning: Repository 'openSUSE-Leap-15.0-Update-Non-Oss' appears to be outdated. Consider using a different mirror or server. Reading installed packages... 'opi' not found in package names. Trying capabilities. No provider of 'opi' found. Resolving package dependencies...

Nothing to do.

Now given the comments by Klaus Vink Slott list-s@vink-slott.dk on another thread, I suspect he's likely to be using a different mirror, so perhaps the problem is worthy of more widespread investigations and ...

If the problem might be related to the mirror I'm using, why doesn't zypper at least tell me what that mirror is? Or better yet, try some other mirror and tell me that the problem is widespread?

O crap, I did not check whether opi exists for Leap 15.X

On 26/07/2019 23.38, Dave Howorth wrote:

On Fri, 26 Jul 2019 23:07:30 +0200 Knurpht-openSUSE <> wrote:

...

Try zypper in opi

Then f.e. opi dog

FWIW, I just did that. Here's the result:

# zypper in opi Loading repository data... Warning: Repository 'openSUSE-Leap-15.0-Update-Debug-Non-Oss' appears to be outdated. Consider using a different mirror or server. Warning:

Ignore this error.

Repository 'openSUSE-Leap-15.0-Update-Non-Oss' appears to be outdated. Consider using a different mirror or server.

ignore this error.

Reading installed packages... 'opi' not found in package names. Trying capabilities. No provider of 'opi' found. Resolving package dependencies...

Nothing to do.

Now given the comments by Klaus Vink Slott list-s@vink-slott.dk on another thread, I suspect he's likely to be using a different mirror, so perhaps the problem is worthy of more widespread investigations and ...

If the problem might be related to the mirror I'm using, why doesn't zypper at least tell me what that mirror is? Or better yet, try some other mirror and tell me that the problem is widespread?

It is not really an error. It is a... not forecasted consequence by the programmer. Nothing to worry about, just noise.

Op zaterdag 16 mei 2020 03:28:28 CEST schreef Patrick Shanahan:

• Knurpht-openSUSE knurpht@opensuse.org [01-01-70 12:34]:

...

Try zypper in opi

Then f.e. opi dog

does opi still work for you?

21:26 crash:~ > opi dog Searching.Empty String at /usr/bin/opi line 327. 21:26 crash:~ > .......

and the process must be killed by hand

Seeing the same now.

* Knurpht-openSUSE knurpht@opensuse.org [05-15-20 21:42]:

Op zaterdag 16 mei 2020 03:28:28 CEST schreef Patrick Shanahan:

...

• Knurpht-openSUSE knurpht@opensuse.org [01-01-70 12:34]:

...

Try zypper in opi

Then f.e. opi dog

does opi still work for you?

21:26 crash:~ > opi dog Searching.Empty String at /usr/bin/opi line 327. 21:26 crash:~ > .......

and the process must be killed by hand

Seeing the same now.

22:23 crash:~ > osc maintainer opi Server returned an error: HTTP Error 401: Unauthorized

:(

16.05.2020 05:24, Patrick Shanahan пишет:

• Knurpht-openSUSE knurpht@opensuse.org [05-15-20 21:42]:

...

Op zaterdag 16 mei 2020 03:28:28 CEST schreef Patrick Shanahan:

...

• Knurpht-openSUSE knurpht@opensuse.org [01-01-70 12:34]:

...

Try zypper in opi

Then f.e. opi dog

does opi still work for you?

21:26 crash:~ > opi dog Searching.Empty String at /usr/bin/opi line 327. 21:26 crash:~ > .......

and the process must be killed by hand

Seeing the same now.

22:23 crash:~ > osc maintainer opi Server returned an error: HTTP Error 401: Unauthorized

:(

OBS migrated to new account database. Surprise.

OBS API needs authentication. This program goes via dedicated proxy server which performs OBS login with fixed account, which is why users themselves do not need OBS logon. Seems account used for this was not migrated.

https://github.com/openSUSE-zh/opi/issues/4

This adds yet another unknown server to equation.

On Sat, 16 May 2020 09:21:04 -0400 Patrick Shanahan paka@opensuse.org wrote:

• Patrick Shanahan paka@opensuse.org [05-15-20 21:29]:

...

• Knurpht-openSUSE knurpht@opensuse.org [01-01-70 12:34]:

...

Try zypper in opi

Then f.e. opi dog

does opi still work for you?

21:26 crash:~ > opi dog Searching.Empty String at /usr/bin/opi line 327. 21:26 crash:~ > .......

and the process must be killed by hand

direct msg to author/maintainer Guo Yunhe described above problem filed requested bug report on github https://github.com/openSUSE-zh/opi/issues/27

issue resolved within one hour

Yep, I can confirm that after I patch the spinner out of the source code, it runs:

$ ./opi dog

1. lapdog 2. dogtail 3. cdogs-sdl 4. python2-watchdog 5. python3-watchdog 6. python2-dogpile.cache 7. python3-dogpile.cache 8. python2-watchdog-doc 9. python3-watchdog-doc 10. freeipmi-bmc-watchdog 11. guarddog 12. guidedog 13. ghc-datadog 14. OpenCPN-watchdog_pi 15. ghc-datadog-devel 16. python2-dogpile-cache 17. python3-dogpile-cache 18. watchdog 19. golang-github-data-dog-sqlmock 20. sheepdog 21. dogecoind 22. dogecoin-doc 23. dogecoin-qt5 24. dogecoin-test 25. dogecoin-utils 26. python3-dogslow Choose a number(0 to quit): 20 You have selected package name: sheepdog 1. home:furrylinx ! | 0.9.2 | x86_64 Choose a number(0 to quit): 0 $

and published to https://download.opensuse.org/repositories/utilities/openSUSE_Factory/

Thanks Guo