configured bootsrap node always defaults to port 4222
Issue generated from Tuleap's migration script. Originally submitted by: Simon Désaulniers (sim590)
I have found that configuring the port using the GNOME client configuration interface fails to configure a bootstrap address with the appropriate port.
I have tried bootstrapping on a local node (on my machine) using an address obtained from the router with first empty port, then changing the port and saving doesn't take the change into account when looking at the log.
I can confirm that this bug doesn't occur on Windows 32 client.