[fossil-users] Gentoo: SQLITE_WARNING... best approach for Portage
On Gentoo Linux, I created a custom ebuild to 2013-09-11 11:43:49, 2013094349, the version offered at http://www.fossil-scm.org/download.html. An ebuild is basically a recipe or install script for a package manager to download and install a project software. The package management system on Gentoo is called Portage and this is one of the main reasons I use Gentoo -- the convenience Portage provides making installing open source projects a breeze. Currently Gentoo's official Portage tree offers version 20130216000435 of Fossil at http://packages.gentoo.org/package/dev-vcs/fossil. I decided to create a custom ebuild as I wanted to get the latest and greatest release of fossil To create a custom ebuild in Gentoo, one can take an existing ebuild file and simply change its version and then see if it installs. http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3chap=5#doc_chap2 I tried using the 20130216000435 release as a template for the and had to remove a reference markdown. Otherwise, I successfully installed fossil 2013094349 using my custom ebuild. Then when I went to follow the Quick Start at http://www.fossil-scm.org/fossil/doc/trunk/www/quickstart.wiki I ran into the SQLITE_WARNING: file renamed while opening: /root/[project name] This SQLITE_WARNING issue was recently vetted on this mail list http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg13410.html. Gentoo offers the ability to follow a trunk line of code development on a project, but that feature is only for the not-so-feint of heart and discourage for obvious reasons. The better practice is to target a project's release, such as Fossil's 2013-09-11 11:43:49 and thereby reaching a broader audience. Portage can incorporate patches to a particular release. The reason I'm writing to this list is to inquire if there will be a new release coming shortly or if I should try to create an ebuild that incorporates the patch that fixes this problem? I'd like to see Gentoo's Portage contain the current release of Fossil. I do not want to submit my ebuild to Gentoo until I know what I have created works. I also don't want to spend the time if a new release is shortly around the corner, e.g. within several weeks. If a new release is not imminent, it would be a tremendous help if someone were to provide me a patch file for your 2013-09-11 11:43:49 release. I confess I'm not experienced in applying patches to Gentoo ebuilds, but I'm willing to try. John ___ 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] how to re-open trunk?
On Sun, Nov 10, 2013 at 07:22:35PM +0100, Stephan Beal wrote: On Sun, Nov 10, 2013 at 7:09 PM, Ben Collver bencoll...@gmail.com wrote: What is the normal way to re-open trunk? I could not find it in the UI. IIRC, you just need to open up the commit you want in the UI, probably this ... Try the Branches option and add it to the trunk branch. i seem to remember this coming up once before (a long time ago). Good evening, I took the following steps: $ fossil clone http://code.rogueclass.org/rcl rcl-test1.fossil $ mkdir rcl $ cd rcl $ fossil open ../rcl-test1.fossil $ fossil update --latest $ fossil settings autosync off $ fossil ui * Edit commit faf2ad2219 * Start new branch trunk $ fossil leaves --recompute You can view the results at the following URL. http://code.rogueclass.org/rcl-test1/ The good news is that the latest commit a6bf272559 is back in trunk, it is labeled as a leaf in the timeline, and it is back on the Open leaves page. The bad news is that trunk is still listed on the Closed Branches page. Is there a way to recompute the open branches? Thank you, -Ben ___ 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] Gentoo: SQLITE_WARNING... best approach for Portage
Thus said John L. Poole on Tue, 19 Nov 2013 05:12:08 -0800: The reason I'm writing to this list is to inquire if there will be a new release coming shortly or if I should try to create an ebuild that incorporates the patch that fixes this problem? I think it would be safest just to wait for the next release. Here are some issues you'll need to consider if you go the patch route: 1) Do you patch just this one bug fix? 2) If you patch the zip archive of the source the version identifier reported by your patched version and the non-patched will report the same. Making bug reporting difficult. 3) To avoid 2, you can merge/commit the patch into a private branch in a cloned copy of the fossil repository. Then extract the patch from there as a diff from the official released version and your branch. I don't know when the next official release will be, but this will give you an idea of the historical trend: http://www.fossil-scm.org/index.html/timeline?t=release Andy -- TAI64 timestamp: 4000528c4bdd ___ 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] how to re-open trunk?
Thus said Ben Collver on Tue, 19 Nov 2013 21:24:33 -0800: * Edit commit faf2ad2219 * Start new branch trunk You need to also edit 816b791510bd638d and add the trunk branch there. Andy -- TAI64 timestamp: 4000528c5460 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
