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

[Slack Coder]

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

REPO=rsync://slackbuilds.org/slackbuilds/15.0/

Sbotools uses 'rsync://slackbuilds.org/slackbuilds/$VERSION/' by default 
for Slackware releases.  This way it points to slackbuilds.org directly 
and it locks the slackbuilds version to your Slackware release.

What went wrong before is sbotools has not updated since the 15.0 
release to include it.

On 10/2/24 14:27, 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
>
>
> Habs
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>