View Issue Details

IDProjectCategoryView StatusLast Update
0003109GNUnetGNSpublic2013-12-24 19:54
Reportervikstrous Assigned ToMatthias Wachs Due Date
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
PlatformlinuxOSarch linuxOS Version3.11.6-1-ARCH
Product VersionGit master 
Target Version0.10.0Fixed in Version0.10.0 
Summary0003109: gnunet-gns-import.sh does not use 'gnunet-namestore -i'
DescriptionThe last 3 lines of gnunet-gns-import.sh are along the lines of:

gnunet-namestore -z master-zone -a -e never -n pin -p -t PKEY -V 72QC35CO20UJN1E91KPJFNT9TG4CLKAPB4VK9S3Q758S9MLBRKOG

They don't use the -i option to give the entries a nickname. This was causing an error from one of the services started by gnunet-arm -s. It looks like the nickname was optional, but now it's mandatory? Maybe this script is out of date?

Let me know if more info is needed.
Steps To Reproduce1. install gnunet
2. run gnunet-arm -s
3. run gnunet-gns-import.sh
TagsNo tags attached.

Relationships

related to 0003092 closedMatthias Wachs Privacy preserving pseudonyms 

Activities

vikstrous

2013-11-14 02:42

reporter   ~0007630

This is the error:

Nov 13 21:41:16-525786 namestore-9695 ERROR No nick name set for zone `MRNLPRU19HEONFHOPDMQ13E4TH97R55JCJH6PJFT4VEIT5MHL6GG'

Christian Grothoff

2013-11-14 12:29

manager   ~0007631

The real issue is merely the log message, which should be at 'INFO' level at best. So don't worry about it.

Matthias Wachs

2013-11-14 13:30

reporter   ~0007634

fixed in rev 30696.

Issue History

Date ModifiedUsernameFieldChange
2013-11-14 01:06vikstrousNew Issue
2013-11-14 01:06vikstrousStatusnew => assigned
2013-11-14 01:06vikstrousAssigned To => Matthias Wachs
2013-11-14 02:42vikstrousNote Added: 0007630
2013-11-14 12:29Christian GrothoffNote Added: 0007631
2013-11-14 12:29Christian GrothoffRelationship addedrelated to 0003092
2013-11-14 13:30Matthias WachsNote Added: 0007634
2013-11-14 13:30Matthias WachsStatusassigned => resolved
2013-11-14 13:30Matthias WachsResolutionopen => fixed
2013-11-16 14:45Christian GrothoffFixed in Version => 0.10.0
2013-11-16 14:45Christian GrothoffTarget Version => 0.10.0
2013-12-24 19:54Christian GrothoffStatusresolved => closed