From jbernts at broadpark.no  Fri Jan  1 17:12:00 2016
From: jbernts at broadpark.no (Jostein Berntsen)
Date: Fri, 01 Jan 2016 18:12:00 +0100
Subject: [sbopkg-users] Install from queue
Message-ID: <20160101171200.GA24263@jostein>

In the manual it says this regarding the -B option for installing without asking for confirmation:

-B
    Process the packages or queues without prompting for confirmation first. 

This works when installing packages, but for queues I still get the confirmation question. Is this right?


Jostein

From willysr at sbopkg.org  Fri Jan  1 22:10:23 2016
From: willysr at sbopkg.org (Willy Sudiarto Raharjo)
Date: Sat, 2 Jan 2016 05:10:23 +0700
Subject: [sbopkg-users] Install from queue
In-Reply-To: <20160101171200.GA24263@jostein>
References: <20160101171200.GA24263@jostein>
Message-ID: <5686F94F.40606@sbopkg.org>

> In the manual it says this regarding the -B option for installing without asking for confirmation:
> 
> -B
>     Process the packages or queues without prompting for confirmation first. 
> 
> This works when installing packages, but for queues I still get the confirmation question. Is this right?

I tried sbopkg -Bi libbonobo and it only asked whether i want to build
it using queues (generated by sqg already), package, or quit
when i pick queues, it will run the process without asking anymore

sbopkg -Bi libbonobo
Both a queuefile and a package were found with the name "libbonobo".

Use (Q)ueuefile, (P)ackage, or (A)bort?: q

###########################################
       New queue process started on:
       Sat Jan  2 05:09:25 WIB 2016
###########################################

+++++++++++++++++++++++++++++++++++++++++++
PRE-CHECK LOG
Using the SBo repository for Slackware 14.1
Queue Process:  Download, build, and install

ORBit2:
  Checking GPG for ORBit2.tar.gz ... OK
  Processing ORBit2 2.14.19-3
  Using original .info file
  Using original SlackBuild file
  No build options selected.

libbonobo:
  Checking GPG for libbonobo.tar.gz ... OK
  Processing libbonobo 2.32.1-3
  Using original .info file
  Using original SlackBuild file
  No build options selected.

+++++++++++++++++++++++++++++++++++++++++++

Pre-check complete.



Processing ORBit2
.
.
.
(truncated)


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20160102/561b6787/attachment.asc>

From ryan.q at linux.com  Fri Jan  1 22:29:42 2016
From: ryan.q at linux.com (Ryan P.C. McQuen)
Date: Fri, 1 Jan 2016 16:29:42 -0600
Subject: [sbopkg-users] Install from queue
In-Reply-To: <5686F94F.40606@sbopkg.org>
References: <20160101171200.GA24263@jostein>
	<5686F94F.40606@sbopkg.org>
Message-ID: <CAAcyf-rhZ9fViYAMupR64SSj2HLHqD6aZRiwYMmq5AbE3Dc5qA@mail.gmail.com>

On Jan 1, 2016 2:10 PM, "Willy Sudiarto Raharjo" <willysr at sbopkg.org> wrote:
>
> > In the manual it says this regarding the -B option for installing
without asking for confirmation:
> >
> > -B
> >     Process the packages or queues without prompting for confirmation
first.
> >
> > This works when installing packages, but for queues I still get the
confirmation question. Is this right?
>
> I tried sbopkg -Bi libbonobo and it only asked whether i want to build
> it using queues (generated by sqg already), package, or quit
> when i pick queues, it will run the process without asking anymore
>
> sbopkg -Bi libbonobo
> Both a queuefile and a package were found with the name "libbonobo".
>
> Use (Q)ueuefile, (P)ackage, or (A)bort?: q

If you want to script it just pipe 'echo q' into your sbopkg command:

  echo q | sbopkg ...

I do something similar in config-o-matic:

https://github.com/ryanpcmcquen/config-o-matic/blob/master/.slackConfigROOT.sh#L144
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20160101/39df5c27/attachment.html>

From jbernts at broadpark.no  Fri Jan  1 22:54:53 2016
From: jbernts at broadpark.no (Jostein Berntsen)
Date: Fri, 01 Jan 2016 23:54:53 +0100
Subject: [sbopkg-users] Install from queue
In-Reply-To: <CAAcyf-rhZ9fViYAMupR64SSj2HLHqD6aZRiwYMmq5AbE3Dc5qA@mail.gmail.com>
References: <20160101171200.GA24263@jostein> <5686F94F.40606@sbopkg.org>
 <CAAcyf-rhZ9fViYAMupR64SSj2HLHqD6aZRiwYMmq5AbE3Dc5qA@mail.gmail.com>
Message-ID: <20160101225453.GA30669@jostein>

