Public bug report changed:
https://launchpad.net/malone/bugs/6419
Task: ubuntu gnunet
Assignee: (unassigned) = MOTU
--
Universe-bugs mailing list
Universe-bugs@lists.ubuntu.com
http://lists.ubuntu.com/mailman/listinfo/universe-bugs
Public bug report changed:
https://launchpad.net/malone/bugs/6419
Comment:
I'll take care of this... thanks for reporting
--
Universe-bugs mailing list
Universe-bugs@lists.ubuntu.com
http://lists.ubuntu.com/mailman/listinfo/universe-bugs
Public bug report changed:
https://launchpad.net/malone/bugs/6419
Comment:
It seems like this config file is from an older version or something...
please delete it and create a new one with gnunet-setup.
It doesn't happen from a new install of gnunet-gtk
--
Universe-bugs mailing list
Public bug report changed:
https://launchpad.net/malone/bugs/6419
Comment:
[EMAIL PROTECTED]:~$ sudo aptitude update; sudo aptitude purge gnunet-gtk
gnunet; sudo aptitude install gnunet-gtk gnunet; gnunet-gtk
Password:
Pakketlijsten worden ingelezen... Klaar
Boom van vereisten wordt opgebouwd...
Public bug report changed:
https://launchpad.net/malone/bugs/6419
Comment:
Okay, it works after manually removing ~/.gnunet
Question is, will this break upgrades from breezy?
--
Universe-bugs mailing list
Universe-bugs@lists.ubuntu.com
http://lists.ubuntu.com/mailman/listinfo/universe-bugs
Public bug report changed:
https://launchpad.net/malone/bugs/6419
Comment:
It will break updates from breezy when someone has on old config in his
home directory... but we can't do anything about files in the home
directory of a user, sorry
(That's what I meant with a new install btw... first
