Confirmed users
18
edits
CIDuty/How To/PyUp Dependency PR Updates: Difference between revisions
CIDuty/How To/PyUp Dependency PR Updates (view source)
Revision as of 14:14, 29 September 2018
, 29 September 2018Added another common issue + fix
(WIP - How to work with PyUp PRs) |
(Added another common issue + fix) |
||
| Line 62: | Line 62: | ||
# Announce Bhearsum that the weekly PR is complete. | # Announce Bhearsum that the weekly PR is complete. | ||
=== Common Issues === | === Common Issues === | ||
1.Requirements of a dependency. Example: flake8 3.5.0 has requirement pycodestyle<2.4.0,>=2.0.0, but you have pycodestyle 2.4.0. | |||
With this issue, you have to keep which deps you have to either manually revert back at the older version (keep in mind you need the old sha512!) or if you pin the version of the dependency. | With this issue, you have to keep which deps you have to either manually revert back at the older version (keep in mind you need the old sha512!) or if you pin the version of the dependency. | ||
2.Another common issue regarding package versions, is that the bot will try and update a package several times if it's not pinned, thus braking things every week if that package cannot be updated because has another unmet dependency . | |||
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. | |||