Difference between revisions of "Scribus Times and Gazette"

From Scribus Wiki
Jump to: navigation, search
(The Case of the Missing SVN)
Line 15: Line 15:
After that, go back to <tt>svn up</tt> for updates.
After that, go back to <tt>svn up</tt> for updates.
Another bit of news &ndash; you can use the newer version of Scripter by adding to the cmake command:
<pre> -DWANT_SCRIPTER2=1</pre>
==Ancient Bug Fixed==
==Ancient Bug Fixed==

Revision as of 03:45, 6 January 2011

In generating this page, I would suggest that it be kept light-hearted and/or humorous, and in contrast to the mailing list, it will work better if you "top-post".


The Case of the Missing SVN

January 5, 2010

If you've been trying to update your Scribus SVN version(s), you've been having a rough time of it, no doubt. This is because the servers have been changed (too bad it's not April Fool's Day!).

You will need to completely get rid of your existing downloads and start all over:

  • svn co svn://scribus.net/branches/Version135/Scribus yourscribusdirname
  • svn co svn://scribus.net/trunk/Scribus yourotherscribusdirname

After that, go back to svn up for updates.

Another bit of news – you can use the newer version of Scripter by adding to the cmake command:


Ancient Bug Fixed

January 4, 2010

Reports are now circulating about the recent excavation and "fixing" of a long-standing bug which has been haunting Scribus for many versions. A recent post to the mailing list by LD pointed to this event, noting that inexplicably there was no major news conference scheduled for this announcement.

"We need people to know that such a long-time bug has been solved!", said LD.

The bug in question, #1908, submitted in the near-prehistoric 05-Apr-22, by a reporter only identifying himself as ikaratzas, mentions that he was having problems with dead keys while trying to use Scribus for (presumably ancient) Greek.

In an official response, mrdocs said, "The fact that there are many resolved, but unclosed bugs is simply a matter of lack of managment up to now. I have been regression testing some of these bugs against all the current development versions to ensure the fixes do not interfere or cause other problems for future releases."

He went on to credit archaeologic programmer Andreas Vox for doing the painstaking excavation, investigation, and correction of the errant commands required to finally extinguish this troublesome creature.

Bug #1686 was reported 05-Feb-19 and resolved 10-Dec-13. Comment made on IRC that the "The bug system works" elicited a response from mrdocs, "no, we work"