#66772 closed defect (fixed)
NanoVNASaver @0.5.4 Failed to destroot
Reported by: | RafalLukawiecki (Rafal Lukawiecki) | Owned by: | ra1nb0w |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.8.0 |
Keywords: | Cc: | ||
Port: | NanoVNASaver |
Description
When installing or upgrading NanoVNASaver port, 0.5.4, the following error is reported:
---> Staging NanoVNASaver into destroot Error: Failed to destroot NanoVNASaver: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_NanoVNASaver/NanoVNASaver/main.log for details. Error: Follow https://guide.macports.org/#project.tickets if you believe there is a bug. Error: Processing of port NanoVNASaver failed
It seems from the log that CHANGELOG.md may be missing:
:info:destroot running install_data :info:destroot error: can't copy 'CHANGELOG.md': doesn't exist or not a regular file :info:destroot Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_NanoVNASaver/NanoVNASaver/work/nanovna-saver-0.5.4" && /opt/local/Library/Frameworks/Python.framework/Versions/3.10/bin/python3.10 setup.py --no-user-cfg install --prefix=/opt/local/Library/Frameworks/Python.framework/Versions/3.10 --root=/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_NanoVNASaver/NanoVNASaver/work/destroot :info:destroot Exit code: 1 :error:destroot Failed to destroot NanoVNASaver: command execution failed
Change History (4)
comment:1 Changed 22 months ago by jmroot (Joshua Root)
Owner: | set to ra1nb0w |
---|---|
Status: | new → assigned |
Summary: | Install fails with Failed to destroot NanoVNASaver → NanoVNASaver @0.5.4 Failed to destroot |
comment:2 Changed 22 months ago by Davide Gerhard <ra1nb0w@…>
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:3 Changed 22 months ago by RafalLukawiecki (Rafal Lukawiecki)
I can confirm that this has fixed the issue, using 0.5.4_1. Thank you for such a speedy response!
Note: See
TracTickets for help on using
tickets.
In 42a6946d3f9ec32159a66f4ca3995cf1629d46b1/macports-ports (master):