Raspberry Ugrade to ARM Fedora 30

Dear All, to upgrade a Raspberry 3 I executed this commands

sudo dnf -y upgrade --refresh
sudo dnf -y install dnf-plugin-system-upgrade
sudo dnf -y system-upgrade download --releasever=30
sudo dnf -y system-upgrade reboot

after the reboot dnf fails. Is anyone else having the problem?

Thanks, Thomas

[pi@raspi ~]$ sudo dnf -y system-upgrade clean
[sudo] password for pi:
Traceback (most recent call last):
  File "/usr/lib64/python3.7/site-packages/libdnf/common_types.py", line
14, in swig_import_helper
    return importlib.import_module(mname)
  File "/usr/lib64/python3.7/importlib/__init__.py", line 127, in
import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
  File "<frozen importlib._bootstrap>", line 983, in _find_and_load
  File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 670, in _load_unlocked
  File "<frozen importlib._bootstrap>", line 583, in module_from_spec
  File "<frozen importlib._bootstrap_external>", line 1043, in create_module
  File "<frozen importlib._bootstrap>", line 219, in
_call_with_frames_removed
ImportError: /lib64/libstdc++.so.6: file too short

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/bin/dnf", line 57, in <module>
    from dnf.cli import main
  File "/usr/lib/python3.7/site-packages/dnf/__init__.py", line 30, in
<module>
    import dnf.base
  File "/usr/lib/python3.7/site-packages/dnf/base.py", line 29, in <module>
    import libdnf.transaction
  File "/usr/lib64/python3.7/site-packages/libdnf/__init__.py", line 3, in
<module>
    from . import common_types
  File "/usr/lib64/python3.7/site-packages/libdnf/common_types.py", line
17, in <module>
    _common_types = swig_import_helper()
  File "/usr/lib64/python3.7/site-packages/libdnf/common_types.py", line
16, in swig_import_helper
    return importlib.import_module('_common_types')
  File "/usr/lib64/python3.7/importlib/__init__.py", line 127, in
import_module
    return _bootstrap._gcd_import(name[level:], package, level)
ModuleNotFoundError: No module named '_common_types'

[Paul Whalen]

----- Original Message -----
> Dear All, to upgrade a Raspberry 3 I executed this commands
>
> sudo dnf -y upgrade --refresh
> sudo dnf -y install dnf-plugin-system-upgrade
> sudo dnf -y system-upgrade download --releasever=30
> sudo dnf -y system-upgrade reboot
>
> after the reboot dnf fails. Is anyone else having the problem?

What image and release are you upgrading from?
> Thanks, Thomas
>
> [pi@raspi ~]$ sudo dnf -y system-upgrade clean
> [sudo] password for pi:
> Traceback (most recent call last):
> File "/usr/lib64/python3.7/site-packages/libdnf/common_types.py", line 14, in
> swig_import_helper
> return importlib.import_module(mname)
> File "/usr/lib64/python3.7/importlib/__init__.py", line 127, in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
> File "<frozen importlib._bootstrap>", line 983, in _find_and_load
> File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
> File "<frozen importlib._bootstrap>", line 670, in _load_unlocked
> File "<frozen importlib._bootstrap>", line 583, in module_from_spec
> File "<frozen importlib._bootstrap_external>", line 1043, in create_module
> File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
> ImportError: /lib64/libstdc++.so.6: file too short
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
> File "/bin/dnf", line 57, in <module>
> from dnf.cli import main
> File "/usr/lib/python3.7/site-packages/dnf/__init__.py", line 30, in <module>
> import dnf.base
> File "/usr/lib/python3.7/site-packages/dnf/base.py", line 29, in <module>
> import libdnf.transaction
> File "/usr/lib64/python3.7/site-packages/libdnf/__init__.py", line 3, in
>
> <module>
> from . import common_types
> File "/usr/lib64/python3.7/site-packages/libdnf/common_types.py", line 17, in
> <module>
> _common_types = swig_import_helper()
> File "/usr/lib64/python3.7/site-packages/libdnf/common_types.py", line 16, in
> swig_import_helper
> return importlib.import_module('_common_types')
> File "/usr/lib64/python3.7/importlib/__init__.py", line 127, in import_module
> return _bootstrap._gcd_import(name[level:], package, level)
> ModuleNotFoundError: No module named '_common_types'
>
> arm mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]

[pi@raspi ~]$ lsb_release -d;uname -r
Description: Fedora release 29 (Twenty Nine)
5.0.9-200.fc29.aarch64

