There is now volumeicon-0.4.6 in core/updates_testing to validate ------------------------------------------------------- Suggested advisory: ------------------- already present in Cauldron, is a backport isn't present in Mandriva 2010.2 but i using it already in my HTPC with Mageia 1: https://wiki.mageia.org/en/File:Openbox.png https://wiki.mageia.org/en/User:Hman/MediaCenter_with_Mageia
You can't submit a backport to core/updates_testing, I'm sorry. We need backports media for that, and they still aren't open unfortunately.
CC: (none) => stormiAssignee: qa-bugs => hmandevteam
Yes, i read it, but i read also: https://wiki.mageia.org/en/Mgarepo#The_package_doesn.27t_exist_yet_in_Mageia_1 so i follow this steps
You told "isn't present in Mandriva 2010.2", so this package doesn't qualify to "There is however an exception for Mageia, on packages that were available in Mandriva 2010.2 but were forgotten in Mageia 1". Please also specify in your other bug reports if the package was present in Mandriva 2010.2
Ok, i know, sorry thanks
This one is actually in 2010.2. It is in contrib-backports (0.4.1-3mdv2010.2) What is our policy on upgrading from 2010.2 backports, it seems sensible to allow for that. I think the only real problem is the yajl package which isn't in Mandriva 2010.2 at all.
yes, i already closed yajl bug: http://bugs.mageia.org/show_bug.cgi?id=4817
If we start making exceptions for Mandriva 2010.2 backports (which we haven't so far), we are risking massive complications due to bug 2317. While volumeicon doesn't have any version specific requires, consider the following scenario. A user upgrades from 2010.2 to Mageia 1. They have backports installed with some version specific requires on some packages that we have in core release. Those core release packages get blocked during the upgrade, due to the backport package not being in Mageia 1. We add the backport as an update. User tries to install the update using mgaapplet. As the version specific required package from core is not in updates, the update will be rejected due to bug 2317. Our current depcheck script doesn't handle new packages, so we'll have to write a new one that can get old requires from the Mandriva repositories in order to determine which packages need linking from Core release to core updates. I'd have to dig through the mailing lists, but if I remember correctly, Mageia 1 only supported upgrading from Mandriva with plf, but not with backports. I think this should be discussed on the developers mailing list, as well as the sysadmin mailing list, before accepting new packages as updates, that were only in backports in Mandriva 2010.2.
CC: (none) => davidwhodgins
Sorry for the delay. I've finally gotten around to posting the question to the developers mailing list. Please be patient while the option to allow 2010.2 backports under the exception is discussed. As will be clear from my wording of the article, I'm against it, but due to bug 2317, I'm willing to keep an open mind, if anyone has a way of solving that bug.
Hi Dave, i understand your point of view, of course there are applications that requires many dependencies where tracking is costly and other (specially bytecode in java or mono or python) where is more simple tracking. I know also that we need of unique rule to manage package submission, distinguish case for case would be impossible to manage.
putting OK on the whiteboard, because the assignee has evidently been working on this backport
CC: (none) => marja11Whiteboard: (none) => OK
Component: RPM Packages => New RPM package requestWhiteboard: OK => OK cauldron
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. 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 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is 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
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => WONTFIX