[PLUG] slackpkg upgrade-all error

[Dick Steffens]

I've been through a first round of slackpkg updating.

Ran slackpkg update gpg
    Successful

Ran slackpkg update
    Successful

Ran slackpkg install-new
    Successful

Ran slackpkg upgrade-all
    Successful, but required it to be run again because slackpkg was
upgraded.

Ran slackpkg upgrade-all again
    Wanted slackpkg update first.

Ran slackpkg update.
    Successful

Ran slackpkg upgrade-all again
    Finished with warning:
        One of more errors occurred while slackpkg was running:
        /usr/libexec/slackpkg/core-functions.sh: line 18: /bincat: No
such file or directory

Mr. Google didn't immediately provide useful comments.

Is bincat something important?

[Rich Shepard]

Post by Dick Steffens
Ran slackpkg upgrade-all again
        /usr/libexec/slackpkg/core-functions.sh: line 18: /bincat: No such
file or directory
Is bincat something important?

Dick,

I've not had that error message show up here in the 15 years I've run
slackware, so ignore it. There's no bincat on my systems so I'd not worry
about it. Here, it's not in core-functions.sh.

I don't recall how to sign up for security patch notices, but running
slackpkg update once a week will compare what's installed with what's in the
change logs on the repository you use (I assume it's
ftp://ftp.osuosl.org/.2/slackware/slackware64-14.2/), if there's nothing new
the script will tell you this. If there are upgraded packages follow that by
slackpkg upgrade-all.

The non-security patches aren't announced via e-mail, but security
upgrades are. So checking once a week is good enough to keep things patched.

Regards,

Rich

[Rich Shepard]

Post by Rich Shepard
The non-security patches aren't announced via e-mail, but security
upgrades are. So checking once a week is good enough to keep things patched.

For example,

# slackpkg update

Updating the package lists...
Downloading...
ChangeLogs
2018-11-23 12:52:19 URL: ftp://ftp.osuosl.org/.2/slackware/slackware64-14.2/ChangeLog.txt [507402] -> "/tmp/slackpkg.sK5RhA/ChangeLog.txt" [1]
Saving ChangeLog.txt from repository slackpkgplus ...

2018-11-23 12:52:21 URL:http://slakfinder.org/slackpkg+/CHECKSUMS.md5 [2200/2200] -> "/tmp/slackpkg.sK5RhA/CHECKSUMS.md5-slackpkgplus" [1]

No changes in ChangeLog.txt between your last update and now.
Do you really want to download all other files (y/N)?

Rich

[Dick Steffens]

Post by Dick Steffens
Ran slackpkg upgrade-all again
        /usr/libexec/slackpkg/core-functions.sh: line 18: /bincat: No
such file or directory
Is bincat something important?

Dick,
  I've not had that error message show up here in the 15 years I've run
slackware, so ignore it. There's no bincat on my systems so I'd not worry
about it. Here, it's not in core-functions.sh.

Ignoring works for me. I hope to remain blissful.

  I don't recall how to sign up for security patch notices,

They use ***@slackware.com

subscribe slackware-security

which I have done.

but running
slackpkg update once a week will compare what's installed with what's in the
change logs on the repository you use (I assume it's
ftp://ftp.osuosl.org/.2/slackware/slackware64-14.2/), if there's nothing new
the script will tell you this. If there are upgraded packages follow that by
slackpkg upgrade-all.
  The non-security patches aren't announced via e-mail, but security
upgrades are. So checking once a week is good enough to keep things patched.

I'll keep that in mind. This laptop will be living down in the living
room, so I'll need to pay closer attention to it.

Thanks.