Hello, I did a wrong thing with my previous message :/ could you package perroquet software. I will try to propose spec file soon to accelerate availability of this software. Thanks
URL: (none) => http://perroquet.b219.org/
Pushed version 1.1.1 to Cauldron.
Status: NEW => RESOLVEDCC: (none) => jani.valimaaResolution: (none) => FIXED
Thanks, could you backport this package to Mageia 1?
Status: RESOLVED => REOPENEDResolution: FIXED => (none)
Version: Cauldron => 1Assignee: bugsquad => jani.valimaa
perroquet is now in updates_testing.
Assignee: jani.valimaa => qa-bugs
Testing of the srpm perroquet-1.1.1-1.0.mga1.src.rpm complete on i586. I used the Edit/Exercise Manager to import one of the exercises, played some sequences, experimenting with the settings under help.
CC: (none) => davidwhodgins
Please also test perroquet-1.1.1-1.1.mga1.src.rpm as I added gstreamer0.10-soundtouch to reqs. When started from cmd -1.0.mga1 displayed: "[VideoPlayer::WARNING] You need to install the gstreamer soundtouch elements to use slowly play feature." New release fixes this.
I tested perroquet-1.1.1-1.1.mga1.noarch (with gstreamer0.10-soundtouch support) on Mageia 1 (64-bits). Works fine. Thanks
With the change, it's now adding a dependency on libsoundtouch0, so I'm including this update as one that is blocked by bug 2317. Other than being blocked by bug 2317, the srpm perroquet-1.1.1-1.1.mga1.src.rpm testing on i586 is now complete. When it is ready, the Advisory should be Perroquet is a educational program to improve playfully your listening in a foreign language. This package was present in Mandriva 2010.2, but missing from Mageia 1.
Depends on: (none) => 2317
Doesn't 2317 only affect packages being updated rather than packages being added Dave? If they're already there and being updated but bring in new dependencies from release media? You might have noticed it as you were updating from a previous testing version rather than installing new. I was asking about it the other day in mageia-dev and that was the consensus. Defer to your experience with it though.
CC: (none) => eeeemail
2317 affects those updates that require something new from release. No matter if it's just update or added package to upgrade from mdv2010.1/2. If the added package can work with packages in release then there is no problem. But if added package needs something extra from release that was not needed in 2010.1/2 then it's affected by 2317. Update can't require anything new from release at the moment and so wouldn't work.
CC: (none) => sander.lepik
So, if I'm understanding correctly, we need to know whether gstreamer0.10-soundtouch was also required in the Mandriva release or is a new dependency? If so, how can we check for that please?
According to the Mandriva SVN gstreamer0.10-soundtouch is not a dependency for perroquet in current Cooker https://svn.mandriva.com/viewvc/packages/cooker/perroquet/current/SPECS/perroquet.spec?revision=685873&view=markup
CC: (none) => derekjenn
Mandriva doesn't seem to have such package at all so it seems to be new require. And if it can't be installed from updates then it is affected by 2317. To check it you would probably need mandriva install and such command as "urpmq --requires-recursive package"
For information about packages of other distributions, you can use http://sophie.zarb.org Deps for perroquet in Mandriva 2010.2 : http://sophie.zarb.org/distrib/Mandriva/2010.2/i586/media/contrib-release/by-pkgid/e3f97998a0c0ca8f599d41735993ffdf/deps Deps for perroquet in Mageia 1 Updates Testing : http://sophie.zarb.org/distrib/Mageia/1/i586/media/core-updates_testing/by-pkgid/41d35097e0adf4e49269b5f5cd55603b/deps
CC: (none) => stormi
Thankyou all for the explanation and the useful links. That is completely different to what I was told the other day. Sophie will make it easy to perform the checks. I heard a workaround was copying the dependencies into updates, is that correct, or will we need to add blocks until 2317 is resolved?
Yes, as i said, if requires can be installed from updates as well (as applet can use only those repos) then there is no problem. Tho' i would prefer hardlinking.
Currently packagers have no way to copy packages from release to updates, so we need the sysadmins to do that, hopefully with hardlinking.
Ok, thanks. So, from a QA perspective, are we able to validate and request the hardlinks or is it not yet finalised how this will be handled? Will/should it be handled when submitted to testing by the packagers? Obviously we'll need to check it anyway. PS. Sorry to hijack the bug.
(In reply to comment #18) > Ok, thanks. So, from a QA perspective, are we able to validate and request the > hardlinks or is it not yet finalised how this will be handled? Will/should it > be handled when submitted to testing by the packagers? > This is still unclear, so I'm sending a mail to the sysadmin's mailing list so that that can be defined.
Could you post the decision to QA when you get one please Samuel. Perroquet otherwise tested OK x86_64 with the Big Apple Hostel reservations.
(In reply to comment #9) > Doesn't 2317 only affect packages being updated rather than packages being > added Dave? If they're already there and being updated but bring in new > dependencies from release media? Bug 2317 is a real pain, made worse by supporting upgrading from Mandriva. Hypothetical example. Mandriva Package A has a dependency on Package B, with a specific version required. Package A is not in Mageia 1, but Package B is in Core Release. On upgrade, package B doesn't get upgraded, as it's version is required by A. When package A becomes available in updates, whether the Mageia package B will be needed by the Mageia package A depends on whether or not the Mandriva package B fulfils the dependency requirements of Mageia package A. If the Mageia package B from Core release is required, the update will fail.
> When package A becomes available in updates, whether the Mageia package B will > be > needed by the Mageia package A depends on whether or not the Mandriva package > B fulfils the dependency requirements of Mageia package A. I have nightmares about sentences like that :D Thanks for the added info though, I'll bookmark this bug I think so I can refer to it later!
As we can now work around bug 2317 by linking from release media this can be considered ready to be pushed. Advisory: ---------------- This update adds the language learning package Perroquet which was present in Mandriva 2010.2 but missing from Mageia 1. Perroquet is an educational program to improve, in a playful way, your listening comprehension in a foreign language. ---------------- SRPM: perroquet-1.1.1-1.1.mga1.src.rpm Please note this requires gstreamer0.10-soundtouch from core/release and I think also core/tainted to be linked. SRPMs - gstreamer0.10-plugins-bad-0.10.21-2.mga1.src.rpm and gstreamer0.10-plugins-bad-0.10.21-3.mga1.tainted.src.rpm Could somebody from sysadmin please push from core/updates_testing to core/updates & link the gstreamer packages. Thankyou!
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugsDepends on: 2317 => (none)
gstreamer0.10-plugins-bad is the one to be linked ?
CC: (none) => dmorganec
It requires gstreamer0.10-soundtouch from core and tainted. It's packaged in the plugins-bad and plugins-bad tainted SRPMs. What is it you need to know when linking, the SRPMs or the actual packages?
just the packages that need to be linked is enough for me.
linked done.
Status: REOPENED => RESOLVEDResolution: (none) => FIXED
Something strange is going on. The package gstreamer0.10-soundtouch in tainted and tainted updates is 0.10.21.3. In Core Release, it's 0.10.21.2, with no copy in Core Updates. The linking for Core doesn't seem to be done, and the version mismatch seems wrong.
new link done.
perroquet has never really been pushed to updates. Something went wrong here. Reopening.
Update pushed: https://wiki.mageia.org/en/Support/Advisories/MGAA-2012-0174
Status: REOPENED => RESOLVEDCC: (none) => tmbResolution: (none) => FIXED