FS#8403 - Downgrade Scribus to 1.3.3.10svn or 1.3.3.9

Attached to Project: Arch Linux
Opened by Branko Vukelic (foxbunny) - Wednesday, 24 October 2007, 16:35 GMT
Last edited by Roman Kyrylych (Romashka) - Monday, 29 October 2007, 09:19 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Kieslich (tobias)
Architecture i686
Severity Low
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Scribus is currently 1.3.4-1, however, that is a development version which is UNSTABLE and quite buggy. The release announcement for Scribus 1.3.4 was badly formulated which gave users an impression that this was the stable release. The currently recommended stable release is 1.3.3.10svn, or 1.3.3.9 (actually released version).

I believe packages in extra should be stable production versions, which disqualifies 1.3.4.

The 1.3.4 could be moved to unstable for those users who want to use the unstable development release (although 1.3.5 is already well into development) because 1.3.4 does not require qt4.

Here are the 1.3.3.9 sources:

http://www.scribus.net/index.php?name=Downloads&req=viewdownload&cid=34

The 1.3.3.10svn is here:

http://sourceforge.net/project/showfiles.php?group_id=125235&package_id=201484

Additional info:

* package version(s)

Scribus 1.3.4-1

* config and/or log files etc.

N/A

Steps to reproduce:

N/A
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Monday, 29 October 2007, 09:19 GMT
Reason for closing:  Fixed
Comment by Branko Vukelic (foxbunny) - Wednesday, 24 October 2007, 16:36 GMT
ADD: I was not aware of this until I spoke to guys on #scribus. They explained that the 1.3.4 release was a big misunderstanding. It is very buggy.
Comment by Branko Vukelic (foxbunny) - Wednesday, 24 October 2007, 16:39 GMT
Sorry, I wasn't looking. The SVN snapshot package is a Windows .exe, my bad.
Comment by Branko Vukelic (foxbunny) - Sunday, 28 October 2007, 13:20 GMT
Tobias, thanks for the quick response. I think this bug can be closed now.

Loading...