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. Back then, services= *was* in the file, period. It had to be. We manually added ",nodeinfo" to it when nodeinfo was created (and then added a bunch of nodeinfo.* lines), but that wasn't a big deal -- because nodeinfo was *new*. You could run without it and never know it existed, or that you were missing out on anything. But now, existing config files are breaking because something has been *removed* (or renamed) instead of added. There was no announcement made in #freenet's /topic, or on support@, or on chat@, except for the one that I sent to support@ a couple days ago when I learned about the issue and the solution to it. There's also nothing on http://freenetproject.org/ (unless it's in Ian's weblog, which is the most recent announcement on the web site). There was some discussion on the devl@ list, but to be honest I skimmed over most of it, thinking that it was just a simple consolidation of the services, or some sort of hack to pacify the people who were complaining that hard-coding the HTTP redirect was breaking their ssh tunneling. 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. 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 . But I don't always know when a change is important and when it isn't, and in the absence of any sort of announcement by the developer who's making a change, issues like this can easily slip through the cracks. This is turning out to be a longer message than I intended. Let me wrap it up with this: if you're a Freenet developer, and you make a change to Fred which might cause someone's node to break when they upgrade, then *please* send a message about the potential problem to one of the mailing lists. -- Greg Wooledge | "Truth belongs to everybody." greg at wooledge.org | - The Red Hot Chili Peppers http://wooledge.org/~greg/ | -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20020927/64636800/attachment.pgp>
