Bug 2333 - activate the Youri::Submit::Test::Precedence check on submit
Summary: activate the Youri::Submit::Test::Precedence check on submit
Status: ASSIGNED
Alias: None
Product: Infrastructure
Classification: Unclassified
Component: BuildSystem (show other bugs)
Version: unspecified
Hardware: i586 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Sysadmin Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 858
  Show dependency tree / graph
 
Reported: 2011-07-29 22:23 CEST by Samuel Verschelde
Modified: 2015-09-10 16:02 CEST (History)
3 users (show)

See Also:
Source RPM:
CVE:
Status comment:

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

Description Samuel Verschelde 2011-07-29 22:23:16 CEST 
Please activate the submit check so that packages uploaded in the (n)th version of mageia always have a smaller EVR than those in the (n+1)th version

Note that it's better is the check is not only against cauldron, but against the (n+1)th version of Mageia, which will ensure that packages in updates will not break upgrade.
Comment 1 Marja Van Waes 2011-10-30 17:12:28 CET 
ping?

CC: (none) => marja11

Nicolas Vigier 2012-01-13 23:20:34 CET

Status: NEW => ASSIGNED
Blocks: (none) => 858

Dan Joita 2012-03-07 11:15:43 CET

CC: (none) => djmarian4u
Summary: Activate the Youri::Submit::Test::Precedence check on submit => activate the Youri::Submit::Test::Precedence check on submit

Comment 2 Samuel Verschelde 2013-08-26 19:18:13 CEST 
bi-yearly ping :)
Comment 3 David Walser 2013-08-30 22:58:06 CEST 
It'd also be nice if submitting to updates_testing in a stable release would refuse it if the same version/release exists in updates.
Comment 4 David Walser 2013-08-30 22:59:05 CEST 
And indeed we have Bug 7208 for that.

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=7208

Comment 5 Rémi Verschelde 2015-09-10 15:46:44 CEST 
Another bi-yearly ping :D
Comment 6 Samuel Verschelde 2015-09-10 16:02:43 CEST 
Ok, next ping is mine, remind me to ping sysadmins in October 2017
Note You need to log in before you can comment on or make changes to this bug.