On 01.01.16,16:29, Ryan P.C. McQuen wrote:
> On Jan 1, 2016 2:10 PM, "Willy Sudiarto Raharjo" <willysr at sbopkg.org> wrote:
> >
> > > In the manual it says this regarding the -B option for installing
> without asking for confirmation:
> > >
> > > -B
> > >     Process the packages or queues without prompting for confirmation
> first.
> > >
> > > This works when installing packages, but for queues I still get the
> confirmation question. Is this right?
> >
> > I tried sbopkg -Bi libbonobo and it only asked whether i want to build
> > it using queues (generated by sqg already), package, or quit
> > when i pick queues, it will run the process without asking anymore
> >
> > sbopkg -Bi libbonobo
> > Both a queuefile and a package were found with the name "libbonobo".
> >
> > Use (Q)ueuefile, (P)ackage, or (A)bort?: q
> 
> If you want to script it just pipe 'echo q' into your sbopkg command:
> 
>   echo q | sbopkg ...
> 
> I do something similar in config-o-matic:
> 
> https://github.com/ryanpcmcquen/config-o-matic/blob/master/.slackConfigROOT.sh#L144

I can use this, thanks,


Jostein

From jbernts at broadpark.no  Fri Jan  1 22:58:33 2016
From: jbernts at broadpark.no (Jostein Berntsen)
Date: Fri, 01 Jan 2016 23:58:33 +0100
Subject: [sbopkg-users] Install from queue
In-Reply-To: <CAAcyf-rhZ9fViYAMupR64SSj2HLHqD6aZRiwYMmq5AbE3Dc5qA@mail.gmail.com>
References: <20160101171200.GA24263@jostein> <5686F94F.40606@sbopkg.org>
 <CAAcyf-rhZ9fViYAMupR64SSj2HLHqD6aZRiwYMmq5AbE3Dc5qA@mail.gmail.com>
Message-ID: <20160101225833.GB30669@jostein>

On 01.01.16,16:29, Ryan P.C. McQuen wrote:
> On Jan 1, 2016 2:10 PM, "Willy Sudiarto Raharjo" <willysr at sbopkg.org> wrote:
> >
> > > In the manual it says this regarding the -B option for installing
> without asking for confirmation:
> > >
> > > -B
> > >     Process the packages or queues without prompting for confirmation
> first.
> > >
> > > This works when installing packages, but for queues I still get the
> confirmation question. Is this right?
> >
> > I tried sbopkg -Bi libbonobo and it only asked whether i want to build
> > it using queues (generated by sqg already), package, or quit
> > when i pick queues, it will run the process without asking anymore
> >
> > sbopkg -Bi libbonobo
> > Both a queuefile and a package were found with the name "libbonobo".
> >
> > Use (Q)ueuefile, (P)ackage, or (A)bort?: q
> 
> If you want to script it just pipe 'echo q' into your sbopkg command:
> 
>   echo q | sbopkg ...
> 
> I do something similar in config-o-matic:
> 
> https://github.com/ryanpcmcquen/config-o-matic/blob/master/.slackConfigROOT.sh#L144

This works nicely, thanks.


Jostein

From c.e.tower at gmail.com  Wed Jan 13 04:31:31 2016
From: c.e.tower at gmail.com (Chick Tower)
Date: Tue, 12 Jan 2016 22:31:31 -0600
Subject: [sbopkg-users] sbopkg, Slackbuilds, & Slackware-current
In-Reply-To: <56510D44.3010604@sbopkg.org>
References: <CAGgjXXjxiQO23bOVc=zhq_Ad36TWwqgGdCJTpFPhYaU_e8pWsw@mail.gmail.com>
 <56510B82.9050703@NorthTech.US> <56510D44.3010604@sbopkg.org>
Message-ID: <5695D323.4010101@gmail.com>

Do any of you know if sbopkg and/or Slackbuilds work on 
Slackware-current?  If so, are any modifications necessary, such has 
hard-coding version 14.1 into sbopkg?

-- 

                                Chick

From rworkman at slackbuilds.org  Wed Jan 13 05:01:08 2016
From: rworkman at slackbuilds.org (Robby Workman)
Date: Tue, 12 Jan 2016 23:01:08 -0600
Subject: [sbopkg-users] sbopkg, Slackbuilds, & Slackware-current
In-Reply-To: <5695D323.4010101@gmail.com>
References: <CAGgjXXjxiQO23bOVc=zhq_Ad36TWwqgGdCJTpFPhYaU_e8pWsw@mail.gmail.com>
 <56510B82.9050703@NorthTech.US> <56510D44.3010604@sbopkg.org>
 <5695D323.4010101@gmail.com>
Message-ID: <20160112230108.6f8de251@home.rlworkman.net>

On Tue, 12 Jan 2016 22:31:31 -0600
Chick Tower <c.e.tower at gmail.com> wrote:

> Do any of you know if sbopkg and/or Slackbuilds work on 
> Slackware-current?  If so, are any modifications necessary, such has 
> hard-coding version 14.1 into sbopkg?


I don't know how to do it (I don't actually use sbopkg), but
we have a "current-wip" git branch that has LOTS of changes
for 14.2beta and forward. 

We'll likely merge that branch into git master soon though.

-RW 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20160112/19522a05/attachment.asc>

