That's a good question. Ultimately, it all comes down to you, but as mentioned by the other commenters, the double ending 'n' (which is uncommon in English, as far as I know) and the fact that there's an established OSS project with a very similar name would make sure that people don't talk about your project as the "Hugin with two n's" or the "Huginn that's not the photography thing." Google will also helpfully redirect queries for "huginn download" to the other project[3], though that's probably because your project doesn't have many links to it yet.
That being said, they're not in a related area, so I doubt anyone would be excessively confused between both, as opposed to say, Go[1] and Go![2].
What I'd do, personally, is try to find another name and only keep the current project name if I can't find a better one that's not already taken. It makes it easier to rank well on Google and is less likely that someone will apt-get the wrong project.
Regardless of the hugin conflict, it'd be nice not to have to spell the name out to people when recommending this. Maybe even something ambitious like just calling it "Tubes"? (I'm not aware of anything else with that name.)
I vote yes. It's one consonant different from an existing application/thing. Having said that I'm terrible with naming things and can't offer any alternatives.
Ah just saw the reason for the name on github. I thought you chose it out of the blue. What about a line from Anchorman: "Great Odin's Raven!" or something to that effect :P
Don't ask me, I just see that your posts are [dead] (so, only someone who has 'showdead' in their profile, like me, can see them), and you don't seem like a troll or spammer, so I decided to tell you.
