updating history in beta site
I've tried to add some item to 1.47 history in the beta site. I've edited .qbk file, and then went to site_tools directory. According to: http://www.boost.org/development/website_updating.html I am supposed to run 'site-tools.py update' there, but there's no such script, and running 'update.py' results in an error. On the 'live' site, I was able to do that, and in fact, I see new content on: http://www.boost.org/users/history/version_1_47_0.html So, it looks like this functionality is not working just in beta site? Thanks, -- Vladimir Prus CodeSourcery / Mentor Graphics +7 (812) 677-68-40
On 17 July 2011 22:17, Vladimir Prus <vladimir@codesourcery.com> wrote:
I've tried to add some item to 1.47 history in the beta site. I've edited .qbk file, and then went to site_tools directory. According to:
http://www.boost.org/development/website_updating.html
I am supposed to run 'site-tools.py update' there, but there's no such script, and running 'update.py' results in an error.
It is the beta site, it's where I do development so sometimes things don't work and haven't been documented yet. I tend to work on this kind of thing at the beginning of the release cycle, so that it's not changing as we prepare for the release. Btw. please try to avoid making changes to the release notes after a release, it causes them to reappear in people's feed readers which annoys them.
Daniel James wrote:
On 17 July 2011 22:17, Vladimir Prus <vladimir@codesourcery.com> wrote:
I've tried to add some item to 1.47 history in the beta site. I've edited .qbk file, and then went to site_tools directory. According to:
http://www.boost.org/development/website_updating.html
I am supposed to run 'site-tools.py update' there, but there's no such script, and running 'update.py' results in an error.
It is the beta site, it's where I do development so sometimes things don't work and haven't been documented yet. I tend to work on this kind of thing at the beginning of the release cycle, so that it's not changing as we prepare for the release.
OK. If that helps, the errors I get are below.
Btw. please try to avoid making changes to the release notes after a release, it causes them to reappear in people's feed readers which annoys them.
I understand, but then some other folks were surprised about b2 rename, so I though that's worth mentioning. (I will post a more detailed email later). -- Vladimir Prus CodeSourcery / Mentor Graphics +7 (812) 677-68-40 ghost@thunder:~/Work/Boost/beta/site-tools$ ./update.py Upgrading to new version. Upgrade 1 Quickbook Version 1.5.6 (trunk) (Boost 1.47) Converting feed/history/boost_1_47_0.qbk: Generating Output File: /tmp/.xmlUte2u0 feed/history/boost_1_47_0.qbk:1: warning: Invalid attribute for 'article document info': purpose Converting feed/history/boost_1_48_0.qbk: Generating Output File: /tmp/.xmlCukw1p feed/history/boost_1_48_0.qbk:1: warning: Invalid attribute for 'article document info': purpose Traceback (most recent call last): File "./update.py", line 16, in <module> boost_site.site_tools.update_quickbook() File "/home/ghost/Work/Boost/beta/site-tools/boost_site/site_tools.py", line 68, in update_quickbook item = generate_rss_item(rss_feed, qbk_page.qbk_file, qbk_page) File "/home/ghost/Work/Boost/beta/site-tools/boost_site/site_tools.py", line 143, in generate_rss_item description = xml.dom.minidom.parseString('<x>%s</x>' % page.description_xml) File "/usr/lib/python2.7/xml/dom/minidom.py", line 1924, in parseString return expatbuilder.parseString(string) File "/usr/lib/python2.7/xml/dom/expatbuilder.py", line 940, in parseString return builder.parseString(string) File "/usr/lib/python2.7/xml/dom/expatbuilder.py", line 223, in parseString parser.Parse(string, True) UnicodeEncodeError: 'ascii' codec can't encode character u'\xe1' in position 290: ordinal not in range(128)
On 17 July 2011 23:01, Vladimir Prus <vladimir@codesourcery.com> wrote:
OK. If that helps, the errors I get are below.
It's fixed now.
Btw. please try to avoid making changes to the release notes after a release, it causes them to reappear in people's feed readers which annoys them.
I understand, but then some other folks were surprised about b2 rename, so I though that's worth mentioning. (I will post a more detailed email later).
Oh, maybe it's okay actually. I forgot that in this release I added a link element to new feed items, and it looks like google reader has updated it without flagging it. I'm not sure what other feed readers do.
participants (2)
-
Daniel James -
Vladimir Prus