On Tue, Feb 13, 2024 at 05:08:03PM -0800, Jeremy Hansen wrote:
On Tue, Feb 13, 2024, 4:34 PM Tonus wrote:
Hi all
I have a slackbuild that builds man pages if Pandoc is installed
(autodetected).
If it isn't, the man pages compression in the SBo template makes the
script fail
What's the good
On Tue, Feb 13, 2024, 4:34 PM Tonus wrote:
> Hi all
>
> I have a slackbuild that builds man pages if Pandoc is installed
> (autodetected).
>
> If it isn't, the man pages compression in the SBo template makes the
> script fail
> What's the good practice ? Add `|| true` at the end of the lines ?
>
Hi all
I have a slackbuild that builds man pages if Pandoc is installed
(autodetected).
If it isn't, the man pages compression in the SBo template makes the script fail
What's the good practice ? Add `|| true` at the end of the lines ?
Tryed on clean system without Pandoc and on my system
Hello guys,
Since compiledb (pip install) was not working for other reasons, I tried to
compile Bear-3-1-3 again, this time successfuly.
The package is available here:
https://mirrors.slackware.devl.club/slackware64-15.0-packages/kernel-5.15.145-x86_64/Bear-3.1.3-x86_64-1_SBo.tgz
On Tue, Feb 13, 2024, 6:30 AM Tim Dickson via SlackBuilds-users <
slackbuilds-users@slackbuilds.org> wrote:
> Hi all, there are three slackbuilds I look after which need a homepage
> update from http to https
> should I submit 3 updates with .info updated and build no. bumped, or is
> there an
Dear Ivan Kovmir,
Thank you for your reply. Have you contacted gRPC maintainer to figure out the
problem?
I'll use compiledb for now, because I can't build Bear. If things change, I'll
write back with news.
Cordialmente,
Ruben
--
Dr. Beco
AI Researcher
Hi all, there are three slackbuilds I look after which need a homepage
update from http to https
should I submit 3 updates with .info updated and build no. bumped, or is
there an easier way.
as the build is identical, maybe the build number doesn't need bumping,
but is it possible
to do an
On Tue, Feb 13, 2024 at 06:50:21AM +0700, Willy Sudiarto Raharjo wrote:
> > My diagnosis is that the configure script from filezilla found an
> > incompatible version when running wx-config. It has found a version 3.0
> > "config" (actually, I'm not sure what this component really is) which
> >
