Bug 2796 - MSEC Sorry, the following package can not be selected: - due to conflict .....
Summary: MSEC Sorry, the following package can not be selected: - due to conflict .....
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 1
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Florian Hubold
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-21 09:26 CEST by Michel Morisot
Modified: 2011-10-20 11:32 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Michel Morisot 2011-09-21 09:26:49 CEST 
hello,

Description of problem:

Sorry, the following package can not be selected:

- Msec-0.80.10-2.1.mga1.i586 (due to conflict with sectool-0.9.3-1.1.mga1.i586)



Version-Release number of selected component (if applicable):

Msec-0.80.10-2.1.mga1.i586


How reproducible:


select rpm


Thank You
Remco Rijnders 2011-09-21 09:31:53 CEST

Assignee: bugsquad => doktor5000

Comment 1 Florian Hubold 2011-09-21 11:00:05 CEST 
Please next time don't blindly update from updates_testing. There is already a bug where the validation of this update gets tracked: Bug 2255.

In the meantime, you can install this update with rpmdrake.

Also i wonder where you got the part 
"(due to conflict with sectool-0.9.3-1.1.mga1.i586)"
from as there is clearly no conflict between those two.

Status: NEW => ASSIGNED

Comment 2 Michel Morisot 2011-09-21 11:17:24 CEST 
Just wanting to check in msec update applet. The action is denied, but msec-gui is ticked
Comment 3 Florian Hubold 2011-09-21 11:47:24 CEST 
Please install with rpmdrake until the update has been pushed from updates_testing to updates.
Comment 4 Samuel Verschelde 2011-09-26 23:42:16 CEST 
(In reply to comment #1)
> Please next time don't blindly update from updates_testing. 

Well, we need people who accept to install all updates from updates_testing and report any issue they would encounter. Sometimes it will be known issues, like in this case, but sometimes it can be unknown bugs. So don't scare our testers away ! :)

CC: (none) => stormi

Comment 5 Florian Hubold 2011-10-20 11:32:08 CEST 
Should be fixed by temporarily removing msec with wrongly added Requires from updates_testing until a proper update candidate is available (i.e. in the next few days).

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.