[Slackbuilds-users] .../sbo/repo exists and is not empty. Exiting.

[Jim]

On Fri, Oct  4, 2024 at 12:16 (+0100), Habs wrote:

> On Thu, 3 Oct 2024, Jim wrote:

>> On Wed, Oct  2, 2024 at 20:27 (+0100), Habs wrote:

>>> On Wed, 2 Oct 2024, Jim wrote:

>>> > Hi,

>>> > every now and then when I run sbocheck it says
>>> > Updating SlackBuilds tree...
>>> > and then nothing else happens.  Eventually, I ^C and I get
>>> >        ^CCould not sync from https://git.slackbuilds.org/slackbuilds/.

>>> > But then when I try it again, I get
>>> >        .../sbo/repo exists and is not empty. Exiting.
>>> > (where "..." is the path to when I keep it that is not of interest).

>>> > Aside from deleting the repository and downloading the whole thing again, is
>>> > there a better way of recovering from this problem?

>>> > Thanks.
>>> > Jim

>>> good day

>>> do you have the REPO value set in the .conf file
>>> it has been said that having it set helps stability

>>> this is used here and has worked fine for a long time:
>>> REPO=https://gitlab.com/SlackBuilds.org/slackbuilds.git

>> Yes, I have
>> REPO=https://git.slackbuilds.org/slackbuilds/
>> and have had that for quite a while.

>> Jim


> That REPO line url you have, does not point to a repository as such...it is
> like an index/header page.  If it worked previously I can't offer an
> explanation, however, if you put in the address you have and then the one I
> supplied and take a look ...  as per the sbotools instructions, the URL has
> to point to a correctly formatted specific repository.
 
> Hope that helps.

It not only worked previously, it works still.  My problem is not that it
does not work, my problem is that sometimes sbocheck fails and does
something to my local repository which requires fixing by hand.  If you
re-read my original message you will see what I am trying to find out is
whether there is a fix other than "completely delete and restart".

On the other hand, it is interesting that among other working values for
the repo, one suggestion was rsync:..., which may not be as fragile as the
one I have (this remains to be seen).

Just for completeness, I did not pull the URL I am currently using out of
thin air, someone (I believe on this list) suggested that some time ago.

                                Jim