I don't see why it should be rebuild but let see that with the maintainer

CC: (none) => nicolas.lecureuil
Assignee: bugsquad => fundawang

Hi Manuel :
You may see bug 6782 comment 7
frescobaldi is the only package using python-poppler-qt4 (as a suggest but it may be a require) ... so it is the only software that shows the problem

indeed Python-poppler-qt4 was built with the previous version of python-qt4 (4.9-2) in december 2011

the version of python-qt4 actually used by Mageia2  is 4.9.1 provided in february 2012 and updated to 4.9.1-1 in july 2012 that is the reason of the mismatch between python-poppler-qt4 and python-qt4 in Mageia2

http://svnweb.mageia.org/packages/cauldron/python-qt4/releases/4.9.1/1.mga2/SPECS/python-qt4.spec?view=log

http://svnweb.mageia.org/packages/cauldron/python-poppler-qt4/releases/0.16.2/1.mga2/SPECS/python-poppler-qt4.spec?view=log

To Manuel :
I rebuilt this package on my own computer (I had only to use the various required devel rpm from core repo)
no problem to rebuild

I updated the installed version (from Mageia2 repo) with this rebuilt rpm

Now bug 6782 and bug 8035 are resolved on my computer !!!

Maybe Funda should be added to the CC list for this bug 8034...

A little off topic :

There seems to be a need of warnings for the dev (don't know how it can be created) to inform them that a rpm must be rebuilt when one of its BuildRequires has been updated.

This case is an illustration...

Perhaps have to mention explicitely the version of the BuildRequires used for this particular build  ??? so that dependancies are shown as broken when a BuildRequire is updated ?

*** Bug 6782 has been marked as a duplicate of this bug. ***

CC: (none) => laidlaws

thanks Funda
I saw you rebuilt it
I'll test the update as soon as it is in the repo

Regards

OK

Funda rebuilt it
it's in update_testing
it works for me :
MGA2 586

It may be proposed for QA

This package is required by only frescobaldi...
to test the update you need :
1) to have installed frescobaldi from core release first and (after a message complaining from missing python-poppler)
2) have installed python-poppler-qt4 from core release

I join a little lilypond file to test...

 when trying to display the score : an error message window appears
quit

3) update python-poppler-qt4
4) launch frescobaldi
open the same file
The score is correctly displayed in the right part of frescobaldi


The reason of the update :

python-poppler-qt4 had been built with a previous version of python-qt4 than the one provided by Mageia2 ... 

This update provide a new build that matches the python-qt4 version

Created attachment 3087 [details]
petite-ouverture-a-danser.ly

This file is a little score from Erik Satie written with Lilypond.
It may be opened by frescobaldi and then displayed and written as a pdf.

I can't install lilypond without removing gnucash (Bug 7283.)  Would you like me to do that and testy this fix?

No ... don't worry 
you will have to only if there's not any other MGA2 x86-64 tester

We already know it's OK for MGA2 586 

(and it certainly will for x86-64 : same diagnostic same cause same treatment)

I am running i586.

SRPM: python-poppler-qt4-0.16.2-1.1.mga2.src.rpm
------------------------------------------------
python-poppler-qt4

Is there a version for x86_64 which I can test?

The version in Cauldron for both is 0.16.2-1, dated Dec 17, but Comment 7 says that it can be updated in the usual way.  The SRPM is not specific to either architecture.  You should have what I have.

I've been running Mageia (and Mandriva and Mandrake) for several years, but I'm new at this bug-fix-testing process, and it's hard to find introductory info on how to participate.   Do I need to set up a Cauldron installation?   Install sources?  Find out how to get SRPMS and use them to build a package?   I guess this lack of HOWTO amounts to another bug.  :-)

(In reply to comment #15)
> I've been running Mageia (and Mandriva and Mandrake) for several years, but I'm
> new at this bug-fix-testing process, and it's hard to find introductory info on
> how to participate.   Do I need to set up a Cauldron installation?   Install
> sources?  Find out how to get SRPMS and use them to build a package?   I guess
> this lack of HOWTO amounts to another bug.  :-)

https://wiki.mageia.org/en/QA_Team - to get you started ;)

CC: (none) => sander.lepik

The simplest and less risky way to test those 2 rpms for 64 bits is to download them from these adresses with your web browser

ftp://ftp-stud.hs-esslingen.de/pub/Mirrors/Mageia/distrib/2/x86_64/media/core/updates_testing/frescobaldi-2.0.4-1.1.mga2.noarch.rpm

ftp://ftp-stud.hs-esslingen.de/pub/Mirrors/Mageia/distrib/2/x86_64/media/core/updates_testing/python-poppler-qt4-0.16.2-1.1.mga2.x86_64.rpm


When they are downloaded just right click on these rpm files in your file manager (in the directory where they were downloaded) and choose the install option (you will be asked to give your root password to install them).

Then you can use and test the updated version ...
Just let us know if Frescobaldi works well now.

(you can download and use the attached file in "Attachments" in the bottom of this page)

The revised python-poppler-qt4 and frescobaldi packages install successfully.  With that, frescobaldi now correctly displays PDF output after compiling a Lilypond piece.

@Richard: you've tested it for mga2 64bit, correct?

If you are interested in QA work, you can join the channel #mageia_qa on IRC, and subscribe to the mailing-list qa-discuss and say hello there. There you will get any help you need, to help us in QA :)

CC: (none) => marc.lattemann

Yes; sorry for the omission: that test was on x86_64.

(In reply to comment #19)
> @Richard: you've tested it for mga2 64bit, correct?
> 
> If you are interested in QA work, you can join the channel #mageia_qa on IRC,
> and subscribe to the mailing-list qa-discuss and say hello there. There you
> will get any help you need, to help us in QA :)

Ok - thanks.

then validating update.

suggested Advisory
==================
python-poppler-qt4 had been built with a previous version of python-qt4 than
the one provided by Mageia2 ... 

This update provide a new build that matches the python-qt4 version

SRPM: python-poppler-qt4-0.16.2-1.1.mga2.src.rpm



@Philippe: please update Advisory if necessary...


If advisory is OK, can sysadmin push package to Updates? Thanks.

Keywords: (none) => validated_update
CC: (none) => sysadmin-bugs
Whiteboard: has_procedure MGA2-32-OK => has_procedure MGA2-32-OK; MGA2-64-OK

mid air collision

I was doing the same thing as you and writing quite the same advisory ! yours is nice ... :)

Thanks Marc

NB
This validates update for bug 8035 too !

Thanks Philippe and Richard. We'd be glad of your help in the QA team.

https://wiki.mageia.org/en/QA_Team

Please give it some thought.

Update pushed:
https://wiki.mageia.org/en/Support/Advisories/MGAA-2012-0226

Status: NEW => RESOLVED
CC: (none) => tmb
Resolution: (none) => FIXED