Yes,
I was wrong to underestimate this criticism.

However
CACHEUPDATE=on
in config file trap the error.

Started development branch (bugfix)

Curious ...

Have Y'All considered using rsync instead of wget if possible ?

rsync will conserver bandwidth if the files are already on the User's System ...

-- kjh

rsync is useful to download an entire tree, not just a file (even if it is possible).
You can try to customize the
DOWNLOADCMD=
entry in configuration file to use rsync if you want

But This is not useful to conserve bandwidth.
slackpkg does not download a package if it is already downloaded, and it you set CACHEUPDATE=on it does not redownload metadatas too if they are not changed.

Problem with 17.0-2mt...the repositories for 14.1 are replaced with 14.2 in the conf file. Then when I corrected back to 14.1 the file connections are being refused.

I do not understand.
Please post the output of slackpkg update.

Slackware 14.1 x86_64 and slackpkgplus-17.0-noarch-1mt installed. I ran sudo /usr/sbin/slackpkg update then install-new and upgrade-all.
The list of upgrades presented slackpkgplus-17.0-noarch-2mt. I accepted the udgrade and MERGED my existing slackpkgplus.conf with the slackpkgplus.conf.new and accepted the selections to replace the MIRRORPLUS addresses for 'multilib', 'alienbob', 'restricted', and 'ktown'. After running slackpkg update gpg, and attempting to run slackpgk update, I recieved the message that some respositories were not configured. So I cat /etc/slackpkg/slackpkgplus.conf and find that the 14.1 version mirrors are no longer in the slackpkgplus mirror lists. I realize that you comment out the MIRRORPLUS respositories, because not everyone is using them. However, I wasn't expected the new commented ones to be for 14.2 already. So I edit slackpkgplus.conf and created MIRRORPLUS address for the 14.1 missing repositories, based on the 14.2 addresses, simply replacing 14.2 with 14.1. Then rerun slackpkg update gpg, and slackpkg update. When running slackpkg update I'm told the connections are refused.

Alien's' repository connection refusals as of 20:30 GMT are now accepted, must have been a temporary connection issue, although I waited 10 minutes at 16:45 GMT between update attempts before posting earlier.

I also note that alienbob's ChangeLog.Txt files are not found in the repository address but one or two levels higher in the tree. Thank you for including code that will search a higher level than the address provided for the changelog.

Hope this better explains what I experienced. Cheers, BrianA_MN

I do not understand if the problem was for all repositories or just for alienbob (it was temporary down?), and if it still remain for some repository.

I added 14.2 repositories (commented) since official slackpkg in slackware-current have added it (even if it does not exists).


Yes, changelog in many repositories is some levels higher in the tree; thanks to phenixia2003 for the code ;). In slackpkg+-1.7.0-noarch-1mt this did cause some 404 error, solved in -2mt release (also consider to use CACHEUPDATE=on for a better output and performance in slackpkg update).
Unfortunately in most of repositories having the changelog out of main tree, that changelog does not contains a slackware-compatible changelog format; for that repositories it will be ignored.

Thank you for feedback.

It was for only repositories from alienbob (ktown, alienbob, multilib, restricted).
I understand why you added the 14.2 repositories, but, shouldn't the still functional "official" repositories be the preference. If 14.2 was the official "long term" or "stable" (not sure which tem Pat prefers), then it would make sense to use it rather than 14.1. It is like the slacke18, the current stable version of the "E" environment, you dropped slacke17 and changed to slacke18 when it was officially announced as stable. I know you still include the other older releasese in the MIRRORPLUS repository list below. That is a nice reference and appreciated.

Keep up the great work. Cheers, BrianA_MN.

In slackpkg+ prior 1.7, I put a default configuration with UNCOMMENTED 14.1 repositories.
Well, I think that this is not the best practice, even if it works.
So in slackpkg+ 1.7 I prefered to add a commented configuration, and since Patrick had declared that the stable is very near to release
I have added a configuration ready for the new stable release to avoid to remake a new package in few days.

Unfortunately seems that Patrick has a strange conception of the word "last" :D, but have no sense now to repackage it with 14.1 repositories.

However all really working repositories are listed in /usr/doc/slackpkg+-*/repositories.lst

Regard slackE, I do not know really it.

For all repositories, simply I look for "PACKAGES.TXT" on google.

Then tipically if the author contact me, I fix it with his instruction, otherwise I sometime check for updates. Also note that the repositories.txt is not an official or exaustive or authoritative document, and repositories in that list cannot be considered as trusted/full working/supported (the only supported repository is the slackware official), and I'm not constrained to reflect/follow the repositories changes as is the repositories authors are not constrained to reflect/comunicate his repository changes; and anyone can add a repository to slackpkgplus.conf also if it is not in repositories.txt (someone asked me to remove his own repository from that list, and I removed it, but it still remain in my personal slackpkgplus.conf ;) )
I just TRY to keep it updated, and sometime the repository's author help me.

Casually I saw slacke18 about one year ago, while slacke18 was released about two years ago.
But my last contact with the author was about 3 years ago.

Recently I had thought to remove slacke totally from repository.txt since both repository and site are stalled to two years ago. But I've desisted

Thanks for the clarification. Best Regards, BrianA_MN

Maybe in this case it would be good to mimic slackpkg's mirror list and just keep all of them commented out and require the user to go in and enable what they want to use. Then you don't accidentally install the wrong versions of packages because a user forgot to change the mirror to a different version.

I think it would be best to err on the side of caution and require the user to configure their config file and uncomment the mirrors they wish to use.

@bassmadrigal Actually, that is what zerouno is doing. He setup the slackpkgplus.conf with the 14.2 MIRROR addresses but they are commented out. I apologize if my earlier explanation was not clear on that point.

Since I don't know if you are familiar with slackpkgplus, and other newbies may read this later, let me further explain. When using slackpkgplus if a new slackpkgplus.conf is available one of the options is to merge your existing .conf with the .conf.new file profided with upgrades. In the merger process you are shown both the existing config and the proposed config, side by side, and you choose which you want in the new merged file. In the .conf.new zerouno comments out all mirrors and you have to keep your old lines or after accepting the new, then "edit"(another option after the merge) the conf file and uncomment the new mirror lines. My feedback was more about the lack of the 14.1 mirrors as default provided config and zerouno's choice to include 14.2 mirror lines. I follow his reasoning, but I feel that until Slackware release is stable, as announced by Pat, that configs for "stable" releases should be primary and "current" should be optional in the mirror list. Just a differnce of opinion. Hey, zerouno is the developer and can and should do what he feels is best for his application/packaging. I'm just one user of many thousands of slackpkgplus, and I'm sure we all have our own prefernces. As far as I know more "current" users are using the application than "stable'. Mine was only feedback not criticism. Cheers, BrianA_MN

Hi zerouno, possible the problem I found: when I tried to search by the word 'slackpkg', I get
I know the reason: it appears because we do below:
The pattern 'slackpkg' matches the slackpkg and then slackpkg+, both is installed, and as described in the code above, slackpkg+ will be marked as uninstalled and masked... Here is a debug output (via sh -x slackpkg search slackpkg). I will look at this later.

Hello,


This is the conjunction of the use of grep -E and the presence of a "+" in slackpkg+. Therefore, the "+" is interpreted by grep as a repetition operator, so, slackpkg+-1.7.0-noarch-2mt cannot be found in ${TMPDIR}/tmplist. Example:

Using grep -E :
Using grep :
Since the pattern is always a package name, I don't see any reason to use an extended grep :

--
SeB