You are not logged in.
Hi,
I fear I've messed something up by not fully understanding pacman and mixing core, testing, community-testing and extra packages.
I get this command now when I run the mpv command:
/usr/bin/mpv http://xpn2hi.streamguys.net/xpn2hi
/usr/bin/mpv: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /usr/lib/librubberband.so.2)
I can't even get the version of mpv at this point:
mpv --version
mpv: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /usr/lib/librubberband.so.2)
Here's my /etc/pacman.conf file without the remarked lines:
[options]
HoldPkg = pacman glibc
Architecture = auto
CheckSpace
SigLevel = Required DatabaseOptional DatabaseTrustAll
LocalFileSigLevel = Optional
[core]
Include = /etc/pacman.d/mirrorlist
[extra]
Include = /etc/pacman.d/mirrorlist
[testing]
Include = /etc/pacman.d/mirrorlist
[community-testing]
Include = /etc/pacman.d/mirrorlist
[community]
Include = /etc/pacman.d/mirrorlist
Here's my /etc/pacman.d/mirrorlist without the remarked lines:
Server = http://de.mirror.archlinux32.org/$arch/$repo/
Sorry if this is a painfully obvious mistake on my part, I suspect I just don't have my head wrapped around the pacman options when using testing and extra package repositories.
Last edited by Zohnsaxen (2021-05-30 19:48:46)
Offline
this most probably indicates, that we need to rebuild rubberband. I will schedule it.
Offline
I just did another system upgrade with "pacman -Syu" but still no luck on my machine abaumann. I didn't see an upgraded version of rubberband in the few packages that were updated this morning since yesterday so I'm guessing the rubberband rebuild hasn't happened just yet.
/usr/bin/mpv http://xpn2hi.streamguys.net/xpn2hi
/usr/bin/mpv: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /usr/lib/librubberband.so.2)
How can I tell which ?pool? (stable/testing/extra/etc..) my version of mpv is from?
Offline
I don't know if you can still tell which repo your packages came from once they've been downloaded. But hopefully it's still up on the server, especially since you last did an update recently, so you can just do '$ pacman -Ss ^mpv$'
Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.
Offline
Thanks levi. That worked and it looks like my mpv is from community.
pacman -Ss ^mpv$
community/mpv 1:0.33.1-2.0 [installed]
a free, open source, and cross-platform media player
Offline
To help diagnose this, what architecture is pacman deciding to download? Do, for example, 'pacman -Qi mpv|grep Architecture:' to find that out.
Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.
Offline
Looks like it's pentium4:
pacman -Qi mpv|grep Architecture
Architecture : pentium4
Offline
That suggests abumann's celebrations were premature then.
Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.
Offline
Sorry, but I don't have those problems neither on pentium4 stable nor testing.
My order in pacman.conf is:
#[testing]
#Include = /etc/pacman.d/mirrorlist[core]
Include = /etc/pacman.d/mirrorlist[extra]
Include = /etc/pacman.d/mirrorlist#[community-testing]
#Include = /etc/pacman.d/mirrorlist[community]
Include = /etc/pacman.d/mirrorlist
Testing should only be enabled if you want to test. Testing is not the "Debian Testing" where you can get newer
stable software. Testing can be quite broken in times.
My versions of the two packages are:
stable:
- mpv 1:0.33.1-2
- gcc-libs 10.2.0-6.1
testing:
mpv 1:0.33.1-2.0
gcc-libs 11.1.0-1.0
Offline
GLIBXX_3.4.29 fits to /usr/lib/libstdc++.so.6.0.29
(this is gcc-libs 11.1.0 from testing).
So this means that some package (mpv or one of it's libraries is built against a newer gcc-libs version).
But still, gcc-libs is usually backwards compatible, so even if you mix a newer version of gcc-libs with older
libraries this should not cause any problem.
It seems you have a newer version of mpv (1:0.33.1-2.0) and an older version of gcc-libs installed.
Can you check your version of gcc-libs?
If you have core before testing in /etc/pacman.conf, you are maybe installing the gcc-libs from core
and mixing it with mpv of testing (which doesn't work).
Offline
I also find mpv in community at version 1:0.33.1-2.0 in community, not community-testing. I think I'm using the agoctrl.org repo in France.
Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.
Offline
I didn't realize that testing wasn't like Debian's testing, so I've removed it from my /etc/pacman.conf file and matched the order to abaumann's pacman.conf. I then ran "pacman -Syu" and now I get this:
pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
:: Starting full system upgrade...
warning: broadcom-wl: local (6.30.223.271-299.0) is newer than community (6.30.223.271-288.0)
warning: rubberband: local (1.9.1-1.3) is newer than community (1.9.1-1.1)
there is nothing to do
Maybe my rubberband was pulled in from community-testing. Is there a way I can now force it to install the 1.9.1-1.1 version from community?
Sorry about all this, I suspect this will probably end up being my fault for mixing/enabling testing in my pacman.conf.
Last edited by Zohnsaxen (2021-05-30 18:33:21)
Offline
The only way to do that to my knowledge it to physically download 1.9.1-1.1 version from a repo such as https://mirror.archlinux32.org/pentium4/community/, then install it with 'pacman -U'
Architecture: pentium4, Testing repos: Yes, Hardware: EeePC 901+2GB RAM+OS half on the SD card.
Offline
Thanks levi. I did just that, downloaded rubberband-1.9.1-1.1-pentium4.pkg.tar.zst from my repo, and then installed it with "pacman -U rubberband-1.9.1-1.1-pentium4.pkg.tar.zst". The issue with mpv has been resolved and it is working fine again.
My apologies again for leading folks on the wild goose chase for an issue I created by mixing testing and non-testing. Hopefully someone else can learn from my error.
Thanks to everyone for your patience and assistance that ultimately lead me to the solution.
Offline
The only way to do that to my knowledge it to physically download 1.9.1-1.1 version from a repo such as https://mirror.archlinux32.org/pentium4/community/, then install it with 'pacman -U'
(just some minor comment on this)
This is exactly, what
-uu
is made for (second paragraph):
-u, --sysupgrade
Upgrades all packages that are out-of-date. Each
currently-installed package will be examined and upgraded if a
newer package exists. A report of all packages to upgrade will be
presented, and the operation will not proceed without user
confirmation. Dependencies are automatically resolved at this level
and will be installed/upgraded if necessary.
Pass this option twice to enable package downgrades; in this case,
pacman will select sync packages whose versions do not match with
the local versions. This can be useful when the user switches from
a testing repository to a stable one.
regards, deep42thought
Offline