Bug 36369 - Ensure that version numbers in 4.0 are higher than in 3.2
Ensure that version numbers in 4.0 are higher than in 3.2
Status: CLOSED FIXED
Product: UCS Test
Classification: Unclassified
Component: General
unspecified
Other Linux
: P5 normal (vote)
: ---
Assigned To: Dmitry Galkin
:
: 37479 (view as bug list)
Depends on: 35387
Blocks: 36381
  Show dependency treegraph
 
Reported: 2014-10-31 13:55 CET by Sönke Schwardt-Krummrich
Modified: 2023-03-25 06:44 CET (History)
3 users (show)

See Also:
What kind of report is it?: Development Internal
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sönke Schwardt-Krummrich univentionstaff 2014-10-31 13:55:14 CET
Create a jenkins test that is based on/similar to the script attached to bug #35387. It should check all repos and compare package versions. The test has to fail if a lower package version number is found in a newer UCS release.

+++ This bug was initially created as a clone of Bug #35387 +++

Package which have only seen NMUs between squeeze and wheezy will usually have a version number smaller than the version in 3.2. The reason is our internal build stamp which appended during build.

Example:
strace in wheezy has version 4.5.20-2.3 in wheezy and had 4.5.20-2 in squeeze. Due to our internal build stamp the package in UCS 3.2 uses 4.5.20-2.11.201104221439 which is higher than the wheezy version. Consequently the package is kept back.

All version numbers in 4.0 and 3.2 need to be compared with a script and the version numbers adjusted and the packages rebuilt, e.g. as done in patches/strace/4.0-0-0-ucs/4.5.20-2.3/bump-version.patch (It must be ensured that he version in jessie is still higher!)
Comment 1 Dmitry Galkin univentionstaff 2014-12-12 14:42:43 CET
r56748:
  * 00_checks/30_compare_package_versions: test that package versions of
    the current release are higher than for the previous (Bug #36369).
    debian/control: added python* dependencies for '00_checks' section.


 - test tagged as 'producttest' to avoid daily run;
 - does similar checks to the original code, but for the remote mirrors:
   'http://testing.software-univention.de/',
   'http://software-univention.de/',
   'http://download.univention.de/',
   'http://updates.software-univention.de/'

and by downloading and reading the Packages.gz for every version (thus no need to access the build-system and fetch the output).

 - can compare versions specified as arguments or picks two the most recent found in the repository (default).
Comment 2 Dmitry Galkin univentionstaff 2015-01-19 10:46:52 CET
*** Bug 37479 has been marked as a duplicate of this bug. ***
Comment 3 Stefan Gohmann univentionstaff 2016-10-12 07:48:45 CEST
For this bug is no separate QA needed.
Comment 4 Florian Best univentionstaff 2019-03-11 13:18:10 CET
The test case either fails in UCS 4.4 or has some requirements:

### FAIL ###
The '/tmp/tmpjJMufi/component/4.3-0-errata/i386/Packages.gz' file is either empty or cannot be read.
###      ###

Performing cleanup after the test:
Removing folder: /tmp/tmpxEDtPc
Removing folder: /tmp/tmp3sPkrm
Removing folder: /tmp/tmpjJMufi

No errors were detected.

Starting 1 ucs-test at 2019-03-10 17:15:49 to /dev/null
UCS 4.4-0-e0 ucs-test 9.0.2-11A~4.4.0.201903111121
Check that package versions of the current release are higher than for the previous... Test failed