On Wed, May 1, 2019 at 6:03 PM Paul Whalen  wrote:
> ----- Original Message -----
> > Dear All, to upgrade a Raspberry 3 I executed this commands
> >
> > sudo dnf -y upgrade --refresh
> > sudo dnf -y install dnf-plugin-system-upgrade
> > sudo dnf -y system-upgrade download --releasever=30
> > sudo dnf -y system-upgrade reboot
> >
> > after the reboot dnf fails. Is anyone else having the problem?
>
> What image and release are you upgrading from?
> > Thanks, Thomas
> >
> > [pi@raspi ~]$ sudo dnf -y system-upgrade clean
> > [sudo] password for pi:
> > Traceback (most recent call last):
> > File "/usr/lib64/python3.7/site-packages/libdnf/common_types.py", line
>
> 14, in
> > swig_import_helper
> > return importlib.import_module(mname)
> > File "/usr/lib64/python3.7/importlib/__init__.py", line 127, in
>
> import_module
> > return _bootstrap._gcd_import(name[level:], package, level)
> > File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
> > File "<frozen importlib._bootstrap>", line 983, in _find_and_load
> > File "<frozen importlib._bootstrap>", line 967, in
>
> _find_and_load_unlocked
> > File "<frozen importlib._bootstrap>", line 670, in _load_unlocked
> > File "<frozen importlib._bootstrap>", line 583, in module_from_spec
> > File "<frozen importlib._bootstrap_external>", line 1043, in
>
> create_module
> > File "<frozen importlib._bootstrap>", line 219, in
>
> _call_with_frames_removed
> > ImportError: /lib64/libstdc++.so.6: file too short
> >
> > During handling of the above exception, another exception occurred:
> >
> > Traceback (most recent call last):
> > File "/bin/dnf", line 57, in <module>
> > from dnf.cli import main
> > File "/usr/lib/python3.7/site-packages/dnf/__init__.py", line 30, in
>
> <module>
> > import dnf.base
> > File "/usr/lib/python3.7/site-packages/dnf/base.py", line 29, in <module>
> > import libdnf.transaction
> > File "/usr/lib64/python3.7/site-packages/libdnf/__init__.py", line 3, in
> > <module>
> > from . import common_types
> > File "/usr/lib64/python3.7/site-packages/libdnf/common_types.py", line
> 17, in
> > <module>
> > _common_types = swig_import_helper()
> > File "/usr/lib64/python3.7/site-packages/libdnf/common_types.py", line
> 16, in
> > swig_import_helper
> > return importlib.import_module('_common_types')
> > File "/usr/lib64/python3.7/importlib/__init__.py", line 127, in
> import_module
> > return _bootstrap._gcd_import(name[level:], package, level)
> > ModuleNotFoundError: No module named '_common_types'
> >
> >
> > _______________________________________________
> > arm mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
> >
> https://lists.fedoraproject.org/archives/list/[e-mail]
> >

[Richard Ryniker]

> Dear All, to upgrade a Raspberry 3 I executed this commands
>
> sudo dnf -y upgrade --refresh
> sudo dnf -y install dnf-plugin-system-upgrade
> sudo dnf -y system-upgrade download --releasever=30
> sudo dnf -y system-upgrade reboot
>
> after the reboot dnf fails. Is anyone else having the problem?

I used the same commands to upgrade a Raspberry Pi 3 from F29 to F30, and
do not see your problem.  Dnf works as expected in F30 for "dnf
system-upgrade clean", "dnf list upgrades", and "dnf upgrade".

[Paul Whalen]

----- Original Message -----
> > Dear All, to upgrade a Raspberry 3 I executed this commands
> >
> > sudo dnf -y upgrade --refresh
> > sudo dnf -y install dnf-plugin-system-upgrade
> > sudo dnf -y system-upgrade download --releasever=30
> > sudo dnf -y system-upgrade reboot
> >
> > after the reboot dnf fails. Is anyone else having the problem?
>
> I used the same commands to upgrade a Raspberry Pi 3 from F29 to F30, and
> do not see your problem.  Dnf works as expected in F30 for "dnf
> system-upgrade clean", "dnf list upgrades", and "dnf upgrade".

I just did another upgrade on the rpi3 starting with the minimal f29 aarch64 
image and using the same commands. No issues here either.

What was the error you hit in dnf? Is there anything helpful in the logs?

Paul

Dear All,

