[Geany-Users] proper upgrade technique

Sat Nov 14 14:21:36 UTC 2020

Le 11/11/2020 à 22:21, Geoff Kaniuk a écrit :
> The best I can do is to report that several Debian users have come
> across this kind of problem. For example,  someone asked: "Why is it so
> bad to have /usr/sbin in PATH?" The answer given in the forums was
> "Because sbin contains programs and scripts only executable by root".

This makes sense, but what's weird is that you don't have it when under
root with sudo:

$ sudo env | grep PATH
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

Basically your sudo probably doesn't reset enough of the environment,
which makes it harder to use and less secure (keeping PATH for example
is dangerous as it might trick you into running a program you didn't
expect, if someone hijacked your PATH).

I don't think I altered my sudo configuration, so I'm not sure why you
do have what you have (but I'm under Debian, not Ubuntu), but e.g. my
/etc/sudoers contain this (among other things):

> Defaults        env_reset
> Defaults        secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"

Anyway, you're not alone with such a configuration that doesn't reset
most of the environment (you can find similar problems on the Web), and
that causes issues.  I'm still not sure where that comes from, as I'm
almost positive I never touched this myself (and I checked on another
machine as well) so that it'd be Debian's default.  I'm not sure what
Ubuntu does, but it kind of sounds odd to me they would not have
env_reset be the default, or include sbin the sudo's path.

I'd recommend you to triple check whether your sudo config is as you
want it, and if you don't know, make sure it's Ubuntu's default.  Do
*NOT* trust the bits I pasted, as it's a highly sensitive configuration,
only use sources you trust and know what they are doing (e.g. the
manual, Debian/Ubuntu's maintainer, and… that's about what I'd trust).
If you're using all the expected defaults from Ubuntu, then I'd check if
they document how to do run admin commands like that.

All this said, for the problem at hand if it's indeed problematic with
stock Ubuntu setups, maybe we could go the sad way and hardcode
ldconfig's path; it's a hack for Ubuntu's broken ldconfig configuration
anyway, so it should not trigger anywhere else and we can thus use
Ubuntu's ldconfig path.  I'd rather avoid that if possible so the hack
is less specific and could work on other problematic setups, but well,
yout can't always get what you want.

Regards,
Colomban

> 
> Debian used to support gksu to get root access from a virtual terminal,
> but that is dropped in Buster.
> 
> Anyway, sudo -s is useful to know!
> 
> Geoff
> 
> 33 Ashbury Close, Cambridge CB1 3RW 01223 710582
> 
> On 11/11/2020 11:38, Lex Trotman wrote:
>> On Wed, 11 Nov 2020 at 21:31, Geoff Kaniuk <geoff at kaniuk.co.uk> wrote:
>>>
>>> I do not think I have modified $PATH from system settings:
>>> --------------------------------------------------------
>>> ~$ echo $PATH
>>> /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
>>> --------------------------------------------------------
>>
>> Your "whereis" puts ldconfig in /sbin/ but thats not in your PATH,
>> thats the problem.  I don't use debian, so I don't know why your PATH
>> is so limited.  By default my Mint has:
>>
>> /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
>>
>>
>> Cheers
>> Lex
>>
>>>
>>> Geoff
>>>
>>> 33 Ashbury Close, Cambridge CB1 3RW 01223 710582
>>>
>>> On 11/11/2020 00:24, Lex Trotman wrote:
>>>> Whats your PATH?
>>>>
>>>> On Wed, 11 Nov 2020 at 09:07, Geoff Kaniuk <geoff at kaniuk.co.uk> wrote:
>>>>>
>>>>> As far as I know, nothing special. But in Debian Buster:
>>>>> ---------------------------------------------------------
>>>>> ~$ whereis ldconfig
>>>>> ldconfig: /sbin/ldconfig /usr/share/man/man8/ldconfig.8.gz
>>>>> ---------------------------------------------------------
>>>>>
>>>>> The error message I got was:
>>>>> ---------------------------------------------------------
>>>>> /home# make install
>>>>> ...
>>>>> /bin/bash: line 3: ldconfig: command not found
>>>>> make[4]: *** [Makefile:1660: fix-ubuntu-libdir] Error 127
>>>>> --------------------------------------------------------
>>>>>
>>>>> There is some more information in the Debian forums:
>>>>> http://forums.debian.net/viewtopic.php?f=17&t=147179
>>>>>
>>>>>
>>>>> Geoff
>>>>>
>>>>> 33 Ashbury Close, Cambridge CB1 3RW 01223 710582
>>>>>
>>>>> On 10/11/2020 19:50, Frank Lanitz wrote:
>>>>>> On 09.11.20 14:17, Geoff Kaniuk wrote:
>>>>>>> 6. ~$ sudo make install
>>>>>>> On Debian that failed because of path problems locating ldconfig.
>>>>>>
>>>>>> This is unexpected for me. Running Debian for >10 years now and never
>>>>>> seen that need before. Do you have any special sh-configuration?
>>>>>>
>>>>>> .f
>>>>>> _______________________________________________
>>>>>> Users mailing list
>>>>>> Users at lists.geany.org
>>>>>> https://lists.geany.org/cgi-bin/mailman/listinfo/users
>>>>>>
>>>>> _______________________________________________
>>>>> Users mailing list
>>>>> Users at lists.geany.org
>>>>> https://lists.geany.org/cgi-bin/mailman/listinfo/users
>>>> _______________________________________________
>>>> Users mailing list
>>>> Users at lists.geany.org
>>>> https://lists.geany.org/cgi-bin/mailman/listinfo/users
>>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.geany.org
>>> https://lists.geany.org/cgi-bin/mailman/listinfo/users
>> _______________________________________________
>> Users mailing list
>> Users at lists.geany.org
>> https://lists.geany.org/cgi-bin/mailman/listinfo/users
>>
> _______________________________________________
> Users mailing list
> Users at lists.geany.org
> https://lists.geany.org/cgi-bin/mailman/listinfo/users