From willysr at sbopkg.org  Wed Jan 13 07:33:45 2016
From: willysr at sbopkg.org (Willy Sudiarto Raharjo)
Date: Wed, 13 Jan 2016 14:33:45 +0700
Subject: [sbopkg-users] sbopkg, Slackbuilds, & Slackware-current
In-Reply-To: <5695D323.4010101@gmail.com>
References: <CAGgjXXjxiQO23bOVc=zhq_Ad36TWwqgGdCJTpFPhYaU_e8pWsw@mail.gmail.com>
 <56510B82.9050703@NorthTech.US> <56510D44.3010604@sbopkg.org>
 <5695D323.4010101@gmail.com>
Message-ID: <5695FDD9.9010502@sbopkg.org>

> Do any of you know if sbopkg and/or Slackbuilds work on
> Slackware-current?  If so, are any modifications necessary, such has
> hard-coding version 14.1 into sbopkg?

See ponce's wiki
https://github.com/Ponce/slackbuilds/wiki/configuring-the-current-repository-with-sbopkg

but that will have to wait until current-wip branch is merged into
master because at this point, master is still for 14.1

probably soon :)


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20160113/3b6984ff/attachment.asc>

From willysr at sbopkg.org  Sun Jan 17 04:32:56 2016
From: willysr at sbopkg.org (Willy Sudiarto Raharjo)
Date: Sun, 17 Jan 2016 11:32:56 +0700
Subject: [sbopkg-users] master branch for current
Message-ID: <569B1978.4090103@sbopkg.org>

Hi folks,

Just now, current-wip branch has been merged into master, which means,
you can help testing against current (soon to be called 14.2) by using
sbopkg and change the repository into SBo's master GIT branch

You need to open /etc/sbopkg/sbopkg.conf and change
REPO_BRANCH=${REPO_BRANCH:-14.1}
into
REPO_BRANCH=${REPO_BRANCH:-master}

and run sbopkg -r
it will checkout the whole SBo GIT repository and replace the 14.1
repository.

Since there has been many changes in the previous current-wip branch due
to changes in core Slackware packages, it's recommended to run sqg -a to
update all local queues to reflect dependencies changes in the master
branch.

Happy testing and Slacking :)


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20160117/770ea462/attachment.asc>

From 1.41421 at gmail.com  Fri Jan 22 17:08:32 2016
From: 1.41421 at gmail.com (JCA)
Date: Fri, 22 Jan 2016 10:08:32 -0700
Subject: [sbopkg-users] Synchronizing queues
Message-ID: <CAFy1yb1n839TQO_j8iDW6+Sx8f7bsKQYdJtYFWa_EiPpGmHqwg@mail.gmail.com>

I have two different systems, A and B, running Slackware 14.1. Every
so often I use sbopkg to synchronize things with slackbuilds in A and
B. This seems to work fine. After that, for each system I rename my
existing /var/lib/sbopkg/queues directory as
/var/lib/sbopkg/queues.old, and create a new queues directory in the
same location. I then cd into this queues directory and invoke 'sqg
-a'.

When, after a while, this command finishes in A, the number of .sqf
files in queues is over 5,700. In B, 'sqg -a' completes significantly
faster - but the number of .sqf files is only about 2,500.

Anybody has an inkling about the reasons behind this discrepancy? For
all I know, both A and B have been configured identically, as far as
sbopkg is concerned. B seems to be the defective one, for it obviously
lacks .sqf files corresponding to packages available in slackbuilds -
e.g. tor.sqf and tor-browser.sqf are missing in B. But I can't fathom
why. Any feedback on how to tackle this issue would be most welcome.

From willysr at sbopkg.org  Fri Jan 22 19:03:06 2016
From: willysr at sbopkg.org (Willy Sudiarto Raharjo)
Date: Sat, 23 Jan 2016 02:03:06 +0700
Subject: [sbopkg-users] Synchronizing queues
In-Reply-To: <CAFy1yb1n839TQO_j8iDW6+Sx8f7bsKQYdJtYFWa_EiPpGmHqwg@mail.gmail.com>
References: <CAFy1yb1n839TQO_j8iDW6+Sx8f7bsKQYdJtYFWa_EiPpGmHqwg@mail.gmail.com>
Message-ID: <56A27CEA.3070709@sbopkg.org>

> I have two different systems, A and B, running Slackware 14.1. Every
> so often I use sbopkg to synchronize things with slackbuilds in A and
> B. This seems to work fine. After that, for each system I rename my
> existing /var/lib/sbopkg/queues directory as
> /var/lib/sbopkg/queues.old, and create a new queues directory in the
> same location. I then cd into this queues directory and invoke 'sqg
> -a'.
> 
> When, after a while, this command finishes in A, the number of .sqf
> files in queues is over 5,700. In B, 'sqg -a' completes significantly
> faster - but the number of .sqf files is only about 2,500.
> 
> Anybody has an inkling about the reasons behind this discrepancy? For
> all I know, both A and B have been configured identically, as far as
> sbopkg is concerned. B seems to be the defective one, for it obviously
> lacks .sqf files corresponding to packages available in slackbuilds -
> e.g. tor.sqf and tor-browser.sqf are missing in B. But I can't fathom
> why. Any feedback on how to tackle this issue would be most welcome.