I have now disabled any DNS resolver related services and was able to
reproduce your successful upgrades. However, I get

[pi@raspi ~]$ lsb_release -d;uname -r
Description: Fedora release 30 (Thirty)
5.0.10-200.fc29.aarch64

Should I wait until Fedora 30 is officially supported? Thanks, Thomas

On Wed, May 1, 2019 at 8:57 PM Paul Whalen  wrote:
> ----- Original Message -----
> > > Dear All, to upgrade a Raspberry 3 I executed this commands
> > >
> > > sudo dnf -y upgrade --refresh
> > > sudo dnf -y install dnf-plugin-system-upgrade
> > > sudo dnf -y system-upgrade download --releasever=30
> > > sudo dnf -y system-upgrade reboot
> > >
> > > after the reboot dnf fails. Is anyone else having the problem?
> >
> > I used the same commands to upgrade a Raspberry Pi 3 from F29 to F30, and
> > do not see your problem.  Dnf works as expected in F30 for "dnf
> > system-upgrade clean", "dnf list upgrades", and "dnf upgrade".
>
> I just did another upgrade on the rpi3 starting with the minimal f29
> aarch64
> image and using the same commands. No issues here either.
>
> What was the error you hit in dnf? Is there anything helpful in the logs?
>
> Paul

[Peter Robinson]

On Fri, May 3, 2019 at 7:04 PM  wrote:
> Dear All,
>
> I have now disabled any DNS resolver related services and was able to reproduce your successful upgrades. However, I get
>
> [pi@raspi ~]$ lsb_release -d;uname -r
> Description: Fedora release 30 (Thirty)
> 5.0.10-200.fc29.aarch64
>
> Should I wait until Fedora 30 is officially supported? Thanks, Thomas

What do you mean by "officially supported"? The release is now
generally available is that's what you mean
> On Wed, May 1, 2019 at 8:57 PM Paul Whalen  wrote:
> > ----- Original Message -----
> > > > Dear All, to upgrade a Raspberry 3 I executed this commands
> > > >
> > > > sudo dnf -y upgrade --refresh
> > > > sudo dnf -y install dnf-plugin-system-upgrade
> > > > sudo dnf -y system-upgrade download --releasever=30
> > > > sudo dnf -y system-upgrade reboot
> > > >
> > > > after the reboot dnf fails. Is anyone else having the problem?
> > >
> > > I used the same commands to upgrade a Raspberry Pi 3 from F29 to F30, and
> > > do not see your problem.  Dnf works as expected in F30 for "dnf
> > > system-upgrade clean", "dnf list upgrades", and "dnf upgrade".
> >
> > I just did another upgrade on the rpi3 starting with the minimal f29 aarch64
> > image and using the same commands. No issues here either.
> >
> > What was the error you hit in dnf? Is there anything helpful in the logs?
> >
> > Paul
>
> arm mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]

https://fedoraproject.org/wiki/Architectures/ARM/Raspberry_Pi#aarch64_suppor...
only
quotes Fedora 29.

Description: Fedora release 30 (Thirty)
in combination w/
5.0.10-200.fc29.aarch64

is the concern. Thanks.

On Fri, May 3, 2019 at 8:19 PM Peter Robinson  wrote:
> On Fri, May 3, 2019 at 7:04 PM  wrote:
> > Dear All,
> >
> > I have now disabled any DNS resolver related services and was able to
>
> reproduce your successful upgrades. However, I get
> > [pi@raspi ~]$ lsb_release -d;uname -r
> > Description: Fedora release 30 (Thirty)
> > 5.0.10-200.fc29.aarch64
> >
> > Should I wait until Fedora 30 is officially supported? Thanks, Thomas
>
> What do you mean by "officially supported"? The release is now
> generally available is that's what you mean
> > On Wed, May 1, 2019 at 8:57 PM Paul Whalen  wrote:
> > > ----- Original Message -----
> > > > > Dear All, to upgrade a Raspberry 3 I executed this commands
> > > > >
> > > > > sudo dnf -y upgrade --refresh
> > > > > sudo dnf -y install dnf-plugin-system-upgrade
> > > > > sudo dnf -y system-upgrade download --releasever=30
> > > > > sudo dnf -y system-upgrade reboot
> > > > >
> > > > > after the reboot dnf fails. Is anyone else having the problem?
> > > >
> > > > I used the same commands to upgrade a Raspberry Pi 3 from F29 to F30,
>
> and
> > > > do not see your problem.  Dnf works as expected in F30 for "dnf
> > > > system-upgrade clean", "dnf list upgrades", and "dnf upgrade".
> > >
> > > I just did another upgrade on the rpi3 starting with the minimal f29
>
> aarch64
> > > image and using the same commands. No issues here either.
> > >
> > > What was the error you hit in dnf? Is there anything helpful in the
>
> logs?
> > > Paul
> >
> > arm mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
>
> https://lists.fedoraproject.org/archives/list/[e-mail]

