On 5/2/19 2:15 PM, Darshit Shah wrote: > That is a terrible suggestion. Please don't do that or suggest it. > I'm sure Jeffrey here is capable of knowing what this is and what the > implications of such a binary are.
I wouldn't call it 'terrible', but it's definitely not a good idea for multi-user production environments :-) It demonstrates the principle for a system where absolutely nothing else uses python3 - that's what Jeff was claiming. And so nothing breaks. It is even not easily possible (or just unwanted !?) to install python3; if it was easy, Jeff wouldn't have posted the question, I guess. > However, this is a publicly archived mailing list. People will find this when > they search the web in the future (not necessarily related to the same issue) > and this will break their systems in very confusing ways. Having in mind what someone *could understand in the future* without accounting the surrounding context... then let's not write anything at all ;-) > Making a fake binary in /usr/bin is something that should be done _very_ > _very_ > carefully. Never said, you should make it without thinking. Having root access to do so implies some qualifications. At least I am not afraid, that the python3 fake shit lands on some heart-lung apparatus. But as I said, it was just to demonstrate the principle. You could also put that file into some homedir subdirectory and add the dir to the front of your $PATH variable. Regards, Tim > > * Tim Rühsen <[email protected]> [190502 14:10]: >> On 5/2/19 10:09 AM, Tim Rühsen wrote: >>> On 5/2/19 10:02 AM, Jeffrey Walton wrote: >>>> On Thu, May 2, 2019 at 4:00 AM Tim Rühsen <[email protected]> wrote: >>>>> >>>>> Hi Jeff, >>>>> >>>>> On 5/1/19 11:38 PM, Jeffrey Walton wrote: >>>>>> On Wed, May 1, 2019 at 3:51 PM Tim Rühsen <[email protected]> wrote: >>>>>>> >>>>>>> could you post e.g. the content of tests/Test-504.log ? >>>>>> >>>>>> Yes, attached. >>>>>> >>>>>> Do you want an account on the box. I keep it around for testing, and I >>>>>> can make you admin. You can connect to it with 'ssh >>>>>> [email protected]'. If so, send over your authorized_keys. >>>>> >>>>> thanks for the offer, but this issue is not Solaris specific. >>>>> But if the need arises, I have access to the OpenCSW Solaris boxes :-) >>>>> >>>>> Please check README.checkout which lists python3 as requirement for >>>>> running the tests in testenv/ (as Darshit also pointed out). >>>> >>>> Ack, thanks. >>>> >>>> Since I got you on the line, how do I disable them. There is no need >>>> to run them if all they are going to do is fail. I did not see a >>>> configure option. >>> >>> Maybe the easiest way is before you bootstrap / autoconf (in the project >>> main dir): >>> >>> sed -i 's/ testenv//g' Makefile.am >>> >> >> Another way to do this once and forever: >> create /usr/bin/python3 with content >> exit 77 >> and chmod a+x it. >> >> If in doubt about the path, consult your $PATH variable. >> >> Regards, Tim >> > > >
signature.asc
Description: OpenPGP digital signature
