On May 14, 2020, at 09:42, Kraus, Nicholas> wrote:
> Installing the SoapySDR port (with +python37, version 0.7.2_0) does not
> actually install the python bindings. Running ‘import SoapySDR’ in python
> (version 3.7.7) raises a ModuleNotFoundError.
>
> No python files are found within the po
Installing the SoapySDR port (with +python37, version 0.7.2_0) does not
actually install the python bindings. Running ‘import SoapySDR’ in python
(version 3.7.7) raises a ModuleNotFoundError.
No python files are found within the port contents for SoapySDR. Unfortunately
the SoapySDR port doesn’
On Oct 15, 2018, at 20:48, M P wrote:
> Do you think cleaning up directories like below will help?
>
> $ sudo port -fp uninstall installed
> followed by
> $ sudo rm -rf \
> /opt/local \
> /Applications/DarwinPorts \
> /Applications/MacPorts \
> /Library/LaunchDaemo
Do you think cleaning up directories like below will help?
$ *sudo port -fp uninstall installed*
followed by
$ *sudo rm -rf \
/opt/local \
/Applications/DarwinPorts \
/Applications/MacPorts \
/Library/LaunchDaemons/org.macports.* \
/Library/Receipts/Darwin
On Oct 14, 2018, at 12:09, M P wrote:
> Yes, I did
> sudo tar xvf
> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports.tar
>
> in
> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/tmp
>
> and went fine
>
> the listing is attache
Yes, I did
sudo tar xvf /opt/local/var/macports/sources/
rsync.macports.org/macports/release/tarballs/ports.tar
in
/opt/local/var/macports/sources/
rsync.macports.org/macports/release/tarballs/tmp
and went fine
the listing is attached
but still
sudo port install nco
Error: Port nco not fo
On Oct 13, 2018, at 19:50, M P wrote:
> On Thu, Oct 11, 2018 at 11:23 PM Ryan Schmidt wrote:
>> Ok, so it's the extraction of the tarball that's failing.
> Yes, all is as expected.
Are you able to extract the tarball manually? For example...
cd /tmp
/usr/bin/tar xf
/opt/local/var/macports/s
Yes, all is as expected.
%dscl . read /Users/macports NFSHomeDirectory
NFSHomeDirectory: /opt/local/var/macports/home
% ls -ld /opt/local/var/macports/home
drwxr-xr-x 3 root wheel 96 Aug 24 2017 /opt/local/var/macports/home
%ls -ld /private/var/tmp /private/tmp
drwxrwxrwt 37 root wheel 11
Ok, so it's the extraction of the tarball that's failing.
On Oct 11, 2018, at 19:57, M P wrote:
> The admin used CarbonCopy for backup. Any suggestions
Does the macports user exist and is its home directory set to the correct path?
It should be:
$ dscl . read /Users/macports NFSHomeDirectory
The admin used CarbonCopy for backup. Any suggestions
On Tue, Oct 9, 2018 at 7:11 PM M P wrote:
> Listing of directory
> /opt/local/var/macports/sources/
> rsync.macports.org/macports/release/tarballs^%
> is
>
> drwxr-xr-x 29 messagebus 505 928 Oct 3 02:32 base/
>
> -rw-r--r-- 1 roo
Listing of directory
/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs
^%
is
drwxr-xr-x 29 messagebus 505 928 Oct 3 02:32 base/
-rw-r--r-- 1 rootwheel 85608960 Oct 3 02:43 base.tar
-rw-r--r-- 1 rootwheel 512 Oct 3 02:43 base.tar.
On Oct 8, 2018, at 22:50, M P wrote:
> DEBUG: successful verification with key
> /opt/local/share/macports/macports-pubkey.pem
> DEBUG: system: /usr/bin/tar -C
> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/tmp
> -xf
> /opt/local/var/macports/sources/rsync.ma
Hi,
As Ryan has been alluding to, something is not right with your
installation, and its very hard to work out what from the information
you are providing.
You say your OS has effectively been updated. Have you followed the
migration instructions
https://trac.macports.org/wiki/Migration
t
Ryan Schmidt wrote:
> Your output still does not show the portindex being fetched or generated, and
> I don't know why that would happen. In fact selfupdate appears to be exiting
> entirely, before printing the output that should always be printed at the
> end, as I showed before:
That may be <
No, I have not customized sources.conf
This is a mac after a major repair with replaced motherboard. My admin made
a backup copy on HD and reinstalled most back from Sierra to Mojave.
Macports worked fine before when I installed back in 2017. There are a few
other ports that don't install e.g.
%su
On Oct 8, 2018, at 21:26, M P wrote:
> On Mon, Oct 8, 2018 at 8:24 PM M P wrote:
>
>> I removed
>> /opt/local/var/macports/sources/rsync.macports.org
>>
>> Then still a problem with nco port:
>>
>> %sudo port -v selfupdate
>> ---> Updating MacPorts base sources using rsync
>>
>> Willkomm
Maybe the mirror does not have this port?
%port search nco
Warning: Can't open index file for source: rsync://
rsync.macports.org/macports/release/tarballs/ports.tar
Error: search for name nco failed: No index(es) found! Have you synced your
port definitions? Try running 'port selfupdate'.
On M
I removed
/opt/local/var/macports/sources/rsync.macports.org
Then still a problem with nco port:
%sudo port -v selfupdate
---> Updating MacPorts base sources using rsync
Willkommen auf dem RSYNC-server auf ftp.fau.de.
Nicht all unsere Mirror sind per rsync verfuegbar.
Welcome to the RSYNC
On Oct 8, 2018, at 19:50, M P wrote:
>
> This is what happens when I issue
> %portindex
> Creating port index in ~/ports
>
> Total number of ports parsed: 0
> Ports successfully parsed:0
> Ports failed: 0
> Up-to-date ports skipped: 0
>
> also
>
> %port version
>
Don't forget to Reply All so that the conversation stays on the mailing list.
On Oct 8, 2018, at 19:12, M P wrote:
> On Mon, Oct 8, 2018 at 4:19 PM Ryan Schmidt wrote:
>
>> On Oct 8, 2018, at 07:19, M P wrote:
>>
>> > Hello,
>> > There is a port "nco" listed as available but its installation f
This is what happens when I issue
%portindex
Creating port index in ~/ports
Total number of ports parsed: 0
Ports successfully parsed: 0
Ports failed: 0
Up-to-date ports skipped: 0
also
%port version
Version: 2.5.4
%which port
/opt/local/bin/port
On Mon, Oct 8, 2018 at 6:12 PM M P
On Oct 8, 2018, at 07:19, M P wrote:
> Hello,
> There is a port "nco" listed as available but its installation fails under
> Mojave 10.14
> with
>
> sudo port install nco
> Error: Port nco not found
>
> What is the reason?
Sounds like a problem with your port index. Try running
sudo port -
Something about your setup may be broken; it installed fine for me (yes, that's
on Mojave):
bigapple:~ root# port install nco
---> Computing dependencies for nco
The following dependencies will be installed:
antlr
cunit
netcdf
udunits2
xercesc3
Continue? [Y/n]: y
---> Fetching archive for
Hello,
There is a port "nco" listed as available but its installation fails under
Mojave 10.14
with
sudo port install nco
Error: Port nco not found
What is the reason?
Thanks
24 matches
Mail list logo
