gt; On Sat, May 25, 2019 at 4:10 PM Dale Phurrough wrote:
>
>> Hi all. I think there is a missing patch file for GnuCash to compile on
>> Windows. The patch file referenced here doesn't exist in the GIT repo
>>
>> https://github.com/Gnucash/gnucash-on-windows/blob/c68c63
patch file referenced here doesn't exist in the GIT repo
>
> https://github.com/Gnucash/gnucash-on-windows/blob/c68c63a5e772330aa09dab98478b8125a9e71c57/gnucash.modules#L210
>
> Anyone have it? And can check it into the git repo?
>
> jhbuild complains...
> *** Error during
Hi all. I think there is a missing patch file for GnuCash to compile on
Windows. The patch file referenced here doesn't exist in the GIT repo
https://github.com/Gnucash/gnucash-on-windows/blob/c68c63a5e772330aa09dab98478b8125a9e71c57/gnucash.modules#L210
Anyone have it? And can check it int
39318a37791476ed52e2c20992623263f367c8c0
Author: Cristian Marchi
Date: Sun Jan 26 10:27:50 2014 +0100
Drop svn repo references in favour of git repo.
Summary of changes:
develdocs.phtml |8
externals/menu.phtml |4 ++--
2 files changed, 6 insertions(+), 6 deletions
2623263f367c8c0
> Author: Cristian Marchi
> Date: Sun Jan 26 10:27:50 2014 +0100
>
> Drop svn repo references in favour of git repo.
>
>
>
> Summary of changes:
> develdocs.phtml |8
> externals/menu.phtml |4
I have one local git repo with 2.4 and trunk branch in there. I regularly
switch the checkout between both branches, e.g. for back-porting commits and
such.
Recently it occurred to me that when doing something on the 2.4 branch and
then switching the working copy to trunk again, suddenly
On Nov 5, 2011, at 11:18 AM, Yawar Amin wrote:
> Hi Mike,
>
> On Thu, Nov 3, 2011 at 1:37 PM, Mike Evans wrote:
>
>> The commit message should be:
>>
>> Bug #457401 - Print invoice should not be disabled for unposted invoices
>> Enable printing of unposted invoices.
>>
>> I'm using git and fo
On Oct 31, 2011, at 5:59 AM, Geert Janssens wrote:
> Hi,
>
> Recently GnuCash 2.4.8 has been released. In svn this means a copy was made
> to
> the tags directory.
>
> I'm working with git for some time now based on John's excellent wiki
> description.
>
> However, in git I don't see the 2.
Hi,
Recently GnuCash 2.4.8 has been released. In svn this means a copy was made to
the tags directory.
I'm working with git for some time now based on John's excellent wiki
description.
However, in git I don't see the 2.4.8 tag, while the older ones are there. How
do I make git recognize the
On May 23, 2011, at 12:53 PM, Casey Cichon wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 5/23/2011 2:33 PM, Christian Stimming wrote:
>> Am Montag, 23. Mai 2011 schrieb Casey Cichon:
>>> Making all in glade
>>> make[4]: Entering directory `/home/casey/Downloads/gnucash/src/gn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 5/23/2011 2:33 PM, Christian Stimming wrote:
> Am Montag, 23. Mai 2011 schrieb Casey Cichon:
>> Making all in glade
>> make[4]: Entering directory `/home/casey/Downloads/gnucash/src/gnome/glade'
>> make[4]: *** No rule to make target `account.glad
Am Montag, 23. Mai 2011 schrieb Casey Cichon:
> Making all in glade
> make[4]: Entering directory `/home/casey/Downloads/gnucash/src/gnome/glade'
> make[4]: *** No rule to make target `account.glade', needed by
> `all-am'. Stop.
> make[4]: Leaving directory `/home/casey/Downloads/gnucash/src/gnome
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I am getting the following error while trying to compile trunk.
./src/core-utils/.libs/libgnc-core-utils.so
../../../src/gnc-module/.libs/libgnc-module.so
../../../src/libqof/qof/.libs/libgnc-qof.so /usr/lib/libglade-2.0.so
/usr/lib/libxml2.so /u
Am Samstag, 30. April 2011 schrieb John Ralls:
> > But at this point the "git-update" script results in the following error:
> >> You asked to pull from the remote 'origin', but did not specify
> >> a branch. Because this is not the default configured remote
> >> for your current branch, you must s
On Apr 29, 2011, at 12:35 PM, Christian Stimming wrote:
> Dear John,
>
> I'm trying to follow again the advice on
> http://wiki.gnucash.org/wiki/Git
> but I'm running into an error message that is not yet mentioned on that page.
> Here are the commands I'm running:
>
> git clone git://github.
Dear John,
I'm trying to follow again the advice on
http://wiki.gnucash.org/wiki/Git
but I'm running into an error message that is not yet mentioned on that page.
Here are the commands I'm running:
git clone git://github.com/Gnucash/gnucash.git gnucash-github.git
cd gnucash-github.git/
git
On Mar 12, 2011, at 10:11 AM, John Ralls wrote:
>
> On Mar 12, 2011, at 8:01 AM, Christian Stimming wrote:
>
>> Am Samstag, 12. März 2011 schrieb John Ralls:
>>>>>>>>>> However, I think the git repo is missing many of the recent tags,
>>>&
On Mar 12, 2011, at 8:01 AM, Christian Stimming wrote:
> Am Samstag, 12. März 2011 schrieb John Ralls:
>>>>>>>>> However, I think the git repo is missing many of the recent tags,
>>>>>>>>> e.g. the 2.4.3 tag.
>>>
>>
Am Samstag, 12. März 2011 schrieb John Ralls:
> >>>>>>> However, I think the git repo is missing many of the recent tags,
> >>>>>>> e.g. the 2.4.3 tag.
> >
> > Sorry to bug you again, but the tags (e.g. 2.4.3) seem to belong to a
> &
rote:
>>>>> John Ralls writes:
>>>>>>> However, I think the git repo is missing many of the recent tags,
>>>>>>> e.g. the 2.4.3 tag. Maybe you need to run "git push --tags" or
>>>>>>> something similar so that the
Am Samstag, 12. März 2011 schrieb John Ralls:
> On Mar 11, 2011, at 2:06 PM, Christian Stimming wrote:
> > Am Freitag, 11. März 2011 schrieb John Ralls:
> >> On Mar 11, 2011, at 7:06 AM, Derek Atkins wrote:
> >>> John Ralls writes:
> >>>>> Howe
On Mar 11, 2011, at 2:06 PM, Christian Stimming wrote:
> Am Freitag, 11. März 2011 schrieb John Ralls:
>> On Mar 11, 2011, at 7:06 AM, Derek Atkins wrote:
>>> John Ralls writes:
>>>>> However, I think the git repo is missing many of the recent tags, e.g.
>&
Am Freitag, 11. März 2011 schrieb John Ralls:
> On Mar 11, 2011, at 7:06 AM, Derek Atkins wrote:
> > John Ralls writes:
> >>> However, I think the git repo is missing many of the recent tags, e.g.
> >>> the 2.4.3 tag. Maybe you need to run "git push --tags&q
On Mar 11, 2011, at 7:06 AM, Derek Atkins wrote:
> John Ralls writes:
>
>>> However, I think the git repo is missing many of the recent tags, e.g. the
>>> 2.4.3 tag. Maybe you need to run "git push --tags" or something similar so
>>> that the tag
John Ralls writes:
>> However, I think the git repo is missing many of the recent tags, e.g. the
>> 2.4.3 tag. Maybe you need to run "git push --tags" or something similar so
>> that the tags are actually pushed?
>
> Hmm. It looks like they have been lost s
for using it.
>
> Thanks a lot for preparing this new repo.
>
> I was able to successfully follow your instructions for cloning, then
> committing something locally and run "git svn dcommit" so that it showed up
> in
> SVN. Works fine.
>
> However, I
o successfully follow your instructions for cloning, then
committing something locally and run "git svn dcommit" so that it showed up in
SVN. Works fine.
However, I think the git repo is missing many of the recent tags, e.g. the
2.4.3 tag. Maybe you need to run "git push --tags"
On donderdag 10 maart 2011, John Ralls wrote:
> On Mar 9, 2011, at 6:27 AM, Geert Janssens wrote:
> > Can you explain this in some more detail for people not deeply into git
> > management ? I have played with git, but I can't map the above text to
> > what I understand so far.
>
> OK, I rewrote t
On Mar 9, 2011, at 6:27 AM, Geert Janssens wrote:
> On woensdag 9 maart 2011, John Ralls wrote:
>> Third time is the charm, I guess. The Git code repo is up and ready to be
>> cloned. I've rewritten completely http://wiki.gnucash.org/wiki/Git with
>> instructions for using it.
>>
> Thanks for th
On 9 March 2011 17:18, Derek Atkins wrote:
> Hi,
>
> Colin Law writes:
>
>> On 8 March 2011 23:50, John Ralls wrote:
>>>
>>> Third time is the charm, I guess. The Git code repo is up and ready to be
>>> cloned. I've rewritten completely http://wiki.gnucash.org/wiki/Git with
>>> instructions fo
Hi,
Colin Law writes:
> On 8 March 2011 23:50, John Ralls wrote:
>>
>> Third time is the charm, I guess. The Git code repo is up and ready to be
>> cloned. I've rewritten completely http://wiki.gnucash.org/wiki/Git with
>> instructions for using it.
>
> It all seems very complicated. Are you
On 8 March 2011 23:50, John Ralls wrote:
>
> Third time is the charm, I guess. The Git code repo is up and ready to be
> cloned. I've rewritten completely http://wiki.gnucash.org/wiki/Git with
> instructions for using it.
It all seems very complicated. Are you sure that it would not be
better
On woensdag 9 maart 2011, John Ralls wrote:
> Third time is the charm, I guess. The Git code repo is up and ready to be
> cloned. I've rewritten completely http://wiki.gnucash.org/wiki/Git with
> instructions for using it.
>
Thanks for the setup and documentation. I'll try it out in one of the
fo
Third time is the charm, I guess. The Git code repo is up and ready to be
cloned. I've rewritten completely http://wiki.gnucash.org/wiki/Git with
instructions for using it.
I'll do the htdocs repo later this week. I hope it won't take very long to
mirror.
Yawar, you haven't been synching the
On Mar 5, 2011, at 8:57 AM, Geert Janssens wrote:
> On zaterdag 5 maart 2011, John Ralls wrote:
>> I realized this morning that I hadn't reported recently on the progress
>> towards making the Github repo fully useable.
>>
>> My Mac Pro has been grinding away for two weeks converting the repo wi
On zaterdag 5 maart 2011, John Ralls wrote:
> I realized this morning that I hadn't reported recently on the progress
> towards making the Github repo fully useable.
>
> My Mac Pro has been grinding away for two weeks converting the repo with
> full metadata. After code.gnucash.org crashed last we
I realized this morning that I hadn't reported recently on the progress towards
making the Github repo fully useable.
My Mac Pro has been grinding away for two weeks converting the repo with full
metadata. After code.gnucash.org crashed last week I svnsync'd a local snapshot
and have been worki
On Jan 11, 2011, at 8:23 PM, Yawar Amin wrote:
> Hi John,
>
> Trying to understand your suggestion. Questions below:
>
> On 2011-01-08, at 17:16, John Ralls wrote:
>
>> […]
>>
>> Maybe instead you could create a fake-master branch off of master in your
>> git-svn repo and tie fake-master to
Hi John,
Trying to understand your suggestion. Questions below:
On 2011-01-08, at 17:16, John Ralls wrote:
> […]
>
> Maybe instead you could create a fake-master branch off of master in your
> git-svn repo and tie fake-master to github's master.
You mean:
[git-svn master] git checkout -b fak
On 01/10/2011 08:28 AM, Geert Janssens wrote:
On Monday 10 January 2011, Jeff Kletsky wrote:
At least as I understand it, branches in git are nothing more than a
pointer to the "head" commit and, structurally, are pretty much the same
(if not identical) to tags. A branch in git is a tag on point
On Jan 10, 2011, at 8:13 AM, Colin Law wrote:
> On 10 January 2011 15:56, Jeff Kletsky wrote:
>> At least as I understand it, branches in git are nothing more than a pointer
>> to the "head" commit and, structurally, are pretty much the same (if not
>> identical) to tags. A branch in git is a ta
On Monday 10 January 2011, Jeff Kletsky wrote:
> At least as I understand it, branches in git are nothing more than a
> pointer to the "head" commit and, structurally, are pretty much the same
> (if not identical) to tags. A branch in git is a tag on point in
> development that is moved to other co
On Monday 10 January 2011, Derek Atkins wrote:
> Geert Janssens writes:
> > On Wednesday 05 January 2011, Jeff Kletsky wrote:
> >> I don't like that history is a pretty flexible thing and that "branches"
> >> are just pointers to specific commits, rather than the kind of
> >> "followable path" tha
On 10 January 2011 15:56, Jeff Kletsky wrote:
> At least as I understand it, branches in git are nothing more than a pointer
> to the "head" commit and, structurally, are pretty much the same (if not
> identical) to tags. A branch in git is a tag on point in development that is
> moved to other co
On 10 January 2011 15:48, Derek Atkins wrote:
> Colin Law writes:
>
>> On 10 January 2011 15:12, Derek Atkins wrote:
>>> Geert Janssens writes:
>>>
On Wednesday 05 January 2011, Jeff Kletsky wrote:
> I don't like that history is a pretty flexible thing and that "branches"
> are jus
At least as I understand it, branches in git are nothing more than a
pointer to the "head" commit and, structurally, are pretty much the same
(if not identical) to tags. A branch in git is a tag on point in
development that is moved to other commits if you commit "to" that
branch. In simpler wo
Colin Law writes:
> On 10 January 2011 15:12, Derek Atkins wrote:
>> Geert Janssens writes:
>>
>>> On Wednesday 05 January 2011, Jeff Kletsky wrote:
I don't like that history is a pretty flexible thing and that "branches"
are just pointers to specific commits, rather than the kind of
On 10 January 2011 15:12, Derek Atkins wrote:
> Geert Janssens writes:
>
>> On Wednesday 05 January 2011, Jeff Kletsky wrote:
>>> I don't like that history is a pretty flexible thing and that "branches"
>>> are just pointers to specific commits, rather than the kind of
>>> "followable path" that
On Monday 10 January 2011, Geert Janssens wrote:
>
> What I don't have experience with at all yet is working with others via
> git. Like pushing or pulling changes to/from other git repositories.
>
Oh, and I forgot to add that I don't have experience with svk. So I don't know
it that also impro
Geert Janssens writes:
> On Wednesday 05 January 2011, Jeff Kletsky wrote:
>> I don't like that history is a pretty flexible thing and that "branches"
>> are just pointers to specific commits, rather than the kind of
>> "followable path" that svn provides.
>>
> That's interesting, because I feel
On Wednesday 05 January 2011, Jeff Kletsky wrote:
> I don't like that history is a pretty flexible thing and that "branches"
> are just pointers to specific commits, rather than the kind of
> "followable path" that svn provides.
>
That's interesting, because I feel exactly the oposite. I don't lik
On Thursday 06 January 2011, Mike Alexander wrote:
> --On January 5, 2011 2:12:06 PM -0500 Derek Atkins
> > I get the "git is cool" aspect of it. But I'm trying to get people
> > ignore the "git is cool" part and to seriously think about the
> > technicalities: what does git buy us that we don't
On Jan 8, 2011, at 1:41 PM, Yawar Amin wrote:
> Hi,
>
> On 2011-01-07, at 23:56, John Ralls wrote:
>
>>> […]
>>
>> I've moved you into the "owners" group. Do what you will.
>
> Thanks. I’ve pushed a new gnucash repository, as well as a gnucash-docs
> repository.
>
>> I've attached the autho
Hi,
On 2011-01-07, at 23:56, John Ralls wrote:
>> […]
>
> I've moved you into the "owners" group. Do what you will.
Thanks. I’ve pushed a new gnucash repository, as well as a gnucash-docs
repository.
> I've attached the authors file I made. If you reimport from svn it will match
> up svn acc
ed branch.
>> Yawar, since you have the svn data that goes with that import, you've bought
>> keeping github synchronized with svn and vice-versa.
>
> :-)
>
> To be honest I’m not entirely satisfied with the repo I pushed to GitHub. I
> did a git svn clone to get
27;ve bought keeping
> github synchronized with svn and vice-versa.
:-)
To be honest I’m not entirely satisfied with the repo I pushed to GitHub. I did
a git svn clone to get a Git repo that was tied to the SVN repo, but then I
pushed that into another ‘plain’ Git repo on my hard disk. Then I
On Jan 5, 2011, at 5:58 PM, John Ralls wrote:
>
> On Jan 5, 2011, at 11:01 AM, Derek Atkins wrote:
>
>> John Ralls writes:
>>
>>> I also started a straight git svn clone, which stopped mysteriously
>>> about the same place. I just restarted it.
>>
>> What's the bottleneck in doing the conver
--On January 5, 2011 2:12:06 PM -0500 Derek Atkins
wrote:
I understand the "I like git, so everyone should use it" mentality.
I'm trying to make sure we don't move over to git only because of
that. I want to make sure there are real technical reasons to spend
the time and effort to not only m
On Jan 5, 2011, at 11:01 AM, Derek Atkins wrote:
> John Ralls writes:
>
>> I also started a straight git svn clone, which stopped mysteriously
>> about the same place. I just restarted it.
>
> What's the bottleneck in doing the conversion?
This time I kept a tee-file of the output, but I didn
I maintain my own, local git repository and have a mixed love/hare
relationship with git.
For me, I like the lightweight branching and merge capabilities. I like
the built-in bisection to locate introduced changes in result (generally
bugs, but sometimes enhancements as well). For local deve
tion. Committing back to
> SVN is also a little tricky in certain situations. A gatekeeper would
> move all that to one point, giving Git users a Git repo that ‘just
> works’. It would collect all Git users’ work. Then someone comfortable
> with the way git-svn works could commit all the
Matthijs Kooijman writes:
> Hey Derek,
>
> a few notes on this, from a patch submitter's point of view :-)
>
>> >> So.. Feel free to play with git. But don't expect your SHA history to
>> >> remain 100% complete or that the repo you create wil
John Ralls writes:
> On Jan 5, 2011, at 2:29 AM, Christian Stimming wrote:
>
>> Am Dienstag, 4. Januar 2011 schrieb John Ralls:
>>> The second try stopped at r15521 for reasons that aren't entirely clear to
>>> me.
>>
>> This particular revision has nothing uncommon at all. I wouldn't understand
On Jan 5, 2011, at 2:29 AM, Christian Stimming wrote:
> Am Dienstag, 4. Januar 2011 schrieb John Ralls:
>> The second try stopped at r15521 for reasons that aren't entirely clear to
>> me.
>
> This particular revision has nothing uncommon at all. I wouldn't understand
> why git-svn stops partic
Am Dienstag, 4. Januar 2011 schrieb John Ralls:
> The second try stopped at r15521 for reasons that aren't entirely clear to
> me.
This particular revision has nothing uncommon at all. I wouldn't understand
why git-svn stops particularly there.
There are other SVN revisions which cause occasiona
at?
This is something only git-svn users experience. Cloning a large remote SVN
repository in Git is a long operation. Committing back to SVN is also a little
tricky in certain situations. A gatekeeper would move all that to one point,
giving Git users a Git repo that ‘just works’. It would collect
Hi John,
On 2011-01-04, at 15:11, John Ralls wrote:
> […]
>
> In trying to find out, I read to the bottom of the git-svn man page, where I
> found a section called "Caveats". The first paragraph says:
>> For the sake of simplicity and interoperating with a less-capable system
>> (SVN), it is r
The second try stopped at r15521 for reasons that aren't entirely clear to me.
Trying to get it to go further with git svn rebase are met with an error
message: Unable to determine upstream SVN information from working tree
history. I still don't know what that means.
In trying to find out, I
Hey Derek,
a few notes on this, from a patch submitter's point of view :-)
> >> So.. Feel free to play with git. But don't expect your SHA history to
> >> remain 100% complete or that the repo you create will at all resemble the
> >> "offical&qu
: Mike Alexander
Cc: gnucash-devel gnucash
Sent: Mon, January 3, 2011 3:15:44 PM
Subject: Re: Public Git repo
On Jan 3, 2011, at 12:02 PM, Mike Alexander wrote:
> --On January 3, 2011 10:13:34 AM -0800 Phil Longstaff
>wrote:
>
>>> Compared to SVN: topic/feature/bugfix branches
On Jan 3, 2011, at 12:02 PM, Mike Alexander wrote:
> --On January 3, 2011 10:13:34 AM -0800 Phil Longstaff
> wrote:
>
>>> Compared to SVN: topic/feature/bugfix branches. For example look at
>>> [2] and notice how each bug I’ve worked on has been in a separate
>>> Git branch. That history has b
--On January 3, 2011 10:13:34 AM -0800 Phil Longstaff
wrote:
Compared to SVN: topic/feature/bugfix branches. For example look at
[2] and notice how each bug I’ve worked on has been in a separate
Git branch. That history has been squished flat by SVN, but Git
remembers the branchy development.
On Jan 3, 2011, at 8:55 AM, Derek Atkins wrote:
> John,
>
> John Ralls writes:
>
>> OK, Christian, you're in.
>>
>> My first import try doesn't seem to have worked out very well, so I'll
>> have another go in a bit.
>
> Can you please keep good notes with what you're trying and what
> worked
See comment below prefixed by [Phil]
Phil
-
I used to be a hypochondriac AND a kleptomaniac. So I took something for it.
From: Derek Atkins
To: Yawar Amin
Cc: gnucash-devel gnucash
Sent: Mon, January 3, 2011 11:53:51 AM
Subject: Re: Public Git repo
John,
John Ralls writes:
> OK, Christian, you're in.
>
> My first import try doesn't seem to have worked out very well, so I'll
> have another go in a bit.
Can you please keep good notes with what you're trying and what
worked/failed in the process? This way we all can learn about it.
Maybe a
Yawar Amin writes:
>> HOWEVER
>> until we, the set of developers, decide as a group to migrate to git we
>> should not bless any tree as "the canonical tree”.
>
> This was actually why I suggested a ‘gatekeeper’ Git repo which we use
> to access the canonical S
On Jan 3, 2011, at 1:29 AM, Christian Stimming wrote:
> Zitat von John Ralls :
>>> Anyway, to end with a clear next action: John, would you be kind enough to
>>> create a ‘gnucash’ organization on GitHub and upload your repo there? I
>>> would like to clone it and try working on #634456.
>>
>>
Zitat von Derek Atkins :
And for the record, I feel using github would be okay for these trials,
but the official git repository should remain on our own server.
(Creating git.gnucash.org as a cname for code is perfectly reasonable, if
we decide to move to git).
I've grown to like github very m
Zitat von John Ralls :
Anyway, to end with a clear next action: John, would you be kind
enough to create a ‘gnucash’ organization on GitHub and upload your
repo there? I would like to clone it and try working on #634456.
OK, I've made a Gnucash "organization" with me as the admin and
Yawar
On Jan 2, 2011, at 9:00 PM, Yawar Amin wrote:
>
> Anyway, to end with a clear next action: John, would you be kind enough to
> create a ‘gnucash’ organization on GitHub and upload your repo there? I would
> like to clone it and try working on #634456.
>
OK, I've made a Gnucash "organization"
git we
> should not bless any tree as "the canonical tree”.
This was actually why I suggested a ‘gatekeeper’ Git repo which we use to
access the canonical SVN repo.[1] Any devs comfortable with Git will use the
gatekeeper, and any devs comfortable with SVN will use the canonical. Th
Hi,
On Sun, January 2, 2011 8:46 pm, Yawar Amin wrote:
> On 2011-01-02, at 19:41, John Ralls wrote:
>
>>> [
]
>>>
>>> On another note, now that 2.4.0 is out, how do we feel about setting up
>>> an official Git repo, say git.gnucash.org? Or even an off
On 2011-01-02, at 19:41, John Ralls wrote:
>> […]
>>
>> On another note, now that 2.4.0 is out, how do we feel about setting up an
>> official Git repo, say git.gnucash.org? Or even an official GnuCash repo on
>> GitHub/Gitorious/something else.
>
> Not tha
On Jan 2, 2011, at 2:33 PM, Yawar Amin wrote:
> Does anyone have a public, maintained Git repo of the entire GnuCash source
> tree? I’m trying to set up an Ubuntu 10.10 build so I can tweak some stuff
> and try it out. I’d prefer not using git-svn to gulp down the entire svn
>
Does anyone have a public, maintained Git repo of the entire GnuCash source
tree? I’m trying to set up an Ubuntu 10.10 build so I can tweak some stuff and
try it out. I’d prefer not using git-svn to gulp down the entire svn history
from the svn.gnucash.org server.
On another note, now that
On Jul 13, 2010, at 10:55 AM, Tao Wang wrote:
>
> I also like decentralized Git for development. We can use both
> git.gnome.organd
> github.com. We can use github.com for decentralized development, and push
> back to git.gnome.org, as an official repository, at any stage. Git is quite
> free t
On Friday 9 April 2010, John Ralls wrote:
> Geert,
>
> Sorry, that's a recent change to the moduleset (using guile-1.8 instead of
> guile-16; the latter is a separate module unaffected by the skip).
> Skip.add('guile") is in jhbuildrc because guile is included in jhbuild
> bootstrap, isn't need
On Apr 9, 2010, at 9:31 AM, Geert Janssens wrote:
> On Friday 9 April 2010, Geert Janssens wrote:
>> On Thursday 8 April 2010, John Ralls wrote:
>>> Geert,
>>>
>>> You're building 64-bit binaries, which isn't what you want. Edit the line
>>> in .jhbuildrc-custom that says 'setup_sdk("10.5", "10.
On Friday 9 April 2010, Geert Janssens wrote:
> On Thursday 8 April 2010, John Ralls wrote:
> > Geert,
> >
> > You're building 64-bit binaries, which isn't what you want. Edit the line
> > in .jhbuildrc-custom that says 'setup_sdk("10.5", "10.5")' to say
> > 'setup_sdk("10.5", "10.5", [i386])', m
On Thursday 8 April 2010, John Ralls wrote:
> Geert,
>
> You're building 64-bit binaries, which isn't what you want. Edit the line
> in .jhbuildrc-custom that says 'setup_sdk("10.5", "10.5")' to say
> 'setup_sdk("10.5", "10.5", [i386])', make sure the "build_policy" line is
> commented out, and
On Apr 8, 2010, at 12:11 PM, Geert Janssens wrote:
> On Wednesday 7 April 2010, John Ralls wrote:
>> On Apr 7, 2010, at 4:02 AM, Geert Janssens wrote:
>>> Hi,
>>>
>>> I'm trying to build GnuCash for OSX from the gnucash-on-osx git repo,
>>> fol
On Wednesday 7 April 2010, John Ralls wrote:
> On Apr 7, 2010, at 4:02 AM, Geert Janssens wrote:
> > Hi,
> >
> > I'm trying to build GnuCash for OSX from the gnucash-on-osx git repo,
> > following the instructions on http://wiki.gnucash.org/wiki/MacOSX/Quartz.
>
On Apr 7, 2010, at 4:02 AM, Geert Janssens wrote:
> Hi,
>
> I'm trying to build GnuCash for OSX from the gnucash-on-osx git repo,
> following the instructions on http://wiki.gnucash.org/wiki/MacOSX/Quartz.
>
> But I don't get very far. The build stops on gt
Hi,
I'm trying to build GnuCash for OSX from the gnucash-on-osx git repo,
following the instructions on http://wiki.gnucash.org/wiki/MacOSX/Quartz.
But I don't get very far. The build stops on gtk-doc, because it can't find
gnome-doc-utils. A bit higher up in the logs I find
94 matches
Mail list logo