[Tom Callaway]

ImportError: /lib64/libstdc++.so.6: file too short

^^^ This is the core problem. Try downloading the libstdc++ package
manually and reinstalling it with rpm.

~tom

I tried this but too many dependencies, see below. Maybe that whole issue
is related to using the Pi3 as a DNS resolver at the same time when
upgrading although plain updating works very well. Can anyone point me to
the right log files to look at. journalctl is inconclusive (to me)?
Appreciate.

[pi@raspi]$ sudo rpm -Uvh libstdc++-9.0.1-0.10.fc30.i686.rpm
error: Failed dependencies:
ld-linux.so.2 is needed by libstdc++-9.0.1-0.10.fc30.i686
ld-linux.so.2(GLIBC_2.3) is needed by libstdc++-9.0.1-0.10.fc30.i686
libc.so.6 is needed by libstdc++-9.0.1-0.10.fc30.i686
libc.so.6(GLIBC_2.0) is needed by libstdc++-9.0.1-0.10.fc30.i686
libc.so.6(GLIBC_2.1) is needed by libstdc++-9.0.1-0.10.fc30.i686
libc.so.6(GLIBC_2.1.3) is needed by libstdc++-9.0.1-0.10.fc30.i686
libc.so.6(GLIBC_2.16) is needed by libstdc++-9.0.1-0.10.fc30.i686
libc.so.6(GLIBC_2.17) is needed by libstdc++-9.0.1-0.10.fc30.i686
libc.so.6(GLIBC_2.18) is needed by libstdc++-9.0.1-0.10.fc30.i686
libc.so.6(GLIBC_2.2) is needed by libstdc++-9.0.1-0.10.fc30.i686
libc.so.6(GLIBC_2.3) is needed by libstdc++-9.0.1-0.10.fc30.i686
libc.so.6(GLIBC_2.3.2) is needed by libstdc++-9.0.1-0.10.fc30.i686
libc.so.6(GLIBC_2.4) is needed by libstdc++-9.0.1-0.10.fc30.i686
libc.so.6(GLIBC_2.6) is needed by libstdc++-9.0.1-0.10.fc30.i686
libgcc_s.so.1 is needed by libstdc++-9.0.1-0.10.fc30.i686
libgcc_s.so.1(GCC_3.0) is needed by libstdc++-9.0.1-0.10.fc30.i686
libgcc_s.so.1(GCC_3.3) is needed by libstdc++-9.0.1-0.10.fc30.i686
libgcc_s.so.1(GCC_3.4) is needed by libstdc++-9.0.1-0.10.fc30.i686
libgcc_s.so.1(GCC_4.2.0) is needed by libstdc++-9.0.1-0.10.fc30.i686
libgcc_s.so.1(GLIBC_2.0) is needed by libstdc++-9.0.1-0.10.fc30.i686
libm.so.6 is needed by libstdc++-9.0.1-0.10.fc30.i686
libm.so.6(GLIBC_2.0) is needed by libstdc++-9.0.1-0.10.fc30.i686

On Wed, May 1, 2019 at 9:04 PM Tom Callaway  wrote:
> ImportError: /lib64/libstdc++.so.6: file too short
>
> ^^^ This is the core problem. Try downloading the libstdc++ package
> manually and reinstalling it with rpm.
>
> ~tom

[Pavel Holica]

You should download aarch64 one and the same version as the rpm -q
libstdc++ tells. The correct rpm should have the dependencies resolved.
It seem the library file is corrupted. To see all the corrupted files you
can also run rpm -Va (or just rpm -V package_name) to see if this is only
isolated issue or if it's system wide.

