On Fri, Aug 2, 2013 at 11:55 AM, Richard Hipp <d...@sqlite.org> wrote:
> On Fri, Aug 2, 2013 at 11:51 AM, Benedikt Ahrens > <benedikt.ahr...@gmx.net>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 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
