Wednesday, 2022-10-26

*** tkajinam is now known as Guest396600:09
*** tkajinam is now known as Guest397201:47
*** marios is now known as marios|ruck05:26
*** tkajinam is now known as Guest398605:43
*** tkajinam is now known as Guest398806:53
*** amoralej|off is now known as amoralej07:13
jpodivinHi. I'm having bit of a quandary on my hands and I need an advice. validations-libs has fallen behind on releasing upstream changes. Normally we would just cut a new version, but the difference is substantial enough that I wonder if it wouldn't be better to release several micros at once. 07:57
jpodivinalternatively several in sequence ... but shortly after one another. 07:57
jpodivinBundling it together in one could still work. afaik there is nothing really problematic there.07:58
jpodivinbut it's a big jump07:58
elodillesi think several in sequence could work, no problem at all08:02
jpodivinelodilles: ok, we'll go with that 08:05
jpodivinthanks elodilles 08:05
opendevreviewJiri Podivin proposed openstack/releases master: Releasing validations-libs 1.7.2  https://review.opendev.org/c/openstack/releases/+/86267208:09
elodillesJayF: sushy-tools and virtualbmc releases look good to me, +2'd08:18
opendevreviewJiri Podivin proposed openstack/releases master: Releasing validations-libs 1.7.3  https://review.opendev.org/c/openstack/releases/+/86267308:25
opendevreviewJiri Podivin proposed openstack/releases master: Releasing validations-libs 1.7.4  https://review.opendev.org/c/openstack/releases/+/86267408:25
elodillesjpodivin: there is a version bump problem with the 1st release patch o:) see my comment on the patch08:52
elodillesjpodivin: oh, one more thing, i think the hashes are wrong as well. you should choose hashes always from the main branch (when a patch is merged with a 'Merge from' patch and the chosen hash is from that side-branch then it shows it's wrong)09:09
jpodivinelodilles: I'm getting the hashes from master log ... not sure how they could be wrong.09:14
jpodivinPatch is in the master. https://opendev.org/openstack/validations-libs/commit/8a69f95e0acf4b3acdff00b2094d476fa463bc8109:17
elodillesfor example a patch 'Title something' has a 'Merge "Title something"', then it shows that 'Title something is not the direct patch on master branch09:17
elodillesthat means 'Merge "Title something"' was the point where "Title something" patch became part of master branch.09:19
jpodivinelodilles: I kind of assumed that if something is in the branch, it's in the branch. Like if I were to revert the merge commit the code wouldn't really change.09:20
jpodivinit seems odd that would be duplicated in the history09:21
jpodivinif there joined with merge that is.09:24
jpodivin... reading up on the merge algo it makes sense now. https://git-scm.com/docs/git-merge#_true_merge09:27
opendevreviewMerged openstack/releases master: Release for VirtualBMC  https://review.opendev.org/c/openstack/releases/+/86264209:29
opendevreviewMerged openstack/releases master: Release for sushy-tools  https://review.opendev.org/c/openstack/releases/+/86264109:29
opendevreviewJiri Podivin proposed openstack/releases master: Releasing validations-libs 1.7.2  https://review.opendev.org/c/openstack/releases/+/86267209:30
opendevreviewJiri Podivin proposed openstack/releases master: Releasing validations-libs 1.7.3  https://review.opendev.org/c/openstack/releases/+/86267309:50
opendevreviewJiri Podivin proposed openstack/releases master: Releasing validations-libs 1.7.4  https://review.opendev.org/c/openstack/releases/+/86267409:50
elodillesjpodivin: a 1 is missing from the end of the hash (on the 1st patch) o:) and also, my previous comments are still valid o:)10:02
opendevreviewJiri Podivin proposed openstack/releases master: Releasing validations-libs 1.7.2  https://review.opendev.org/c/openstack/releases/+/86267210:04
jpodivinwe can't really release a major version because of dependency change though. Major releases are for backwards incompatible changes. Afaik we are still backwards compatible with previous releases10:07
elodillespy36 & py37 support is dropped. that kind of backward incompatible change10:07
elodillespypi won't list the new release for py36 versions10:08
jpodivinHypothetically you can still run code on them, it's just not something we support.10:08
jpodivinwhy wouldn't it?10:08
jpodivinyou mean because of the selectors? I guess that would be the case. 10:10
jpodivinin any case semver does provide some leeway https://semver.org/#what-should-i-do-if-i-update-my-own-dependencies-without-changing-the-public-api10:12
elodillesfor the record every deliverables that dropped the support of py36 & py37 bumped MAJOR version10:33
*** amoralej is now known as amoralej|lunch10:55
jpodivinelodilles: I guess we can't really break the common practice ... Ok, patches abandoned11:14
*** dviroel|afk is now known as dviroel11:28
opendevreviewMerged openstack/releases master: [vitrage] Transition Wallaby to EM  https://review.opendev.org/c/openstack/releases/+/86234312:22
*** amoralej|lunch is now known as amoralej12:31
opendevreviewMerged openstack/releases master: [murano] Transition Wallaby to EM  https://review.opendev.org/c/openstack/releases/+/86233212:31
elodilleshberaud ttx : it seems we have a release job failure: announce-release https://zuul.opendev.org/t/openstack/build/a970b3bf9bdc449f87e92ba7f77af60a : RETRY_LIMIT in 2m 07s12:59
elodillesthe cause is the job try to install the bindeps12:59
elodillesand python-dev is a py2 package12:59
elodilleswhich is not in ubuntu-jammy12:59
elodilles* not available12:59
elodillesi guess announce-release uses the default nodeset, which was probably changed to jammy recently13:00
elodilles(i see only ubuntu-focal until some days ago)13:01
elodillesthis is probably a relevant issue and can cause failed jobs in the future13:02
elodilleswhat is weird for me that why we need the bindep (of the released deliverable!) for the announce13:03
hberaudI see13:36
fricklerthe nodeset for the base job was switched to jammy yesterday, yes13:37
hberaudWe faced something similar on oslo with another packages (qpid) on jammy13:37
elodillesfrickler: ack, thanks for the info13:52
elodillesi'm trying to figure out why we need to install binary dependencies for the released deliverable13:54
elodillesanyway, maybe it is enough if projects fixes their bindep.txt to work with jammy13:54
fricklermight be to extract name and description https://opendev.org/openstack/releases/src/branch/master/tools/announce.sh#L176-L17914:00
fricklerthat might also need to be switched to invoke python3 instead of python on jammy14:01
elodillesfrickler: yepp, probably that is the reason. i haven't found anything else beyond that either14:17
elodilles'python' seems to be working14:18
elodilles(at least the announce-release job passed for sushy-tools: https://zuul.opendev.org/t/openstack/build/9b9aa6419d6341179120770cc3414070 )14:19
fricklerelodilles: ah, the script activates a venv, that has python in the path then, fine14:21
elodillesoh, cool, so that's the trick14:23
*** dviroel is now known as dviroel|lunch15:08
opendevreviewMerged openstack/releases master: [solum] Transition Wallaby to EM  https://review.opendev.org/c/openstack/releases/+/86233715:25
*** marios|ruck is now known as marios|out15:33
opendevreviewMerged openstack/releases master: [zaqar] Transition Wallaby to EM  https://review.opendev.org/c/openstack/releases/+/86230315:35
*** dviroel|lunch is now known as dviroel16:26
*** amoralej is now known as amoralej|off16:43
*** dviroel is now known as dviroel|afk20:03

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!