Bugs for Sorcery are reported here

[bugzilla-daemon AT bugs.sourcemage.org]

http://bugs.sourcemage.org/show_bug.cgi?id=14398


jakakranjc AT email.si changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED




------- Additional Comments From jakakranjc AT email.si  2008-03-28 16:20 -------
fixed in devel. Now it is nicer, but only checks the grimoire name when 
determining if the grimoire is official and explicitly needs to be verified - 
we have manifest support for trees (bug 8220), which was intended for rsync. 
But the manifest itself has to be gpg-signed and the keys are only searched 
for 
in the official keyrings and the manifests only in a hardcoded url pointing 
to 
our codex. So unofficial trees have no way to be verified and the shortcut 
makes sense.

lynxlynx navaden 0 # scribe add staable from 
git_local:///home/navaden/sorcery/
main-grim
Adding grimoire staable to /var/lib/sorcery/codex from git_local:///home/
navaden/sorcery/main-grim
Running git clone...
git-clone /home/navaden/sorcery/main-grim main-grim
Initialized empty Git repository in /var/lib/sorcery/codex/main-grim/.git/
0 blocks
Checking out files: 100% (28804/28804), done.
git-checkout master
Already on branch "master"
The grimoire (tree) staable is not an official grimoire and for such there is 
no verification method!
Continue anyway? [y]

Reindexing spell list... done.
Grimoire "/var/lib/sorcery/codex/staable" successfully added to your codex.

*********************************************************
Saying no gives you the old menu:
Continue anyway? [y] n
Verification of the grimoire tree staable failed!
What would you like to do?
        (0)  set aside
        (1)  remove
        (2)  ignore

Which one do you want? [0] 1


-- 
Configure bugmail: http://bugs.sourcemage.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.