stable/current bug reports

PartiZan · 03-20-2022, 04:36 PM

After I uninstall ca-certificates, broken links are not removed under /etc/ssl/certs

PartiZan · 03-20-2022, 04:44 PM

When I explicitly install package from patches using "slackpkg install", the dialog shows me both versions, old and patched new one.

For example:
slackpkg install openssl-1.1.1n-x86_64-1_slack15.0

The dialog shows me two packages:
openssl-1.1.1m-x86_64-1
openssl-1.1.1n-x86_64-1_slack15.0

I would expect to see the only new patched version, which I explicitly specified in "slackpkg install"

JayByrd · 03-20-2022, 05:07 PM

Quote:

Originally Posted by PartiZan

When I explicitly install package from patches using "slackpkg install", the dialog shows me both versions, old and patched new one.

For example:
slackpkg install openssl-1.1.1n-x86_64-1_slack15.0

The dialog shows me two packages:
openssl-1.1.1m-x86_64-1
openssl-1.1.1n-x86_64-1_slack15.0

I would expect to see the only new patched version, which I explicitly specified in "slackpkg install"

If this is what you expect, then you need to use "upgrade", not "install".

When you use "upgrade," the older package will be removed before installing the new one.

PartiZan · 03-20-2022, 05:13 PM

Quote:

Originally Posted by JayByrd

If this is what you expect, then you need to use "upgrade", not "install".

When you use "upgrade," the older package will be removed before installing the new one.

Yes, but what if I don't have some package on the system and want to install it. Using bash-completion I pick the latest patched version, hit enter and the dialog offers me old package too. This is wrong/weird behavior of slackpkg script.

JayByrd · 03-20-2022, 05:21 PM

Quote:

Originally Posted by PartiZan

Yes, but what if I don't have some package on the system and want to install it. Using bash-completion I pick the latest patched version, hit enter and the dialog offers me old package too. This is wrong/weird behavior of slackpkg script.

So decline the offer and simply uncheck the older one. It's not wrong, and, to my knowledge, it's how it has always worked.

marav · 03-20-2022, 05:22 PM

Quote:

Originally Posted by PartiZan

Yes, but what if I don't have some package on the system and want to install it. Using bash-completion I pick the latest patched version, hit enter and the dialog offers me old package too. This is wrong/weird behavior of slackpkg script.

bash-completion never completes package names

cwizardone · 03-20-2022, 05:24 PM

Quote:

upgradepkg --reinstall --install-new packagename.txz

But, if you want to purposely install a package and not replace the old, e.g., a kernel, then just use,

Quote:

installpkg packagename.txz

PartiZan · 03-20-2022, 05:28 PM

Quote:

Originally Posted by marav

bash-completion never completes package names

It does.

15.0 version: type "slackpkg install openssl" and hit TAB. You'll see two versions.

PartiZan · 03-20-2022, 05:29 PM

Quote:

Originally Posted by JayByrd

So decline the offer and simply uncheck the older one. It's not wrong, and, to my knowledge, it's how it has always worked.

I can, but this is against of logic and common sense to offer old package as well, when I requested new one.

PartiZan · 03-20-2022, 05:30 PM

Quote:

Originally Posted by cwizardone

But, if you want to purposely install a package and not replace the old, e.g., a kernel, then just use,

I'm talking about ap/slackpkg

JayByrd · 03-20-2022, 05:33 PM

Quote:

Originally Posted by PartiZan

I can, but this is against of logic to offer old package when I requested new one.

"Against of logic" ???

Your "logic" is against of/for/by prepositions.

What a joke. I'm through with you.

marav · 03-20-2022, 06:12 PM

Quote:

Originally Posted by PartiZan

It does.

15.0 version: type "slackpkg install openssl" and hit TAB. You'll see two versions.

ok, I see

there is no issue with slackpkg
but it's only because of bash-completion

Code:

      install | reinstall | upgrade | blacklist | download)
            _filedir
            COMPREPLY+=($(compgen -W 'a ap d e f k kde kdei l n t tcl x
                xap xfce y' -- "$cur"))
            COMPREPLY+=($(cut -f 6 -d\  "${WORKDIR}/pkglist" 2>/dev/null |
                command grep "^$cur"))
            return

it checks repositories (a, ap, d ...)
where openssl-1.1.1m is

Code:

http://ftp.slackware.com/pub/slackware/slackware64-15.0/slackware64/n/openssl-1.1.1m-x86_64-1.txz

and also pkglist
where openssl-1.1.1n is

Code:

# grep openssl-1.1.1 /var/lib/slackpkg/pkglist
slackware64 openssl 1.1.1n x86_64 1 openssl-1.1.1n-x86_64-1 ./slackware64/n txz

marav · 03-20-2022, 06:33 PM

Quote:

Originally Posted by PartiZan

After I uninstall ca-certificates, broken links are not removed under /etc/ssl/certs

Yes
symlink are created by /usr/sbin/update-ca-certificates

Code:

add() {
  CERT="$1"
  PEM="$ETCCERTSDIR/$(basename "$CERT" .crt | sed -e 's/ /_/g' \
                                                  -e 's/[()]/=/g' \
                                                  -e 's/,/_/g').pem"
  if ! test -e "$PEM" || [ "$(readlink "$PEM")" != "$CERT" ]
  then
    ln -sf "$CERT" "$PEM"
    echo "+$PEM" >> "$ADDED"
  fi
  # Add trailing newline to certificate, if it is missing (#635570)
  sed -e '$a\' "$CERT" >> "$TEMPBUNDLE"
}

So, if you remove ca-certificates (apart from the fact that I don't see the point)
you must run the command again, but you can't because /usr/sbin/update-ca-certificates is a part of the package ca-certificates :-)

marav · 03-20-2022, 06:34 PM

issue #1 : solved
issue #2 : solved

happy ?

bassmadrigal · 03-20-2022, 06:43 PM

Quote:

Originally Posted by PartiZan

When I explicitly install package from patches using "slackpkg install", the dialog shows me both versions, old and patched new one.

For example:
slackpkg install openssl-1.1.1n-x86_64-1_slack15.0

The dialog shows me two packages:
openssl-1.1.1m-x86_64-1
openssl-1.1.1n-x86_64-1_slack15.0

I would expect to see the only new patched version, which I explicitly specified in "slackpkg install"

slackpkg is giving you the ability to install the original package or the patched package. I see nothing wrong with that. It's no different than what someone is presented when browsing through 15.0's mirror. You'll have the original package under slackware{64}/ and any changes under patches/.

slackpkg upgrade-all is the one that has the logic built in to show you replaced stock packages with newer ones within patches/. Why should bash-completion have that logic? With slackpkg install, you can either install the stock or patched version and it's presenting you both options. Bash completion shouldn't be deciding which one you want to install.