There is now comex-0.1.6.1 in core/updates_testing to validate ------------------------------------------------------- Suggested advisory: ------------------- already present in Cauldron, is a backport its present in Mandriva 2010.2 backports with 0.1.6.0 release
seems we need specific hardware for this one
Depends on: (none) => 4815, 4820, 4821
it's the same hardware for monosim https://bugs.mageia.org/show_bug.cgi?id=4839#c10 monosim-qt and monosim-gtk use comex-base as hardware communication layer
ah yes so the install is ok on x86_64 for comex-0.1.6.1-1.mga1.noarch.rpm comex-gtk-0.1.6.2-1.mga1.noarch.rpm comex-qt-0.1.6.2-1.mga1.noarch.rpm (the other one was valided ) I will close the blocker
*** Bug 4820 has been marked as a duplicate of this bug. ***
*** Bug 4821 has been marked as a duplicate of this bug. ***
See https://bugs.mageia.org/show_bug.cgi?id=4839#c1 The monosim package was in contrib on Mandriva 2010.2. The comex packages were only in backports on 2010.2, so they don't fit the exception for installing as an update for Mageia 1, and backports has not been opened yet.
CC: (none) => davidwhodgins
Assigning back to the packager. Thanks for providing this update candidate, unfortunately we can't push it to updates media, we have to wait for backports media. Once backports media are opened for Mageia 1, if you still wish to provide comex for Mageia 1, please assign the bug back to QA but as a backport candidate in backports_testing (or just close this bug report and create a new one when ready). To sysadmins: please remove comex, comex-gtk and comex-qt from updates_testing.
Keywords: (none) => BackportCC: (none) => stormi, sysadmin-bugsAssignee: qa-bugs => hmandevteamSummary: Backport of comex from Cauldron => Backport of comex from Cauldron to Mageia 1
putting OK on the whiteboard, because the assignee has evidently been working on this backport
CC: (none) => marja11Whiteboard: (none) => OK
Keywords: Backport => (none)Component: RPM Packages => Backports
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