can you make sure that both sqg files are identical?
in 0.37.0, sqg is still pointing to 14.0 repository and that was fixed
in 0.37.1.


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20160123/ea975cd1/attachment.asc>

From Bradley at NorthTech.US  Wed Jan 27 10:19:11 2016
From: Bradley at NorthTech.US (Bradley D. Thornton)
Date: Wed, 27 Jan 2016 02:19:11 -0800
Subject: [sbopkg-users] master branch for current
In-Reply-To: <569B1978.4090103@sbopkg.org>
References: <569B1978.4090103@sbopkg.org>
Message-ID: <56A8999F.30402@NorthTech.US>



On 1/16/2016 8:32 PM, Willy Sudiarto Raharjo wrote:
> Hi folks,
>
> Just now, current-wip branch has been merged into master, which means,
> you can help testing against current (soon to be called 14.2) by using
> sbopkg and change the repository into SBo's master GIT branch
>
> You need to open /etc/sbopkg/sbopkg.conf and change
> REPO_BRANCH=${REPO_BRANCH:-14.1}
> into
> REPO_BRANCH=${REPO_BRANCH:-master}

Willy, the doc at 
https://github.com/Ponce/slackbuilds/wiki/configuring-the-current-repository-with-sbopkg 
says to have the following in sbopkg.conf:

|REPO_BRANCH=${REPO_BRANCH:-current}|

|REPO_NAME=${REPO_NAME:-SBo-git}
|

|According to what I'm gleaning from you above, I've got this in 
sbopkg.conf:
|

|REPO_BRANCH=${REPO_BRANCH:-master}
REPO_NAME=${REPO_NAME:-SBo}

and this is what I have in /usr/bin/sqg, since I have no need to 
override anything in sbopkg.conf:

#QUEUEDIR=${QUEUEDIR:-/var/lib/sbopkg/queues}
#REPO_ROOT=${REPO_ROOT:-/var/lib/sbopkg}
#REPO_NAME=${REPO_NAME:-SBo}
#REPO_BRANCH=${REPO_BRANCH:-master}
#SKIP_EMPTY=${SKIP_EMPTY:-NO}
|

>
> and run sbopkg -r

and I get this, which looks good to me:

# sbopkg -r
Syncing with the remote repository into /var/lib/sbopkg/SBo.
 From git://slackbuilds.org/slackbuilds
  * branch            master     -> FETCH_HEAD
Already up-to-date.
HEAD is now at 314148f network/chromium: Updated for version 48.0.2564.82.

Repository update complete.


> it will checkout the whole SBo GIT repository and replace the 14.1
> repository.
>
> Since there has been many changes in the previous current-wip branch due
> to changes in core Slackware packages, it's recommended to run sqg -a to
> update all local queues to reflect dependencies changes in the master
> branch.

sqg -a yields the following for me:

#  ls /var/lib/sbopkg/queues |wc -l
2588


That's much less than the 5,700 mentioned by JCA in his earlier post. 
Other than the low count of queue files, does everything else appear 
correct?

Also, as a second question, moving forward in a rolling -current, will I 
be looking to switch the repo name and branch to what the doc in the 
link above says? i.e.,

|REPO_BRANCH=${REPO_BRANCH:-current}|

|REPO_NAME=${REPO_NAME:-SBo-git}
|

|Thanks!
|





---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20160127/afcacf04/attachment.html>

From willysr at slackbuilds.org  Wed Jan 27 14:43:07 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Wed, 27 Jan 2016 21:43:07 +0700
Subject: [sbopkg-users] master branch for current
In-Reply-To: <56A8999F.30402@NorthTech.US>
References: <569B1978.4090103@sbopkg.org> <56A8999F.30402@NorthTech.US>
Message-ID: <56A8D77B.1010205@slackbuilds.org>

> Willy, the doc at
> https://github.com/Ponce/slackbuilds/wiki/configuring-the-current-repository-with-sbopkg
> says to have the following in sbopkg.conf:
> 
> |REPO_BRANCH=${REPO_BRANCH:-current}|
> 
> |REPO_NAME=${REPO_NAME:-SBo-git}
> |

The wiki applies to Ponce's current branch, not SBo's master branch

> |According to what I'm gleaning from you above, I've got this in
> sbopkg.conf:
> |
> 
> |REPO_BRANCH=${REPO_BRANCH:-master}
> REPO_NAME=${REPO_NAME:-SBo}
> 
> and this is what I have in /usr/bin/sqg, since I have no need to
> override anything in sbopkg.conf:
> 
> #QUEUEDIR=${QUEUEDIR:-/var/lib/sbopkg/queues}
> #REPO_ROOT=${REPO_ROOT:-/var/lib/sbopkg}
> #REPO_NAME=${REPO_NAME:-SBo}
> #REPO_BRANCH=${REPO_BRANCH:-master}
> #SKIP_EMPTY=${SKIP_EMPTY:-NO}


