Hi Pavel,
On 18 November 2018 at 21:30, Pavel N. Krivitsky wrote: | Hi, Dirk, | | Thanks for looking into this. It all makes sense, until this: | | > root@03c3abf866d1:/# which sed | > /usr/bin/sed | | As far as I can tell, the sed Debian package (all versions) puts the | executable in /bin/ , not in /usr/bin/ . The following package content | search confirms it: | https://packages.debian.org/search?suite=stretch&arch=any&mode=exactfilename&searchon=contents&keywords=sed . I just heard the same from R Core upstream (Hi Kurt, please see this bug log at http://bugs.debian.org/913982 for my "counter example" -- so far I cannot reproduce) | > R is pretty well organized that way -- configure will govern the R | > script and that will flow from /usr/bin/R. | | Thanks for the explanation. Granted, I am not very familiar with the R | build system. However, looking inside the | | r-base-core_3.5.1-1+b2_amd64.2.deb | | archive, I am seeing SED=/usr/bin/sed everywhere, so I don't think it's | a misconfiguration specific to my system. The Docker container I used and updated did not (yet?) have a changed sed location. Maybe that is only in unstable? Dirk | Best Regards, | Pavel | | -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org
