Closed Bug 730400 Opened 13 years ago Closed 13 years ago

Make sure that staging-opsi has the same package version as production-opsi

Categories

(Release Engineering :: General, defect, P3)

x86_64
Linux
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rail, Assigned: bhearsum)

Details

(Whiteboard: [opsi][buildduty])

No description provided.
Of which package?
Assignee: nobody → bhearsum
09:30 < rail> bhearsum|buildduty: all packages, I suspect that we have some outdated packages in staging
Diff of 'opsi-package-manager -l' output on production vs. staging, comments inline: production-opsi:~# diff -Naur my-versions.txt staging-versions.txt --- my-versions.txt 2012-03-05 15:47:28.000000000 +0100 +++ staging-versions.txt 2012-03-05 15:47:56.000000000 +0100 + autoit 3.4.4.0-2 Scripted GUI installation Unused package, don't care. - mozillabuild 1.4-1 MozillaBuild 1.4 + mozillabuild 1.5.1-2 MozillaBuild 1.5.1 This is due to coop looking at upgrading MozillaBuild recently, I reverted this package. + mozillamaintenance-service 1.0-1 Adds a scheduled tasks th This is something we decided not to deploy, removed it. - opsi-adminutils 3.4-5 opsi-configed 1.4.04 (28. + opsi-adminutils 3.4-1 Opsi-Configed 1.4 (29.5.0 I think this is just the opsi GUI, which we don't use on these machines. In any case, I'm too scared to try to match them up. - purge-builds 1.0-1 purge_builds.py Configura + purge-builds-staging 1.0-1 purge_builds.py Configura Looks like this is OK to be different judging by the names. ssh-config 1.1-1 SSH Configuration - ssh-config-staging 1.0-1 SSH Configuration for sta + ssh-config-staging 1.1-1 SSH Configuration for sta Similar here, I don't think ssh-config-staging is used on production-opsi, so I didn't change anything. So, no major issues here, closing as FIXED.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.