as scribus 1.5.x is not yes completly stable we need to introduce back version 1.4.x ( qt4 based ) src.rpm: scribus-stable-1.4.4-1.mga6
Assignee: bugsquad => qa-bugs
1.4.6 is current scribus stable Nicolas https://www.scribus.net/downloads/stable-branch/
And furthermore, the development branch has a new version available, 1.5.3, which may fix the unspecified issues you're concerned about. We should update that.
Assignee: qa-bugs => mageiaCC: (none) => qa-bugs
scribus 1.5.3 is on updates_testing too. a user who reported pbs against scribus tested it and it is better but not perfect. I am updating to scribus 1.4.6 too. src.rpm: scribus-stable-1.4.6-1.mga6 scribus-1.5.3-1.mga6
Assignee: mageia => qa-bugs
Well I hope they have better luck with this Qt4 app than I had with others when testing during the Mageia 6 development cycle. Let's agree that when the next stable release comes out (1.6.0) that it will obsolete this scribus-stable package.
i will obsolete scribus-stable on cauldron today.
i just restart a build to fix build on arm
Willing to test 64-bit But I am confused about what is going on. The current issued version is scribus-1.5.2-6.mga6 Are we planning to offer scribus-1.5.3-1 as a regular update? To test. And scribus-stable-1.4.6-1 as an alternative new package?
CC: (none) => lewyssmith
exactly :) scribus as an update as branch 1.5 is a dev branch ( took more longer than expected ) and add back scribus-stable as a new package
This bug needs I think to be 2: 1. introduction of scribus-stable scribus-stable-1.4.6-3.mga6 2. update of scribus (development) to scribus-1.5.3-1.mga6 The two cannot co-exist. BTAIM Testing Mageia 6 64-bit 1. [This bug title] scribus-stable-1.4.6-3.mga6 Because this is not an update, it does not yet exist in normal repos, does not show in the Updates Testing available updates, but has to be installed directly from Updates Testing removing the issued devel version if that is present). Created a document with a single text frame + 2 image frames. This is inherently superb software, but sooo difficult to fathom & use. I can see why you would want this version! MGA6-64-OK (+ validation) once these bugs are sorted. 2. [New bug?] BEFORE update: scribus-1.5.2-6.mga6 Re-installed from normal repos, it takes out scribus-stable if that is present. Opened the previous document; it complained about profiles, used its default. No problem with this. It seems even more obscure than its predecessor. AFTER update: scribus-1.5.3-1.mga6 This has a major problem: In a text frame, F2 (properties) pops up a list of topics. This should include 'Text' for font etc; you can do nothing without it. It is *missing* in this update, but was present in the previous version. A stopper.
Blocks: (none) => 21607
Summary: Introduce back scribus-stable => Update scribus to new development release 1.5.3
Blocks: 21607 => (none)
Created attachment 9638 [details] Scribus 1.5.2-6 text frame properties Shows the full properties set for a text frame for M6 issued Scribus 1.5.2-6 In Welsh, but the important item is "Testun" = "Text".
Created attachment 9639 [details] Scribus 1.5.3-1 text frame properties Shows the text frame properties *for the same frame as previously* as displayed by this update Scribus 1.5.3-1. In Welsh, but it is missing the "Testun" = "Text" tab (between 'Grŵp' and 'Delwedd'). This renders the update useless; setting 'feedback'.
Whiteboard: (none) => feedback
Moving 'feedback' from whiteboard to keywords now that madb has been updated to handle that keyword.
Whiteboard: feedback => (none)Keywords: (none) => feedback
Keywords: feedback => (none)Assignee: qa-bugs => mageia
This message is a reminder that Mageia 6 is end of life. Mageia stopped maintaining and issuing updates for Mageia 6. At that time this bug will be closed as OLD (EOL). Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 6's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we cannot be able to fix it before Mageia 6 was end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad
CC: (none) => ouaurelienStatus: NEW => RESOLVEDResolution: (none) => OLD