Closed Bug 1260224 Opened 8 years ago Closed 8 years ago

Upgrade hg version to 3.7.3 on linux build and test machines

Categories

(Infrastructure & Operations :: RelOps: Puppet, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dividehex, Assigned: dividehex)

References

Details

Attachments

(2 files, 2 obsolete files)

      No description provided.
Summary: Upgrade hg version to > 3.7.2 on linux build and test machines → Upgrade hg version to 3.7.2 on linux build and test machines
New hg packages for centos (both i386 and x86_64)
I've also added a custom repo for this going forward.
Attachment #8735622 - Flags: review?(dustin)
Attachment #8735622 - Flags: review?(dustin) → review+
3.7.3 came out on 2016-03-29 with some sec fixes, and gps recommends we use that.
Summary: Upgrade hg version to 3.7.2 on linux build and test machines → Upgrade hg version to 3.7.3 on linux build and test machines
This is almost identical to the last patch.  hg-3.7.3
Attachment #8735622 - Attachment is obsolete: true
Attachment #8738011 - Flags: review?(dustin)
Attachment #8738012 - Flags: review?(dustin)
Attachment #8738011 - Flags: review?(dustin) → review+
Attachment #8738012 - Flags: review?(dustin) → review+
Comment on attachment 8738012 [details] [diff] [review]
bug1260224-3-update-hg-ubuntu.patch

remote:   https://hg.mozilla.org/build/puppet/rev/adb2f9c2abf4
remote:   https://hg.mozilla.org/build/puppet/rev/52de085748fc

This had to be backed out.  I missed changing a dependency in debian/control
Attachment #8738012 - Flags: checked-in+ → checked-in-
Two things going on in this patch.

First, bumping the custom mozilla-python27-mercurial package to 3.7.3-1mozilla2 on ubuntu precise(12.04).  I've rebuilt hg in a single arch dependent deb package (both for i386 and amd64) to remain consistent with how it was built previously.  The package was tested on precise.

Second, during testing I noticed that packages::mozilla::python27 fails to install the custom python27 package on trusty.  The version specified is not available and I suspect it was never actually built for trusty.  And since packages::mozilla::python27 is a dependency for packages::mozilla::py27_mercurial, I'm opting to explicitly fail when including either on trusty.  They will need to be dealt with if we ever start using them there.  Building the custom python27 package for trusty is a rabbit hole I'm not getting anywhere near at this time.
Attachment #8738012 - Attachment is obsolete: true
Attachment #8740187 - Flags: review?(dustin)
Attachment #8740187 - Flags: review?(dustin) → review+
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: