Hi, Oh? Hmm that's odd, the blender_multimail pyc file is still old, so it would appear that one wasn't called yet, or it's pyc file would have been recreated after I edited the py file:
-rwxr-xr-x 1 git git 85296 Aug 20 06:01 blender_multimail.py* -rw-r--r-- 1 git git 78850 Jun 8 2016 blender_multimail.pyc Unless it's meant to be git_daemon instead of git id, which is quite possible since git_daemon is the process it's running as. Let me make the dir group writable and see if it gets created as git_daemon, and could explain why the daemon process can't recreate the file, but could always run/read it. Ah, I also see the hoot/update and similar files for bf repo have an old python2 env shebang. Let me update that and then track down all the old ones. At a glance it seems that some are bash, but most are python2: #> find ./ -type f -name post-receive -exec head -n1 '{}' + | grep python2 ==> ./blender-addons.git/hooks/post-receive <== #!/usr/bin/env python2 ==> ./blender-translations.git/hooks/post-receive <== #!/usr/bin/env python2 ==> ./blender.git/hooks/post-receive <== #!/usr/bin/env python2 ==> ./gitosis-admin.git/hooks/post-receive <== #!/usr/bin/env python2 ==> ./blender-addons-contrib.git/hooks/post-receive <== #!/usr/bin/env python2 ==> ./phabricator.git/hooks/post-receive <== #!/usr/bin/env python2 Okay, I changed those few files to python2.7. Also, a `grep 'python2' */hooks/*` now shows only: blender-addons-contrib.git/hooks/post-receive:#!/usr/bin/env python2.7 blender-addons.git/hooks/post-receive:#!/usr/bin/env python2.7 blender-translations.git/hooks/post-receive:#!/usr/bin/env python2.7 blender.git/hooks/post-receive:#!/usr/bin/env python2.7 gitosis-admin.git/hooks/post-receive:#!/usr/bin/env python2.7 phabricator.git/hooks/post-receive:#!/usr/bin/env python2.7 So hopefully that is fixed now. Also, sorry for the hassle! These old systems collect dust ;) Note: $5 says we break mail again when I remove 2.7 :D Dan On Mon, Aug 20, 2018 at 12:39 AM Joshua Leung <aligor...@gmail.com> wrote: > Nope, emails still don't seem to be getting sent, but I also didn't see any > warnings about python2 when pushing, so at least we're seeing some progress > now ;) > > On Mon, Aug 20, 2018 at 4:07 PM Dan McGrath <danmcgrath...@gmail.com> > wrote: > > > Hi Joshua, > > > > Ah, that's probably the cause then. I was wondering why git wasn't > > relinking properly. Sure enough, the shebang for the mailhook blender > uses > > had `env python2` instead of `python2.7`. I've updated the mailhook for > > now. Try a commit and see how that goes? > > > > The more modern approach I think would be to use the one found in > > /usr/local/share that ships with svn (I test/use it now for the manual > > commits), but it's possibly lacking some of the output compared to the > one > > we have in use now from like 15 years ago :p > > > > > > Dan > > > > On Sun, Aug 19, 2018 at 11:58 PM Joshua Leung <aligor...@gmail.com> > wrote: > > > > > Hi Dan, > > > > > > Hmm... interesting. Maybe this is why most commit messages from the > last > > > day or so don't seem to have been coming through on the mailing list. > > The > > > last ones were from Aug 18th. > > > > > > Regards, > > > Joshua > > > > > > On Mon, Aug 20, 2018 at 3:52 PM Dan McGrath <danmcgrath...@gmail.com> > > > wrote: > > > > > > > Hi, > > > > > > > > Try again? Recently switched from py2.7 to py3.6 in there, but > > apparently > > > > it still thinks git should be linked to 2.7 for some reason. Worst > > case I > > > > can symlink, but lets see if reinstalling ports helps. Let me know, > > > thanks. > > > > > > > > > > > > Dan > > > > > > > > On Sun, Aug 19, 2018 at 8:08 PM Ray Molenkamp <r...@lazydodo.com> > > wrote: > > > > > > > > > All, > > > > > > > > > > Not sure who to poke for this, but since a few days when committing > > > > > through git push > > > > > > > > > > git it now spits back a python related warning/error > > > > > > > > > > k:\BlenderGit\blender>git push > > > > > Counting objects: 6, done. > > > > > Delta compression using up to 8 threads. > > > > > Compressing objects: 100% (6/6), done. > > > > > Writing objects: 100% (6/6), 696 bytes | 696.00 KiB/s, done. > > > > > Total 6 (delta 5), reused 0 (delta 0) > > > > > remote: env: python2: No such file or directory > > > > > To git.blender.org:blender.git > > > > > b6b6eab6ae9..2349273ade5 master -> master > > > > > > > > > > The commits still go through, anyhow, someone should probably look > at > > > > that? > > > > > > > > > > --Ray > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > Bf-committers mailing list > > > > > Bf-committers@blender.org > > > > > https://lists.blender.org/mailman/listinfo/bf-committers > > > > > > > > > _______________________________________________ > > > > Bf-committers mailing list > > > > Bf-committers@blender.org > > > > https://lists.blender.org/mailman/listinfo/bf-committers > > > > > > > _______________________________________________ > > > Bf-committers mailing list > > > Bf-committers@blender.org > > > https://lists.blender.org/mailman/listinfo/bf-committers > > > > > _______________________________________________ > > Bf-committers mailing list > > Bf-committers@blender.org > > https://lists.blender.org/mailman/listinfo/bf-committers > > > _______________________________________________ > Bf-committers mailing list > Bf-committers@blender.org > https://lists.blender.org/mailman/listinfo/bf-committers > _______________________________________________ Bf-committers mailing list Bf-committers@blender.org https://lists.blender.org/mailman/listinfo/bf-committers