Hello, I'm trying to ween mpd-portage's overlay off of it's custom subversion.eclass, one major issue I'm seeing right now is I keep getting the error when trying to emerge mpd-live with the portage subversion.eclass: !!! subversion.eclass: ESVN_REPO_URI and working copy's URL are not matched. !!! If you need support, post the topmost build error, and the call stack if relevant. I have tried removing the svn dir from distfiles, then reemergeing, but when I goto update, after initial checkin it fails. with the above error message. Any information would be useful, I will attach the mpd-live-0.1.ebuild. Thanks!
Created attachment 97720 [details] mpd-live-0.1.ebuild from mpd-portage overlay
Temporarily I have commented out this error from the eclass and put it into our overlay, this works like a charm, thanks.
(In reply to comment #2) > Temporarily I have commented out this error from the eclass and put it into our > overlay, this works like a charm, thanks. Which error? Can you attach the eclass diff?
I just worked around, as I said all I did was remove the error message I referenced in comment 1: --- /usr/portage/eclass/subversion.eclass 2006-09-06 08:35:52.000000000 -0700 +++ /usr/local/portage-overlays/mpd-portage/eclass/subversion.eclass 2006-09-21 19:33:57.193515248 -0700 @@ -185,11 +185,11 @@ ${ESVN_FETCH_CMD} ${ESVN_OPTIONS} "${repo_uri}" || die "${ESVN}: can't fetch from ${repo_uri}." else - subversion_wc_info || die "${ESVN}: unknown problem occurred while accessing working copy." +# subversion_wc_info || die "${ESVN}: unknown problem occurred while accessing working copy." - if [[ "${ESVN_WC_URL}" != "${ESVN_REPO_URI}" ]]; then - die "${ESVN}: ESVN_REPO_URI and working copy's URL are not matched." - fi +# if [[ "${ESVN_WC_URL}" != "${ESVN_REPO_URI}" ]]; then +# die "${ESVN}: ESVN_REPO_URI and working copy's URL are not matched." +# fi
Err, not in comment 1 it was in the original bug report: !!! subversion.eclass: ESVN_REPO_URI and working copy's URL are not matched. !!! If you need support, post the topmost build error, and the call stack if relevant.
Eh, TBH I don't think this is a bug...
I'm not sure it is 'a bug' myself, but I need more information here as to why it's happening with my subversion ebuilds, I'm not a fan of distributing my own eclass, the only difference I see between mine and others is that we're using https when getting from svn and this only started since this stuff was added to the eclass.
Fixed in CVS. Thank you for reporting.