Opened 12 years ago

Closed 7 years ago

#38354 closed defect (worksforme)

Install latest kmymoney4

Reported by: renang010@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: guide Version: 2.1.3
Keywords: Cc:
Port:

Description (last modified by larryv (Lawrence Velázquez))

Hi,
I want to install the latest kmymoney4 from the subversion repository.

I started a clean macports installation doing this:

1) Check out MacPorts source

%% mkdir -p /opt/mports
%% cd /opt/mports
%% svn checkout https://svn.macports.org/repository/macports/trunk

2) Build and Install MacPorts

%% cd /opt/mports/trunk/base
%% ./configure --enable-readline
%% make
%% sudo make install
%% make distclean

3) Configure MacPorts to use port information from Subversion

Open /opt/local/etc/macports/sources.conf in a text editor.
Change the last line from:

rsync://rsync.macports.org/release/tarballs/ports.tar [default]

to:

file:///opt/mports/trunk/dports [default]

4) Set the path

export PATH=/opt/local/bin:/opt/local/sbin:$PATH

Up to here, everything went fine.

Now my problems began. I firstly tried:

sudo port install kmymoney4

and got:

Error: Port kmymoney4 not found

So I thought I should do a selfupdate:

sudo port selfupdate

and got:

--->  Updating MacPorts base sources using rsync
MacPorts base version 2.1.99 installed,
MacPorts base version 2.1.3 downloaded.
--->  Updating the ports tree
Error: Synchronization of the local ports tree failed doing an svn update
Error: /opt/local/bin/port: port selfupdate failed: Couldn't sync the ports tree: Synchronization of 1 source(s) failed

Can someone help me?

Renan

Change History (7)

comment:1 Changed 12 years ago by larryv (Lawrence Velázquez)

Component: guidebase
Description: modified (diff)
Resolution: invalid
Status: newclosed
Type: requestdefect

This is not a bug; it’s a support issue. Please post a message to the macports-users mailing list. (Although I suspect I know what the issue is.)

comment:2 Changed 12 years ago by larryv (Lawrence Velázquez)

Component: baseguide
Resolution: invalid
Status: closedreopened

Actually, I do suppose this could be considered a problem with the guide.

Can you attach the output of "port -d sync"?

comment:3 Changed 12 years ago by renang010@…

macmini:mports Renan$ sudo port -d sync
DEBUG: Copying /Users/Renan/Library/Preferences/com.apple.dt.Xcode.plist to /opt/local/var/macports/home/Library/Preferences
--->  Updating the ports tree
Synchronizing local ports tree from file:///opt/mports/trunk/dports
DEBUG: /usr/bin/svn update --non-interactive /opt/mports/trunk/dports
DEBUG: changing euid/egid - current euid: 0 - current egid: 0
svn: OPTIONS of 'https://svn.macports.org/repository/macports/trunk': Server certificate verification failed: issuer is not trusted (https://svn.macports.org)
Command failed: /usr/bin/svn update --non-interactive /opt/mports/trunk/dports
Exit code: 1
DEBUG: command execution failed
    while executing
"system $svn_commandline"

Error: Synchronization of the local ports tree failed doing an svn update
DEBUG: Synchronization of 1 source(s) failed
    while executing
"mportsync [array get global_options]"
port sync failed: Synchronization of 1 source(s) failed
Last edited 11 years ago by ryandesign (Ryan Carsten Schmidt) (previous) (diff)

comment:4 Changed 12 years ago by larryv (Lawrence Velázquez)

The system Subversion often has issues recognizing the validity of our certificates. By which I mean, it usually doesn’t.

Try switching back to rsync, doing a selfupdate, and installing MacPorts' Subversion (sudo port install subversion). Then you can switch back to using a Subversion port tree, since MacPorts' Subversion has no problems accepting our certificate.

comment:5 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

Is this still an issue?

comment:6 Changed 10 years ago by mf2k (Frank Schima)

Owner: changed from markd@… to macports-tickets@…
Status: reopenednew

markd has retired. See #44782.

comment:7 Changed 7 years ago by raimue (Rainer Müller)

Resolution: worksforme
Status: newclosed

Not a bug.

Note: See TracTickets for help on using tickets.