you don't have to change anything in sqg since it detects whether you
are taking 14.1 repository or GIT repository

This is the code snippet
if [ -d $REPO_ROOT/$REPO_NAME/.git ]; then
    REPO_SUBPATH=$REPO_NAME
else
    REPO_SUBPATH=$REPO_NAME/$REPO_BRANCH
fi


> sqg -a yields the following for me:
> 
> #  ls /var/lib/sbopkg/queues |wc -l
> 2588
> 
> 
> That's much less than the 5,700 mentioned by JCA in his earlier post.
> Other than the low count of queue files, does everything else appear
> correct?

5700+ is the number of scripts available in SBo and the queue files are
not that much since some scripts do not have dependencies, thus no queue
file is generated for that particular script when you run sqg -a.

ll /var/lib/sbopkg/queues/ | wc -l
2599

> Also, as a second question, moving forward in a rolling -current, will I
> be looking to switch the repo name and branch to what the doc in the
> link above says? i.e.,
> 
> |REPO_BRANCH=${REPO_BRANCH:-current}|
> 
> |REPO_NAME=${REPO_NAME:-SBo-git}

the only change is from 14.1 to master and that's it. No other changes
are required to use SBo's master branch.
When 14.2 repository gets released, simply change it back to 14.2 and
re-run sbopkg -r.



-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20160127/29243f6e/attachment.asc>

From willysr at sbopkg.org  Wed Jan 27 14:47:15 2016
From: willysr at sbopkg.org (Willy Sudiarto Raharjo)
Date: Wed, 27 Jan 2016 21:47:15 +0700
Subject: [sbopkg-users] opencv 3.0.0 compile error
In-Reply-To: <20151114111134.67bff7ea@gmail.com>
References: <20151114111134.67bff7ea@gmail.com>
Message-ID: <56A8D873.5000602@sbopkg.org>

