[Slackbuilds-users] sbotools config issues

[fourtysixandtwo]

An instance where seeing the full error message would be helpful.

On Sun, Mar 10, 2024 at 7:30 PM K. Eugene Carlson <kvngncrlsn at gmail.com> wrote:
>
> Hi,
>
> SBo packages that have been added to -current are removed from Ponce's repo to avoid file conflicts, which is why sbotools didn't find python3-wheel and python3-build.
>
> When the "unable to locate" message comes up (and it often does for Python stuff), I just select "y" to ignore and continue. That should work provided that the corresponding Slackware packages have been installed.
>
> Gene
>
> On Mon, Mar 11, 2024 at 9:51 AM J. Milgram <milgram at cgpp.com> wrote:
>>
>>
>> Thanks, and thanks Didier too.
>>
>> ( I misunderstood ... item #15 at https://slackbuilds.org/faq/ says:
>> "Slackware -current is not supported, but as a general rule, the scripts
>> should work on it as well." so I didn't think to look for a -current repo. )
>>
>> So I did:
>>
>> sboconfig -r https://github.com/Ponce/slackbuilds.git
>> sboconfig -l # to confirm sbo was in fact pointed at that URL
>> sbocheck
>>
>> It ran, didn't seem to download anything new. But no improvement, still got "Unable to locate..."
>>
>> Then just to be sure, started from scratch:
>>
>> rm -rf /usr/sbo
>> sbosnap fetch
>> sboinstall python3-matplotlib
>>
>> ... but same problem. FWIW sbotools is 2.7.
>>
>> So tried it with sbopkg, selected the -current git repo and it seems to have worked. Good enough for me, though I would still like to know what went wrong with sbotools.
>>
>> Is sbopkg more actively maintained than sbotools?
>>
>> thx
>> Judah
>>
>> On 3/10/24 19:07, fourtysixandtwo wrote:
>> > Both work fine pointed at ponce's repo for -current.
>> >
>> > sbotools by default does point to ponce's repo, but maybe try pointing
>> > at it explicitly.
>> >
>> > sboconfig -r https://github.com/Ponce/slackbuilds.git
>> > sbocheck
>> >
>> > Cheers
>> >
>> > On Sun, Mar 10, 2024 at 4:35 PM J. Milgram <milgram at cgpp.com> wrote:
>> >>
>> >> ... or maybe I just need to switch to sbopkg?
>> >>
>> >>
>> >> On 3/10/24 18:21, J. Milgram wrote:
>> >>> Hello.
>> >>>
>> >>> Once again having problems installing with sbotools. There's evidently
>> >>> some config subtlety I'm not grasping, hopefully someone can set me
>> >>> straight.
>> >>>
>> >>> I have a fresh -current install and am using the default 15.0 repo.
>> >>> Many slackbuilds installed fine, but then:
>> >>>
>> >>> /usr/sbin/sboinstall XXX fails with:
>> >>>
>> >>> "Unable to locate XXX in the SlackBuilds.org tree."
>> >>>
>> >>> Where XXX is in [ python3-build, python3-wheel ] ... and maybe others.
>> >>> May be just python3 packages that fail but haven't investigated. I do
>> >>> see these slackbuilds in the slackbuilds repo so they're not mirages.
>> >>>
>> >>> Some config stuff:
>> >>>
>> >>>>> cat /etc/slackware-version
>> >>> Slackware 15.0+
>> >>>
>> >>>>> cat /etc/sbotools/sbotools.conf
>> >>> JOBS=5
>> >>> DISTCLEAN=TRUE
>> >>>
>> >>>>> /usr/sbin/sboconfig -l
>> >>> sboconfig -d|--distclean:
>> >>>      DISTCLEAN=TRUE
>> >>> sboconfig -j|--jobs:
>> >>>      JOBS=5
>> >>> sboconfig -o|--local-overrides:
>> >>>      LOCAL_OVERRIDES=FALSE
>> >>> sboconfig -c|--noclean:
>> >>>      NOCLEAN=FALSE
>> >>> sboconfig -p|--pkg-dir:
>> >>>      PKG_DIR=FALSE
>> >>> sboconfig -r|--repo:
>> >>>      REPO=FALSE
>> >>> sboconfig -s|--sbo-home:
>> >>>      SBO_HOME=/usr/sbo
>> >>> sboconfig -V|--slackware-version:
>> >>>      SLACKWARE_VERSION=FALSE
>> >>>
>> >>> /usr/sbo/repo has 320+ MB of slackbuilds files, but nothing for
>> >>> python3-build or python3-wheel.
>> >>>
>> >>> /usr/sbo/distfiles is empty (I guess because I have DISTCLEAN=TRUE and
>> >>> have also done sboclean -d.
>> >>>
>> >>> /usr/sbin/sbosnap and sboupdate both run seemingly without error, but
>> >>> don't pick up the missing slackbuilds.
>> >>>
>> >>> I'm guessing this is a 15.0 vs. -current thing, but I am out of ideas.
>> >>> Grateful for any advice!
>> >>>
>> >>> Maybe I need to install these problem packages by hand ... if it must
>> >>> be, so be it. But in the long term it would be nice to get everything
>> >>> configured properly.
>> >>>
>> >>> thanks!
>> >>>
>> >>> Judah
>> >>>
>> >> --
>> >> =====
>> >> milgram at cgpp.com
>> >> 301-257-7069
>> >>
>> >> _______________________________________________
>> >> 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/
>> >>
>> > _______________________________________________
>> > 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/
>> >
>>
>> --
>> =====
>> milgram at cgpp.com
>>
>> _______________________________________________
>> 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/
>>
> _______________________________________________
> 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/
>