st 1. 5. 2019 v 22:20 odesílatel  napsal:
> I tried this but too many dependencies, see below. Maybe that whole issue
> is related to using the Pi3 as a DNS resolver at the same time when
> upgrading although plain updating works very well. Can anyone point me to
> the right log files to look at. journalctl is inconclusive (to me)?
> Appreciate.
>
> [pi@raspi]$ sudo rpm -Uvh libstdc++-9.0.1-0.10.fc30.i686.rpm
> error: Failed dependencies:
> ld-linux.so.2 is needed by libstdc++-9.0.1-0.10.fc30.i686
> ld-linux.so.2(GLIBC_2.3) is needed by libstdc++-9.0.1-0.10.fc30.i686
> libc.so.6 is needed by libstdc++-9.0.1-0.10.fc30.i686
> libc.so.6(GLIBC_2.0) is needed by libstdc++-9.0.1-0.10.fc30.i686
> libc.so.6(GLIBC_2.1) is needed by libstdc++-9.0.1-0.10.fc30.i686
> libc.so.6(GLIBC_2.1.3) is needed by libstdc++-9.0.1-0.10.fc30.i686
> libc.so.6(GLIBC_2.16) is needed by libstdc++-9.0.1-0.10.fc30.i686
> libc.so.6(GLIBC_2.17) is needed by libstdc++-9.0.1-0.10.fc30.i686
> libc.so.6(GLIBC_2.18) is needed by libstdc++-9.0.1-0.10.fc30.i686
> libc.so.6(GLIBC_2.2) is needed by libstdc++-9.0.1-0.10.fc30.i686
> libc.so.6(GLIBC_2.3) is needed by libstdc++-9.0.1-0.10.fc30.i686
> libc.so.6(GLIBC_2.3.2) is needed by libstdc++-9.0.1-0.10.fc30.i686
> libc.so.6(GLIBC_2.4) is needed by libstdc++-9.0.1-0.10.fc30.i686
> libc.so.6(GLIBC_2.6) is needed by libstdc++-9.0.1-0.10.fc30.i686
> libgcc_s.so.1 is needed by libstdc++-9.0.1-0.10.fc30.i686
> libgcc_s.so.1(GCC_3.0) is needed by libstdc++-9.0.1-0.10.fc30.i686
> libgcc_s.so.1(GCC_3.3) is needed by libstdc++-9.0.1-0.10.fc30.i686
> libgcc_s.so.1(GCC_3.4) is needed by libstdc++-9.0.1-0.10.fc30.i686
> libgcc_s.so.1(GCC_4.2.0) is needed by libstdc++-9.0.1-0.10.fc30.i686
> libgcc_s.so.1(GLIBC_2.0) is needed by libstdc++-9.0.1-0.10.fc30.i686
> libm.so.6 is needed by libstdc++-9.0.1-0.10.fc30.i686
> libm.so.6(GLIBC_2.0) is needed by libstdc++-9.0.1-0.10.fc30.i686
>
> On Wed, May 1, 2019 at 9:04 PM Tom Callaway  wrote:
> > ImportError: /lib64/libstdc++.so.6: file too short
> >
> > ^^^ This is the core problem. Try downloading the libstdc++ package
> > manually and reinstalling it with rpm.
> >
> > ~tom
>
> arm mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]

Yep, it looks like the whole system is corrupted by probably breaking up
during the upgrade process when a problem occurs with DNS resolution I
suspect but please correct me, if I am wrong.

