LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 12-17-2022, 05:08 PM   #1
LuckyCyborg
Senior Member
 
Registered: Mar 2010
Posts: 3,505

Rep: Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320
WARNING! DO NOT APPLY the batch Sat Dec 17 21:14:11 UTC 2022 unless you have applied previously all updates. Conflict: XZ vs. aaa_libraries


At least IF you do not did the last 2 updates (like I did) and you do them in a batch, the latest update of XZ gives:

Code:
root@darkstar:~/works/test# xz
xz: /lib64/liblzma.so.5: version `XZ_5.4' not found (required by xz)
THIS IS FREAKING WRONG, because the upgradepkg will broke your packages database, and of course, will do nothing good.

Additionally, you can't even rollback, because XZ is broken.

Workaround: DO NOT APPLY THE UPDATE unless you have applied previously all updates.

Last edited by LuckyCyborg; 12-17-2022 at 05:56 PM.
 
Old 12-17-2022, 05:26 PM   #2
Aeterna
Senior Member
 
Registered: Aug 2017
Location: Terra Mater
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,008

Rep: Reputation: Disabled
stop screaming
works fine here. liblzma.so.5 is installed
 
1 members found this post helpful.
Old 12-17-2022, 05:30 PM   #3
LuckyCyborg
Senior Member
 
Registered: Mar 2010
Posts: 3,505

Original Poster
Rep: Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320
Quote:
Originally Posted by Aeterna View Post
stop screaming
works fine here. liblzma.so.5 is installed
I do NOT scream, buddy! I never scream. It's a warning for others.

BTW, did you did you did the last 2 updates in a batch?

I talk about this
Code:
Sat Dec 17 21:14:11 UTC 2022
a/xz-5.4.0-x86_64-1.txz:  Upgraded.
l/harfbuzz-6.0.0-x86_64-1.txz:  Upgraded.
l/libmpc-1.3.1-x86_64-1.txz:  Upgraded.
n/NetworkManager-1.40.8-x86_64-1.txz:  Upgraded.
n/samba-4.17.4-x86_64-1.txz:  Upgraded.
  This update fixes security issues:
  This is the Samba CVE for the Windows Kerberos RC4-HMAC Elevation of
  Privilege Vulnerability disclosed by Microsoft on Nov 8 2022.
  A Samba Active Directory DC will issue weak rc4-hmac session keys for
  use between modern clients and servers despite all modern Kerberos
  implementations supporting the aes256-cts-hmac-sha1-96 cipher.
  On Samba Active Directory DCs and members
  'kerberos encryption types = legacy'
  would force rc4-hmac as a client even if the server supports
  aes128-cts-hmac-sha1-96 and/or aes256-cts-hmac-sha1-96.
  This is the Samba CVE for the Windows Kerberos Elevation of Privilege
  Vulnerability disclosed by Microsoft on Nov 8 2022.
  A service account with the special constrained delegation permission
  could forge a more powerful ticket than the one it was presented with.
  The "RC4" protection of the NetLogon Secure channel uses the same
  algorithms as rc4-hmac cryptography in Kerberos, and so must also be
  assumed to be weak.
  Note that there are several important behavior changes included in this
  release, which may cause compatibility problems interacting with system
  still expecting the former behavior.
  Please read the advisories of CVE-2022-37966, CVE-2022-37967 and
  CVE-2022-38023 carefully!
  For more information, see:
    https://www.samba.org/samba/security/CVE-2022-37966.html
    https://www.samba.org/samba/security/CVE-2022-37967.html
    https://www.samba.org/samba/security/CVE-2022-38023.html
    https://www.cve.org/CVERecord?id=CVE-2022-37966
    https://www.cve.org/CVERecord?id=CVE-2022-37967
    https://www.cve.org/CVERecord?id=CVE-2022-38023
  (* Security fix *)
xfce/exo-4.18.0-x86_64-1.txz:  Upgraded.
xfce/garcon-4.18.0-x86_64-1.txz:  Upgraded.
xfce/libxfce4ui-4.18.0-x86_64-1.txz:  Upgraded.
xfce/libxfce4util-4.18.0-x86_64-1.txz:  Upgraded.
xfce/thunar-4.18.0-x86_64-1.txz:  Upgraded.
xfce/thunar-volman-4.18.0-x86_64-1.txz:  Upgraded.
xfce/tumbler-4.18.0-x86_64-1.txz:  Upgraded.
xfce/xfce4-appfinder-4.18.0-x86_64-1.txz:  Upgraded.
xfce/xfce4-dev-tools-4.18.0-x86_64-1.txz:  Upgraded.
xfce/xfce4-notifyd-0.6.5-x86_64-1.txz:  Upgraded.
xfce/xfce4-panel-4.18.0-x86_64-1.txz:  Upgraded.
xfce/xfce4-power-manager-4.18.0-x86_64-1.txz:  Upgraded.
xfce/xfce4-session-4.18.0-x86_64-1.txz:  Upgraded.
xfce/xfce4-settings-4.18.0-x86_64-1.txz:  Upgraded.
xfce/xfce4-weather-plugin-0.11.0-x86_64-1.txz:  Upgraded.
xfce/xfconf-4.18.0-x86_64-1.txz:  Upgraded.
xfce/xfdesktop-4.18.0-x86_64-1.txz:  Upgraded.
xfce/xfwm4-4.18.0-x86_64-1.txz:  Upgraded.
+--------------------------+
Sat Dec 17 02:40:06 UTC 2022
a/aaa_libraries-15.1-x86_64-14.txz:  Rebuilt.
  Upgraded:  liblzma.so.5.2.9, libpcre2-8.so.0.11.2, libglib-2.0.so.0.7400.3,
  libgmodule-2.0.so.0.7400.3, libpng16.so.16.39.0.
  Removed:  libFLAC++.so.6.3.0, libFLAC.so.8.3.0, libicudata.so.71.1,
  libicui18n.so.71.1, libicuio.so.71.1, libicutest.so.71.1, libicutu.so.71.1,
  libicuuc.so.71.1, libjasper.so.6.0.0.
  Added:  libboost_atomic.so.1.80.0, libboost_chrono.so.1.80.0,
  libboost_container.so.1.80.0, libboost_context.so.1.80.0,
  libboost_contract.so.1.80.0, libboost_coroutine.so.1.80.0,
  libboost_date_time.so.1.80.0, libboost_fiber.so.1.80.0,
  libboost_filesystem.so.1.80.0, libboost_graph.so.1.80.0,
  libboost_iostreams.so.1.80.0, libboost_json.so.1.80.0,
  libboost_locale.so.1.80.0, libboost_log.so.1.80.0,
  libboost_log_setup.so.1.80.0, libboost_math_c99.so.1.80.0,
  libboost_math_c99f.so.1.80.0, libboost_math_c99l.so.1.80.0,
  libboost_math_tr1.so.1.80.0, libboost_math_tr1f.so.1.80.0,
  libboost_math_tr1l.so.1.80.0, libboost_nowide.so.1.80.0,
  libboost_prg_exec_monitor.so.1.80.0, libboost_program_options.so.1.80.0,
  libboost_python27.so.1.80.0, libboost_python39.so.1.80.0,
  libboost_random.so.1.80.0, libboost_regex.so.1.80.0,
  libboost_serialization.so.1.80.0, libboost_stacktrace_addr2line.so.1.80.0,
  libboost_stacktrace_basic.so.1.80.0, libboost_stacktrace_noop.so.1.80.0,
  libboost_system.so.1.80.0, libboost_thread.so.1.80.0,
  libboost_timer.so.1.80.0, libboost_type_erasure.so.1.80.0,
  libboost_unit_test_framework.so.1.80.0, libboost_wave.so.1.80.0,
  libboost_wserialization.so.1.80.0.
ap/pamixer-1.5-x86_64-5.txz:  Rebuilt.
  Recompiled against boost-1.81.0.
kde/kig-22.12.0-x86_64-2.txz:  Rebuilt.
  Recompiled against boost-1.81.0.
kde/kopeninghours-22.12.0-x86_64-2.txz:  Rebuilt.
  Recompiled against boost-1.81.0.
kde/krita-5.1.4-x86_64-2.txz:  Rebuilt.
  Recompiled against boost-1.81.0.
l/boost-1.81.0-x86_64-1.txz:  Upgraded.
  Shared library .so-version bump.
l/cryfs-0.10.3-x86_64-7.txz:  Rebuilt.
  Recompiled against boost-1.81.0.
x/fcitx5-chinese-addons-5.0.16-x86_64-2.txz:  Rebuilt.
  Recompiled against boost-1.81.0.
x/libime-1.0.16-x86_64-2.txz:  Rebuilt.
  Recompiled against boost-1.81.0.
xap/mozilla-firefox-108.0.1-x86_64-1.txz:  Upgraded.
  This is a bugfix release.
  For more information, see:
    https://www.mozilla.org/en-US/firefox/108.0.1/releasenotes/
xfce/elementary-xfce-0.17-x86_64-1.txz:  Upgraded.
 
Old 12-17-2022, 05:31 PM   #4
Markus Wiesner
Member
 
Registered: Mar 2016
Distribution: Slackware
Posts: 146

Rep: Reputation: 237Reputation: 237Reputation: 237
aaa_libraries-15.1-x86_64-14.txz still contains liblzma.so.5.2.9. I assume that, when you install/upgrade this package AFTER xz-5.4.0, the /lib64/liblzma.so.5 symlink (pointing to liblzma.so.5.4.0 after the upgrade of xz) is replaced by a link to the old version?

If i'm right, this should repair the link (and xz):
Code:
/sbin/ldconfig -l /lib64/liblzma.so.5.4.0

Last edited by Markus Wiesner; 12-17-2022 at 05:33 PM.
 
Old 12-17-2022, 05:36 PM   #5
Aeterna
Senior Member
 
Registered: Aug 2017
Location: Terra Mater
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,008

Rep: Reputation: Disabled
Quote:
Originally Posted by LuckyCyborg View Post
I do NOT scream, buddy! I never scream. It's a warning for others.

BTW, did you did you did the last 2 updates in a batch?

I talk about this
Code:
Sat Dec 17 21:14:11 UTC 2022
a/xz-5.4.0-x86_64-1.txz:  Upgraded.
l/harfbuzz-6.0.0-x86_64-1.txz:  Upgraded.
l/libmpc-1.3.1-x86_64-1.txz:  Upgraded.
n/NetworkManager-1.40.8-x86_64-1.txz:  Upgraded.
n/samba-4.17.4-x86_64-1.txz:  Upgraded.
  This update fixes security issues:
  This is the Samba CVE for the Windows Kerberos RC4-HMAC Elevation of
  Privilege Vulnerability disclosed by Microsoft on Nov 8 2022.
  A Samba Active Directory DC will issue weak rc4-hmac session keys for
  use between modern clients and servers despite all modern Kerberos
  implementations supporting the aes256-cts-hmac-sha1-96 cipher.
  On Samba Active Directory DCs and members
  'kerberos encryption types = legacy'
  would force rc4-hmac as a client even if the server supports
  aes128-cts-hmac-sha1-96 and/or aes256-cts-hmac-sha1-96.
  This is the Samba CVE for the Windows Kerberos Elevation of Privilege
  Vulnerability disclosed by Microsoft on Nov 8 2022.
  A service account with the special constrained delegation permission
  could forge a more powerful ticket than the one it was presented with.
  The "RC4" protection of the NetLogon Secure channel uses the same
  algorithms as rc4-hmac cryptography in Kerberos, and so must also be
  assumed to be weak.
  Note that there are several important behavior changes included in this
  release, which may cause compatibility problems interacting with system
  still expecting the former behavior.
  Please read the advisories of CVE-2022-37966, CVE-2022-37967 and
  CVE-2022-38023 carefully!
  For more information, see:
    https://www.samba.org/samba/security/CVE-2022-37966.html
    https://www.samba.org/samba/security/CVE-2022-37967.html
    https://www.samba.org/samba/security/CVE-2022-38023.html
    https://www.cve.org/CVERecord?id=CVE-2022-37966
    https://www.cve.org/CVERecord?id=CVE-2022-37967
    https://www.cve.org/CVERecord?id=CVE-2022-38023
  (* Security fix *)
xfce/exo-4.18.0-x86_64-1.txz:  Upgraded.
xfce/garcon-4.18.0-x86_64-1.txz:  Upgraded.
xfce/libxfce4ui-4.18.0-x86_64-1.txz:  Upgraded.
xfce/libxfce4util-4.18.0-x86_64-1.txz:  Upgraded.
xfce/thunar-4.18.0-x86_64-1.txz:  Upgraded.
xfce/thunar-volman-4.18.0-x86_64-1.txz:  Upgraded.
xfce/tumbler-4.18.0-x86_64-1.txz:  Upgraded.
xfce/xfce4-appfinder-4.18.0-x86_64-1.txz:  Upgraded.
xfce/xfce4-dev-tools-4.18.0-x86_64-1.txz:  Upgraded.
xfce/xfce4-notifyd-0.6.5-x86_64-1.txz:  Upgraded.
xfce/xfce4-panel-4.18.0-x86_64-1.txz:  Upgraded.
xfce/xfce4-power-manager-4.18.0-x86_64-1.txz:  Upgraded.
xfce/xfce4-session-4.18.0-x86_64-1.txz:  Upgraded.
xfce/xfce4-settings-4.18.0-x86_64-1.txz:  Upgraded.
xfce/xfce4-weather-plugin-0.11.0-x86_64-1.txz:  Upgraded.
xfce/xfconf-4.18.0-x86_64-1.txz:  Upgraded.
xfce/xfdesktop-4.18.0-x86_64-1.txz:  Upgraded.
xfce/xfwm4-4.18.0-x86_64-1.txz:  Upgraded.
+--------------------------+
Sat Dec 17 02:40:06 UTC 2022
a/aaa_libraries-15.1-x86_64-14.txz:  Rebuilt.
  Upgraded:  liblzma.so.5.2.9, libpcre2-8.so.0.11.2, libglib-2.0.so.0.7400.3,
  libgmodule-2.0.so.0.7400.3, libpng16.so.16.39.0.
  Removed:  libFLAC++.so.6.3.0, libFLAC.so.8.3.0, libicudata.so.71.1,
  libicui18n.so.71.1, libicuio.so.71.1, libicutest.so.71.1, libicutu.so.71.1,
  libicuuc.so.71.1, libjasper.so.6.0.0.
  Added:  libboost_atomic.so.1.80.0, libboost_chrono.so.1.80.0,
  libboost_container.so.1.80.0, libboost_context.so.1.80.0,
  libboost_contract.so.1.80.0, libboost_coroutine.so.1.80.0,
  libboost_date_time.so.1.80.0, libboost_fiber.so.1.80.0,
  libboost_filesystem.so.1.80.0, libboost_graph.so.1.80.0,
  libboost_iostreams.so.1.80.0, libboost_json.so.1.80.0,
  libboost_locale.so.1.80.0, libboost_log.so.1.80.0,
  libboost_log_setup.so.1.80.0, libboost_math_c99.so.1.80.0,
  libboost_math_c99f.so.1.80.0, libboost_math_c99l.so.1.80.0,
  libboost_math_tr1.so.1.80.0, libboost_math_tr1f.so.1.80.0,
  libboost_math_tr1l.so.1.80.0, libboost_nowide.so.1.80.0,
  libboost_prg_exec_monitor.so.1.80.0, libboost_program_options.so.1.80.0,
  libboost_python27.so.1.80.0, libboost_python39.so.1.80.0,
  libboost_random.so.1.80.0, libboost_regex.so.1.80.0,
  libboost_serialization.so.1.80.0, libboost_stacktrace_addr2line.so.1.80.0,
  libboost_stacktrace_basic.so.1.80.0, libboost_stacktrace_noop.so.1.80.0,
  libboost_system.so.1.80.0, libboost_thread.so.1.80.0,
  libboost_timer.so.1.80.0, libboost_type_erasure.so.1.80.0,
  libboost_unit_test_framework.so.1.80.0, libboost_wave.so.1.80.0,
  libboost_wserialization.so.1.80.0.
ap/pamixer-1.5-x86_64-5.txz:  Rebuilt.
  Recompiled against boost-1.81.0.
kde/kig-22.12.0-x86_64-2.txz:  Rebuilt.
  Recompiled against boost-1.81.0.
kde/kopeninghours-22.12.0-x86_64-2.txz:  Rebuilt.
  Recompiled against boost-1.81.0.
kde/krita-5.1.4-x86_64-2.txz:  Rebuilt.
  Recompiled against boost-1.81.0.
l/boost-1.81.0-x86_64-1.txz:  Upgraded.
  Shared library .so-version bump.
l/cryfs-0.10.3-x86_64-7.txz:  Rebuilt.
  Recompiled against boost-1.81.0.
x/fcitx5-chinese-addons-5.0.16-x86_64-2.txz:  Rebuilt.
  Recompiled against boost-1.81.0.
x/libime-1.0.16-x86_64-2.txz:  Rebuilt.
  Recompiled against boost-1.81.0.
xap/mozilla-firefox-108.0.1-x86_64-1.txz:  Upgraded.
  This is a bugfix release.
  For more information, see:
    https://www.mozilla.org/en-US/firefox/108.0.1/releasenotes/
xfce/elementary-xfce-0.17-x86_64-1.txz:  Upgraded.
yes, I did
 
Old 12-17-2022, 05:37 PM   #6
LuckyCyborg
Senior Member
 
Registered: Mar 2010
Posts: 3,505

Original Poster
Rep: Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320
Quote:
Originally Posted by Aeterna View Post
yes, I did
In a single batch?
 
Old 12-17-2022, 05:41 PM   #7
LuckyCyborg
Senior Member
 
Registered: Mar 2010
Posts: 3,505

Original Poster
Rep: Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320
Quote:
Originally Posted by Markus Wiesner View Post
aaa_libraries-15.1-x86_64-14.txz still contains liblzma.so.5.2.9. I assume that, when you install/upgrade this package AFTER xz-5.4.0, the /lib64/liblzma.so.5 symlink (pointing to liblzma.so.5.4.0 after the upgrade of xz) is replaced by a link to the old version?

If i'm right, this should repair the link (and xz):
Code:
/sbin/ldconfig -l /lib64/liblzma.so.5.4.0
Well, I for one I've fixed already (just before posting) that symlink manually, with "ln -sf" , BUT I can confirm that that is the root issue.

However, I believe that a fix should be issued ASAP, before people to broke theirs systems and their packages database.

Because, there are many who does not follow daily the updates, because of lack of time or interest. Even I can't follow always daily the updates.

And this event made me believe that upgradepkg should check the incoming package's consistency before renaming the /var/log/packages files. Because this conflict between XZ and aaa_libraries makes upgradepkg to rename those files and bail out, the user ending with a broken database.

Last edited by LuckyCyborg; 12-17-2022 at 05:46 PM.
 
1 members found this post helpful.
Old 12-17-2022, 05:49 PM   #8
Markus Wiesner
Member
 
Registered: Mar 2016
Distribution: Slackware
Posts: 146

Rep: Reputation: 237Reputation: 237Reputation: 237
Quote:
Originally Posted by LuckyCyborg View Post
Well, I for one I fixed already the symlink manually, with "ln -sf" , BUT I can confirm that that is the root issue.

However, I believe that a fix should be issued ASAP, before people to broke theirs systems and their packages database.
Yes, of course. But those who already broke their system with this update need a workaround that does not require upgradepkg
 
2 members found this post helpful.
Old 12-17-2022, 06:10 PM   #9
marav
LQ Sage
 
Registered: Sep 2018
Location: Gironde
Distribution: Slackware
Posts: 5,366

Rep: Reputation: 4082Reputation: 4082Reputation: 4082Reputation: 4082Reputation: 4082Reputation: 4082Reputation: 4082Reputation: 4082Reputation: 4082Reputation: 4082Reputation: 4082
So,

aaa_libraries should have been rebuilt after the xz update, right ?
 
3 members found this post helpful.
Old 12-17-2022, 06:12 PM   #10
LuckyCyborg
Senior Member
 
Registered: Mar 2010
Posts: 3,505

Original Poster
Rep: Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320
Quote:
Originally Posted by marav View Post
So,

aaa_libraries should have been rebuilt after the xz update, right ?
Yep.
 
1 members found this post helpful.
Old 12-17-2022, 06:47 PM   #11
Markus Wiesner
Member
 
Registered: Mar 2016
Distribution: Slackware
Posts: 146

Rep: Reputation: 237Reputation: 237Reputation: 237
aaa_libraries currently does this in doinst.sh:

Code:
# Let's attempt to activate these libraries as they might be needed by various
# install scripts early on. We used to package symlinks in the normal way, and
# it's possible that would be fine too, but there must(?) have been a reason
# that we quit doing that...
cat var/lib/pkgtools/packages/aaa_libraries* 2> /dev/null | grep -e "^lib" -e "/lib" | grep -v "/$" | while read file ; do
  if [ -r "$file" ]; then
    ldconfig -l "$file" 1> /dev/null 2> /dev/null
  fi
done
Probably it would be safer NOT to use ldconfig -l and instead just update the whole directory with e.g.

Code:
cat var/lib/pkgtools/packages/aaa_libraries* 2> /dev/null | grep -e "^lib" -e "/lib" | grep "/$" | while read dir ; do
  if [ -d "$dir" ]; then
    ldconfig -n "$dir" 1> /dev/null 2> /dev/null
  fi
done
to prevent problems in case another future update misses updating a file? Or could that lead to other problems as it also updates links for libraries that are NOT part of aaa_libraries? ldconfig -n picks the higher version number when multiple libraries provide the same major version.

Quote:
We used to package symlinks in the normal way, and
it's possible that would be fine too, but there must(?) have been a reason
that we quit doing that...
Maybe this problem was the reason? But ldconfig -l does not solve it either as it also changes the symlink to the older version.
 
2 members found this post helpful.
Old 12-17-2022, 07:01 PM   #12
Aeterna
Senior Member
 
Registered: Aug 2017
Location: Terra Mater
Distribution: VM Host: Slackware-current, VM Guests: Artix, Venom, antiX, Gentoo, FreeBSD, OpenBSD, OpenIndiana
Posts: 1,008

Rep: Reputation: Disabled
Quote:
Originally Posted by LuckyCyborg View Post
In a single batch?
you are asking same question the second time:

Yes I applied update in a single batch. Files listed per @marav thread.
 
Old 12-17-2022, 07:04 PM   #13
LuckyCyborg
Senior Member
 
Registered: Mar 2010
Posts: 3,505

Original Poster
Rep: Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320
@Markus Wiesner

Excuse my ignorance, BUT from what I understand, a program linked against /lib64/liblzma.so.5.2.9 will find it even there /lib64/liblzma.so.5 symlink points to another library, right?

So, how about this logic: if there is a valid symlink and it points to a valid target (i.e. /lib64/liblzma.so.5.4.0 ), then do not touch it?

However, I do not know how could be calculated the symlink name in a Bash script...

Last edited by LuckyCyborg; 12-17-2022 at 07:09 PM.
 
Old 12-17-2022, 07:08 PM   #14
LuckyCyborg
Senior Member
 
Registered: Mar 2010
Posts: 3,505

Original Poster
Rep: Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320Reputation: 3320
Quote:
Originally Posted by Aeterna View Post
you are asking same question the second time:

Yes I applied update in a single batch. Files listed per @marav thread.
IF you have upgraded aaa_libraries after upgrading xz package, you should have ended with a broken xz tool - there is no other way around.

Last edited by LuckyCyborg; 12-17-2022 at 07:15 PM.
 
Old 12-17-2022, 07:46 PM   #15
garpu
Senior Member
 
Registered: Oct 2009
Distribution: Slackware
Posts: 1,538

Rep: Reputation: 899Reputation: 899Reputation: 899Reputation: 899Reputation: 899Reputation: 899Reputation: 899
If you're using slackpkg, then it should apply aaa_ and a libraries first, then itself, and all other updates.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] No problems here with the xorg Updates for Wed Dec 14 21:19:34 UTC 2022 kjhambrick Slackware 5 12-20-2022 04:35 PM
[SOLVED] KDE crashes when mounting USB drive, -current ( Sat Jul 17 17:55:10 UTC 2021) atelszewski Slackware 5 07-19-2021 02:25 AM
[SOLVED] Thu Feb 18 19:29:30 UTC 2021 and 20:47:35 UTC 2021: Strange ChangeLog? Thom1b Slackware 4 02-20-2021 01:55 AM
Sat Dec 24 02:36:05 UTC 2016 updates burdi01 Slackware 11 12-26-2016 09:53 AM
Smartd: Device /dev/sda: using '-d sat' for ATA disk behind SAT layer. deathsfriend99 Linux - Newbie 0 12-09-2009 12:47 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 07:02 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration