repo copy (svn cp) gives pre-commit "Do not replace a file. This will break the CVS exporter."

[Palle Girgensohn]

Ok, thanks. That is probably exactly what happened. I'll check it out tomorrow.

PostgreSQL 9.3 beta1 will be announced on Monday... :-)

11 maj 2013 kl. 16:54 skrev Chris Rees <crees at FreeBSD.org>:

> On 11 May 2013 15:29, Palle Girgensohn <girgen at pingpong.net> wrote:
>> Hi Chris,
>> 
>> I did
>> 
>> cd /usr/ports/databases
>> svn cp postgresql90-server postgresql93-server
>> 
>> and some then another set I'd similar copies. After that I modified the Makefiles and some other stuff. At commit it complained as per subject.
> 
> Yes, it looks as though you've replaced a file with svn cp somehow.
> Unfortunately this kind of thing is incredibly fiddly... and some bugs
> can present in the svn pre-commit checks that break it.
> 
> Your best bet is to do an old-fashioned svn cp postgresql90-server
> postgresql93-server, svn commit, then do the fiddling around with it
> all, as we used to in the cvs days.  (Don't add it to
> databases/Makefile until it's ready of course!)
> 
> If you run svn diff, you may even see which file you've "replaced".
> 
> Chris
> 
>> 11 maj 2013 kl. 15:36 skrev Chris Rees <crees at FreeBSD.org>:
>> 
>>> On 11 May 2013 14:24, Palle Girgensohn <girgen at freebsd.org> wrote:
>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>> Hash: SHA1
>>>> 
>>>> Hi,
>>>> 
>>>> I though I could just do my own repo copies not, using svn copy in the
>>>> ports tree. Is this just not allowed, due to the CVS exporter?
>>>> 
>>>> Will I still have to request a repo copy from portmgr@?
>>> 
>>> 
>>> Depends what you are repocopying from -> to.  If you are copying a
>>> file over an existing file, that is disallowed (though why, I'm not
>>> sure-- I think the exporter hooks were left enabled even though we
>>> don't export any more).
>>> 
>>> What are you trying to do?
>>> 
>>> Chris
>>