View Issue Details

IDProjectCategoryView StatusLast Update
0003109GNUnetGNSpublic2013-12-24 20:54
Reportervikstrous Assigned ToMatthias Wachs  
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 03: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 13: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 14:30

reporter   ~0007634

fixed in rev 30696.

Issue History

Date Modified Username Field Change
2013-11-14 02:06 vikstrous New Issue
2013-11-14 02:06 vikstrous Status new => assigned
2013-11-14 02:06 vikstrous Assigned To => Matthias Wachs
2013-11-14 03:42 vikstrous Note Added: 0007630
2013-11-14 13:29 Christian Grothoff Note Added: 0007631
2013-11-14 13:29 Christian Grothoff Relationship added related to 0003092
2013-11-14 14:30 Matthias Wachs Note Added: 0007634
2013-11-14 14:30 Matthias Wachs Status assigned => resolved
2013-11-14 14:30 Matthias Wachs Resolution open => fixed
2013-11-16 15:45 Christian Grothoff Fixed in Version => 0.10.0
2013-11-16 15:45 Christian Grothoff Target Version => 0.10.0
2013-12-24 20:54 Christian Grothoff Status resolved => closed