On 3/16/22 02:28, Henrik Carlqvist wrote:
> On Tue, 15 Mar 2022 19:23:04 -0400, bad sector wrote:
>>> The short of the long is that binutils was NOT aboard. This is on my
>>> laptop, later tonight I'll check the desktop.
>>
>> wasn't installed on the desktop either (64 bit both machines)
>
> Unless you have made a full install you can expect that more packages
> from SBO will fail to build.

That brings me to my second question for yesterday which was slackware
day :-)

I perhaps mistakenly thought that a full install meant clicking the
'install everything' option on the DVD, as I have always done, though
now there seems to be some doubt about this.

In desperation I looked at the slackpkg 'upgrade-all' option which I
understood to mean, well, upgrading i.e. elevating a distro from one
stable version # to a higher stable version #. So I was surprised to see
it install all manner of stuff on my fresh v-15.0 as it upgraded it to
v-15.0.

Maybe I should have clarified this first. Oh well, the process allowed
me to install a few more SBO packages so why knock it?

On a 15.0 system and in the absence of a higher stable #, does 'slackpkg
upgrade-all' install 15.0 packages that are not on the distro DVD, or
does it install packages from current/unstable, or...?

--
https://i.imgur.com/arA6B5R.png

On Wed, 16 Mar 2022 08:51:45 -0400, bad sector wrote:

> On 3/16/22 02:28, Henrik Carlqvist wrote:
>> On Tue, 15 Mar 2022 19:23:04 -0400, bad sector wrote:
>>>> The short of the long is that binutils was NOT aboard. This is on my
>>>> laptop, later tonight I'll check the desktop.
>>>
>>> wasn't installed on the desktop either (64 bit both machines)
>>
>> Unless you have made a full install you can expect that more packages
>> from SBO will fail to build.
>
> That brings me to my second question for yesterday which was slackware
> day :-)
>
> I perhaps mistakenly thought that a full install meant clicking the
> 'install everything' option on the DVD, as I have always done, though
> now there seems to be some doubt about this.

I have not yet installed 15.0 myself, but in earlier versions of
Slackware that is the proper way to get a full install. Of course many
things could still go wrong. The installation media might be broken. Some
partiotion might get filled up during installation. Broken hardware could
cause all kinds of weird behavior. However, as you failed to get binutils
installed on both yout laptop and desktop my guess is that something is
broken on your installation media. Did you check the iso md5sum before
burning it to a DVD?
> On a 15.0 system and in the absence of a higher stable #, does 'slackpkg
> upgrade-all' install 15.0 packages that are not on the distro DVD, or
> does it install packages from current/unstable, or...?

I haven't used slackpkg myself, but since 15.0 was released there have
been a number of security patches:
http://www.slackware.com/changelog/stable.php?cpu=x86_64

Could it be that slackpkg upgraded your system with those patches? If so
you should now have a number of packages installed which are named
*_slack15.0.

regards Henrik

On 3/16/22 13:47, Henrik Carlqvist wrote:
> On Wed, 16 Mar 2022 08:51:45 -0400, bad sector wrote:
>
>> On 3/16/22 02:28, Henrik Carlqvist wrote:
>>> On Tue, 15 Mar 2022 19:23:04 -0400, bad sector wrote:
>>>>> The short of the long is that binutils was NOT aboard. This is on my
>>>>> laptop, later tonight I'll check the desktop.
>>>>
>>>> wasn't installed on the desktop either (64 bit both machines)
>>>
>>> Unless you have made a full install you can expect that more packages
>>> from SBO will fail to build.
>>
>> That brings me to my second question for yesterday which was slackware
>> day :-)
>>
>> I perhaps mistakenly thought that a full install meant clicking the
>> 'install everything' option on the DVD, as I have always done, though
>> now there seems to be some doubt about this.
>
> I have not yet installed 15.0 myself, but in earlier versions of
> Slackware that is the proper way to get a full install. Of course many
> things could still go wrong. The installation media might be broken. Some
> partiotion might get filled up during installation. Broken hardware could
> cause all kinds of weird behavior. However, as you failed to get binutils
> installed on both yout laptop and desktop my guess is that something is
> broken on your installation media. Did you check the iso md5sum before
> burning it to a DVD?

That was it, and no I didn't. See my other reply.

.
>> On a 15.0 system and in the absence of a higher stable #, does 'slackpkg
>> upgrade-all' install 15.0 packages that are not on the distro DVD, or
>> does it install packages from current/unstable, or...?
>
> I haven't used slackpkg myself, but since 15.0 was released there have
> been a number of security patches:
> http://www.slackware.com/changelog/stable.php?cpu=x86_64

I normally ignore many technical warnings or alerts for a first installation the purpose of which is a dry run that's going to be wiped anyway.

> Could it be that slackpkg upgraded your system with those patches? If so
> you should now have a number of packages installed which are named
> *_slack15.0.

How would I find those?

