08:30 <felixfontein> is it normal that the bb check just waits forever in a PR? (https://github.com/buildbot/buildbot/pull/6121)

12:02 <p12tic> tardyp, skelly: Looks like subprocess.Popen(['my', 'arg', 'list'], shell=True) does not work on the new FreeBSD

12:02 <p12tic> Seems like a reason to switch to something else sooner rather than later

12:03 <p12tic> I could migrate events and buildbot to somewhere

12:04 <p12tic> I like the OSUOSL idea that was raised before

12:04 <p12tic> Could we ask OSUOSL about what we need to do to be able to host on their cluster?

12:07 <p12tic> felixfontein: It's just our scripts being not upgraded after OS upgrade on the system that runs buildbot.buildbot.net

12:10 <tardyp> p12tic: in my understanding, subprocess.Popen(['my', 'arg', 'list'], shell=True) should never work

12:10 <tardyp> when shell=True, the args should be a string

12:12 <tardyp> The shell argument (which defaults to False) specifies whether to use the shell as the program to execute. If shell is True, it is recommended to pass args as a string rather than as a sequence.

12:12 <tardyp> I don't like too much this phrasing

12:12 <tardyp> they do not say why

12:17 <tardyp> https://www.irccloud.com/pastebin/lCKECeX4/

12:17 <tardyp> I don't see why it wouldn't work on freebsd.

12:19 <tardyp> koobs is maitaining the freebsd packages. I think he would have detected this issue before

12:19 <tardyp> koobs: please see: https://github.com/buildbot/buildbot/pull/6122

12:20 <p12tic> so the issue is that e.g. /bin/sh -c yarn --version treats --version as the argument to the shell itself

12:20 <p12tic> /bin/sh -c "yarn --version" works

12:21 <p12tic> It's an interesting incompatibility that I guess people will get burned by

12:26 <tardyp> I guess it is indeed more /bin/sh which is different

12:26 <tardyp> on freebsd

12:28 <tardyp> might be derivated of csh and not bash like linux

12:28 <tardyp> this might also be the same for other bsd

12:28 <tardyp> on macos /bin/sh is bash

12:30 <p12tic> yes

12:30 <p12tic> tardyp: Will `ansible-playbook local.yml --vault-password=~/.vault-password` work on all jails?

12:32 <tardyp> yes, on bootstrap of a jail, the vault-password file is copied to the bbinfra user directory

12:34 <p12tic> great

12:34 <p12tic> my primary concern is not to break something by running local.yml

13:34 <felixfontein> p12tic: ah, so it's related to that :)

13:37 <tardyp> bash -c echo toto

13:37 <tardyp> does not echo anything

13:41 <tardyp> p12tic: are you really sure there are any shell which has "/bin/sh -c yarn --version" working?

14:10 <tardyp> bash -c yarn --version

14:10 <tardyp> --version: line 1: yarn: command not found

14:11 <tardyp> so in bash, the second argument after -c is the command name that is displayed for errors

17:43 <p12tic> tardyp: Indeed, looks like I should have selected a simplier example with echo like you say

17:43 <p12tic> yarn without --version still prints version number in the first line - that confused me

18:07 <tardyp> anyways, this is still a good catch!

18:32 <p12tic> tardyp: Could you green ligth https://github.com/buildbot/buildbot-infra/pull/243?

21:10 <dol-sen> tardyp, p12tic python3.9 setup.py install --skip-build --root=/var/tmp/portage/dev-util/buildbot-pkg-3.2.0/image/_python3.9

21:10 <dol-sen> warnings.warn(tmpl.format(**locals()))

21:10 <dol-sen> total of 2 of those in latest release

21:11 <dol-sen> * Normalizing '2021.06.17' to '2021.6.17'

21:11 <dol-sen> * Normalizing '2021.06.20' to '2021.6.20'

21:11 <dol-sen> any idea where???

21:12 <dol-sen> oh, is in buildbot-pkg

21:19 <dol-sen> I'm not finding it anywhere in hte tarball or sources

21:23 <dol-sen> must be a bug in our eclass...