Re: [fossil-users] fossil running out of memory
On Tue, Aug 20, 2013 at 5:56 PM, Benedikt Ahrens wrote: > It works fine with 1.26. > :) > BTW, is there any chance the Debian packaging could happen in a debian > branch of the fossil development repository, i.e. that the Debian fossil > maintainer get write access to that repo? > @that maintainer: if you're reading this, please speak up :). -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] fossil running out of memory
> On Mon, Aug 5, 2013 at 10:15 PM, Richard Hipp wrote: > >> On Mon, Aug 5, 2013 at 3:55 PM, Benedikt Ahrens >> wrote: >> >>> is not feasible in my situation. >>> >> >> packages or libraries or deal with package managers. Just copy *one file* >> into your $PATH on each machine where it matters. >> > > @Benedikt: the easiest thing to do is to edit your $PATH to include > $HOME/bin and drop fossil in $HOME/bin. If you need help with setting the > PATH, google for "ubuntu edit path" (bzw. "ubuntu path bearbeiten") and > several useful answers are there. Thanks. However, my objection to upgrading to newer fossil was not motivated by a lack of know-how, but rather by the fact that this solution comes with a complexity of O(number of affected machines). Also, not all of the affected machines are mine. >>My question was intended to be "Can I do something to the >> >>> repository---and not to fossil---in order to get things working again, >>> with version 1.22?" >>> >> > We don't know, and that version is old enough for us to justify suggesting > you try a newer version before we pursue it further. It works fine with 1.26. BTW, is there any chance the Debian packaging could happen in a debian branch of the fossil development repository, i.e. that the Debian fossil maintainer get write access to that repo? Thanks for your help and patience. Benedikt [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718812 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] fossil running out of memory
On Mon, Aug 5, 2013 at 10:15 PM, Richard Hipp wrote: > On Mon, Aug 5, 2013 at 3:55 PM, Benedikt Ahrens > wrote: > >> is not feasible in my situation. >> > > packages or libraries or deal with package managers. Just copy *one file* > into your $PATH on each machine where it matters. > @Benedikt: the easiest thing to do is to edit your $PATH to include $HOME/bin and drop fossil in $HOME/bin. If you need help with setting the PATH, google for "ubuntu edit path" (bzw. "ubuntu path bearbeiten") and several useful answers are there. >My question was intended to be "Can I do something to the > >> repository---and not to fossil---in order to get things working again, >> with version 1.22?" >> > We don't know, and that version is old enough for us to justify suggesting you try a newer version before we pursue it further. > [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718812 > > :) -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] fossil running out of memory
On Mon, Aug 5, 2013 at 3:55 PM, Benedikt Ahrens wrote: > > Hello, > > thanks a lot for your answers. > > The repository in question is a bit less than 100MB big and carries > around 30 binaries of up to 6MB each. > > I am aware that the fossil version I am using is outdated, but as Joseph > said, it is the version packaged in Debian stable, and in Ubuntu 12.04 > as well. Installing newer versions manually on all the machines involved > is not feasible in my situation. > You are aware that "installing" Fossil simply means copying the self-contained executable file into /usr/bin (or whatever other $PATH directory you want to use), right? There are no dependencies. You do not need to run configuration scripts or installers or update related packages or libraries or deal with package managers. Just copy *one file* into your $PATH on each machine where it matters. > My question was intended to be "Can I do something to the > repository---and not to fossil---in order to get things working again, > with version 1.22?" > > In line with what Joseph suggested I have filed a wishlist bug against > fossil in Debian, where I ask the package maintainer to package a recent > version of fossil for inclusion in unstable and testing (not backports, > though). > > Best, > Benedikt > > [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718812 > > > > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] fossil running out of memory
Hello, thanks a lot for your answers. The repository in question is a bit less than 100MB big and carries around 30 binaries of up to 6MB each. I am aware that the fossil version I am using is outdated, but as Joseph said, it is the version packaged in Debian stable, and in Ubuntu 12.04 as well. Installing newer versions manually on all the machines involved is not feasible in my situation. My question was intended to be "Can I do something to the repository---and not to fossil---in order to get things working again, with version 1.22?" In line with what Joseph suggested I have filed a wishlist bug against fossil in Debian, where I ask the package maintainer to package a recent version of fossil for inclusion in unstable and testing (not backports, though). Best, Benedikt [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718812 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] fossil running out of memory
On Fri, Aug 2, 2013 at 11:55 AM, Richard Hipp wrote:
> On Fri, Aug 2, 2013 at 11:51 AM, Benedikt Ahrens
> wrote:
>
Hello,
>>
>> I am having trouble with a fossil repository containing many binary files.
>>
>> The fossil version is the one packaged in Debian Wheezy:
>>
>> $ fossil version
>> This is fossil version 1.22 [ab461f39af] 2012-03-29 08:48:38 UTC
>>
>> Any hints what I could try to better debug the problem, or to even solve
>> it?
>>
>
> Version 1.22 is pretty old. I suspect that this problem is already
> solved. Just upgrade and you should be fine.
>
[I have intentionally CC'd the original poster with this response, on the
off-chance he is not subscribed to fossil-users.]
Debian Wheezy (a.k.a. 7.0) is the current stable version of Debian Linux.
He is using the version provided by the distribution (specifically
1:1.22.1+dfsg-0.1 -- the +dfsg-0.1 presumably refers to modifications made
by the packager to the original source code as provided by the Fossil
Project to make it acceptable for distribution in the "main" (as opposed to
"contrib" or "non-free") section of Debian Linux). Debian Wheezy was
officially released on 4 May 2013, with its first point release update on
15 Jun 2013. (It looks like Wheezy started to be "frozen" in terms of
adding new software or new versions of software, so as to stabilize it for
release as the next stable version of Debian Linux, around Apr 2012, tho
not all of it was frozen at that time.)
The current version of fossil in Debian Testing (which will become the next
stable version of Debian Linux in due time) is 1:1.24+dfsg-0.1, entering
Testing on 5 May 2013, which is still two point releases behind the current
stable release of Fossil as distributed by the Fossil Project itself.
Assuming the correct / easiest way to fix the problem is to upgrade the
version of fossil being used, and assuming the original poster wishes to
continue using fossil as provided by Debian (which allows it to be managed
by the package management system, the bug tracking system, etc), he could
either:
1: Upgrade his version of fossil to the version available through Debian
Testing, which might involve changes to his system configuration -- how to
do this is outside the scope of the fossil-users mailing list, and he
should probably contact / use one or more of the resources available for
support of Debian Linux if he needs help (which is the *point* of using a
distribution-provided binary, after all). Good places to look at would
include:
1.1: http://www.debian.org/support (talks about many different points of
contact for support, including IRC, wikis, bug reports, mailing lists, etc);
1.2: http://www.debian.org/MailingLists/ (talks about the many Debian
mailing lists for end-user support and other purposes); and specifically
1.3: http://lists.debian.org/debian-user/ ("Help and discussion among users
of Debian / Support for Debian users who speak English. (High-volume
mailing list.)")
2: Request that the version of fossil available in Debian Testing be
backported to Debian Wheezy, where it will be found in the
"wheezy-backports" repository, and then install it from wheezy-backports.
See http://www.debian.org/News/2013/20130320.en.html - "Backports
integrated in the main archive" for more information.
3. Request that the version of fossil in Debian Testing be upgraded to the
most recent stable version of fossil as released by the Fossil Project,
which appears to be 1.26 (per http://www.fossil-scm.org/download.html), and
then (if applicable) request this updated version be backported to
wheezy-backports. The easiest way to do this would be to file a wishlist
bug against fossil in the Debian bug tracking system requesting the new
version be packaged and/or backported.
Alternatively, the original poster could resend the bug and/or ask for help
directly to Debian (by filing a bug against fossil in the BTS, sending a
mail message requesting help to debian-user, etc). This might result in a
version upgrade as mentioned above, or might result in just this bug being
fixed (which fix hopefully would be sent upstream to the Fossil Project).
Since Debian is providing the binary the original poster is using, Debian
(and not the Fossil Project) is responsible for first-tier end-user
support. (Debian presumably would forward upstream bugs and/or patches for
them which were bugs in the original source code as distributed by the
Fossil Project.)
Unfortunately, I am not currently using Debian (or any) Linux, nor am I
actively using fossil, so I myself cannot be of more direct help. But,
that's my advice for the original poster, assuming they wish to continue to
use fossil as provided by Debian (as opposed to fossil as provided by the
Fossil Project).
Thanks for giving me some of your time by reading this response. I hope it
is of some use, interest. Be well.
Joseph
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
h
Re: [fossil-users] fossil running out of memory
On Fri, Aug 2, 2013 at 11:51 AM, Benedikt Ahrens wrote: > > Hello, > > I am having trouble with a fossil repository containing many binary files. > > The fossil version is the one packaged in Debian Wheezy: > > $ fossil version > This is fossil version 1.22 [ab461f39af] 2012-03-29 08:48:38 UTC > > Any hints what I could try to better debug the problem, or to even solve > it? > Version 1.22 is pretty old. I suspect that this problem is already solved. Just upgrade and you should be fine. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] fossil running out of memory
On Fri, Aug 2, 2013 at 5:51 PM, Benedikt Ahrens wrote: > $ fossil version > This is fossil version 1.22 [ab461f39af] 2012-03-29 08:48:38 UTC > Oh, my, that's practically 27 years old. In that time one of the devs (don't remember who) put a lot of work into trimming down stray allocations/missing deallocations, and you might have better luck with a newer binary. > On a different machine with the same operating system, fossil version > and architecture, cloning and updating works without problems. > > Any hints what I could try to better debug the problem, or to even solve > it? > First we need more info: how many is "many" and how big is "big"? But first, please try with a version from this year. It fossil crashing with an allocation error or just eating up everything for a while? -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] fossil running out of memory
Hello, I am having trouble with a fossil repository containing many binary files. Firstly, after cloning I only have the first (empty) commit in the timeline, even though many commits have been made to the cloned repository: $ fossil timeline === 2013-08-01 === 13:06:56 [c497b616a3] *CURRENT* initial empty check-in (user: user tags: trunk) Then, when trying to update, fossil runs out of memory: $ fossil update trunk Autosync: https://u...@host.com/cgi-bin/r.cgi/repo Bytes Cards Artifacts Deltas Sent: 177 2 0 0 Received:4679 96 0 1 Total network traffic: 396 bytes sent, 2773 bytes received fossil: out of memory During the update try, fossil uses 100% of one of the cores (AMD Athlon 64 X2 Dual Core Processor 4400+). The fossil version is the one packaged in Debian Wheezy: $ fossil version This is fossil version 1.22 [ab461f39af] 2012-03-29 08:48:38 UTC On a different machine with the same operating system, fossil version and architecture, cloning and updating works without problems. Any hints what I could try to better debug the problem, or to even solve it? Thanks a lot. Benedikt ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
