| opendevreview | OpenStack Proposal Bot proposed openstack/requirements stable/2026.1: update constraint for os-ken to new release 4.1.2 https://review.opendev.org/c/openstack/requirements/+/994857 | 08:05 |
|---|---|---|
| opendevreview | OpenStack Proposal Bot proposed openstack/requirements master: update constraint for networking-generic-switch to new release 10.0.0 https://review.opendev.org/c/openstack/requirements/+/994865 | 09:24 |
| *** ykarel__ is now known as ykarel | 09:51 | |
| opendevreview | Merged openstack/requirements master: Updated from generate-constraints https://review.opendev.org/c/openstack/requirements/+/994169 | 11:02 |
| opendevreview | Merged openstack/requirements stable/2026.1: update constraint for os-ken to new release 4.1.2 https://review.opendev.org/c/openstack/requirements/+/994857 | 11:02 |
| frickler | fyi I've proposed to switch the reqs update cron to monthly in an attempt to reduce reviewer load (mostly my own ;) https://review.opendev.org/c/openstack/project-config/+/994923 | 14:54 |
| stephenfin | frickler: out of curiosity, what are the manual updates that are currently needed? | 15:08 |
| stephenfin | (I have seen your manual updates to the patches. I'm just missing the context on why they're needed) | 15:09 |
| frickler | stephenfin: I try to list the reasons in the commit message. for pyroute2 there is a bug in os-vif/nova/neutron that prevents using a newer version. maybe that cap could be hardcoded into one of the projects. then latest pytest causes swift unit tests to fail, so there is a manual cap to allow at least the remainder of the bumps to merge | 15:32 |
| frickler | the alternatives would be to not merge any updates until all issues are fixed, which would mean we could maybe have updates once per year. or have the bot propose one patch per library bumped, but that would end up in review- and merge-conflict hell | 15:33 |
| stephenfin | frickler: would I be stepping on toes if I took a look at automating those downgrades tomorrow? | 16:19 |
| stephenfin | I assume you'd be okay keeping it weekly if we could make the process less manual? | 16:20 |
| frickler | well most of the time the work is spent finding out what to upgrade/pin, not then performing the actual pin. but I'm open to look at what you come up with | 16:43 |
| mnasiadka | One patch per library wouldn’t be bad, but merge-conflict hell is surely not what we want to manage here | 17:03 |
| frickler | the insane part about that is, in reality there are no merge-conflicts for upper-constraints.txt, the relevant context is 0, which can be told to e.g. git-rebase as "-C0", but good luck telling gerrit and zuul about that | 18:33 |
Generated by irclog2html.py 4.1.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!