[boost] [svn] pre-commit hook/mime-type

0 views
Skip to first unread message

Tim Blechmann

unread,
Sep 17, 2013, 5:32:54 AM9/17/13
to bo...@lists.boost.org
hi all,

is it possible that the pre-commit hook had changed recently? not sure
if this was intended, but it currently breaks the use of git-svn, which
imo is a huge inconvenience:

--
tim@moka-mac:~/Documents/boost-trunk-git/boost$ git svn dcommit
Committing to https://svn.boost.org/svn/boost/trunk ...
A boost/sync/detail/generic/event_cv_emulation.hpp
A boost/sync/detail/windows/event.hpp
A boost/sync/event.hpp
A libs/sync/test/event_test.cpp

ERROR from SVN:
A repository hook failed: Commit blocked by pre-commit hook (exit code
1) with output:
/home/subversion/boost/hooks/check-mime-type.pl:

trunk/boost/sync/detail/generic/event_cv_emulation.hpp : svn:mime-type
is not set
trunk/boost/sync/detail/windows/event.hpp : svn:mime-type is not set
trunk/boost/sync/event.hpp : svn:mime-type is not set
trunk/libs/sync/test/event_test.cpp : svn:mime-type is not set



Every added file must have the svn:mime-type property set. In
addition text files must have the svn:eol-style property set.

For binary files try running
svn propset svn:mime-type application/octet-stream path/of/file

For text files try
svn propset svn:mime-type text/plain path/of/file
svn propset svn:eol-style native path/of/file

You may want to consider uncommenting the auto-props section
in your ~/.subversion/config file. Read the Subversion book
(http://svnbook.red-bean.com/), Chapter 7, Properties section,
Automatic Property Setting subsection for more help. Also,
see http://svn.boost.org/trac/boost/wiki/BoostSubversion

W: b7ab541813d43b7d74b44f57eb04c2625ce305a7 and refs/remotes/git-svn
differ, using rebase:
:040000 040000 4b2ab78eaa8f1e5fa80761a327da5066ca15d465
73aa096ac4b16618132d6d012e964b1790542c8f M boost
:040000 040000 6146f06c45f590b38f76d123656cea13f24471d1
7a95e843ffc2f67fff874b6bd6c142b040423414 M libs
Current branch master is up to date.
ERROR: Not all changes have been committed into SVN, however the committed
ones (if any) seem to be successfully integrated into the working tree.
Please see the above messages for details.
--

this used to work fine just a few days ago. was this done intentionally?
if so, an announcement on the list with a comment on the implications
for the git-svn users would have been good to see.

best,
tim

signature.asc

Andrey Semashev

unread,
Sep 17, 2013, 5:42:59 AM9/17/13
to bo...@lists.boost.org
On Tue, Sep 17, 2013 at 1:32 PM, Tim Blechmann <t...@klingt.org> wrote:

> hi all,
>
> is it possible that the pre-commit hook had changed recently? not sure
> if this was intended, but it currently breaks the use of git-svn, which
> imo is a huge inconvenience:
>
> trunk/boost/sync/detail/generic/event_cv_emulation.hpp : svn:mime-type
> is not set
> trunk/boost/sync/detail/windows/event.hpp : svn:mime-type is not set
> trunk/boost/sync/event.hpp : svn:mime-type is not set
> trunk/libs/sync/test/event_test.cpp : svn:mime-type is not set
>
> this used to work fine just a few days ago. was this done intentionally?
> if so, an announcement on the list with a comment on the implications
> for the git-svn users would have been good to see.
>

AFAIR, svn:mime-type has always been a requirement. I use svn directly, and
it didn't add new files until I configured autoprops. Not sure how to do
this with git-svn (maybe there is a way to set mime type in git?).

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

Jürgen Hunold

unread,
Sep 17, 2013, 5:47:02 AM9/17/13
to bo...@lists.boost.org
Hi!

On Tuesday, 17. September 2013 13:42:59 Andrey Semashev wrote:
> > trunk/libs/sync/test/event_test.cpp : svn:mime-type is not set
> >
> > this used to work fine just a few days ago. was this done intentionally?
> > if so, an announcement on the list with a comment on the implications
> > for the git-svn users would have been good to see.
>
> AFAIR, svn:mime-type has always been a requirement. I use svn directly, and
> it didn't add new files until I configured autoprops. Not sure how to do
> this with git-svn (maybe there is a way to set mime type in git?).

git-svn just runs "svn add" under the hood. So the easiest way is just to set
up svn autoprops as you would for plain svn use. This is how I use git-svn.

Yours,

Jürgen
--
* Dipl.-Math. Jürgen Hunold !
* voice: ++49 4257 300 ! Fährstraße 1
* fax : ++49 4257 300 ! 31609 Balge/Sebbenhausen
* jhu...@gmx.eu ! Germany

Tim Blechmann

unread,
Sep 17, 2013, 6:04:33 AM9/17/13
to bo...@lists.boost.org
>>> trunk/libs/sync/test/event_test.cpp : svn:mime-type is not set
>>>
>>> this used to work fine just a few days ago. was this done intentionally?
>>> if so, an announcement on the list with a comment on the implications
>>> for the git-svn users would have been good to see.
>>
>> AFAIR, svn:mime-type has always been a requirement. I use svn directly, and
>> it didn't add new files until I configured autoprops. Not sure how to do
>> this with git-svn (maybe there is a way to set mime type in git?).
>
> git-svn just runs "svn add" under the hood. So the easiest way is just to set
> up svn autoprops as you would for plain svn use. This is how I use git-svn.

funny, works fine when running this from my linux workstation. whatever,
i just hope that the git migration will happen soon!

tim

signature.asc

Andrey Semashev

unread,
Sep 17, 2013, 6:08:19 AM9/17/13
to bo...@lists.boost.org
Here is how to setup autoprops:

https://svn.boost.org/trac/boost/wiki/BoostSubversion

See the MIME types section.
Reply all
Reply to author
Forward
0 new messages