Website updates with binary files (like pdf) via git ?

[Derek Atkins]

Following up, I just noticed that there are three items in the
gnucash-changes moderation queue:

From: gjanssens at code.gnucash.org on Mon Nov 19 08:40:28 2012
Subject: r22571 - htdocs/trunk/docs/v2.4 - Add documentation version 2.4.2
to the
GnuCash website
Cause: Message body is too big: 46985720 bytes with a limit of 10240 KB

From: gjanssens at code.gnucash.org on Tue Nov 20 06:41:48 2012
Subject: r22577 - htdocs/trunk/docs/v2.4/ja_JP - Add most recent version
of the
Japanese guide
Cause: Message body is too big: 14121358 bytes with a limit of 10240 KB

From: gjanssens at code.gnucash.org on Sat Nov 24 12:56:27 2012
Subject: r22594 - htdocs/branches/beta - Synchronize beta with trunk
Cause: Message body is too big: 61701685 bytes with a limit of 10240 KB


I presume these are your missing messages?

-derek

On Sun, November 25, 2012 8:32 am, Derek Atkins wrote:
> Are the files marked as Binary Type in the svn repo?  How about in the git
> repo?  Also, how big was the PDF.  If the "patch" gets to be too big then
> it wont get sent out.
>
> Alas, I don't know what log to look at here.  When was this done?
>
> -derek
>
> On Sun, November 25, 2012 4:35 am, Geert Janssens wrote:
>> I have noticed something curious while updating the website the last few
>> days: whenever I attempt to
>>    git svn dcommit
>> a patch that contains some binary files, something seems to fail. I
>> don't think it happens for all binary file types. At first sight, I seem
>> to have issues with commits containing pdf files.
>>
>> First sign of something going wrong is that the git svn dcommit command
>> hangs on my system right after all changes are pushed, just before
>> normally the svn revision number would be printed.
>> The second clue is that no mail is sent from gnucash-changes for this
>> commit, only a mail from gnucash-patches.
>> Third hint is that the website doesn't get updated with these changes.
>>
>> Example commits that failed in this way are: r22571, r22577 and r22594.
>>
>> The subversion repository itself is updated though. I can check by
>> checking out the subversion site directly. It will contain the most
>> recent files.
>>
>> And all seems to be ok again once another patch is committed, but only
>> when done from outside of the git repo, like via subversion directly.
>> The git repo remains in an inconsistent state until that happened and I
>> can't get it fixed up unless another commit is added via another way.
>> Tried the usual git update, git svn rebase and even rm -fr .git/svn.
>>
>> Are there logs somewhere on the server that could contain some hint to
>> what happens here ?
>>
>> The first question would be: why is the gnucash-changes mail never sent
>> in these cases ?
>>
>> Geert
>> _______________________________________________
>> gnucash-devel mailing list
>> gnucash-devel at gnucash.org
>> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
>>
>
>
> --
>        Derek Atkins                 617-623-3745
>        derek at ihtfp.com             www.ihtfp.com
>        Computer and Internet Security Consultant
>
> _______________________________________________
> gnucash-devel mailing list
> gnucash-devel at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
>


-- 
       Derek Atkins                 617-623-3745
       derek at ihtfp.com             www.ihtfp.com
       Computer and Internet Security Consultant