[pi@raspi]$  rpm -q libstdc++
libstdc++-8.3.1-2.fc29.aarch64
libstdc++-9.0.1-0.10.fc30.aarch64
[pi@raspi]$ sudo rpm -V libstdc++-9.0.1-0.10.fc30.i686.rpm
Unsatisfied dependencies for libstdc++-9.0.1-0.10.fc30.i686:
ld-linux.so.2 is needed by libstdc++-9.0.1-0.10.fc30.i686
ld-linux.so.2(GLIBC_2.3) is needed by libstdc++-9.0.1-0.10.fc30.i686
libc.so.6 is needed by libstdc++-9.0.1-0.10.fc30.i686
libc.so.6(GLIBC_2.0) is needed by libstdc++-9.0.1-0.10.fc30.i686
libc.so.6(GLIBC_2.1) is needed by libstdc++-9.0.1-0.10.fc30.i686
libc.so.6(GLIBC_2.1.3) is needed by libstdc++-9.0.1-0.10.fc30.i686
libc.so.6(GLIBC_2.16) is needed by libstdc++-9.0.1-0.10.fc30.i686
libc.so.6(GLIBC_2.17) is needed by libstdc++-9.0.1-0.10.fc30.i686
libc.so.6(GLIBC_2.18) is needed by libstdc++-9.0.1-0.10.fc30.i686
libc.so.6(GLIBC_2.2) is needed by libstdc++-9.0.1-0.10.fc30.i686
libc.so.6(GLIBC_2.3) is needed by libstdc++-9.0.1-0.10.fc30.i686
libc.so.6(GLIBC_2.3.2) is needed by libstdc++-9.0.1-0.10.fc30.i686
libc.so.6(GLIBC_2.4) is needed by libstdc++-9.0.1-0.10.fc30.i686
libc.so.6(GLIBC_2.6) is needed by libstdc++-9.0.1-0.10.fc30.i686
libgcc_s.so.1 is needed by libstdc++-9.0.1-0.10.fc30.i686
libgcc_s.so.1(GCC_3.0) is needed by libstdc++-9.0.1-0.10.fc30.i686
libgcc_s.so.1(GCC_3.3) is needed by libstdc++-9.0.1-0.10.fc30.i686
libgcc_s.so.1(GCC_3.4) is needed by libstdc++-9.0.1-0.10.fc30.i686
libgcc_s.so.1(GCC_4.2.0) is needed by libstdc++-9.0.1-0.10.fc30.i686
libgcc_s.so.1(GLIBC_2.0) is needed by libstdc++-9.0.1-0.10.fc30.i686
libm.so.6 is needed by libstdc++-9.0.1-0.10.fc30.i686
libm.so.6(GLIBC_2.0) is needed by libstdc++-9.0.1-0.10.fc30.i686
missing   a /usr/lib/.build-id/ba/a735e48f9645a7e5bef8b869cd9b61d81e894a
missing     /usr/lib/libstdc++.so.6
missing     /usr/lib/libstdc++.so.6.0.26
S.5......    /usr/share/gcc-9/python/libstdcxx/__init__.py
S.5....T.
/usr/share/gcc-9/python/libstdcxx/__pycache__/__init__.cpython-37.opt-1.pyc
S.5....T.
/usr/share/gcc-9/python/libstdcxx/__pycache__/__init__.cpython-37.pyc
S.5......    /usr/share/gcc-9/python/libstdcxx/v6/__init__.py
S.5....T.
/usr/share/gcc-9/python/libstdcxx/v6/__pycache__/__init__.cpython-37.opt-1.pyc
S.5....T.
/usr/share/gcc-9/python/libstdcxx/v6/__pycache__/__init__.cpython-37.pyc
S.5....T.
/usr/share/gcc-9/python/libstdcxx/v6/__pycache__/printers.cpython-37.opt-1.pyc
S.5....T.
/usr/share/gcc-9/python/libstdcxx/v6/__pycache__/printers.cpython-37.pyc
S.5....T.
/usr/share/gcc-9/python/libstdcxx/v6/__pycache__/xmethods.cpython-37.opt-1.pyc
S.5....T.
/usr/share/gcc-9/python/libstdcxx/v6/__pycache__/xmethods.cpython-37.pyc
S.5......    /usr/share/gcc-9/python/libstdcxx/v6/printers.py
S.5......    /usr/share/gcc-9/python/libstdcxx/v6/xmethods.py
missing     /usr/share/gdb/auto-load/usr/lib
missing     /usr/share/gdb/auto-load/usr/lib/__pycache__
missing
 /usr/share/gdb/auto-load/usr/lib/__pycache__/libstdc++.so.6.0.26-gdb.cpython-37.opt-1.pyc
missing
 /usr/share/gdb/auto-load/usr/lib/__pycache__/libstdc++.so.6.0.26-gdb.cpython-37.pyc
missing     /usr/share/gdb/auto-load/usr/lib/libstdc++.so.6.0.26-gdb.py

