[fossil-users] fossil: bad object id: 0
Hello, I've been using from some time fossil built for cygwin [12a79e5b93]. And on fossil update it says only this: fossil: bad object id: 0 fossil rebuild does not help. We use a central repository in linux 32-bit also running that version, but some clients use older and newer fossil versions (all after 2010-09-01). Any idea? Regards, Lluís. ___ 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: bad object id: 0
On Tue, Nov 23, 2010 at 09:57:23AM +0100, Lluís Batlle i Rossell wrote: Hello, Ah, I thought I was in an open branch. This happens only when updating (fossil update), being in a closed branch. It happens with the latest released version too. fossil update in an open branch works fine. The error surprised me, and I wrote instead of noticing I was not in 'trunk'. Regards, Lluís. ___ 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: bad object id: 0
On Tuesday 23 November 2010 12:06:51 Lluís Batlle i Rossell wrote: Ah, I thought I was in an open branch. This happens only when updating (fossil update), being in a closed branch. Nevertheless, it's an unexpected result. The message given should be more informative. -- For privacy, my GPG key signature is: AD29415D signature.asc Description: This is a digitally signed message part. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] (no subject)
Hi, I've release a new version of Fossil GUI Jurassic (0.3.0). New user interface with office-ish ribbon (with tickets and wikis). Fixed the DAG upside-down problem. Discuss: http://groups.google.com/group/jurassic-fossil Download: http://code.google.com/p/jurassic-fossil/ Enjoy! ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Still trouble changing two fields in a ticket
Hello, I wrote a ticket long ago to fossil. We have an 'assigned_to' field. http://www.fossil-scm.org/index.html/tktview?name=13813896d5 If in a ticked Edit I change 'assigned_to' and add a comment, the ticket does not change at all. Nothing new appears in the history either. If I only add a comment, it works. If I only change the 'assigned_to', it works. Both, not. It happend to me with every ticket. Using firebug, I see the 'Post' says, for this case: assigned_to viric cmappnd we have to remember to split the headers csrf6/8D420CD4 effort foundin [de6ac549e7] name78282ff482 owner viric priorityImmediate private_contact resolution Open severityImportant status Open submit Submit Changes subsystem core title Move that thing there typeCode_Defect usernameviric Any idea of what happens? Regards, Lluís. ___ 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] (no subject)
Hi, I can't run it on 1.6, what java version did you compile with? Exception in thread AWT-EventQueue-0 java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.RangeCheck(ArrayList.java:547) at java.util.ArrayList.get(ArrayList.java:322) at jurassic.GUI2.configureApplicationMenu(GUI2.java:478) at jurassic.GUI2$4.run(GUI2.java:303) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209) at java.awt.EventQueue.dispatchEvent(EventQueue.java:597) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161) at java.awt.EventDispatchThread.run(EventDispatchThread.java:122) Petr On Tue, Nov 23, 2010 at 12:40, markovi...@inwind.it markovi...@inwind.it wrote: Hi, I've release a new version of Fossil GUI Jurassic (0.3.0). New user interface with office-ish ribbon (with tickets and wikis). Fixed the DAG upside-down problem. Discuss: http://groups.google.com/group/jurassic-fossil Download: http://code.google.com/p/jurassic-fossil/ Enjoy! ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] R: Re: (no subject)
Hi, as written on the web page, you must run Jurassic from the same folder where your .fossil are. Messaggio originale Da: p...@madnetwork.org Data: 23/11/2010 13.13 A: markovi...@inwind.itmarkovi...@inwind.it, fossil-us...@lists.fossil- scm.org Cc: jurassic-fos...@googlegroups.com Ogg: Re: [fossil-users] (no subject) Hi, I can't run it on 1.6, what java version did you compile with? Exception in thread AWT-EventQueue-0 java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.RangeCheck(ArrayList.java:547) at java.util.ArrayList.get(ArrayList.java:322) at jurassic.GUI2.configureApplicationMenu(GUI2.java:478) at jurassic.GUI2$4.run(GUI2.java:303) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209) at java.awt.EventQueue.dispatchEvent(EventQueue.java:597) at java.awt.EventDispatchThread.pumpOneEventForFilters (EventDispatchThread.java:269) at java.awt.EventDispatchThread.pumpEventsForFilter (EventDispatchThread.java:184) at java.awt.EventDispatchThread.pumpEventsForHierarchy (EventDispatchThread.java:174) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java: 169) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java: 161) at java.awt.EventDispatchThread.run(EventDispatchThread.java:122) Petr On Tue, Nov 23, 2010 at 12:40, markovi...@inwind.it markovi...@inwind.it wrote: Hi, I've release a new version of Fossil GUI Jurassic (0.3.0). New user interface with office-ish ribbon (with tickets and wikis). Fixed the DAG upside-down problem. Discuss: http://groups.google.com/group/jurassic-fossil Download: http://code.google.com/p/jurassic-fossil/ Enjoy! ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ 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] Contributor agreements in Fossil projects
On Wed, Nov 17, 2010 at 01:06:45PM -0600, Nolan Darilek wrote: I have a project for which I'd like to use copyright assignment for all contributors. In thinking about it for a bit, I felt like Fossil might work well for this system. My thoughts were to make the contributor agreement a Wiki page, then have people's signatures take the form: - -- Real Name (fossil username) Fossil doesn't really give you integrity in the sense that a commit by a given username was really done by that person. As such I would strongly advice against doing this. You can protect against that with signing every commit, but in that case you can just require a clear-signed version of your copyright assignment as well. For practical reasons, it is useful to have that in paper as well, but that's a different issue :) Joerg ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Updating, with files moved
Hello, I had the working directory with some files moved from one directory to another: Something like this, but on three files: fossil mv path/file.txt path2/file.txt mv path/file.txt path2/file.txt edit path2/file.txt ... Then I decide to do: fossil update # being on trunk And to my surprise, the update had lines like: CONFLICT path2/file.txt REMOVE path2/file2.txt ADD path/file.txt ADD path/file2.txt So it updated the working directory quite wrong, if I understand correctly. Some of the files I had were removed. And the 'fossil status' now shows nothing about path2, but all edited in 'path'. All the 'fossil mv' things went away. It seems like today I'm having more troubles than usual with fossil. :) (version [cf178577ec]) ___ 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] Updating, with files moved
On Tue, Nov 23, 2010 at 03:00:10PM +0100, Lluís Batlle i Rossell wrote: Hello, I had the working directory with some files moved from one directory to another: Something like this, but on three files: fossil mv path/file.txt path2/file.txt mv path/file.txt path2/file.txt edit path2/file.txt ... Then I decide to do: fossil update # being on trunk And to my surprise, the update had lines like: CONFLICT path2/file.txt REMOVE path2/file2.txt ADD path/file.txt ADD path/file2.txt So it updated the working directory quite wrong, if I understand correctly. Some of the files I had were removed. And the 'fossil status' now shows nothing about path2, but all edited in 'path'. All the 'fossil mv' things went away. I forgot to mention that none of the files I had modified were modified between the initial ckout and the head of trunk. So it should have been trivial to merge, I think. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] Change of marking of privacy for branches ...
Hello, I have a question that is associated with ticket [e29ea5912a] Privacy attribution loss due to de/reconstruct. Currently, information which artifacts are private is stored in a SQL table 'private' whose content cannot be deconstructed or transferred to another repository. A repository that is deconstructed and reconstructed again, lose all information what branches were private in the original repository. Now I am thinking whether it could be a feasible idea to not store privacy information within a separate table, but to simply attach a raw tag 'private' (*not* 'sym-private') to every checkin we would like to mark private (i.e. that should not be sync'd or cloned). Such a raw-tag could survive a deconstruct/reconstruct cycle. And more: we could edit a branch privacy after the fact, if we like. Or we could also allow to 'push' such branches marked as 'private' to e.g. a backup repository. This would allow to backup a large repository via automatic issued push tasks, instead of copying the whole repository ever and ever again ... Would anything speack against such changed behavior to depend a branche's privacy on a raw-tag instead of an entry in a local SQL table within the repository? What is your opinion? Regards, chi. ___ 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] Still trouble changing two fields in a ticket
On Tue, Nov 23, 2010 at 04:57:21PM -0500, Erik Lechak wrote: Hello, If in a ticked Edit I change 'assigned_to' and add a comment, the ticket does not change at all. Nothing new appears in the history either. If you look at the system log under admin, you will see that there are artifacts that contain the changes you made. But they are not being applied to the ticket. I just wrote about that problem and posted the code that will fix that error. See my last two posts to this group for a more detailed description of the problem and the fix. I've submitted the code fix, but I don't have the ability to check it in. (Can somebody help me with the check-in issue?) If you need this feature to work now without the code fix, you can get around the bug by naming the assigned_to field to xassigned_to. You will need to change it in all of your ticket editing and viewing pages as well. Thank you very much! I also cannot checkin. I hope someone will take the fix in. I'll wait for that. ___ 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] ticket bug fixed, how should I submit it?
On Sun, Nov 21, 2010 at 3:32 AM, Erik Lechak e...@lechak.info wrote:
Hello,
manifest.c has this code:
if( i0 strcmp(p-aField[i-1].zName, zName)=0 ){
goto manifest_syntax_error;
}
The code above is correct. J-cards have to be in strict lexicographical
order, including any + prefix.
But it doesn't take into account that names can have a '+' prepended
to the front of them.
This code fixes it:
if (i0){
curName = zName;
prevName = p-aField[i-1].zName;
//strip off leading plus sign if it exists
if (curName[0] == '+') curName++;
if (prevName[0] == '+') prevName++;
if (strcmp(prevName, curName)=0){
goto manifest_syntax_error;
}
}
Should I add a trouble ticket?
Should I submit a patch file?
I've already submitted a signed code release form, should I just check
the code in (my login no longer works)?
Thanks,
Erik Lechak
___
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] ticket bug fixed, how should I submit it?
Hello, The code above is correct. J-cards have to be in strict lexicographical order, including any + prefix. Huh... Then the J-card system appears to be broken. When I have an assigned_to column fossil generates the following: D 2010-11-15T23:38:35 J assigned_to eriklechak J +comment \n\nhr\s/ieriklechak\sadded\son\s2010-11-15\s23:38:35:/ibr\s/\nabcd K b8d3a9acb552bc11cc01483fcc710d6c994198e3 U eriklechak Z 9e9120a9d85b67a50280a96b04d117c6 In ascii the + comes before the a. And the strcmp throws a manifest error. --Erik Lechak ___ 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] ticket bug fixed, how should I submit it?
On Tue, Nov 23, 2010 at 05:41:46PM -0500, Richard Hipp wrote: On Tue, Nov 23, 2010 at 5:31 PM, Erik Lechak e...@lechak.info wrote: Huh... Then the J-card system appears to be broken. When I have an assigned_to column fossil generates the following: Correct. The ticket-change artifact generator was putting the J-cards in the wrong order. Fixed here: http://www.fossil-scm.org/fossil/ci/e1dac0e4f6 Thank you very much to both! ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
