Univention Bugzilla – Bug 37479
Compare version numbers in 3.2-x-errata against 4.0-0
Last modified: 2023-03-25 06:49:24 CET
We need to ensure that the version numbers in 3.2-x-errata are always lower than the version in 4.0-0. Also bumping the version in 4.0-x-errata isn't sufficient, since UCS updates occur consecutively; a UCS 3.2 system is firstly updated to 4.0-0 and then to either 4.0-0-errata oder 4.0-1. We need an automated test which compares the version number of all binary packages in UCS 3.2-x-errata against their counterpart in 4.0-0.
Actually, we have a test in 00_checks/30_compare_package_versions added with Bug #36369, which at the moment shows the following: --------------------------------------------------------- The following packages use a smaller package version: --------------------------------------------------------- Package: icedtea-6-jre-cacao ucs_component/3.2-4-errata: 6b33-1.13.5-2.74.201412171318 ucs_4.0-0: 6b31-1.13.3-1.73.201406190130 Source package: openjdk-6 Package: openjdk-6-dbg ucs_component/3.2-4-errata: 6b33-1.13.5-2.74.201412171318 ucs_4.0-0: 6b31-1.13.3-1.73.201406190130 Source package: openjdk-6 Package: openjdk-6-demo ucs_component/3.2-4-errata: 6b33-1.13.5-2.74.201412171318 ucs_4.0-0: 6b31-1.13.3-1.73.201406190130 Source package: openjdk-6 Package: openjdk-6-doc ucs_component/3.2-4-errata: 6b33-1.13.5-2.74.201412171318 ucs_4.0-0: 6b31-1.13.3-1.73.201406190130 Source package: openjdk-6 Package: openjdk-6-jdk ucs_component/3.2-4-errata: 6b33-1.13.5-2.74.201412171318 ucs_4.0-0: 6b31-1.13.3-1.73.201406190130 Source package: openjdk-6 Package: openjdk-6-jre-zero ucs_component/3.2-4-errata: 6b33-1.13.5-2.74.201412171318 ucs_4.0-0: 6b31-1.13.3-1.73.201406190130 Source package: openjdk-6 Package: openjdk-6-source ucs_component/3.2-4-errata: 6b33-1.13.5-2.74.201412171318 ucs_4.0-0: 6b31-1.13.3-1.73.201406190130 Source package: openjdk-6 Affected source packages: openjdk-6 Number of affected binary packages: 7 Number of affected source packages: 1 This test is tagged as a 'producttest', thus it is not run on daily basis (as discussed with Philipp and Stefan some time ago). I think it should run at least with every errata update.
*** This bug has been marked as a duplicate of bug 36369 ***
Ok