Menu
▾
▴
pyblosxom-users
|
From: will kahn-g. <wi...@bl...> - 2010-08-03 15:05:57
|
Hi!
I just release pyblosxom 1.5rc2. It consists mostly of fixes to
plugins, additional tests, and documentation updates.
I also updated PyPI so doing::
pip install pyblosxom
works now.
Additionally, I tweaked the web-site so it's easier to find the most
recent release and older releases in the sidebar.
Plus I wrote up the release process because I had to go figure it out again.
Things I could use some help with:
1. reviewing, correcting and updating documentation
2. updating plugins in the contributed plugins pack to work with
PyBlosxom 1.5, adding tests for them, and cleaning up the plugin code
3. adding tests for PyBlosxom
4. making the web-site prettier, more useful, and less "busy"
5. writing a plugin that makes the front page static rather than an
index of blog entries
I could really use your help. If you're interested in helping, but
don't know where to start, let me know. I hang out as willkg on
#pyblosxom on freenode.
Rock on!
/will
|
|
From: Hauke F. <ha...@Es...> - 2010-08-09 21:27:19
|
At 11:05 Uhr -0400 3.8.2010, will kahn-greene wrote: >I just release pyblosxom 1.5rc2. It consists mostly of fixes to >plugins, additional tests, and documentation updates. Thanks, Will! I am the maintainer of the pkgsrc py-blosxom package <http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/py-blosxom/README.html>. A few minor pleas from here: Please be consistent in naming the releases (*1.5-rc1 vs. *1.5rc2), and the tarball (pyblosxom-*.tgz vs. pybloxsom*.tgz). pkgsrc can work around quirks like that, but they makes updating the package lengthier than needs be. The masters of pkgsrc like to know what's different in an update, so it would be helpful if there were release-specific (or at least dated) sections in the changelog. Keep up the good work! hauke -- "It's never straight up and down" (DEVO) |
|
From: will kahn-g. <wi...@bl...> - 2010-08-09 21:39:33
|
On 08/09/2010 04:43 PM, Hauke Fath wrote: > At 11:05 Uhr -0400 3.8.2010, will kahn-greene wrote: >> I just release pyblosxom 1.5rc2. It consists mostly of fixes to >> plugins, additional tests, and documentation updates. > > I am the maintainer of the pkgsrc py-blosxom package > <http://ftp.NetBSD.org/pub/pkgsrc/current/pkgsrc/www/py-blosxom/README.html>. A > few minor pleas from here: > > Please be consistent in naming the releases (*1.5-rc1 vs. *1.5rc2), and the > tarball (pyblosxom-*.tgz vs. pybloxsom*.tgz). pkgsrc can work around quirks > like that, but they makes updating the package lengthier than needs be. I changed version naming to be valid per the Python version metadata spec: http://www.python.org/dev/peps/pep-0386/ This allows versions to be compared correctly when using PyPI and other tools. If you check the Pyblosxom/pyblosxom.py file, you'll note that I've codified the new version scheme that will be used going forward. > The masters of pkgsrc like to know what's different in an update, so it > would be helpful if there were release-specific (or at least dated) > sections in the changelog. I don't plan on doing this for rc releases. rc releases are not considered final and are considered to be unstable. For now, if you want to see what's changed, grab the repository and look at "git log". If someone wants to volunteer to take the notes in git log and convert them into an appropriate changelog for rc releases, that'd be super, too. Just let me know and I'll point you in the right place and we'll figure out what the workflow should look like. /will |
|
From: seanh <sn...@gm...> - 2010-09-27 23:39:58
|
I can't get pyblosxom-1.5rc2 to work on Ubuntu 10.04. There seems to be
many ways of installing: pip, setuptools, easy_install, virtualenv, why
so many? And there are two sets of installation instructions, the
INSTALL file in the download the Installing PyBlosxom section in the
PyBlosxom 1.5 Documentation on the website. These two seem to be
slightly different from each other.
I'm just trying to get pyblosxom running so that I can make a blog on my
desktop and preview it with paste. I'll worry about deploying it to a
web server later. I'm going to give up for now and come back to it
another day.
$ cd ~/src/pyblosxom-1.5rc2
$ sudo pip install pyblosxom
Downloading/unpacking pyblosxom
Running setup.py egg_info for package pyblosxom
Using setuptools....
warning: no files found matching '*' under directory 'docs/source'
Installing collected packages: pyblosxom
Running setup.py install for pyblosxom
Using setuptools....
warning: no files found matching '*' under directory 'docs/source'
changing mode of /usr/local/bin/pyblosxom-cmd to 755
Successfully installed pyblosxom
$ pyblosxom-cmd -v
Traceback (most recent call last):
File "/usr/local/bin/pyblosxom-cmd", line 22, in <module>
from Pyblosxom.commandline import command_line_handler
ImportError: No module named Pyblosxom.commandline
$ sudo easy_install pyblosxom
Searching for pyblosxom
Best match: pyblosxom 1.5rc2
Adding pyblosxom 1.5rc2 to easy-install.pth file
Using /usr/local/lib/python2.6/dist-packages
Processing dependencies for pyblosxom
Finished processing dependencies for pyblosxom
$ pyblosxom-cmd -v
Traceback (most recent call last):
File "/usr/local/bin/pyblosxom-cmd", line 22, in <module>
from Pyblosxom.commandline import command_line_handler
ImportError: No module named Pyblosxom.commandline
$ sudo python setup.py install
... (lots of output)
$ pyblosxom-cmd -v
Traceback (most recent call last):
File "/usr/local/bin/pyblosxom-cmd", line 5, in <module>
pkg_resources.run_script('pyblosxom==1.5rc2', 'pyblosxom-cmd')
File "/usr/lib/python2.6/dist-packages/pkg_resources.py", line 461, in run_script
self.require(requires)[0].run_script(script_name, ns)
File "/usr/lib/python2.6/dist-packages/pkg_resources.py", line 1188, in run_script
raise ResolutionError("No script named %r" % script_name)
pkg_resources.ResolutionError: No script named 'pyblosxom-cmd'
I also tried the two different sets of instructions for installing with
virtualenv, and neither worked.
I'm stumped! And I have no idea how to clean up my system after all
those botched install commands seem to have left a terrible mess behind.
Now I tried just cd'ing into the pyblosxom-1.5rc2 source directory and
running `bin/pyblosxom-cmd create ./blog` and that worked, but then
`paster serve blog.ini` fails with "ImportError: No module named
Pyblosxom.pyblosxom". I'm not sure whether this is because previous
install commands have made a mess of my system.
<rant>
I hate all these language-specific package managers for Python, Ruby,
Haskell, etc. They're a disaster. There's millions of them, they always
fail, and they can't uninstall! So if you have a failed pyblosxom
install or an install of an old version and you want to try out a new
version, what can you do? You can't uninstall the old one so that you
can be sure you're starting fresh with the new one. You just have to
install the old version over the new one and hope for the best.
</rant>
|
|
From: seanh <sn...@gm...> - 2010-09-27 23:50:06
|
Hey, after all that, I closed my terminal emulator and opened it again
to clean up my environment and:
$ cd pyblosxom-1.5rc2
$ bin/pyblosxom-cmd create ./myblog
...
$ cd myblog
$ sudo aptitude install python-pastescript
$ paster serve blog.ini
Starting server in PID 2675.
serving on 0.0.0.0:5000 view at http://127.0.0.1:5000
So if all you want to do is try pyblosxom locally, all those install
tools seem to be unnecessary? I imagine that if I wanted to hack on
pyblosxom and git cloned it instead of downloading and extracting the
tarball, then I could run pyblosxom from the source directory the same
way as well.
That is, _if_ I understand things correctly and the paster server is
running pyblosxom from the source code files in the extracted tarball,
and not finding it elsewhere on my system as a result of all those
failed install commands. I don't know how to get back to a clean system
to find that out.
On Tue, Sep 28, 2010 at 12:39:42AM +0100, seanh wrote:
> I can't get pyblosxom-1.5rc2 to work on Ubuntu 10.04. There seems to be
> many ways of installing: pip, setuptools, easy_install, virtualenv, why
> so many? And there are two sets of installation instructions, the
> INSTALL file in the download the Installing PyBlosxom section in the
> PyBlosxom 1.5 Documentation on the website. These two seem to be
> slightly different from each other.
>
> I'm just trying to get pyblosxom running so that I can make a blog on my
> desktop and preview it with paste. I'll worry about deploying it to a
> web server later. I'm going to give up for now and come back to it
> another day.
>
> $ cd ~/src/pyblosxom-1.5rc2
> $ sudo pip install pyblosxom
> Downloading/unpacking pyblosxom
> Running setup.py egg_info for package pyblosxom
> Using setuptools....
> warning: no files found matching '*' under directory 'docs/source'
> Installing collected packages: pyblosxom
> Running setup.py install for pyblosxom
> Using setuptools....
> warning: no files found matching '*' under directory 'docs/source'
> changing mode of /usr/local/bin/pyblosxom-cmd to 755
> Successfully installed pyblosxom
>
> $ pyblosxom-cmd -v
> Traceback (most recent call last):
> File "/usr/local/bin/pyblosxom-cmd", line 22, in <module>
> from Pyblosxom.commandline import command_line_handler
> ImportError: No module named Pyblosxom.commandline
>
> $ sudo easy_install pyblosxom
> Searching for pyblosxom
> Best match: pyblosxom 1.5rc2
> Adding pyblosxom 1.5rc2 to easy-install.pth file
>
> Using /usr/local/lib/python2.6/dist-packages
> Processing dependencies for pyblosxom
> Finished processing dependencies for pyblosxom
>
> $ pyblosxom-cmd -v
> Traceback (most recent call last):
> File "/usr/local/bin/pyblosxom-cmd", line 22, in <module>
> from Pyblosxom.commandline import command_line_handler
> ImportError: No module named Pyblosxom.commandline
>
> $ sudo python setup.py install
> ... (lots of output)
> $ pyblosxom-cmd -v
> Traceback (most recent call last):
> File "/usr/local/bin/pyblosxom-cmd", line 5, in <module>
> pkg_resources.run_script('pyblosxom==1.5rc2', 'pyblosxom-cmd')
> File "/usr/lib/python2.6/dist-packages/pkg_resources.py", line 461, in run_script
> self.require(requires)[0].run_script(script_name, ns)
> File "/usr/lib/python2.6/dist-packages/pkg_resources.py", line 1188, in run_script
> raise ResolutionError("No script named %r" % script_name)
> pkg_resources.ResolutionError: No script named 'pyblosxom-cmd'
>
> I also tried the two different sets of instructions for installing with
> virtualenv, and neither worked.
>
> I'm stumped! And I have no idea how to clean up my system after all
> those botched install commands seem to have left a terrible mess behind.
>
> Now I tried just cd'ing into the pyblosxom-1.5rc2 source directory and
> running `bin/pyblosxom-cmd create ./blog` and that worked, but then
> `paster serve blog.ini` fails with "ImportError: No module named
> Pyblosxom.pyblosxom". I'm not sure whether this is because previous
> install commands have made a mess of my system.
>
> <rant>
> I hate all these language-specific package managers for Python, Ruby,
> Haskell, etc. They're a disaster. There's millions of them, they always
> fail, and they can't uninstall! So if you have a failed pyblosxom
> install or an install of an old version and you want to try out a new
> version, what can you do? You can't uninstall the old one so that you
> can be sure you're starting fresh with the new one. You just have to
> install the old version over the new one and hope for the best.
> </rant>
--
seanh <sn...@gm...>
|
|
From: seanh <sn...@gm...> - 2010-09-28 00:07:40
|
On Tue, Sep 28, 2010 at 12:49:53AM +0100, seanh wrote: > $ cd pyblosxom-1.5rc2 > $ bin/pyblosxom-cmd create ./myblog > ... > $ cd myblog > $ sudo aptitude install python-pastescript > $ paster serve blog.ini > Starting server in PID 2675. > serving on 0.0.0.0:5000 view at http://127.0.0.1:5000 > > That is, _if_ I understand things correctly and the paster server is > running pyblosxom from the source code files in the extracted tarball, > and not finding it elsewhere on my system as a result of all those > failed install commands. I don't know how to get back to a clean system > to find that out. Ok, I had a spare laptop with Ubuntu 10.04 on it so I tried the above on a clean system and the paster command failed with "No module named Pyblosxom.pyblosxom". So the reason it's working on my desktop must be that one of the various different install attempts succeeded. Whichever one it was, it required my terminal to be restarted before things would work. |
|
From: Will Kahn-G. <wi...@bl...> - 2010-09-28 01:15:13
|
So let's work through your issues one at a time: 1. The INSTALL file is different than the instructions on the web-site. That's because I did the 1.5rc2 release and then we did some documentation changes which I pushed to the web-site. The changes should be persisted in git, but they haven't made it to a release tarball yet. It's also possible that you were looking at the wrong site. Were you looking at the instructions on http://pyblosxom.bluesock.org/ or http://pyblosxom.sourceforge.net/ ? 2. Python/Ruby/Perl have their own packaging system which is different than the Ubuntu/Fedora/OpenSUSE/etc packaging systems. There are people who build packages of Python/Ruby/Perl modules. If you prefer to use your system's packaging system, then you'll have to either build the PyBlosxom package yourself or you'll have to wait for some other contributor to build it for you. Last time I checked Tollef was maintaining the PyBlosxom package for Debian and I think that's the package that Ubuntu has as well. You should create a Debian/Ubuntu bug to get him to update it. 3. There are a couple of different ways to install PyBlosxom because there are two different packaging systems for Python. Yes, it's kind of a pain in the ass. There are a lot of really great Python devs working on the situation currently and figuring out better solutions. 4. You couldn't get it to work with virtualenv. It sounds like you missed a step when setting up the virtual environment. Incidentally, using virtual environments makes it really easy to encapsulate PyBlosxom and it's dependencies into a directory that you can wipe away if you don't want it around anymore. Then it doesn't poison your system. Also, when you upgrade system packages, PyBlosxom won't break. I don't see any evidence of you being in a virtual environment in your emails, but I can only guess at what you did. It's possible the instructions need some more work, but they're pretty basic, so I'm not sure what we could improve. 5. You've now got a situation where you don't know what you've got on your system. Ubuntu packages Python 2.6 such that all site packages are stored in the same place (might be dist packages--I know they changed the name between Python 2.5 and 2.6, but I don't remember the details offhand). Find that directory and you can just delete the pyblosxom related directory trees. Then it won't be on your system anymore. 6. You used easy_install _AND_ pip. You don't want to mix and match easy_install/setuptools and pip/distribute because they don't play well with each other's metadata. I'll try to make that clearer in the instructions. Honestly, I didn't expect anyone to try both. I'm sorry that it's so frustrating. If anyone has any ideas on how to alleviate the confusion in the installation instructions, I'm interested in hearing them. The source for the instructions is the INSTALL file in the git repository. /will On Tue, 28 Sep 2010, seanh wrote: > On Tue, Sep 28, 2010 at 12:49:53AM +0100, seanh wrote: >> $ cd pyblosxom-1.5rc2 >> $ bin/pyblosxom-cmd create ./myblog >> ... >> $ cd myblog >> $ sudo aptitude install python-pastescript >> $ paster serve blog.ini >> Starting server in PID 2675. >> serving on 0.0.0.0:5000 view at http://127.0.0.1:5000 >> >> That is, _if_ I understand things correctly and the paster server is >> running pyblosxom from the source code files in the extracted tarball, >> and not finding it elsewhere on my system as a result of all those >> failed install commands. I don't know how to get back to a clean system >> to find that out. > > Ok, I had a spare laptop with Ubuntu 10.04 on it so I tried the above on > a clean system and the paster command failed with "No module named > Pyblosxom.pyblosxom". So the reason it's working on my desktop must be > that one of the various different install attempts succeeded. Whichever > one it was, it required my terminal to be restarted before things would > work. > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > pyblosxom-users mailing list > pyb...@li... > https://lists.sourceforge.net/lists/listinfo/pyblosxom-users > |
|
From: Asheesh L. <as...@as...> - 2010-09-28 13:11:28
|
On Tue, 28 Sep 2010, Will Kahn-Greene wrote: > > So let's work through your issues one at a time: > > 1. The INSTALL file is different than the instructions on the web-site. > That's because I did the 1.5rc2 release and then we did some documentation > changes which I pushed to the web-site. The changes should be persisted > in git, but they haven't made it to a release tarball yet. > > It's also possible that you were looking at the wrong site. Were you > looking at the instructions on http://pyblosxom.bluesock.org/ or > http://pyblosxom.sourceforge.net/ ? Will, can you make http://pyblosxom.sourceforge.net/ do an HTTP redirect to http://pyblosxom.bluesock.org/ to avoid confusion? -- Asheesh. |
|
From: will kahn-g. <wi...@bl...> - 2010-09-28 13:48:50
|
I think I left the sites the way they were because I didn't have permissions to edit certain files. The one I want to edit is the .htaccess file. I'll see what I can do. On 09/28/2010 09:04 AM, Asheesh Laroia wrote: > On Tue, 28 Sep 2010, Will Kahn-Greene wrote: > >> >> So let's work through your issues one at a time: >> >> 1. The INSTALL file is different than the instructions on the web-site. >> That's because I did the 1.5rc2 release and then we did some documentation >> changes which I pushed to the web-site. The changes should be persisted >> in git, but they haven't made it to a release tarball yet. >> >> It's also possible that you were looking at the wrong site. Were you >> looking at the instructions on http://pyblosxom.bluesock.org/ or >> http://pyblosxom.sourceforge.net/ ? > > Will, can you make http://pyblosxom.sourceforge.net/ do an HTTP redirect > to http://pyblosxom.bluesock.org/ to avoid confusion? > > -- Asheesh. |
|
From: seanh <sn...@gm...> - 2010-09-29 12:09:08
|
On Tue, Sep 28, 2010 at 01:15:04AM +0000, Will Kahn-Greene wrote: > > So let's work through your issues one at a time: > > 1. The INSTALL file is different than the instructions on the > web-site. That's because I did the 1.5rc2 release and then we did > some documentation changes which I pushed to the web-site. The > changes should be persisted in git, but they haven't made it to a > release tarball yet. Right. So the instructions on the site are the newest ones. > It's also possible that you were looking at the wrong site. Were > you looking at the instructions on http://pyblosxom.bluesock.org/ or > http://pyblosxom.sourceforge.net/ ? No, it was bluesock.org. > 4. You couldn't get it to work with virtualenv. It sounds like you > missed a step when setting up the virtual environment. > Incidentally, using virtual environments makes it really easy to > encapsulate PyBlosxom and it's dependencies into a directory that > you can wipe away if you don't want it around anymore. That's good to know about. I'll have to learn my way around virtualenv for the future. > 5. You've now got a situation where you don't know what you've got > on your system. Ubuntu packages Python 2.6 such that all site > packages are stored in the same place (might be dist packages--I > know they changed the name between Python 2.5 and 2.6, but I don't > remember the details offhand). Find that directory and you can just > delete the pyblosxom related directory trees. Then it won't be on > your system anymore. Great, thanks! Now I no how to clean up after python installers. Haven't had time to return to trying to install pyblosxom yet. I thought I'd try Jekyll instead, it is easy to install after all, just a simple gem install ARGH! :) > If anyone has any ideas on how to alleviate the confusion in the > installation instructions, I'm interested in hearing them. The > source for the instructions is the INSTALL file in the git > repository. Sorry that I don't have time to work on the docs, but I will give my thoughts. Try not to duplicate instructions because they might go out of sync, e.g. by having an INSTALL file and also install instructions on the website. The two notes at the top of the Installing PyBlosxom section in the docs are insufficient. This is the version of the docs I'm talking about: http://pyblosxom.bluesock.org/1.5/notes/INSTALL.html Here's what I would do to it: I think the Installing PyBlosxom section and subsections and the various Deploying PyBlosxom sections and the upgrading pyblosxom section probably need to be merged, they should each become subsections of one big installing and deploying page. They have some overlap I think (e.g. virtualenv and paste), and the difference between 'installing' and 'deploying' is not obvious, if they were merged into one section then that section could explain the difference at the top and contain all the info on one page instead of spread about. I would suggest the following headings: Section: Installing and Deploying PyBlosxom Subsection: Installing PyBlosxom on Your Computer Subsubsection: Installing PyBlosxom with virtualenv and paste Subsubsection: Upgrading PyBlosxom with virtualenv and paste Subsubsection: Installing PyBlosxom with distribute and pip Subsubsection: Upgrading PyBlosxom with distribute and pip Subsubsection: Installing PyBlosxom with setuptools and easy_install Subsubsection: Upgrading PyBlosxom with setuptools and easy_install Subsection: Deploying PyBlosxom to a Web Server The various subsubsections about the different ways of deploying. At the top of "Section: Installing and Deploying PyBlosxom" explain the difference between "Installing PyBlosxom on Your Computer" and "Deploying PyBlosxom to a Web Server". At the top of "Subsection: Installing PyBlosxom on Your Computer" add a paragraph explaining why there are multiple ways of installing pyblosxom on your computer, and some advice to the user about which they should choose. This should be in the form of an explanatory paragraph, an introduction to the section, currently there is a brief note saying virtualenv is easiest (and the instructions for virtualenv are elsewhere in a different section!). This is what I think it should explain: from what I now understand there are three ways to install: with virtualenv and paste, with distribute and pip, or with setuptools and easy_install. New users who just want to try out PyBlosxom and people who want to hack on PyBlosxom want to use virtualenv because it's easy to undo, it should say this right at the top of the section, and then the first subsection in the section should be the one that tells you how to install with virtualenv. Then, after trying PyBlosxom and deciding you want to use it, if you need to install it on your system you can do so with either distribute and pip or with setuptools and easy_install. There are two ways to install because Python, unfortunately, currently has two incompatible packaging systems. Warning: Choose one or the other, but don't try both as they will conflict with each other. Then the subsections about virtualenv, distribute and pip, and setuptools and easy_install would follow. In the subsubsections about each way of installing, explain briefly and in general terms what the install commands do. I know you won't be able to give exact details as it varies from system to system, but something like "it installs files to a specific place, e.g. /path/to/dist-packages on Ubuntu", would be a good idea, just so these commands seem less like sorcery and the user has at least a starting point if they need to debug or undo something. Hope that helps anyone who might do some work on the docs! |
|
From: seanh <sn...@gm...> - 2010-10-05 21:03:45
|
On Tue, Sep 28, 2010 at 01:15:04AM +0000, Will Kahn-Greene wrote: > 4. You couldn't get it to work with virtualenv. It sounds like you > missed a step when setting up the virtual environment. > Incidentally, using virtual environments makes it really easy to > encapsulate PyBlosxom and it's dependencies into a directory that > you can wipe away if you don't want it around anymore. Then it > doesn't poison your system. Also, when you upgrade system packages, > PyBlosxom won't break. I returned to the virtualenv instructions today. I don't understand step 4: http://pyblosxom.bluesock.org/1.5/notes/INSTALL.html#installing-pyblosxom-to-hack-on-it which says: `easy_install paste_deploy` or `pip install paste_deploy`. How are either of those commands going to know that I mean to install into the virtual environment that I've just created? Surely there is an instruction missing? I cd'd into the bin/ dir in my virtual environment and saw that it contains easy_install and pip executables so I tried executing the commands using those executables, but they don't seem to think that "paste_deploy" exists: seanh@kisimul:.../foo/VEDIR/bin % ./easy_install paste_deploy Searching for paste-deploy Reading http://pypi.python.org/simple/paste_deploy/ Reading http://pypi.python.org/simple/paste-deploy/ Couldn't find index page for 'paste_deploy' (maybe misspelled?) Scanning index of all packages (this may take a while) Reading http://pypi.python.org/simple/ No local packages or download links found for paste-deploy error: Could not find suitable distribution for Requirement.parse('paste-deploy') seanh@kisimul:.../VEDIR/bin % (1) ./pip install paste_deploy Downloading/unpacking paste-deploy Could not find any downloads that satisfy the requirement paste-deploy No distributions at all found for paste-deploy Storing complete log in /home/seanh/.pip/pip.log seanh@kisimul:.../VEDIR/bin % (1) Also, the note at the top of the Installing PyBlosxom page in the docs says "If you’re testing PyBlosxom, use virtualenv and deploy with Paste" but instructions to do so do not follow. They are further down the page, and with a different title "Installing PyBlosxom to hack on it". The note at the top of the page does not lead the reader to this subsection. |
|
From: Asheesh L. <as...@as...> - 2010-09-28 13:50:26
|
On Tue, 28 Sep 2010, will kahn-greene wrote: > I think I left the sites the way they were because I didn't have > permissions to edit certain files. The one I want to edit is the > .htaccess file. Even then, one giant GUYS THE SITE HAS MOVED notice would be way better than this confusing situation of two sites with content. If you want, I can write you a PHP file that will cause the redirect to happen, BTW. If SF.net can do PHP. -- Asheesh. -- Q: What do you call the money you pay to the government when you ride into the country on the back of an elephant? A: A howdah duty. |
|
From: Tim G. <tg...@pr...> - 2010-09-28 13:53:20
|
On Sep 28, 2010 at 09:50 AM -0400, Asheesh Laroia wrote: > Even then, one giant GUYS THE SITE HAS MOVED notice would be way better > than this confusing situation of two sites with content. Unfortunately the Sourceforge site is the first couple hits on Google. Not much you can do about that. Other than to use a redirect... |
|
From: Tim G. <tg...@pr...> - 2010-09-28 13:57:31
|
On Sep 28, 2010 at 12:39 AM +0100, seanh wrote: > I'm just trying to get pyblosxom running so that I can make a blog on my > desktop and preview it with paste. I'll worry about deploying it to a > web server later. I'm going to give up for now and come back to it > another day. I'll be honest with you, maybe because I'm not familiar with paste, but installing it remotely on Ubuntu 10.04 for a 'production' server was *way* easier for me than trying to get it up and running under paste on OS X locally for hacking. I ended up figuring I could hack in most of what I wanted via plugins, which was mostly true. Though it prevents me from contributing back in any meaningful manner. Someday I'll try again. For the server, I just used easy_install: sudo easy_install pyblosxom pyblosxom-cmd create blog cp pyblosxom.cgi /path/to/my/cgi/ chmod 755 pyblosxom.cgi |
|
From: Blake W. <bw...@la...> - 2010-09-28 14:25:16
|
I don't know if you can change anything on the page, but if you have access to the head element, you could add <meta http-equiv="refresh" content="0;url=http://pyblosxom.bluesock.org/" /> (from <http://en.wikipedia.org/wiki/Meta_refresh#Examples>) and it should do the trick. Later, Blake. On 09/28/2010 09:48 AM, will kahn-greene wrote: > I think I left the sites the way they were because I didn't have > permissions to edit certain files. The one I want to edit is the > .htaccess file. > > I'll see what I can do. > >> Will, can you make http://pyblosxom.sourceforge.net/ do an HTTP redirect >> to http://pyblosxom.bluesock.org/ to avoid confusion? >> |
|
From: will kahn-g. <wi...@bl...> - 2010-09-28 14:40:31
|
So there were two (three) problems. The first is that I needed to edit the .htaccess file so that I could rewrite all the urls to a single page that redirects to the new site. The second is that I needed to create the page that redirects. (The third problem is that SF drives me crazy because every time I want to go do something, I have to learn how they've changed how to do it. Rrrr....) The second item is/was easy. The problem is that I didn't have permissions to the .htaccess file and SF keeps changing how project web directories get edited. I talked with someone on #sourceforge to get permissions fixed and he/she was puzzled and then told me how to get shell access which it turned out they completely changed since the last time I fiddled with things. Long story short, the entire site should redirect to the new one now. If anyone sees pages that don't, let me know. /will On 09/28/2010 09:58 AM, Blake Winton wrote: > I don't know if you can change anything on the page, but if you have > access to the head element, you could add > > <meta http-equiv="refresh" content="0;url=http://pyblosxom.bluesock.org/" /> > > (from <http://en.wikipedia.org/wiki/Meta_refresh#Examples>) and it > should do the trick. > > Later, > Blake. > > On 09/28/2010 09:48 AM, will kahn-greene wrote: >> I think I left the sites the way they were because I didn't have >> permissions to edit certain files. The one I want to edit is the >> .htaccess file. >> >> I'll see what I can do. >> >>> Will, can you make http://pyblosxom.sourceforge.net/ do an HTTP redirect >>> to http://pyblosxom.bluesock.org/ to avoid confusion? >>> > > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > pyblosxom-users mailing list > pyb...@li... > https://lists.sourceforge.net/lists/listinfo/pyblosxom-users > |
|
From: Joseph R. <jos...@re...> - 2010-09-28 14:56:46
|
Is comment_draft_ext still supported? |
|
From: will kahn-g. <wi...@bl...> - 2010-09-28 14:52:50
|
I use it, so, yes. Why do you ask? Are you encountering problems with it? On 09/28/2010 10:42 AM, Joseph Reagle wrote: > > Is comment_draft_ext still supported? > |
|
From: Joseph R. <jos...@re...> - 2010-09-28 15:21:23
|
On Tuesday, September 28, 2010, will kahn-greene wrote: > I use it, so, yes. Why do you ask? Are you encountering problems with it? comments/README doesn't mention it and I haven't gotten it right yet in the upgrade, but working on it. A long time ago I had ping and trackbacks, but too much of it was spam -- trying to game Google rank. Do the new spam features like akismetcomments.py and check_javascript.py work for these too? |
|
From: will kahn-g. <wi...@bl...> - 2010-09-28 15:22:34
|
According to the documentation, akismetcomments works on comments and
trackbacks.
check_javascript probably doesn't help with spam from pingbacks and
trackbacks. I don't know if they work with pingbacks and trackbacks,
either.
I don't use pingbacks, trackbacks, check_javascript or akismetcomments
on my blog, so I don't know.
I do use comment_draft_ext and it works fine. I have it set like this
in my config.py file:
py["comment_draft_ext"] = "cmt-"
/will
On 09/28/2010 11:07 AM, Joseph Reagle wrote:
> On Tuesday, September 28, 2010, will kahn-greene wrote:
>> I use it, so, yes. Why do you ask? Are you encountering problems with it?
>
> comments/README doesn't mention it and I haven't gotten it right yet in the upgrade, but working on it.
>
> A long time ago I had ping and trackbacks, but too much of it was spam -- trying to game Google rank. Do the new spam features like akismetcomments.py and check_javascript.py work for these too?
>
|
|
From: Blake W. <bw...@la...> - 2010-09-28 16:21:33
|
On 09/28/2010 11:07 AM, Joseph Reagle wrote: > On Tuesday, September 28, 2010, will kahn-greene wrote: >> I use it, so, yes. Why do you ask? Are you encountering problems with it? > comments/README doesn't mention it and I haven't gotten it right yet in the upgrade, but working on it. > > A long time ago I had ping and trackbacks, but too much of it was spam -- trying to game Google rank. Do the new spam features like akismetcomments.py and check_javascript.py work for these too? I found that most of my spam comments were on articles that were older than 30 days, so I whipped up the noOldComments plugin, which you can find at http://bwinton.latte.ca/temp/noOldComments.py I know, it seems stupid that something so simple would block 98% of my spam comments, but there you go. :) Later, Blake. |
Thanks for helping keep SourceForge clean.
X