Main Stories
Slash Boxes

Slash Open Source Project

Slashcode Log In

Log In

[ Create a new account ]

Slashcode 1.0.7 Released

posted by CaptTofu on 02:56 PM July 12th, 2000   Printer-friendly   Email story
Slashcode 1.0.7 has been released. A couple more changes needed to get into the main branch that were significant enough to warrant a new release, so here it is. You can find it in all the usual places.
slash-1.0.7, 2000.07.12

*       Poll booth now checks to insure answers are in range before
        counting them

*       Removed spurious entries for user with uid "7" in users_
        tables in slashdata_dump.sql

*       Add schema changes for 1.0.6 back into slash_schema.sql

*       Added fixparam() function (same as fixurl($foo, 1)) and
        cleaned up fixurl() to better handle stuff

*       Slash now checks story dates for validity before saves and
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login
Loading... please wait.
  • Is this the beginning again of weekly updates, or was this just a coincidence?
  • 5.Restart slashd (if you have it set up, this could just be a /etc/rc.d/init.d/slashd restart or something like that; otherwise, ps -ef | grep slashd to get the PID and kill it by hand, then start it again)
    6.Restart apache
    That's about what I do, anyway.

    Ewwww. Ick. Pudge runs Red Hat ;)


  • The changes are not many. You can get all of them with just,,, and

    The database schema/dump changes are only for new users, really.
  • by Anonymous Coward
    Appreciate if someone could put the upgrade procedure to 1.0.7 in simple terms for me. I am getting started into slahcode..(cool stuff!). Am currently running 1.0.5

    1. Untar the 1.0.7 file under /home/slash and overwrite all the existing 1.0.5 files?
    2. Run the update script under sql/updates/1.0.6 as root or slash?

    script kiddie:)
  • And then did everything work? I also got around this but am still having problems with slash.
    We're up unless it's raining.
    We're up unless it's raining.
  • Is this it, though? I'm at Slashhosting.Com, and I want to know if this is the one I tell Ryan to update me to or if I should wait for 1.0.8, 1.0.9 or 1.0.25? Lemme know, --.\\-H--
  • I run both. Debian for PPC is still not well supported, so I use Yellow Dog Linux, which is based on LinuxPPC which is based on Red Hat. I think my other home box is Red Hat too, since I couldn't find a Debian CD and I don't really care. :-) But all the boxes Slashdot/Slashcode/etc. run on (except for the database box, which is Red Hat, because Debian had some problems with it) are Debian.
  • More like the end, actually. At this point, every release is another one that isn't supposed to happen, since work is now almost all on the development branch.

  • I don't know how much simpler Pudge could've put it, but here's a way that you can do it since you are running 1.0.5:

    Upgrade to 1.0.6, make sure your site(s) work,
    and then do the 1.0.7 upgrade. (The 1.0.7 upgrade is very easy to install, and reverse, if needed.)Atleast, this is how I did it, and so far I've no problems.

    When I did it, here's what I did:

    shut down apache

    Backup the current slash sql db (use mysql hot copy, etc, look at the mysql docs), and backup
    your slash user directory (/home/slash probably).

    I replaced all files in the account's user dir (typically /home/slash ) with the files from the 1.0.6 archive except the images directory ~slash/public_html/images/* and ~slash/

    Then imported the sql 1.0.6 upgrade changes.
    Then started apache up. Everything looked good.
    Shutdown apache.

    Then grab the 1.0.7 archive. Untar it to somewhere like /tmp. then do

    cp /tmp/slash-1.0.7/public_html/ ~slash/public_html/.
    cp /tmp/slash-1.0.7/public_html/ ~slash/public_html/.
    cp /tmp/slash-1.0.7/public_html/ ~slash/public_html/.
    cp /tmp/slash-1.0.7/ ~slash/.

    start apache, everything should be OK.

    lottadot []
  • It's been fixed in the latest dump file on CVS, and will, of course, be in the next release.
  • Yeah, we won't have another release any time soon, unless there is a real emergency. And if there is, maybe we will just upload a patch.
  • Yeah, we will only release the occasional bugfix release now. We put out this quick one because I really fuX0r3d fixurl(), and the schema thing was kinda screwed up, too (although that could be taken care of with the update script), and me and CaptTofu and Krow (the three full-time slash developers) are all gonna be gone next week at The Perl Conference [] (a.k.a. The Open Source Convention []).
  • I'm not sure if this was my version of MySQL-3.22.32-1 or something else, but there seems to be a bug (if it has been reported, please ignore this message) in dumping default tables to slash database. Towards the end of the dump, MySQL complains about invalid number of data and columns in the table. So, users_info table consists of 16 columns (fields) and the dump file only had 12. I was able to fix it by manually adding four additional values to each record for users_info table.

    Is this normal?


    e-mail: [mailto]


    e-mail: [mailto]
  • Tell me, what's wrong with Red Hat?

  • This is something like what I do (assuming that ~ is my live slash directory):
    1. Unpack the new dist in a separate directory and chdir to it
    2. Copy all the files over like so:
      1. cp dailyStuff moderatord portald slashd CHANGES README INSTALL ~
      2. cp bin/* ~/bin/
      3. cp docs/* ~/docs/
      4. cp contrib/* ~/contrib/ or cp -r contrib ~
      5. cp utils/* ~/utils/
      6. cp public_html/*.pl ~/public_html/
    3. diff -c ~/ and then add in all the changes by hand
    4. cd sql/updates/ and run all the SQL scripts from my current version to the new version (so for 1.0.5 to 1.0.7, that would be the script in 1.0.6, and there is none for 1.0.7)
    5. Restart slashd (if you have it set up, this could just be a /etc/rc.d/init.d/slashd restart or something like that; otherwise, ps -ef | grep slashd to get the PID and kill it by hand, then start it again)
    6. Restart apache

    That's about what I do, anyway.