[Sbopkg] - sqg generates wrong queue file for "linphone"
 

Hi all,
I generated queue file with sqg to install linphone using sbopkg.

I'm on Slackware-14.2 and I use:
The issue regards that generated queue file:
When sbopkg process that queue some packages don't compile correctly and final package linphone can't be built...
The problem is the above queue is wrong.
It should be:
Thanks to Ponce who shared his working queue for comparison on slacky.eu forum. I tried it with sbopkg and that linphone queue worked: now I have linphone installed on my system.

So how can I find where the issue is?
Could be a sqg bug?
Or something broken on my sbopkg local files?

Thank you in advance for any suggests!
Bye :)

I wonder if your local repo is corrupt somehow. I would try removing it and then generating it again, like this:

Then try generating the queue again.

Thank you!
I'll try... but where exactly could be the problem?

All I can think of is that either some of your .info files are missing the proper requirements information, or there are some directories missing from the repository altogether. If you want to dig into it, back up /var/lib/sbopkg/SBo/14.2 first, and try to manually work recursively through the requirements for linphone, starting at whatever is listed in linphone.info.

In the meantime, I tried your solution without backup...
Anyway it doesn't solve.

I read a topic in which was suggested to delete the whole content of dir /var/lib/sbopkg/*
I tried:

Maybe the problem was related to many directories in /var/lib/sbopkg/SBo other than the branches dir like "14.2" and so on, there were a tree of the repo in that dir... that tree now is just present under /var/lib/sbopkg/SBo/14.2/, and not more in /var/lib/sbopkg/SBo/

Okay, so it looks like removing everything in /var/lib/sbopkg worked, correct? The queue file is right now.

It's possible that it was building the queue from a different version of the repo (ie, not 14.2), but without doing more digging, it's only a guess.

mine produce the correct queue
another possible reason is that you haven't sync with the latest changes in the repository because there was a new dep introduced and 2nd dep also got changed.

Yes, I removed "the content" of that dir (there is a "*" at the end ---> "/var/lib/sbopkg/*" ).

Sorry, I made a mistake in above solving procedure: a repo sync is needed too after the "remove":

After that, sqg works properly again.
I had looked at the content of the above directory and repo sub-dir "SBo" was not as clean as expected it should contain just branch subdir, "14.2" in my case, but there were many directories other than "14.2".
Now (after cleaning re-sync procedure) I have:
On the contrary, before the remove/re-sync procedure, I had something like:
I mean the "14.2" repo tree was repeated both within the "14.2" sub-dir (as expected) and at the same level! (and this likely reveals something broken in /var/lib/sbopkg/*). I can't say how those subdirs were generated in that wrong path, nor when.. because I erased all...

Anyway, the procedure solves the problem!
Now sqg and sbopkg are working properly and this is what matters! :)

That's probably caused by using current repo which is synced using git instead of rsync

It shouldn't, because it uses the SBo-git directory by default for syncing (/var/lib/sbopkg/SBo-git )...

ups, you are right. It was caused by using master branch instead of 14.2 repo