Greg Wooledge <greg at wooledge.org> writes:
> Matthew Toseland (mtoseland at blueyonder.co.uk) wrote:
>
> > The problem is that some people have hardcoded services= (if they use
> > the default, since months ago, which is commented out, they'll get the
> > default list of services).
>
> Some people have config files that are older than the %thing.
Yeah, me too. And maybe people were using the config settings to
actually set something, not run with the defaults...
> But now, existing config files are breaking because something has
> been *removed* (or renamed) instead of added. There was no
> announcement [...] There was some discussion on the devl@ list, but
> to be honest I skimmed over most of it, [...]
It really boils down to this: if you're running bleeding edge Freenet,
you have to read devl. It's the logical place where developers post
announcements about changes to the development branch.
Unfortunately Freenet doesn't have a stable branch[1] currently, so
forwarding some information to other channels would certainly be a
good thing (is there an announce list?). You don't have to be a
developer to do this, but of course the person implementing a change
should understand its ramifications best.
That said, I can see how you could miss GJ's announcement to the list
-- the change itself seemed innocuous enough. "Windows/Unix installer
broken" did ring a warning bell, though.
> But, do you know what the most amazing aspect of this is to me? The
> build number is still 504! This incredibly non-backward-compatible
> change has been made without even bothering to bump the version number
> of the node.
The build number, as I understand it, is more for inter-node
communication, and this didn't change at all (it does, e.g. when
frobbing routing or announcement algorithms).
We could have another "config file generation" number ... or fix the
upgrade path -- a current node finding "fproxy" or "nodeinfo" in the
services, could just rewrite that to "mainport". That's what I do for
Debian, anyway.
> I'm trying to keep things running as smoothly as possible, because
> it's one of the ways that I can help Freenet. I've made an
> announcement on support@, I've added text to the FAQ, I've added
> text to my Freesite (which isn't always very well propagated), and
> I've put announcements in the #freenet topic. (Whoever made the
> channel "-t": thank you.) I've directly answered questions about
> the new mainport stuff from a few people in #freenet, and maybe one
> or two on support at .
Thanks!
Footnotes:
[1] Though you do have the option to not update to the latest and
greatest. A lot of sites in my routing table stayed at 480.
--
Robbe
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.ng
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL:
<https://emu.freenetproject.org/pipermail/devl/attachments/20020929/6b2ae1d0/attachment.pgp>
