It seems to me that this is *still* an issue... No further development
upstream has been done to address this, afaict, so where does that leave us?
I repeat my offer to maintain subversion1.7
On Mon, Aug 5, 2013 at 8:15 AM, Jim Jagielski jim...@gmail.com wrote:
Look for posts regarding how
On Aug 19, 2013, at 7:42 AM, Jim Jagielski jim...@gmail.com wrote:
It seems to me that this is *still* an issue... No further development
upstream has been done to address this, afaict, so where does that leave us?
I repeat my offer to maintain subversion1.7
ok? so do it?
if you have
Here is the proposed subversion17 port (updated for svn 1.7.11)...
On Mon, Aug 19, 2013 at 7:42 AM, Jim Jagielski jim...@gmail.com wrote:
It seems to me that this is *still* an issue... No further development
upstream has been done to address this, afaict, so where does that leave us?
I
On Aug 19, 2013, at 4:40 PM, Jim Jagielski jim...@gmail.com wrote:
Here is the proposed subversion17 port (updated for svn 1.7.11)...
It makes no sense to implement this as a separate port. I am currently working
on moving the various Subversion bindings ports to be subports of the
subversion
On Aug 19, 2013, at 4:56 PM, Lawrence Velázquez lar...@macports.org wrote:
On Aug 19, 2013, at 4:40 PM, Jim Jagielski jim...@gmail.com wrote:
Here is the proposed subversion17 port (updated for svn 1.7.11)...
It makes no sense to implement this as a separate port.
except that I'm not going
On Mon, Aug 19, 2013 at 5:04 PM, Daniel J. Luke dl...@geeklair.net wrote:
As far as the port that was added to this thread, that's not a way to get
a port into macports.
Who said it was?
I've also mentioned (a few times), that this effort would likely be
better spent getting git-svn
On Aug 19, 2013, at 5:12 PM, Jim Jagielski jim...@gmail.com wrote:
On Mon, Aug 19, 2013 at 5:04 PM, Daniel J. Luke dl...@geeklair.net wrote:
As far as the port that was added to this thread, that's not a way to get a
port into macports.
Who said it was?
you attached it to your message
On Aug 19, 2013, at 5:19 PM, Daniel J. Luke dl...@geeklair.net wrote:
But in the meantime anyone who uses MacPorts and git-svn is screwed.
there's already a workaround (don't upgrade, or revert to svn 1.7)
Or, if you have it, use the Git provided with Xcode, which is admittedly older
but
If you'd like help, let me know. In the meantime, I'm simply not bothering
anymore.
On Mon, Aug 19, 2013 at 4:56 PM, Lawrence Velázquez lar...@macports.orgwrote:
On Aug 19, 2013, at 4:40 PM, Jim Jagielski jim...@gmail.com wrote:
Here is the proposed subversion17 port (updated for svn
On 2013-8-5 01:53 , Adam Mercer wrote:
On Sat, Aug 3, 2013 at 6:53 PM, Ryan Schmidt ryandes...@macports.org wrote:
It needn't be. If Subversion 1.7 doesn't have the problem, you can downgrade
back to that.
https://trac.macports.org/wiki/howto/InstallingOlderPort
I just find doing that a
Look for posts regarding how svn 1.8 has dropped neon and the phrase
'svn_delta already in use'
You'll find posts from the svn team saying that its a git problem and the
git team saying svn has changed the API, etc...
On Sun, Aug 4, 2013 at 10:36 PM, Lawrence Velázquez lar...@macports.orgwrote:
On Sat, Aug 3, 2013 at 6:53 PM, Ryan Schmidt ryandes...@macports.org wrote:
It needn't be. If Subversion 1.7 doesn't have the problem, you can downgrade
back to that.
https://trac.macports.org/wiki/howto/InstallingOlderPort
I just find doing that a pain, even though at the end of the day
On Aug 4, 2013, at 08:59, Jim Jagielski wrote:
You need to downgrade to subversion 1.7 and force git-core to not require
the latest.
If you leave 1.8.1 installed but activate 1.7.x, then MacPorts will not try to
re-activate 1.8.1 automatically when you install git-core or other ports that
On Aug 2, 2013, at 10:04 AM, Jim Jagielski jim...@gmail.com wrote:
Looking over some of the threads related to this on the git and svn lists,
I don't think so :)
Could you point us to some of these threads? I'm trying to find them, with
little success. It's entirely possible that I'm just
Yeppers.
--
Jim Jagielski
Brief? Mobile
On Aug 2, 2013, at 10:30 PM, Adam Mercer ramer...@gmail.com wrote:
On Fri, Aug 2, 2013 at 8:40 AM, Jim Jagielski jim...@gmail.com wrote:
I'm thinking it makes sense to break out the subversion port to svn17 and
svn18, since git-svn only appears to
On Sat, Aug 3, 2013 at 9:50 AM, Jim Jagielski jim...@gmail.com wrote:
On Aug 2, 2013, at 10:30 PM, Adam Mercer ramer...@gmail.com wrote:
I'm assuming this unreliability with subversion-1.8 and git-svn is the
reason for this:
$ git svn clone -s -r9:HEAD
On Aug 3, 2013, at 16:20, Adam Mercer r...@macports.org wrote:
On Sat, Aug 3, 2013 at 9:50 AM, Jim Jagielski jim...@gmail.com wrote:
On Aug 2, 2013, at 10:30 PM, Adam Mercer ramer...@gmail.com wrote:
I'm assuming this unreliability with subversion-1.8 and git-svn is the
reason for this:
$
I'm thinking it makes sense to break out the subversion port to svn17 and
svn18, since git-svn only appears to work reliably with subversion 1.7. As
it is now, git-core +svn forces the use of svn 1.8.
Comments?
___
macports-dev mailing list
On Aug 2, 2013, at 9:40 AM, Jim Jagielski jim...@gmail.com wrote:
I'm thinking it makes sense to break out the subversion port to svn17 and
svn18, since git-svn only appears to work reliably with subversion 1.7.
might be easier to just help upstream fix git-svn?
As it is now, git-core +svn
I'll take it on, at least until git-svn no longer requires 1.7... Sound OK?
On Fri, Aug 2, 2013 at 10:01 AM, Daniel J. Luke dl...@geeklair.net wrote:
On Aug 2, 2013, at 9:40 AM, Jim Jagielski jim...@gmail.com wrote:
I'm thinking it makes sense to break out the subversion port to svn17
and
On Aug 2, 2013, at 10:03 AM, Jim Jagielski jim...@gmail.com wrote:
I'll take it on, at least until git-svn no longer requires 1.7... Sound OK?
have you checked with upstream about whatever the issue is? (do you have a link
to an upstream bug report on it?)
--
Daniel J. Luke
On Fri, Aug 2, 2013 at 10:01 AM, Daniel J. Luke dl...@geeklair.net wrote:
On Aug 2, 2013, at 9:40 AM, Jim Jagielski jim...@gmail.com wrote:
I'm thinking it makes sense to break out the subversion port to svn17
and svn18, since git-svn only appears to work reliably with subversion 1.7.
might
On Fri, Aug 2, 2013 at 8:40 AM, Jim Jagielski jim...@gmail.com wrote:
I'm thinking it makes sense to break out the subversion port to svn17 and
svn18, since git-svn only appears to work reliably with subversion 1.7. As
it is now, git-core +svn forces the use of svn 1.8.
I'm assuming this
23 matches
Mail list logo