There's tons of 'slackware ways' that I have to soak up. Is there a way to correct the installation from the DVD or from online repos to make sure that everything is installed? Partly an academic question given that I will make a new DVD anyway and almost certainly reinstall on both machines.

--
Devuan GNU/Linux 4 (chimaera), Kernel=5.10.0-11-amd64 on x86_64,
DM=Unknown, DE=XFCE, ST=x11,grub2, GPT, BIOS-boot

On Wed, 16 Mar 2022 20:21:06 -0400, bad sector wrote:

> On 3/16/22 13:47, Henrik Carlqvist wrote:
>> Could it be that slackpkg upgraded your system with those patches? If
>> so you should now have a number of packages installed which are named
>> *_slack15.0.
>
> How would I find those?

In all versions of Slackware that I have been running there have been a
file for each package installed in /var/log/packags. I haven't tried 15.0
yet, but if I understand things correctly, the contents of that directory
might have been moved to /var/lib/pkgtools.
> There's tons of 'slackware ways' that I have to soak up. Is there a way
> to correct the installation from the DVD or from online repos to make
> sure that everything is installed? Partly an academic question given
> that I will make a new DVD anyway and almost certainly reinstall on both
> machines.

I run the following Makefile in each directory containing upgraded or
possibly uninstalled packages:

-8<------------------------------
PACKAGES = $(wildcard *.t?z)
LOG_FILES = $(PACKAGES:%.tgz=/var/log/packages/%) \
$(PACKAGES:%.txz=/var/log/packages/%)
VERSION_FILE = $(wildcard sla*-version)

all: Check_Version $(sort $(LOG_FILES))

/var/log/packages/%: %.tgz
upgradepkg --install-new --reinstall $<

/var/log/packages/%: %.txz
upgradepkg --install-new --reinstall $<

Check_Version:
diff $(VERSION_FILE) /etc/$(VERSION_FILE)
-8<------------------------------

However, my directories with packages also contain a copy of /etc/
slackware-version to avoid that I install packages on the wrong version
of Slackware. Again, on 15.0, you might have to modify the Makefile to
look for installed packages in another directory than /var/log/packages.

regards Henrik

On 3/17/22 02:44, Henrik Carlqvist wrote:
> On Wed, 16 Mar 2022 20:21:06 -0400, bad sector wrote:
>
>> On 3/16/22 13:47, Henrik Carlqvist wrote:
>>> Could it be that slackpkg upgraded your system with those patches? If
>>> so you should now have a number of packages installed which are named
>>> *_slack15.0.
>>
>> How would I find those?
>
> In all versions of Slackware that I have been running there have been a
> file for each package installed in /var/log/packags. I haven't tried 15.0
> yet, but if I understand things correctly, the contents of that directory
> might have been moved to /var/lib/pkgtools.

working on my laptop, it looks like it did do package upgrades but no
installs of missing packages; binutils is installed so I must have
installed that manually

# ls /0/sa03/var/lib/pkgtools/packages/*_slack15.0
/0/sa03/var/lib/pkgtools/packages/aaa_base-15.0-x86_64-4_slack15.0
/0/sa03/var/lib/pkgtools/packages/at-3.2.3-x86_64-1_slack15.0
/0/sa03/var/lib/pkgtools/packages/boost-1.78.0-x86_64-2_slack15.0
/0/sa03/var/lib/pkgtools/packages/ca-certificates-20220309-noarch-1_slack15.0
/0/sa03/var/lib/pkgtools/packages/cyrus-sasl-2.1.28-x86_64-1_slack15.0
/0/sa03/var/lib/pkgtools/packages/expat-2.4.7-x86_64-1_slack15.0
/0/sa03/var/lib/pkgtools/packages/flac-1.3.4-x86_64-1_slack15.0
/0/sa03/var/lib/pkgtools/packages/httpd-2.4.53-x86_64-1_slack15.0
/0/sa03/var/lib/pkgtools/packages/libxml2-2.9.13-x86_64-1_slack15.0
/0/sa03/var/lib/pkgtools/packages/libxslt-1.1.35-x86_64-1_slack15.0
/0/sa03/var/lib/pkgtools/packages/mariadb-10.5.15-x86_64-2_slack15.0
/0/sa03/var/lib/pkgtools/packages/mozilla-firefox-91.7.1esr-x86_64-1_slack15.0
/0/sa03/var/lib/pkgtools/packages/mozilla-thunderbird-91.7.0-x86_64-1_slack15.0
/0/sa03/var/lib/pkgtools/packages/php-7.4.28-x86_64-1_slack15.0
/0/sa03/var/lib/pkgtools/packages/polkit-0.120-x86_64-3_slack15.0
/0/sa03/var/lib/pkgtools/packages/seamonkey-2.53.11-x86_64-1_slack15.0
/0/sa03/var/lib/pkgtools/packages/util-linux-2.37.4-x86_64-1_slack15.0

