CIDuty/How To/PyUp Dependency PR Updates: Difference between revisions

m
added link to other doc
m (added link to other doc)
 
(One intermediate revision by the same user not shown)
Line 26: Line 26:
# [https://github.com/mozilla-releng/mozilla-version/ Mozilla Version]
# [https://github.com/mozilla-releng/mozilla-version/ Mozilla Version]
# [https://github.com/mozilla-releng/build-puppet/ Build Puppet]
# [https://github.com/mozilla-releng/build-puppet/ Build Puppet]
# [https://github.com/mozilla-releng/treescript/ Treescript]
# [https://github.com/mozilla-releng/addonscript/ Addonscript]


== How To: Mozilla-Version ==
== How To: Mozilla-Version ==
Line 70: Line 68:
In order to correct that we need to pin it, and that can be done providing a "\" after the hash of the package, [https://github.com/mozilla-releng/mozilla-version/pull/36/commits/d8049b0bdf5201b986fb83bd37d804c6598468b8 example].
In order to correct that we need to pin it, and that can be done providing a "\" after the hash of the package, [https://github.com/mozilla-releng/mozilla-version/pull/36/commits/d8049b0bdf5201b986fb83bd37d804c6598468b8 example].
This situation can appear on both repositories and would be a good thing to ask around what can be pinned and what not.
This situation can appear on both repositories and would be a good thing to ask around what can be pinned and what not.
See also : [[CIDuty/How_To/Update_Python_dependencies|Update Python dependencies]]
canmove, Confirmed users
112

edits