Bug 6781 - check/or warn people if a package in tainted and core are not in the same version
Summary: check/or warn people if a package in tainted and core are not in the same ver...
Status: NEW
Alias: None
Product: Infrastructure
Classification: Unclassified
Component: BuildSystem (show other bugs)
Version: unspecified
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Sysadmin Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-14 20:34 CEST by Manuel Hiebel
Modified: 2014-04-03 00:15 CEST (History)
4 users (show)

See Also:
Source RPM:
CVE:
Status comment:

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

Description Manuel Hiebel 2012-07-14 20:34:31 CEST 
Description of problem:

In Mageia 2 there is/was a conflict with mesa.
In core/release we have the version 8.0.2-2.mga2 
and in tainted/release we have 8.0-1.mga2.tainted
see bug 6674, comment 1 (no other bugs reports against that for now)

so the idea is to add a check or a warning (in check.mageia.org ? I don't know if it's really for that) so we don't repeat this issue in the future
Manuel Hiebel 2012-07-14 20:34:56 CEST

CC: (none) => pterjan

Comment 1 Pascal Terjan 2012-07-14 20:37:15 CEST 
Checks are currently not run on tainted, else it would be detected by the "missing" check, as the binary packages are built from an old version of the src.rpm.
Helge Hielscher 2013-10-28 18:27:33 CET

CC: (none) => hhielscher

Comment 2 Damien Lallement 2014-04-03 00:15:06 CEST 
(In reply to Pascal Terjan from comment #1)
> Checks are currently not run on tainted, else it would be detected by the
> "missing" check, as the binary packages are built from an old version of the
> src.rpm.

What is needed to run checks on tainted?

CC: (none) => mageia
Note You need to log in before you can comment on or make changes to this bug.