On 11/14/2015 12:41 PM, Subash wrote:
> hi,
> 
> my name is subash, from chennai india. been on slackware since about
> 2003, on slackware-current now.
> 
> just recently came across sbopkg and been using it for the last week or
> so. looks like a nice way to browse and install libraries/applications.
> thanks.
> 
> i had opencv 2.4.x on my system but since the latest digikam needed
> opencv-3.0.0, was trying to compile that using sbopkg and i run into
> the following error:
> /usr/lib/gcc/i586-slackware-linux/4.9.3/../../../../i586-slackware-linux/bin/ld:
> warning: libhogweed.so.2, needed by /usr/lib/libavformat.so.56, not found (try using -rpath or -rpath-link)
> /usr/lib/gcc/i586-slackware-linux/4.9.3/../../../../i586-slackware-linux/bin/ld:
> warning: libgnutls.so.28, needed by /usr/lib/libavformat.so.56, not found (try using -rpath or -rpath-link)
> /usr/lib/libavformat.so.56: undefined reference to
> `gnutls_server_name_set at GNUTLS_1_4'
> /usr/lib/libavformat.so.56: undefined reference to
> `gnutls_transport_set_ptr at GNUTLS_1_4'
> /usr/lib/libavformat.so.56: undefined reference to
> `gnutls_record_recv at GNUTLS_1_4'
> /usr/lib/libavformat.so.56: undefined reference to
> `gnutls_deinit at GNUTLS_1_4'
> /usr/lib/libavformat.so.56: undefined reference to
> `gnutls_certificate_set_x509_system_trust at GNUTLS_3_0_0'
> /usr/lib/libavformat.so.56: undefined reference to
> `gnutls_global_deinit at GNUTLS_1_4'
> /usr/lib/libavformat.so.56: undefined reference to
> `gnutls_handshake at GNUTLS_1_4'
> /usr/lib/libavformat.so.56: undefined reference to
> `gnutls_certificate_set_x509_key_file at GNUTLS_1_4'
> /usr/lib/libavformat.so.56: undefined reference to
> `gnutls_certificate_set_x509_trust_file at GNUTLS_1_4'
> /usr/lib/libavformat.so.56: undefined reference to
> `gnutls_certificate_type_get at GNUTLS_1_4'
> /usr/lib/libavformat.so.56: undefined reference to
> `gnutls_certificate_set_verify_flags at GNUTLS_1_4'
> /usr/lib/libavformat.so.56: undefined reference to
> `gnutls_certificate_allocate_credentials at GNUTLS_1_4'
> /usr/lib/libavformat.so.56: undefined reference to
> `gnutls_x509_crt_check_hostname at GNUTLS_1_4'
> /usr/lib/libavformat.so.56: undefined reference to
> `gnutls_priority_set_direct at GNUTLS_1_4'
> /usr/lib/libavformat.so.56: undefined reference to
> `gnutls_init at GNUTLS_1_4'
> /usr/lib/libavformat.so.56: undefined reference to
> `gnutls_certificate_get_peers at GNUTLS_1_4'
> /usr/lib/libavformat.so.56: undefined reference to
> `gnutls_record_send at GNUTLS_1_4'
> /usr/lib/libavformat.so.56: undefined reference to
> `gnutls_bye at GNUTLS_1_4'
> /usr/lib/libavformat.so.56: undefined reference to
> `gnutls_record_get_direction at GNUTLS_1_4'
> /usr/lib/libavformat.so.56: undefined reference to
> `gnutls_certificate_free_credentials at GNUTLS_1_4'
> /usr/lib/libavformat.so.56: undefined reference to
> `gnutls_strerror at GNUTLS_1_4'
> /usr/lib/libavformat.so.56: undefined reference to
> `gnutls_credentials_set at GNUTLS_1_4'
> /usr/lib/libavformat.so.56: undefined reference to
> `gnutls_x509_crt_deinit at GNUTLS_1_4'
> /usr/lib/libavformat.so.56: undefined reference to
> `gnutls_certificate_verify_peers2 at GNUTLS_1_4'
> /usr/lib/libavformat.so.56: undefined reference to
> `gnutls_x509_crt_init at GNUTLS_1_4'
> /usr/lib/libavformat.so.56: undefined reference to
> `gnutls_global_init at GNUTLS_1_4'
> /usr/lib/libavformat.so.56: undefined reference to
> `gnutls_x509_crt_import at GNUTLS_1_4'
> collect2: error: ld returned 1 exit status
> modules/core/CMakeFiles/opencv_perf_core.dir/build.make:806: recipe for
> target 'bin/opencv_perf_core' failed
> make[2]: *** [bin/opencv_perf_core] Error 1
> make[2]: Leaving directory '/tmp/SBo/opencv-3.0.0/build'
> CMakeFiles/Makefile2:1873: recipe for target
> 'modules/core/CMakeFiles/opencv_perf_core.dir/all' failed
> make[1]: *** [modules/core/CMakeFiles/opencv_perf_core.dir/all] Error 2
> make[1]: Leaving directory '/tmp/SBo/opencv-3.0.0/build'
> Makefile:149: recipe for target 'all' failed
> make: *** [all] Error 2
> 
> i do have the latest gnutls installed (compiled from source). any
> pointers will be helpful. thanks, subash

Hi Subash

Your posting was in moderator queue for so long until i realize there
was a pending post. Sorry for the long wait.

Since opencv is now upgraded to 3.0.0, digiKam is now patched to use
OpenCV 3.0.0 as well and this should be fixed in master branch.


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20160127/be4c3318/attachment.asc>

From ryan.q at linux.com  Wed Jan 27 16:59:06 2016
From: ryan.q at linux.com (Ryan P.C. McQuen)
Date: Wed, 27 Jan 2016 16:59:06 +0000
Subject: [sbopkg-users] master branch for current
In-Reply-To: <56A8D77B.1010205@slackbuilds.org>
References: <569B1978.4090103@sbopkg.org> <56A8999F.30402@NorthTech.US>
 <56A8D77B.1010205@slackbuilds.org>
Message-ID: <CAAcyf-rp6AxJPW1nnaE1en+CLNgEjX5sa=wRFFViaBTE8SvP+g@mail.gmail.com>

On Wed, Jan 27, 2016 at 6:44 AM Willy Sudiarto Raharjo <
willysr at slackbuilds.org> wrote:

> > Willy, the doc at
> >
> https://github.com/Ponce/slackbuilds/wiki/configuring-the-current-repository-with-sbopkg
> > says to have the following in sbopkg.conf:
> >
> > |REPO_BRANCH=${REPO_BRANCH:-current}|
> >
> > |REPO_NAME=${REPO_NAME:-SBo-git}
> > |
>
> The wiki applies to Ponce's current branch, not SBo's master branch
>
> > |According to what I'm gleaning from you above, I've got this in
> > sbopkg.conf:
> > |
> >
> > |REPO_BRANCH=${REPO_BRANCH:-master}
> > REPO_NAME=${REPO_NAME:-SBo}
>



For reference, this is what I do.  :^)

https://github.com/ryanpcmcquen/config-o-matic/blob/master/.slackConfigROOT.sh#L469-L518
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20160127/d91489ab/attachment.html>

From 1.41421 at gmail.com  Wed Jan 27 17:41:29 2016
From: 1.41421 at gmail.com (JCA)
Date: Wed, 27 Jan 2016 10:41:29 -0700
Subject: [sbopkg-users] Synchronizing queues
Message-ID: <CAFy1yb0_gk6bY9AYq6nPh1jE3+PftYEx1LQC+us0ybju5R+HUw@mail.gmail.com>

>> I have two different systems, A and B, running Slackware 14.1. Every
>> so often I use sbopkg to synchronize things with slackbuilds in A and
>> B. This seems to work fine. After that, for each system I rename my
>> existing /var/lib/sbopkg/queues directory as
>> /var/lib/sbopkg/queues.old, and create a new queues directory in the
>> same location. I then cd into this queues directory and invoke 'sqg
>> -a'.
>>
>> When, after a while, this command finishes in A, the number of .sqf
>> files in queues is over 5,700. In B, 'sqg -a' completes significantly
>> faster - but the number of .sqf files is only about 2,500.
>>
>> Anybody has an inkling about the reasons behind this discrepancy? For
>> all I know, both A and B have been configured identically, as far as
>> sbopkg is concerned. B seems to be the defective one, for it obviously
>> lacks .sqf files corresponding to packages available in slackbuilds -
>> e.g. tor.sqf and tor-browser.sqf are missing in B. But I can't fathom
>> why. Any feedback on how to tackle this issue would be most welcome.
>
> can you make sure that both sqg files are identical?
> in 0.37.0, sqg is still pointing to 14.0 repository and that was fixed
> in 0.37.1.

They are not identical, but they both point to the 14.1 repository.
Anyway, I copied the sqg file from A to B, and when I ran it on B I
got the same results as in A - which is great. However, I do not
understand why things work correctly with A's sqg file.  A's and B's
sqg files differ mostly in comments, plus (crucially) in the following
lines:

45c45
< #QUEUEDIR=${QUEUEDIR:-/var/lib/sbopkg/queues}
---
> QUEUEDIR=${QUEUEDIR:-/var/lib/sbopkg/queues}
49c49
< #SKIP_EMPTY=${SKIP_EMPTY:-NO}
---
> SKIP_EMPTY=${SKIP_EMPTY:-NO}

I.e. the original sqg file in B comments out the QUEUEDIR and
SKIP_EMPTY lines. It is not immediately obvious to me why that should
have such a huge impact in the number of sqf files downloaded by sqg.

From willysr at sbopkg.org  Wed Jan 27 17:48:25 2016
From: willysr at sbopkg.org (Willy Sudiarto Raharjo)
Date: Thu, 28 Jan 2016 00:48:25 +0700
Subject: [sbopkg-users] Synchronizing queues
In-Reply-To: <CAFy1yb0_gk6bY9AYq6nPh1jE3+PftYEx1LQC+us0ybju5R+HUw@mail.gmail.com>
References: <CAFy1yb0_gk6bY9AYq6nPh1jE3+PftYEx1LQC+us0ybju5R+HUw@mail.gmail.com>
Message-ID: <56A902E9.5040208@sbopkg.org>

> They are not identical, but they both point to the 14.1 repository.
> Anyway, I copied the sqg file from A to B, and when I ran it on B I
> got the same results as in A - which is great. However, I do not
> understand why things work correctly with A's sqg file.  A's and B's
> sqg files differ mostly in comments, plus (crucially) in the following
> lines:
> 
> 45c45
> < #QUEUEDIR=${QUEUEDIR:-/var/lib/sbopkg/queues}
> ---
>> QUEUEDIR=${QUEUEDIR:-/var/lib/sbopkg/queues}
> 49c49
> < #SKIP_EMPTY=${SKIP_EMPTY:-NO}
> ---
>> SKIP_EMPTY=${SKIP_EMPTY:-NO}
> 
> I.e. the original sqg file in B comments out the QUEUEDIR and
> SKIP_EMPTY lines. It is not immediately obvious to me why that should
> have such a huge impact in the number of sqf files downloaded by sqg.

actually, i may have wrong analysis
5700 is the number of scripts available on SBo, but queueu files will be
less and it will be around 2600+ (mine is 2601) since it will only be
generated for packages that have deps.

the easiest way to confirm is to reinstall sbopkg and move sqg from
contrib back to /usr/bin and re-check. Also it's best to remove all
queue files first to get the actual results. I never made changes to sqg
on my computer, only sbopkg.conf


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20160128/5d96eefb/attachment.asc>

From 1.41421 at gmail.com  Wed Jan 27 17:58:50 2016
From: 1.41421 at gmail.com (JCA)
Date: Wed, 27 Jan 2016 10:58:50 -0700
Subject: [sbopkg-users] Synchronizing queues
Message-ID: <CAFy1yb0QfenRqYA6Y+ESA2_gwR9-SqqWqbzyHvBtOepa0fVrmg@mail.gmail.com>

Actually, after reading the comments to sqg it becomes obvious why sqg
behaves so differently with the SKIP_EMPTY assignment commented out.
Thanks.

From Bradley at NorthTech.US  Wed Jan 27 20:16:34 2016
From: Bradley at NorthTech.US (Bradley D. Thornton)
Date: Wed, 27 Jan 2016 12:16:34 -0800
Subject: [sbopkg-users] master branch for current
In-Reply-To: <56A8D77B.1010205@slackbuilds.org>
References: <569B1978.4090103@sbopkg.org> <56A8999F.30402@NorthTech.US>
 <56A8D77B.1010205@slackbuilds.org>
Message-ID: <56A925A2.6030902@NorthTech.US>



On 1/27/2016 6:43 AM, Willy Sudiarto Raharjo wrote:
> you don't have to change anything in sqg since it detects whether you
> are taking 14.1 repository or GIT repository
>
> This is the code snippet
> if [ -d $REPO_ROOT/$REPO_NAME/.git ]; then
>      REPO_SUBPATH=$REPO_NAME
> else
>      REPO_SUBPATH=$REPO_NAME/$REPO_BRANCH
> fi
>

Kewl, Thanks Willy! My der :)

>
> 5700+ is the number of scripts available in SBo and the queue files are
> not that much since some scripts do not have dependencies, thus no queue
> file is generated for that particular script when you run sqg -a.
>
> ll /var/lib/sbopkg/queues/ | wc -l
> 2599
>
>
> the only change is from 14.1 to master and that's it. No other changes
> are required to use SBo's master branch.
> When 14.2 repository gets released, simply change it back to 14.2 and
> re-run sbopkg -r

Okay I'm thinking he (JCS) may have set the SKIP_EMPTY to yes in sqg for 
his "A" machine to get that bigger number earlier.

Regarding what you said about not having to touch anything in sqg, the 
comments in that script appear a little misleading to me since my 
interpretation was that with the exception of the SKIP_EMPTY were 
overrides for sqg over that which sbopkg.conf would otherwise be used 
for the repo/branch and directory for the queuefiles generated. That's 
why I simply commented everything out there.

i.e., it looked like not touching anything in sqg would have seemingly 
led to queuefiles being generated from the 14.1 repo/branch

Thanks again!

Bradley

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


From Bradley at NorthTech.US  Wed Jan 27 21:50:30 2016
From: Bradley at NorthTech.US (Bradley D. Thornton)
Date: Wed, 27 Jan 2016 13:50:30 -0800
Subject: [sbopkg-users] Install from queue
In-Reply-To: <CAAcyf-rhZ9fViYAMupR64SSj2HLHqD6aZRiwYMmq5AbE3Dc5qA@mail.gmail.com>
References: <20160101171200.GA24263@jostein> <5686F94F.40606@sbopkg.org>
 <CAAcyf-rhZ9fViYAMupR64SSj2HLHqD6aZRiwYMmq5AbE3Dc5qA@mail.gmail.com>
Message-ID: <56A93BA6.9030709@NorthTech.US>



On 1/1/2016 2:29 PM, Ryan P.C. McQuen wrote:
>
>
> > sbopkg -Bi libbonobo
> > Both a queuefile and a package were found with the name "libbonobo".
> >
> > Use (Q)ueuefile, (P)ackage, or (A)bort?: q
>
> If you want to script it just pipe 'echo q' into your sbopkg command:
>
>   echo q | sbopkg ...
>

Very nice Ryan :)

  echo "alias sbfind='sbopkg -g'
alias sbgo='echo q |sbopkg -Bi'" >> /root/.bashrc
. /root/.bashrc

Not a big fan of aliases, but I was inspired by what what the Paclid's 
asked of Geordi LaForge - Make it go! Make it go fast!

On another note, I can't seem to get -k to work. i.e., sbopkg -Bik 
<package> or even sbopkg -i -k <package>

It would be nice to not rebuild every dep that's already been compiled, 
maybe breaking something else, until such time as I manually update 
installed packages.

What about -k am I missing?



---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus


From ryan.q at linux.com  Thu Jan 28 00:48:14 2016
From: ryan.q at linux.com (Ryan P.C. McQuen)
Date: Wed, 27 Jan 2016 16:48:14 -0800
Subject: [sbopkg-users] Install from queue
In-Reply-To: <56A93BA6.9030709@NorthTech.US>
References: <20160101171200.GA24263@jostein> <5686F94F.40606@sbopkg.org>
 <CAAcyf-rhZ9fViYAMupR64SSj2HLHqD6aZRiwYMmq5AbE3Dc5qA@mail.gmail.com>
 <56A93BA6.9030709@NorthTech.US>
Message-ID: <CAAcyf-qMtQQvZgX97ZJ4MtVrcPvn-LYf6PmCsXVkAdxHb8-Ptg@mail.gmail.com>

On Jan 27, 2016 1:50 PM, "Bradley D. Thornton" <Bradley at northtech.us> wrote:
>
>
>
> On 1/1/2016 2:29 PM, Ryan P.C. McQuen wrote:
>>
>>
>>
>> > sbopkg -Bi libbonobo
>> > Both a queuefile and a package were found with the name "libbonobo".
>> >
>> > Use (Q)ueuefile, (P)ackage, or (A)bort?: q
>>
>> If you want to script it just pipe 'echo q' into your sbopkg command:
>>
>>   echo q | sbopkg ...
>>
>
> Very nice Ryan :)
>
>  echo "alias sbfind='sbopkg -g'
> alias sbgo='echo q |sbopkg -Bi'" >> /root/.bashrc
> . /root/.bashrc
>
> Not a big fan of aliases, but I was inspired by what what the Paclid's
asked of Geordi LaForge - Make it go! Make it go fast!

You could always use shell functions instead of aliases, they often look
cleaner ...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20160127/e1a23806/attachment.html>