On Wed, May 1, 2019 at 10:24 PM Pavel Holica  wrote:
> You should download aarch64 one and the same version as the rpm -q
> libstdc++ tells. The correct rpm should have the dependencies resolved.
> It seem the library file is corrupted. To see all the corrupted files you
> can also run rpm -Va (or just rpm -V package_name) to see if this is only
> isolated issue or if it's system wide.
>
> st 1. 5. 2019 v 22:20 odesílatel  napsal:
> > I tried this but too many dependencies, see below. Maybe that whole issue
> > is related to using the Pi3 as a DNS resolver at the same time when
> > upgrading although plain updating works very well. Can anyone point me to
> > the right log files to look at. journalctl is inconclusive (to me)?
> > Appreciate.
> >
> > [pi@raspi]$ sudo rpm -Uvh libstdc++-9.0.1-0.10.fc30.i686.rpm
> > error: Failed dependencies:
> > ld-linux.so.2 is needed by libstdc++-9.0.1-0.10.fc30.i686
> > ld-linux.so.2(GLIBC_2.3) is needed by libstdc++-9.0.1-0.10.fc30.i686
> > libc.so.6 is needed by libstdc++-9.0.1-0.10.fc30.i686
> > libc.so.6(GLIBC_2.0) is needed by libstdc++-9.0.1-0.10.fc30.i686
> > libc.so.6(GLIBC_2.1) is needed by libstdc++-9.0.1-0.10.fc30.i686
> > libc.so.6(GLIBC_2.1.3) is needed by libstdc++-9.0.1-0.10.fc30.i686
> > libc.so.6(GLIBC_2.16) is needed by libstdc++-9.0.1-0.10.fc30.i686
> > libc.so.6(GLIBC_2.17) is needed by libstdc++-9.0.1-0.10.fc30.i686
> > libc.so.6(GLIBC_2.18) is needed by libstdc++-9.0.1-0.10.fc30.i686
> > libc.so.6(GLIBC_2.2) is needed by libstdc++-9.0.1-0.10.fc30.i686
> > libc.so.6(GLIBC_2.3) is needed by libstdc++-9.0.1-0.10.fc30.i686
> > libc.so.6(GLIBC_2.3.2) is needed by libstdc++-9.0.1-0.10.fc30.i686
> > libc.so.6(GLIBC_2.4) is needed by libstdc++-9.0.1-0.10.fc30.i686
> > libc.so.6(GLIBC_2.6) is needed by libstdc++-9.0.1-0.10.fc30.i686
> > libgcc_s.so.1 is needed by libstdc++-9.0.1-0.10.fc30.i686
> > libgcc_s.so.1(GCC_3.0) is needed by libstdc++-9.0.1-0.10.fc30.i686
> > libgcc_s.so.1(GCC_3.3) is needed by libstdc++-9.0.1-0.10.fc30.i686
> > libgcc_s.so.1(GCC_3.4) is needed by libstdc++-9.0.1-0.10.fc30.i686
> > libgcc_s.so.1(GCC_4.2.0) is needed by libstdc++-9.0.1-0.10.fc30.i686
> > libgcc_s.so.1(GLIBC_2.0) is needed by libstdc++-9.0.1-0.10.fc30.i686
> > libm.so.6 is needed by libstdc++-9.0.1-0.10.fc30.i686
> > libm.so.6(GLIBC_2.0) is needed by libstdc++-9.0.1-0.10.fc30.i686
> >
> > On Wed, May 1, 2019 at 9:04 PM Tom Callaway  wrote:
> > > ImportError: /lib64/libstdc++.so.6: file too short
> > >
> > > ^^^ This is the core problem. Try downloading the libstdc++ package
> > > manually and reinstalling it with rpm.
> > >
> > > ~tom
> >
> > arm mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
> > https://lists.fedoraproject.org/archives/list/[e-mail]
>
> --
> Pavel Holica

[David]

Why is everyone trying to upgrade?  Why not just install aarach version 30:
https://dl.fedoraproject.org/pub/fedora-secondary/releases/30/Workstation/aa...
?

David Nowak

On Wed, May 1, 2019 at 8:54 AM  wrote:
> Dear All, to upgrade a Raspberry 3 I executed this commands
>
> sudo dnf -y upgrade --refresh
> sudo dnf -y install dnf-plugin-system-upgrade
> sudo dnf -y system-upgrade download --releasever=30
> sudo dnf -y system-upgrade reboot
>
> after the reboot dnf fails. Is anyone else having the problem?
>
> Thanks, Thomas
>
> [pi@raspi ~]$ sudo dnf -y system-upgrade clean
> [sudo] password for pi:
> Traceback (most recent call last):
>   File "/usr/lib64/python3.7/site-packages/libdnf/common_types.py", line
> 14, in swig_import_helper
>     return importlib.import_module(mname)
>   File "/usr/lib64/python3.7/importlib/__init__.py", line 127, in
> import_module
>     return _bootstrap._gcd_import(name[level:], package, level)
>   File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
>   File "<frozen importlib._bootstrap>", line 983, in _find_and_load
>   File "<frozen importlib._bootstrap>", line 967, in
> _find_and_load_unlocked
>   File "<frozen importlib._bootstrap>", line 670, in _load_unlocked
>   File "<frozen importlib._bootstrap>", line 583, in module_from_spec
>   File "<frozen importlib._bootstrap_external>", line 1043, in
> create_module
>   File "<frozen importlib._bootstrap>", line 219, in
> _call_with_frames_removed
> ImportError: /lib64/libstdc++.so.6: file too short
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
>   File "/bin/dnf", line 57, in <module>
>     from dnf.cli import main
>   File "/usr/lib/python3.7/site-packages/dnf/__init__.py", line 30, in
>
> <module>
>     import dnf.base
>   File "/usr/lib/python3.7/site-packages/dnf/base.py", line 29, in <module>
>     import libdnf.transaction
>   File "/usr/lib64/python3.7/site-packages/libdnf/__init__.py", line 3, in
> <module>
>     from . import common_types
>   File "/usr/lib64/python3.7/site-packages/libdnf/common_types.py", line
> 17, in <module>
>     _common_types = swig_import_helper()
>   File "/usr/lib64/python3.7/site-packages/libdnf/common_types.py", line
> 16, in swig_import_helper
>     return importlib.import_module('_common_types')
>   File "/usr/lib64/python3.7/importlib/__init__.py", line 127, in
> import_module
>     return _bootstrap._gcd_import(name[level:], package, level)
> ModuleNotFoundError: No module named '_common_types'
>
> arm mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]