>> There's tons of 'slackware ways' that I have to soak up. Is there a way
>> to correct the installation from the DVD or from online repos to make
>> sure that everything is installed? Partly an academic question given
>> that I will make a new DVD anyway and almost certainly reinstall on both
>> machines.
>
> I run the following Makefile in each directory containing upgraded or
> possibly uninstalled packages:
>
> -8<------------------------------
> PACKAGES = $(wildcard *.t?z)
> LOG_FILES = $(PACKAGES:%.tgz=/var/log/packages/%) \
> $(PACKAGES:%.txz=/var/log/packages/%)
> VERSION_FILE = $(wildcard sla*-version)
>
> all: Check_Version $(sort $(LOG_FILES))
>
>
> /var/log/packages/%: %.tgz
> upgradepkg --install-new --reinstall $<
>
> /var/log/packages/%: %.txz
> upgradepkg --install-new --reinstall $<
>
> Check_Version:
> diff $(VERSION_FILE) /etc/$(VERSION_FILE)
> -8<------------------------------
>
> However, my directories with packages also contain a copy of /etc/
> slackware-version to avoid that I install packages on the wrong version
> of Slackware. Again, on 15.0, you might have to modify the Makefile to
> look for installed packages in another directory than /var/log/packages.

Waaaay over my head, though I might try it later if I know what it's
supposed to do :-)

Right now I have to resolve a confidence issue and then decide on fresh
reinstalls. I've checked the md5 on the 64-bit iso file used and it's
good. I have also downloaded the 32 bit file and a new 64-bit one for
insurance. Their md5's also check out good.

As seen elsewhere it appears that my install DVD was defective as
binutils did not get installed on either machine originally, more
packages in addition failed to install on an aborted test install
yesterday. Burning anew is thus inevitable, already underway.

Do I now go for the reinstalls or do I attempt to correct/salvage the
existing ones? My home rags are on another drive and a maximum of maybe
20 applications not in the standard iso image are needed from SBO, so
fresh reinstalls would not be such horrors.

--
my slack DT https://i.imgur.com/Mjrw9Wm.png

On 3/17/22 11:04, bad sector wrote:

> Do I now go for the reinstalls or do I attempt to correct/salvage the
> existing ones? My home rags are on another drive and a maximum of maybe
> 20 applications not in the standard iso image are needed from SBO, so
> fresh reinstalls would not be such horrors.
>
> --
> my slack DT https://i.imgur.com/Mjrw9Wm.png

what if I just reinstall on top of the old ones overwriting?

That would assure that everything that needs to be aboard is aboard and
then I could repeat some of the updates/app-packages if needed.

bad sector <forgetski@postit_invalid_.gov> wrote:
> On 3/17/22 11:04, bad sector wrote:
>
>> Do I now go for the reinstalls or do I attempt to correct/salvage the
>> existing ones? My home rags are on another drive and a maximum of maybe
>> 20 applications not in the standard iso image are needed from SBO, so
>> fresh reinstalls would not be such horrors.
>>
>> --
>> my slack DT https://i.imgur.com/Mjrw9Wm.png
>
> what if I just reinstall on top of the old ones overwriting?

The computer will expend time and effort unpacking, and overwriting,
everything.

If you made any customizations to config files (i.e. /etc/) then those
too will also be overwritten.

> That would assure that everything that needs to be aboard is aboard and
> then I could repeat some of the updates/app-packages if needed.

Unless you can easily determine what got missed, a 'reinstall' is
probably the fastest, and easiest, way to make sure nothing has been
missed.

Don't, however, just skip past any "errors" should they be reported
this time.

On 3/17/22 15:32, Rich wrote:
> bad sector <forgetski@postit_invalid_.gov> wrote:
>> On 3/17/22 11:04, bad sector wrote:
>>
>>> Do I now go for the reinstalls or do I attempt to correct/salvage the
>>> existing ones? My home rags are on another drive and a maximum of maybe
>>> 20 applications not in the standard iso image are needed from SBO, so
>>> fresh reinstalls would not be such horrors.
>>>
>>> --
>>> my slack DT https://i.imgur.com/Mjrw9Wm.png
>>
>> what if I just reinstall on top of the old ones overwriting?
>
> The computer will expend time and effort unpacking, and overwriting,
> everything.
>
> If you made any customizations to config files (i.e. /etc/) then those
> too will also be overwritten.
>
>> That would assure that everything that needs to be aboard is aboard and
>> then I could repeat some of the updates/app-packages if needed.
>
> Unless you can easily determine what got missed, a 'reinstall' is
> probably the fastest, and easiest, way to make sure nothing has been
> missed.
>
> Don't, however, just skip past any "errors" should they be reported
> this time.

First I just did an overwrite to see, it lead to problems so I repeated
with a formatting install. No errors of any sort this time :-)

With the weekend coming up I should be back where I was on both machines
by Monday, with nothing missing.