Ticket #13407 (confirmed Bug)
Akismet is rejecting valid bug reports
Reported by: | MatthewWilkes | Owned by: | admins@… |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | Sysadmin and Development Infrastructure | Version: | |
Keywords: | trac | Cc: |
Description (last modified by aclark) (diff)
woha on IRC couldn't submit #13406 due to akismet.
Example of legitimate content that caused Akismet to report spam:
[...] running install_egg_info Writing /home/whartter/plone/Python-2.7/lib/python2.7/lib-dynload/Python-2.7.3-py2.7.egg-info if test -f /home/whartter/plone/Python-2.7/bin/python -o -h /home/whartter/plone/Python-2.7/bin/python; \ then rm -f /home/whartter/plone/Python-2.7/bin/python; \ else true; \ fi (cd /home/whartter/plone/Python-2.7/bin; ln -s python2 python) rm -f /home/whartter/plone/Python-2.7/bin/python2 (cd /home/whartter/plone/Python-2.7/bin; ln -s python2.7 python2) rm -f /home/whartter/plone/Python-2.7/bin/python2-config (cd /home/whartter/plone/Python-2.7/bin; ln -s python2.7-config python2-config) rm -f /home/whartter/plone/Python-2.7/bin/python-config (cd /home/whartter/plone/Python-2.7/bin; ln -s python2-config python-config) test -d /home/whartter/plone/Python-2.7/lib/pkgconfig || /usr/bin/install -c -d -m 755 /home/whartter/plone/Python-2.7/lib/pkgconfig rm -f /home/whartter/plone/Python-2.7/lib/pkgconfig/python2.pc (cd /home/whartter/plone/Python-2.7/lib/pkgconfig; ln -s python-2.7.pc python2.pc) rm -f /home/whartter/plone/Python-2.7/lib/pkgconfig/python.pc (cd /home/whartter/plone/Python-2.7/lib/pkgconfig; ln -s python2.pc python.pc) Creating directory /home/whartter/plone/Python-2.7/share/man/man1 /usr/bin/install -c -m 644 ./Misc/python.man \ /home/whartter/plone/Python-2.7/share/man/man1/python2.7.1 ##################################################################### Calling install.sh again without changing parameters will finish the installation: ./install.sh standalone --target=/home/whartter/plone --build-python standalone We already have a Python environment for this target; ignoring --build-python. Rootless install method chosen. Will install for use by system user whartter Detailed installation log being written to /home/whartter/Downloads/plone/Plone-4.3b1-UnifiedInstaller/install.log Installing Plone 4.3b1 at /home/whartter/plone Unpacking buildout cache to /home/whartter/plone/buildout-cache Copying Plone-docs Copying buildout skeleton Fixing up bin/buildout Building Zope/Plone; this takes a while... Buildout completed ##################################################################### ###################### Installation Complete ###################### Plone successfully installed at /home/whartter/plone See /home/whartter/plone/zinstance/README.html for startup instructions Use the account information below to log into the Zope Management Interface The account has full 'Manager' privileges. Username: xxx Password: xxx This account is created when the object database is initialized. If you change the password later (which you should!), you'll need to use the new password. Use this account only to create Plone sites and initial users. Do not use it for routine login or maintenance. - If you need help, ask the mailing lists or #plone on irc.freenode.net. - The live support channel also exists at http://plone.org/chat - You can read/post to the lists via http://plone.org/forums - Submit feedback and report errors at http://dev.plone.org/plone (For install problems, specify component "Installer (Unified)")
Why does this happen? Can we "train" Akismet?
Change History
comment:1 Changed 3 years ago by MatthewWilkes
- Cc eleddy added
- Keywords trac added
- Component changed from Unknown to Sysadmin and Development Infrastructure
- Owner set to admins@…
- Milestone 4.x deleted
comment:2 Changed 3 years ago by eleddy
- Cc aclark added; eleddy removed
I don't know what this means. popcorn.
comment:5 Changed 3 years ago by aclark
Me neither, but I removed the content having to do with #13406 since it has nothing to do with the Trac + Akismet problem which is apparently what this ticket is about.
comment:6 Changed 3 years ago by MatthewWilkes
It's pretty simple. You put the #13406 content in as an anonymous user and trac refuses it. It shouldn't. It was here as a test case so the problem can be verified.
Note: See
TracTickets for help on using
tickets.