In my opinion, a rolling release is the preferred solution.

Thomas

On Sun, May 5, 2019 at 6:17 AM David  wrote:
> Why is everyone trying to upgrade?  Why not just install aarach version
> 30:
> https://dl.fedoraproject.org/pub/fedora-secondary/releases/30/Workstation/aa...
> ?
>
> David Nowak
>
> On Wed, May 1, 2019 at 8:54 AM  wrote:
> > Dear All, to upgrade a Raspberry 3 I executed this commands
> >
> > sudo dnf -y upgrade --refresh
> > sudo dnf -y install dnf-plugin-system-upgrade
> > sudo dnf -y system-upgrade download --releasever=30
> > sudo dnf -y system-upgrade reboot
> >
> > after the reboot dnf fails. Is anyone else having the problem?
> >
> > Thanks, Thomas
> >
> > [pi@raspi ~]$ sudo dnf -y system-upgrade clean
> > [sudo] password for pi:
> > Traceback (most recent call last):
> >   File "/usr/lib64/python3.7/site-packages/libdnf/common_types.py", line
> > 14, in swig_import_helper
> >     return importlib.import_module(mname)
> >   File "/usr/lib64/python3.7/importlib/__init__.py", line 127, in
> > import_module
> >     return _bootstrap._gcd_import(name[level:], package, level)
> >   File "<frozen importlib._bootstrap>", line 1006, in _gcd_import
> >   File "<frozen importlib._bootstrap>", line 983, in _find_and_load
> >   File "<frozen importlib._bootstrap>", line 967, in
> > _find_and_load_unlocked
> >   File "<frozen importlib._bootstrap>", line 670, in _load_unlocked
> >   File "<frozen importlib._bootstrap>", line 583, in module_from_spec
> >   File "<frozen importlib._bootstrap_external>", line 1043, in
> > create_module
> >   File "<frozen importlib._bootstrap>", line 219, in
> > _call_with_frames_removed
> > ImportError: /lib64/libstdc++.so.6: file too short
> >
> > During handling of the above exception, another exception occurred:
> >
> > Traceback (most recent call last):
> >   File "/bin/dnf", line 57, in <module>
> >     from dnf.cli import main
> >   File "/usr/lib/python3.7/site-packages/dnf/__init__.py", line 30, in
> >
> > <module>
> >     import dnf.base
> >   File "/usr/lib/python3.7/site-packages/dnf/base.py", line 29, in
> > <module>
> >     import libdnf.transaction
> >   File "/usr/lib64/python3.7/site-packages/libdnf/__init__.py", line 3,
> > in <module>
> >     from . import common_types
> >   File "/usr/lib64/python3.7/site-packages/libdnf/common_types.py", line
> > 17, in <module>
> >     _common_types = swig_import_helper()
> >   File "/usr/lib64/python3.7/site-packages/libdnf/common_types.py", line
> > 16, in swig_import_helper
> >     return importlib.import_module('_common_types')
> >   File "/usr/lib64/python3.7/importlib/__init__.py", line 127, in
> > import_module
> >     return _bootstrap._gcd_import(name[level:], package, level)
> > ModuleNotFoundError: No module named '_common_types'
> >
> > arm mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
> > https://lists.fedoraproject.org/archives/list/[e-mail]